[DRAFT] Motion to verify new hashes for 5 previous motions

CoinGame · March 2, 2016, 4:51pm

During the process of verifying text and hashes to produce the base for NuLaws I found myself unable to calculate the hashes for 5 previous motions.

@Cybnate suggested we create new hashes using the previous text and move forward with that. So the idea here is to put all of the previous motions into a new file with their content, old hash, and new hash. Then vote on one motion to validate the new hashes for those previous motions.

This would effectively bind references from the old hashes to the new hashes. I produced the new hashes from the raw links you can see at the top of the gist. My thought was to make the motion a hash of the JSON file below. It will contain the motion text describing the changes with necessary text.

Thoughts?

gist.github.com

https://gist.github.com/CoinGame/efe3ca434498b88c98d9

Hashes raw URL's

[Raw motion to open source code](https://discuss.nubits.com/raw/1083)
[Raw motion to begin NSR buyback immediately](https://discuss.nubits.com/raw/2654)
[Raw motion to change dividend period 001 of Kiara Tamm’s liquidity grant proposal](https://discuss.nubits.com/raw/624)
[Raw motion to modify terms of custodain grant](https://discuss.nubits.com/raw/1226)
[Raw motion to adjust the dividend distribution structure of custodian grant](https://discuss.nubits.com/raw/1096)

motions.json

{
  "0": "Here is where the motion text defining the purpose of this document will go",
  "1": {
    "title": "Motion to open source code",
    "old-hash": "6f361693a7b248730b41d4292f89dc6f6f166bc8",
    "new-hash": "6235a2aa0f6fd09a8f205e0a369ce2de3793c5a1",
    "hash-content": "With the successful passage of this motion, the Nu Shareholders[1] (\"Shareholders\") have instructed the Nu Development Team[2] (\"Developers\") to make the Nu source code available to the general public. The updated license will allow free, permissive use of the source code in Nu-related and derivative projects.\n\nThe Nu source code (including the code that describes the underlying Nu network protocol, the daemons, the GUIs, and the associated support systems for testing, distribution, and deployment) will include a text file, COPYING, in the root directory of the project.\n\n>Copyright (c) {YEAR[3]} Nu Developers\nCopyright (c) 2013-2014 Peershares Developers\nCopyright (c) 2011-2014 Peercoin (PPCoin) Developers\nCopyright (c) 2009-2012 Bitcoin Developers\n\n>Permission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\n>The above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\n>THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n\nExisting copyrights held by outside persons or organizations for code integrated into, or adapted for use within Nu, will be retained within the source code as required by their respective licenses. The license text follows the model established by Bitcoin[4] (and then continued by the Peercoin[5] and Peershares[6] software forks).\n\nAdditionally, the Shareholders grant the Developers the ability to determine a location for the code repository (BitBucket, Github, etc.) where the source code will be available to view and download. The Developers will act in the best interests of Shareholders when selecting the person(s) granted permissions to review, approve, and merge proposed modifications to the Nu source code.\n\nFinally, the Shareholders grant the Developers discretion when determining which features, submitted to the project's code repository from individual contributors by way of \"pull requests,\" are merged into the Nu source code. Members of the Nu Community at-large are all empowered to introduce motions to identify the \"roadmap\" that core development will follow.\n\nOnce this motion has been passed, the Developers will have forty-five (45) days to inform Shareholders of the steps required to open the Nu source code to the public, and to take those steps. The final action required by the passage of this motion will be to release a new version of the Nu clients (daemon and GUI, for Windows, OS X, and Linux) that includes the updated software license. This release will be tagged \"v1.0.0\" within the version control system. After meeting the requirements, this motion's purpose is complete, with no further action required by the Shareholders or the Developers.\n\n.....\n\n[1] \"Nu Shareholders\" are persons with legitimate access to enough NSR to cast a vote for this motion by minting a valid Nu block.\n\n[2] \"Nu Development Team\" are the person(s) ultimately responsible for software development of the Nu network, and who have unrestricted access to Nu source code when this motion passes.\n\n[3] The date of the copyright listed in COPYING will match the year that this motion is passed, and will be back-dated to 2014 if needed. For example, 'Copyright (c) 2014-2015 Nu Developers' if the motion passes this year, or 'Copyright (c) 2014-2016 Nu Developers' if the motion does not pass until 2016.\n\n[4] https://github.com/bitcoin/bitcoin/blob/master/COPYING\n\n[5] https://github.com/ppcoin/ppcoin/blob/master/COPYING\n\n[6] https://github.com/Peershares/Peershares/blob/master/COPYING\n    ",
    "content-b64": "V2l0aCB0aGUgc3VjY2Vzc2Z1bCBwYXNzYWdlIG9mIHRoaXMgbW90aW9uLCB0aGUgTnUgU2hhcmVob2xkZXJzWzFdICgiU2hhcmVob2xkZXJzIikgaGF2ZSBpbnN0cnVjdGVkIHRoZSBOdSBEZXZlbG9wbWVudCBUZWFtWzJdICgiRGV2ZWxvcGVycyIpIHRvIG1ha2UgdGhlIE51IHNvdXJjZSBjb2RlIGF2YWlsYWJsZSB0byB0aGUgZ2VuZXJhbCBwdWJsaWMuIFRoZSB1cGRhdGVkIGxpY2Vuc2Ugd2lsbCBhbGxvdyBmcmVlLCBwZXJtaXNzaXZlIHVzZSBvZiB0aGUgc291cmNlIGNvZGUgaW4gTnUtcmVsYXRlZCBhbmQgZGVyaXZhdGl2ZSBwcm9qZWN0cy4NCg0KVGhlIE51IHNvdXJjZSBjb2RlIChpbmNsdWRpbmcgdGhlIGNvZGUgdGhhdCBkZXNjcmliZXMgdGhlIHVuZGVybHlpbmcgTnUgbmV0d29yayBwcm90b2NvbCwgdGhlIGRhZW1vbnMsIHRoZSBHVUlzLCBhbmQgdGhlIGFzc29jaWF0ZWQgc3VwcG9ydCBzeXN0ZW1zIGZvciB0ZXN0aW5nLCBkaXN0cmlidXRpb24sIGFuZCBkZXBsb3ltZW50KSB3aWxsIGluY2x1ZGUgYSB0ZXh0IGZpbGUsIENPUFlJTkcsIGluIHRoZSByb290IGRpcmVjdG9yeSBvZiB0aGUgcHJvamVjdC4NCg0KPkNvcHlyaWdodCAoYykge1lFQVJbM119IE51IERldmVsb3BlcnMNCkNvcHlyaWdodCAoYykgMjAxMy0yMDE0IFBlZXJzaGFyZXMgRGV2ZWxvcGVycw0KQ29weXJpZ2h0IChjKSAyMDExLTIwMTQgUGVlcmNvaW4gKFBQQ29pbikgRGV2ZWxvcGVycw0KQ29weXJpZ2h0IChjKSAyMDA5LTIwMTIgQml0Y29pbiBEZXZlbG9wZXJzDQoNCj5QZXJtaXNzaW9uIGlzIGhlcmVieSBncmFudGVkLCBmcmVlIG9mIGNoYXJnZSwgdG8gYW55IHBlcnNvbiBvYnRhaW5pbmcgYSBjb3B5DQpvZiB0aGlzIHNvZnR3YXJlIGFuZCBhc3NvY2lhdGVkIGRvY3VtZW50YXRpb24gZmlsZXMgKHRoZSAiU29mdHdhcmUiKSwgdG8gZGVhbA0KaW4gdGhlIFNvZnR3YXJlIHdpdGhvdXQgcmVzdHJpY3Rpb24sIGluY2x1ZGluZyB3aXRob3V0IGxpbWl0YXRpb24gdGhlIHJpZ2h0cw0KdG8gdXNlLCBjb3B5LCBtb2RpZnksIG1lcmdlLCBwdWJsaXNoLCBkaXN0cmlidXRlLCBzdWJsaWNlbnNlLCBhbmQvb3Igc2VsbA0KY29waWVzIG9mIHRoZSBTb2Z0d2FyZSwgYW5kIHRvIHBlcm1pdCBwZXJzb25zIHRvIHdob20gdGhlIFNvZnR3YXJlIGlzDQpmdXJuaXNoZWQgdG8gZG8gc28sIHN1YmplY3QgdG8gdGhlIGZvbGxvd2luZyBjb25kaXRpb25zOg0KDQo+VGhlIGFib3ZlIGNvcHlyaWdodCBub3RpY2UgYW5kIHRoaXMgcGVybWlzc2lvbiBub3RpY2Ugc2hhbGwgYmUgaW5jbHVkZWQgaW4NCmFsbCBjb3BpZXMgb3Igc3Vic3RhbnRpYWwgcG9ydGlvbnMgb2YgdGhlIFNvZnR3YXJlLg0KDQo+VEhFIFNPRlRXQVJFIElTIFBST1ZJREVEICJBUyBJUyIsIFdJVEhPVVQgV0FSUkFOVFkgT0YgQU5ZIEtJTkQsIEVYUFJFU1MgT1INCklNUExJRUQsIElOQ0xVRElORyBCVVQgTk9UIExJTUlURUQgVE8gVEhFIFdBUlJBTlRJRVMgT0YgTUVSQ0hBTlRBQklMSVRZLA0KRklUTkVTUyBGT1IgQSBQQVJUSUNVTEFSIFBVUlBPU0UgQU5EIE5PTklORlJJTkdFTUVOVC4gSU4gTk8gRVZFTlQgU0hBTEwgVEhFDQpBVVRIT1JTIE9SIENPUFlSSUdIVCBIT0xERVJTIEJFIExJQUJMRSBGT1IgQU5ZIENMQUlNLCBEQU1BR0VTIE9SIE9USEVSDQpMSUFCSUxJVFksIFdIRVRIRVIgSU4gQU4gQUNUSU9OIE9GIENPTlRSQUNULCBUT1JUIE9SIE9USEVSV0lTRSwgQVJJU0lORyBGUk9NLA0KT1VUIE9GIE9SIElOIENPTk5FQ1RJT04gV0lUSCBUSEUgU09GVFdBUkUgT1IgVEhFIFVTRSBPUiBPVEhFUiBERUFMSU5HUyBJTg0KVEhFIFNPRlRXQVJFLg0KDQpFeGlzdGluZyBjb3B5cmlnaHRzIGhlbGQgYnkgb3V0c2lkZSBwZXJzb25zIG9yIG9yZ2FuaXphdGlvbnMgZm9yIGNvZGUgaW50ZWdyYXRlZCBpbnRvLCBvciBhZGFwdGVkIGZvciB1c2Ugd2l0aGluIE51LCB3aWxsIGJlIHJldGFpbmVkIHdpdGhpbiB0aGUgc291cmNlIGNvZGUgYXMgcmVxdWlyZWQgYnkgdGhlaXIgcmVzcGVjdGl2ZSBsaWNlbnNlcy4gVGhlIGxpY2Vuc2UgdGV4dCBmb2xsb3dzIHRoZSBtb2RlbCBlc3RhYmxpc2hlZCBieSBCaXRjb2luWzRdIChhbmQgdGhlbiBjb250aW51ZWQgYnkgdGhlIFBlZXJjb2luWzVdIGFuZCBQZWVyc2hhcmVzWzZdIHNvZnR3YXJlIGZvcmtzKS4NCg0KQWRkaXRpb25hbGx5LCB0aGUgU2hhcmVob2xkZXJzIGdyYW50IHRoZSBEZXZlbG9wZXJzIHRoZSBhYmlsaXR5IHRvIGRldGVybWluZSBhIGxvY2F0aW9uIGZvciB0aGUgY29kZSByZXBvc2l0b3J5IChCaXRCdWNrZXQsIEdpdGh1YiwgZXRjLikgd2hlcmUgdGhlIHNvdXJjZSBjb2RlIHdpbGwgYmUgYXZhaWxhYmxlIHRvIHZpZXcgYW5kIGRvd25sb2FkLiBUaGUgRGV2ZWxvcGVycyB3aWxsIGFjdCBpbiB0aGUgYmVzdCBpbnRlcmVzdHMgb2YgU2hhcmVob2xkZXJzIHdoZW4gc2VsZWN0aW5nIHRoZSBwZXJzb24ocykgZ3JhbnRlZCBwZXJtaXNzaW9ucyB0byByZXZpZXcsIGFwcHJvdmUsIGFuZCBtZXJnZSBwcm9wb3NlZCBtb2RpZmljYXRpb25zIHRvIHRoZSBOdSBzb3VyY2UgY29kZS4NCg0KRmluYWxseSwgdGhlIFNoYXJlaG9sZGVycyBncmFudCB0aGUgRGV2ZWxvcGVycyBkaXNjcmV0aW9uIHdoZW4gZGV0ZXJtaW5pbmcgd2hpY2ggZmVhdHVyZXMsIHN1Ym1pdHRlZCB0byB0aGUgcHJvamVjdCdzIGNvZGUgcmVwb3NpdG9yeSBmcm9tIGluZGl2aWR1YWwgY29udHJpYnV0b3JzIGJ5IHdheSBvZiAicHVsbCByZXF1ZXN0cywiIGFyZSBtZXJnZWQgaW50byB0aGUgTnUgc291cmNlIGNvZGUuIE1lbWJlcnMgb2YgdGhlIE51IENvbW11bml0eSBhdC1sYXJnZSBhcmUgYWxsIGVtcG93ZXJlZCB0byBpbnRyb2R1Y2UgbW90aW9ucyB0byBpZGVudGlmeSB0aGUgInJvYWRtYXAiIHRoYXQgY29yZSBkZXZlbG9wbWVudCB3aWxsIGZvbGxvdy4NCg0KT25jZSB0aGlzIG1vdGlvbiBoYXMgYmVlbiBwYXNzZWQsIHRoZSBEZXZlbG9wZXJzIHdpbGwgaGF2ZSBmb3J0eS1maXZlICg0NSkgZGF5cyB0byBpbmZvcm0gU2hhcmVob2xkZXJzIG9mIHRoZSBzdGVwcyByZXF1aXJlZCB0byBvcGVuIHRoZSBOdSBzb3VyY2UgY29kZSB0byB0aGUgcHVibGljLCBhbmQgdG8gdGFrZSB0aG9zZSBzdGVwcy4gVGhlIGZpbmFsIGFjdGlvbiByZXF1aXJlZCBieSB0aGUgcGFzc2FnZSBvZiB0aGlzIG1vdGlvbiB3aWxsIGJlIHRvIHJlbGVhc2UgYSBuZXcgdmVyc2lvbiBvZiB0aGUgTnUgY2xpZW50cyAoZGFlbW9uIGFuZCBHVUksIGZvciBXaW5kb3dzLCBPUyBYLCBhbmQgTGludXgpIHRoYXQgaW5jbHVkZXMgdGhlIHVwZGF0ZWQgc29mdHdhcmUgbGljZW5zZS4gVGhpcyByZWxlYXNlIHdpbGwgYmUgdGFnZ2VkICJ2MS4wLjAiIHdpdGhpbiB0aGUgdmVyc2lvbiBjb250cm9sIHN5c3RlbS4gQWZ0ZXIgbWVldGluZyB0aGUgcmVxdWlyZW1lbnRzLCB0aGlzIG1vdGlvbidzIHB1cnBvc2UgaXMgY29tcGxldGUsIHdpdGggbm8gZnVydGhlciBhY3Rpb24gcmVxdWlyZWQgYnkgdGhlIFNoYXJlaG9sZGVycyBvciB0aGUgRGV2ZWxvcGVycy4NCg0KLi4uLi4NCg0KWzFdICJOdSBTaGFyZWhvbGRlcnMiIGFyZSBwZXJzb25zIHdpdGggbGVnaXRpbWF0ZSBhY2Nlc3MgdG8gZW5vdWdoIE5TUiB0byBjYXN0IGEgdm90ZSBmb3IgdGhpcyBtb3Rpb24gYnkgbWludGluZyBhIHZhbGlkIE51IGJsb2NrLg0KDQpbMl0gIk51IERldmVsb3BtZW50IFRlYW0iIGFyZSB0aGUgcGVyc29uKHMpIHVsdGltYXRlbHkgcmVzcG9uc2libGUgZm9yIHNvZnR3YXJlIGRldmVsb3BtZW50IG9mIHRoZSBOdSBuZXR3b3JrLCBhbmQgd2hvIGhhdmUgdW5yZXN0cmljdGVkIGFjY2VzcyB0byBOdSBzb3VyY2UgY29kZSB3aGVuIHRoaXMgbW90aW9uIHBhc3Nlcy4NCg0KWzNdIFRoZSBkYXRlIG9mIHRoZSBjb3B5cmlnaHQgbGlzdGVkIGluIENPUFlJTkcgd2lsbCBtYXRjaCB0aGUgeWVhciB0aGF0IHRoaXMgbW90aW9uIGlzIHBhc3NlZCwgYW5kIHdpbGwgYmUgYmFjay1kYXRlZCB0byAyMDE0IGlmIG5lZWRlZC4gRm9yIGV4YW1wbGUsICdDb3B5cmlnaHQgKGMpIDIwMTQtMjAxNSBOdSBEZXZlbG9wZXJzJyBpZiB0aGUgbW90aW9uIHBhc3NlcyB0aGlzIHllYXIsIG9yICdDb3B5cmlnaHQgKGMpIDIwMTQtMjAxNiBOdSBEZXZlbG9wZXJzJyBpZiB0aGUgbW90aW9uIGRvZXMgbm90IHBhc3MgdW50aWwgMjAxNi4NCg0KWzRdIGh0dHBzOi8vZ2l0aHViLmNvbS9iaXRjb2luL2JpdGNvaW4vYmxvYi9tYXN0ZXIvQ09QWUlORw0KDQpbNV0gaHR0cHM6Ly9naXRodWIuY29tL3BwY29pbi9wcGNvaW4vYmxvYi9tYXN0ZXIvQ09QWUlORw0KDQpbNl0gaHR0cHM6Ly9naXRodWIuY29tL1BlZXJzaGFyZXMvUGVlcnNoYXJlcy9ibG9iL21hc3Rlci9DT1BZSU5HDQogICAg"
  },
  "2": {

This file has been truncated. show original

Cybnate · March 3, 2016, 7:50am

Nice work: One challenge left is how to compare the gist content captured in json format with the original text in the forum.
Json is not known for its human readability. Are there any user friendly tools to just grab the raw document as presented and make it readable as far as you or anyone else are aware? This would greatly help to have a few of us comparing and providing confidence to vote for it.

CoinGame · March 3, 2016, 9:24am

I was thinking of adding a QA canary somewhere in the middle to make sure someone checked my work! Forgot about it though. I’ve included all the information in the gist needed to check the work. From the raw URL of the original forum posts to the exact content used from those posts to form the new hashes. I’m not sure I understand what the challenge is here. Is someone going to actually read though everything? Why not just copy/paste the contents of the json file into the online converters like I did? Starting with the source text, and then dumping the outputs into an online diff tool. It should take less than a minute for each if you have the tools. I’ll find the links I used when I get to my computer and put together a quick guide on how to check everything.

Cybnate · March 3, 2016, 9:29am

Actually, you answered my question You provide a good way to do the verification and which tools to use! I was just not thinking this through. You should have added the canary though

CoinGame · March 3, 2016, 9:41am

Ah okay sorry. I just woke up and my brain wasn’t braining properly. I’ll put together a quick guide once I’m situated.

CoinGame · March 3, 2016, 12:14pm

how to verify my results above

At the top of the gist are links to raw versions of each motion which I used as the source. People formatted their sections differently but basically where they created dividers to delineate start/ends of motions I used the text inside the dividers. If you’re not sure where to start check the hash-content field of the motion your checking to see where I started and ended.

https://discuss.nubits.com/raw/624

Lets use this motion as an example since it’s nice and small. That is the text of the post.

Dividend period 001 of Kiara Tamm’s Proposal to Provide Early Stage, Dual-Side Liquidity and Shareholder Dividends, Revision 0.1.0 (https://gist.github.com/KiaraTamm/c30172f9d5d73e970bf2) will be changed in the following way:

Period 001 will be split into two (2) distributions. The first (1st) distribution of 50,000 NBT worth of PPC will be prepared and delivered to shareholders no later than 72 hours after the passing of this motion. The remaining portion of 22,000 NBT worth of PPC will prepared and delivered to shareholders no later than 72 hours after the funds become available from the proceeds of continued NBT sales. After the second (2nd) distribution of Period 001 is paid, the grant operations will continue as outlined in the original proposal, with no other changes.

That is the raw text I used to produce the hash. From here we can create all of the other values in the JSON file I produced.

Checking the new hash

Copy the text inside the code block above (normally you would do it from the source URL in the gist)
Use this tool to produce a hash from the text.
Check the hashes with a diff tool

Checking the hash-content text

Copy the text inside the code block above (normally you would do it from the source URL in the gist)
Use this tool to escape the source text and make it JSON friendly.
Check the result with a diff tool

Checking the content-b64 text:

Copy the text inside the code block above (normally you would do it from the source URL in the gist)
Use this tool to produce a b64 encoded string of the source text
Check the result with a diff tool

That should be it. By following those steps you can verify the source content used, the transformation of that content into the gist, and compare it to the contents I’ve put into the gist.