Registry / gl_moo

moo MOO

No signature request anywhere on the site, and approvals are scoped to the exact amount. The token itself is immutable with no owner and nothing that can mint, pause or freeze it.

Reviewedreviewed 17 Sept 2026, 41 days ago

ChainRobinhood Chain

Contract address0xc103ac00a25173870c909223c5676d50bf5728b2

Site reviewedhttps://moo.guru

Reviewed on2026-09-17 23:25 UTC

Re-review due17 Dec 2026

Reviewer@arron

Findings

three passes, written up as reviewed

[01]

Wallet connection

No issues found

What the site asks your wallet for when you connect, and whether connecting alone can cost you anything.

Reviewer notes

Connecting is free in the literal sense: the site asks for eth_requestAccounts and nothing else, and the only follow-up request is the chain switch it needs to reach chain 4663 at all. There is no signature bundled into the connect step, which is the usual place a drain hides. The page also carries a localhost-only development shortcut that uses the publicly known Anvil test key. It is gated on the hostname and the wallet path is preferred ahead of it, so it cannot be reached on moo.guru. It is inert on the hosted site and it is not a key that protects anything.

What was examined

Connect requests accounts only, with no signature attached to it.
The only other wallet request is switching or adding Robinhood Chain, chain id 4663.
Connecting alone moves nothing and grants nothing.
No analytics or third-party call carries the connected address.

[02]

Transactions and signatures

No issues found

Every transaction and signature the site puts in front of you, and whether what it shows matches what it does.

Reviewer notes

There is no off-chain signature request on this site at all. Every wallet interaction is an on-chain call your wallet can decode and show you, which means there is no opaque message to mistake for a login. Approvals are the part worth stating plainly. The site reads your current allowance and approves exactly the amount the next action needs, so it never asks for an unlimited approval. That is better than the common practice and it limits what a later problem could reach. One thing a holder should understand rather than a fault in the site: the contract your deposit goes to is supplied by the page when it loads, not fixed inside the reviewed script. The fingerprints below therefore include the page itself, so that value is covered by the evidence and not merely by the script around it.

What was examined

No personal_sign, eth_sign or signTypedData anywhere in the application.
Approvals are scoped to the exact amount needed, never unlimited.
Every write is a named contract call with arguments visible in the wallet: subscribe, fill, settle, claim, withdraw.
The swap path sets a minimum output from a slippage bound rather than accepting any result.

[03]

Contract code

Source not available

The deployed contract, when the source is public or the team supplies it. Verified against what is actually on chain.

Reviewer notes

The deployed bytecode carries no operator levers: nothing can mint, freeze, blacklist, pause, or change a fee, and there is no owner account to hold such a power. Supply is fixed at 1,000,000,000 and can only go down, via burn. Marked not-available rather than clear because the source is not published and was not supplied. Everything above is read from the deployed bytecode, and reading bytecode is not reading code. If the team publishes or sends the source, this becomes a real pillar-3 review and the verdict can change. This pillar covers the moo token only. The pool contract that receives deposits, and the assets it settles in, are separate deployments and were not read as source.

What was examined

Not a proxy: no EIP-1967, EIP-1822, beacon or minimal-proxy pattern. The logic cannot be replaced.
No owner() accessor exists on the contract at all.
PUSH4 scan of the deployed dispatcher finds no mint, blacklist, pause, fee-setter or max-transaction function.
Exposed surface is standard ERC20 plus burn and burnFrom. 25 selectors total.
Source is not verified on Sourcify for chain 4663, and was not supplied.
The pool that holds deposits is a separate contract and is not covered by this pillar.

Exactly what was reviewed

so you can check it yourself

This review describes the site and the contract as they were on 17 Sept 2026. Nothing here is re-checked automatically, so these are the fingerprints of the exact files that were looked at. If a hash below no longer matches what the site serves, the site has changed since it was reviewed and this report no longer describes it.

What was reviewed, by fingerprint

Reproduce any of these yourself:

# a site script
curl -s <url> | shasum -a 256

# the deployed contract
cast code <address> --rpc-url <rpc> | tr -d '\n' | shasum -a 256

https://moo.guru/

sha256 af69e674670e1c03bd6c8f576ffae20522656b07a53ba46f7cfe37fd39b066c9

https://moo.guru/app.js

sha256 3cdb870547dc775e5f0e36b9566fa15c0fa3c16118b95f74437b31b6bced851e

https://moo.guru/vendor/viem.js

sha256 47541efc64a92b54a0cfb5d41e29bb5ddb7f08bf21ab2add70475b7b7e2c7a3f

deployed contract bytecode

sha256 5c75c8f6b0d5c90bb8cb12ee5b473ed270a64bae0de8073e6135844fbd23ed7b

A project can change its site the day after a review, and a badge on a page cannot tell you that. The date and these hashes are what let you find out.

Badge embed

for moo to put on their site

The badge renders from this server on every load. It carries the full contract address, the review date and this page’s address in the image itself, so a copy that is taken and re-hosted still points back here. If the review is revoked or expires, the badge turns red or grey everywhere it is embedded without the project having to do anything.

<a href="https://greenlightsec.xyz/v/gl_moo" target="_blank" rel="noopener">
  <img src="https://greenlightsec.xyz/b/gl_moo/29ad5055.svg"
       alt="GreenLight: moo reviewed, 0xc103ac00a25173870c909223c5676d50bf5728b2. Verify at https://greenlightsec.xyz/v/gl_moo"
       width="364" height="128" loading="lazy" decoding="async"
       referrerpolicy="strict-origin-when-cross-origin">
</a>

What this review does not cover

What the team does next. This is a review of a site and a contract, not of people.
The price, the tokenomics, or whether any of this is a good idea.
Anything the project changed after 17 Sept 2026. Compare the hashes above against what the site serves now.
Third-party infrastructure the project uses but does not control.

Status reviewed. This review expires on 17 Dec 2026, after which the badge stops claiming anything until the project is reviewed again.