What are your plans for ongoing development and adoption?

We plan on making a number of improvements.

1. Prevention of double withdrawals

An untested implementation of preventing double withdrawal is on our code repository branch here: https://github.com/ConjurTech/switcheo/blob/no-double-withdraw/switc heo/BrokerContract.cs

This uses a mark and withdraw strategy, with backtracking of the blockchain to the marked point to ensure double withdrawal does not happen.

2. Usage of DynamicCall

We hardcoded all known NEP-5 tokens in our contract as Appcall can only be done statically at the moment. We hope to push for the implementation of DynamicCall in the vm / compiler so that the contract does not need to be updated.

3. Refund of failed verifications

This will be done before mainnet deployment.

4. Runtime.Notify

We did not implement this yet due to compiler issues and uncertainty about how this will be used in future. Once confirmed, we can use this to interact with clients / other exchanges before main net deployment.