Network status & feature reality

This page exists so an integrator never builds against something that is not running. Check the network yourself before debugging your own code, and consult the feature table before designing a flow around a capability.

Check the network yourself

# 1. Is the RPC answering?
curl -s -X POST https://rpc.54-237-170-237.sslip.io \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'
# → {"jsonrpc":"2.0","id":1,"result":"0x..."}   the chain is producing

# 2. Is the indexer answering?
curl -s https://api.54-237-170-237.sslip.io/api/mobile/chain/status

# 3. Is the rollup sequencer up? (it can be down while the chain is fine)
curl -s https://api.54-237-170-237.sslip.io/api/rollup/status
# → {"ready":true,...}

GET on the RPC returns 405. That is correct, not an outage — the JSON-RPC endpoint only accepts POST. Likewise, hitting /api/... on the dashboard host returns the SPA’s HTML with status 200, which looks like success and is not. Always use the api. subdomain for REST.

Call twice a few seconds apart: if eth_blockNumber returns the same height both times, the chain is reachable but not advancing, which is a different failure from a dead endpoint and needs an operator, not a client-side fix.

Feature reality

The whitepaper describes the full protocol vision. The table below is what the running testnet does today. Build on the first column; treat the second as roadmap.

Live and verified

Feature	Notes
EVM execution	`revm`. Standard Ethereum tooling works
BLS12-381 aggregate BFT, ⌊2N/3⌋+1	Certified DAG (FireDAG / Bullshark-style)
EIP-1559 base fee + burn	Fee split 30% burn / 50% validator / 20% treasury
Verkle state root	Deviation: hashing is SHA3-512, not Poseidon; storage slots still Sparse Merkle
Block reward	Flat 1 YCE per block to the proposer — not the 10-year schedule; credited as native balance
Staking jars, 3–22% APR by lock	Values match the paper
Engagement economy	Live: the node mirrors each block’s engagement actions into `EngagementOracle`; YCR mints, ES computes, conversion floor 25 and creator royalty are wired
Light client (YLC/1) core	Header + signature + BLS quorum + Verkle proof; RPC `yc_lightCheckpoint`. Deviation: quorum by count, not 75% stake-weighted
Device checkpoint attestation	`DeviceRegistry` + `CheckpointAttestation` deployed; this is the viable mobile-participation path
Peer discovery (pull + push)	Consensus votes remain restricted to the validator set

Written but not switched on

Do not design a user-facing flow around these.

Feature	Why it does nothing today
Slashing	The penalty table exists in `ValidatorRegistry.sol`; the node never submits a proof
ES boost in validator selection	Leader rotation is round-robin; ES is pinned at 1.0 for selection
Parallel execution (Block-STM)	The node executes serially; the parallel path has no caller
Quadratic voting	Deployed, but without the ES amplifier and without a timelock
On-chain validator registry	Registry is empty — the chain runs on the genesis set, so registration/rotation are inert
YCE 2B hard cap	The cap lives on the ERC-20; block rewards are minted as native balance outside it, so it does not bind
USDY / stYCE	Deployment status is unconfirmed — two address sets disagree between `deployed.json` and the last on-chain measurement. Verify with `eth_getCode` before wiring either into a product surface

Not built

Sharding and the TPS figures that derive from it · pre-confirmations · hardware tiers and per-tier caps · sublinear √stake weighting (weight is linear) · Poseidon · per-shard fee market · forkless Wasm hot-swap · cross-chain bridge / YCMP · encrypted mempool / PBS · multi-region seeds. The VM is EVM by design decision — Move is not missing, it was dropped.

Contract addresses

Addresses live in contracts/script/deployed.json in the protocol repo and are listed on Contracts overview.

Never trust a contract address from memory or from a chat message. This chain has been wiped more than once; a full list of addresses went stale in the past while still looking plausible. Confirm with eth_getCode before shipping:

curl -s -X POST https://rpc.54-237-170-237.sslip.io -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["0x<addr>","latest"]}'

A result of "0x" means no contract there. After the most recent wipe the core addresses were preserved deliberately (deterministic CREATE from the same deployer at nonce 0, same order), which is why app builds kept working — that is a property to verify, not to assume.

Endpoints move

Every public URL embeds the server’s IP (54-237-170-237.sslip.io → 54.237.170.237). When the infrastructure moves, every URL changes. Read the base URLs from configuration your app can update without a new release.

Get Started

Concepts

Resources

Network status & feature reality

Check the network yourself

Feature reality

Live and verified

Written but not switched on

Not built

Contract addresses

Endpoints move

​Check the network yourself

​Feature reality

​Live and verified

​Written but not switched on

​Not built

​Contract addresses

​Endpoints move

Check the network yourself

Feature reality

Live and verified

Written but not switched on

Not built

Contract addresses

Endpoints move