Tekosue

---

⚡ The 30-second pitch

The problem. Rina (Indonesia), Wei (Singapore) and Jack (Australia) go to Japan together. Splitwise only records who owes whom. They still have to settle with three bank transfers across three countries, each slow, with fees and an exchange-rate loss. Local e-wallets don't cross borders. Crypto apps do, but they ask for seed phrases and gas tokens.

Tekosue. One pot for the whole trip:

flowchart LR
    A["🔑 <b>1. Sign in with a passkey</b><br/>Face ID, fingerprint or PIN<br/>no seed phrase, no gas token"]
    B["💵 <b>2. Everyone puts dollars in</b><br/>AUSD, from any country"]
    C["🧾 <b>3. Anyone pays from the pot</b><br/>recorded automatically<br/>big payments need a friend's OK<br/>left-out members can dispute"]
    D["✅ <b>4. The pot settles itself</b><br/>on the trip's end date:<br/>refund overpayers, collect the rest<br/>within each safety net"]
    E["📄 <b>Invoice for everyone</b><br/>Paid · Refunded · Due"]
    A --> B --> C --> D --> E

Why it only works on-chain. The money and the settle-up logic live in a contract, not with us. No one holds the funds, settlement is final in seconds, and everyone uses the same digital dollar, so there's no FX loss between friends. Monad makes this cheap and fast enough to feel like a normal payment app.

	Splitwise	Local e-wallet	Bank transfer	Tekosue
Tracks group spending	✅	Partly	❌	✅
Moves real money	❌ IOUs only	One country	✅	✅
Works across borders	Notes only	❌	Slow, fees, FX	✅ Same dollar for everyone
Settles up	Manually	Manually	Days	Automatically, in seconds
Needs crypto knowledge	No	No	No	No, just a passkey
Someone holds your money	n/a	Yes	Yes	No. The contract holds it, your key stays on your phone

Pitch video: youtu.be/2ba0CKPJkk8 · Product demo: youtu.be/Va0lA2mHJLw · Website: www.tekosue.xyz · Android APK: get the app

---

🎬 Demo videos

Video	Length	What it shows	Link
Product demo	~3 min	The real app on two Android phones: passkey sign-in, invite link, chip in, pay from the pot with a receipt, the other phone updating within seconds, automatic settle-up, the invoice, and the GroupVault contract on the Monad explorer.	▶ Watch on YouTube
Proof of work on Monad	43 s	The live website, the app sending a spend() transaction, the GroupVault contract on testnet.monadvision.com, and six real transactions (create, join, deposit, spend, receipt, settle) read straight from Monad testnet RPC, all success.	▶ Watch on X
30-second ad	30 s	The pitch in 30 seconds, for social.	▶ Watch on X

The proof-of-work transactions are on the current GroupVault (0x02Fb…bCE0) and anyone can open them on the explorer: createGroup · joinGroupWithPermit · depositWithPermit · spend · attachReceipt · settle. The videos are built with Remotion in video/demo. Follow along on X: @tekosuexyz.

---

🎯 Who it's for

Primary user: a mixed-nationality group of 3 to 10 friends on one shared trip. They met studying abroad, at work or online, they live in different countries now, and once or twice a year they meet somewhere new. None of them think of themselves as crypto users. Most have never held a stablecoin.

What happens to them today, and what Tekosue changes:

flowchart LR
    subgraph Today["😩 Today"]
      direction TB
      T1["<b>One person becomes the bank</b><br/>pays the villa up front,<br/>keeps a spreadsheet or Splitwise"]
      T2["<b>Settling up drags on for weeks</b><br/>3–4 transfers across banks and currencies,<br/>each with a fee and an FX loss"]
      T3["<b>Local apps stop at the border</b><br/>GoPay, PayNow, PayID: one country each"]
      T4["<b>Nobody wants a crypto wallet</b><br/>just to split a dinner"]
      T1 --> T2 --> T3 --> T4
    end
    subgraph With["😌 With Tekosue"]
      direction TB
      W1["Money goes in <b>before</b> the trip"]
      W2["Any member pays from the pot"]
      W3["The <b>last day settles itself</b>"]
      W4["Nobody plays banker,<br/>nobody learns what a wallet is"]
      W1 --> W2 --> W3 --> W4
    end
    Today ==> With

Who comes first, and who comes next:

