New:Microsoft Teams Notifications Are Now Available in Socket.Learn more →
Get Started
w

warda_protocol

npm

2.54K

total weekly downloads

Packages

Current Co-maintainers

Former Co-maintainers

10 packages

@warda_protocol/borsh

Kaspa over borsh wRPC — the encoding the public resolvers actually serve. Reads the UTXO set, and submits covenant-carrying transactions through a build that has them, so neither side of a Warda payment needs a node.

@warda_protocol/cli

One short command for the whole life of a Warda grant: create it, see what it may spend, pay behind an HTTP 402, and read back every attempt. Adds no capability — the rules stay in @warda_protocol/core.

@warda_protocol/core

Reference implementation of the Warda agent grant protocol. Defines the exact semantics a Toccata covenant must enforce.

@warda_protocol/kaspa

Build, sign and verify Warda agent grants on Kaspa L1 covenants. Derives grant addresses and assembles covenant transactions with no Silverscript compiler and no Rust toolchain.

@warda_protocol/mcp

MCP server exposing a Warda grant's whole life to agent frameworks: authority, spends, delegation, settlement, revocation and recovery. Builds unsigned transactions and explains verdicts; never holds a key, never enforces — the covenant does that on-chain

@warda_protocol/registry

Service discovery for agents holding a Warda grant. A listing is a manifest the operator signs with the key they are paid at and publishes on their own domain; this reads it and says whether it stands.

@warda_protocol/router

Turning a price into an amount an agent can pay, and saying which parts of the answer consensus enforced and which parts somebody asserted.

@warda_protocol/vendor

Sell an API for Kaspa over HTTP 402. Quotes a price, then verifies the payment is in the UTXO set before serving — it never trusts the payment header.

@warda_protocol/verify

An HTTP endpoint that answers a counterparty's question about a Warda grant: are these terms real, where did the grant go, and what would the covenant refuse right now. Reads a node, decides nothing.

@warda_protocol/x402

Pay HTTP 402 (x402) invoices from a Warda grant on Kaspa, so an agent's spending limits are enforced by consensus rather than by the process holding the key.