Pact contracts (V6)
Solidity contracts behind Pact, an iPhone and Mac app for keeping
commitments with friends. Friends agree on a goal, each puts a small stake into a shared pool,
and the pool is split by the result when the Pact ends.
There are two contract generations on Fuji:
- The gem generation (13 October 2026) is what the current app uses. The stake is gems,
an earn-only token with no monetary value, and collectible cat cards are soulbound tokens. See
Gem generation.
- The USDC generation (8 October 2026) takes test USDC and charges a 5% commission on net
winnings. It is deployed and verified but not used by the current app. The sections from
How a Pact works on-chain to
Previous deployments describe it.
Status: unaudited prototype, Avalanche Fuji testnet only. These contracts have not had
an independent security review. They are deployed only on Fuji and hold only test USDC and
zero-value gems. Do
not use them with real funds. The constructors accept Fuji (43113), Avalanche C-Chain
(43114) and a local test chain (31337); a mainnet deployment would need an explicit owner
decision and an independent audit first, and neither has happened.
The sources here are exactly what runs on Fuji. Some code comments are out of date. They
are left unchanged on purpose. See Source comments.
Gem generation (used by the current app)
Deployed on Fuji at block 59391986 (13 October 2026) by one deployer in seven consecutive
transactions. All seven contracts are source-verified on Routescan/Snowtrace.
The manifest, with runtime code hashes, the minter, invite signer and guardian addresses and
the timing, is in
deployments/avalanche-fuji-v6-gem-prototype.json.
How it differs from the USDC generation:
- Gems are restricted.
PactGemV6 is an ERC-20 with 6 decimals and an immutable minter.
The only movements are a mint by the minter, holder to vault (the vault's own
transferFrom), vault to holder, and a holder burning its own gems. approve works only for
the vault. The minter cannot burn. Gems cannot be bought, sold or sent to another person.
- Cat cards are soulbound.
PactCatCardsV6 is an ERC-1155 whose transfers and approvals
always revert; only the minter can mint.
- One registry, three domains.
PactGemRegistryV6 runs Walking (0), Working (1) and Proof
(2) pacts, each with its own settlement module and verifier. Every action names the domain it
expects. The settlement module is the same contract as in the USDC generation.
- No rollover and no commission (the vault's commission is the constant 0).
- Timing: 2-hour review window, 72-hour settlement window, 1-hour challenge window. After
the settlement window anyone can trigger the refund.
- Fuji only. Every gem contract refuses any chain but Fuji (43113) and a local test chain
(31337) in its constructor. Mainnet would need a new, audited generation.
- Solo pacts are not on chain, and a shared pact is registered on chain only when every
member has an account wallet. The app's database stays the source of truth.
The first gem-registry pact settled on 19 October 2026 in
0x6997f716…daae:
a two-person photo-proof pact where nobody sent proof, so each member got their 50 gems back.
How a Pact works on-chain
App users never see a wallet, gas or a chain. They sign in with a passkey, and their passkey
smart account sends sponsored transactions for them. Underneath:
This is the beginning of the README. Read the rest at the original. Read the full README ↗