flowchart LR
    N["🟢 <b>Now</b> (the demo story)<br/>Friends from several countries on one trip<br/><i>shared money across borders,<br/>without a banker friend</i>"]
    X["🟡 <b>Next</b>, once the pot has a card<br/>Groups from one country travelling abroad<br/><i>one pot to spend from at the destination</i>"]
    L["⚪ <b>Later</b><br/>Families and teams spread across countries<br/><i>a recurring pot for events and shared costs</i>"]
    N --> X --> L

---

📱 Try it

The judge path through the app (each screen is a real route in apps/mobile):

flowchart TD
    W[Welcome] --> S["Sign in<br/>🔑 one passkey prompt"] --> H[Home]
    H --> N["New trip<br/>end date + approval limit"] --> I[Share invite link]
    I --> J["Friend joins with a passkey<br/>agrees to the trip's safety net"]
    J --> M["Add money to the pot"]
    M --> P[Pay from pot]
    P --> Q{Above the<br/>approval limit?}
    Q -- no --> F[Paid instantly]
    Q -- yes --> R[Request approval] --> A[A friend approves<br/>on their phone] --> F
    F --> E[Trip end date passes]
    E --> X["⚙️ The pot settles itself"]
    X --> V["📄 See your invoice<br/>Paid · Refunded · Due"]
    V --> QR["Scan the QR"] --> WEB["www.tekosue.xyz/v/…<br/>checks the invoice against<br/>the trip record"]

Step	What you'll see
Sign in	One passkey prompt (Face ID, fingerprint or PIN). The passkey derives the account key on the device (Mera).
New trip / Invite	Pick an end date and an approval limit, share a link. Friends join with one tap and one passkey confirmation.
Join	"Join with Passkey" on the invite. The trip creator's safety net (the most the trip may pull from you at settle-up) is shown first; joining means you agree to it. One confirmation.
Add money	Put dollars in the pot whenever you like, one confirmation (no separate "approve").
Pay from pot	Amount, who it was for, optional receipt photo. Above the limit → a friend approves on their phone.
Trip	Live pot balance, activity feed, "who owes whom" preview, all read from the Envio indexer.
Settled	Each member's invoice with Paid / Refunded / Due, a Pay button for debts, PDF export, and a QR code anyone can verify on the web. Someone who still owes sees "You still owe $X" and can't start or join a new trip until it's paid.
Invite link on the web	www.tekosue.xyz/j/<code> shows the real trip (name, members, end date, pot) before the app is installed, then opens the app.
Invoice check on the web	www.tekosue.xyz/v/<number> rebuilds the invoice from the indexed settle-up and says whether it matches. No sign-in needed.

If someone doesn't pay. Whatever a safety net couldn't cover at settle-up stays as a bill on their invoice. Nothing is frozen and the money stays theirs, but until the bill is paid the contract won't let them start or join another trip:

flowchart LR
    S["Settle-up computes<br/>a member's share"] --> C{Covered by<br/>their safety net?}
    C -- yes --> OK["✅ Paid"]
    C -- no --> B["🧾 The rest becomes a bill<br/>on their invoice"]
    B --> G["🚫 Can't start or join<br/>a new trip (OutstandingDebt)"]
    B --> R["🔔 Daily reminder +<br/>'You still owe $X' with a Pay button"]
    B --> K["Trips they're already in<br/>keep working · nothing frozen"]
    R --> PAY["Pay → straight to the creditor<br/>(payDebtWithPermit)"] --> OK

Install on Android: open www.tekosue.xyz/get-app on your phone. It runs live on Monad testnet; sign in with a passkey (Android needs a screen lock, and Google Password Manager stores the passkey).

Run it yourself: see Getting started.

---

🧭 How it works

sequenceDiagram
    autonumber
    actor R as Rina (ID)
    actor W as Wei (SG)
    participant App as Tekosue app<br/>(passkey key on device)
    participant V as GroupVault<br/>(Monad testnet)
    participant E as Envio HyperIndex
    participant S as Settle scheduler

    R->>App: Passkey (Face ID / fingerprint / PIN)
    App->>V: createGroup(endDate, approvalLimit, safetyNet)
    W->>App: Opens invite link + passkey
    App->>V: joinGroupWithPermit(inviteSig, safetyNet)<br/>one transaction, no "approve" step
    W->>App: Add money
    App->>V: depositWithPermit(amount)
    R->>App: Pay $42 dinner for everyone
    App->>V: spend(amount, participants, noteHash)
    V-->>E: events
    E-->>App: pot balance, feed, who-owes-whom
    S->>V: settle(groupId) on the end date
    V->>R: refund what Rina overpaid
    V->>W: pull Wei's share (up to safety net) or record debt
    W->>App: Pay invoice
    App->>V: payDebtWithPermit → paid straight to the creditor

