M64 SVG Icons · Polygon

Read SVG definitions directly from a Polygon contract. No IPFS, gateway, contract deployment or wallet connection required to view. Each stored icon is returned by entry(uint256) and decoded in the browser.

M64 tools · Contract Factory · Solidity source · PolygonScan

1. Inspect deployed dictionary

Polygon PoS, chain 137. Contract 0xd78e182813cd4e964aa382d6a81f9efbb10648bd. Reads are pinned to one block and compare all 62 primary definitions to the local SVG seed.

Read RPC

Checking contract…

2. Request an icon

Enter a name such as home, an ordinal 0–63, or a six-bit character such as A (icon 0), B (icon 1), or a (icon 26). Prefix a digit with @ to interpret it as an M64 character (@0 = icon 52), or use #N for a literal contract entry ID. Names and characters are resolved by Chisel, not Solidity.

Name / ordinal / character / #entry

Reconstructed SVG symbol fragment (read-only)

Static artifact mirror (optional)

FileProxy can publish an SVG and a content-addressed manifest that Apache serves directly, even when FileProxy is stopped. The default URL uses the bundled static home fixture on this site as a working example; enter a different manifest URL after configuring rigler.org or another mirror. Exact bytes are checked against the bundled icon fixture, not treated as a Polygon audit.

Static manifest URL

No static read attempted.

64-icon manifest

Green outlines mean a complete matching icon has been recovered from Polygon. Others are local previews, not yet on-chain.

3. Append compressed icons (optional, costs gas)

The initial deployment has 62 text-fragment compression symbols but zero stored icons. This tool encodes the missing icon definitions with native M64 v2 and calls addSecondaryBatch(bytes[],uint32[]) in groups of up to eight. Anyone may append. Existing entries remain immutable. Nothing is submitted without wallet approval.

Wallet for writes

Read a matching dictionary first. No transaction prepared.

Storage costs Polygon gas. Review estimates can change. The contract stores compressed binary fragments and exposes them through getters; it does not render complete SVG markup itself. This page wraps a verified <symbol> fragment into a viewable SVG image.