New app txVulcano and many fixes in the Hub
- We include a new application called txVulcano that creates massive amounts of (test) transactions that are valid and can be mined.
- Mining is battle-field tested now. It works.
- The APIs used for high speed services has substantially matured. There
are various new useful commands that have been enabled and most of the
interface will stay consistent. Although this is not yet guaranteed.
Developers will be able to start developing services using this API.
- A new TransactionBuilder class is shipped.
In previous versions in order to fully create a transaction you would be required to know a mind boggling amount of details about how transactions are build, how they are signed etc. This builder provides a simple class interface and it even includes actual signing so as to make this a stand-alone solution for developers.
- The network API is built on top of a separate network layer that is also made for speed. The submission of thousands of transactions every second from txVulcano app helped stabilising this component for real world usage.
Kick-starting the services cycle
Flowee is a family of products with the hub is first and only product.
The function of the Hub is to become the platform that other services can build on top of. In order to create a great platform you need actual services because actual services implies usage. And we need actual usage to see how the Hub performs in real life.
This was the basic idea that started the -02 series of development. The
effective means to get the services cycle started was the creation of a new
txVulcano. The application is separate and will only
communicate with the Hub over a network.
Included in this release is the new application: txVulcano. An application that creates a massive amount of transactions it pushes to a (regtest debug) Hub instance and subsequently creates blocks of increasing size.
The creation and mining of individual blocks up till 100MB has been achieved and many small bugs fixed in this release as a result. An initial block sync connecting to this debug chain showed a throughput of the Hub of around 30.000&npsb;transactions/second on a modern desktop machine.