bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-19 12:08:05 +00:00
Code Issues Releases Wiki Activity

typos

Browse Source
This commit is contained in:
Paul Sztorc 2018-02-10 17:02:33 -05:00
parent 9207df7d05
commit 486505b8fa
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
bip-hashrate-escrows.mediawiki
View File

@ -315,7 +315,7 @@ In fact, M4 can also be *nothing*. In other words, it may be optional. This is p
The following sections assume a maximum of one sucessful withdrawal per sidechain at a time. In other words, as WT^s are proposed, only one can make progress toward the finish line. As a result, a given side-to-main transfer will always take between 3 and 6 months. If there were more simulataneous withdrawals, the worst-case transfer duration would improve.
<img src="bip-hasrate-escrows/two-groups.png?raw=true" align="middle"></img>
<img src="bip-hashrate-escrows/two-groups.png?raw=true" align="middle"></img>
The worst-case withdrawal time obeys f(n)=3+(3/n) months, where n is the number of simultaneous withdrawals.
@ -453,12 +453,12 @@ As a soft fork, older software will continue to operate without modification. No
This BIP will be deployed by "version bits" BIP9 with the name "hrescrow" and using bit 4.
```
<pre>
// Deployment of Drivechains (BIPX, BIPY)
consensus.vDeployments[Consensus::DEPLOYMENT_DRIVECHAINS].bit = 4;
consensus.vDeployments[Consensus::DEPLOYMENT_DRIVECHAINS].nStartTime = 1515974401; // January 15th, 2018.
consensus.vDeployments[Consensus::DEPLOYMENT_DRIVECHAINS].nTimeout = 1547510401; // January 15th, 2019.
```
</pre>
==Reference Implementation==