Configure the default tenant wallet used to sign and anchor tenant attestations. Each organization keeps its own wallet identity and network. Phantom Direct is the default SaaS path so the tenant wallet signs and pays for the on-chain proof itself, while relay-based broadcasting stays in advanced options for private deployments and custom integrations.
Workspace Attestation Wallet
Each workspace can configure its own default attestation wallet. That wallet is the durable proof actor for PCAA-style evidence, replay anchoring, and future runtime interop, including 8004-style agent surfaces.
Workspace-owned proof identity
Connect Phantom, choose the network, and OSuite will fill the wallet identity for you. The default path keeps responsibility with the workspace wallet, which signs and sends the attestation itself even when different users or future agent runtimes initiate the action.
Recommendation: keep proof authority at the workspace layer. Individual users may connect or verify wallets in the browser, but the governance anchor should remain attached to the workspace boundary rather than a personal mailbox or personal identity.
`provider` stays fixed to `provn-solana`. In the default flow, OSuite prepares the digest and Phantom sends the transaction.
Phantom has not been detected yet. Open or unlock the extension, then retry detection.
Relay-based broadcasting is still available, but it lives in advanced options for private deployments, npm integrations, or customer-managed infrastructure.
Ready for Solscan?
Not yet. Finish the missing items below, then approve a new action to test the explorer link.
Phantom connectedNot connected
Default wallet savedMissing
Wallet modeMissing
Relay transportMissing
This prepares a test transaction, asks Phantom to sign and send it, and only shows Solscan after the chain can actually observe the transaction.
Tip: wallet verification and test-anchor actions stay disabled until Phantom is connected in this browser.
Enterprise-ready onchain controls
Agent wallet boundary
Keep wallet authority attached to the workspace instead of a personal operator account.
Ownership verification
Verify wallet ownership before allowing live buyer-facing attestation or anchoring.
Smart-account posture
Use expansion packs to move from single-wallet proof to Safe-style smart-account execution.
Phantom Direct makes the tenant wallet the on-chain actor. OSuite prepares the digest, but the connected Phantom wallet signs and pays for the transaction.
This is the recommended SaaS path. Most tenants should never need to touch relay settings.
Optional Web3 governance profile
Wallet profiles stay optional. Use them to describe how this workspace should treat governed chain actions without making wallet execution mandatory for the rest of OSuite.
These profiles inform spend posture, approval tiers, and demo-safe readiness language for optional Web3 actions.
