mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 09:46:12 +00:00
Fix incorrect usage of 'script' rather than 'scriptPubKey'
This is causing quite a bit of confusion, for example by people looking in the Bitcoin Core sourcecode and seeing the term 'scriptPubKey' instead.
This commit is contained in:
parent
d27cf78449
commit
9183f98bc1
6 changed files with 73 additions and 73 deletions
|
@ -223,7 +223,7 @@ design these minimalist wallets:
|
|||

|
||||
|
||||
* Pre-populate a database with a number of public keys or addresses, and
|
||||
then distribute on request an output script or address using one of
|
||||
then distribute on request an output scriptPubKey or address using one of
|
||||
the database entries. To [avoid key reuse][devguide avoiding key
|
||||
reuse], webservers should keep track
|
||||
of used keys and never run out of public keys. This can be made easier
|
||||
|
@ -357,7 +357,7 @@ a few complications, as the hashed form of an uncompressed key is
|
|||
different than the hashed form of a compressed key, so the same key
|
||||
works with two different P2PKH addresses. This also means that the key
|
||||
must be submitted in the correct format in the input scriptSig so it
|
||||
matches the hash in the previous output script.
|
||||
matches the hash in the previous output scriptPubKey.
|
||||
|
||||
For this reason, Bitcoin Core uses several different identifier bytes to
|
||||
help programs identify how keys should be used:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue