Skip to content

Instantly share code, notes, and snippets.

View dexX7's full-sized avatar

dexX7

View GitHub Profile
@dexX7
dexX7 / gist:9ff9844ab4741568e26e
Last active January 14, 2016 17:56 — forked from achamely/Omnicore cli raw tx creation
Manual omni tx creation tests
source: "34UsEfJjU4pBwWVvSnqdKE6o6gvp3WS1gE"
reference: "12wSMSUQRVH1qKxUJF2V5S2jDXaU57gKPv"
reference pubkey: "0216e22d5e07b43a7402dcef62a9cb1dd25d7b201655799e19f0713c45d251ff97"
Property Id: 31
Amount: 298.59
payload : 000000000000000100000006f3bc2ec0
UTXO:
[{
@dexX7
dexX7 / API.md
Last active September 11, 2015 21:39 — forked from iros/API.md
Documenting your REST API

Title

<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>

  • URL

    <The URL Structure (path only, no root url)>

  • Method:

SPV clients lack the ability of full nodes to detect whether or not a chain provided to them by another source complies with the rules of the Bitcoin protocol.

SPV clients can connect to multiple full nodes in the hope that at least one of the nodes is honest and will provide them with the best valid chain, however situations may arise where the non-compliant chain contains more proof of work than the compliant chain. In this situation, there is no way for the honest full node to signal to an SPV client that it should disregard the chain with more proof of work.

Fraud proofs are a technique which provide honest full nodes the capability to conclusively demonstrate that chain is invalid regardless of the amount of proof of work backing the invalid chain.

If Bitcoin nodes implement the ability to create, propagate, and verify fraud proofs, the security of SPV clients will be improved.

Assumptions and Definitions