-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

..::[ The Bitcoin Foundation: Creating, Naming And Submitting A Vpatch ]::..

    [                   Date: 2017.12.10                               ]
    [                Version: 0.0.4                                    ]
    [                 Author: mod6 [R.01]                              ]

Introduction]:
      With the recent implementation of `V' [R.02] by asciilifeform [R.03] this
      document requires a fourth revision to ensure a consistent methodology for
      creating, naming, and submitting a vpatch.

0x00] Creating the Patch:

      With all of the signed vpatches from The Bitcoin Foundation applied via
      `V', follow these next steps to copy over the `pressed' source so you
      can make the changes for your patch and then output the vpatch of the
      changes with `vdiff.sh' [R.04].

      mkdir -p a b
      cp -pr bitcoin a && cp -pr bitcoin b

      Now that you have the patched source copied into ``a'' and ``b'':

      cd b

      Now you should make your changes to the code as necessary.

      NOTE:  No PGP clearsigned material in vpatches.  Also, no '--- ' or '+++ '
      as the first four characters of any line.  You have been warned! [R.05].

0x01] Naming and Numbering the Vpatch:

      Once the code changes are complete, create a vdiff of the changes:

      vdiff.sh a b > patchname.vpatch

      [ Example ]:
      vdiff.sh a b > mod6_fix_dumpblock_params.vpatch

0x02] Signing the Patch:

      The Bitcoin Foundation requires that you use a PGP Detached Signature to
      sign your vpatch file.

      Sign the vpatch as follows with strict adherence to the nomenclature:

      gpg --armor --output <vpatch_name>.vpatch.<wot_uid>.sig \
      --detach-sig <vpatch_name>.vpatch

      [ Example ]:
      gpg --armor --output mod6_fix_dumpblock_params.vpatch.mod6.sig \
      --detach-sig mod6_fix_dumpblock_params.vpatch

0x03] Submitting the Patch

      To send your patch(s) to the BTC-Dev [R.06] mailing list, first you need
      to create a PGP signed message and then attach your vpatch file(s) and
      your detached signature file(s) to the email.  Also, create a clear-signed
      message detailing vpatch(s) contained in the submission.

      The BTC-dev [R.06] mailing list won't broadcast messages that aren't PGP
      signed with a PGP key in the TMSR~ WoT [R.07].  Your submission must be
      signed with a key that has positive ratings with respect to `deedbot`'s L2
      [R.08].

[ References ]:

  [R.01]: 027A 8D7C 0FB8 A166 4372 0F40 7217 05A8 B71E ADAF
  [R.02]: http://therealbitcoin.org/ml/btc-dev/2015-August/000160.html
  [R.03]: 1721 5D11 8B72 3950 7FAF ED98 B982 28A0 01AB FFC7
  [R.04]: http://deedbot.org/deed-372115-1.txt
  [R.05]: http://btcbase.org/log/2017-12-07#1747850
  [R.06]: http://thebitcoin.foundation/mailman/listinfo/btc-dev
  [R.07]: http://wot.deedbot.org
  [R.08]: http://wot.deedbot.org/29F5BC967632415AB9836DB63E452A7A2A00DEC1.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iQIcBAEBCgAGBQJaLYiHAAoJEHIXBai3Hq2vu6sP/juMpJC9CIz5Ftwr06CjTQem
T4y62cPYaH5jFNUbh4+1gLaL3AM0jUGy6XW+XjQCNUU6ip/X89FSvveo/2DKhrAO
P+jf/RoWocUeocXCaI5gsG077H/5a+zPp02mfoT2+cN3QMIlGxsLsCPjj/oXsXMR
hTYAEYZNpfAq/0gLnylq+I9gUn75+ql8gCwuo4diLctkM7RODvfHfZ3a8qfoiEIX
1QJifIch1xuRU5v1aizwrT2YI9KzvHJhS51eGR8FSgOG4lz/csPZNeVRyaWrR1qo
OGWt3p3G4Ichus7+vusVZcdVjGP/Q0mwW2bsJMFvRCcyUlVYxtdCedhtBeS6ovbK
9acvGZuocRByv+LvxP6HUkux8FEyTBh4jVze1doQl2nadXEALajG3ctsACB8eyIl
R72izcGD9f55b3z3FSVdp9H2PhV4UFBZg77uvLjXk/Jc7Eic6/ST/dJh33LJGnJz
vsG2+zwBj8LO9Wt4zol2uKsVVel19GsKd1oTWyfEfHX1LCuNxopznzVLdTotVeky
gArFSoZygSy300TKnhvHkeJba11JkNL4e33MoLH5l41M4evM6iXTG4NnX5+aaGxk
ZcjZPbnwft0Snmy4db6RVfH+Pu8wocEzs6kIbl8w5NkXLIARHsow8FRhMVZhfKoK
ieSE0Ib9VPtpgMTOPZyb
=YvCk
-----END PGP SIGNATURE-----