Skip to content
ZARX Technologies

Web3 Products

On-chain products built to pass an audit

We design and build smart contracts, dApps and wallets with tested code, safe key management and onboarding that feels like a normal app – so your users never need to understand gas fees.

  • Test suites on every contract
  • Audit-ready code and documentation
  • Multisig and role-based admin keys by default

Sound familiar?

The problems we hear most

  • “We're nervous one bug could drain the treasury.”

  • “Users drop off the moment we ask them to install a wallet.”

  • “We're not sure what India's rules mean for our product.”

Outcomes

What changes for you

  • Contracts with full test coverage on critical paths, ready for an external audit.

  • Wallet-less or embedded-wallet onboarding that converts mainstream users.

  • A clear map of the compliance questions to settle with your lawyer before launch.

Capabilities

What we build

  • Smart contracts

    Tokens, NFTs, staking, vesting and escrow.

    • Solidity
    • OpenZeppelin
  • dApps & dashboards

    Web front ends connected to on-chain data.

    • Next.js
    • wagmi / viem
  • Wallets & onboarding

    Embedded wallets, account abstraction and gasless transactions.

    • Account abstraction
  • Tokenised loyalty, tickets & game items

    Utility users understand without a crypto glossary.

    • ERC-721
    • ERC-1155
  • Indexing & integrations

    Subgraphs, oracles, payment rails and off-chain APIs.

    • The Graph
    • Chainlink
  • Security & audit prep

    Threat modelling, test suites, audit coordination and fixes.

    • Foundry
    • Static analysis

Deliverables

What you walk away with

Everything is yours at handover: in your repository, your accounts and your files.

  • Architecture and threat model
  • Smart contracts with tests
  • Deployment scripts for testnet and mainnet
  • Admin multisig set-up
  • dApp front end
  • Indexer or API
  • Audit-ready documentation
  • Post-audit fixes
  • Runbook for upgrades and incidents

Timeline

Typical build

A typical engagement, week by week. Your plan is confirmed in the Discovery Sprint.

  1. 01

    Weeks 1–2

    Utility design and threat model

  2. 02

    Weeks 3–8

    Contracts and app in sprints, weekly testnet demo

  3. 03

    Weeks 9–11

    Independent audit by a firm you choose, then fixes

  4. 04

    Week 12

    Mainnet launch and monitoring

Technologies

What we build with

We choose the stack that fits your product, not the other way round.

Chains
EthereumPolygonBaseArbitrum
Contracts
SolidityOpenZeppelinFoundryHardhat
Front end
Next.jswagmiviem
Data
The GraphChainlink oracles

Ways to start

Pick the size of the first step

Each option has a fixed scope and a fixed quote.

  • 1–2 weeks

    Web3 Feasibility Sprint

    Best for: Deciding whether on-chain is right for your product

    Fixed quote after a free call

    • Utility design and chain choice
    • Threat model
    • Compliance questions for your counsel
  • 8–12 weeks

    Build to Audit

    Best for: Contracts and app built ready for an independent audit

    Fixed quote after a free call

    • Contracts with tests
    • dApp and admin set-up
    • Audit-ready documentation
  • 1–2 weeks

    Contract Review

    Best for: Existing contracts before a formal audit

    Fixed quote after a free call

    • Internal review of your contracts
    • Findings by severity
    • Fix recommendations

Right fit

Are we right for this?

Great fit if you…

  • Have a use case that needs ownership, transparency or programmable payments
  • Will fund an independent security audit
  • Want mainstream users, not only crypto natives

Probably not a fit if you…

  • Want a token launch with no product
  • Want guaranteed-return schemes
  • Want to skip the audit
  • Prefer to stay anonymous as founders

Quality & security

Standards this work ships with

  • Threat model before any code
  • Tests on every state-changing function
  • Static analysis on every pull request
  • No single-key admin rights in production
  • Independent audit before mainnet
  • Incident runbook and on-chain monitoring

FAQ

Common questions

Something else on your mind? Ask us directly.

How much does smart contract development cost?

It depends on how many contracts you need, how complex the logic is and which chains you deploy to. We usually start with a 1–2 week Web3 Feasibility Sprint covering utility design, chain choice and a threat model, which ends with a fixed quote. Budget separately for an independent audit, which is paid directly to the audit firm you choose.

Do you do the security audit yourselves?

No, and you shouldn't want us to. We prepare your contracts for audit with tests, static analysis, a threat model and clear documentation, then fix every finding. The audit itself should come from an independent firm you choose, so the people checking the code are not the people who wrote it.

Which blockchain should we build on?

It depends on your users, fees and the ecosystem you need. We mostly build on Ethereum and EVM networks such as Polygon, Base and Arbitrum, where tooling and audit expertise are mature. During discovery we compare transaction costs, wallet support and liquidity for your use case, then recommend a chain with the reasons written down.

Can users sign up without a crypto wallet?

Yes. With embedded wallets and account abstraction, users can sign up with an email or social login and get a wallet created for them in the background. We can sponsor gas fees so they never need to buy crypto to start. Experienced users can still connect their own wallet if they prefer.

What are the rules for Web3 businesses in India?

If your product exchanges, transfers or holds digital assets on behalf of users in India, it may need to register with FIU-IND under the Prevention of Money Laundering Act. Tax and other rules may also apply. We flag these questions early in discovery and work alongside your legal counsel; we don't give legal advice ourselves.

Can contracts be upgraded after launch?

They can be, if upgradeability is designed in from the start using proxy patterns, with upgrades controlled by a multisig and a time delay so users can see changes coming. Some products are better immutable for trust reasons. We discuss the trade-off with you, document the choice, and include an upgrade runbook at handover.

Let's build

Build on-chain without the sleepless nights.

Tell us what you're making. A founder replies within one working day with next steps, a rough timeline and a budget range.