Dark Star Z
The native six-bit M64 Polygon publication and rebuild tool uses the newly deployed 0xe6e9df9f49b1ab4417129454991466adc9923f8c dictionary after a read-only, byte-for-byte on-chain seed verification. This page still uses the older M64 v3 text-dictionary format; the two codecs are deliberately not interchangeable.
Landscape controls
IPFS artifact
Supply a CID to hydrate M64 v3. Without one, Chisel runs the local source; no ledger is needed just to draw.
Rendered output
Image is computed in a restricted iframe from the active program. Parameter changes re-run the same hydrated source.
Publish / reconstruct from two contracts
Polygon mainnet (chain 137). Chisel publishes the renderer and the M64 program as separate logs; M64Dictionary stores the symbol IDs needed to reconstruct the program. The program log explicitly names both the dictionary contract and the earlier renderer-template transaction. Neither contract executes the reconstructed JavaScript. Wire format and compression accounting.
Chisel receives the HTML renderer template and the M64 program record. Contract compatibility is checked read-only before preparing a write.
Existing deployment reported with 51 Dark Star Z symbols. Inspect live term count and contract metadata before publishing. This address is part of the M64 artifact identity; it must match the dictionary reference embedded in the Chisel program record.
Dictionary term list and permanent IDs
All entries are retrieved from the selected contract. IDs 0–63 use one-byte references; higher IDs use an extension byte. Additional pages are read on demand.
Renderer transaction: Chisel-only log of reusable HTML. Program transaction: Chisel log of exact M64 text, referring to the M64Dictionary address and the renderer-template transaction. Preview buttons prepare unsigned data; publishing requires wallet approval.
Wallet execution: MetaMask may route a requested Chisel call through its Delegation Manager. This is wallet smart-account behavior, not a separate Polygon network. Chisel cannot disable it. To revert on Polygon, use MetaMask → Account details → Smart account and disable Polygon, confirming any wallet transaction.
MetaMask instructions for reverting to a standard account. The page checks the final transaction destination and Chisel event after mining.
Unsigned Polygon transaction fields (read-only, no diagnostics embedded)
Only chainId, to, value and encoded calldata are passed to the wallet. Compression percentages, estimates and the screen report are NOT part of the transaction data.
The unsigned transaction JSON above is not this hash. First publish the renderer template to Chisel and approve it in your wallet; its mined transaction hash will be inserted here automatically. If you already published the template, paste its transaction hash.
Polygon RPC / dictionary settings
The M64Dictionary address and inspect/encode actions are in the main publishing section above. Reads use RPC; inspection and compression are read-only. Appending new terms is a separate wallet-approved action, never required just to compress or reconstruct a program.
The image renders locally without ledger publication. The dictionary is never replaced silently during reconstruction.
Publish via Pinata
Pinata v3 uses a JWT. This is a per-session field; Chisel does not save the token in localStorage, the artifact, the URL, or the repository. A browser page holding a JWT can still expose it if the page is compromised. For stronger isolation, use a short-lived signed upload URL or a local credential broker.
Thunder trust / warning draft
This prepares 72-byte ASCII for a future UTXO OP_RETURN or a cross-chain attestation. It is not signed and does not send a transaction. A publisher's signed provenance must be established separately.
0x11111111111111111111111111111111111111110x2222222222222222222222222222222222222222Artifact metadata / provenance
Publication and safety attestations are separate signed records. Contract deployment does not endorse an artifact; the publisher or an independent signer does.