Skip to content
HEY Research Lab
Menu

Loom

$LOOM

AI Agents

Contract 0xdd0c034dada72325bc893fa39bc392e82bf847d7

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

Is this your project? Claim it →

LoomDesk is a liquidity app and market for everything that trades on Robinhood Chain: provide liquidity to tokenized stocks and tokens in Uniswap v3 and v4 pools, or open your own pool on LoomDesk's v4 hook and take a royalty on every swap.

Read more

What HEY knows

Development

Shipping consistentlyActive: 25 counted ships in 30 days; latest ship 8 days ago. Evidence Source

Build Momentum 84How it is measured

Latest: 0.7.1

Token market · context

Active market$94K market cap

Token check

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

Get updates

Follow puts Loom 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 Loom

No account? Email me Loom’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 99.8% of them, its market attention ahead of 84% (a gap of 15.8). 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
Fact13 of 66 watched contracts active · 5,035 calls in 7 days (3,599 calls to the contracts' own functions; 1,436 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.

Contracts
Fact50 contracts on record for code changes, 1 with published source code; latest change 8 days ago: Deployed a new contract: 0x019a…7d5a. Source
Not yet known
Unknown2 gaps: Published packages (not enough yet), Official site changes (stale). Packages name its repository, but none is confirmed as the project’s own.
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: 25 counted ships in the last 30 days, the newest 2026-11-02.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecords0.7.1Code changes, week of 2026-11-02 – 2026-11-08 · 2 commitsDeployed a new contract: 0x019a…7d5a+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, 2 of them context only.ReadRecords0.7.1Code changes, week of 2026-11-02 – 2026-11-08 · 2 commitsDeployed a new contract: 0x019a…7d5a+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 17 of the 19 research questions that apply.
17 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 4h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 8d ago.
  • TimelineMeasured

Official site

  • Official docsMeasured
  • API descriptionMeasuredRead 36d ago.
  • Official site changesStaleThe last read of its website’s files is out of date.

Code and packages

  • Repository detailsMeasuredRead 3d ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Contracts

  • Contract creationMeasuredRead 16h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 2d ago.
  • Contract interfaceMeasuredRead 2d ago.

Market

  • Current marketMeasuredRead 59m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 1h ago.
  • Market checksMeasured

Not applicable here: Package advisories, Protocol economics.

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

0.7.1 loomdesk-hq/sdk

GitHub releaseSource-backed

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

0.7.1 (2026-11-02) Four low findings from Hey Research Lab's read of 0.7.0, all under the same threat model as before (a hostile plan reaching a trusted contract), none exploitable by LoomDesk's own plans, none seen on chain: · The router check accepted the router itself… Show all
  • 0.7.1 (2026-11-02) Four low findings from Hey Research Lab's read of 0.7.0, all under the same threat model as before (a hostile plan reaching a trusted contract), none exploitable by LoomDesk's own plans, none seen on chain:
  • The router check accepted the router itself (ADDRESS_THIS) as a recipient without asking whether the execute moved everything back out. A plan could wrap the wallet's ETH to the router, or pull tokens to it with Permit2, and end there: the router keeps no balances, so anyone sweeps them in the next transaction. Now every currency routed to the router must leave it…

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

View evidence ↗ (opens in a new tab)Post this ship on X

Shared change · Development spike

Loom: 5 meaningful ships were recorded in the latest 7 days, from 2 in the 7 days before.

Builder status: Active.

Dated 2026-11-05 by the sourceSource: HEY Signal

View evidence ↗Evidence receipt

What they’re building

LoomDesk is a liquidity app and market for everything that trades on Robinhood Chain. Anyone can provide liquidity to tokenized stocks and tokens in Uniswap v3 and v4 pools, or open their own pool on LoomDesk's Uniswap v4 hook and take a royalty on every swap. 3% of every LOOM trade goes into a book of protocol-owned liquidity, a LOOM/ETH pool whose fee is never under 4% and where arbitrage pays for the gap it closes. Most of what the book earns goes back into that pool, part of it buying LOOM; nothing is paid out to holders. (Earn was retired and payouts to LOOM holders ended on 24 September 2026.)

Read more

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: 3 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-11-02 – 2026-11-08 · 1 commit loomdesk-hq/mcp

    Code activitySource-backed

    1 active day in loomdesk-hq/mcp.

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

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

  2. Code changes, week of 2026-11-02 – 2026-11-08 · 2 commits loomdesk-hq/sdk

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in loomdesk-hq/sdk.

    How HEY read this week

    This week HEY looked inside 1 of 2 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-11-02 – 2026-11-08 · 2 commits (opens in a new tab)

  3. 0.7.0: the send gate reads where every call pays loomdesk-hq/sdk

    GitHub releaseSource-backed

    sendPlan and assertSendable now read where every call pays. A close, collect, withdrawal or open on LoomLadder, a PilotGas fill or withdrawal, a LoomStake withdrawal, and every command and v4 action of a Universal Router swap must name the wallet (or the router itself, inside a… Show all

    sendPlan and assertSendable now read where every call pays. A close, collect, withdrawal or open on LoomLadder, a PilotGas fill or withdrawal, a LoomStake withdrawal, and every command and v4 action of a Universal Router swap must name the wallet (or the router itself, inside a swap). Anything else is refused, as is a call to one of these contracts the SDK cannot read, or a router command LoomDesk's swaps never use (TRANSFER, PAY_PORTION). A give or a delegate goes only to an address named in the new recipients option. Before this, a plan to a trusted contract was sent whatever it…

    View evidence: 0.7.0: the send gate reads where every call pays (opens in a new tab)

  4. Deployed a new contract: 0x019a…7d5a

    New contractSource-backed

    The account that launched Loom’s token deployed 0x019a…7d5a on 2026-11-02. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x019a…7d5a (opens in a new tab)

  5. Code changes, week of 2026-10-26 – 2026-11-01 · 10 commits loomdesk-hq/sdk

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in loomdesk-hq/sdk.

    How HEY read this week

    This week HEY looked inside 1 of 10 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-10-26 – 2026-11-01 · 10 commits (opens in a new tab)

  6. Deployed a new contract: 0xb14f…65a4

    New contractSource-backed

    The account that launched Loom’s token deployed 0xb14f…65a4 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xb14f…65a4 (opens in a new tab)

  7. 3 contracts deployed by the project’s deployer between 17:44:48 and 17:44:55 UTC on 30 Oct

    New contract

    Show all 3 contracts

    1. Deployed a new contract: 0x3a56…ecde

      New contractSource-backed

      The account that launched Loom’s token deployed 0x3a56…ecde on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x3a56…ecde (opens in a new tab)

    2. Deployed a new contract: 0x6e29…1fff

      New contractSource-backed

      The account that launched Loom’s token deployed 0x6e29…1fff on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x6e29…1fff (opens in a new tab)

    3. Deployed a new contract: 0x792c…7afa

      New contractSource-backed

      The account that launched Loom’s token deployed 0x792c…7afa on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x792c…7afa (opens in a new tab)

  8. 7 contracts deployed by the project’s deployer between 16:00:01 and 16:01:59 UTC on 30 Oct

    New contract

    Show all 7 contracts

    1. Deployed a new contract: 0x066e…aca9

      New contractSource-backed

      The account that launched Loom’s token deployed 0x066e…aca9 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x066e…aca9 (opens in a new tab)

    2. Deployed a new contract: 0xc658…0162

      New contractSource-backed

      The account that launched Loom’s token deployed 0xc658…0162 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0xc658…0162 (opens in a new tab)

    3. Deployed a new contract: 0x4a0a…cb2c

      New contractSource-backed

      The account that launched Loom’s token deployed 0x4a0a…cb2c on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x4a0a…cb2c (opens in a new tab)

    4. Deployed a new contract: 0x96d6…8e01

      New contractSource-backed

      The account that launched Loom’s token deployed 0x96d6…8e01 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x96d6…8e01 (opens in a new tab)

    5. Deployed a new contract: 0xa3bf…8707

      New contractSource-backed

      The account that launched Loom’s token deployed 0xa3bf…8707 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0xa3bf…8707 (opens in a new tab)

    6. Deployed a new contract: 0x8f0b…9518

      New contractSource-backed

      The account that launched Loom’s token deployed 0x8f0b…9518 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x8f0b…9518 (opens in a new tab)

    7. Deployed a new contract: 0xb10a…67b2

      New contractSource-backed

      The account that launched Loom’s token deployed 0xb10a…67b2 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0xb10a…67b2 (opens in a new tab)
Earlier ships (8)

  1. 2 contracts deployed by the project’s deployer between 19:03:36 and 19:03:53 UTC on 27 Oct

    New contract

    Show all 2 contracts

    1. Deployed a new contract: 0x698c…fc32

      New contractSource-backed

      The account that launched Loom’s token deployed 0x698c…fc32 on 2026-10-27. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x698c…fc32 (opens in a new tab)

    2. Deployed a new contract: 0xf8b0…ecea

      New contractSource-backed

      The account that launched Loom’s token deployed 0xf8b0…ecea on 2026-10-27. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0xf8b0…ecea (opens in a new tab)

  2. Deployed a new contract: 0xd0da…3660

    New contractSource-backed

    The account that launched Loom’s token deployed 0xd0da…3660 on 2026-10-27. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xd0da…3660 (opens in a new tab)

  3. Deployed a new contract: 0x546b…006b

    New contractSource-backed

    The account that launched Loom’s token deployed 0x546b…006b on 2026-10-26. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x546b…006b (opens in a new tab)

  4. Code changes, week of 2026-10-19 – 2026-10-25 · 2 commits loomdesk-hq/sdk

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in loomdesk-hq/sdk.

    How HEY read this week

    This week HEY looked inside 1 of 2 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-10-19 – 2026-10-25 · 2 commits (opens in a new tab)

  5. 2 contracts deployed by the project’s deployer between 14:28:59 and 14:29:27 UTC on 20 Oct

    New contract

    Show all 2 contracts

    1. Deployed a new contract: 0x465a…00a6

      New contractSource-backed

      The account that launched Loom’s token deployed 0x465a…00a6 on 2026-10-20. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x465a…00a6 (opens in a new tab)

    2. Deployed a new contract: 0x72e5…f273

      New contractSource-backed

      The account that launched Loom’s token deployed 0x72e5…f273 on 2026-10-20. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x72e5…f273 (opens in a new tab)

  6. Deployed a new contract: 0xb120…0974

    New contractSource-backed

    The account that launched Loom’s token deployed 0xb120…0974 on 2026-10-20. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xb120…0974 (opens in a new tab)

Other changes on HEY’s record

163 changes on HEY’s record for Loom: 3 releases · 1 contract in use again or for the first time · 1 market check · 2 official source changes · 156 other changes in 5 more kinds.

All 163 changes for Loom →

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

Build through the drawdown

Down 72.3% from the HEY-tracked high, with 32 counted ships since.

0.7.1 — 8d agoCode changes, week of 2026-11-02 – 2026-11-08 — 8d agoCode changes, week of 2026-11-02 – 2026-11-08 — 8d ago0.7.0: the send gate reads where every call pays — 8d agoDeployed a new contract: 0x019a…7d5a — 8d agoCode changes, week of 2026-10-26 – 2026-11-01 — 11d agoDeployed a new contract: 0xb14f…65a4 — 11d agoDeployed a new contract: 0x3a56…ecde — 11d agoDeployed a new contract: 0x6e29…1fff — 11d agoDeployed a new contract: 0x792c…7afa — 11d agoDeployed a new contract: 0x066e…aca9 — 11d agoDeployed a new contract: 0xc658…0162 — 11d agoDeployed a new contract: 0x4a0a…cb2c — 11d agoDeployed a new contract: 0x96d6…8e01 — 11d agoDeployed a new contract: 0xa3bf…8707 — 11d agoDeployed a new contract: 0x8f0b…9518 — 11d agoDeployed a new contract: 0xb10a…67b2 — 11d agoDeployed a new contract: 0x698c…fc32 — 14d agoDeployed a new contract: 0xf8b0…ecea — 14d agoDeployed a new contract: 0xd0da…3660 — 14d agoDeployed a new contract: 0x546b…006b — 15d agoCode changes, week of 2026-10-19 – 2026-10-25 — 19d agoDeployed a new contract: 0x465a…00a6 — 21d agoDeployed a new contract: 0x72e5…f273 — 21d agoDeployed a new contract: 0xb120…0974 — 21d ago$611K
Valuation over time. Each marker is a meaningful ship.

A factual observation about past activity and market context. It is not a prediction, and not investment advice.

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

Contract 0xdd0C034DAdA72325BC893fA39bc392E82bF847D7 on Robinhood Chain

0xdd0c…47d70xdd0c034dada72325bc893fa39bc392e82bf847d7

Project names this contract.

Market context

Active market · market cap $93.8K · current liquidity $26.6K · reading under an hour old (DEX Screener).

Token

Launch stage
Trading in a DEX pool
Pair age
32d ago

Market

Fully diluted valuation
$102K
24h volume
$3.5K
Trades 24h
5 buys · 19 sells
Price 24h
down 29.1 percent over 24 hours· 6hdown 23.0 percent over 6 hours· 1hup 2.1 percent over 1 hour

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 69% below the level it held two days running ($101.9K, 2026-10-17).

Market
Active market
Last day with trading
2026-11-09
  1. seen 2026-10-27Trading fell from 698 trades a day (the seven days to 2026-09-26) to 18 a day in the seven days to 2026-11-10, in HEY's decoded on-chain trades.

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-10 12:59 UTC · How HEY checks this

Sources

8 places HEY reads for Loom

16 Uniswap v4 hooks HEY ties to this project · Builders shipping Uniswap v4 hooks