Skip to content
Menu

Blackforge

$BFORGE

No narrative yet

Contract 0xe1c078a09dc0e66feeaba67d6f16456b0c10c87b

HEY holds 7 other Robinhood Chain tokens that use $BFORGE. This page is only the contract above. See them

Is this your project? Claim and verify →

Hot Gpus. Cold country. NVDA H200s from a forge in Iceland, rented by the second, the hour bank or the whole node.

What HEY knows

Building
Shipped this weekShipping: 4 meaningful events in 30 days; latest ship yesterday. Evidence Source

Build Momentum 59How it is measured

Latest ship
F1 is built on NVIDIA B200 · · Feature release
Latest change
FactYesterday: Docs, API reference and the forge CLI. Evidence Source

Announcement, from the team’s own feed · not an implementation HEY has seen

What this change is
What it names
In the team’s words: “Docs, API reference and the forge CLI”.
Stage
An announcement is not an implementation: HEY has not observed code, a release or a deployment for it.
Reported by
From the team’s own feed. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to 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-24.
Not known
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.

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.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Blackforge 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 Blackforge’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
Discovery Gap not measured — market too thin. What the Discovery Gap is
Product usage
Fact1 of 1 watched contract active · 4 calls to the contracts' own functions over the 3 of 7 days HEY holds; the other 1,365 of 1,369 calls were ERC-20 token transfers and approvals, which trading alone produces; the rest unknown, not zero.

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

Contracts
Fact1 contract on record for code changes; no implementation or interface change recorded.
Token market · context
Launch pool only$4.1K fully diluted valuationToken verified
Not yet known
Unknown3 gaps: Repositories (no source), API description (no source), Contract interface (no source). No repository the project claims as its own.

