nimbus-eth1
nimbus-eth1 copied to clipboard
status-im
Nimbus: an Ethereum Execution Client for Resource-Restricted Devices
I set the schedule to Cancun. Only need to modify 4 lines of code to move it back to Shanghai if needed. It pass deployment test in `test_eof.nim`. I try...
It would be possible to create automated tests that verify if JSON-RPC APIs are compliant to the JSON-RPC specs. Most (all?) specs are written in / using open-rpc and one...
I've created an issue for that in the nim-lang repo: https://github.com/nim-lang/Nim/issues/22820 Branch under question: https://github.com/status-im/nimbus-eth1/tree/compiler-segfault
The specs listed here is currently for hive and only once hive is green we will move on to client deployment on devnet-9. - [ ] cancun engine api test...
The following program compiles and runs ok. ``` import results, unittest2 type ARef = ref AObj AObj = object of RootObj BRef = ref BObj BObj = object of AObj...
Implementation + benchmarking of PoC for discv5 sub-protocol data transmission in combination with uTP. See also https://github.com/ethereum/devp2p/issues/229
Has Nimbus implemented eip1153? Sometimes before the inclusion we use this schema Shanghai+1153 to tell that 1153 is to be activated on top of Shanghai rules. This is because we...
Although not mentioned in the spec, fetching block bodies should be more complicated than just simply call peer.getBlockBodies(hashes). Upon arrival, those block bodies also need to be filtered by it's...
both rpc and graphql endpoint have method to query sync status. - startBlock - currentBlock - highestBlock currently they are not connected. need #640