a5e377f42a
Update ch01.asciidoc
4 years ago
a127847dc2
Update ch01.asciidoc
4 years ago
5eaf59a8fe
Update ch01.asciidoc
4 years ago
2da8710372
Update ch01.asciidoc
4 years ago
b0ad3150fd
Update ch01.asciidoc
4 years ago
4dcaf5b1f8
ch10: stale block -> fix text, update diagrams & subtitle
4 years ago
6635f27e85
Update ch01.asciidoc
4 years ago
be941d5585
Update ch01.asciidoc
4 years ago
3c819ec440
Update ch01.asciidoc
4 years ago
dc9733339c
Update ch01.asciidoc
4 years ago
5a562bfb74
Add files via upload
4 years ago
0cb81479af
Update ch01.asciidoc
4 years ago
a344ffb053
Update ch05.asciidoc
...
Replacing mycelium with Bluewallet.
4 years ago
778f50fd8a
Update ch06.asciidoc
...
A quick note that scriptsig is just one type of unlocking script - adheres to chapters main intent of using "unlocking/locking script" more broadly.
4 years ago
e6e0b43d4c
Update ch06.asciidoc
4 years ago
911d4a073e
Update ch06.asciidoc
4 years ago
a3ce7114be
Update ch06.asciidoc
4 years ago
17ff33257e
Added ScriptSig table for completeness
...
The public key was lost in this chapter when dissecting the transaction in whole. For completeness, a table demonstrating a breakdown of the ScriptSig was necessary to cover this.
4 years ago
39d663ed30
ch04: Fix 'key-to-address-ecc-example'
...
The 'pybitcointools' library is deprecated. Vitalik mentions using the
fork from 'primal100'. This updates the code sample which is currently
broken, to use the Python package for that fork.
Runs all good now.
4 years ago
de68a97638
ch03: s/archieved fork/archived fork of/
4 years ago
ea93a3da15
Merge pull request #850 from rating89us/patch-56
...
ch10: equal to or lower than the bitcoin network's target
4 years ago
db0f37b731
Merge pull request #851 from rating89us/patch-58
...
ch10: changes to the analogy of a dice game
4 years ago
947f18ca69
Merge pull request #852 from rating89us/patch-59
...
ch10: add hard/soft forks to tip
4 years ago
99a0114ad5
Merge pull request #853 from rating89us/patch-60
...
ch10: candidate blocks -> winning/valid blocks; some other fixes
4 years ago
b5e2f83eeb
Merge pull request #855 from rating89us/patch-61
...
ch10: fixing diagrams and text of blockchain fork event
4 years ago
801eb92661
Merge pull request #859 from rating89us/patch-62
...
ch10: coinbase -> coinbase data
4 years ago
e1e7e256d7
Merge pull request #860 from rating89us/patch-63
...
appdx-bitcoinwhitepaper: and -> which
4 years ago
e5595689be
Merge pull request #861 from rating89us/patch-64
...
glossary: block/coinbase/mining reward; coinbase data; halving
4 years ago
ea20a9a312
Merge branch 'develop' into patch-64
4 years ago
f15be3a63e
Merge pull request #862 from rating89us/patch-65
...
ch10: add candidate block; edit stale block
4 years ago
666b304900
ch10: add candidate block; edit stale block
4 years ago
c1e03f85ed
glossary: block reward, coinbase reward, mining reward
4 years ago
635d9ae2b0
appdx-bitcoinwhitepaper: and -> which
4 years ago
7bc0385c3a
ch10: coinbase -> coinbase data
4 years ago
e6a534e9c8
ch10: fixing diagrams and text of blockchain fork event
4 years ago
dc2ec6a072
ch10: candidate blocks -> winning/valid blocks; some other fixes
4 years ago
b1d987ee51
ch10: add hard/soft forks to tip
4 years ago
0a62adef85
ch01: Update market cap and largest transaction to date
4 years ago
5b0ab20667
ch10: changes to the analogy of a dice game
4 years ago
a24e87f0ba
github_contrib: Add new contributors
4 years ago
6edcea1ece
ch10: equal to or lower than the bitcoin network's target
4 years ago
f681618620
Merge pull request #848 from rating89us/patch-54
...
ch10: block reward decreases over time
4 years ago
f4cba4e09e
Merge pull request #843 from rating89us/patch-53
...
ch10: also known as block reward or coinbase reward
4 years ago
a9a5ed38a9
Update ch07.asciidoc
...
refactored text to create sizeable tip box; fixed typos
4 years ago
73c3af32c3
Update ch07.asciidoc
...
Elaborated a bit more on IsStandard() function and provided clarity to the examples written above.
Reference: ed25cb58f6/src/policy/policy.cpp (L53)
4 years ago
d2a386cf7f
Update ch07.asciidoc
...
Aim is to clarify the current restrictions of standard multisig vs. P2SH. The aim is to further clarify why a transaction would be invalid, in each perspective. On a technical note, saying that it 'invalidates the transaction' may not be correct, but my current understanding is that a 2 of 5 multisig transaction would enter the mempool but then become invalid by nodes.
On the other hand, nodes wouldn't have a way to tell if a P2SH hash has within it 15 public keys as it is just a hash; therefore, the only way to tell is to analyze unlocking script of a transaction in input, unless the basis for 15 public keys is a size restriction? Thank you
4 years ago
5fb752cf6e
ch10: block reward decreases over time
4 years ago
58d1407fc9
ch10: also known as a block reward or coinbase reward
4 years ago
3e6ae4aaee
Update ch07.asciidoc
...
Updated the P2SH unlocking script to state that just signatures are required to satisfy unlocking conditions, as depicted by the examples.
4 years ago
9745ca5887
Merge pull request #844 from rating89us/patch-54
...
ch10: block reward decreases over time
4 years ago
krupawan5618