Subscribe to MOMUA
Subscribe to MOMUA
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
1.618 — on-chain determinism: ERC-721 with no IPFS; JSON from the contract. Mosaic evolves until a match; OrderHash/ArtHash verify the state.
1.618 OCN - WHEN THE MATCH IS SEALED BY THE CHAIN
IDEA
We turn the perfect tile order (the match) into an event recorded by the blockchain itself. The moment a match happens, the token's state freezes (match -> freeze), and that frame becomes truth forever.
WHY
To blend art, cryptography, and verifiable randomness so viewers see not a trick, but a fair result, attested on-chain.
CONTEXT
Author - MomUA, who takes part in volunteer initiatives supporting Ukraine. The collection is on Polygon; contracts are verified on Polygonscan; submitted to DappRadar (status: pending review).
HOW IT WORKS (SHORT AND CLEAR)
A living canvas. The renderer draws a tile mosaic and updates it in discrete 5 second steps (on-chain SVG).
Fair mechanics. Tile order and motion are deterministic yet unique per tokenId; same rules, different stories.
Moment of truth. When the order becomes perfect, a freeze locks the token's metadata; from then on they do not change.
Proof (attributes). Metadata expose exactly two traits:
OrderHash - hex hash of the perfect order
ArtHash - hex hash of the assembled image This is sufficient to independently verify the frame's correctness.
**IMPORTANT NOTE ABOUT FREEZE**
Freeze is a transactional action in Core (not a background daemon).
autoFreezeIfPerfect(tokenId) - callable by any address at the moment of a live match ("perfect now")
finalizeFreeze(tokenId) - callable by owner/approved if the perfect order has already been fixed during a past match The renderer can always produce a deterministic frozenTokenURI(tokenId) snapshot, but actual freezing happens only when Core stores that snapshot in its cache and emits the event.
ON-CHAIN VERIFICATION (SO YOU DO NOT HAVE TO TAKE OUR WORD)
Goal: confirm (a) real addresses and Core->Renderer link; (b) exactly two attributes; (c) that freeze truly happened.
A) ADDRESSES AND LINKAGE
Core (main contract): 0x2fBdd3670eB82e78e36aac0fC94A927Ed920eCA4
Renderer: 0xeaDeCf40E127c8B518eb20ac4aE26b01e0b58d81 Steps:
On Polygonscan, open Core -> Read Contract -> renderer() -> it must return 0xeaDe...8d81
Ensure both contracts are verified
B) ATTRIBUTE CHECK (ANY tokenId)
In Core, call tokenURI(tokenId) and frozenTokenURI(tokenId) - both return data:application/json;base64,...
Decode Base64 locally
In both JSONs, the attributes array must contain exactly two traits - OrderHash and ArtHash (no others)
C) HOW TO BE SURE A FREEZE ALREADY HAPPENED
URI equality: after freezing, tokenURI(tokenId) == frozenTokenURI(tokenId) bit-for-bit. Before freezing they differ (live vs snapshot)
Event: Core must have emitted PermanentURI for that tokenId
Order status: isOrderFixed(tokenId) == true means the perfect order was fixed at some point Tip: isPerfectNow(tokenId) only tells whether it is perfect right now (handy to time autoFreezeIfPerfect)
D) STATE MATRIX (QUICK REFERENCE)
Normal: isPerfectNow=false; isOrderFixed=false; tokenURI vs frozenTokenURI: different; Action: wait for a match
Match now: isPerfectNow=true; isOrderFixed=false; tokenURI vs frozenTokenURI: still different; Action: call autoFreezeIfPerfect
Order fixed, no cache: isPerfectNow=any; isOrderFixed=true; tokenURI vs frozenTokenURI: still different; Action: owner/approved calls finalizeFreeze
Frozen (final): isPerfectNow=any; isOrderFixed=true; tokenURI vs frozenTokenURI: identical; Action: done; PermanentURI present
Note: do not expect "false" in frozenTokenURI. It always returns a valid snapshot JSON. A real freeze is confirmed by URI equality + event + isOrderFixed.
CONTRACT ADDRESSES (POLYGON)
Core: 0x2fBdd3670eB82e78e36aac0fC94A927Ed920eCA4
Renderer: 0xeaDeCf40E127c8B518eb20ac4aE26b01e0b58d81
These are the only two addresses relevant for verifying "1.618 OCN" in this article.
LINKS
DappRadar: submitted, status pending (we will add the link once approved)
ORIGIN AND INTENT
This is an experiment in trust without narrators: the match is recorded by code on-chain. MomUA cares for Mother Ukraine; that human note stays gentle and secondary - the focus is the mechanism's fairness.
TRUST MANIFEST
Correctness does not ask for belief - it is proven by code
Each match is an event etched into the chain
The artwork gains a time coordinate of truth - auditable by anyone
P.S. I am MomUA. If the idea of fair mechanics resonates, support the collection in your own way: read, share, leave feedback (mint/buy only if you genuinely want to).
EXTRA NOTES FOR DEEP READERS
Order update interval: 5 seconds
Freeze cannot be back-dated: Core caches exactly what renderer.frozenTokenURI(tokenId) returns at freeze time and emits PermanentURI
After freezing, tokenURI becomes immutable and equals frozenTokenURI for that token
1.618 — on-chain determinism: ERC-721 with no IPFS; JSON from the contract. Mosaic evolves until a match; OrderHash/ArtHash verify the state.
1.618 OCN - WHEN THE MATCH IS SEALED BY THE CHAIN
IDEA
We turn the perfect tile order (the match) into an event recorded by the blockchain itself. The moment a match happens, the token's state freezes (match -> freeze), and that frame becomes truth forever.
WHY
To blend art, cryptography, and verifiable randomness so viewers see not a trick, but a fair result, attested on-chain.
CONTEXT
Author - MomUA, who takes part in volunteer initiatives supporting Ukraine. The collection is on Polygon; contracts are verified on Polygonscan; submitted to DappRadar (status: pending review).
HOW IT WORKS (SHORT AND CLEAR)
A living canvas. The renderer draws a tile mosaic and updates it in discrete 5 second steps (on-chain SVG).
Fair mechanics. Tile order and motion are deterministic yet unique per tokenId; same rules, different stories.
Moment of truth. When the order becomes perfect, a freeze locks the token's metadata; from then on they do not change.
Proof (attributes). Metadata expose exactly two traits:
OrderHash - hex hash of the perfect order
ArtHash - hex hash of the assembled image This is sufficient to independently verify the frame's correctness.
**IMPORTANT NOTE ABOUT FREEZE**
Freeze is a transactional action in Core (not a background daemon).
autoFreezeIfPerfect(tokenId) - callable by any address at the moment of a live match ("perfect now")
finalizeFreeze(tokenId) - callable by owner/approved if the perfect order has already been fixed during a past match The renderer can always produce a deterministic frozenTokenURI(tokenId) snapshot, but actual freezing happens only when Core stores that snapshot in its cache and emits the event.
ON-CHAIN VERIFICATION (SO YOU DO NOT HAVE TO TAKE OUR WORD)
Goal: confirm (a) real addresses and Core->Renderer link; (b) exactly two attributes; (c) that freeze truly happened.
A) ADDRESSES AND LINKAGE
Core (main contract): 0x2fBdd3670eB82e78e36aac0fC94A927Ed920eCA4
Renderer: 0xeaDeCf40E127c8B518eb20ac4aE26b01e0b58d81 Steps:
On Polygonscan, open Core -> Read Contract -> renderer() -> it must return 0xeaDe...8d81
Ensure both contracts are verified
B) ATTRIBUTE CHECK (ANY tokenId)
In Core, call tokenURI(tokenId) and frozenTokenURI(tokenId) - both return data:application/json;base64,...
Decode Base64 locally
In both JSONs, the attributes array must contain exactly two traits - OrderHash and ArtHash (no others)
C) HOW TO BE SURE A FREEZE ALREADY HAPPENED
URI equality: after freezing, tokenURI(tokenId) == frozenTokenURI(tokenId) bit-for-bit. Before freezing they differ (live vs snapshot)
Event: Core must have emitted PermanentURI for that tokenId
Order status: isOrderFixed(tokenId) == true means the perfect order was fixed at some point Tip: isPerfectNow(tokenId) only tells whether it is perfect right now (handy to time autoFreezeIfPerfect)
D) STATE MATRIX (QUICK REFERENCE)
Normal: isPerfectNow=false; isOrderFixed=false; tokenURI vs frozenTokenURI: different; Action: wait for a match
Match now: isPerfectNow=true; isOrderFixed=false; tokenURI vs frozenTokenURI: still different; Action: call autoFreezeIfPerfect
Order fixed, no cache: isPerfectNow=any; isOrderFixed=true; tokenURI vs frozenTokenURI: still different; Action: owner/approved calls finalizeFreeze
Frozen (final): isPerfectNow=any; isOrderFixed=true; tokenURI vs frozenTokenURI: identical; Action: done; PermanentURI present
Note: do not expect "false" in frozenTokenURI. It always returns a valid snapshot JSON. A real freeze is confirmed by URI equality + event + isOrderFixed.
CONTRACT ADDRESSES (POLYGON)
Core: 0x2fBdd3670eB82e78e36aac0fC94A927Ed920eCA4
Renderer: 0xeaDeCf40E127c8B518eb20ac4aE26b01e0b58d81
These are the only two addresses relevant for verifying "1.618 OCN" in this article.
LINKS
DappRadar: submitted, status pending (we will add the link once approved)
ORIGIN AND INTENT
This is an experiment in trust without narrators: the match is recorded by code on-chain. MomUA cares for Mother Ukraine; that human note stays gentle and secondary - the focus is the mechanism's fairness.
TRUST MANIFEST
Correctness does not ask for belief - it is proven by code
Each match is an event etched into the chain
The artwork gains a time coordinate of truth - auditable by anyone
P.S. I am MomUA. If the idea of fair mechanics resonates, support the collection in your own way: read, share, leave feedback (mint/buy only if you genuinely want to).
EXTRA NOTES FOR DEEP READERS
Order update interval: 5 seconds
Freeze cannot be back-dated: Core caches exactly what renderer.frozenTokenURI(tokenId) returns at freeze time and emits PermanentURI
After freezing, tokenURI becomes immutable and equals frozenTokenURI for that token
No activity yet