Support

WaaP can be used as a signer for account abstraction wallets. Used on its own it offers instant transactions, cross-chain UX, and no single point of failure in a smart contract.

Your keys are held in attested Trusted Execution Environments and are bound to your account. No WaaP operator can extract them or sign with them: every signature requires an authenticated request from you that the Policy Engine has authorized against your own spend limits, risk thresholds, and 2FA settings. If you would rather key material not sit with any single operator at all, Squid Mode distributes it across the Ika Network validator set.

WaaP protects against common attack vectors along with uncommon ones that even browser and hardware wallets do not protect against. WaaP and the tools developed by Holonym Foundation have been audited by numerous companies such as Cure53, Hexens, Least Authority, and Halborn.

For more details, please refer to Audit and Security Partners page.

Yes, WaaP can be white labeled for your dApp or website. Just reach out to our team.

Security: only the account owner can authorize a signature, and each one is authorized individually. Keys never reach your device, so malware has nothing to steal, and an approval is bound to one exact transaction and used once.

UX: no multi-chain restrictions, flexible spend limits, simplified social logins, and proactive transaction security. Without asking users to manage a seed phrase.

WaaP is Free wallet powered by a decentralized network secured by Ethereum proof of stake. And WaaP offers more flexibility than a WaaS when it comes to key recovery, and ZK Identity features. On top of that, WaaP users can mint a Proof of Personhood and recover their wallet by proving their identity in ZK.

Browsers grant same-origin privileges per domain. Keeping the wallet on a separate origin stops the rest of our websites from reading its data, so the separation is deliberate rather than an oversight.

The wallet is served from app.waap.human.tech. You may also reach it through waap.xyz or silksecure.net, which are ours. Anything else is not.

Yes. WaaP is free to integrate for dApp developers. There are no SaaS fees, no per-wallet charges, and no recurring costs. The SDK and CLI are both free.

WaaP supports all major EVM-compatible chains (Ethereum, Optimism, Base, Polygon, Arbitrum, Gnosis, and more) plus Sui and Solana. You can also add custom EVM chains. See the full list on our Supported Networks page.

WaaP is a non-custodial alternative to Privy’s embedded wallets. Key differences: WaaP wallets are portable across all dApps (not locked to one app), WaaP has no SaaS fees, and WaaP keys are held in attested TEEs and every signature is separately authorized by the Policy Engine against the user’s own limits, so no WaaP operator can move funds. Squid Mode goes further and distributes key material across the Ika validator set. See our detailed WaaP vs Privy comparison.

Yes. WaaP is fully EIP-1193 compliant, which means it works as a standard wallet provider with wagmi, ethers.js, and viem out of the box. See the Quick Start guide for integration examples.

Yes. WaaP CLI (@human.tech/waap-cli) gives AI agents programmatic wallet access without exposing private keys. Agents can send transactions, sign messages, and interact with smart contracts. All constrained by policy controls (daily spend limits) and optional 2FA approval via Telegram. See WaaP for Agents for details.

Inside a Trusted Execution Environment. WaaP accounts use standard mode: t1 (secp256k1) signs on EVM and Sui, t2 (ed25519) signs on Solana, and neither key ever leaves the enclave. Nothing on your device can sign, so malware on your machine has no key to steal.

What stops a compromised device from simply asking for a transaction is the authorization gate: the Policy Engine decides every request against your spend limits, risk thresholds, and 2FA settings, and the approval it issues is bound to one exact transaction and used once.

If you want key material distributed rather than enclave-held, Squid Mode splits it across the Ika validator set. Learn more in our Architecture docs.

Older accounts used two-party computation, with one keyshare on your device and one in the enclave. They convert automatically the next time you sign in: the enclave reconstructs the original key, verifies it derives your existing address, and imports it as t1. Your EVM and Sui addresses and balances are unchanged, and you gain a Solana address. Conversion happens once and needs nothing from you.

Create a project in the Gas Tank Console, pass its project ID to the SDK, and fund the tank. From then on eligible transactions are sponsored automatically. There is no SDK method to call at send time. The user signs the exact transaction they reviewed, the gas tank funds their wallet, and the unchanged transaction is broadcast. See Gas Tank.