Skip to content
Menu

Arbitrum Docker

Infrastructure

Is this your project? Claim and verify →

Arbitrum RPC node in docker compose

What HEY knows

Building
Last shipped 12 days agoActive: 1 meaningful event in 30 days; latest ship 12 days ago. Evidence Source

Build Momentum 21How it is measured

Latest ship
Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit · · Code activity

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

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Arbitrum Docker 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 Arbitrum Docker’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 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
Active.
“Active” by the activity rule: 1 meaningful event in the last 30 days, the newest 2026-10-07. Not called Resumed: HEY began reading the source of the newest ships after the quiet stretch before them began, so it did not watch that gap.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-05 – 2026-10-11 · 1 commitCode changes, week of 2026-06-29 – 2026-07-05Version 4.1.1+2 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.
Source1 registered source, 0 of them context only.ReadRecordsCode changes, week of 2026-10-05 – 2026-10-11 · 1 commitCode changes, week of 2026-06-29 – 2026-07-05Version 4.1.1+3 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-10-05 – 2026-10-11 · 1 commit

Code activitySource linked

What changed, in the repository’s own words:

1 active day in cryptomanufaktur-io/arbitrum-docker.

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

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

View evidence ↗

Shared change · Release

Arbitrum Docker shipped Version 4.1.1.

1 meaningful development event was recorded in the last 30 days. Builder status: Active.

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

Questions HEY can answer about Arbitrum Docker — as of 2026-10-19

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

Build timeline

  1. Code changes, week of 2026-06-29 – 2026-07-05

    Code activitySource linked

    1 active day in CryptoManufaktur-io/arbitrum-docker.

    View evidence

  2. Version 4.1.1

    GitHub releaseSource verified

    Fix the ./arbd prune command · ext-network.yml now uses DOCKER_EXT_NETWORK in .env and no longer needs to be edited directly Show all
    • Fix the ./arbd prune command
    • ext-network.yml now uses DOCKER_EXT_NETWORK in .env and no longer needs to be edited directly
    View evidence

  3. Version 4.1.0

    GitHub releaseSource verified

    This is an optional release · Support for Apechain · Support for Mind · Refactor arbd, prepare for ext-network.yml change Show all
    • This is an optional release
    • Support for Apechain
    • Support for Mind
    • Refactor arbd, prepare for ext-network.yml change
    View evidence

  4. Version 4.0.0

    GitHub releaseSource verified

    This is a mandatory release for ArbOS 30 Breaking changes: · Requires Arbitrum Nitro 3.0.0 or later Show all
    • This is a mandatory release for ArbOS 30 Breaking changes:
    • Requires Arbitrum Nitro 3.0.0 or later
    View evidence

  5. Version 3.0.0

    GitHub releaseSource verified

    This is a mandatory release for Arbitrum Nitro v2.3.0 Breaking changes · Requires Arbitrum Nitro v2.3.0 or later · Requires setting PARENT_BEACON variable in .env Show all
    • This is a mandatory release for Arbitrum Nitro v2.3.0 Breaking changes
    • Requires Arbitrum Nitro v2.3.0 or later
    • Requires setting PARENT_BEACON variable in .env
    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 Arbitrum Docker? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

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

All 6 changes for Arbitrum Docker →

The full change record holds 2 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 5h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1y 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 7d ago.
  • Published packagesMeasuredRead 7d 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