feat(solana-tx-landing): expose slot delta column + rewrite content - #117
Merged
Merged
Conversation
solana confirmation is slot-level: when a slot reaches supermajority,
every tx in it becomes confirmed at the same instant. wall-clock ms
between services that landed in the same slot differs only by goroutine
startup variance and RTT, not by actual routing quality. slot_delta is
what the chain records and is sponsor-proof (RTT-independent).
changes:
- schema: optional slot_p50 / slot_p99 query fields per provider
- spec.ts: fetch slot queries when present, attach slots: {p50,p99} to
ProviderResult
- ledger-table: conditional 'Slot delta' column showing p50 / p99 slots
when any provider declares slots; renders as compact mono cell
- solana-tx-landing-latency.yml: add slot_p50 / slot_p99 queries for the
4 active providers; full rewrite of abstract, methodology, findings,
faq to lead with slot delta as the canonical metric and explain ms as
derived. new faq entries for slot definition + signatureSubscribe path.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Validation experimentale a confirmé que Solana confirmation est slot-level: quand un slot atteint supermajority, toutes les txs dans ce slot deviennent
confirmedau même instant. Si 3 services delivrent leur tx dans le même slot, leurs wall-clock ms sont identiques (artefact de mesure) alors que slot_delta capture la vraie inclusion.slot_delta est sponsor-proof:
signatureNotification.context.slotms reste publié à côté pour l'intuition (trader pense en secondes pas en slots) mais slot_delta est la métrique citable en audit.
Changes
slot_p50/slot_p99queries per providerslots: {p50, p99}to ProviderResultp50 / p99in compact mono cellslots?: { p50: number; p99: number }fieldTest plan
pnpm validate(18 specs OK)pnpm typecheckcleanpnpm buildcleanslotsfield = no column)