📄️ Core Architecture
The core architecture of WaaP is based on the following core primitives:
📄️ Compared to WaaS
WaaP differs substantially from wallet-as-a service (WaaS), along dimensions such as trust model, security, use cases, and of course business model. You can think of it as a secure, web3-native alternative to WaaS tailored to many real-world use cases such as those involving secure storage of funds and usage of the funds across multiple applications.
📄️ Malware Resistance
The 2PC(-MPC) eliminates single points of failure for the private key. This means a compromised user, server, or network can at most suggest a transaction to be signed that the other party must approve for it to actually be signed...
📄️ Blind Signing Resistance
The security of WaaP is geared toward being like standard financial services one company with a large budget for security controls the entirety of user funds. However, with WaaP, security is outsourced without a company being able to access any funds!
📄️ Audits & Security Partners
WaaP and its underlying protocols (Human Network and Human ID) been audited. However, equally important, WaaP incorporates an advanced threat model and extensively employs security consultants in the design and implementation of features before audits are even done. Additionally, we have found and responsibly disclosed numerous bugs in other wallets to help secure their user funds. This had led to WaaP being a leader in wallet security.