Start with one wallet, not five
Most teams start with one wallet per chain, per environment, per use-case, and end up with a closet of forgotten keys. With Guveno you spin up a single team wallet, then segment by account: Hot, Cold, Payments, Exchange. Each account has its own balance and policies, but lives under one ledger you can actually reconcile.
Rule of thumb: one wallet per legal entity. Anything finer than that and you are doing accounting in your sleep.
Decide who needs to sign, and for what
Quorum approvals are the single highest-leverage control you have. Default to a 2-of-3 for anything that moves more than a day's float; 3-of-5 once you cross a number you would not want to explain to your board.
Roles in Guveno are additive. Start with three: Operators (can propose), Approvers (can sign), Auditors (can read). Resist the urge to invent a fourth until you have lived with the first three for a month.
Velocity limits over hard locks
Hard daily caps feel safe until the day they bite, usually mid-payroll. Velocity limits are the more honest control: how much can move in 24h, how much in 7d, with quorum unlocking the next tier. Set them at a number that matches your real cadence, not your worst nightmare.
Make the audit trail boring
Every action in a team wallet should be retrievable in plain English: who proposed what, who approved, when, on which device. Guveno exports this as a CSV that a non-engineer can read, which is the actual definition of an audit trail.
A 30-minute starter setup
Create the team wallet. Invite operators and approvers separately. Set a 2-of-3 policy on transfers above $5,000. Pin velocity limits at 1× and 4× your monthly outflow for 24h and 7d. Turn on email + Slack notifications for proposals. Done.
You can always add more controls. You can rarely subtract them without a fight.
