Mapae — 마패

The Mapae was not a token of privilege but a token of limits. The engraved horse count was not the authority granted — it was where that authority ended.

한국어판 →

Give an AI agent an on-chain limit, not a wallet. Mapae is agentic payment infrastructure on GIWA Chain that lets an agent pay by itself only within the limit delegated to it. The owner keeps the funds in a smart account and signs over a single permission engraved with amount, period, recipient, and expiry. What the agent's session key can do extends exactly to the point where that permission ends. You can start before the account even exists — sign first, and a sponsor deploys the account on your behalf; the user holds no ETH at any step.

Three claims

1. The limit is not a promise in code but a fact enforced by deployed contracts. The period cap, expiry, and pinned recipient are judged by on-chain caveat enforcers, not by backend checks. Swap out the entire backend and the limit stays.
2. The payer never touches gas. The payer smart account's ETH balance is 0 by design, and transactions are broadcast by the facilitator's relayer. Even a fully compromised relayer cannot steal funds, redirect the payment, or exceed the cap — 4. Security Considerations proves that boundary case by case.
3. A refusal is evidence too. An over-cap payment and an expired permission are refused before settlement, and the reason is recorded verbatim as the revert string the enforcer returned.

Evidence — GIWA Sepolia

Mined is a transaction that entered a block and opens in the explorer; Simulation is an eth_call against GIWA's current state. A refusal having no hash is not a gap but the design — the facilitator screens it out first by simulation, so no gas is spent on a transaction that would revert anyway.

The full evidence table and sequences are in 2. Payment Flows; the list of deployed and verified contracts is in Deployed Contracts (Korean).

Verify it yourself

The numbers in this document can be reproduced directly with the commands below.

bun run check                # 키·네트워크 없이 전 계층 회귀 + 문서 게이트
cd apps/delegation-lab
bun run test:negative        # 일회용 체인에 프레임워크를 직접 배포해 거절 케이스를 실행

test:negative needs no keys, no network, and no separate deployment artifacts — it runs from a clean clone with nothing but Bun and Foundry. The suite counts and prints the number of cases itself.

To wire it straight into an agent, follow the MCP Connection Guide (Korean). To create an account of your own, app.mapae.io is the shortest path — one signature and a sponsor deploys the account.

Reading order

Public documentation: docs.mapae.io · Repository: github.com/kooroot/Mapae · Original single-file source: tech-notes.md