Super-Genius
commented
2 months ago This is switched to an easier ZKSnark Proof generation, then each full node will accept or reject based on the verification of the proof system.
Open henriqueaklein opened 6 months ago
Super-Genius
commented
2 months ago This is switched to an easier ZKSnark Proof generation, then each full node will accept or reject based on the verification of the proof system.
The blockchain consensus was never integrated with CRDT and only worked on the previous implementation.
Blockchain is already integrated on CRDT, however transactions are directly posted on the blockchain, instead of going through transaction pool and then recorded on the blockchain through consensus.
So the transaction manager will need to stop posting directly on the blockchain and instead feed into the transaction pool and there's gonna have to be a thread running consensus to record the next set of transactions to the blockchain (I think)
- Integrate the block_tree code. This was removed because it relied on runtime/binaryen stuff which was stripped a while ago.- Integrate the transaction pool. Also removed due to runtime/binaryen dependencies.- Check how the consensus would work. It's supposed to be hashgraph consensus algorithm