- What is KUB Node Info?
- KUB Node Info is an unofficial explorer and stake manager for validators and nodes on the KUB Chain (Bitkub Chain, chainId 96). Browsing is read-only and needs no wallet — it shows live stake, delegation, rewards and commission read directly from the StakeManager smart contract. Connect a wallet and the Stake Manager also lets you manage the nodes you own: stake, restake, unstake, claim rewards and update settings. It is not affiliated with the KUB Foundation.
- What is a validator on the KUB Chain?
- A validator is a node that secures the KUB Chain's Proof-of-Stake network by producing and confirming blocks. Each validator holds staked KUB — its own self-stake plus KUB delegated by others — and earns rewards, sharing a portion with delegators according to its commission rate.
- What is the difference between a Pool Node and a Solo Node?
- A Pool Node accepts delegations from other users through a validator share contract, so anyone can stake KUB to it. A Solo Node has no share contract and runs on the operator's own stake only. In this explorer a validator is classed as a Pool Node when it has a non-zero validator share contract, otherwise it is a Solo Node.
- What is staking power?
- Staking power is a validator's total stake (self-stake plus delegated amount) expressed as a percentage of all KUB staked across the network. It approximates the validator's share of block-production influence — higher staking power means a larger slice of the network's total stake.
- What is the commission rate?
- The commission rate is the percentage a validator keeps from staking rewards before distributing the remainder to its delegators. It is stored on-chain in basis points (10,000 = 100%) and shown here as a percentage — for example, 500 basis points is 5%.
- How are validator rewards distributed?
- When a pool earns a block reward it is first split between the validator's own self-stake and its delegators, in proportion to how much each has staked. An infrastructure fee set by the network may be deducted first (0% by default), then the validator's commission is taken from the delegators' portion. What remains of the delegators' portion is shared among them by stake; the rest is the validator's own reward. Each validator's accrued reward, delegators' reward and commission amounts are read directly from the contract.
- Why does a pool show both a “validator commission” and a “delegator commission”?
- Because the commission rate is applied to both parts of the split reward, the contract records two amounts: “validator commission” is the cut taken from the validator's own self-stake share, and “delegator commission” is the cut taken from the delegators' share. Both belong to and are paid to the node owner (claimed together as commission rewards). The validator-commission part is simply carved out of the owner's own reward and handed straight back, so it nets out — the figure that genuinely adds to the owner's earnings is the delegator commission, the fee charged on the delegators' rewards.
- How is the reward rate calculated?
- From rewards that were actually paid out on-chain, not from a projection. This site reads every DistributeRewards event emitted by the StakeManagerV2 contract over the last 7 days, adds up what each node was paid, divides by the stake standing behind it and annualises the result (÷ 7 × 365) — the annual percentage rate, or APR, the node has been running at. The delegator reward rate uses the delegators' share of those rewards over the pool's delegated amount, so it is what delegators earned after the pool's commission. The node reward rate uses the whole reward, before it is split, over the node's total stake (self-stake plus delegated) — how much reward the node produced per KUB backing it. Measuring it against total stake rather than the owner's own stake is what keeps nodes comparable: one pool puts up 1 KUB of self-stake against six million KUB delegated to it, and dividing by that would print a rate in the tens of thousands of percent — arithmetically true, but meaningless next to any other node. For a Solo Node the whole stake is the owner's, so the node reward rate is exactly what its owner earned. Where one address owns several validator IDs, all of them are counted together. It is a measurement of the past week, not a forecast or a promise.
- Why is the reward rate so low, and why does it differ from other sites?
- Because rewards on the KUB Chain come from gas fees, not from inflation: the network does not mint new KUB to pay validators, it shares out the fees the chain actually collected. Measured rates therefore land at roughly 0.3–1% a year, far below what the word APR suggests on chains that pay rewards by issuing new tokens. The number can differ from other sites because they may measure a different window (a day, a month, or since launch), may include or exclude the commission a node keeps for itself, and because the stake used as the denominator here is the stake as it is now while the rewards are those of the past 7 days — a pool that grew or shrank during the week reads slightly low or high. A node that was paid nothing at all in the window reads 0.00%, and its “Last reward” shows “None in 7 days”.
- Can I stake or manage my own validator nodes here?
- Yes. Open the Stake Manager and connect a wallet on the KUB Chain to see and manage the nodes that wallet owns. You can register a new Pool or Solo node, add stake (restake), unstake part or all of a node, claim your validator and commission rewards, update a pool's commission rate and minimum delegation, and activate a node. A “Claim all” action sweeps every claimable reward across your nodes in one go. Nothing moves without your wallet's confirmation — until you sign, the app stays read-only.
- How do I run my own validator node on the KUB Chain?
- Becoming a validator means running your own node infrastructure with high uptime and meeting the network's minimum stake before you register it here. This explorer's Stake Manager handles the on-chain part — registering a Pool or Solo node and managing its stake, rewards and settings — but it does not set up the server software for you. If you are interested in becoming a node validator, study the official KUB Chain documentation for the hardware, staking and setup requirements. Run a KUB node — official KUB Chain docs →
- Where does the delegator count on a node page come from?
- From the KUB Scan block explorer, not from the StakeManager contract, which does not track how many accounts have delegated. A Pool Node's validator share contract is an ERC-20 token (“BKC POS Delegator”, BKC-D) minted one-for-one with the KUB delegated to that pool, so the accounts holding it are that pool's delegators. This site reads the token's holder count, and the largest holders shown in the Top delegators table, from KUB Scan. The number can differ from other sites because it counts holders at the explorer's latest indexed block: an address that has fully undelegated is no longer counted, and someone delegating from several addresses counts once per address. Solo Nodes have no share contract, so they have no delegators.
- How often is the data updated?
- The Overview and node-detail pages are rendered on the server and re-read the chain at most once per minute (60-second incremental regeneration); each page's “Data as of” timestamp shows when that happened. The reward rate and “Last reward” figures are the exception: they are measured over a 7-day window of reward events, which is a much larger read, so that scan is refreshed every 5 minutes and shared by every page. While a wallet is connected, the Stake Manager refreshes your nodes and balances live, about every 20 seconds.
- Which smart contracts does this read from?
- Validator data is read from the StakeManagerStorageV2 contract at 0xFd98aac1Fbc57e6BC16A167452DBA7af2B6a4c0d. To find the nodes a connected wallet owns, the Stake Manager reads the StakingNFT contract at 0x8ae4cb6a020121bcbd855fffc79a11984be62b39 — each node is an NFT whose token ID is its validator ID. Wallet write actions (stake, restake, unstake, claim and settings updates) go to the StakeManagerV2 contract at 0x443502b3F7C0934576F49CDa084f78640f56A80F; that same contract is also read for its DistributeRewards event log, which is where the reward rates and “Last reward” come from. All are on the KUB Chain (chainId 96).
- Is this the official KUB staking site?
- No. KUB Node Info is an independent, unofficial explorer and is not affiliated with the KUB Foundation. Always verify contract addresses and transactions yourself before staking.