Safe Treasuries
Use private notes that also require approval from your Safe.
Proof and Safe approval#
A Safe-controlled note requires a private spend proof and the Safe's approval. The note commitment includes its controller, and the Pool checks the controller when the spend executes. Account access alone cannot authorize it.
The Safe's own rules determine the required owners and threshold. Fuyu adds no minimum owner count or threshold of its own.
Fund and approve a spend#
Use the supported Safe funding flow. Check the Safe address, token, amount, receiving account and deployment. Prepare the proof on the holder's device, then collect the owner approvals for that request.
Owners should see the destinations, amounts, route and fees before signing. Show their quorum status separately from wallet connection and account recovery so users know which approval is still missing.
Check the current Safe rules#
Safe owners, thresholds and modules can change. Check the current authorization at execution and keep the original request while co-signers are reviewing it.
A signature collected before a policy change may no longer work. Check the operation's chain state and show which approvals are needed under the new policy.
Recover a controlled account#
Back up account keys and operation drafts in addition to owner signatures. A fresh browser should find the same controlled notes, then obtain whatever approval the Safe currently requires to spend them.
The repository reports software flows tested on disposable forks. Test the hardware, mobile browser and deployed Safe you intend to support as well.
- Show recovered note ownership and Safe approval as separate states.
- Test direct funding, co-signing and recovery on your deployment.
- Check a pending profile update before asking owners to approve a replacement.