/quantus/block/1 shows one extrinsic and nothing else. The index holds twenty-eight events for that block and the route returns none of them: BlockDetail has body and no events.
The asymmetry is visible from the outside. An account page shows a Wormhole::NativeTransferred at block 1; following the link to block 1 shows no
sign of it.
Two things worth noticing, and neither is visible anywhere on the site today:
The chain's opening distribution went out as 21 wormhole transfers in block
1's Initialization phase — not in block zero, and not as extrinsics.
Vesting::LaunchMomentSet fired at block 1, so vesting has been exercised
even though the calls index shows zero Vesting::* dispatched. A pallet used
by the runtime rather than by a submitter looks unused from the call side
alone.
Scope
Store — events_at(chain, height), the counterpart to the existing extrinsics_at.
Entities / API — BlockDetail gains the block's events.
Web — render them on the block page, grouped by phase, and where the
phase is ApplyExtrinsic(n) nest them under extrinsic n. The block already
lists its extrinsics; an event's extrinsic_index is exactly the join that
turns "what was asked" and "what happened" into one readable block. Initialization and Finalization events belong to the block rather than to
any extrinsic and want their own groups.
Note
phase and extrinsic_index are already stored — they were kept for precisely
this join and have never been used. Nothing new needs indexing.
## What
`/quantus/block/1` shows one extrinsic and nothing else. The index holds
**twenty-eight events** for that block and the route returns none of them:
`BlockDetail` has `body` and no `events`.
The asymmetry is visible from the outside. An account page shows a
`Wormhole::NativeTransferred` at block 1; following the link to block 1 shows no
sign of it.
## What block 1 actually holds
```
extrinsic 0 Timestamp::set
event 1–41 Wormhole::NativeTransferred × 21 Initialization
event 42 Vesting::LaunchMomentSet ApplyExtrinsic(0)
event 45 System::NewAccount Finalization
event 46 Balances::Endowed Finalization
event 47 Balances::Minted Finalization
event 49 Wormhole::NativeTransferred Finalization
event 50 MiningRewards::MinerRewarded Finalization
event 51 ZkTree::TreeGrew Finalization
```
Two things worth noticing, and neither is visible anywhere on the site today:
- The chain's opening distribution went out as **21 wormhole transfers in block
1's `Initialization` phase** — not in block zero, and not as extrinsics.
- `Vesting::LaunchMomentSet` fired at block 1, so vesting *has* been exercised
even though the calls index shows zero `Vesting::*` dispatched. A pallet used
by the runtime rather than by a submitter looks unused from the call side
alone.
## Scope
1. **Store** — `events_at(chain, height)`, the counterpart to the existing
`extrinsics_at`.
2. **Entities / API** — `BlockDetail` gains the block's events.
3. **Web** — render them on the block page, **grouped by phase**, and where the
phase is `ApplyExtrinsic(n)` nest them under extrinsic `n`. The block already
lists its extrinsics; an event's `extrinsic_index` is exactly the join that
turns "what was asked" and "what happened" into one readable block.
`Initialization` and `Finalization` events belong to the block rather than to
any extrinsic and want their own groups.
## Note
`phase` and `extrinsic_index` are already stored — they were kept for precisely
this join and have never been used. Nothing new needs indexing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
/quantus/block/1shows one extrinsic and nothing else. The index holdstwenty-eight events for that block and the route returns none of them:
BlockDetailhasbodyand noevents.The asymmetry is visible from the outside. An account page shows a
Wormhole::NativeTransferredat block 1; following the link to block 1 shows nosign of it.
What block 1 actually holds
Two things worth noticing, and neither is visible anywhere on the site today:
1's
Initializationphase — not in block zero, and not as extrinsics.Vesting::LaunchMomentSetfired at block 1, so vesting has been exercisedeven though the calls index shows zero
Vesting::*dispatched. A pallet usedby the runtime rather than by a submitter looks unused from the call side
alone.
Scope
events_at(chain, height), the counterpart to the existingextrinsics_at.BlockDetailgains the block's events.phase is
ApplyExtrinsic(n)nest them under extrinsicn. The block alreadylists its extrinsics; an event's
extrinsic_indexis exactly the join thatturns "what was asked" and "what happened" into one readable block.
InitializationandFinalizationevents belong to the block rather than toany extrinsic and want their own groups.
Note
phaseandextrinsic_indexare already stored — they were kept for preciselythis join and have never been used. Nothing new needs indexing.