Skip to content
Menu

Liquihood Dev

Dev Tools

Is this your project? Claim and verify →

Liquihood smart contracts. Full lending protocol with isolated markets, kinked interest rates, health factor engine, and on-chain name registry. Deployed on Robinhood Chain (Chain ID 4663).

What HEY knows

Building
Dormant: no ship for 96 daysDormant: 0 meaningful events in 30 days; latest ship on 2026-07-14. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-07-13 – 2026-07-19 · at least 3 commits · · Code activity

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

FollowCreate alertTerminal previewView latest ship
Share

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

No account? Email me Liquihood Dev’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.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer.

HEY can answer 7 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Dormant.
“Dormant” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-07-14.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-07-13 – 2026-07-19 · at least 3 commitsCode changes, week of 2026-07-06 – 2026-07-12 · at least 1 commitDeployed a new contract: 0x22ac…bf9a+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Dormant”.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 verified building evidence from the project's own sources.
Source6 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-07-13 – 2026-07-19 · at least 3 commitsCode changes, week of 2026-07-06 – 2026-07-12 · at least 1 commitDeployed a new contract: 0x22ac…bf9a+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.
Market figures are context only and never change activity status. Methodology
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-07-13 – 2026-07-19 · at least 3 commitsliquihood-dev/liquihood

Code activitySource linked

What changed, in the repository’s own words:

1 active day in Liquihood-dev/liquihood.

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:9a778c34… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Builder activity

No meaningful, source-backed updates in the 7 weeks since HEY began reading this project’s sources; earlier weeks are not yet read.

Questions HEY can answer about Liquihood Dev — as of 2026-10-18

Is Liquihood Dev still being built?
DerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-07-14. Evidence
What did Liquihood Dev ship last?
FactCode changes, week of 2026-07-13 – 2026-07-19 · at least 3 commits — Code activity, on 2026-07-14. Evidence
What does HEY not know about Liquihood Dev?
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer. Details

Build timeline

  1. Code changes, week of 2026-07-06 – 2026-07-12 · at least 1 commitliquihood-dev/liquihood-contracts

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in Liquihood-dev/liquihood-contracts.

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

    View evidence

  2. Code changes, week of 2026-07-06 – 2026-07-12 · at least 1 commitliquihood-dev/liquihood-cli

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in Liquihood-dev/liquihood-cli.

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

    View evidence

  3. Code changes, week of 2026-07-06 – 2026-07-12 · at least 1 commitliquihood-dev/liquihood-app

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in Liquihood-dev/liquihood-app.

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

    View evidence

  4. Deployed a new contract: 0x22ac…bf9a

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0x22ac…bf9a on 2026-06-29. Read from the chain; the creating transaction is the evidence.

    View evidence

  5. Deployed a new contract: 0x3eb3…f852

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0x3eb3…f852 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  6. Deployed a new contract: 0xd4cc…d007

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0xd4cc…d007 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  7. Deployed a new contract: 0xffb4…6265

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0xffb4…6265 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  8. Deployed a new contract: 0x3e33…3e2f

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0x3e33…3e2f on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  9. Deployed a new contract: 0xe4a5…0272

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0xe4a5…0272 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  10. Deployed a new contract: 0x43e4…c2d4

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0x43e4…c2d4 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  11. Deployed a new contract: 0xf0a8…1675

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0xf0a8…1675 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  12. Deployed a new contract: 0x5b56…fa8c

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0x5b56…fa8c on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  13. Deployed a new contract: 0xd851…21e7

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0xd851…21e7 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  14. Deployed a new contract: 0x581f…419b

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0x581f…419b on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  15. Deployed a new contract: 0xf36f…66e8

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0xf36f…66e8 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  16. Deployed a new contract: 0xbaf5…f06c

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0xbaf5…f06c on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  17. Deployed a new contract: 0xca63…6081

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0xca63…6081 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  18. Deployed a new contract: FRouterV3

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed FRouterV3 at 0x2339…9d7d on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  19. Deployed a new contract: TransparentUpgradeableProxy

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed TransparentUpgradeableProxy at 0xfc2e…20a9 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  20. Deployed a new contract: 0x38b1…356f

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed 0x38b1…356f on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  21. Deployed a new contract: TransparentUpgradeableProxy

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed TransparentUpgradeableProxy at 0x6d80…1ce7 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  22. Deployed a new contract: AgentTaxV2

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed AgentTaxV2 at 0x4d4e…01bb on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  23. Deployed a new contract: TransparentUpgradeableProxy

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed TransparentUpgradeableProxy at 0x4008…d8d0 on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

  24. Deployed a new contract: AgentNftV2

    New contractSource verified

    The account that launched Liquihood-dev’s token deployed AgentNftV2 at 0x5967…c0af on 2026-06-25. Read from the chain; the creating transaction is the evidence.

    View evidence

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about Liquihood Dev? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

28 changes on HEY’s record for Liquihood Dev: 24 contract changes · 4 weeks of code pushed.

All 28 changes for Liquihood Dev →

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

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 2d ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsSource unavailableIts website did not answer.
  • API descriptionSource unavailableIts website did not answer.
  • Official site changesSource unavailableIts website did not answer.

Code and packages

  • Repository detailsMeasuredRead 5d ago.
  • Published packagesMeasuredRead 5d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, 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.

Sources