HEY can answer 14 of the 17 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: 4 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.ReadRecordsChange log.F1 is built on NVIDIA B200Four plans, one price each+1 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 verified building evidence from the project's own sources.
Source10 registered sources, 0 of them context only.ReadRecordsF1 is built on NVIDIA B200Change log.Four plans, one price each+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.
Token verified.
Token verified: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedToken verified: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Launch pool only.
Launch pool only: the only pool is the launch pool holding the token’s own supply, and it traded in the last day.
Source9 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Launch pool only”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Discovery Gap: Not measured — market too thin.
Not measured — market too thin: the tracked token's market reads “Launch pool only”. A Discovery Gap is measured only on an active market that is more than a launch curve and trades at least $1,000 a day: a thin market's attention percentile sits near the floor, so its gap would measure the thinness, not the building.
SourceThe score row: the Build Momentum percentile and the market-attention percentile, both taken over the projects with a market reading.ReadWhat HEY derivedNot measured — market too thin.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)X (opens in a new tab)defined.fi (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Checked

F1 is built on NVIDIA B200

Feature releaseSource linked

Each node is an HGX B200: eight Blackwell GPUs with 180 GB of HBM3e each on one NVLink 5 fabric at 1.8 TB/s per GPU, two Xeon Platinum 8570 CPUs, 2 TB of memory and 30 TB of local NVMe. The host runs NVIDIA driver 580 and CUDA 13.0. Bring any image built with CUDA 12.8 or later… Show all

Each node is an HGX B200: eight Blackwell GPUs with 180 GB of HBM3e each on one NVLink 5 fabric at 1.8 TB/s per GPU, two Xeon Platinum 8570 CPUs, 2 TB of memory and 30 TB of local NVMe. The host runs NVIDIA driver 580 and CUDA 13.0. Bring any image built with CUDA 12.8 or later, the first release that targets Blackwell. 23 October 2026 Pricing

Record ship:60283c22… · 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 · Verified Builder

Blackforge is now a verified builder: HEY verified its builder sources.

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

Observed by HEY on 2026-10-24Source: HEY’s research record

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

Questions HEY can answer about Blackforge — as of 24 Oct

Is Blackforge still being built?
DerivedShipping: 4 meaningful events in 30 days; latest ship yesterday. Evidence
What did Blackforge ship last?
FactF1 is built on NVIDIA B200 — Feature release, yesterday. Evidence
Is 0xe1c078A09dc0E66fEEabA67D6F16456b0c10C87B Blackforge’s own contract?
FactToken verified: The project’s own site names this contract. Details
What does HEY not know about Blackforge?
Unknown3 gaps: Repositories (no source), API description (no source), Contract interface (no source). No repository the project claims as its own. Details

Build timeline

  1. Change log.

    Feature releaseSource linked

    Launches, hardware, prices and forge updates. Price changes are announced here and in the heat ledger a month before they apply. RSS feed Follow @useblackforge 23 October 2026 Launch

    View evidence: Change log. (opens in a new tab)

  2. Forge F1 opens in preview

    AnnouncementSource linked

    Blackforge is taking work orders. Forge F1 on the Reykjanes peninsula runs sixteen NVIDIA B200 GPUs across two HGX nodes, cooled by outside air and powered by geothermal and hydro. Access is by invitation while F1 is in preview. Send a work order with your workload, GPU count… Show all

    Blackforge is taking work orders. Forge F1 on the Reykjanes peninsula runs sixteen NVIDIA B200 GPUs across two HGX nodes, cooled by outside air and powered by geothermal and hydro. Access is by invitation while F1 is in preview. Send a work order with your workload, GPU count and hours, and a person replies within one business day with start dates and a quote. 23 October 2026 Hardware

    View evidence: Forge F1 opens in preview (opens in a new tab)

  3. Four plans, one price each

    Feature releaseSource linked

    Strike at 3.79 USD per GPU hour, billed to the second. Hour bank at 3.09, prepaid in blocks of 1,000 hours. Anvil, a whole node for a month, at 16,640 USD, which is 2.89 per GPU hour. Ember at 1.39 for preemptible work on idle GPUs. CPU, memory, scratch and traffic inside the… Show all

    Strike at 3.79 USD per GPU hour, billed to the second. Hour bank at 3.09, prepaid in blocks of 1,000 hours. Anvil, a whole node for a month, at 16,640 USD, which is 2.89 per GPU hour. Ember at 1.39 for preemptible work on idle GPUs. CPU, memory, scratch and traffic inside the forge are included, with 2 TB of shared storage and 5 TB of egress a month. Prices change at most once a month, announced a month ahead in the heat ledger. 23 October 2026 Docs

    View evidence: Four plans, one price each (opens in a new tab)

  4. Docs, API reference and the forge CLI

    Docs updateSource linked

    Twenty four pages covering the quickstart, jobs, storage, interactive sessions, every plan, scheduling, telemetry, the full API and the forge CLI. The API answers 503 until your key is activated; the request and response shapes in the docs are final. 23 October 2026 Forge

    View evidence: Docs, API reference and the forge CLI (opens in a new tab)

What changed

9 changes on HEY’s record for Blackforge: 3 releases · 1 verification change · 1 token verification change · 1 new project on HEY · 3 other changes in 2 more kinds.

All 9 changes for Blackforge →

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 14 of the 17 research questions that apply.

14 of 17 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1d ago.

Building

  • Building activityMeasuredRead 50m ago.
  • RepositoriesNo sourceNo repository the project claims as its own.
  • ReleasesMeasuredRead yesterday.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 1h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 4h ago.

Contracts

  • Contract creationMeasuredRead 29m ago.
  • Contract activityMeasuredRead yesterday.
  • Verified sourceMeasuredRead 1d ago.
  • Contract interfaceNo sourceThe contract publishes no verified interface.

Market

  • Current marketMeasuredRead just now.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 5h ago.
  • Market checksMeasured

Not applicable here: Repository details, Published packages, Package advisories, 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

5 more sources (docs)

Security context: a published security contact. An audit shows an audit took place; it is not a guarantee of safety.

Contract
0xe1c0…c87b0xe1c078a09dc0e66feeaba67d6f16456b0c10c87b