see the risk. keep the code.
moire runs eight fixed checks on your bytecode and lets one AI reviewer read the source, once, with nothing kept. What lands on chain is a seal: a hash, eight answers and a signed opinion. Never a line of your code.
two layers. the pattern shows what's hidden.
A moire pattern appears when two grids overlap. Neither grid holds the picture on its own. moire works the same way: a fixed proof layer and an agent layer, kept apart, and the seal is what you see where they meet.
proof layer
Eight checks run on the compiled bytecode. Every answer is yes or no, the same for anyone who runs it, and bound to the hash of the code.
agent layer
One AI reviewer reads the source in isolation on a zero-retention route. It describes who holds which powers, scores the risk, never quotes a line, and signs its text as an opinion.
the seal
A registry on Robinhood Chain writes both results against the code hash. Wallets, launchpads and bots can read it in one call.
the code goes in. only the seal comes out.
- 01
point it at one commit
A read-only grant on one repo at one commit. moire compiles it and matches the result to the deployed bytecode, byte for byte.
- 02
two layers run apart
The checks run on the bytecode. The reviewer reads the source alone, writes its notes without quoting, and the working copy is deleted.
- 03
wear the seal
The seal follows the bytecode wherever it is deployed. Anyone can read it. Nobody can read your code from it.
eight checks. fixed, public, the same for everyone.
no hidden mint
Supply can only grow through paths the interface declares.
no owner drain
No address can move balances that are not its own.
tax under the cap
Any transfer tax is fixed or bounded, and the bound is 10%.
no blacklist
No function can stop a specific address from selling.
no transfer pause
Transfers cannot be switched off once trading starts.
not upgradeable
No proxy and no delegatecall to an address that can change.
sell path clears
A buy then a sell from a fresh address completes on a fork.
no self-destruct
Nothing can remove the code after it is sealed.
the chain reads the answers. never the source.
public, in the seal
- hashkeccak256 of the runtime bytecode
- 8 answerswhich checks passed, signed against the hash
- reviewthe reviewer's signed text, with no quotes from the code
- reviewerthe key that signed, and which model it used
private, always
- sourceread once by one reviewer, then deleted
- reponame, history and branches stay hidden; only the commit hash is noted
- youno account; the paying wallet is the only identity
a seal is a list, not a promise.
It says these eight checks ran on this exact bytecode and what they found, and that a named reviewer signed an opinion about it. It does not say the code is good, and it cannot see what the checks do not look for.
the card on the right is an example of the format. it is not a real review.
each check shows pass or fail once a review is written.
launch with the mark, before the reveal.
$MOIRE launches on Robinhood Chain. The contract address is posted here first. If it is not on this page, it is not ours.
questions.
does anyone read my code?
One AI reviewer reads it, once, on a route that keeps no prompts or responses. The working copy is deleted when the seal is signed. No person reads it and nothing on chain contains it.
what does a seal actually prove?
The eight answers are bound to the bytecode hash, so anyone can check they belong to that exact code. The review is an opinion and is labelled as one. A seal never says a contract is safe in general.
why two layers instead of one score?
Because a fixed check and an AI opinion are different kinds of evidence. Keeping them apart means a reader always knows which part is proof and which part is judgement.
can a bot read seals?
Yes. A seal is looked up by code hash and returns the eight answers, the score and who signed. One call, no source to parse.
where do I find the token address?
On this page, in the token section and the header, before anywhere else. Ignore addresses posted by anyone else.
when can I submit a contract?
Reviews open at launch. Follow the X account for the date.