Skip to content
Menu

SDK Monorepo

No narrative yet

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 →

What HEY knows

Building
Last shipped 3 days agoShipping: 8 meaningful events in 30 days; latest ship 3 days ago. Evidence Source

Build Momentum 63How it is measured

Latest ship
@defuse-protocol/intents-sdk@0.93.0 · · GitHub release

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

Latest change
Derived3 days ago: 3 meaningful ships in the 7 days to 23 Oct, 1 the 7 days before. Evidence

HEY’s own reading

What this change is
What it names
HEY’s own reading names no capability.
Stage
HEY’s own reading of the record, not something the project shipped.
Reported by
HEY’s reading of the record. HEY’s own reading of the record: nothing to corroborate.
Release and deployment
Not a release or 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 2026-10-23; HEY first knew on 2026-10-23.
Not known
  • No source HEY holds names what this change does.

Evidence: signal 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.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts SDK Monorepo 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 SDK Monorepo’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 (no source), API description (no source), Official site changes (no source). No official website on record.

HEY can answer 8 of the 11 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
Shipping.
“Shipping” by the activity rule: 8 meaningful events in the last 30 days, the newest 2026-10-23.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecords@defuse-protocol/intents-sdk@0.93.0Code changes, week of 2026-10-19 – 2026-10-25 · 3 commits@defuse-protocol/intents-sdk@0.92.0+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".
Researched.
HEY researched this project; the gate has not found verified building evidence from its own sources.
Source1 registered source, 0 of them context only.ReadRecords@defuse-protocol/intents-sdk@0.93.0Code changes, week of 2026-10-19 – 2026-10-25 · 3 commits@defuse-protocol/intents-sdk@0.92.0+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
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

@defuse-protocol/intents-sdk@0.93.0

GitHub releaseSource verified

Minor Changes · 28de6a0: Pearl (PRL) PoA Support Patch Changes · Updated dependencies [28de6a0] · @defuse-protocol/internal-utils@0.44.0 Show all
  • Minor Changes
  • 28de6a0: Pearl (PRL) PoA Support Patch Changes
  • Updated dependencies [28de6a0]
  • @defuse-protocol/internal-utils@0.44.0

Record ship:ec84c792… · 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 · Release

SDK Monorepo shipped defuse-protocol/intents-sdk0.92.0.

8 meaningful development events were recorded in the last 30 days. Builder status: Shipping.

Dated 2026-10-21 by the sourceSource: GitHub

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: a week before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about SDK Monorepo — as of 26 Oct

