Hossein

Has anyone thought of implementing a new data structure for mempool to enable parallelization, (To run verify unspent outpoints & tx validation in parallel)?

Only changes the rules in the consensus requires everyone to follow. Almost all the other rules are subject to interpretation. Isn't it?

I mean cauldron can't build an api to order transaction unless they sign every single one of the transactions. Which inherently centralizes the system. A single entity decides...

Currently bch uses the mempool state to prevent double spend for unconfirmed transactions. Are you suggesting it's not doing the job?

Well, If a central authority has control over the flow of transactions, Can we call that system defi. Is it still defi?

I think two things are missing in BCH, 1. Rating System (for rating merchants, apps, developers, etc etc), 2. An app management system for distribution and update of bch apps ...