MosaecVerify
Check every
pack yourself.
Paste any pack account into the app and your browser runs five checks against the chain before you lend or borrow.
Pack check
NEAR Testnet
- Created by the Mosaec registryRecorded by v0.mosaec.testnet
- Zero access keys0 keys on the account
- Runs the published pack codeCode hash matches
- Predecessor authentication onEnabled at the verifier
- Unlocked at the verifierNo lock on this account
1Rules
Six rules,
each a line of code.
Fixed in the registry and the pack contract, the same for every lender and borrower.
Full-access keys0
Function-call keys0
Published pack code hash
4NVfLnVFYQxUPfsHRGpU6h8eKmp2AbQxNR2mYNx3BwzcPack #0Pack #1Pack #2
Ticket pays 537.50 USDC before T
1.00 ZEC to the Ticket holder
T passes unpaid
1.00 ZEC stays with the Title holder
T - 24hTT + 24h
Disruption recorded Borrower keeps redeeming
Zcash1 ZEC
Bitcoin0.01 BTC
Solana5 SOL
USD Coin1,000 USDC
Pause stopsNew packsNew offersNew fills
Always openRedeemWithdrawCancelExpireVerify
2Custody
Three accounts,
one path for your coins.
Your walletHolds the Ticket
PackZero keys
NEAR Intents verifierintents.mosaec.testnet
The coins sit in the pack's own balance inside the NEAR Intents verifier. Predecessor authentication means only the pack contract itself can move them.
3Review
What we have checked,
and what comes next.
Where security work stands today, and the step that comes before mainnet.
Internal ReviewContracts reviewed by the team
External AuditPlanned before mainnet
MIT SourceEvery contract readable
Security Contactsecurity@mosaec.finance
Safety, answered.
Which servers does a check trust?
A public NEAR RPC node and nothing else. The app reads the pack, the registry and the verifier directly from chain, and the Mosaec API plays no part.
Can the team upgrade a pack?
The pack contract is immutable. A new version would deploy under a new code hash, and every existing pack keeps running the code it started with.
What should I do when a check fails?
Treat the pack as unsafe and skip it. Each failed check names its reason, such as the key count or the code hash the account runs.
Which network is live?
NEAR testnet, with the registry v0.mosaec.testnet and test ZEC and USDC. The mainnet registry v0.mosaec.near is the next milestone.