Gav Wood
11 years ago
5 changed files with 26 additions and 109 deletions
@ -1,99 +0,0 @@ |
|||
### UP FOR GRABS |
|||
|
|||
For PoC-4: |
|||
|
|||
GUI |
|||
- Make address/block chain list model-based, JIT populated. |
|||
- Make everything else model-based |
|||
- Qt/QML class. |
|||
|
|||
Core |
|||
- Signalling for changes to State. |
|||
|
|||
THREAD-SAFETY |
|||
- BlockChain |
|||
- TransactionQueue |
|||
- State |
|||
|
|||
Robustness |
|||
- Store version alongside BC DB. Kill old DBs when protocol different. Remove block chain on protocol change (i.e. store protocol with block chain). |
|||
|
|||
Cleanups & caching |
|||
- All caches should flush unused data (I'm looking at you, BlockChain) to avoid memory overload. |
|||
|
|||
|
|||
Generally: |
|||
|
|||
Crypto stuff: |
|||
- kFromMessage |
|||
- Check all the tweak instructions. |
|||
|
|||
Network: |
|||
- *** Exponential backoff on bad connection. |
|||
- *** Handle exception when no network. |
|||
- NotInChain will be very bad for new peers - it'll run through until the genesis. |
|||
- Check how many it has first. |
|||
- Crypto on network - use id as public key? |
|||
- Make work with IPv6 |
|||
- Peers rated. |
|||
- Useful/useless - new blocks/transactions or useful peers? |
|||
- Solid communications? |
|||
- Strategy for peer suggestion? |
|||
- Ignore transactions with future nonces until address's nonce changes. |
|||
|
|||
Cleanups & caching |
|||
- State DB should keep only last few N blocks worth of nodes (except for restore points - configurable, defaults to every 30000th block - all blocks that are restore points should be stored so their stateRoots are known good). |
|||
|
|||
General: |
|||
- Better logging. |
|||
- Colours. |
|||
- Move over to new system. |
|||
|
|||
Robustness |
|||
- Remove aborts |
|||
- Recover from all exceptions. |
|||
- Especially RLP & other I/O. |
|||
- RLP should never assert; only throw. |
|||
- Better handling of corrupt blocks. |
|||
- Kill DB & restart. |
|||
|
|||
GUI: |
|||
- Turn on/off debug channels. |
|||
|
|||
|
|||
### Marko |
|||
|
|||
Ubuntu builds |
|||
- Raring (branch, local, x64 only :-( ) |
|||
- Quantal (branch) (Launchpad) |
|||
- Saucy (master) (Launchpad) |
|||
|
|||
### Alex |
|||
|
|||
Mac build. |
|||
Mac build instructions. |
|||
|
|||
### Eric |
|||
|
|||
Windows XC build. |
|||
Windows XC build instructions. |
|||
|
|||
### Tim/Harv |
|||
|
|||
Windows MSVC build. |
|||
Windows MSVC build instructions. |
|||
|
|||
LATER: |
|||
|
|||
Trie on DB. |
|||
- Move the restore point stuff into block restore points |
|||
- i.e. keep all nodes from last 127 blocks with counter, at 128, kill but keep every (60*24*7)th or so i.e. one per week as a restore point. |
|||
- maybe allow this to be configured. |
|||
|
|||
|
|||
### TIM |
|||
|
|||
Stateful Miner class. |
|||
|
|||
Better Mod-Exp. |
|||
|
Loading…
Reference in new issue