Skip to content
Permalink
Browse files

Update Whitepaper_XEL_Draft_001.md

  • Loading branch information...
tieandsuit committed Jun 16, 2019
1 parent dee7829 commit caa0e0d81e1ac35f112bf114da969f1f23217ec1
Showing with 1 addition and 1 deletion.
  1. +1 −1 Whitepaper_XEL_Draft_001.md
@@ -45,7 +45,7 @@ When a worker finds a bounty solution, they will submit the values used to gener

### 4.3. Working for PoW Solutions

PoW Solutions can be found at almost no additional cost after performing a full evaluation of the scientist’s code while check-ing if a certain pseudo-random input constituted a valid bounty solution. The POW task is simply to perform a MD5 hash of the results of each run of the job’s code and compare that to a PoW target hash set by the network. If the computational node’s run produces a hash less than the target, they are eligible for a POW reward. When a PoW solution is found, the inputs and calculation outputs are submitted, similar to submitting a bounty solution. The network recalculates the PoW target hash once per block with a goal of ten PoW rewards per block (with a maxi-mum of 25 per block) averaged over all currently running jobs. That is, given a block-time of 60 seconds, the network tries to converge towards a state where all jobs, in total, payout ten PoW rewards per minute. Similar to the case outlined above, workers get rewarded the PoW rewards for every PoW submission that the network can positively validate.
PoW Solutions can be found at almost no additional cost after performing a full evaluation of the scientist’s code while check-ing if a certain pseudo-random input constituted a valid bounty solution. The POW task is simply to perform a MD5 hash of the results of each run of the job’s code and compare that to a PoW target hash set by the network. If the computational node’s run produces a hash less than the target, they are eligible for a POW reward. When a PoW solution is found, the inputs and calculation outputs are submitted, similar to submitting a bounty solution. The network recalculates the PoW target hash once per block with a goal of ten PoW rewards per block (with a maximum of 50 per block) averaged over all currently running jobs. That is, given a block-time of 60 seconds, the network tries to converge towards a state where all jobs, in total, payout ten PoW rewards per minute. Similar to the case outlined above, workers get rewarded the PoW rewards for every PoW submission that the network can positively validate.


### 4.4. Validation of Results

0 comments on commit caa0e0d

Please sign in to comment.
You can’t perform that action at this time.