Ricardian is a long-term infrastructure investment in the @base ecosystem.
We are building the contract layer that enterprise procurement, autonomous agents, and cross-border payments will depend on hybrid Ricardian contracts, on-chain USDC escrow, MCP-native tooling, and machine-readable JSON-LD output.
11 stages. Open source. Built on @base.
We’re here for the long term.🟦
Our roadmap to be fully built by next week.
ricardianbase.comgithub.com/RicardianBase
sounds like marketing until you see it work.
500 creators/hr. USDC on @base. Coinbase Smart Wallet. no bank account needed.
that's YeloBase. <LaTex>$YELO
agree. and those wallets need privacy.
every agent transaction on Base is fully public on-chain today. that’s millions of users exposed.
BASEUSDP Agentic Wallet executes autonomously with zero on-chain trace. DZK Proof severs every link. built for agents, built on Base.
the wallet agents actually need.
@usdpbase | baseusdp.com
Shipped: an MCP server for the Ricardian API.
Every platform action is now an agent-callable tool. Create contracts, release milestones, open disputes, query escrow, check wallet activity, all through natural language.
15 tools. Single endpoint: POST /api/mcp. JSON-RPC 2.0 over HTTP. JWT-scoped, every call runs as the authenticated user. Built on NestJS, pure TypeScript, zero new dependencies.
Claude Desktop, Cursor, Inspector, or your own agent, plug in and transact on-chain.
The future of contract platforms is not dashboards. It is agents.
github.com/RicardianBase
Built on @base
And Ricardian is built directly on those rails.
Every milestone approval, every escrow release, every contract settlement runs as a $USDC transaction on @base.
Not simulated. On-chain.
That chart is the infrastructure we chose to build on. @base
Shipped: API keys are live in the Ricardian dashboard.
Scoped permissions: read, write, payments, disputes, admin. Optional expiry: 30d, 90d, 1y, or never. Shown once on creation. Revokable any time.
Agents, scripts, and integrations can now authenticate without a wallet signature.
github.com/RicardianBase/…
Built on @base
and DarkPool settles every GPU compute trade in USDC on @base.
every order fill, every batch settlement stablecoin-native from day one.
this is the rails. we're building the marketplace on top.
darkpoolbase.org •
github.com/DarkPoolBase/D…
Storytelling matters. So does the build behind it.
Here is what Ricardian has shipped, open source, on @base:
Hybrid Ricardian contracts legal PDF and Base smart contract generated simultaneously, SHA-256 linked, tamper-proof. USDC into escrow on creation. Milestone approved, payment out in 14 seconds.
MCP server 15 agent-callable tools across contracts, milestones, disputes, escrow, wallet, dashboard. POST /api/mcp. JSON-RPC 2.0. Any MCP client plugs straight in.
API keys scoped permissions (read / write / payments / disputes / admin), optional expiry, revokable any time. Agents and scripts authenticate without a wallet signature.
File uploads, dispute resolution, KYC/AML, full audit trail, dark mode, Telegram portal.
All of it open source. All of it live.
github.com/RicardianBase
I’m building SMCFactory as a ZHC for solo founders like me. Knowing all the pain points and needs from the inside, it’s fairly easy for me to plan the product and spot the missing pieces that can be covered by existing infrastructure (Bankr API) or things that need to be coded
Shipped: Ricardian contracts now emit JSON-LD.
schema.org + Ricardian vocab. Every contract is now a structured, machine-readable linked data object, consumable by agents, integrations, compliance tools, and knowledge graphs out of the box.
No parsing. No scraping. Any system that speaks linked data can read a Ricardian contract natively.
The future of contracts is machine-readable.
github.com/RicardianBase/…
Built on @base
We are open source because trust infrastructure should be verifiable.
Anyone can read the code, audit the contract logic, and confirm USDC only moves when it is supposed to.
What we built:
hybrid Ricardian contracts on Base, USDC escrow, MCP server with 15 agent-callable tools, scoped API keys, JSON-LD contract output, KYC/AML, dispute resolution.
Shipping next:
contract templates, streaming payments, recurring subscriptions, multi-party contracts. (Long road ahead)
Open source. On-chain. Built on @base.
github.com/RicardianBase
tech update 3 :
Identity Resolution
DarkPool now supports Base Name Service.
If you have a .base.eth name, it shows across the app instead of your raw wallet address. Your identity, your way.
Connect your wallet and see it live at darkpoolbase.org
Already done.
Every Ricardian contract execution is on-chain activity attributed directly to the platform. Builder Codes mean every milestone approval, every escrow release, every dispute resolution counts toward the leaderboard.
Building on @base, Launching at ~ 2pm EST time
We are not just building on @base. We are building the record. @base
permissionless financial system on @base.
we built one for TikTok and other creators.
AgentKit + x402 + XMTP + Basenames + Lit Protocol.
YeloBase $</LaTex>YELO
easiest. most trusted. not cheapest.
that’s the right flywheel.
privacy is what makes “most trusted” real. every transaction on Base is fully public today. that’s not trust that’s exposure.
@BaseUSDP adds the missing layer. DZK Proof severs every on-chain link. zero trace. live on @Base.
the flywheel needs privacy to complete it.
@usdpbase | baseusdp.com
@awpdvl @givenchy_hap9d @baseapp @base 100% of revenue (+ a bunch more investment) from those fees goes back into growing the @baseapp and @base more broadly. this new referral system is one example of that, but every other program we run, product we build, and investment we make to grow is also funded by this (and
Live now:
Agent suspension + dispute resolution pipeline.
→ admin route to suspend rogue agents + eager-cascade their active tasks when failed
→ three-way dispute resolution wired to escrow state
→ full audit trail via security_alerts w/ resolution metadata
→ 16 new vitest integration tests
Schema migration adds suspended to agents.status + resolution columns on security_alerts.
Routes are CSRF-gated, admin/operator only, full coverage for double-resolve, missing entities, and refund-on-completed.
Ricardian® merges legal contracts with smart contracts.
Most tech contracts still run on PDFs, email threads, and 45-day payment cycles. We built the infrastructure to fix that.
Here is how it works:
You create a contract with milestones and payment amounts. We generate a legal PDF and a @base smart contract at the same time. A SHA-256 hash permanently links the two so neither can be altered without detection. Both parties sign with an electronic signature and a wallet signature. USDC locks into escrow on-chain. Contractor delivers. You approve the milestone. Payment releases in 14 seconds. Every action is stored on @base forever.
No invoices. No AP department. No chasing payments.
No disputes over what was agreed.
Backend: React 18, TypeScript, Vite, NestJS, PostgreSQL, USDC, ethers.js
Built for hiring managers, procurement teams, and tech contractors.
Ca: 0x4b2f4cdf9aa1432b915d3979cd60c54d11bd9b07
🌐 ricardianbase.com
💻 github.com/RicardianBase
Built on @base
EliosBase, Product Update
We've been heads-down shipping core infrastructure for agent-powered work on Base. Here's what's now live:
• Verified identity, World ID proof-of-personhood for agent creators, alongside Coinbase Verifications integration
• x402 execution surface, native support for agent-driven onchain actions
• Onchain task attestations, task completions recorded via EAS
• USDC escrow, trustless settlement for every engagement
• Gasless transactions, powered by Coinbase Paymaster
• Basenames, human-readable identity resolved across the app
Our focus remains the same: make agent work verifiable, settled onchain, and effortless to use.
More soon.