docs: Solana TX landing active bench V0-Lean (methodology + plan)#79
Merged
Merged
Conversation
Pre-registered methodology v1.1 + launch plan (5 services x us-east x 1h cadence, ~$159/mo). Required by Rule #1 to be merged before any sponsor contract. - methodology/solana-tx-landing-active.md: probe payload, submission flow, drop reasons, sponsor-proof guarantees, versioning - solana-landing-tiered-architecture.md: V0-Lean spec + escalation tiers (V0.5, V1, V2) - solana-landing-cost-model.md: probe cost formula + tip-floor analysis (note flagging arithmetic error in scenarios table) - solana-landing-deployment-checklist.md: 8-step Florent runbook (keypair, API keys, Railway env, sponsor outreach) - solana-landing-active-bench-plan.md: redirect to current docs
5 tasks
Flotapponnier
added a commit
that referenced
this pull request
May 21, 2026
* bench #27: solana-tx-landing-latency (active probing) New separate bench page complementing #16 (observational market share). Measures p50/p99 time-to-land in ms and slots, plus landing rate, across 5 services from us-east at 1h cadence. Querying solana_landing_probe_* metrics emitted by the active prober (mobula-monorepo PR #6396). Methodology pre-registered at docs/methodology/solana-tx-landing-active.md (PR #79, merged). Cross-linked with #16 via disclaimer + related_benches field. * benchmarks: add 4 france-cryptos sprint 1 bench pages (018, 022, 025, 026) - buyback-audit (#18): Hyperliquid AF + Sky SBE on-chain execution ratio - token-unlocks (#22): conditional impact median bucketed by % supply - oracle-deviation (#25): 4 oracles × 10 USD pairs deviation bps - validator-yield (#26): Solana + Hyperliquid net yield comparison All specs validated against live Prom prod (https://prometheus-production-0859.up.railway.app). Editorial scope honest: Sky low ratio = batched execution (not failure), ARB v1 limitation noted, SOL Chainlink lag flagged as real signal, 'Net of MEV' framing rejected in favor of 'Net Yield Comparison'.
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.
Résumé
Pré-enregistre la méthodologie de l'extension active de bench #16 (Solana TX Landing) avant tout contact sponsor — Rule #1 du sponsor-proof framework (sponsors ne peuvent influencer ni la méthodologie ni le résultat).
Scope V0-Lean
5 services × 1 région (us-east) × cadence 1 h × ~$159/mo (à SOL=$86) :
swqos_only=true(isole le path Helius pur du fan-out Jito)Documents
docs/methodology/solana-tx-landing-active.mddocs/solana-landing-tiered-architecture.mddocs/solana-landing-cost-model.mddocs/solana-landing-deployment-checklist.mddocs/solana-landing-active-bench-plan.mdPourquoi ça doit merger AVANT le code
Rule #1 du sponsor-proof framework : la méthodologie doit être committée publiquement sur GitHub avant tout contrat sponsor. Sinon les sponsors peuvent (de fait ou perçu) influencer ce qui sera mesuré.
PR liée
Code prober associé sur mobula-monorepo : https://github.com/MobulaFi/mobula-monorepo/pull/6396
Test plan