Delegate to Simba Pool from your own wallet. Review current pool data, how rewards work, and the limits that matter before you choose.
Delegation is non-custodial: Simba Pool never receives your ADA, spending key, or recovery phrase. Rewards and block production are variable and are not guaranteed.
Pool data updated Loading…
Delegating points your stake at a pool. It does not move, lock, or lend your ADA, and you can spend it or switch pools at any time.
Search the ticker or paste the pool ID into any Cardano wallet that supports staking.
Your wallet shows the transaction fee and any stake-key registration deposit before you approve. Your balance stays spendable.
First rewards normally arrive after Cardano's activation window, then continue each epoch. Amounts vary and are not guaranteed.
Every Cardano pool pays rewards under the same protocol rules. What differs is who runs the pool, how it is run, and what your stake does for the network. Here is what yours does at SIMBA.
SIMBA is a single-pool operator: not an exchange, and not a pool farm spreading stake across a dozen tickers. Cardano stays decentralized only while many independent operators make blocks. Every delegation here keeps one more of them in the game.
The operator pledges 107.5K ADA of their own ADA to SIMBA, a large share of the pool's active stake. When the pool has a quiet epoch, the operator's ADA has the same quiet epoch as yours.
The block producer has no public face. It talks only to SIMBA's own relays, which run on two separate networks: one in a datacenter, one on the operator's own hardware. Losing one relay does not cut the pool off, and the block-signing keys rotate on schedule.
The fixed cost is 170 ADA, the lowest the protocol allows, and the margin is 1%. Both come off the pool's rewards before the rest is shared, so lower fees leave more for delegators.
Cardano governs itself on chain. SIMBA casts its stake pool vote on governance actions, and the operator is a registered DRep. Positions follow published principles you can read before you delegate.
The operator has been part of the Cardano community since before the Incentivized Testnet, and keeps building in public: a Cardano news desk, a Data Lab of on-chain history and plain-language guides, all free to read.
Don't take the pitch on faith. Check the receipts.
Review live stake, delegator, epoch, and block data with freshness shown.
See the data →See what the site can substantiate, what remains variable, and where data comes from.
Open transparency →Read the principles that guide pool operation and Cardano participation.
Review governance →A live map of the machines behind SIMBA and the jobs they do. Hover or tap any part to see what it does. Parts marked NEXT are on the roadmap and not running yet.
Hover or tap any part of the map to see what it does.
You sign one delegation certificate. Your ADA never moves; the ledger counts it toward SIMBA's stake, and you can spend or redelegate at any time.
Thousands of relays run by independent operators pass transactions and blocks to each other. SIMBA's relays are its doors into that network.
A public-facing node that pulls in transactions and blocks from peers, hands them to the block producer, and pushes SIMBA's blocks back out.
A second relay on the operator's own machine and a separate network, away from any cloud provider. It also keeps a full index of the chain. If one relay drops, the other keeps SIMBA connected.
The node that mints SIMBA's blocks when the protocol elects the pool for a slot. It has no public ports and talks only to SIMBA's own relays.
Blocks are signed with a key-evolving (KES) key that is renewed roughly every 90 days, so a leaked hot key goes stale quickly.
Automated alarms watch block production and KES key expiry, and alert the operator when something looks wrong.
Under Cardano's Voltaire rules, stake pools and DReps vote on governance actions. SIMBA has voted on chain as a pool, and the operator is a registered DRep. Read the principles.
Mithril lets stake pools co-sign certified snapshots of the chain, so new nodes and light wallets can sync in a fraction of the time and still verify what they download. SIMBA plans to join the signer set.
Midnight is a privacy-focused partner chain of Cardano, and Cardano stake pool operators can produce its blocks. SIMBA plans to run a Midnight node beside its Cardano block producer.
The feed is limited to Cardano and crypto, including Bitcoin. Research briefs disclose their model and important evidentiary limits.
As the theft investigation into the incident continues, Ledger said the implant was found in at least one affected user's device and that the incident appeared isolated to CryptoBilis, an authorized Southeast Asian reseller. Loss figures vary by source: Cointelegraph's headline says losses may exceed $86M, while CryptoSlate cites independent investigators' estimate of $93.2M in suspected thefts and says the implant exposes a gap in Ledger's authenticity check.
Read research brief →Cointelegraph says the foundation pushed back on claims that the patch was forced on network operators. The Block and CryptoSlate describe an overflow bug in the payment engine that could have minted about 18 trillion spendable XRP in one transaction; CryptoSlate says testing produced spendable XRP but the disclosure reports no evidence of public-network exploitation, and Cointelegraph's weekly digest says the researchers got a $250K bounty for a bug it headlines as "$94 billion."
Read research brief →CryptoSlate, citing SoSoValue, says bitcoin, ether, and solana funds lost nearly $1.25B in the week ended Oct. 9 ($681.1M, $542.07M, and $24.81M respectively), and Decrypt counts $386.3M of bitcoin ETF outflows over October's first seven trading days plus nine straight days of ether fund losses. CoinDesk's headline says bitcoin shrugged off the outflows to trade above $84,000 as oil fell.
Read research brief →Decrypt says the IMF analysis found that more than half of tokenized-stock trading happens outside US market hours, and that the roughly $2.3B market is more volatile and less liquid than traditional equities.
Read research brief →CryptoSlate cites a CoinGlass snapshot at 20:28 UTC on Oct. 11 with STRK at $0.1190, up 17.7% in 24 hours and 116.7% over seven days, after Starknet said on Oct. 8 it was actively considering leaving Ethereum for its own Layer 1. Decrypt says Zcash full-node developer Zakura expects hash-based signatures in January and is rolling out a privacy tool for rotating transparent addresses this week.
Read research brief →Cointelegraph says holders could face fines of up to 10,000 euros for failing to declare qualifying assets. The item reports lawmakers' backing; it does not report final adoption.
Read research brief →The Block says the AI data protocol will be upgraded to run natively on Sui and its independent chain will be retired; Cointelegraph reports the same migration and investment.
Read research brief →Cointelegraph says the Financial Stability Board urged G20 policymakers to support stronger safeguards against both.
Read research brief →The Block says the same wallet later lost $450,000 when 30 short positions were liquidated on Saturday night after staying open for more than three hours.
Read research brief →A merge into cardano-scaling/hydra at 14:26 UTC on 2026-10-09, "Followups on some recent work (#2899)", makes sure the node doesn't "observe something else as a deposit". It also tidies decommit-related code. It continues the run of Hydra deposit merges covered here on 2026-10-06 and 2026-10-07, but the commit doesn't say which earlier work it follows up, and doesn't call itself a security fix.
A Hydra node acts on what it observes on chain. If it read the wrong thing as a deposit, its view of a head's funds could drift from the chain. This change tightens that check. It lands days after the deposit-related security fixes covered here on 2026-10-06, so builders and operators using deposits or decommits should watch which release ships it.
Limit: The message doesn't say what "something else" is, or whether a misread deposit ever happened. It doesn't say what one could have caused, or which "recent work" this follows up. It names no advisory, severity or affected versions. It's a merge to master, not a release, so running heads are not shown to be patched. This is Hydra, not the Cardano base protocol.
Read research brief →"benchmark fixes (#2898)", merged at 12:23 UTC on 2026-10-09, makes Hydra's benchmark reports show average live heap during the load instead of peak memory since start. The slope row now needs 8 snapshots in its window instead of 4, and a row is coloured only when at least 3 of the 4 pairs measured it. It follows the PR-benchmark queue-size change covered here on 2026-10-07. This changes measurement, not Hydra's performance.
Anyone using Hydra's benchmark reports to size or compare deployments should know the memory metric changed. Peak-since-start and average live heap answer different questions: worst case versus typical load. So memory figures from before and after this change measure different things. The stricter slope and colouring rules should mean fewer trend signals drawn from thin data.
Limit: The commit doesn't say Hydra uses less memory or got faster. Reported memory may fall simply because the metric changed. No benchmark figures are given. It doesn't say what the "pairs" are, or whether peak memory is still reported anywhere. It's benchmark tooling, not a release or a protocol change.
Read research brief →Showing 11 of 11 stories. JavaScript enables topic filters and additional stories.
