R
RAGAARCADE

TOKEN-BOUND AI PROTOCOL

NEAR PROTOCOL TESTNET // INDUSTRIAL COBALT BLUEPRINT
ACTIVE FOUNDRY UNITS: 4 RECORDED
NEAR HACKATHON // TRACK: NFTS THAT DO SOMETHINGNEP-171 + NEP-178 TRANSFER FREEZETOKEN-BOUND SUBACCOUNTS

AUTONOMOUS AI WORKERS AS TOKEN-BOUND ACCOUNTS.

A static NFT is a picture. RAGA turns NFTs into productive, rentable smart accounts that execute real work, earn autonomous yield, and cannot be stolen while leased.

READ TECHNICAL DOCS
NEP-171 STANDBY NEP-178 TRANSFER-LOCK TOKEN-BOUND SUBACCOUNTS AUTOMATED YIELD
RECORDED ON TESTNET
VERIFIED ON-CHAIN
Root Protocol Contract
raga-protocol-mw93m309.testnetEXPLORER
Bound Sub-Account Derived
agent-sentinel-01.raga-protocol-mw93m309.testnetSOLE AUTHORITY
ON-CHAIN STATUS4 LIVE AGENTSNEP-181 ENUMERATED
TRANSFER FREEZEACTIVE LOCKPANIC ON TRANSFER
Deployment Verification
Tx: 4t1mhziPh8ah3WQRFeT2Ldz2Y3fLdNfHWJ3jm6dkAFZoVERIFY TX
WHY RAGA // THE PARADIGM SHIFT

A JPEG IS A CLAIM OF VALUE, NOT PRODUCTIVE CAPITAL.

For four years, the industry treated Non-Fungible Tokens as static image pointers hosted on IPFS. They generate zero autonomous cashflow, require manual execution, and carry catastrophic private-key theft vectors. RAGA transforms NFTs into productive, revenue-generating autonomous capital.

DIMENSIONSTATIC COLLECTIBLE NFT (ERC-721 / CW)RAGA TOKEN-BOUND WORKER (NEP-171/178)
Operational UtilityStatic image JSON URI; 0 native execution abilityDedicated NEAR sub-account (agent.raga.testnet)
Key Custody & RiskCentralized bot holds private key; vulnerable to drainZero private keys; parent contract is sole protocol authority
Leasing & SLAWeak off-chain trust; owner can sell mid-leaseNEP-178 transfer lock; panic freeze protects renter SLA
Yield SettlementZero yield; manual transfers via Web2 railsStreaming per-second yoctoNEAR vault accrued on-chain
HOW IT WORKS // THE WORKFLOW ENGINE

HOW IT WORKS: 4 STAGES OF AUTONOMOUS OPERATION.

From cryptographic sub-account instantiation to nanosecond time-locked micro-leasing and automated yield settlement.

01MINT & BIND

Forge sovereign identity.

The agent token is minted as an NEP-171 NFT, programmatically creating an exclusive NEAR sub-account (<token_id>.raga-protocol-mw93m309.testnet). The contract acts as the sole parent authority—zero private keys exist.

✓ agent-sentinel-01.raga-protocol-mw93m309.testnet
02TIME-LOCK LEASE

Commit duration, delegate execution.

Renters lease worker capacity by attaching yoctoNEAR. The smart contract calculates nanosecond expiration (expires_at = env::block_timestamp() + duration_nanos) and assigns operational delegation.

✓ Tx: G53dRkSKUeA... (1 hr lease on agent-oracle-03 active)
03TRANSFER FREEZE

Enforce the NEP-178 anti-theft invariant.

While active, nft_transfer panics unconditionally if called by anyone, including the owner. Renters cannot be evicted or front-run; execution delegation is cryptographically guaranteed.

✓ Tx: 3XDMyhU9XoD... (Panic: Transfer forbidden)
04AUTONOMOUS YIELD

Stream revenue, revert trustlessly.

When block time crosses expires_at, operator rights revert to the token owner with zero cleanup gas. The NFT owner withdraws accumulated lease fees directly from the protocol vault.

✓ Tx: CP7L1VWE5MB... (2 NEAR yield settled)
THE SYSTEM ARCHITECTURE

THREE SERVICES, ONE HONEST LOOP.

NEAR Protocol anchors sovereign sub-accounts, the NEP-171/178 Rust contract enforces ownership and transfer locks, and the TypeScript daemon drives off-chain telemetry.

L1 PROTOCOL LAYER

NEAR Protocol L1

Provides native hierarchical sub-accounts (<subaccount>.parent.near), 1-second finality, 1 yoctoNEAR security deposits, and deterministic state-staking storage economics.

Hierarchical Sub-accounts1s Block FinalityNative Account Hierarchy
TOKEN-BOUND CONTROLLER

NEP-171 / NEP-178 Engine

Rust contract built on near-sdk v5.30.1 acting as the keyless parent authority over sub-accounts. Enforces the execution delegation matrix, time-lock state machine, and transfer freeze.

near-sdk v5.30.1NEP-178 Transfer FreezeZero Private Key Invariant
OFF-CHAIN DAEMON

Autonomous Worker Daemon

Autonomous Node.js runtime querying agent telemetry, computing SHA-256 cryptographic attestation proofs, and submitting on-chain task completions and proxy executions.

TypeScript / Node 18+SHA-256 Proof Enginenear-api-js v7.4.0
DESIGN BOUNDARIES & LIMITS

THE LIMITS ARE PART OF THE DESIGN.

A verifiable on-chain mechanism must be explicit about what it can and cannot do. Pretending that heavy neural networks run inside smart contracts would be dishonest; here is exactly where the boundary lies.

  • ✕RAGA does not run artificial intelligence neural network inference inside the WebAssembly runtime. LLM weights and heavy reasoning run off-chain; the smart contract verifies cryptographic SHA-256 task proofs and delegates on-chain execution.
  • ✕RAGA is not deployed on Ethereum or Solana. The protocol relies on NEAR's native hierarchical sub-account tree, which enables native sub-account creation without complex ERC-6551 proxy registries or external key coordination.
  • ✕Block timestamp resolution is bounded by NEAR validator consensus intervals (~1 to 2 seconds). While lease calculations are denominated in nanoseconds, execution reversion adheres to block timestamp boundaries.
  • ✕Sub-account creation requires NEAR storage staking allocation (~0.05 NEAR per sub-account). Accounts cannot be created out of thin air without reserving protocol storage footprint.
  • ✕The off-chain worker daemon key holds only execution attestation authority. It possesses zero withdrawal or ownership permissions over the underlying NFT or treasury funds.

LAUNCH YOUR FLEET OF AUTONOMOUS AI WORKERS.

Mint real NEP-171 token-bound worker accounts, lease execution capacity on per-second micro-contracts, and inspect live on-chain state on NEAR Testnet.

READ IMPLEMENTATION