ARPA Staking
ARPA Staking locks ARPA on Ethereum to support the network’s threshold-signature nodes. Community stakers receive rewards through auto-delegation and face a 14-day unlock. Node operators can lose rewards for malicious DKG behavior. DefiLlama reported about $0.20M of staking on 2026-08-16, only 0.20% of the size floor. The network and token risks merit full review at scale, but current capacity is too small for institutional use. We will not open an individual review until it clears the size floor.
- TVL sustained above the retired TVL threshold for 30 days
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-16.
The research file
Mechanism applicability
ARPA uses groups of nodes to produce BLS threshold signatures together. Community holders stake ARPA in the Ethereum staking contract, which auto-delegates their stake to nodes. A node operator must stake at least 500,000 ARPA and maintain network service. Rewards pay for community participation and node tasks. They do not represent a claim on external assets.
Control, loss and exit applicability
ARPA documentation says malicious node behavior during distributed-key generation can cost the node 50% of its monthly auto-delegation reward and harm community rewards. Community users may start an exit at any time, but they must wait 14 days before claiming unlocked tokens. Holders still bear the risk of token price, contract errors, node operation, reward policy, and the unlock queue, along with the resulting losses and limits on liquidity.
Current observation and perimeter
The DefiLlama API read on 2026-08-16 classified ARPA Staking as a Staking Pool and reported approximately $0.20M. The full amount was Ethereum staking TVL rather than ordinary protocol TVL. ARPA’s current network-parameter page identifies the Ethereum token and staking contracts, which match the registry perimeter.
Why the materiality dossier still applies
Current staking value is about 0.20% of the size floor. An advised-client position would dominate observed capacity and face its 14-day exit before a full review could justify use. The protocol is below the size floor, and we will not open an individual review until it clears it. Reopen only after staking TVL remains above the size floor for 30 days, then review contract roles and upgrades, node concentration and uptime, slashing and reward history, token liquidity, and proposed-size unlock execution.
Research status
This is a capacity-unproven record for ARPA Staking, not a quality rejection or approval. Reported TVL says how big the venue is, not what the client owns, who can change the rules, or how a position exits at a proposed size. The individual review opens when the protocol clears the size floor.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- ARPA — current staking overview · primary · accessed 2026-08-16
Supports: community staking, node staking, 14-day unlock, 500,000 ARPA node minimum - ARPA Docs — native staking v0.1 · primary · accessed 2026-08-16
Supports: auto-delegation, slashing, community rewards, unlock period, contract addresses - ARPA Docs — node mechanism and rewards · primary · accessed 2026-08-16
Supports: BLS threshold signatures, node tasks, staking and slashing, reward sources - ARPA Docs — supported networks and contracts · primary · accessed 2026-08-16
Supports: Ethereum mainnet, ARPA token address, staking contract, network perimeter - DefiLlama — ARPA Staking survey record · secondary · accessed 2026-08-16
Supports: current staking TVL, Ethereum, Staking Pool category
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Ethereum | Approved | No freeze key | No sequencer, no upgrade key, no operator who can be compelled. Rule changes require social consensus. |