SYSTEM DESIGN / RELEASE 0.1

Staking infrastructure,
before production.

Release 0.1 contains a network-fixture endpoint and a simple reward calculator for wallet and custody integration planning. It does not move funds, create staking transactions, or run validators.

GET/api/calculate200
{
  "symbol": "ETH",
  "amount": 100,
  "apr": 3.4,
  "yearly": 3.4,
  "rateSource": "fixed-demo-input"
}
WORKING RESPONSE / NO AUTH

Release contents

16
calculator fixture records
02
working API routes
00
private keys handled
v0.1
fixture version

Modules and delivery state

Working endpoints are marked as such. Proposed production components stay labeled until infrastructure and audits exist.

API-01

Delegation API

Prepare staking requests, return unsigned transaction data, and keep signing inside the client wallet or custody system.

Interface specification
ETH-02

Ethereum workflow

Model validator deposits, withdrawal credentials, reward reporting, and exit requests for solo or distributed validators.

Workflow prototype
EMB-03

Embedded staking

A white-label flow for wallets and custodians: choose a network, review terms, sign, then track the resulting position.

Frontend prototype
DAT-04

Network data

Normalize network names, reward assumptions, and calculator inputs behind one read-only endpoint.

Working demo endpoint
DVT-05

Validator topology

Define how signer separation, operator redundancy, and failover would be represented before production deployment.

Architecture proposal
OPS-06

Operations console

A proposed view for positions, validator state, rewards, and incident history across supported networks.

Product concept

Two public GET routes

Release 0.1 accepts no authentication and performs no writes. Responses use application/json.

GET/api/networks200

Returns fixture metadata and all 16 calculator records.

{
  "fixtureVersion": "2026-09-demo-v1",
  "rateDefinition": "gross nominal APR sample; not live market data",
  "networks": [{ "symbol": "ETH", "apr": 3.4, ... }]
}
GET/api/calculate?symbol=ETH&amount=100200

symbol must match a registry asset. amount must be a positive number denominated in that asset.

{
  "symbol": "ETH", "amount": 100, "apr": 3.4,
  "yearly": 3.4000000000000004,
  "monthly": 0.2833333333333334,
  "daily": 0.009315068493150686
}

Network registry

These records feed the calculator. Rates are versioned fixtures, not live quotes or forecasts.

AssetNetwork / contextSample APRFixture
ETHEthereumBeacon Chain3.4%2026-09-demo-v1
SOLSolanaNative delegation6.8%2026-09-demo-v1
DOTPolkadotNomination pools12.1%2026-09-demo-v1
ATOMCosmos HubNative delegation14.6%2026-09-demo-v1
TIACelestiaNative delegation10.2%2026-09-demo-v1
POLPolygon PoSEthereum staking contracts4.9%2026-09-demo-v1
APTAptosDelegated staking6.1%2026-09-demo-v1
SUISuiDelegated staking4.4%2026-09-demo-v1
NEARNEARValidator pools8.3%2026-09-demo-v1
ADACardanoStake pools3.1%2026-09-demo-v1
XTZTezosDelegation5.7%2026-09-demo-v1
HYPEHyperliquid L1Native staking2.4%2026-09-demo-v1
SEISeiNative delegation5.2%2026-09-demo-v1
MONMonad mainnetFixture only7.9%2026-09-demo-v1
TRXTRONResource delegation4.1%2026-09-demo-v1
CCCanton NetworkFixture only3.8%2026-09-demo-v1

Reward calculation

Gross nominal APR over a 365-day year. Yearly = principal × APR; monthly = yearly ÷ 12; daily = yearly ÷ 365. UI values round to two decimals. Fees, commission, compounding, activation, unbonding, slashing, inflation changes, and token prices are excluded.

100 ETH
— ETH
APR—
Monthly rewards—
Daily rewards—

Demo only. Fixed sample APR, simple annual calculation, no fee or compounding.

Proposed signing boundary

Only the directory and calculator exist in this release. The flow below records the intended production boundary; it is not an audit claim.

01Client apprequests transaction data
→
02Proposed APIreturns unsigned payload + chain ID
→
03Wallet / custodianchecks policy, simulates, signs
→
04Client broadcastersubmits through chosen RPC
→
05Networkvalidates transaction
01

Signing boundary

The proposed API returns unsigned data. Wallets and custody systems retain signing authority.

02

Operator separation

Validator, signer, and monitoring roles remain separate in the proposed production topology.

03

Evidence before claims

Audit reports, uptime history, and incident records must be published before production use.

04

Current limitation

This deployment is a product prototype. It does not provision validators or submit transactions.

Release notes

The network directory, reward calculator, and two read-only API routes work. Wallet signing, validator provisioning, custody integrations, and production monitoring are outside this release.

Inspect the working response

The public endpoint returns the same 16 network records used by this page. No account, wallet connection, or API key is required.

GET /api/networks