Minor Bitcoin to Dash changes

This commit is contained in:
thephez 2018-01-11 12:46:31 -05:00
parent 2c3cf8a85d
commit da8a1f1737
19 changed files with 231 additions and 236 deletions

View file

@ -170,9 +170,9 @@ spent anything so far, except possibly a small transaction fee, and
he'll be able to broadcast the refund transaction in 24 hours for a
full refund.
Now, when Alice does some work worth 1 millibitcoin, she asks Bob to create
Now, when Alice does some work worth 1 millidash, she asks Bob to create
and sign a new version of the refund transaction. Version two of the
transaction spends 1 millibitcoin to Alice and the other 99 back to Bob; it does
transaction spends 1 millidash to Alice and the other 99 back to Bob; it does
not have a locktime, so Alice can sign it and spend it whenever she
wants. (But she doesn't do that immediately.)

View file

@ -288,7 +288,7 @@ Once the syncing node receives the counts and inventories, it may request any
*Governance Sync Data Flow*
| **Syncing Node Message** | **Direction** | **Masternode Response** | **Description** |
| **Inital request** | | | **Requests all governance objects (without votes)** |
| **Initial request** | | | **Requests all governance objects (without votes)** |
| `govsync` message | → | | Syncing node initiates governance sync (hash set to all zeros)
| | ← | `ssc` message (govobj) | Number of governance objects (0 or more)
| | ← | `ssc` message (govobjvote)| Number of governance object votes *(0 since votes are only returned if a specific hash is provided with the `govsync` message)*

View file

@ -506,7 +506,7 @@ Standard transactions must also meet the following conditions:
opcodes which solely push data to the stack.
* The transaction must not include any outputs which receive fewer than
1/3 as many satoshis as it would take to spend it in a typical input.
1/3 as many duffs as it would take to spend it in a typical input.
That's currently 5460 duffs for a
P2PKH or P2SH output on a Dash Core node with the default relay fee.
Exception: standard null data outputs must receive zero duffs.

View file

@ -280,7 +280,7 @@ In order to make copying of private keys less prone to error, [Wallet Import For
1. Take a private key.
2. Add a 0x80 byte in front of it for mainnet addresses or 0xef for testnet addresses.
2. Add a 0xCC byte in front of it for mainnet addresses or 0xEF for testnet addresses.
3. Append a 0x01 byte after it if it should be used with compressed
public keys (described in a later subsection). Nothing is appended if