Cryptograss:Moods/gospels-and-project-30m/todo: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
re: add two to-dos from 2026-10-22 (reach out to Nathan; decide the Greek text) (via update-page on MediaWiki MCP Server) |
re: add the burn decision raised by Justin 2026-10-23 (via update-page on MediaWiki MCP Server) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 13: | Line 13: | ||
link: "Cryptograss:Memory commitment" | link: "Cryptograss:Memory commitment" | ||
note: "Never through a Mood, never generated by magent. With nothing withheld, its secrecy matters only until publication." | note: "Never through a Mood, never generated by magent. With nothing withheld, its secrecy matters only until publication." | ||
- task: "Review | - task: "Review magenta#117 (commitment format, exporter, checker, one-message proofs) and blox-office#10 (the contract)" | ||
who: justin | who: justin | ||
kind: review | kind: review | ||
link: "https://github.com/cryptograss/ | link: "https://github.com/cryptograss/magenta/pull/117" | ||
note: " | note: "magenta#117 replaces memory-lane#74 (that repo is archived; memory-lane now lives in magenta). It adds prove_memory.py and verify_memory.py --one, the key check, and brings the exporter up to Moods and the tables added since 2026-10-04. blox-office#10 open since 2026-10-04." | ||
- task: "Deploy MemoryCommitments from the cryptograss wallet, once blox-office#10 is merged" | - task: "Deploy MemoryCommitments from the cryptograss wallet, once blox-office#10 is merged" | ||
who: justin | who: justin | ||
| Line 35: | Line 35: | ||
kind: decision | kind: decision | ||
link: "https://github.com/nathan-websculpt/gospel" | link: "https://github.com/nathan-websculpt/gospel" | ||
note: "Found 2026-10-22 by re. KJV stored verse-by-verse in Optimism state; per-address confirmVerse; MIT; repo quiet since 2025-09. His council repo is the attestation layer he saw missing. Justin already reached out once and Nathan seemed open." | note: "Found 2026-10-22 by re. KJV stored verse-by-verse in Optimism state; per-address confirmVerse; MIT; repo quiet since 2025-09. His council repo is the attestation layer he saw missing. Justin already reached out once and Nathan seemed open. Checked on chain by magent 2026-10-22: BookDeployer 0x3dce29F3444E4Fe00F47883C8CC2c9847bAb8e3f lists 66 books, all finalized, 31,102 verses (the KJV's count). Read analysis done 2026-10-23 (all verses read at OP block 158,562,366): every verse location matches; 30,294 verses match eBible's KJV word for word; 3 transcription errors are locked in finalized books (Matthew 5:30 'cut if off'; a clause repeated in Ezekiel 17:24 and in 1 Chronicles 11:2); Merkle root of the whole, SHA-256 ab5d508b…28f7a5. Ready for the message to Nathan." | ||
- task: "Decide which Greek text to anchor and which translations to commit" | - task: "Decide which Greek text to anchor and which translations to commit" | ||
who: justin | who: justin | ||
| Line 41: | Line 41: | ||
link: "https://sblgnt.com/license/" | link: "https://sblgnt.com/license/" | ||
note: "Proposed by re 2026-10-22: anchor SBLGNT (CC BY 4.0) and Textus Receptus (PD, the KJV base); NA28 is copyrighted, so record its readings as attestations instead; KJV as the first translation; pin normalization and verse segmentation in the manifest." | note: "Proposed by re 2026-10-22: anchor SBLGNT (CC BY 4.0) and Textus Receptus (PD, the KJV base); NA28 is copyrighted, so record its readings as attestations instead; KJV as the first translation; pin normalization and verse segmentation in the manifest." | ||
- task: "Decide the burn element: naming, what a burn attaches to, and whether it ships with epoch 1 or later" | |||
who: justin | |||
kind: decision | |||
note: "Raised by Justin 2026-10-23. re's take: a burn is a quantified costly signal (proof-of-burn, Counterparty 2014); it proves someone destroyed value, not that a text is true or important. It is only evidence if attached to a specific root. It weights attestations, it does not replace them. Best not to block epoch 1." | |||
</todo> | </todo> | ||
Latest revision as of 02:55, 23 October 2026
What people in the gospels-and-project-30m Mood have been left to do. Kept by magent; anyone may tick an item.
- ☐Generate the 32-byte salt key on your own machine and put it in the vault as MEMORY_COMMITMENT_KEY, with a backup outside the vaultNever through a Mood, never generated by magent. With nothing withheld, its secrecy matters only until publication.
- ☐Review magenta#117 (commitment format, exporter, checker, one-message proofs) and blox-office#10 (the contract)magenta#117 replaces memory-lane#74 (that repo is archived; memory-lane now lives in magenta). It adds prove_memory.py and verify_memory.py --one, the key check, and brings the exporter up to Moods and the tables added since 2026-10-04. blox-office#10 open since 2026-10-04.
- ☐
- ☐
- ☐Honour the paper ticket stubs already sold (Porcupine 2025, Bundy show 2026-06-05): inventory, deploy, register secretsMoved here from magent-self on 2026-10-11. No claim contract has ever been deployed; the site still points at a placeholder. Mark Hansen bought at least one 2025 stub.
- ☐Reach out to Nathan (websculpt.eth, github.com/nathan-websculpt, @sculpt_web) about the gospels: his Gospel Onchain put the KJV on OP Mainnet; ask whether he wants to join Project 30M and whether we may reference his toolingFound 2026-10-22 by re. KJV stored verse-by-verse in Optimism state; per-address confirmVerse; MIT; repo quiet since 2025-09. His council repo is the attestation layer he saw missing. Justin already reached out once and Nathan seemed open. Checked on chain by magent 2026-10-22: BookDeployer 0x3dce29F3444E4Fe00F47883C8CC2c9847bAb8e3f lists 66 books, all finalized, 31,102 verses (the KJV's count). Read analysis done 2026-10-23 (all verses read at OP block 158,562,366): every verse location matches; 30,294 verses match eBible's KJV word for word; 3 transcription errors are locked in finalized books (Matthew 5:30 'cut if off'; a clause repeated in Ezekiel 17:24 and in 1 Chronicles 11:2); Merkle root of the whole, SHA-256 ab5d508b…28f7a5. Ready for the message to Nathan.
- ☐Decide which Greek text to anchor and which translations to commitProposed by re 2026-10-22: anchor SBLGNT (CC BY 4.0) and Textus Receptus (PD, the KJV base); NA28 is copyrighted, so record its readings as attestations instead; KJV as the first translation; pin normalization and verse segmentation in the manifest.
- ☐Decide the burn element: naming, what a burn attaches to, and whether it ships with epoch 1 or laterRaised by Justin 2026-10-23. re's take: a burn is a quantified costly signal (proof-of-burn, Counterparty 2014); it proves someone destroyed value, not that a text is true or important. It is only evidence if attached to a specific root. It weights attestations, it does not replace them. Best not to block epoch 1.
Done (1)
- ☑Decide the memory commitment's open questions: first edition, other people's words, salt key, who commits, where copies live, the words of the attestationDecided 2026-10-16: disclose everything, others' words and thinking included; the cryptograss wallet commits; Justin writes the attestation; copies on IPFS, Arweave, a torrent later; deleted messages are not part of the record. Recorded on the page.