Simple Logins
Streamlined access with social, phone or email.
The human.tech Wallet Protocol
Wallet access for apps and agents, with signing controlled by your account policy.
The human.tech Wallet Protocol gives apps and agents access to signing under a user’s authority. Standard accounts sign inside a secure enclave. WaaP Squid Mode adds co-signing with the Ika network. Your application requests the action without receiving the private key.
Read the docsChoose how your account signs.
| Account mode | Standard | WaaP Squid Mode |
|---|---|---|
| Signing | Inside the WaaP enclave | WaaP enclave and Ika network co-signing |
| Controls | Account policy and approval rules | Account policy and approval rules |
| Network costs | Transaction network fees | Transaction fees plus Sui and Ika signing fees |
Security
Inspect the controls before you integrate.
Standard accounts sign inside secure hardware. In WaaP Squid Mode, signing also requires the Ika network. Review the authorization flow and the audit scope for the components your integration uses.
Account policy controls
Review transaction requests
Approval before signing
Keep keys outside the client
Policy controls
Apply the account’s authorization rules before signing.
Embedded wallet access
Connect your application through the wallet SDK.
Quick Link Payments
Simple, shareable payment requests.
Account access
Sign in with your configured authentication method.
Network support
Integrate the supported EVM, Sui and Solana flows.
Protected Self Custody
Request signing without storing keys in your application.
EVM gas sponsorship
Sponsor EVM transaction gas through a developer-funded tank.
FAQQuestions,
Questions,
Answered by Humans
Standard accounts sign inside a secure enclave. WaaP Squid Mode uses co-signing with the enclave and Ika’s validator network. The agent or application requests a signature without receiving the private key.
The account’s authorization policy controls signing. Privileges allow specific actions within a defined scope and expiry. Review those rules before giving an agent access.
Approval depends on the account’s policy and any active Privilege. A pre-approved action can proceed within its scope; other requests follow the account’s authorization rules.
Standard uses enclave signing. WaaP Squid Mode requires the enclave and the Ika network to participate. Choose the mode deliberately when integrating your application.
Wallet integration is free. Transactions can incur network fees, and WaaP Squid Mode also requires the Sui and Ika network fees used for signing.
