Lumen

Quantifying execution fairness on Solana. Every trade scored. Every score reproducible. Every receipt anchored on-chain.

[Lumen @LumenLayer]

Solana's bundle layer, made auditable.

90 seconds.

https://t.co/tmer1h6PEy

[Lumen @LumenLayer]

Lumen Layer SDK is live on npm.

npm install @lumen-layer/sdk

Three function calls: stamp, verify, scan. Full TypeScript types. Apache 2.0. Zero dependencies.

For Solana wallets, frontends, and aggregators that want execution quality auditable by their users.

https://t.co/VfMfJZE90W

[Lumen @LumenLayer]

Honoured to place 3rd with @SuperteamAU 🇦🇺

Huge thanks to the Australian Solana ecosystem for backing builders down under 🦘

We’ll continue building infrastructure that brings greater transparency, attribution, and verifiability to on-chain activity.

More depth. More integrations. More coverage.

[Superteam Australia @SuperteamAU]

🥉 Lumen Layer: Three surfaces live, 145,000+ bundles ingested, the receipt protocol verifiable end-to-end against on-chain memo signatures.

What's next is depth, not breadth. More integrations, more attribution coverage, real SDK.

Built by @LumenLayer
Link: https://t.co/CQHfE62QW5

[Superteam Australia @SuperteamAU]

🥉 Lumen Layer: Three surfaces live, 145,000+ bundles ingested, the receipt protocol verifiable end-to-end against on-chain memo signatures.

What's next is depth, not breadth. More integrations, more attribution coverage, real SDK.

Built by @LumenLayer
Link: https://t.co/CQHfE62QW5

[Lumen @LumenLayer]

https://t.co/wOK1ZfHRTY

[Lumen @LumenLayer]

100%, BAM should be the default for that exact reason (open + verifiable).

That’s why Lumen is built on top of Jito BAM attestations: every bundle gets an Execution Quality Score (EQS 0-100) + a SHA-256 verifiable receipt that’s anchored on-chain via memo. No trust, no black box, anyone can re-derive and verify exactly how a trade executed.

Makes the ‘why’ super easy to answer with data instead of hope.

[knox @justinknox__]

at this point if your validator is not running BAM I think you are entitled to ask why.

not in a confrontational way.

just in a "what is the reason" way. because the default should probably be the one where the code is open source and runs in a verifiable environment.

[Lumen @LumenLayer]

Public roadmap.
Four phases. No fake dates.

Directional roadmap. Capabilities listed are planned and prioritised. Specific dates intentionally not committed; the protocol ships when each piece is verified.

[Lumen @LumenLayer]

Lumen's path to becoming Solana's execution quality standard, openly.

PHASE 1: FOUNDATIONS
Adoption infrastructure for the protocol.

• Official SDK published to npm
• 30+ day bundle archive coverage
• End-to-end webhook delivery
• Public protocol metrics dashboard
• First external integration partner

[Lumen @LumenLayer]

PHASE 3: DISTRIBUTION
Lumen receipts in every Solana surface.

• Multiple wallet integrations
• Trading frontend integrations
• Solana Blinks for receipt verification
• Self-serve developer onboarding
• MEV research partnerships

[Lumen @LumenLayer]

If you’re building on @Solana and your users care about execution integrity, DEXs, launchpads, MEV-aware infra. Lumen receipts are open.

Spec is public. API is live at https://t.co/xJkqUrNqzj.

[Lumen @LumenLayer]

Execution context, not “proof you weren’t front-run.”

The distinction matters. We don’t tell you what happened to your trade emotionally. We give you a cryptographically verifiable record of how it executed.

You decide what to do with it.

[Lumen @LumenLayer]

Execution context, not “proof you weren’t front-run.”

The distinction matters. We don’t tell you what happened to your trade emotionally. We give you a cryptographically verifiable record of how it executed.

You decide what to do with it.

[Lumen @LumenLayer]

Lumen Layer is in the @colosseum Frontier Hackathon.

Read the project: https://t.co/Gff0MDGkId
Read the spec: https://t.co/ESNdVJxooS

An open execution fairness protocol for Solana. Every Jito bundle scored against a public rubric. Every receipt anchored on-chain via memo. Free for anyone to verify.

[Lumen @LumenLayer]

Take a Jito bundle. Score it against a public rubric. Anchor the receipt on Solana. Let anyone verify.

https://t.co/tmer1h6PEy

[Lumen @LumenLayer]

Bigger BAM = deeper bundle data for everyone building verification on top of it.

Lumen Layer's wallet scanner and receipt protocol scale directly with this expansion.

The open layer wins.

[Jito @jito_sol]

Excited to announce the launch of FireBAM! 🔥💥

FireBAM, the Frankendancer-compatible BAM client, is now live on both testnet and early third-party onboarding, expanding BAM as well as the Early Subsidy Program to an additional ~12% of Solana validators!

More on this below. 🧵

[Lumen @LumenLayer]

Submitted to Colosseum Frontier today.

Three surfaces live, 145,000+ bundles ingested, the receipt protocol verifiable end-to-end against on-chain memo signatures.

What's next is depth, not breadth. More integrations, more attribution coverage, real SDK.

https://t.co/iNJyjpoZXn

[Lumen @LumenLayer]

4/ Receipts bind the transaction signature, bundle ID, slot, EQS score, and flags into a single hash.

The hash is anchored on Solana via memo. Anyone can independently re-derive it. No trust required. No special access. The protocol is the proof.

5/ The wallet damage scanner uses a documented lower-bound heuristic. 0.3% of trade size for confirmed sandwiches. 0.1% for frontrun suspicion.

Real extraction is usually higher. The estimates are intentionally conservative.

The methodology is published in full.

Apache 2.0. Built on Jito BAM. Solana native.
https://t.co/ESNdVJxooS

[Lumen @LumenLayer]

1/ Lumen is live.
Most Solana traders never find out what happened to their order between sign and settle.

Lumen makes that information legible, scored, and cryptographically verifiable.
https://t.co/tmer1h6PEy

[Kairos @SimplyKairos]

https://t.co/pYumdGF643

[Lumen @LumenLayer]

2/ Three surfaces.
Wallet damage scanner. Paste any address, see what extracted from it. Receipt protocol. Every trade gets a SHA-256 bound, on-chain anchored receipt anyone can verify.

Public spec. Schema and scoring algorithm are open source.

3/ Receipts are scored on EQS, an Execution Quality Score from 0 to 100.

Ten flags covering sandwich detection, frontrun suspicion, bundle congestion, slippage anomalies, sniper proximity. Bands: Clean, Acceptable, Degraded, Harmful.

Every flag is reproducible from public bundle data.