Vision
Read why the check belongs in the wallet and not in the site, and who Baret is for.
Where the check actually happens.
A standard wallet goes straight from the site's request to your signature. Baret adds one step in between. These files explain that step, one topic each.
The specs came first. When the code and a spec disagree, the code wins and the spec gets fixed.
A standard wallet
- The site asks
- You press Sign
- The chain decides
Nothing checks the transaction in between.
With Baret
- The site asks
- Baret simulates and checks
- Your rules decide
- You sign, or you do not
Start here
Two files answer most questions.
Architecture
Follow one transaction from request to verdict: simulation, nine detectors, the policy engine and the API.
What you see
The screens, the pages and the words on them.
Wallet spec
Walk through every screen of the extension and the passkey wallet, including the empty and error states.
Frontend content
See what belongs on each page of this site, section by section.
Brand
Get the mark, the colors, the type and the voice, including the words Baret never uses.
Contracts and payments
The parts that hold money or move it.
Contracts
Read the PaymentGuard vault and the ReputationRegistry: functions, events, invariants and the tests they must pass.
x402 payments
Trace an HTTP 402 payment from the request to settlement, and see where Baret checks it.
Plan and decisions
Why the project looks the way it does, and what comes next.
Resources
See which sponsor tool does which job, from Alchemy RPC to Nansen, Mera, Cleanverse, Envio, Dynamic and Chainlink CRE.
Bounties and tracks
Check the hackathon track and the sponsor bounties Baret is built for, in priority order.
Roadmap
Follow the weekly plan and see what is done.
Decision log
Read each architecture and scope decision with its reason and the options it ruled out.
For developers
Calling Baret from your own code, with or without the SDK.
Guard SDK
Install, the smallest working call against the live API, and what fail-closed means for your code.
Agent kit
Give an agent a signer that cannot sign past Baret's verdict, plus the baret CLI.
API reference
Every route of the live API: what to send, what comes back, the errors and the limits.
Known limitations
- A simulation is a preflight. State can change between the check and the block that includes your transaction.
- Baret checks what goes through Baret. A key used somewhere else is not checked before it signs. The monitor can only tell you afterwards.
- The analysis runs on a server. It sees the unsigned transaction, your address and the site asking. It never sees a key.
- Reputation lists only know what has been reported. A drainer nobody has flagged yet is on no list.
- If the server is down, signing through Baret stops. That is on purpose.
- No audit yet. The code is open. Read it.
Prefer to watch it work?
The showcase has six fake sites, each with a trap built from a real transaction. Every sign request goes through the same analysis the wallet uses.