Application-Specific Parallel Chains

The rules that define a parallel chain can imply adding privacy features or even trading decentralization & security for more throughput. There is a scope for experimenting here and trade-offs can be considered to produce the optimal performance, based on the needs of the particular application.

Also, as compared to financial applications the incentives are lesser in the case of data-driven applications. It may be worth it for an exploiter to spend hundreds of millions of dollars to attack 51% of a financial blockchain and reverse a payment, but it probably doesn’t make any sense for them to reverse a tweet on a blockchain-based microblogging platform. Because of this, applications need to optimize for performance and be able to choose more flexible threat modelling.

There is a huge need for disruptive applications that provide high performance, are censorship-resistant, and are transparent.

With that in mind, in an X (previously Twitter) – like Decentralized Application running on a blockchain, adjustable security can enable higher throughput while submitting “checkpoints” to the main chain in order to declare the finality of the data so far.