Commit graph

17 commits

Author SHA1 Message Date
David A. Harding
224127f2f0
Merge pulls #824 and #830
* 824: Dev Docs: Update For New 'generate' RPC
* 830: Link "quantum computing" in FAQ to related Bitcoin Magazine article
2015-04-22 17:38:44 -04:00
David A. Harding
a2a5f454cb
Revert "Revert "Merge pull #793: Dev Docs: New Glossary & JS Search Box""
This reverts commit 961d6c988f.
2015-04-14 08:55:53 -04:00
David A. Harding
df2f3a77d0
Dev Docs: Describe New RPC 'generate' In Examples 2015-04-12 20:31:27 -04:00
David A. Harding
961d6c988f
Revert "Merge pull #793: Dev Docs: New Glossary & JS Search Box"
This reverts commit e3dcf0ce1f, reversing
changes made to c71e9fdf2d.

Once again we had a broken new plugin that Travis CI and local building
didn't catch.
2015-04-10 19:33:39 -04:00
David A. Harding
801ea9f4ad
Fix links for new glossary entries 2015-03-19 15:32:09 -04:00
David A. Harding
f368d38e04
Dev Docs: Add "Edit|History|Report Issue|Discuss" Links To Subheads 2014-12-13 17:35:21 -05:00
Saivann
2a139a51a1 Set license files and headers for bitcoin.org's content 2014-11-21 19:09:12 -05:00
David A. Harding
6afc6835bf
Use Terms "Pubkey Script" And "Signature Script"
This modifies commits provided by @petertodd to use the terms "pubkey
script" and "signature script" instead of other terms.

* Rename "scriptPubKey" and "output script" to "pubkey script"
  (suggested by @luke-jr). We leave a token "scriptPubKey" at the point
  where we define pubkey script so that searchers can find it.

* Rename "scriptSig" to "signature script" (suggested by @luke-jr). We
  also leave a token "scriptSig" at this definition point.

* Rename "redeemScript" to "redeem script"

* Defined ECDSA on secp256k1 curve as the crypto used in the Transaction
  section and added references to secp256k1 private/public keys and
  signatures.

* Removed "The Parts Of A Transaction" illustration by commenting it out
  in the HTML. Shoehorning the pubkey/signature script terms into this
  image was becoming difficult, and I'm not very fond of that
  illustration anyway. I'll see if I can think of a nicer replacement
  illustration for some point in the future.

* Add a short paraphrased version @petertodd's description of scripts as
  generalized crypto.

* Updated all the illustrations which referred to either pubkey scripts
  or signature scripts to use these terms.
2014-09-20 15:07:42 -04:00
Saivann
a80ab54f7e Apply various typos and text improvements (thanks @harding!) 2014-06-13 17:40:15 -04:00
Saivann
ffed3c2529 Create a "Testing Applications" subsection in devel-examples
Move existing "regtest / testnet" texts to the new subsection and link to it
Move Bitcoin Core setup instructions in devel-examples
Add a consistent introduction for devel-(guide/ref/examples)
Fix autocrossref.rb to not add links inside {% highlight %} code blocks
2014-06-12 21:42:42 -04:00
Saivann
21bdb0fd1a Apply a warning icon to all warning texts in devel-docs 2014-06-10 23:51:58 -04:00
David A. Harding
85f27095c3
Briefly Reapeat Warning Not To Manually Manage Priv Keys In P2SH Example 2014-06-10 23:36:56 -04:00
David A. Harding
18c2c8dd9f
Add Warning About Handling Private Keys To Transaction Examples 2014-06-10 22:09:48 -04:00
Saivann
0cb0a999f6 Fix various typos or naming inconsistencies 2014-06-08 23:17:04 -04:00
David A. Harding
abf8ac25d6
Add Note About Tx Fees To All Createrawtransaction Example Calls
Based on feedback from @saivann, this may help remind users that poor
use of createrawtransactions can cost them satoshis.
2014-06-08 19:16:09 -04:00
David A. Harding
96bc22b40c
Add Tx Malleability Warning To Spending Unconfirmed Tx Example
Suggested and written by @saivann, with a revised version being
commited here. Thanks!
2014-06-08 18:53:37 -04:00
David A. Harding
d1b4b08729
Add Developer Examples; Transaction Tutorial
* Add new Developer Examples page

* Add a transaction tutorial describing in detail how to make various
  different transactions.

* Add a new "multicode" CSS class to allow combination of consecutive
  code blocks into a single code block. This lets us use pygments
  highlighting for multiple different types of code within the same
  aparent block of code.

* Get autocrossref to ignore code blocks so we don't need to endcrossref
  every time we encounter a code block. This makes the source much more
  readable and maintainable.
2014-05-29 23:19:57 -04:00