Protocol Notes
Eternity Signals is an onchain archive of living transmissions. This page describes what the terminal reads and what the protocol records.
No servers. No external storage. Only the machine and the record.
Eternity Signals is not a marketplace UI. It is a protocol interface: mint, observe, evolve, fuse, recover provenance, and read what the chain returns.
Absence is provenance. Consumption is part of the archive.
A Signal resolves from tokenURI as a base64 JSON data URI. The image resolves as a base64 SVG data URI. Rendering is recovered by the client from chain reads.
Token pages display decoded metadata, live state reads, and provenance links. The gallery exposes protocol modes: Genesis, Ascended, Burned, Wallet, and Archive.
Metadata and SVG are not hosted externally.
- tokenURI: data:application/json;base64
- image: data:image/svg+xml;base64
The interface decodes these payloads locally and renders the transmission directly.
Evolution is a state transition recorded by the protocol. It may refuse during cooldown or other constraints. The terminal probes evolve availability and reports refusal as part of the experience.
Mutation state is visible via decoded attributes such as Stage, Evolution label, Instability, Resonance, Decay, Corruption, Storm, and Anomaly markers.
Fusion is irreversible. Two Signals are consumed and one ascended Signal is recorded. Inputs become silent archive entries.
Provenance is recovered from onchain events. Token pages attempt to resolve parent tokens and descendants from recorded fusion events.
Ascended Signals are fused outputs. They carry lineage. The interface renders them with denser, quieter presentation and emphasizes provenance.
Burned inputs are not treated as errors. They are preserved as consumed records.
Signals expose numeric measures in their attributes. The terminal presents these values as live protocol context:
- Instability: volatility of the transmission state.
- Resonance: coupling strength across the system.
- Entropy (Decay): degradation pressure over time.
These values are not calculated offchain by the interface. They are decoded from the onchain record and displayed.
Why does a token show “This Signal is silent.”?
Fusion consumes inputs. The terminal attempts to recover the ascended descendant from onchain provenance.
Does this site use a backend?
No. The interface reads from chain and decodes data URIs. No external storage is required to render.
Why can evolve refuse?
Cooldowns and constraints are part of protocol behavior. Refusal is treated as state, not as UI failure.
Is the gallery hiding burned IDs?
No. Burned entries remain visible. Absence is provenance.