Skip to content
HEY Research Lab
Menu

Liege Agents

$LIEGE

AI Agents · Utility

Not named by the project: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Token market

Contract 0xc32ab2e562ade6fba6d3d1e3960d49b0957ef645

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

Is this your project? Claim it →

Liege gives agent work a real transaction layer on Robinhood Chain. Clients define the scope, deadline, acceptance criteria, and evaluator before funding a job in USDG escrow. Agents deliver privately, evaluators settle against the agreed brief, and payment follows the outcome. Liege is built around clear work agreements, encrypted job data, and accountability for agent services, with portable reputation and client-controlled strategy wallets forming the next layer.

Read more

What HEY knows

Development

Shipping consistentlyShipping: 5 counted ships in 30 days; latest ship 4 days ago. Evidence Source

Build Momentum 51How it is measured

Latest: Code changes this week (since Mon 9 Nov) · 6 commits

Token market · context

Active marketTracked token: $15K market cap

Token check

Not named by the project
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Liege Agents 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 Liege Agents

No account? Email me Liege Agents’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 97.3% of them, its market attention ahead of 71.1% (a gap of 26.2). 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
Fact1 of 1 watched contract active · 795 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.

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

Contracts
Fact1 contract on record for code changes, 1 with published source code; no implementation or interface change recorded.
Not yet known
Unknown3 gaps: Official docs (not tied to the project yet), API description (not tied to the project yet), Official site changes (not tied to the project yet). Only docs others link to; none the project publishes itself.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 5 counted ships in the last 30 days, the newest 2026-11-11.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 9 Nov) · 6 commitsCode changes, week of 2026-11-02 – 2026-11-08 · 10 commitsCode changes, week of 2026-10-26 – 2026-11-01 · 19 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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.
Source6 registered sources, 2 of them context only.ReadRecordsCode changes this week (since Mon 9 Nov) · 6 commitsCode changes, week of 2026-11-02 – 2026-11-08 · 10 commitsCode changes, week of 2026-10-26 – 2026-11-01 · 19 commits+6 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.
Not named by the project.
Not named by the project: HEY has not confirmed that the project stands behind this contract — HEY knows it from a launchpad record, and the site that record named does not name it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedNot named by the project: HEY knows it from a launchpad record, and the site that record named does not name 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.
Source8 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 20 research questions that apply.
17 of 20 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead just now.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 36d ago.
  • TimelineMeasured

Official site

  • Official docsNot tied to the project yetOnly docs others link to; none the project publishes itself.
  • API descriptionNot tied to the project yetIts website is not yet confirmed as the project’s own.
  • Official site changesNot tied to the project yetIts website is not yet confirmed as the project’s own.

Code and packages

  • Repository detailsMeasuredRead 1d ago.
  • Published packagesMeasuredRead 1d ago.
  • Package advisoriesMeasuredRead 1d ago.

Contracts

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

Market

  • Current marketMeasuredRead 6m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead yesterday.
  • LocksMeasuredRead 6m ago.
  • Market checksMeasured

Not applicable here: 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 (context only) (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 this week (since Mon 9 Nov) · 6 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 liegeagents/liegeagentsapp.

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

Record ship:a789bcc8… · 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-11-11; HEY first knew on 2026-11-10.
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)

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-11-02 – 2026-11-08 · 10 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    4 active days in liegeagents/liegeagentsapp.

    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-11-02 – 2026-11-08 · 10 commits (opens in a new tab)

  2. Code changes, week of 2026-10-26 – 2026-11-01 · 19 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in liegeagents/liegeagentsapp.

    How HEY read this week

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

  3. Code changes, week of 2026-10-19 – 2026-10-25 · 35 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in liegeagents/liegeagentsapp.

    How HEY read this week

    This week HEY looked inside 3 of 35 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

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

  4. Code changes, week of 2026-10-12 – 2026-10-18 · 32 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in liegeagents/liegeagentsapp.

    How HEY read this week

    This week HEY looked inside 3 of 32 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 32 commits (opens in a new tab)

  5. Code changes, week of 2026-10-05 – 2026-10-11 · 36 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in liegeagents/liegeagentsapp.

    How HEY read this week

    This week HEY looked inside 3 of 36 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

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

  6. android-v0.1.3

    GitHub releaseSource-backed

    Full Changelog: https://github.com/LiegeAgents/LiegeAgentsApp/compare/backend-202610101958-d9a280d...android-v0.1.3

    View evidence: android-v0.1.3 (opens in a new tab)

  7. Code changes, week of 2026-09-28 – 2026-10-04 · at least 257 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 3 active days in liegeagents/liegeagentsapp since 2026-10-02; the count stops at the newest 100 commits listed.

    How HEY read this week

    This week HEY looked inside 3 of 257 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

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

  8. android-v0.1.2

    GitHub releaseSource-backed

    Full Changelog: https://github.com/LiegeAgents/LiegeAgentsApp/compare/backend-202610031318-228860c...android-v0.1.2

    View evidence: android-v0.1.2 (opens in a new tab)

Other changes on HEY’s record

19 changes on HEY’s record for Liege Agents: 2 releases · 2 new Verified Builders or owner proofs · 1 market check · 1 new project on HEY · 13 other changes in 3 more kinds.

All 19 changes for Liege Agents →

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

Around a recent ship: the market and product usage the week either side, on the market page →

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

Contract 0xc32Ab2e562adE6fBa6D3d1E3960d49b0957Ef645 on Robinhood Chain

0xc32a…f6450xc32ab2e562ade6fba6d3d1e3960d49b0957ef645

Not named by the project.

Market context

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

Token

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

Market

Fully diluted valuation
$16K
24h volume
$1.2K
Trades 24h
8 buys · 7 sells
Price 24h
down 1.2 percent over 24 hours· 6hdown 15.2 percent over 6 hours· 1hdown 16.7 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 80% below the level it held two days running ($56.6K, 2026-10-04).

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

Liquidity is under 25% of the level it held, on two consecutive daily readings to 2026-11-15.

  1. seen 2026-10-14Trading fell from 4,102 trades a day (the seven days to 2026-10-05) to 46 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-15 12:55 UTC · How HEY checks this

Sources

6 places HEY reads for Liege Agents