Every regulated digital-asset platform we have built resolves into four subsystems: issuance, custody integration, transfer policy and settlement. Miss one and the other three inherit its absence as operational pain.
Issuance covers the offering lifecycle — eligibility, subscription, allocation, redemption. Custody integration keeps key ceremonies with the custodian while giving the platform controlled signing interfaces. Transfer policy encodes who may hold and move assets. Settlement makes movements final, recorded and reconcilable.
Reconciliation is the product
Auditors do not trust dashboards; they trust replay. Our settlement pipelines record every movement as an event the books can be reconstructed from — deterministically, idempotently, provably. The evidence pack is generated from the system itself, not assembled by hand at quarter-end.
Identity-bound transfers, particularly ERC-3643 frameworks, tie these subsystems together: eligibility as verified claims, policy enforced in the transfer itself, evidence captured at decision time.
Build the surroundings first
Teams naturally start with the token contract. We start with the registrar's reconciliation spreadsheet and the auditor's evidence list — then design backwards. The token is the smallest part; the surroundings are the system.
Related articles