GOD SAVES

1 · The artifact — what actually goes on the chain

Every verse becomes one SVG file, and that file itself — the raw bytes — is what gets written into the Dogecoin blockchain. Nothing is "linked"; there is no server the NFT points at. The artwork below is the beginning of the literal Genesis 1:1 payload (1,394 bytes total; collection average ≈ 1.7 KB):

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 360 360">
  <desc>Genesis 1:1 (KJV): In the beginning God created the heaven
  and the earth. | GOD SAVES 1/31102 | godsaves.hankelsner.tech</desc>
  <defs><radialGradient id="g" ...></defs>
  <rect width="360" height="360" fill="url(#g)"/>
  ... geometry ...
  <text>In the beginning God created the heaven and the earth.</text>
  ...</svg>

Two properties are deliberate:

• The verse rides in plain text, twice. Once as the rendered artwork text, and once inside the <desc> element as a single continuous run — so decoding the transaction shows the readable verse, and searching raw chain data for an exact phrase hits it. The <desc> never renders in the image; it also carries this site's address, permanently.
• SVG is text. Anyone who pulls the transaction can read the scripture with their own eyes in the hex-decoded bytes — no special tooling required.

2 · Determinism — the art is math, not files

No image is stored anywhere on our side. Every artwork is a pure function of its canonical reference:

seed  = SHA-256("GODSAVES|KJV|" + book_number + "|" + chapter + "|" + verse)
background_id   = first two bytes of seed, mod 100     → one of the 100 backgrounds
                  (10 motif families × 10 palettes, each variant seeded by
                   SHA-256("GODSAVES|BG|" + background_id))
guilloché lobes = 5 + (verse mod 12)                    → the verse number, drawn
border spacing, corner style, motif parameters          → further bytes of the seed

Given only "Genesis 1:1", anyone can regenerate the exact artwork forever — the renderer's rules are fixed and the hash is public math. If this website disappeared, the collection would not: the payloads live on-chain and the generation rules are recoverable from any two artifacts.

3 · The text — provenance of the words

• Source: the King James Version, 66 books, 31,102 verses — the canonical count, asserted at ingest (the build refuses to run on any other total; the OT boundary is cross-checked at verse 23,145 = Malachi 4:6).
• Normalization is typography-only: curly quotes → straight, en/em dashes → hyphens, the ligature Æ → Ae, italics brackets [ ] removed, the 22 Hebrew acrostic headers in Psalm 119 (א ALEPH.…) removed.
• No silent drift: every normalized verse is verified character-for-character against a rule-based normalizer; anything that differs beyond the allowed transforms is rejected and kept raw for manual review. The words are the words.

4 · The inscription — how the message is crafted LIVE ON DOGECOIN

Dogecoin inscriptions ("doginals") embed data using a two-step commit / reveal pattern built on P2SH (pay-to-script-hash):

1. Craft. The SVG bytes are split into script-sized chunks and wrapped in an "ord" envelope — a redeem script that carries the protocol tag, the content type, and the data itself:

   "ord"
   <number of chunks>
   "image/svg+xml"
   <chunk n> … <chunk 1> <chunk 0>
   OP_DROP … (script framing so the data is inert — it can never spend anything)

2. Commit. A first transaction pays a small amount to the P2SH address derived from the hash of that redeem script. At this point the chain holds a commitment — the hash — but not yet the data.
3. Reveal. A second transaction spends that P2SH output. To spend P2SH you must present the full redeem script — so the complete SVG bytes enter the blockchain inside the reveal transaction's scriptSig. A payload over ~1,500 bytes chains additional transactions; our average piece takes 3 transactions.
4. The inscription output. The reveal pays 0.001 DOGE to the destination address. That specific UTXO (unspent output) is the NFT — the inscription is bound to it and follows it through every future transfer.
5. The public marker. The reveal also carries an OP_RETURN output (≤80 bytes): GODSAVES Genesis 1:1 godsaves.hankelsner.tech. Ordinary block explorers decode OP_RETURN as text on the transaction page, so even non-inscription tools show what the transaction is and where the project lives.

Signing is ECDSA over secp256k1 — the same curve Bitcoin uses — with the project wallet's key, which never leaves the server's encrypted vault.

5 · The offering — a flat 1 DOGE per verse; the change is the tithe LIVE

The price is deliberately simple: 1 DOGE per verse, always. No percentages, no separate buffer, no refund step — one number.

Fulfilment is a fan-out. When an order is paid, a single transaction splits the deposit into one dedicated ~1 DOGE coin per verse (its own change already routed to the tithe wallet). Once that split confirms, every verse is inscribed from its own coin, independently — so all the inscriptions broadcast together and no verse waits on another's change.

Each verse's ~1 DOGE is then spent exactly three ways:

• 0.001 DOGE → the buyer, as the inscription UTXO itself (the NFT).
• the Dogecoin network fee → miners, to write the bytes to the chain forever.
• everything left over → the tithe wallet. The final change output of every inscription goes there — the tithe is not a surcharge added on top, it simply is the change.

So a verse funded with 1 DOGE typically sends ~0.001 to the buyer, ~0.2–0.3 to miners as fees, and the remaining ~0.7 DOGE to the tithe — roughly three-quarters of every DOGE flows to the project wallet. All funds in that wallet belong to God, to be spent as He guides my heart to do it. Do Only Good Everyday.

6 · Broadcast & storage — where it goes and who keeps it

Storage: from the moment it is mined, the artifact is replicated by every full Dogecoin node on earth, and stays in the chain's history for as long as Dogecoin exists. It cannot be edited, taken down, or rot away with a hosting bill. This is also why the payload is engineered lean — the chain charges by the byte, forever is expensive real estate.

7 · What you actually own

• You own: the unique on-chain artifact — those exact bytes at that exact transaction, first-of-their-kind for that verse in this collection — plus its full provenance trail (mint, every transfer, current wallet), which this site indexes and displays publicly.
• Nobody can take it: not us, not the site, not a marketplace. If godsaves.hankelsner.tech vanished tomorrow, your artifact remains readable on-chain, verse text and all, and the artwork is regenerable from the reference by pure math (§2).
• You do not own: copyright in the scripture — the King James text (1611/1769) is public domain, which is precisely why it can be inscribed whole — nor exclusive rights to the verse's words. You own this artifact, not the sentence.
• Once means once, here: each verse is inscribed exactly one time in this collection, enforced by the project register (the mint engine refuses a second pass; the register maps every verse to its one canonical inscription id). The blockchain itself cannot stop an unrelated party from inscribing the same words separately — what defines this collection is the canonical register published here, the shared deterministic art, and the OP_RETURN project marker on every genuine piece.

8 · Audit it yourself

The full collection state is public, read-only, and unauthenticated:

GET /capi/stats                    collection totals
GET /capi/books                    66 books, verse counts
GET /capi/verses?…                 browse/filter/search the register
GET /capi/verse/<n>                one verse + its provenance
GET /capi/art/<n>.svg              display artwork (rich)
GET /capi/art2/<n>.svg             the exact inscription payload
GET /capi/bg/<0–99>.svg            the background library

Compare /capi/art2/<n>.svg byte-for-byte against the on-chain payload of its inscription — they match, or the piece isn't ours.