Is SDK Monorepo still being built?
DerivedShipping: 8 meaningful events in 30 days; latest ship 3 days ago. Evidence
What did SDK Monorepo ship last?
Fact@defuse-protocol/intents-sdk@0.93.0 — GitHub release, 3 days ago. Evidence
What does HEY not know about SDK Monorepo?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

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

  1. 2 releases in defuse-protocol/sdk-monorepo on 23 Oct

    GitHub release

    Show all 2 releases

    1. @defuse-protocol/crosschain-assetid@1.15.0

      GitHub releaseSource verified

      Minor Changes · 28de6a0: Pearl (PRL) PoA Support Show all
      • Minor Changes
      • 28de6a0: Pearl (PRL) PoA Support
      View evidence: @defuse-protocol/crosschain-assetid@1.15.0 (opens in a new tab)

    2. @defuse-protocol/internal-utils@0.44.0

      GitHub releaseSource verified

      Minor Changes · 28de6a0: Pearl (PRL) PoA Support Show all
      • Minor Changes
      • 28de6a0: Pearl (PRL) PoA Support
      View evidence: @defuse-protocol/internal-utils@0.44.0 (opens in a new tab)

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

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in defuse-protocol/sdk-monorepo.

    How HEY read this week

    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. 3 automated commits (bot accounts or a repeating scripted message) not counted.

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

  3. 4 releases in defuse-protocol/sdk-monorepo on 21 Oct

    GitHub release

    Show all 4 releases

    1. @defuse-protocol/intents-sdk@0.92.0

      GitHub releaseSource verified

      Minor Changes · 3e7a500: Adjust Miden validate address to accept only bech32 Show all
      • Minor Changes
      • 3e7a500: Adjust Miden validate address to accept only bech32
      View evidence: @defuse-protocol/intents-sdk@0.92.0 (opens in a new tab)

    2. @defuse-protocol/crosschain-assetid@1.14.0

      GitHub releaseSource verified

      Minor Changes · 15956e3: Support Miden in PoA Show all
      • Minor Changes
      • 15956e3: Support Miden in PoA
      View evidence: @defuse-protocol/crosschain-assetid@1.14.0 (opens in a new tab)

    3. @defuse-protocol/internal-utils@0.43.0

      GitHub releaseSource verified

      Minor Changes · 15956e3: Support Miden in PoA Show all
      • Minor Changes
      • 15956e3: Support Miden in PoA
      View evidence: @defuse-protocol/internal-utils@0.43.0 (opens in a new tab)

    4. @defuse-protocol/intents-sdk@0.91.0

      GitHub releaseSource verified

      Minor Changes · 15956e3: Support Miden in PoA Patch Changes · Updated dependencies [15956e3] · @defuse-protocol/internal-utils@0.43.0 Show all
      • Minor Changes
      • 15956e3: Support Miden in PoA Patch Changes
      • Updated dependencies [15956e3]
      • @defuse-protocol/internal-utils@0.43.0
      View evidence: @defuse-protocol/intents-sdk@0.91.0 (opens in a new tab)

  4. @defuse-protocol/intents-sdk@0.90.0

    GitHub releaseSource verified

    Minor Changes · d4263ef: Reworked prefunded withdrawal fees configuration. When fees are prefunded, the account already holds the fee asset (e.g. NEAR, or the destination chain's native token for HOT Bridge), so the SDK skips quoting withdrawal fees. · bridgeConfigs now supports… Show all
    • Minor Changes
    • d4263ef: Reworked prefunded withdrawal fees configuration. When fees are prefunded, the account already holds the fee asset (e.g. NEAR, or the destination chain's native token for HOT Bridge), so the SDK skips quoting withdrawal fees.
    • bridgeConfigs now supports RouteEnum.HotBridge, RouteEnum.OmniBridge, RouteEnum.NearWithdrawal and RouteEnum.VirtualChain.
    • Added bridgeConfigs[route].feesPrefunded — prefunds fees for all tokens on the route, overriding prefundedFeesTokens. BREAKING CHANGES: Renamed bridgeConfigs[route].prefundedNativeFeeTokens to…
    View evidence: @defuse-protocol/intents-sdk@0.90.0 (opens in a new tab)

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

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in defuse-protocol/sdk-monorepo.

    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. 2 automated commits (bot accounts or a repeating scripted message) not counted.

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

  6. 2 releases in defuse-protocol/sdk-monorepo on 5 Oct

    GitHub release

    Show all 2 releases

    1. @defuse-protocol/intents-sdk@0.89.0

      GitHub releaseSource verified

      Minor Changes · 28f7e5b: Support prefunded tokens for Near Withdrawal via Bridge Config, also change Quantus PoA network reference. · Added bridgeConfigs[RouteEnum.NearWithdrawal].prefundedNativeFeeTokens — asset IDs whose withdrawal storage deposit fee is prefunded. · Changed… Show all
      • Minor Changes
      • 28f7e5b: Support prefunded tokens for Near Withdrawal via Bridge Config, also change Quantus PoA network reference.
      • Added bridgeConfigs[RouteEnum.NearWithdrawal].prefundedNativeFeeTokens — asset IDs whose withdrawal storage deposit fee is prefunded.
      • Changed Quantus PoA network reference from quantus:mainnet to qtc:mainnet. CAIP-2 identifier (Chains.Qtc) remains quantus:mainnet. Patch Changes
      • Updated dependencies [28f7e5b]
      • @defuse-protocol/internal-utils@0.42.0
      View evidence: @defuse-protocol/intents-sdk@0.89.0 (opens in a new tab)

    2. @defuse-protocol/internal-utils@0.42.0

      GitHub releaseSource verified

      Minor Changes · 28f7e5b: Support prefunded tokens for Near Withdrawal via Bridge Config, also change Quantus PoA network reference. · Added bridgeConfigs[RouteEnum.NearWithdrawal].prefundedNativeFeeTokens — asset IDs whose withdrawal storage deposit fee is prefunded. · Changed… Show all
      • Minor Changes
      • 28f7e5b: Support prefunded tokens for Near Withdrawal via Bridge Config, also change Quantus PoA network reference.
      • Added bridgeConfigs[RouteEnum.NearWithdrawal].prefundedNativeFeeTokens — asset IDs whose withdrawal storage deposit fee is prefunded.
      • Changed Quantus PoA network reference from quantus:mainnet to qtc:mainnet. CAIP-2 identifier (Chains.Qtc) remains quantus:mainnet.
      View evidence: @defuse-protocol/internal-utils@0.42.0 (opens in a new tab)

  7. @defuse-protocol/intents-sdk@0.88.1

    GitHub releaseSource verified

    Patch Changes · e00418b: Delimit DirectBridge storage-deposit cache key so distinct (contract, account) pairs can't collide. Show all
    • Patch Changes
    • e00418b: Delimit DirectBridge storage-deposit cache key so distinct (contract, account) pairs can't collide.
    View evidence: @defuse-protocol/intents-sdk@0.88.1 (opens in a new tab)

  8. Code changes, week of 2026-09-28 – 2026-10-04 · 1 commit

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in defuse-protocol/sdk-monorepo.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 1 commit (opens in a new tab)
Earlier ships (11)

  1. @defuse-protocol/intents-sdk@0.88.0

    GitHub releaseSource verified

    Minor Changes · f354fb5: HyperCore withdrawals support via Omni Bridge Show all
    • Minor Changes
    • f354fb5: HyperCore withdrawals support via Omni Bridge
    View evidence: @defuse-protocol/intents-sdk@0.88.0 (opens in a new tab)

  2. Code changes, week of 2026-09-21 – 2026-09-27 · 1 commit

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in defuse-protocol/sdk-monorepo.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 1 commit (opens in a new tab)

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

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in defuse-protocol/sdk-monorepo.

    How HEY read this week

    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. 3 automated commits (bot accounts or a repeating scripted message) not counted.

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

  4. 3 releases in defuse-protocol/sdk-monorepo on 18 Sep

    GitHub release

    Show all 3 releases

    1. @defuse-protocol/intents-sdk@0.87.0

      GitHub releaseSource verified

      Minor Changes · 68cc672: Add support for Arc chain (arc-prefixed tokens, chain id 5042) Patch Changes · Updated dependencies [68cc672] · @defuse-protocol/internal-utils@0.41.0 Show all
      • Minor Changes
      • 68cc672: Add support for Arc chain (arc-prefixed tokens, chain id 5042) Patch Changes
      • Updated dependencies [68cc672]
      • @defuse-protocol/internal-utils@0.41.0
      View evidence: @defuse-protocol/intents-sdk@0.87.0 (opens in a new tab)

    2. @defuse-protocol/crosschain-assetid@1.13.0

      GitHub releaseSource verified

      Minor Changes · 68cc672: Add support for Arc chain (arc-prefixed tokens, chain id 5042) Show all
      • Minor Changes
      • 68cc672: Add support for Arc chain (arc-prefixed tokens, chain id 5042)
      View evidence: @defuse-protocol/crosschain-assetid@1.13.0 (opens in a new tab)

    3. @defuse-protocol/internal-utils@0.41.0

      GitHub releaseSource verified

      Minor Changes · 68cc672: Add support for Arc chain (arc-prefixed tokens, chain id 5042) Show all
      • Minor Changes
      • 68cc672: Add support for Arc chain (arc-prefixed tokens, chain id 5042)
      View evidence: @defuse-protocol/internal-utils@0.41.0 (opens in a new tab)

  5. 3 releases in defuse-protocol/sdk-monorepo on 17 Sep

    GitHub release

    Show all 3 releases

    1. @defuse-protocol/intents-sdk@0.86.0

      GitHub releaseSource verified

      Minor Changes · 35f3663: Quantus PoA Support Patch Changes · Updated dependencies [35f3663] · @defuse-protocol/internal-utils@0.40.0 Show all
      • Minor Changes
      • 35f3663: Quantus PoA Support Patch Changes
      • Updated dependencies [35f3663]
      • @defuse-protocol/internal-utils@0.40.0
      View evidence: @defuse-protocol/intents-sdk@0.86.0 (opens in a new tab)

    2. @defuse-protocol/crosschain-assetid@1.12.0

      GitHub releaseSource verified

      Minor Changes · 35f3663: Quantus PoA Support Show all
      • Minor Changes
      • 35f3663: Quantus PoA Support
      View evidence: @defuse-protocol/crosschain-assetid@1.12.0 (opens in a new tab)

    3. @defuse-protocol/internal-utils@0.40.0

      GitHub releaseSource verified

      Minor Changes · 35f3663: Quantus PoA Support Show all
      • Minor Changes
      • 35f3663: Quantus PoA Support
      View evidence: @defuse-protocol/internal-utils@0.40.0 (opens in a new tab)

  6. @defuse-protocol/intents-sdk@0.85.1

    GitHub releaseSource verified

    Patch Changes · 073495f: Improve zcash transparent address validation Show all
    • Patch Changes
    • 073495f: Improve zcash transparent address validation
    View evidence: @defuse-protocol/intents-sdk@0.85.1 (opens in a new tab)

  7. @defuse-protocol/internal-utils@0.39.0

    GitHub releaseSource verified

    Minor Changes · 341898a: Rename robinhood to hood to match deployed token prefix Show all
    • Minor Changes
    • 341898a: Rename robinhood to hood to match deployed token prefix
    View evidence: @defuse-protocol/internal-utils@0.39.0 (opens in a new tab)

What changed

61 changes on HEY’s record for SDK Monorepo: 52 releases · 3 build pace changes · 6 weeks of code pushed.

All 61 changes for SDK Monorepo →

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 8 of the 11 research questions that apply.

8 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 48d ago.

Building

  • Building activityMeasuredRead 48m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 3d ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesMeasuredRead 39m ago.
  • Package advisoriesMeasuredRead 6d ago.

Not applicable here: 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