dash-docs/en/developer-reference.md
David A. Harding 1634212dd5
Dev Docs: Add P2P Messages That Request Or Reply With Data
Adds to the devel reference page detailed documentation on the following
messages: block, getblocks, getdata, getheaders, headers, inv, mempool,
merkleblock, notfound, and tx.

Adds to the devel examples page an example of requesting and parsing a
merkleblock message.

Adds to the devel docs overview pages links to the above two new
P2P sections.

Tweaks the autocrossref plugin ignore pattern to not crossref in the
middle of a GIF image name; this allows the inclusion of animated GIFs.
2014-11-12 12:39:36 -05:00

1.8 KiB

layout lang id title
base en developer-reference Developer Reference - Bitcoin

Bitcoin Developer Reference

Find technical specifications and API documentation.

  • Table of contents {:toc}

{% include fragment_reviews_needed.md %}

{% include ref_intro.md %}

{% include ref_block_chain.md %}

{% include ref_transactions.md %}

{% include ref_wallets.md %}

{% include ref_p2p_networking.md %}

Bitcoin Core APIs

{% include ref_core_rpc_intro.md %}

Remote Procedure Calls (RPCs)

Warning: the block chain and memory pool can include arbitrary data which several of the commands below will return in hex format. If you convert this data to another format in an executable context, it could be used in an exploit. For example, displaying an output script as ASCII text in a webpage could add arbitrary Javascript to that page and create a cross-site scripting (XSS) exploit. To avoid problems, please treat block chain and memory pool data as an arbitrary input from an untrusted source.

{% include ref_core_rpcs-abcdefg.md %} {% include ref_core_rpcs-hijklmn.md %} {% include ref_core_rpcs-opqrst.md %} {% include ref_core_rpcs-uvwxyz.md %} {% include references.md %}