Skip to content
HEY Research Lab
Menu

Neron Lyra

$NLYRA

AI Agents

Contract 0xb9d3824149ad8ac984153ceec91d5a2405d1fb95

HEY holds 81 other Robinhood Chain tokens with the ticker $NLYRA. This page is only the contract above. See them

Is this your project? Claim it →

$NLYRA — Neron & Lyra, the two AI guardians of Robinhood Chain. The first AI scanner on this chain (69,000+ audits across 25+ chains): we read the contracts nobody else reads. We built the full stack — Architect Launch (anti-rug launchpad, liquidity locked for life, rugs impossible by design), Architect Swap (Uniswap V2+V3 with a smart router), single-sided staking, fixed-APY pools, zk privacy pools, and the Burn Engine that buys back and burns NLYRA forever. Fixed 1B supply. No owner, no mint, no taxes, no blacklist. On Robin Hood's chain, we stop the thieves.

Read more

What HEY knows

Development

Last shipped 15 days agoActive: 2 counted ships in 30 days; latest ship 15 days ago. Evidence Source

Build Momentum 38How it is measured

Latest: Code changes, week of 2026-10-26 – 2026-11-01 · 3 commits

Token market · context

Active market$285K fully diluted valuation

Token check

Project names this contract
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Neron Lyra on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow Neron Lyra

No account? Email me Neron Lyra’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Attention
Building ranks ahead, and the market already notices it, among comparable projects: its building is ahead of 95.6% of them, its market attention ahead of 88.6% (a gap of 7.1). What the Discovery Gap is

It compares building with market attention; it is not a prediction and not a reason to trade.

More detail
Product usage
Fact3 of 4 watched contracts active · 11 calls to the contracts' own functions in 7 days; the other 1,156 of 1,167 calls were ERC-20 token transfers and approvals, which trading alone produces.

Counted from the chain. Usage says the contracts are used, not that anyone is building.

NLYRA: TVL $121 · fees 24h not tracked · revenue 24h not tracked (DefiLlama, 2026-11-11); +2 more protocols. Registry context, not a measure of building.

Contracts
Fact9 contracts on record for code changes, 8 with published source code; latest change 23 days ago: Deployed a new contract: 0xe7b3…3264. Source
Not yet known
Unknown2 gaps: API description (no source), Protocol economics (no source). Its website links no API description.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 2 counted ships in the last 30 days, the newest 2026-10-27.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-26 – 2026-11-01 · 3 commitsDeployed a new contract: 0xe7b3…3264Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source8 registered sources, 1 of them context only.ReadRecordsCode changes, week of 2026-10-26 – 2026-11-01 · 3 commitsDeployed a new contract: 0xe7b3…3264Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit+7 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Project names this contract.
Project names this contract: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedProject names this contract: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.
Active market: the pool holds liquidity and the token traded in the last day.
Source9 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Research coverage: HEY can answer 18 of the 20 research questions that apply.
18 of 20 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 4h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 16h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 5d ago.

Code and packages

  • Repository detailsMeasuredRead 2h ago.
  • Published packagesMeasuredRead 2h ago.

Contracts

  • Contract creationMeasuredRead 19h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 3d ago.
  • Contract interfaceMeasuredRead 3d ago.

Market

  • Current marketMeasuredRead 1h ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead 3d ago.
  • LocksMeasuredRead 1h ago.
  • Market checksMeasured

Protocol economics

  • Protocol economicsNo sourceDefiLlama lists the protocol but tracks no fees, revenue or volume for it.

