[Specification] Unified Atomic Onboarding: Recursive Safes & OIDC Auth

The Unified Account Model

We eliminate the distinction between a “User” and an “Organization.” Both are represented as Safe Smart Accounts.

• For Individuals: The Safe is owned by a single passkey or a hardware-backed EOA.
• For Organizations: The Safe is a multisig (e.g., the “Accenture Safe” or “Miner-DAO Safe”).
• Recursive Power: An Organization Safe can be added as a signer to the DAO’s Master Safe. This allows for Hierarchical Handover, if a consulting firm is hired, you onboard their Safe, and they manage their own internal “Invisible Handover.”

The OIDC-Safe Handshake (< 500ms)

The OIDC bridge acts as the “Identity Router.” When the OIDC trigger hits, the system checks the Credential Type (Individual vs. Org):

• Identity Verification: The user/org authenticates via the OIDC provider (e.g., Azure AD for Orgs, Google/Apple for Individuals).
• Role Mapping: The OIDC token contains a claim: org_id or individual_id.
• The Transaction Batch:
  If Individual: The Zodiac module calls Safe.addOwnerWithThreshold(user_address, 1).
  If Organization: The module calls Safe.addOwnerWithThreshold(org_safe_address, current_threshold).
• Atomic Activation: Because this is a Based Rollup, the onboarding transaction is sequenced by the L1 miners instantly. Total latency remains < 500ms.

The Federated Dev Environment (Sovereign Context)

Whether it’s an Org or an Individual, the onboarding triggers the Federated Cloud (e.g. IDE) provisioning:

• Individuals get a private, sandboxed dev environment.
• Organizations get a “Team Workspace” where their internal Safes manage access.
• Security: Both environments are “Non-Local.” The code stays on the DSP Cluster, and the Lit Protocol grants decryption keys only to the verified Safe address.

Economic Forwarding & Hedging

To ensure these new members have the resources to build, we leverage the Miner-DAO agreement:

• The 5% Forward: Miners forward 5% of block rewards to the treasury, specifically earmarked for “Contributor Gas and Ops.”
• Prediction Market Buffer: To prevent a “market crash” from stalling new developers, Bob’s Bot hedges the ETC price on prediction markets. This ensures that the 5% forwarding maintains a stable purchasing power for the onboarding “Starter Kits.”

The Onboarding UX