dave/bft-crdt-experiment
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added a note about commit-reveal

Browse Source
This commit is contained in:
Dave Hrycyszyn
2024-07-17 13:18:17 +01:00
parent f6db54ac34
commit 4cf3d03349
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -51,7 +51,7 @@ Next dev tasks:
- [ ] we don't need a Watcher, the first node can act as a leader until people decide they don't want to trust it any more - [ ] we don't need a Watcher, the first node can act as a leader until people decide they don't want to trust it any more
- [ ] the leader node can have a timer in it for block creation - [ ] the leader node can have a timer in it for block creation
- [ ] code up the ability to switch leaders (can be a human decision at first, later an (optional) automated choice) - [ ] code up the ability to switch leaders (can be a human decision at first, later an (optional) automated choice)
- [ ] pick a commit and reveal scheme to remove MEV - [ ] pick a commit and reveal scheme to remove MEV. One thing to investigate is [single-use seals](https://docs.rgb.info/distributed-computing-concepts/single-use-seals)
- [ ] enable Side Nodes to download current P2P chain state so that they start - out with a consistent copy of transaction data, and also do catch-up after going off-line - [ ] enable Side Nodes to download current P2P chain state so that they start - out with a consistent copy of transaction data, and also do catch-up after going off-line
- [ ] remove the proc macro code from bft-json-crdt - [ ] remove the proc macro code from bft-json-crdt
- [ ] add smart contract execution engine (CosmWasm would be a good first choice) - [ ] add smart contract execution engine (CosmWasm would be a good first choice)