Skip to content
Menu

Ipor ABI

Dev Tools

Integration record: a multichain project that lists Robinhood Chain. Its code is filed under other ecosystems and HEY holds no Robinhood Chain evidence of its own, so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim and verify →

IPOR Protocol ABIs and addresses from Mainnet and public testnets

What HEY knows

Building
Quiet for 47 daysQuiet: 0 meaningful events in 30 days; latest ship on 2026-09-02. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-08-31 – 2026-09-06 · at least 1 commit · · Code activity

Why it matters: The first week of code changes HEY has recorded for this project.

Latest change
Fact4 days ago: Links the official site declares changed: 0 added, 1 removed. Removed docs link: docs.ipor.io/resources/resources. Evidence Source
FollowCreate alertTerminal previewView latest ship
Share

Follow puts Ipor ABI 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 Ipor ABI’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
Unknown2 gaps: API description (no source), Official site changes (stale). Its website links no API description.

HEY can answer 8 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
Quiet.
“Quiet” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-09-02.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06 · at least 1 commitWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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".
Researched.
HEY researched this project; the gate has not found verified building evidence from its own sources.
Source66 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06 · at least 1 commitsource:5629b0bd-92f4-4b71-ab7c-6b6046c6bc82source:6c5ec7d0-24ef-442c-83c0-fb2f176ecf0d+3 moreWhat HEY derivedThe quality gate’s stored decision: “Researched”.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-08-31 – 2026-09-06 · at least 1 commit

Code activitySource linked

What changed, in the repository’s own words:

14 active days in IPOR-Labs/ipor-abi.

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

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

View evidence ↗

Shared change · Official source change

Ipor ABI's official site changed.

Links the official site declares changed: 3 added, 1 removed. Added docs link….

Observed by HEY on 2026-10-02Source: 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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Ipor ABI — as of 2026-10-19

Is Ipor ABI still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship on 2026-09-02. Evidence
What did Ipor ABI ship last?
FactCode changes, week of 2026-08-31 – 2026-09-06 · at least 1 commit — Code activity, on 2026-09-02. Evidence
What does HEY not know about Ipor ABI?
Unknown2 gaps: API description (no source), Official site changes (stale). Its website links no API description. Details

Build timeline

  1. Code changes, week of 2026-10-12 – 2026-10-18 · 2 commits

    Code activitySource linked

    2 active days in ipor-labs/ipor-abi.

    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-12 – 2026-10-18 · 2 commits (opens in a new tab)

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

    Code activitySource linked

    1 active day in ipor-labs/ipor-abi.

    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-09-28 – 2026-10-04 · 2 commits (opens in a new tab)

  3. Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits

    Code activitySource linked

    2 active days in ipor-labs/ipor-abi.

    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-09-21 – 2026-09-27 · 2 commits (opens in a new tab)

  4. Code changes, week of 2026-09-14 – 2026-09-20 · at least 3 commits

    Code activitySource linked

    2 active days in ipor-labs/ipor-abi.

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

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 3 commits (opens in a new tab)

  5. Fusion x Blockaid: Bringing Onchain Threat Monitoring to Fusion Vaults

    AnnouncementSource linked

    Fusion has begun integrating Blockaid across its vault stack. Monitoring and post-transaction analysis are live for a selection of ecosystem vaults, with proactive detection in development.

    View evidence: Fusion x Blockaid: Bringing Onchain Threat Monitoring to Fusion Vaults (opens in a new tab)

  6. Covered Vaults Come to Fusion: Embedded Onchain Protection by OpenCover

    AnnouncementSource linked

    Onchain cover is now available for select Fusion vaults, provided by OpenCover and underwritten by Nexus Mutual, starting with a Covered Vault for the Liquity ETH Carry strategy.

    View evidence: Covered Vaults Come to Fusion: Embedded Onchain Protection by OpenCover (opens in a new tab)

  7. BitGo Opens Institutional Access to Tesseract's Dedicated Client Vaults Powered by Fusion

    AnnouncementSource linked

    Eligible institutions can now allocate to Tesseract's Dedicated Client Vaults, powered by Fusion, directly from BitGo qualified custody, with assets staying inside the custodial perimeter.

    View evidence: BitGo Opens Institutional Access to Tesseract's Dedicated Client Vaults Powered by Fusion (opens in a new tab)

  8. How Vault Curators Can Navigate MiCA in 2026

    AnnouncementSource linked

    At Vault Summit during EthCC Cannes 2026, Stéphane Daniel of d&a partners laid out the MiCA legal considerations for vault curators, from CASP reclassification risk to three structuring strategies. A guest article, with a note on how Fusion's architecture relates.

    View evidence: How Vault Curators Can Navigate MiCA in 2026 (opens in a new tab)

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 Ipor ABI? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

14 changes on HEY’s record for Ipor ABI: 5 official source changes · 4 other ships · 5 weeks of code pushed.

  • Official source changed4d ago · 4 official source changes

    Links the official site declares changed: 0 added, 1 removed. Removed docs link: docs.ipor.io/resources/resources

    See the change Source ↗

  • Code pushed5d ago

    Code changes, week of 2026-10-12 – 2026-10-18 · 2 commits

    See the change Source ↗

  • Official source changed17d ago

    Links the official site declares changed: 3 added, 1 removed. Added docs link: docs.ipor.io/dao-governance/dao-governance/fusion-dao-governance; docs link: docs.ipor.io/ipor-derivatives; docs link: docs.ipor.io/resources. Removed docs link: docs.ipor.io/llms.txt

    See the change Source ↗

  • Code pushed21d ago

    Code changes, week of 2026-09-28 – 2026-10-04 · 2 commits

    See the change Source ↗

  • Code pushed24d ago

    Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits

    See the change Source ↗

All 14 changes for Ipor ABI →

The full change record holds 66 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 8 of the 10 research questions that apply.

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

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

Official site

  • Official docsMeasuredRead 2d ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesStaleThe last read of its website’s files is out of date.

Code and packages

  • Repository detailsMeasuredRead 1d ago.
  • Published packagesMeasuredRead 1d 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

61 more sources (docs)

Security context: 2 audit reports found · bug bounty on Immunefi. An audit shows an audit took place; it is not a guarantee of safety.