Before you say yes,
make it count
You agree on something. You both say yes, and it's sealed. Neither of you can undo it alone, and nobody else gets to read it unless a court asks.
Seeing each other, exclusively
7f3c9a2e41b8d05c6e7a19f4b2c8de35a0f61d97
Two people,
one agreement,
a few seconds.
Every step is explicit. Nothing becomes real until both sides have said yes, and saying no later is a first-class action, not a loophole.
Pick a scenario, set the terms
The creator chooses the agreement type, terms, duration and participants. An optional witness or arbiter can be attached from the start.
The other side says yes, on chain
Participants receive the invite and accept explicitly. Only then does the token become active. No acceptance, no agreement.
It ends by agreement, never by deleting
Once accepted, neither side can quietly undo it. An agreement ends when it expires, or when both sides consent to revoke it, and the record of what was agreed survives either way.
Four categories, the agreements people actually make.
Not enterprise contracts. The everyday promises that live in chat threads and get remembered differently by each side.
Personal & mutual consent
Casual relationships, friendly bets, reciprocal promises. Clear, mutual, timestamped consent that protects both sides from “that never happened”.
Pre-work & collaboration
Letters of intent, pre-work agreements, informal collaborations. Proof of what was agreed before any paperwork exists.
Loans & shared expenses
Microloans between friends, IOUs, splitting expenses. Small money, big friendships. This keeps both of them intact.
Temporary access & delegation
Lend your car, your house keys, your account access, with an explicit scope and a hard expiry date attached.
Why it holds up later.
Strong technical evidence by default, upgradeable to a digitally signed contract on the day it actually matters.
Tamper-proof
Each agreement is an ERC-721 token on Polygon. Terms are hashed on chain, so nobody can quietly edit history.
Sealed, not public
On chain there is only a fingerprint, never the content. Attachments are encrypted on the device with AES-GCM. The agreement is not browsable by anyone.
Opened only by court order
In a dispute, the sealed record can be disclosed to a court or an appointed arbiter. That is the only path in. There is no public explorer view of who agreed to what.
Legal upgrade path
An agreement can be elevated to an eIDAS-grade signed contract (AdES/QES) when both parties want real legal weight.
Built as a production monorepo, not a mockup.
Smart contract, backend, indexer and mobile client are already written, tested and building.
- Mobile
- Flutter (iOS 12+ / Android 8+), Riverpod state, non-custodial wallet with WalletConnect v2. Two Android APKs already built.
- Backend
- Node.js + Fastify + TypeScript, JWT with TOTP second factor,
EIP-2771relayer for gasless UX. - Blockchain
- Polygon, ERC-721
AgreementTokencontract with a 6-state lifecycle and consent-based revocation. - Indexing
- Dedicated sync microservice, 15-block confirmations, reorg-safe, Postgres + Prisma.
- Storage
- IPFS via Pinata, client-side encrypted attachments, GDPR-compliant EU infrastructure.
Say yes on the record.
Draft your first agreement in under a minute. Revoke it just as fast if you change your mind.
Start with a scenario