7–8 October 2026 · Marina Bay Sands
Testing for products that move value.
A bad transaction does not roll back.
IntraQA tests the product around the chain: wallets, dApps, exchanges, NFTs, and the contracts they call. One engineer owns the coverage, from the control a user touches to the result the network returns.
What the practice covers.
Each of these is its own engagement. Most products need two or three of them.
- 01Smart contract testingFunctional tests of the contract as production will call it: expected paths, edge cases, and what happens when a transaction fails.Unit and integration tests on the contract logicForked state, so the test sees real protocol conditionsRevert, access, and failure paths written down
- 02dApp & wallet testingConnect, sign, switch network, and recover from a rejected signature, across the wallets your users actually hold.MetaMask, WalletConnect, and Ledger in the same matrixNetwork switching and wrong-chain handlingSigning prompts, rejections, and revert messages
- 03Exchange & custody testingProduct testing for exchanges, custody, and payment flows: balances, approvals, limits, and the checks the product says it enforces.Deposit and withdrawal journeysMFA, approvals, and withdrawal limitsKYC steps the product claims to run
- 04NFT & marketplace testingThe full path from upload to the buyer's wallet, including metadata, price, and what the buyer actually receives.Mint and listing with the right metadataPurchase flows and wallet transferFailed and partial transactions
- 05Nodes, APIs & integrationsRPC, indexers, oracles, and third-party APIs, including what the product does when one of them is slow or wrong.Balances and status checked against chain dataIndexer and oracle responsesRetries, fallbacks, and degraded modes
Connect, sign, switch network, reject a signature. The same flow is run on the wallets your users actually hold.
Why this is its own practice.
The transaction stays.
A flaw that reaches mainnet can move funds in one confirmation. The suite has to stop that release before users do.
Wallets do not behave alike.
The same sign-and-send can finish in MetaMask and stall on a Ledger. Coverage includes the wallets your users hold.
The screen can be wrong.
Balances, status, and history are checked against what the chain returned, including when an indexer or RPC is slow.
How an engagement runs.
- 01
Map what moves value
Journeys, wallets, networks, and contract states. The risky flows come first.
- 02
Write the cases
Steps and expected results, owned by one IntraQA engineer, kept in the suite.
- 03
Run the release
Manual passes and automated checks on the build you are about to ship.
- 04
Leave a record
Failures come back with steps. The next release starts from that suite.
Testing and a security review answer different questions.
This practice checks that the product works for the people using it. A security review looks for the ways an attacker could move funds or break the system. When you want both, we scope the review with the cybersecurity practice.
Vulnerability assessmentIn Singapore for TOKEN2049? Bring the flow you are about to ship.