Solana development, designed for a congested network
We build on-chain programs, trading and execution systems, and integrations into trading systems that are already running. Every retry path is designed so a dropped transaction can't turn into a duplicate trade.
Talk to an engineer, not a salesperson.
Skills clients endorsed include Solana, Trading Automation and Blockchain.
SOL-01Order → Sign → Send → Confirm
IllustrationThe problem
Where Solana systems go wrong
On Solana, a transaction can be dropped, retried and land twice. In a trading system that is a duplicate position, not a duplicate log line.
Solana rewards systems that are correct under congestion. Transactions drop and retries duplicate. An execution path that was never tested against a congested network produces a financial incident rather than a latency spike. Idempotency is the design constraint, not an optimisation.
What we build
What we build on Solana
On-chain programs, and the systems that trade through them.
Program development
On-chain programs in Rust. We work out the account model and constraints before writing code, because they are hard to change once deployed.
Trading and execution systems
Routing, sizing, transaction construction and a retry policy that is idempotent from order to fill. Risk limits are checked on the server before anything executes.
Bundle integration
Bundle submission for control over ordering. The tip is weighed against the chance of inclusion under congestion.
Integrations into live trading systems
Adding to a system that already trades is its own discipline: a written scope, a staged rollout and a rollback plan. The review below comes from an integration of this kind.
Reconciliation
Off-chain state is compared continuously with on-chain fills. A mismatch shows up as an alert, not a surprise at month end.
Congestion and failure testing
Behaviour checked against dropped transactions, expired blockhashes and simulated congestion. The happy path is the smallest part of the test plan.
Evidence
What a client wrote
A client's review and the related jobs, with their dates. Client names withheld.
“Excellent developer. Anupam delivered a complex production integration with strong attention to architecture, safety, testing, and rollback procedures. He followed the scope carefully, communicated clearly, and provided a reusable solution…”
Rust Certification · HackerRank · July 2022
Related work
| When | Project type | Engagement | Rating |
|---|---|---|---|
| Sep 2026 | Solana trading-system integration | Hourly · 17 h | 5.0 out of 5 stars |
| Jun–Aug 2026 | Solana DEX bot | Hourly · 62 h | No feedback given |
| Jun–Sep 2026 | Blockchain arbitrage bot | Hourly · 71 h | No feedback given |
Ratings, reviews and engagement dates come from client contracts delivered through Upwork, checked 24 Sep 2026. '…' marks where a quote was shortened. Client names stay private.
Detail
Retry safety and reconciliation
Every trade needs an answer to one question: if this send times out, did it land? We record the intent before signing, check the signature's status before any resend, and reconcile fills against what we meant to do.
Detail
- Assign a
client order IDand persist the intent before signing. - Build and sign with a recent
blockhash; send and confirm with a timeout. - On timeout, query the
signature statusfirst. Resend only if it did not land. - If the
blockhashhas expired, rebuild under the sameorder ID. - Reconcile fills against the
intent table; alert on any mismatch.
A first step
Already trading? Start with a review
If your system is already running, a review of the execution path is a good first engagement. We look at retry safety, reconciliation gaps and what happens under congestion. You get a written list of findings, ranked by risk.
We build and test trading infrastructure. We don't give trading advice or make claims about returns.
Process
How a Solana project runs
Four steps. You get something you can read at the end of each.
Discover
We learn your programs, your existing system and what must never happen, such as a double fill.
You get
A written brief.
Architect
Account model, execution semantics, retry policy and a rollback plan, written down before code.
You get
An architecture doc, the key decisions (ADRs) and a milestone plan with estimates.
Build
Programs and services with failure-path tests from the start, on devnet before real funds.
You get
Regular demos and written updates.
Validate and hand over
Tests for congestion, dropped transactions and duplicate sends, then a staged rollout with limits.
You get
UAT sign-off and handover notes.
Pricing
How pricing works
A fixed-price review or discovery sprint, then fixed-price milestones. Work inside a running system can also be hourly.
The number of programs, whether we work inside an existing system, the integrations, and how much testing against congestion the risk calls for.
- Discovery sprint
- Fixed-price milestones
- Dedicated engineer, monthly
- Hourly
Start here
Launching on Solana soon?
Web3 readiness check
An 11-point check before you launch a contract or dApp. Results on screen; no email needed.
Questions
Questions we get about Solana work
What does MEV-aware mean here?
That ordering exposure is treated as a real cost and designed against. In practice, that means controlling transaction ordering where the network allows it, with tips weighed against the chance of inclusion under congestion.
Why does idempotency come up so often?
Because on Solana a transaction can be dropped, retried and land twice. In a trading system that is a duplicate position, not a duplicate log line. Every retry path has to be idempotent by construction.
Can you work on an existing Solana system?
Yes. The review on this page comes from that kind of job: an integration into a trading system that was already running. A review of the retry and reconciliation path is a good first step.
Do you promise trading results?
No. We build and test the infrastructure: programs, execution, risk checks and monitoring. Strategy and returns are yours, and we make no performance claims.
Three ways to start
Planning a Solana system?
Pick whichever suits you. A person reads every message.