Org accounts
An org is an account controlled by a SET of principals with an M-of-N threshold. When an org owns a vault, publishing or revoking a grant under it takes M distinct signatures, not one key, and a high-value release can require M co-signatures. The approver set and threshold are owner-signed and anchored on Hedera, so the rule is on-chain and tamper-proof, never read live from an outside service. M-of-N raises the bar to authorize spend; it never lowers it.
How an org is formed
- Choose the member identities (wallets) and a threshold M.
- Each of M members signs the same registration body with their own wallet. The registration is self-authorizing: the founders vouch for the org, no outside authority.
- Submit the gathered signatures. The org is anchored as
org:<slug>and can then own vaults and grants.
Membership change is a re-registration signed by the current set. Reading an org's own data is 1-of-N: any one member can read it, no value moves.