Common setups
Single-party approvals
If your business needs a single party to be able to unilaterally approve actions applied to or taken by wallets, the most common setup is to assign an authorization key or a user in your authentication system as the owner of the wallet.
Privy’s TEE infrastructure enforces that all requests to update a wallet (e.g. assign policies or delegate permissions to signers) or take actions with the wallet (e.g. sign messages or send transactions) must be signed by the authorization key or a time-bound key associated with your user. If no valid signature is provided on requests, Privy will not execute the action.
Privy’s TEE infrastructure enforces that all requests to update a wallet (e.g. assign policies or delegate permissions to signers) or take actions with the wallet (e.g. sign messages or send transactions) must be signed by the authorization key or a time-bound key associated with your user. If no valid signature is provided on requests, Privy will not execute the action.