Skip to content
Menu

orbitflare

Dev Tools

Is this your project? Claim and verify →

Rust SDK for Robinhood Chain by OrbitFlare - alloy-typed RPC and WebSocket clients with retry, endpoint failover, and self-healing subscriptions.

What HEY knows

Building
Last shipped 34 days agoActive: 0 meaningful events in 30 days; latest ship 34 days ago. Evidence Source

Build Momentum 20How it is measured

Latest ship
Code changes, week of 2026-09-14 – 2026-09-20 · 1 commit · · Code activity

Why it matters: First week of code changes after 30 quiet days.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts orbitflare 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 orbitflare’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
Active.
“Active” by the activity rule's longer window: 2 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-14, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 1 commitInitial ReleaseCode changes, week of 2026-08-10 – 2026-08-16 · 1 commit+1 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 verified building evidence from the project's own sources.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 1 commitInitial ReleaseCode changes, week of 2026-08-10 – 2026-08-16 · 1 commit+4 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
LinksGitHubSources

Latest ship

Checked

Code changes, week of 2026-09-14 – 2026-09-20 · 1 commitorbitflare/orbitflare-evm-sdk-rs

Code activitySource linked

What changed, in the repository’s own words:

1 active day in orbitflare/orbitflare-evm-sdk-rs.

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

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

View evidence ↗

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 orbitflare — as of 2026-10-18

Is orbitflare still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 34 days ago. Evidence
What did orbitflare ship last?
FactCode changes, week of 2026-09-14 – 2026-09-20 · 1 commit — Code activity, 34 days ago. Evidence
What does HEY not know about orbitflare?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

  1. Initial Releaseorbitflare/orbitflare-evm-sdk-rs

    GitHub releaseSource verified

    orbitflare-evm-sdk v0.1.0 Rust SDK for OrbitFlare's EVM chains, built on alloy types with endpoint failover, retry, and self-healing WebSocket subscriptions. What's new: · Initial release. One generic client (RpcClient / WsClient ) across Polygon, BNB, and Robinhood Chain, with… Show all
    • orbitflare-evm-sdk v0.1.0 Rust SDK for OrbitFlare's EVM chains, built on alloy types with endpoint failover, retry, and self-healing WebSocket subscriptions. What's new:
    • Initial release. One generic client (RpcClient / WsClient ) across Polygon, BNB, and Robinhood Chain, with per-chain aliases
    • and custom chains via impl Chain for MyChain.
    • RPC, WebSocket (newHeads / logs / newPendingTransactions), and Polygon Bor gRPC, feature-gated as rpc / ws / grpc.
    • NitroBlockExt exposes Robinhood's Arbitrum Nitro block fields (l1_block_number, send_root…
    View evidence

  2. Code changes, week of 2026-08-10 – 2026-08-16 · 1 commitorbitflare/orbitflare-robinhood-sdk-rs

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in orbitflare/orbitflare-robinhood-sdk-rs.

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

    View evidence

  3. Initial Releaseorbitflare/orbitflare-robinhood-sdk-rs

    GitHub releaseSource verified

    orbitflare-robinhood-sdk v0.1.0 Added: · rpc and ws clients for Robinhood Chain, feature-gated (rpc default, ws, all). · Alloy types across the API: Address, U256, B256, Filter, TransactionRequest, with typed Block, Transaction, TransactionReceipt, Log, and Header returns.… Show all
    • orbitflare-robinhood-sdk v0.1.0 Added:
    • rpc and ws clients for Robinhood Chain, feature-gated (rpc default, ws, all).
    • Alloy types across the API: Address, U256, B256, Filter, TransactionRequest, with typed Block, Transaction, TransactionReceipt, Log, and Header returns.
    • Arbitrum-aware decoding via catch-all envelopes, so system transactions (internal, retryable, deposit) parse instead of erroring.
    • Typed WebSocket subscriptions: newHeads, logs, newPendingTransactions, with auto-resubscribe on reconnect.
    • Multi-endpoint failover with health…
    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 orbitflare? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

4 changes on HEY’s record for orbitflare: 2 releases · 2 weeks of code pushed.

orbitflare on What changed →

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 1mo ago.

Building

  • Building activityMeasuredRead 2h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1mo 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 5d ago.
  • Published packagesMeasuredRead 29m ago.
  • Package advisoriesMeasuredRead 29m 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