How the pot settles itself (per member, inside settle(groupId)):

flowchart TD
    T["⏰ End date + dispute window passed<br/>the scheduler (or anyone) calls settle(groupId)"] --> N["For each member:<br/>net = deposited − their share of spends"]
    subgraph Phase1["Phase 1 · members who owe the pot"]
      P1["Pull what they owe, capped by<br/>safety net, balance and allowance"] --> C1{Pulled in full?}
      C1 -- yes --> PAID["Paid"]
      C1 -- "no / transfer failed" --> DEBT["The rest becomes debt → Due<br/>(blocks new trips until paid)"]
    end
    subgraph Phase2["Phase 2 · members who put in too much"]
      P2["Refund from the pot, pro rata<br/>if the pot is short"] --> C2{Transfer OK?}
      C2 -- yes --> REF["Refunded"]
      C2 -- "no (e.g. frozen account)" --> CRED["Kept as claimable credit"]
    end
    N --> P1
    PAID & DEBT --> P2
    REF & CRED --> INV["📄 Pulled / Refunded / Settled events<br/>→ Envio → invoices for everyone"]

Design choices that matter

• Settle-up can never get stuck. One frozen account or a missing allowance would normally revert the whole settlement. GroupVault uses try-transfers: a failed pull becomes a debt, a failed payout becomes a claimable credit. Invariants are fuzz-tested in Foundry.
• Invites can't be replayed or front-run. The invite link carries a one-time key; the joiner signs inviteDigest(groupId, joiner), so a signature only works for that person.
• One passkey confirmation per action. AUSD's EIP-2612 permit is bundled in (joinGroupWithPermit, depositWithPermit, payDebtWithPermit), so there's no separate approve transaction.
• No gas token for users. The backend drips a little MON to new accounts for their first transactions. It holds gas keys only, never user keys or user funds.
• Unpaid bills block new trips, nothing gets frozen. Whatever a safety net couldn't cover becomes a bill. Until it's paid, the contract refuses to let that person start or join another trip (OutstandingDebt), and they get a daily reminder. Their money is never frozen and the trips they're already in keep working.
• Anyone can check an invoice. The invoice QR opens www.tekosue.xyz/v/<number>, which rebuilds the invoice from the indexed settle-up with the same code the api uses and compares fingerprints. No sign-in, no trust in our server.
• Money lives only on-chain. Balances, spends and settlement come from the contract via Envio. The database stores labels only (names, trip titles, encrypted receipts), and each label is bound to an on-chain hash (noteHash, receiptHash) so it can't be swapped.
• No crypto words in the UI. Users see "pot", "safety net", "receipt", "invoice" and dollar amounts. Never "wallet", "gas", "token" or "hash".

---

🤝 Sponsor integrations

Each sponsor has one clear job in the product, and every integration runs for real on Monad testnet. The only simulated parts are the card network and the bank side of Top up / Cash out, and the app labels them as simulated.

Sponsor	Role in Tekosue	Where
Agora · AUSD	The only money. Deposits, spends, settle-up and invoices are all in AUSD (6 decimals, bigint end to end). Uses EIP-2612 permit for one-step joins and payments, and handles isAccountFrozen without blocking a settle-up.	GroupVault.sol, chain.ts
Monad	Settlement layer. Fast finality makes "Processing → Done" feel like a card payment, and cheap execution makes a full multi-member settle-up practical.	packages/contracts
Mera (Category Labs)	The entire account layer: passkey → PRF → on-device secp256k1 signing session → viem account. No other wallet, no extension, no seed phrase, no custody.	src/wallet, ADR 0003
Envio HyperIndex	The read model for money: pot balance, activity feed, positions and "who owes whom" in the app; the live invite page and invoice verification on the web; and the event source for push notifications and debt reminders in the api.	packages/indexer, envio.ts, apps/web/src/data/live,

---

🟢 Live on Monad testnet

	Address / URL
