Web3 integrations
On-chain functionality added to existing products without breaking the experience.
- Engagement
- Fixed-scope build inside an existing product
- Typical timeline
- 6 weeks
- Starts with
- The deployed contract addresses and the two user journeys that touch them.
Your product needs one on-chain element, a proof of ownership, a payment, a token gate, and everything else about it is a normal application. The awkward part is the middle: a user clicks, the network takes twelve seconds to agree, and your interface has to be honest about that without looking broken.
Blockchain features your non-crypto users can still use.
What we build
Concrete artefacts, handed over and documented.
An indexer that reads chain state into your own database, so pages load from Postgres rather than waiting on a public node
Reorganisation handling, so blocks that get reversed are unwound in your data instead of leaving a record that never really happened
Pending, confirmed and failed treated as three real states in the interface, described in words a non-crypto customer understands
A server-side view of the truth, so support can answer whether a transaction went through without asking the customer for a hash
Failover across node providers, because one provider’s outage otherwise looks exactly like your product being down
What changes
On-chain features feel like the rest of the product rather than a bolted-on section
Support resolves transaction questions without escalating to engineering
Page load stops depending on the mood of a public node
How it runs
01Contract surface and states
Which calls the product makes, what each one can return, and what the customer should see at every stage of waiting.
02Indexer and interface
Chain data mirrored into your database, and the front end built against your own records rather than live calls.
03Failure paths
Reversals, reverts, dropped transactions and provider outages, each given a defined behaviour and tested deliberately.
Chosen per project. Named here so you can see the shape of it.
- viem
- wagmi
- The Graph
- Alchemy
- Postgres
Questions we get asked
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.