Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ This repository implements the off-chain backend of AgentPay. Before changing co
Companion repos are wired in via the filesystem MCP server. The canonical roots are:

- `agent-pay-docs` — protocol architecture (`agentpay-architecture/`). Required reading for protocol-sensitive work. The `state-guardian-network/` subtree is **not** required background; read it only when the task is explicitly about SGN behavior or SGN-related profile wiring.
- `agent-pay-contracts` — Solidity contracts (CelerLedger, PayResolver, PayRegistry, RouterRegistry, Wallet, plus the chain-canonical wrapped-native / WETH-style contract that CelerLedger references for native-token funding flows). Optional background; read only when the task touches on-chain contract logic, event semantics, generated bindings under `chain/channel-eth-go/`, or profile/address wiring that depends on contract behavior.
- `agent-pay-contracts` — Solidity contracts (AgentPayLedger, PayResolver, PayRegistry, RouterRegistry, Wallet, plus the chain-canonical wrapped-native / WETH-style contract that AgentPayLedger references for native-token funding flows). Optional background; read only when the task touches on-chain contract logic, event semantics, generated bindings under `chain/channel-eth-go/`, or profile/address wiring that depends on contract behavior.
- `agent-pay-x402` — downstream integration that consumes this repo via WebAPI gRPC + Admin HTTP. Useful as an "external consumer" reference, not required reading.

`.mcp.json` is gitignored per-developer. Copy `.mcp.json.example` to `.mcp.json` and fill in absolute paths to your local sibling clones. If a path is unavailable when needed, ask the user before guessing on protocol-sensitive work.
Expand Down
2 changes: 1 addition & 1 deletion CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ The protocol-and-contract design lives in the companion `agent-pay-docs` repo (`
`.mcp.json` is gitignored per-developer — each contributor wires their own absolute paths. The current wiring exposes three filesystem MCP roots:

- **agent-pay-docs** — protocol architecture + SGN docs. Read `agentpay-architecture/`. Skip `state-guardian-network/` unless the task is explicitly about SGN behavior or SGN-related profile wiring.
- **agent-pay-contracts** — Solidity contracts (CelerLedger, PayResolver, PayRegistry, RouterRegistry, Wallet, plus the chain-canonical wrapped-native / WETH-style contract that CelerLedger references for native-token funding flows). Foundry project. Read only when the task touches on-chain contract logic, event semantics, or generated bindings under [chain/channel-eth-go/](chain/channel-eth-go/).
- **agent-pay-contracts** — Solidity contracts (AgentPayLedger, PayResolver, PayRegistry, RouterRegistry, Wallet, plus the chain-canonical wrapped-native / WETH-style contract that AgentPayLedger references for native-token funding flows). Foundry project. Read only when the task touches on-chain contract logic, event semantics, or generated bindings under [chain/channel-eth-go/](chain/channel-eth-go/).
- **agent-pay-x402** — downstream Go integration that layers x402 HTTP payment over AgentPay state channels. Useful as an "external consumer" reference: it talks to this repo's WebAPI gRPC (clients) and Admin HTTP (OSP) only, never `CelerStream` directly. Friction observed there is logged in that repo's `docs/agent-pay-feedback.md`.

If a path is unavailable in your MCP roots, ask the user before guessing — do not silently proceed on protocol-sensitive work.
Expand Down
2 changes: 1 addition & 1 deletion chain/channel-eth-go/channel/channel.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading
Loading