GroupVault	0x02Fb964B6b4470C14D61738EC0a296fa9F2dbCE0 (block 68690383) · unpaid debt blocks new trips (ADR 0013)
AUSD (Agora)	0xa9012a055bd4e0eDfF8Ce09f960291C09D5322dC
Envio GraphQL	https://graphql.mulalabs.biz.id/v1/graphql
API	https://api.mulalabs.biz.id/health
Website	https://www.tekosue.xyz (invite links /j/…, invoice checks /v/…, download page /get-app)

Real transactions you can open right now. Every step of the trip lifecycle, decoded from the transaction input. The current contract lives at 0x02Fb…bCE0; it was created by deploy transaction 0x5bdf1228…d6a6 in block 68690383. All rows run on that contract (trip #1 on 6–7 Oct, the approval on trip #2 on 12 Oct) except the one marked v0, which ran on the first deployment (0x1467…B7ee, same function; the current contract adds the unpaid-debt rule) because no settle-up on the current contract has left a bill yet.

Step	Contract call	Transaction
Create a trip	createGroup	0x1636a212…983c
Join + agree to the safety net, one signature	joinGroupWithPermit	0x01b96530…69b3
Add money to the pot	depositWithPermit	0x5b14838d…2cad
Pay from the pot	spend	0x4ed570d5…a792
Attach an encrypted receipt	attachReceipt	0x98988f1a…babd
Ask for approval of a big payment ($90 hotel, above the limit)	spend	0x77bdba1f…520a
A different member approves it, and the pot pays	approveSpend	0x43c4fd26…599c
The trip settles itself	settle

What's built

flowchart LR
    classDef done fill:#dff3ec,stroke:#1f7a6e,color:#123
    classDef wip fill:#fff1e0,stroke:#d9822b,color:#321

    C["✅ <b>GroupVault</b> deployed + verified<br/>signed invites, permit flows, approvals,<br/>disputes, receipts, settle-up, debts & credits,<br/>unpaid debt blocks new trips<br/><i>28 Foundry tests incl. fuzzed invariants</i>"]:::done
    I["✅ <b>Envio indexer</b> hosted<br/>13 event handlers (12 GroupVault<br/>events + AUSD transfers),<br/>enough to rebuild every invoice"]:::done
    A["✅ <b>API</b> deployed<br/>settle scheduler, MON drip, SIWE login,<br/>labels bound to on-chain hashes, invoices,<br/>push + daily debt reminders from Envio,<br/>Nudge for pending approvals<br/><i>61 tests</i>"]:::done
    M["✅ <b>Mobile app</b> (Android APK)<br/>Mera passkey sign-up + signing on real phones,<br/>every screen live on testnet, invoices with PDF + QR,<br/>invite deep links, feed, encrypted receipts,<br/>card history, background push (Firebase),<br/>'You still owe' guard,<br/><i>tested end to end on two phones:<br/>payments show on the other phone in seconds</i>"]:::done
    W["✅ <b>Website</b> www.tekosue.xyz<br/>landing, download page, live invite pages,<br/>invoice verification, passkey domain files"]:::done
    P["🟠 <b>In progress</b><br/>iPhone build (needs Apple Team ID)"]:::wip

    C --> I --> A --> M --> W -.-> P

Receipts design: ADR 0008. Mera signing path: src/wallet (web and Expo Go fall back to an on-device demo key).

Full progress: docs/STATUS.md.

---

🏗 Architecture

flowchart LR
    subgraph Phone["📱 apps/mobile (Expo)"]
      UI[Screens] --> Mera[Mera passkey<br/>signing session]
    end
    Mera -- signed tx --> Vault[(GroupVault<br/>Monad testnet)]
    Vault -- AUSD --> AUSD[(AUSD · Agora)]
    Vault -- events --> Envio[Envio HyperIndex<br/>+ Hasura GraphQL]
    Envio -- balances, feed --> UI
    UI -- labels, receipts --> API[apps/api<br/>Express]
    API --> DB[(Neon Postgres<br/>labels only)]
    API -- settle on end date,<br/>MON drip --> Vault
    Envio -- new events --> API
    API -- push + debt reminders --> Phone
    Web[apps/web · www.tekosue.xyz<br/>static Next.js] -- trip data, settle records --> Envio
    Web -- shared invoice, trip name --> API

Repository layout:

flowchart TB
    R(("tekosue<br/>monorepo"))
    subgraph Apps["apps/"]
      AM["<b>mobile</b><br/>Expo + Expo Router<br/>every user interaction"]
      AW["<b>web</b><br/>static Next.js on Vercel<br/>landing, /get-app, invite links,<br/>invoice check, passkey domain files"]
      AA["<b>api</b><br/>Express in Docker<br/>settle scheduler, MON drip, metadata,<br/>invoices, push from Envio"]
    end
    subgraph Packages["packages/"]
      PC["<b>contracts</b><br/>Foundry · GroupVault.sol"]
      PI["<b>indexer</b><br/>Envio HyperIndex<br/>read model for money"]
      PS["<b>shared</b><br/>ABI, addresses, chain,<br/>money helpers, zod schemas"]
    end
    D["<b>docs/</b><br/>BRD, PRD, spec, user stories,<br/>flows, screen map, ADRs"]
    R --> Apps
    R --> Packages
    R --> D
    PS -. used by .-> AM & AW & AA & PI

Product, design and planning docs live in docs/; design decisions are in docs/decisions/.

---

🚀 Getting started

Requirements: Node 22+ (npm), Foundry, Docker (for the Envio indexer).

npm install
cp .env.example apps/mobile/.env           # fill in the values
cp apps/api/.env.example apps/api/.env      # backend secrets (RELAXED_ENV=true to boot locally without all of them)
npm run start -w @tekosue/mobile
npm test -w @tekosue/contracts

The app runs with demo data by default. Set EXPO_PUBLIC_DATA_SOURCE=live (plus the vault, Envio and API URLs from the table above) to use Monad testnet.

Backend services in Docker

docker-compose.yml runs Hasura, the Envio indexer and the api. There is no local Postgres: both the indexer and the api use Neon. Mobile runs separately (Expo), and web deploys standalone to Vercel.

Secrets stay in each package's gitignored .env:

• apps/api/.env: the api's Neon database, drip/settler keys, JWT.
• packages/indexer/.env: ENVIO_API_TOKEN, ENVIO_PG_* and HASURA_GRAPHQL_DATABASE_URL (see .env.example). Use a separate Neon database from the api's (Envio may DROP SCHEMA … CASCADE on reset) and the direct host, not -pooler.

npm run docker:up     # build + start in the background
npm run docker:ps     # status
npm run docker:logs   # follow logs
npm run docker:down   # stop

Service	URL
api	http://localhost:3001/health
Hasura / Envio GraphQL	http://localhost:8080 (console, admin secret testing) · /v1/graphql
indexer	http://localhost:9898/healthz

Port 8080 clashes with envio dev, so stop that stack first (envio stop). Host ports and the Hasura secret can be overridden in a root .env (API_HOST_PORT, HASURA_HOST_PORT, INDEXER_HOST_PORT, HASURA_ADMIN_SECRET). Then run mobile against it as usual (EXPO_PUBLIC_API_URL=http://localhost:3001, EXPO_PUBLIC_ENVIO_GRAPHQL_URL=http://localhost:8080/v1/graphql).

Website

npm run dev -w @tekosue/web                                # landing + demo dashboard (next dev)
npm run build -w @tekosue/web && npm run preview -w @tekosue/web   # static export with the /j and /v rewrites

next dev only knows the placeholder shells /j/_ and /v/_; use the preview server to open real invite codes and invoice numbers. Point it at your own backend with NEXT_PUBLIC_API_URL and NEXT_PUBLIC_ENVIO_GRAPHQL_URL at build time. Production runs on Vercel with apps/web/vercel.json.

Brand assets

App icons, Android adaptive icon, splash, favicons, the web Open Graph image and the banner above are generated from tekosue-mark.svg, tekosue-mark-mono.svg and tekosue-logo.svg by scripts/brand-assets.mjs (instructions at the top of the file).

---

🧪 Testing with real people

The bar for this track is a non-crypto user finishing the core flow without help. We test exactly that, with people who don't use crypto, on the demo path: sign in, join a trip, pay from the pot, open a receipt, read the invoice. Script, tasks and the observation sheet: docs/user-testing.md.

flowchart LR
    U["👥 <b>5 people</b><br/>zero web3 experience<br/>no wallet, never held a stablecoin"]
    U --> T1["🔑 Sign in<br/>with a passkey"] --> T2["🔗 Join a trip<br/>from an invite link"] --> T3["💵 Pay<br/>from the pot"] --> T4["🧾 Open<br/>a receipt"] --> T5["📄 Read<br/>the invoice"]
    T5 --> RES["✅ <b>5 of 5</b> finished<br/>the core flow without help"]

	Result
People tested	5, none with any web3 or crypto experience
Finished the core flow without help	5 of 5

Changes made from our walkthroughs: every form now starts empty instead of pre-filled, disabled buttons say what is missing ("Choose your safety net"), and every word that hinted at a blockchain (fingerprints "on Monad", "view proof", "transaction") was replaced with plain language.

---

📣 How the next 100 users find us

1. Every trip recruits its own users. A trip only works when friends join it, so each person who starts a trip brings 2 to 9 new people through the invite link, and that link is the whole onboarding. Around 20 trip creators are enough to reach 100 users.
2. Start where mixed-nationality trips are planned. Student associations abroad and exchange-alumni groups, travel group chats, and digital-nomad communities in places like Bali are full of friend groups planning their next meetup.
3. Group-trip organisers. Organisers of small open trips already collect money from people who don't know each other well, using spreadsheets and bank transfers. One pot with automatic settle-up replaces that whole workflow, and every trip they run brings 5 to 15 travellers.
4. Show the moment it settles. Short videos of the last day of a trip, when everyone's balance evens out in seconds with nobody chasing anyone. That moment is easy to understand and easy to share.

flowchart LR
    CH["📣 <b>Channels</b><br/>student associations abroad,<br/>exchange alumni, travel chats,<br/>digital nomads in Bali"] --> CR
    ORG["🧳 <b>Trip organisers</b><br/>each trip brings<br/>5–15 travellers"] --> CR
    VID["🎬 <b>Settle-up videos</b><br/>the moment balances even out"] --> CR
    CR["Trip creator<br/>starts a trip"] --> INV["Invite link =<br/>the whole onboarding"]
    INV --> J["2–9 friends join"]
    J --> NT["Some of them start<br/>their own trip"] --> CR
    J --> M["~20 creators ≈ 100 users"]

What we will watch: trips started, the share of invitees who actually join, and how many groups start a second trip.

---

🛣 What's next

flowchart LR
    A["🔒 <b>Real money</b><br/>contract audit,<br/>Monad mainnet,<br/>fiat on/off-ramp partners"]
    B["💳 <b>A card for the pot</b><br/>pay at a shop in Japan<br/>straight from the pot<br/>(simulated in the demo)"]
    C["🕶 <b>Private receipts</b><br/>photos and notes encrypted<br/>with a passkey-derived key<br/>(Mera PRF), trip-only"]
    D["👨‍👩‍👧 <b>Beyond trips</b><br/>families and teams<br/>across countries,<br/>recurring pot"]
    A --> B --> C --> D

How it could make money (proposed): a small fee per settle-up, a share of the on/off-ramp spread through partners, and card interchange once the pot has a real card. The free path stays free: chipping in and paying friends back costs nothing beyond network fees, which we sponsor.

---

👥 Team

	Who	Built
	Kyy · @kikik27	Product, the mobile app, the GroupVault contract, the Envio indexer, live invite and invoice pages on the web
	Rakyavara Artomily · @artomily	The website: landing page with the 3D Teko scenes, the read-only demo dashboard, and the app's design system ported to the web
	MasDapa · @Dapoodap	The backend API: auth, gas drip, settle-up scheduler, profiles, receipts, push

Full history: contributors.

🙏 Acknowledgements and third-party code

Tekosue is built on open-source software and sponsor SDKs. We did not copy code from other projects: everything below is used as a dependency, each under its own license (see the package.json files).

Area	What we use
Sponsors	Monad testnet · Agora AUSD · Mera (@category-labs/mera) passkey accounts · Envio HyperIndex
Contract	OpenZeppelin Contracts (SafeERC20, IERC20Permit, ReentrancyGuard, ECDSA), Foundry + forge-std, Slither
Mobile	Expo + Expo Router, React Native, react-native-passkey, viem, TanStack Query, React Hook Form, zod, @noble/ciphers, curves, hashes, Reanimated, react-native-svg
Web	Next.js, , + , icons,

The Teko mascot, the app design and all product code are our own work from the hackathon period.

🤖 Use of AI tools

We used AI coding assistants throughout the hackathon, mainly Claude (via Claude Code), which appears as a co-author on many commits. It helped with planning documents, code, tests, docs and the brand assets. Every change was reviewed and merged by the team, and the product decisions are ours. The apps started from the official create-expo-app and create-next-app templates.

📄 License

MIT © 2026 sewunodetech