nodpay 0.2.22 → 0.2.23

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.
Files changed (2) hide show
  1. package/SKILL.md +5 -5
  2. package/package.json +1 -1
package/SKILL.md CHANGED
@@ -27,11 +27,11 @@ You propose payments, your human approves with one tap. 2-of-3 multisig — you
27
27
 
28
28
  | Guarantee | How |
29
29
  |-----------|-----|
30
- | **2-of-3 multisig custody** | Agent (EOA), human (passkey), and recovery signer each hold one key. Any 2 can authorize — agent alone cannot move funds. Human + recovery signer can operate without agent. |
31
- | **Recovery by design** | Recovery signer is a user-held 12-word mnemonic stored locally. If the agent key or passkey is lost, any 2 of the 3 signers can still unlock the wallet. |
32
- | **Agent key isolated from context** | `keygen` writes directly to `~/.nodpay/.env` (chmod 600). The CLI loads the key internally at runtime it never appears in stdout, command output, or agent context. |
33
- | **Zero trust** | Every party verifies every other. Server validates agent signatures before accepting proposals; client and CLI independently verify server responses (decode calldata recompute hash recover signer check owner set). The chain is the sole source of truth. |
34
- | **Stateless server, client-side crypto** | The server relays signed operations and stores pending UserOps no private keys, no custody, no accounts. All signing happens locally (agent CLI or user passkey). Funds stay on-chain if the server goes offline. |
30
+ | **Threshold Security** | Elimination of single point of failure: authority keys are distributed between the agent, human, and a recovery signer (2-of-3 multisig). Ensures non-custodial controlthe agent cannot move funds unilaterally. |
31
+ | **Zero Trust** | End-to-end verification: no party is implicitly trusted. Server validates signatures; client and CLI independently verify server responses (decode calldata recompute hash recover signer check owner set). The blockchain serves as the canonical source of truth. |
32
+ | **Sovereign Recovery** | Key redundancy & continuity: uses a locally-stored 12-word mnemonic as recovery signer. Any two of the three signers can reconstruct authority to unlock the wallet, ensuring the user is never locked out by a single lost credential. |
33
+ | **Hardened Key Isolation** | `keygen` writes directly to `~/.nodpay/.env` (chmod 600). The CLI loads the key internally at runtime preventing accidental leakage via LLM outputs or stdout. |
34
+ | **Keyless & Non-Custodial Server** | The server acts purely as a relayer it stores no private keys and maintains no session state that could compromise assets. All signing happens locally. Funds stay on-chain if the server goes offline. |
35
35
 
36
36
  All wallet parameters (Safe address, passkey X/Y, recovery signer address) are public key material — safe to store, pass in URLs, and include in CLI flags.
37
37
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "nodpay",
3
- "version": "0.2.22",
3
+ "version": "0.2.23",
4
4
  "description": "NodPay CLI — propose on-chain payments from agent-human shared wallets",
5
5
  "type": "module",
6
6
  "bin": {