BCE development roadmap

[masterOfDisaster]

I want to get this started as I think BKS holders want to be aware of the development progress of BCE.
I’m not intending to have completion dates put to the milestones, but I think a general overview helps to see where BCE is and to prepare next steps.
It would be horrible to have the exchange ready just to realize the reputed signers environment isn’t ready
Ok, just kiddin’, you’ll see below why this won’t happen (in case you don’t already know) but you understand what I mean.

@JordanLee gave an overview of the development here: https://bitcointalk.org/index.php?topic=1033773.msg12005312#msg12005312
I tried to highlight the parts I consider important.

We have two independent iterations moving forward right now. Sigmike is working on the reputation voting system along with its associated block reward as detailed on pages 14 and 15 of the design document. John (aka erasmospunk) will be working on the other voting features unique to B&C Exchange as detailed on page 3 and 4 of the design document. When complete, these changes will be deployed to our publicly available test network, but will not be added to the production network until enough development has been completed to make the exchange fully functional.

When those iterations are complete, we will begin implementing the individual message types unique to B&C Exchange which are described in detail in the design document. Each will be implemented in our public test network when complete. Here is a summary of those message types:

1. Reputed signer deposit public key list
2. Non-reputed signer deposit address request
3. Non-reputed signer withdrawal address request
4. Order
5. Order validation
6. Fill (not signed and no transaction fee)
7. Fill validation
8. Fund transfer
9. Cancel order
10. Withdraw from deposit address
11. Pairing of BlockCredit and BlockShare addresses

We will start with forming the message pairing BlockCredit and BlockShare addresses and client processing of that message. Next will be the reputed signer deposit public key list. Then we will add the non-reputed signer deposit address request message. We will continue to add the rest of the messages to testnet one at a time in the approximate order they would be used in typically.

When the bulk of the messages have been implemented we will begin developing the web interface.

If additional funding is received, we could see additional goodies such as an Android interface that simultaneously functions as a wallet for assets being traded.

As additional funds have been received (at least another 100,000 NBT over the last week in addition to the minimum funding of 200,000 NBT; that’s +50%!) “additional goodies” can be put to the roadmap.

For the additional goodies there’s another statement on bitcointalk: https://bitcointalk.org/index.php?topic=1033773.msg12177198#msg12177198

I’m not sure it is optimal to commit funds to it now. I do think they ought to be the top priorities (CHECKLOCKTIMEVERIFY and the Android app, with the escrow framework as a third priority).

When it does become time to decide whether to commit to an Android app, it makes the most sense to pass a motion to transfer a specific quantity of NuBits raised to the developer that commits to developing it, such as Giannis or Cybnate. There isn’t much reason for me to be directly involved in that because it doesn’t pertain to the core client software.

So, shareholders can decide whatever they want to about how funds raised are allocated and spent. As always, I will be very responsive to motions. But it is probably premature to commit to specific features many months before development begins.

Reputation voting has been implemented. You can see screenshots of the user interface for it here. Once the reputation reward is done (currently in progress), the other new voting types are complete (also in progress) and Bitcoin dividends are supported we will push a release to test net. It probably makes sense to push this release to production so that reputed signers can get established before the exchange is operational.

That already gives a quite detailed overview of the development. We might focus on the additional goodies of which some can be bought with the additional ~100,000 NBT that have been raised.

I second @JordanLee’s assessment that it’s too early now to decide hard and fast what develop in addition, but I think discussing what might be useful and in which order of importance can be done already.

I agree that CHECKLOCKTIMEVERIFY should have priority. But I fear the implementation of it relies on the foreign blockchains having support for it.
The most obvious benefit of CHECKLOCKTIMEVERIFY is the automatic payout to a specified address at a certain point of time in the future. This completely eliminates risk that might arise from reputed signers vanishing.
I’m not able to tell how likely it is that reputed signer disappear and that funds might get locked in multi signature addresses forever, but I’m able to tell that CHECKLOCKTIMEVERIFY completely solves the problem - unless I understood it wrong.

I’d like to see a kind of
"website to access BCE blockchain packages" before
Android apps or an
escrow framework