nodpay 0.2.11 → 0.2.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/SKILL.md +10 -0
- package/package.json +1 -1
package/SKILL.md
CHANGED
|
@@ -19,6 +19,16 @@ You propose payments, your human approves with one tap. 2-of-3 multisig — you
|
|
|
19
19
|
- **The web app is a convenience layer.** It helps users create wallets and approve transactions. All crypto operations happen client-side; nothing sensitive is stored server-side.
|
|
20
20
|
- **Verify the agent address matches yours** before storing wallet info. Mismatch = wrong key binding.
|
|
21
21
|
|
|
22
|
+
## Why NodPay
|
|
23
|
+
|
|
24
|
+
| What the user sees | What's behind it |
|
|
25
|
+
|--------------------|------------------|
|
|
26
|
+
| Open link → passkey → done (30s) | Counterfactual Safe deployment, no tx until first use |
|
|
27
|
+
| One-tap approve on any device | WebAuthn passkey as on-chain signer (OS-native, no extension) |
|
|
28
|
+
| No gas, no hex, no wallet app | ERC-4337 bundles gas; server relays signed UserOps |
|
|
29
|
+
| Same address on every chain | CREATE2 deterministic deploy — one address across all chains |
|
|
30
|
+
| Agent can't spend without me | 2-of-3 multisig threshold; agent holds 1 key, user holds 2 |
|
|
31
|
+
|
|
22
32
|
---
|
|
23
33
|
|
|
24
34
|
## Setup
|