small fixes, github link in footer

This commit is contained in:
Alex Grintsvayg 2018-10-25 14:53:09 -04:00
parent 96bb9aa5fd
commit fe5d91b05e
2 changed files with 17 additions and 6 deletions

View file

@ -308,12 +308,16 @@
<p>If the claim is an update or support to an already active claim, or if it is the first claim for a name, the claim becomes active as soon as it is accepted. Otherwise it becomes active at the block heigh determined by the following formula:</p>
<p><code>C + min(4032, floor((H-T) / 32))</code></p>
<pre><code>C + min(4032, floor((H-T) / 32))
</code></pre>
<p>Where:
- C = claim height (height when the claim was accepted)
- H = current height
- T = takeover height (the most recent height at which the claimtrie state for the name changed)</p>
<p>Where:</p>
<ul>
<li>C = claim height (height when the claim was accepted)</li>
<li>H = current height</li>
<li>T = takeover height (the most recent height at which the claimtrie state for the name changed)</li>
</ul>
<p>In plain English, the delay before a claim becomes active is equal to the claims height minus height of the last takeover, divided by 32. The delay is capped at 4032 blocks, which is 7 days of blocks at 2.5 minutes per block (our target block time). The max delay is reached 224 (7x32) days after the last takeover. The goal of this delay function is to give long-standing claimants time to respond to takeover attempts, while still keeping takeover times reasonable and allowing recent or contentious claims to be taken over quickly.</p>
@ -836,6 +840,8 @@ Talk about how lightning can be used for streaming payments.
<p><em>TODO</em></p>
<p><em>Edit this on Github: <a href="https://github.com/lbryio/spec">https://github.com/lbryio/spec</a></em></p>
<!---
### Supports, Tips

View file

@ -275,9 +275,12 @@ The activation delay depends on the claim operation, the height of the current b
If the claim is an update or support to an already active claim, or if it is the first claim for a name, the claim becomes active as soon as it is accepted. Otherwise it becomes active at the block heigh determined by the following formula:
`C + min(4032, floor((H-T) / 32))`
```
C + min(4032, floor((H-T) / 32))
```
Where:
- C = claim height (height when the claim was accepted)
- H = current height
- T = takeover height (the most recent height at which the claimtrie state for the name changed)
@ -837,6 +840,8 @@ Talk about how lightning can be used for streaming payments.
*TODO*
_Edit this on Github: https://github.com/lbryio/spec_
<!---
### Supports, Tips