Blockchain stats

Komodo blockchain scaling is a load test requiring a lot of resources, preparation, co-ordination and then statistics.  Any load test does.  My days at Omnium World were about seeing how many users could upload their portfolio work to our servers.  My days using asterisk and doing the occasional load tests for carriers to see how many concurrent calls their networks could handle.

We are using AWS for infrastructure – EC2, DynamoDB, S3, ECS and maybe another service or two.

Komodo AWS Blockchain Scaling

Notary node operator blackjok3r from the a-team has built a docker image (with help from NN operator patchkez of dragonriders) for us to scale.  Testing with 64 chains, we created a start parameter using the serverless framework for a simple URL to poll to trigger the transaction blasters.

As the blasting of transaction happens across the chains, we use the blocknotify event to send the latest block info.  It is captured using AWS API Gateway ->Lambda -> DynamoDB.  Another serverless framework thing to speed us along.

We’re now at a stage of tuning to maximise the transactions per second, but more importantly – have statistics available for the public to view in realtime (or close to realtime) on our efforts.  Something like this is being prepared.

Blockchain stats

Massaging sample data for smk782’s stats site, is the work for the next day.

Stay tuned for more updates 😀

Checkout Komodo Pioneers while you’re here!


2 thoughts on “Komodo Blockchain Scaling – 1 million tx per second – stats – prep etc.”

    1. How can you “fake 1 million tx / s” when they are decentralized blockchain transactions? The first confirmation is after 1 minute, which 60,000,000 tx have been processed across the network.

      If the network contains more nodes, then it is just more nodes confirming the transactions. For the sake of costs, we cannot run so many nodes – blocks are full.

      The chains are federated into a cluster which talk to one another (e.g. sharding) and the coin supply between all chains is maintained via a burn protocol, a smart contract – in the core of Komodo. The smart contracts are an implementation of the Crypto Conditions IETF standard.

      Security is maintained across all “shards” via notarization.

      Thanks for the comment, everything is verifiable and we will continue testing. If you have any questions please feel free to respond, or join us in the


Leave a Reply

Your email address will not be published. Required fields are marked *