mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-22 03:30:35 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

rename sharding proposer cli entrypoint, add travis

Browse Source 
Former-commit-id: 9ef2e52fa98e4451baf611135740c82aeb52c092 [formerly 8623b637d7c8b4cb414329dcd753e322f79bf31d]
Former-commit-id: 6305062eeaf7074ef75d779bd69f4a1c7ae8999e
This commit is contained in:
Raul Jordan 2018-03-05 21:25:34 -06:00
parent a9548320d5
commit c9cfb23312
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -109,9 +109,9 @@ This will extract 100ETH from your account balance and insert you into the VMC's
## Becoming a Proposer
The proposer node can be started with the following command:
The proposer node (collator) can be started with the following command:
geth sharding-proposer --password /path/to/your/password.txt
geth sharding-collation --password /path/to/your/password.txt
Proposers are tasked with state execution, so they will process and validate pending transactions in the Geth node and create collations with headers that are then broadcast to a proposals pool along with an ETH deposit.

6
sharding/README.md
View File

@ -190,9 +190,9 @@ If it is the first time the client runs, it will deploy a new **VMC** into the l
If the initial deposit is successful, the sharding client will launch a **local, transaction simulation generator**, which will queue transactions into the txpool for the geth node to process that can then be added into collations on a shard.
Concurrently, a user will need to launch a **proposer client** that will start processing transactions into collations that can then be “sold” to validators by including a cryptographic proof of an eth deposit in their unsign collation headers. This proof is a guarantee of a state change in the validator’s account balance for accepting to sign the incoming collation header. The proposer client can also be initialized as follows in a separate process:
Concurrently, a user will need to launch a **proposer client** that will start processing transactions into collations that can then be “sold” to validators by including a cryptographic proof of an eth deposit in their unsign collation headers. This proof is a guarantee of a state change in the validator’s account balance for accepting to sign the incoming collation header. The proposer client (also known as a collator) can also be initialized as follows in a separate process:
geth sharding-proposer --password ~/Desktop/password.txt
geth sharding-collator --password ~/Desktop/password.txt
Back to the validators, the validator client will begin its main loop, which involves the following steps:
@ -339,7 +339,7 @@ In addition to launching a validator client, our system will require a user to c
Users will launch a proposal client as another geth entrypoint as follows:
geth sharding-proposer --password ~/Desktop/password.txt
geth sharding-collator --password ~/Desktop/password.txt
Launching this command will connect via JSON-RPC to fetch the geth node’s tx pool and see who the currently active validator node is for the period. The proposer is tasked with running transactions to create valid collations and executing their required computations, tracking used gas, and all the heavy lifting that is usually seen in full Ethereum nodes. Once a valid collation is created, the proposer broadcasts the unsigned header **(note: the body is not broadcasted)** to a proposals pool along with a guaranteed ETH deposit that is extracted from the proposer’s account upfront. Then, the current validator assigned for the period will find proposals for her/her assigned shard and sign the one with the highest payout.