Celestia
Celestia: stake TIA or run a light node
Delegate Celestia’s native token, TIA, to support proof-of-stake consensus and potentially receive staking rewards after validator commission, or run a light node to check whether block data is available. Celestia is a modular blockchain network; application execution belongs to the layers that use its data availability service.
| Aspect | Delegate TIA | Run a light node |
|---|---|---|
| Network role | Back a validator’s participation in consensus. | Perform data availability sampling (DAS). |
| What you manage | A delegation through a wallet with staking support for the selected network. | A light-node client, its network configuration, and the resources to keep it running. |
| Costs to consider | Validator commission takes a percentage of staking rewards. | Node operation has infrastructure costs; service providers may impose separate fees or quotas. |
Delegating TIA
Keplr is one documented staking interface for Mainnet Beta, with a separate entry for Mocha testnet. The wallet account and staking interface must refer to the intended network. Delegation lets a token holder participate through an existing validator without operating that validator’s consensus node.
The validator’s commission rate uses staking rewards as its base, so it describes the validator’s share of those rewards. It does not describe a percentage deduction from the entire delegated balance or establish how much TIA a delegation will earn.
Bonded delegators also share slashing exposure. If a validator is slashed, the same percentage is removed from the funds delegated to that validator.
Reward accrual and reward withdrawal are separate. Celestia’s staking guidance describes the CIP-30 change: modifying a delegation, including redelegating or undelegating, no longer automatically claims its rewards. An explicit
MsgWithdrawDelegatorReward
is used to claim accrued rewards.
Running a light node
A local CLI setup uses
celestia-node
. Choose the software version and configuration for the intended network, check the light-node hardware requirements, and initialize its node store before starting it. Creating that store is a setup step; an operating light node receives headers and performs sampling. A documented browser alternative is Lumina through Celenium.
Sampling checks small, randomly selected data shares and their Merkle proofs. Its assurance depends on enough light nodes sampling for the block size so honest bridge nodes can reconstruct the data, and contact with at least one honest bridge node to receive fraud proofs of incorrect erasure coding. Successful sampling gives probabilistic confidence in availability; it does not validate a rollup’s transactions.
Validators produce and vote on consensus blocks. Light-node sampling is a separate role, so operating a light node does not by itself establish a TIA delegation or a staking reward claim.
Example: Unclaimed rewards after redelegation
In this hypothetical example, a Mainnet Beta account already has a delegation and accrued rewards. Its owner wants to claim the rewards while leaving the principal staked. Assume each alternative transaction succeeds, the account has sufficient spendable TIA for its fee, and all checks concern the same account and network.
- Explicit reward claim
-
The transaction contains only
MsgWithdrawDelegatorRewardfor the relevant delegation. Its pending rewards are claimed, and the delegation remains in place. - Redelegation without a claim
- The transaction only redelegates to another validator. Under CIP-30, the accrued rewards remain unclaimed. Repeated balance checks do not initiate a reward withdrawal.
Pending rewards in the second case are consistent with the transaction that executed. To withdraw them, submit an explicit reward claim. This interpretation applies only while no reward-claim message has executed; a transaction that also includes a claim must be assessed according to its executed messages.
Sampling and publishing data have different payment requirements
Light nodes can also post and retrieve blobs. Publishing blobs on Mainnet Beta costs TIA, while Mocha uses testnet tokens for testing. That publication fee is separate from the light node’s sampling role. RPC access, indexing, archival data, and hosting may also have provider fees or quotas; network transaction fees do not buy a provider subscription.
Updated ·