Finally submitted!
I built Forge, a trustless freelance marketplace on Solana that turns completed work into permanent on-chain identity. With Forge your wallet becomes your resume, built from verified, on-chain work history that no platform can take away
@colosseum@superteam
Well right now, the Yellowstone gRPC stream is only used to stamp the "submit_slot" for tracking confirmation deltas, rather than driving the tip logic directly.
The tip selection currently keys off Jito's p75 floor, with the AI agent layering in its own confidence-weighted recommendation on top, but neither is yet conditioned on leader distance or skip rate from the stream itself.
I've been building for the @SuperteamNG Advanced Infrastructure bounty, and the most interesting part has been moving beyond the usual “submit tx + poll RPC” flow.
The stack I’m using:
- @SolinfraDev RPC for reliablemainnet access
- Yellowstone gRPC for live slot / network streaming
- Jito Block Engine for priority-aware transaction submission
- Rust for the transaction engine and lifecycle tracker
- Next.js for the operator surface
- Groq for low-latency AI-assisted infra decisions
The biggest lesson: once you start working with streamed network data, transaction submission feels very different.
Instead of treating confirmation as a black box, you can reason about:
- observed submit slot
- dynamic tip selection
- block engine response
- bundle / signature lifecycle
- processed -> confirmed -> finalized progression
- failure classification
- retry strategy
- latency between stages
Jito also makes it obvious that “fee” is not just a static number. Tip selection becomes an operational decision that depends on current network conditions, recent outcomes, and risk tolerance.
Still keeping the actual build private until submission, but this bounty has been a serious deep dive into what a smarter Solana transaction stack should look like.
#Solana #BuildInPublic
I finally decided on a name and I am calling my project Sentry.
I made little updates and here are the highlights:
1. I decided to wrap the whole thing in an installable CLI called Sentry (using npm link for global access). The main goal was a persistent operator console rather than a single run tool.
Running sentry with no arguments drops you into a live sentry REPL that shows a menu on startup and stays open until you exit.
2. Added some commands worth calling out:
a.) Sentry fail test: simulates specific execution issues like submitting a transaction with a zero tip or using an expired blockhash. This confirms that the Rust engine handles failures gracefully and logs them correctly.
b.) Sentry verify: allows quick verification of bundle signatures on Solana to confirm slot status. It gives a full breakdown of the landing slot and confirmation delays.
The entire stack is now containerized using Docker compose so you can spin up the services without installing local dependencies.
Everything works perfectly on mainnet btw.
@SuperteamNG@SolinfraDev@alexfavour
I've been building for the @SuperteamNG Advanced Infrastructure bounty, and the most interesting part has been moving beyond the usual “submit tx + poll RPC” flow.
The stack I’m using:
- @SolinfraDev RPC for reliablemainnet access
- Yellowstone gRPC for live slot / network streaming
- Jito Block Engine for priority-aware transaction submission
- Rust for the transaction engine and lifecycle tracker
- Next.js for the operator surface
- Groq for low-latency AI-assisted infra decisions
The biggest lesson: once you start working with streamed network data, transaction submission feels very different.
Instead of treating confirmation as a black box, you can reason about:
- observed submit slot
- dynamic tip selection
- block engine response
- bundle / signature lifecycle
- processed -> confirmed -> finalized progression
- failure classification
- retry strategy
- latency between stages
Jito also makes it obvious that “fee” is not just a static number. Tip selection becomes an operational decision that depends on current network conditions, recent outcomes, and risk tolerance.
Still keeping the actual build private until submission, but this bounty has been a serious deep dive into what a smarter Solana transaction stack should look like.
#Solana #BuildInPublic
You know...
...not letting your core ideals bend to every opinion doesn't mean you should ignore advice that could actually make you better.
A lot of people stand on "it is my life and I can do whatever I want".
Yes, it is your life but billions of us share the same planet and we have some responsibility to each other and to ourselves because we share this world.
I've been building for the @SuperteamNG Advanced Infrastructure bounty, and the most interesting part has been moving beyond the usual “submit tx + poll RPC” flow.
The stack I’m using:
- @SolinfraDev RPC for reliablemainnet access
- Yellowstone gRPC for live slot / network streaming
- Jito Block Engine for priority-aware transaction submission
- Rust for the transaction engine and lifecycle tracker
- Next.js for the operator surface
- Groq for low-latency AI-assisted infra decisions
The biggest lesson: once you start working with streamed network data, transaction submission feels very different.
Instead of treating confirmation as a black box, you can reason about:
- observed submit slot
- dynamic tip selection
- block engine response
- bundle / signature lifecycle
- processed -> confirmed -> finalized progression
- failure classification
- retry strategy
- latency between stages
Jito also makes it obvious that “fee” is not just a static number. Tip selection becomes an operational decision that depends on current network conditions, recent outcomes, and risk tolerance.
Still keeping the actual build private until submission, but this bounty has been a serious deep dive into what a smarter Solana transaction stack should look like.
#Solana #BuildInPublic
@BybitAfrica@Bybit_Official
I made a transaction of about 430 solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH to pay for something I needed some months ago. The vendor didn't inform me that solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH is not supported so neither of us can access the funds, what can I do?
We reached out to customer support but got nothing so far.
This is the transaction signature, 34zDBMdYzhqiyvuTgXAobJsYtYX6XukfELRtmoXbgEuxSqfn1NsZrZtt6ht9C2tfVAhmoEGMyUdSomAzBBUbfYUS
@BybitAfrica@Bybit_Official
I made a transaction of about 430 solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH to pay for something I needed some months ago. The vendor didn't inform me that solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH is not supported so neither of us can access the funds, what can I do?
We reached out to customer support but got nothing so far.
This is the transaction signature, 34zDBMdYzhqiyvuTgXAobJsYtYX6XukfELRtmoXbgEuxSqfn1NsZrZtt6ht9C2tfVAhmoEGMyUdSomAzBBUbfYUS
@BybitAfrica@Bybit_Official
I made a transaction of about 430 solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH to pay for something I needed some months ago. The vendor didn't inform me that solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH is not supported so neither of us can access the funds, what can I do?
We reached out to customer support but got nothing so far.
This is the transaction signature, 34zDBMdYzhqiyvuTgXAobJsYtYX6XukfELRtmoXbgEuxSqfn1NsZrZtt6ht9C2tfVAhmoEGMyUdSomAzBBUbfYUS
@BybitAfrica@Bybit_Official
I made a transaction of about 430 solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH to pay for something I needed some months ago. The vendor didn't inform me that solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH is not supported so neither of us can access the funds, what can I do?
We reached out to customer support but got nothing so far.
This is the transaction signature, 34zDBMdYzhqiyvuTgXAobJsYtYX6XukfELRtmoXbgEuxSqfn1NsZrZtt6ht9C2tfVAhmoEGMyUdSomAzBBUbfYUS
@BybitAfrica@Bybit_Official
I made a transaction of about 430 solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH to pay for something I needed some months ago. The vendor didn't inform me that solana:2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH is not supported so neither of us can access the funds, what can I do?
We reached out to customer support but got nothing so far.
This is the transaction signature, 34zDBMdYzhqiyvuTgXAobJsYtYX6XukfELRtmoXbgEuxSqfn1NsZrZtt6ht9C2tfVAhmoEGMyUdSomAzBBUbfYUS