01
New projects
A paragraph about the problem is enough to start. We reply within two working days, usually with questions rather than a quote.
Blockchain · Service Solana program development
Solana programs in Rust with Anchor: account and PDA design, SPL tokens and Token-2022 extensions, tests against a local validator, and a security review.
In short
Solana runs programs written in Rust under a different model from Ethereum: the code holds no state, and all data lives in accounts that each transaction must name in advance. We write Solana programs with the Anchor framework, design the account layout and its access checks, integrate SPL tokens, and test and review the result before it holds value.
- How to engage
- Product build, Security review
- Practice
- Blockchain
Signs this is the right service
- Your users, liquidity or partners are on Solana and the product has to be there too.
- The use case needs many low-cost transactions — payments, trading, games — that would be expensive elsewhere.
- A team experienced in Solidity is moving to Solana and the account model is slowing them down.
- An existing program needs a review, an upgrade, or its upgrade authority put under proper control.
What you get
Account and PDA design
Which accounts exist, who owns them, how program-derived addresses are seeded, and how the layout can change later.
Anchor programs in Rust
Instruction handlers with explicit signer, owner and constraint checks — the checks whose absence is behind many Solana exploits.
Token integration
SPL tokens and Token-2022 extensions such as transfer hooks and transfer fees, chosen for what the product needs.
Testing
Unit and integration tests against a local validator, including transactions built to pass the wrong accounts on purpose.
Upgrade authority and deployment
The upgrade key held in a multisig from the first deployment, releases scripted, and a decision on whether the program ever becomes immutable.
The process
- 01
Design the accounts first
The account model and its invariants are written down before any instruction is coded.
- 02
Build with tests alongside
Every instruction arrives with tests for the path that should work and the ones that should fail.
- 03
Review adversarially
A second engineer who did not write the program tries to break it.
- 04
Deploy under a multisig
Devnet first, then mainnet, with the upgrade authority under shared control.
RustAnchorSolanaSPL TokenToken-2022TypeScriptSquads
Solana development: common questions
How is Solana development different from Ethereum?
- Programs hold no state of their own; data lives in separate accounts that each transaction lists up front. That allows transactions to run in parallel and makes account validation the main security concern.
Do you use Anchor or native Rust?
- Anchor for most programs, because its account constraints remove a class of mistakes. Native Rust where compute limits or program size make it necessary.
Can a Solana program be upgraded?
- Yes, by whoever holds its upgrade authority, unless that authority has been removed. We put it under a multisig and agree in advance what would justify an upgrade.
Does your review replace an external audit?
- No. For programs holding meaningful value we recommend an independent audit as well; our review means the auditor spends their time on the hard problems.
06 / Let’s build
Bring us the difficult problem.
02
Careers
Engineers, designers and researchers who like systems that are hard to get right. Send something you built and what you would change about it now.
03
Studio
Based in India and working remotely, with overlap hours agreed up front so your team always has a time to reach us.
04
Read
Guides on AI agents, RAG, MCP, tokenization and chain abstraction, written by the engineers who build them.