Assess finality gadget use of ethereum network data in simulations about cbc-casper HOT 9 CLOSED

@djrtwo already done 😄

from cbc-casper.

Whoops! Sorry @djrtwo somehow I only saw this now!

Pyethereum implements a Casper validator which receives blocks, looks for events in those blocks, and then sends transactions to other validators. Upon receiving transactions from other validators, a validator will create a block with those transactions included. You can take a look at the validator code here: https://github.com/ethereum/pyethereum/blob/develop/ethereum/hybrid_casper/validator.py

Nodes simply add themselves to a network, and then broadcast new blocks & txs

This code is based on the full implementation in Pyethapp which you can check out here: https://github.com/ethereum/pyethapp/blob/develop/pyethapp/eth_service.py#L377-L398

Let me know if you have any questions!

from cbc-casper.

@karlfloersch while I have your attention.. can you add @jonchoi as a collaborator on the repo?

please and thankyou

from cbc-casper.

@karlfloersch Can you point us to this network data y'all used? Vlad said you'd know where to look

from cbc-casper.

Pinging @karlfloersch. Any insight into this?

from cbc-casper.

You the best. Will dig in tomorrow and holler if I need anything.

from cbc-casper.

oh hello! 👋🏼

from cbc-casper.

@karlfloersch Just to be clear.. in the referenced code, when a validator broadcasts a new block/transaction, there is 100% success in propagation? Looks like Network.broadcast ensures that everyone in the network receives, right?

Another way to put it, the casper validator code doesn't simulate cases when messages are propagated in more complex asynchronous ways.

from cbc-casper.

Networking was refactored in PR: #151

Unless we decide to make this simulation very realistic, this is probably enough for our purposes. Closing.

from cbc-casper.