reinskit
v0.0.3
Published
Reins CLI: init, plan, apply, verify, inspect, revoke
Maintainers
Readme
Reins
Ledger-native spend controls for AI agents on the XRP Ledger.
Alpha. Testnet only. Not externally reviewed. Requires Node.js 22.12 or later.
Reins keeps an agent's spending on a separate allowance account. The agent receives limited transaction permissions; the owner keeps control of the vault and revocation.
Run the CLI
npx [email protected] --helpCreate fresh testnet accounts and review a plan:
npx [email protected] init --testnet-accounts
npx [email protected] plan reins.yamlInitialization uses the testnet faucet and writes reins.yaml plus .reins/testnet-wallets.json. The wallet file contains plaintext testnet seeds. Keep it local and out of the agent process.
After reviewing the plan, apply and verify it:
npx [email protected] apply reins.yaml --wallets .reins/testnet-wallets.json
npx [email protected] verify reins.yamlapply signs and submits testnet transactions. A failed apply can leave earlier steps completed; inspect the reported results before retrying.
Revoke as the owner:
npx [email protected] revoke reins.yaml --wallets .reins/testnet-wallets.jsonRead the final ledger verification. Submission alone does not confirm revocation.
Inspect exposure (0.0.3)
Version 0.0.3 adds a read-only inspector:
npx [email protected] inspect reins.yaml
npx [email protected] inspect reins.yaml --jsonThe command reads public ledger state at one validated snapshot. It does not load a wallet, ask for keys, sign or submit transactions. Use --endpoint <url> to select an RPC endpoint. The report separates observed ledger state from toolkit interpretation and explicitly marks incomplete exposure information. An incomplete report or observed delegated-permission mismatch exits with status 1; it must not be treated as a zero spending bound. Inspection is separate from verify, which checks whether live state matches the policy.
What is enforced
The agent can still send the reachable budget to an attacker. Reins limits exposure; it does not judge intent. Payee allowlists, per-payment caps, and rolling velocity require the planned independent co-signer and are not enforced in this release.
Apache-2.0. See LICENSE and NOTICE.
