01 · Ryntra Guard for Arc
Policy-controlled USDC payouts with verifiable outcomes.
Prepare an exact payout, apply your own rules, authorize it in your own wallet, and prove what Arc Public Testnet actually settled.
- ARC PUBLIC TESTNET
- NON-CUSTODIAL
- HUMAN-AUTHORIZED
- REAL TX + EXPLORER
- RECONCILED RECEIPT
- INDEPENDENT PROJECT
- TESTNET ONLY
- NOT AUDITED
- NOT FINANCIAL ADVICE
02 · The problem
Moving USDC is easy. Proving the decision is not.
A treasury team can send a stablecoin payment in seconds. Afterwards they still have to answer why it was allowed, who approved it, what exactly was signed, and whether the result matched the plan.
- A payment form
- A wallet prompt
- A policy spreadsheet
- A block explorer tab
- An approval in chat
- Reconciliation by hand
- One exact intent
- One versioned policy
- One human authorization
- One observed outcome
- One verifiable receipt
The missing layer is not another payment rail. It is decision accountability around the rail that already works.
03 · Customer and use case
Start with one real workflow: paying a supplier in USDC.
The first customer is a fintech operator, a treasury team, or an Arc builder embedding payouts — anyone who moves USDC on someone else’s behalf and has to answer for it.
- Payee
- An approved supplier
- Amount
- 2,500.00 USDC
- Purpose
- Invoice
- Policy
- A versioned treasury payout policy
- Approvals
- One or two, by threshold
- Signer
- The operator's own wallet
- Settlement
- Arc Public Testnet
- Outcome
- A reconciled receipt
- Understandable in seconds, by someone who is not an engineer.
- Uses USDC directly, with a real production path.
- Demonstrates policy and human control in the same motion.
- Expands into batch, recurring, cross-chain and agent-submitted payouts.
04 · The product
One spine, seven recorded stages.
Every movement runs the same lifecycle, and every stage leaves an artifact that can be checked later. The violet stage is the one act software never performs.
- 01Intent
One normalized, versioned action: chain, asset, decimal amount, recipient, route, policy reference and expiry.
- 02Evidence Status
Every input carries provider, source reference, observation time, validity, coverage and a response digest. Missing, stale or unsupported coverage stays visible.
- 03Policy Decision
A deterministic engine evaluates a versioned policy. No model returns the outcome, and no model can authorize.
- 04Human Authorization
A distinct human act, recorded separately from the policy result and bound to the intent revision, evidence root and execution fingerprint.
- 05Arc Testnet Settlement
The user's own wallet signs and broadcasts. Ryntra holds no key, no seed phrase and no withdrawal authority.
- 06Expected vs Actual
Onchain effects are compared with the effects that were authorized, and a drift is reported rather than smoothed over.
- 07Execution Receipt
A structured, hash-checkable record linking intent, evidence, decision, authorization, settlement and reconciliation.
Five axes that stay independent: evidence, policy, authorization, execution and reconciliation. Allowed is not authorized, and confirmed is not reconciled — the separation is the product.
05 · The flagship workflow
Treasury Payout: who, to whom, how much, under which rule, approved by whom.
Three zones, left to right: the exact draft, the policy verdict on it, and the lifecycle it has to walk. Nothing advances until the stage before it is satisfied.
The exact intent before anything is evaluated: wallet, beneficiary, amount to the asset’s own precision, purpose code, and an optional external reference hash. No invoice, payroll memo or identity document is stored.
The policy decision and the exact action it applies to, with the evidence behind it one disclosure deep. A verdict names what is missing rather than simply refusing.
Draft, review, authorization, external wallet, reconciliation, receipt. Each stage shows its own state, and the receipt is unavailable until the stage before it produced something to receipt.
06 · Why Arc and Circle
Arc makes settlement fast. Circle makes the flow composable.
USDC-native economics
The asset moved and the fee paid are the same unit, so a budget, a limit and a total debit are all denominated in the thing being controlled.
Deterministic settlement
Arc confirms quickly and predictably. That lets Ryntra spend its complexity on the decision rather than on waiting for finality.
App Kits compose the flow
Send, Swap, Bridge and Unified Balance are one typed interface over payment and liquidity movement — one integration surface instead of four.
An agentic path worth guarding
Agent Stack points at machine-initiated payments. That is precisely the world where owner policy, human authorization and receipts stop being optional.
We chose Arc because its primitives absorb the transport complexity, which lets Ryntra spend its own on decision quality, authorization and proof. Ryntra does not replace Arc, USDC, App Kit, Circle Wallets, CCTP, Gateway or Arcscan.
07 · Circle integration matrix
Every Circle capability at the maturity we can evidence.
A planned integration is never counted as present-tense use. Only the top five rows carry a verified tone, and they are the only five with evidence behind them.
| Capability | State | Evidence |
|---|---|---|
| Arc Public Testnet connection | Deployed | Live RPC reads and a deployed workspace anyone can open. |
| USDC transfer lifecycle | Testnet verified | One exact transfer, reconciled, with a finalized receipt. |
| Deterministic policy evaluation | Verified in product | Versioned rules, recorded evaluation, and tests over the engine. |
| External wallet boundary | Verified | The wallet owner signs. Ryntra holds no key and no seed phrase. |
| Circle App Kit — Swap | Testnet verified | One exact USDC→EURC swap, reconciled MATCHED and independently re-verified; in-product execution remains preview. |
| CCTP / Bridge | Next gate | No burn-attestation-mint lifecycle has been proven, so none is claimed. |
| Gateway / Unified Balance | Next gate | No deposit-and-spend proof exists yet. |
| Agent tools | Boundary only | Read, explain and draft. No agent authorizes, signs or executes. |
08 · What is proven, what is next
The line between what we have shown and what we have only built.
Every surface in the product carries one of these words, and the product will not let a capability wear a stronger one than its evidence supports.
- A deployed Arc Public Testnet workspace a reviewer can open and use.
- One exact direct-EOA ERC-20 USDC transfer of 1.000000 USDC, confirmed in block 55677295.
- One Circle App Kit swap — 3.000000 USDC → 2.651611 EURC — reconciled MATCHED and independently re-verified against Arc Testnet JSON-RPC.
- Expected-versus-actual reconciliation against the chain, not against the estimate.
- A receipt whose hash and integrity digest were recomputed independently of the application.
- A receipt verifier in the workspace that re-hashes a stored receipt and answers without a wallet.
- Treasury Payout — the workbench, policy verdict and approval threshold are real; no payout has been signed.
- Swap — the in-product execution path: estimate and preflight are real; one recorded App Kit operation is testnet verified, general availability is not.
- Batch payouts — CSV validation and the queue are real; a batch has not been run end to end.
- CCTP / Bridge — a proven burn, attestation and destination mint, plus a recovery case.
- Gateway / Unified Balance — a proven deposit and a proven spend.
- Agent tools — an operating console with identity, budget, intent history and revocation.
- Reliability — idempotency under load, replay and TOCTOU protection, RPC failure handling and monitoring.
09 · Arc Hub vision
Ryntra Guard starts with Treasury Payout. The same kernel becomes the Arc Hub.
One Evidence Kernel — intent, evidence, policy, authorization, reconciliation, receipt — under every operation. The zones below are the product architecture, and each capability enters the workspace only when it has its own proof.
- Network
- Assets
- Providers
- Flows
- Send
- Request
- Swap
- Bridge
- Unified Balance
- Treasury Payout
- Batch
- Scheduled
- Checkout
- Policies
- Recipients
- Approvers
- Agents
- Activity
- Receipts
- Verifier
- Journal
- Developers
- Data API
- MCP
- Webhooks
Those six numbers are counted from the registry the workspace itself renders from, across 43 registered capabilities. A capability that is not proven appears on the in-product Arc Hub map with the exact gate it waits on — never in the navigation as a finished feature.
10 · The evidence receipt
The receipt binds the whole decision, not only the transaction.
A block explorer proves a transfer happened. It cannot say which rule allowed it, who authorized it, or whether the result matched what was approved. This is one real recorded run, and every field below is re-derivable from the chain and the stored receipt.
- Operation
- Direct-EOA ERC-20 USDC transfer · 1.000000 USDC · Arc Public Testnet
- Policy
- ALLOWED_BY_POLICY under a versioned, immutable policy
- Authorization
- APPROVED — a human act, recorded apart from the signature
- Expected vs actual
- Fee quoted 0.001548973026 USDC, settled 0.001530838950 USDC — read back from the chain, not copied from the estimate.
- Reconciliation
- MATCHED · ONCHAIN_VERIFIED
- Integrity
- SHA-256 0xed006ede12c4e99648a089e401a661d4e7d8c6c9afe5a0ea9892228327ebd1fe
What was observed and what was decided are separate records, so missing or stale evidence cannot be laundered into an approval.
A rule permitting an action is not a person choosing to take it. The human act is recorded on its own.
A transaction succeeding is not the same as it doing what was approved. Only a match finalizes the receipt.
11 · Production path
From one verified operation to a reusable Arc control layer.
Complete the payout proof
- One user-signed Arc Testnet payout from an approved treasury wallet
- Independent reconciliation and a finalized payout receipt
- One negative recovery scenario, recorded
Pilot with Arc builders
- Three to five design partners moving USDC on Arc
- Recipient and approver workflows
- A partner API and receipt export
Extend the Circle primitives
- App Kit Send and Swap execution proof
- CCTP bridge lifecycle with recovery
- Gateway Unified Balance deposit and spend
What we will measure: payouts prepared, policy violations blocked, human approvals recorded, share of operations reconciled, time from request to receipt, partner integrations, and receipt verifications. No current value is invented here — the product has two recorded runs, and that is what it says.
12 · Founder and ask
Built in Ukraine by a two-developer team — already shipping.
Dmytro Plavutskyi — Founder & Product Architect
Product strategy, architecture, UX, protocol integrations, QA and release management — a two-developer engineering team, founder-led, with direct founder ownership of requirements, safety boundaries and deployment decisions.
Operated through a registered Ukrainian sole proprietor. A dedicated entity can be formed when a grant or investment agreement requires one.
- Accelerator support.
- Technical feedback on Arc and App Kit external-signing boundaries.
- Three to five Arc fintech or treasury design partners.
- Guidance toward Circle Developer Grant milestones.
Ryntra makes Arc value flows inspectable before authorization and traceable after settlement.
13 · Appendix
The recorded run, field by field.
Everything a reviewer needs to check the claim in section 10 without taking our word for any part of it.
- Intent and preflight
- int_58e9bf523de5438c9bc118b5ec1e7dd1 · preflight 0xb9d52657e4ed10933e63b57adf597f8d1f75d7055d87206570155e92a0ae799c
- Evidence root
- COMPLETE · 0x24aaa5bdc8db9129e87f3c4df03a2d0109b596375450d6d9a3883254d01e50fe
- Policy
- ALLOWED_BY_POLICY · demo-arc-usdc-transfer-policy v1 · digest 0x4134277b4a9b0660f8844de8aebb2b59f491d4e4138a52a9da6a7ebab257f8aa
- Authorization
- APPROVED · PARTNER_AUTHENTICATED, recorded separately from the wallet signature
- Execution fingerprint
- 0x9dc7552c2cc6271474c89bd1930aec1cdbda01549b7b0d707cabe31e28ee93ed
- Transaction
- 0x6476dc81a38f0cbe385eab5162f391d7954a992a443db7d268e07b2698b8d5f9 · block 55677295 · SUCCESS (0x1)
- Dual-event hazard
- Arc emitted this single movement as two Transfer events — 1000000000000000000 from the native precompile at 18 decimals, and 1000000 from the ERC-20 interface at 6. Reconciliation reads only the ERC-20 log, so the recorded amount is 1.000000 USDC rather than a 10^12 error.
- Receipt
- rcpt_b6b010ec3d5e4be19b4c26cdfce28e73 · 0xb1530b1273adf5efd0a41ab194546da2c17f58d1842384a281dac173478e64f2
- Integrity
- SHA-256 0xed006ede12c4e99648a089e401a661d4e7d8c6c9afe5a0ea9892228327ebd1fe — recomputed independently of the application
- Public Testnet prototype.
- No custody or private-key access by Ryntra.
- No autonomous signing by Ryntra.
- Human/user-controlled wallet authorization.
- Not a compliance certification.
- No guarantee of safety, execution success or profit.
- Evidence may be partial, stale, conflicting or unavailable.
- Mainnet/production support is not claimed.
The published repository is a bounded MIT extraction at b8af07a0f2e7, carrying the status STALE_PUBLIC_SNAPSHOT. It predates the current candidate and does not prove source or deployment parity.
Bounded public extraction; it predates the corrective candidate and does not prove source or deployment parity.