BUILD

What is written, and what comes next.

Written and checkable

  • BilateralSwap.sol, a complete bilateral settlement contract. It compiles under solc 0.8.24 to 3,726 bytes and has no admin function of any kind, so there is no key that can move a counterparty's funds.
  • Nine test cases covering settlement, cancellation, deadline behaviour and access control, written against Foundry.
  • Our own infrastructure. We build and host our own e-commerce platform, serving customers across Indonesia, on servers we run.

The plan from here

  • Run the test suite, then deploy to a testnet so the contract has an address anyone can read.
  • Write the Daml implementation and put it beside the Solidity one, so the two can be compared line for line.
  • Have it audited independently before it settles anything that matters.

Both implementations get published, the Solidity one that exists now and the Daml one as it is written. The comparison is the part worth reading: where the escrow pattern stops being necessary, and where a reverted transaction becomes a state that cannot be represented at all. That is the document an EVM developer needs before they will look at Canton seriously, and it does not exist yet.

Both or Neither is built and operated from Indonesia. It is not an exchange, a broker, or a money services business. It does not custody assets outside the duration of a settlement window, holds no financial services or commodity trading licence, and nothing on this page is an offer to trade or a solicitation to do so.