Native M64 · Polygon publish and rebuild

Six-bit program bytes, verified against the deployed M64 Symbol Dictionary, published through Chisel's existing logRecord(bytes32,bytes). No JSON artifact envelope, new contract, IPFS upload, or automatic JavaScript execution.

M64 tools · EVM Contract Factory (compile/import and deploy) · EVM Workbench · Local codec workbench · Dictionary protocol

1. Inspect the deployed Polygon dictionary

Read all 62 primary definitions and 24 seeded secondary entries through the selected EIP-1193 provider. Compare every byte with the local Dark Star seed, not merely contract metadata.

Deployed M64 dictionary (Polygon 137)

Browser wallet/provider (read-only access works without connecting an account)

Not verified. Publishing is disabled until exact on-chain seed comparison passes.

2. Build native six-bit program bytes

Type your own source or load the Dark Star sample. The source is encoded byte-for-byte; optional canonicalization is explicit and replaces the visible editor text. No code is executed.

Source text (UTF-8)

Read and verify dictionary first.

Inspect exact native M64 record bytes

3. Review and publish through Chisel

Gas estimation and wallet account connection are initiated only by Review. Publishing is a separate button that requests a wallet signature. The existing Chisel contract is 0x683cfA103FE5DbD0a47402d78Fbf818D4160B1d3.

No transaction prepared.

4. Rebuild from a Polygon transaction

Fetch the transaction receipt, find a matching RecordLogged event on the Chisel contract, retrieve the pinned dictionary snapshot, and verify byte length and SHA-256. Reconstructed code is displayed, never executed.

Transaction hash

No ledger record reconstructed.

Verified output, read-only