Applications & Protocols
For product and engineering teams building an application that interacts with accounts, contracts and operational services. Define the complete journey, including approvals, pending actions and exceptions, before treating a working contract as a finished application.
Illustrative engineering workflow. Interfaces, environments and responsibilities are assessed for the agreed scope.
01 / SCOPE
Different transaction models require different state machines.
Scope CEX spot or derivatives systems, or DEX AMM, order-book and derivatives models. Define matching or pricing behaviour, balances, order states and settlement boundaries. OTC/P2P workflows need offers, escrow, settlement evidence and explicit dispute responsibilities. Operating a venue requires separate commercial and legal decisions.
Define lending, borrowing, staking, vaults, rewards, collateral and liquidity mechanics. Specify accounting units, interest or reward calculations, withdrawal conditions and liquidation inputs where applicable. Test stale oracle data, insufficient liquidity and interrupted operations against agreed economic assumptions.
Decide which system is authoritative for orders, balances and positions. Reconcile on-chain events with backend records. Specify duplicate requests, partial completion and delayed confirmations so one visible user action cannot silently become several financial operations.
02 / SCOPE
Scope the interfaces and backend behaviour together.
Build scoped wallet applications, authentication, embedded-wallet integrations and smart-account journeys. Specify signing requests, session permissions and recovery boundaries. Assess the chosen provider and network interfaces; custody and key-management responsibilities must be agreed separately from frontend implementation.
Connect frontends and backends to contract interfaces with clear transaction states. Design onboarding, network switching, approval and confirmation journeys alongside administration tools. Handle rejected signatures, insufficient fees, expired sessions and refreshed pages without presenting an unfinished transaction as complete.
Scope checkout, stablecoin payments, invoices, payouts and reconciliation. Define accepted networks and assets, invoice expiry, amount matching and confirmation thresholds. Approval controls, payout permissions and exception queues must reflect the operator model; refund and treasury policies require explicit business decisions.
03 / SCOPE
A user-facing journey depends on observable backend state.
Provide scoped transaction histories, reconciliation views and exception records. Define which actions an operator may retry or cancel and when the application must wait for chain state. Record manual decisions without hiding them inside an automated success state.
Agree supported networks, account models, dependencies and test environments. Security engineering and audit preparation can be included, but are not independent certification. Market access, custody, legal obligations and commercial launch decisions remain separate from software delivery.
FROM BRIEF TO HANDOVER
Map user journeys, account authority and protocol rules. Agree which components are custom-built, integrated or explicitly excluded from the engagement.
Implement the selected contracts, backend services and interfaces. Review transaction states and administrative behaviour using concrete acceptance scenarios.
Exercise successful and rejected actions, delayed confirmations, disconnects and restart recovery in suitable test environments. Record dependency assumptions and unresolved issues.
Deliver agreed code, interface documentation, configuration and operator notes. Establish deployment ownership, maintenance boundaries and approval for any live rollout.
BEFORE WE BEGIN
No. This scope builds venue or protocol workflows. Software that trades through an existing exchange belongs in the Trading Development service.
No. Signing, key storage and recovery depend on the selected account model. Custody responsibilities must be explicitly defined with the relevant providers and owners.
A prototype establishes only its tested behaviour. Production scope, operating responsibilities, independent review where required and release checks need their own evidence.
CONNECTED CAPABILITIES
YOUR NEXT STEP
Tell us about your users, existing tools and the outcome you want. Please do not send passwords, private keys or account secrets.