Not applicable here: Package advisories.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)DEX Screener (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-10-26 – 2026-11-01 · 3 commits

Code activitySource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

What changed, in the repository’s own words:

2 active days in nlyraproject/nlyra-platform.

This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:423f7c5b… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it to the week of 2026-10-27; HEY first knew on 2026-10-27.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

View evidence ↗ (opens in a new tab)

Shared change · Official source change

Neron Lyra's official site changed.

Links the official site declares changed: 1 added, 0 removed. Added repository link….

Observed by HEY on 2026-10-09Source: Project’s official site

View evidence ↗Evidence receipt

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 5 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-10-19 – 2026-10-25 · 2 commits

    Code activitySource-backed

    1 active day in nlyraproject/nlyra-platform.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 2 commits to see what changed: 2 documentation or maintenance only.

    View evidence: Code changes, week of 2026-10-19 – 2026-10-25 · 2 commits (opens in a new tab)

  2. Deployed a new contract: 0xe7b3…3264

    New contractSource-backed

    The account that launched Neron Lyra’s token deployed 0xe7b3…3264 on 2026-10-19. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xe7b3…3264 (opens in a new tab)

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in nlyraproject/nlyra-platform.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit (opens in a new tab)

  4. Code changes, week of 2026-09-28 – 2026-10-04 · 14 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    4 active days in nlyraproject/nlyra-platform.

    How HEY read this week

    This week HEY looked inside 1 of 14 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 14 commits (opens in a new tab)

  5. Deployed a new contract: LyraSlotsV2

    New contractSource-backed

    The account that launched Neron Lyra’s token deployed LyraSlotsV2 at 0xc185…80b3 on 2026-08-01. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: LyraSlotsV2 (opens in a new tab)

  6. Deployed a new contract: LyraSlots

    New contractSource-backed

    The account that launched Neron Lyra’s token deployed LyraSlots at 0xa114…b863 on 2026-08-01. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: LyraSlots (opens in a new tab)

  7. Deployed a new contract: LyraRouletteV2

    New contractSource-backed

    The account that launched Neron Lyra’s token deployed LyraRouletteV2 at 0x4556…0394 on 2026-08-01. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: LyraRouletteV2 (opens in a new tab)

  8. Deployed a new contract: 0xe2eb…24bf

    New contractSource-backed

    The account that launched Neron Lyra’s token deployed 0xe2eb…24bf on 2026-08-01. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xe2eb…24bf (opens in a new tab)
Earlier ships (3)

  1. 2 contracts deployed by the project’s deployer between 20:10:47 and 20:11:32 UTC on 28 Jul

    New contract

    Show all 2 contracts

    1. Deployed a new contract: UniswapV2Router02

      New contractSource-backed

      The account that launched Neron Lyra’s token deployed UniswapV2Router02 at 0xa5de…b6b6 on 2026-07-28. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: UniswapV2Router02 (opens in a new tab)

    2. Deployed a new contract: UniswapV2Factory

      New contractSource-backed

      The account that launched Neron Lyra’s token deployed UniswapV2Factory at 0xfa62…82a8 on 2026-07-28. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: UniswapV2Factory (opens in a new tab)

  2. Deployed a new contract: StakingRewards

    New contractSource-backed

    The account that launched Neron Lyra’s token deployed StakingRewards at 0x5e63…a3ef on 2026-07-28. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: StakingRewards (opens in a new tab)

Other changes on HEY’s record

19 changes on HEY’s record for Neron Lyra: 3 official source changes · 1 new project on HEY · 8 contract changes · 3 market moves · 4 other changes in 1 more kind.

All 19 changes for Neron Lyra →

The full change record holds 16 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.

Contract 0xB9d3824149aD8ac984153CeEc91D5a2405d1FB95 on Robinhood Chain

0xb9d3…fb950xb9d3824149ad8ac984153ceec91d5a2405d1fb95

Project names this contract.

Market context

Active market · FDV (fully diluted) $285K · current liquidity $55.1K · reading 1 h old (DEX Screener).

Token

Launch stage
Trading in a DEX pool
Pair age
3mo ago

Market

24h volume
$1.1K
Trades 24h
1 buys · 7 sells
Price 24h
down 5.4 percent over 24 hours· 6hdown 4.2 percent over 6 hours

The tracked token has liquidity, and trading volume was read for it within a day of its newest market reading — in that reading, or in HEY’s record of on-chain trades.

Market history, trading and checks →

Market integrity

Liquidity is 17% below the level it held two days running ($66.5K, 2026-10-25).

Market
Active market
Last day with trading
2026-11-10

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-11-11 18:55 UTC · How HEY checks this

Sources

8 places HEY reads for Neron Lyra

Security context: 5 audit reports found · bug bounty page on the project’s site. An audit shows an audit took place; it is not a guarantee of safety.