Skip to main content

Supported Networks

The Stakely Staking API covers two tiers of availability:

  • Available: live and self-serve. The endpoints are documented in this site, exposed in the OpenAPI schema, and reachable with any API key entitled to that integration.
  • On demand: not enabled by default. We can activate these networks and tokens for your integration; the staking type and the networks exposed are confirmed during scoping.

Network availability

Blockchain / TokenStatusStaking TypeNetworks
Cosmos Hub✅ AvailableNativeMainnet, Testnet
Celestia✅ AvailableNativeMainnet, Testnet
Ethereum✅ AvailableStakeWiseMainnet, Hoodi
Pharos✅ AvailableNativeMainnet
Monad✅ AvailableNativeMainnet
Monad✅ AvailableMagma (liquid staking)Mainnet
Solana✅ AvailableNativeMainnet, Devnet
Solana✅ AvailableJPool (liquid staking)Mainnet, Devnet
Sui✅ AvailableNativeMainnet, Testnet
Stablecoins🟡 On demandVault strategy-
Polkadot🟡 On demand--
Kusama🟡 On demand--
NEAR🟡 On demand--
Aptos🟡 On demand--
Data🟡 On demand--
Aztec🟡 On demand--
Avalanche🟡 On demand--
Starknet🟡 On demand--
Sonic🟡 On demand--
Algorand🟡 On demand--
Bitcoin🟡 On demandVault strategy-
Polygon🟡 On demand--
BNB Chain🟡 On demand--
Hyperliquid🟡 On demand--
TON🟡 On demand--
Tron🟡 On demand--
info

On-demand networks and tokens have no endpoints in the public OpenAPI schema and are not returned by any /networks endpoint until they are enabled for your API key. If you are interested in one of them, or in a network that is not listed at all, contact us. New networks can be evaluated and integrated quickly based on technical feasibility and demand.

The API also exposes endpoints to programmatically discover available networks per blockchain (each blockchain's /networks endpoint). These return the exact X-NETWORK values enabled for your API key and are covered in detail in later sections of the documentation.

Network staking parameters

Staking mechanics differ per network. The table below summarizes the practical differences that affect an integration: minimum stake, how long a new stake takes to activate, how long funds are locked when unstaking, and how rewards are realized. Use it to plan UX and treasury flows; the per-network sections cover each in detail. It only covers the networks marked Available above; parameters for on-demand networks are shared during scoping.

Blockchain / productStaking typeAPI minimumStake activationUnbonding / lock when exitingRewards model
Cosmos HubNativeNoneImmediate (next block)~21-day unbondingManual claim (claim-rewards)
CelestiaNative (Cosmos family)NoneImmediate (next block)~21-day unbondingManual claim (claim-rewards)
Ethereum StakeWiseVault (pooled)NoneImmediate on depositExit queue, fulfilled through Ethereum partial withdrawals: variable, typically 1 to 7 daysAccrues in the Vault position; realized on withdraw
PharosNativeNone~1 epoch (max ~4h)84-epoch withdraw windowManual claim or compound
Monad (native)NativeNoneNext epoch (~5h 30m); up to 2 epochs (~11h) depending on when in the epoch you stakeNext epoch (~5h 30m); up to 2 epochs (~11h), same as activationManual claim or compound
Monad (Magma)Liquid100 MONImmediate (liquid)1–2 epochs (~5h 30m to ~11h), same as Monad nativeAccrues in gMON (liquid)
Solana (native)Native1 SOLWarm-up ~1 epoch (up to ~2 days)Deactivation cooldown (~2–3 days typical, not a hard cap; cluster limits can extend it across epochs)Auto-compounds into the stake account (no claim action)
Solana (JPool)Liquid0.003 SOLImmediate (liquid)Instant when paying the pool's withdrawal fee, or fee-free by waiting ~1 epoch (the Solana native cooldown)Accrues in JSOL (liquid)
SuiNative1 SUINext epoch (~24h)Instant: unstaking the StakedSui object returns principal plus rewards in the same transactionAccrues to the staked position
note
  • API minimum is the smallest amount the API accepts. None means no fixed API minimum, but on-chain gas/dust rules still apply; on Solana each stake account must hold the rent-exempt minimum.
  • Stake activation and unbonding / lock periods are defined by each protocol and can change over time. We keep these values updated as closely as possible; you can always confirm current on-chain parameters through the balance endpoints before signalling availability to users.