Brief technical situation update:
After negotiations and enrolling events during the past week with ABN AMRO bank, which is the 3rd largest bank in The Netherlands, they've chosen us for their disruptive high tech program embracing a fairly extensive yet carefully selected list of fintech companies with whom they intend to get ahead competition in the adoption of blockchain and other disruptive technologies closely related to the banking field.
That progression of events is highly desired and fits HEAT perfectly - in that our next step would've in any case been the deployment of microservices. Microservices is an unique feature of HEAT, as described by the lead developer Dennis in the following words in our many banking / fintech contact meetings:
The big issue with creating custom blockchain applications for your organisation is that in most cases you'll need skilled blockchain developers, which are hard to come by. With micro services all you need is one of your own programmers who is able to write one or more TypeScript scripts. The scripts are able to react to all the things that happen on the blockchain by simply registering an event listener, they can also do everything you can do on heat (send money, message, place order etc). Finally from a micro service you can connect to any other system or database in your organization through standard methods.
HEAT microservices, enhanced with our unique replicator model for external RDBMS such as Mysql, DB2, H2 or Berkeley, allow anyone to implement BaaS services in the HEAT public blockchain, and specifically they allow us Heat Ledger Ltd to deploy customized duplicates of the HEAT technology into corporate environments without dedicated personnel to service blockchain software in particular. This is the model we're going to develop into full fruitition while delivering the pilot solution for ABN AMRO's needs during the next 100 days, thus yielding us 3x leveraged benefit:
- Completion of the possibly highly lucrative bank co-op project
- Streamlined general corporate solution deployment model, and
- Considerable feature enhancement for the public HEAT blockchain
The high HEAT tps figures advertised are fit for HEAT blockchain internal corporate use already. Whereas even the highest speed data network lag between various continents of the earth AFAIK makes it impossible to disseminate p2p data globally at speeds higher than well under 20 tps in the best case scenario, the goal for the public HEAT chain of guaranteed 1000 tps 24/7 is actually designed to not be dependent on node communication lag.
Due to the replicator infrastructure as described in the HEAT White Paper we can use single node pre-matching and broadcast the bulk pre-matched tx batch to p2p network at regular intervals with sophisticated ordering automation handling any race conditions or frontrunning situations. This is some near future (~6-12 months) development that goes along with the restructuring of the p2p traffic to binary messaging (Akka). The current HEAT model allows us to deploy high speed pilot projects for organizations like ABN AMRO, as corporations use private blockchain configuration in closed environment with either single matching node or very high speed dedicated / cloud server network capable of reaching 50+ tps levels even on realtime p2p basis.
We've got to resolve some public key issues for full blockchain rescan before the new server release for enabling HEAT block rewards is made available. The block rewards are expected to be re-enabled when that's sorted out, which should happen during the weekend or shortly after. Interest towards HEAT and Heatwallet.com trading has been improving sharply during the past days and is expected to keep doing so when the block rewards are enabled.