Reading the chain

The loop in three sentences

Validators query the miners on their subnet and score the responses. Once per epoch each validator writes a weight vector to the chain, and Yuma Consensus combines those vectors — discounting validators whose scores are outliers — into one ranking. That ranking decides how the subnet’s share of newly minted TAO is split between its miners and validators.

What the explorer shows

Four record types, nested inside each other. Knowing which one answers your question is most of the skill.

• Blocks — one every twelve seconds or so. A block is the unit of finality: once it is finalized, everything in it is settled.
• Extrinsics — transactions. Something a keypair signed and submitted: a transfer, a stake, a registration, a weight submission.
• Calls — the individual operations inside an extrinsic. A batch extrinsic can carry thousands, each succeeding or failing on its own.
• Events — what the runtime emitted in response. Most events on a given block have no extrinsic behind them; they are the chain’s own scheduled work.

The rule that trips people up: an extrinsic can succeed while the work inside it fails. A batch reports success as long as the batch itself was dispatched, so for anything wrapped in batch or proxy the events are the only honest answer.

Following a stake

A worked example, and the pattern for almost every other question you will have:

Current chain-wide parameters — block emission, take-rate caps, root weight — are read live on the chain parameters reference →

Questions