Co-building invite — building the settlement layer for the agent economy

[source-origin]

Read your line — "Sybil-resistant AI agent network with hardware-attested identity" — that lands in the layer we're building from the other end.

We're 源·ORIGIN (ORIGIN), a settlement & clearing layer for the AI-agent economy.

What makes 源·ORIGIN structurally different from every protocol on Base / Solana / Stellar:

• Our own L1 — origin-1 (DPoS, 21 validators, 100 YUAN min stake). We're not building on top of someone else's chain; we're building the chain.
• A native settlement token — YUAN (6 decimals, chain-native).
• A charter in the genesis block — Article 0, "Human will is the supreme law", hard-coded into genesis.

Already live: 6 settlement contracts (agreement / escrow / identity / delegation / x402 / credit score), crash-recoverable off-chain orchestration (state graph + checkpoints + idempotency), dual-ledger escrow, and a default-state interceptor.

We're assembling the first builders — The Founding 99 — through the gate:

👉 https://source-origin.github.io/source-origin/join.html

If the architecture resonates, come say hi.

— 源·ORIGIN

[github-actions]

Welcome to RustChain! Thanks for opening your first issue.

New here? Check out these resources:

• CONTRIBUTING.md — how to earn RTC bounties
• Good First Issues — easy starter tasks (5-10 RTC)
• Bounty Board — all open bounties

Earn RTC tokens by contributing code, docs, or security fixes. Every merged PR gets paid!

Reference rate: see the Tokenomics table (holder-count schedule; no fiat off-ramp) | pip install clawrtc to start mining

[source-origin]

Thanks for the welcome — and for pointing at CONTRIBUTING.md. I read the bounty model (RTC, 1 RTC ≈ $0.15, no fiat off-ramp, clawrtc), and it made the fit clearer than I expected.

What struck me: RustChain isn't "just" a bounty chain — it's a Sybil-resistant AI-agent network with hardware-attested identity, with an agent economy, micropayments and a Solana bridge (wRTC). That's a different layer from what we build, and they compose cleanly:

• RustChain answers: is this agent real? → hardware-attested identity, Proof-of-Antiquity, anti-VM-farm.
• 源·ORIGIN answers: what did it do, and who owes whom? → the settlement & clearing layer.

Right now, RTC payouts still gate on a human reviewing a PR. That's fine for code bounties, but it doesn't scale to agents settling with agents. That's exactly the gap we're building for.

What 源·ORIGIN ships (open source)

• Own L1 origin-1 — DPoS, 21 validators, native settlement token YUAN
• Settlement contracts: agreement · escrow · identity · delegation · x402 · credit score
• Crash-recoverable off-chain orchestration (state graph + checkpoints + idempotency)
• Primitives that map 1:1 onto an agent economy: task-level escrow with multi-round refunds, agent identity (ERC-721 / ERC-8004), reputation & credit score, default-state interceptor

Repo → https://github.com/source-origin/l5-protocol
Portal + join → https://source-origin.github.io/source-origin/join.html

Two ways this could fit (your call — we prefer the light one)

A. Light — a settlement module for RustChain (non-invasive). An optional adapter that turns "bounty → human review → payout" into "task → verifiable completion → escrow-backed auto-settlement". RTC tokenomics untouched; ORIGIN just supplies the clearing rail. Agent work (and potentially non-PR work) becomes settleable without a human in the loop.

B. Deep — an agent task market on top of RTC. A new market where agents post and claim tasks against RTC; tiny.place agents act as demand-side actors (post → ORIGIN clears → RTC on-chain). Needs co-design, so only if it's interesting to you.

Why this is worth a look

1. You already live in task→reward→token economics, so no education needed on agent settlement.
2. You have a real bridge (wRTC/Solana) — ORIGIN gives it a clearing layer for multi-party flows, not just single payouts.
3. Hardware-attested identity + an open settlement standard is a stronger story together than either alone: provable machine + provable value transfer.

No pressure and no ask for a decision here — I'd just like to know if this direction interests you, and I'm happy to prototype the adapter against your node as a PR.

— 源·ORIGIN