StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

shibarium: build bor + heimdall from source (bone fork, chain 109) #12

Merged
sebastian merged 2 commits from shibarium-bone-fork-fix into main 2026-06-19 13:02:00 +00:00
Conversation 0 Commits 2 Files Changed 3 +68 -17
claude commented 2026-06-19 11:46:54 +00:00
Collaborator
Copy Link

Shibarium mainnet (chain 109) — build bor + heimdall from source

shibaone publishes no docker images for the bone fork (only source + .deb config packages), so both clients must clone+build. This asset branch carries the Dockerfiles; the matching source branch is shibarium-bone-fork-fix on vibe-node.

Changes

  • shibarium/bor.Dockerfile — clone shibaone/bor@${BOR_VERSION}, make bor, cp build/bin/bor (golang:1.22.1, mirroring upstream). Fixes the earlier alpine build + wrong /src/build/bor path.
  • shibarium/cometbft.Dockerfile — clone shibaone/heimdall@${CL_VERSION}, make install, then layer the CometBFT init entrypoint. Fixes FROM shibaone/heimdall:v1.0.7-bone — that tag does not exist on any registry, so the heimdall image build would have failed.

Verified

  • update.sh --filter shibarium.mainnet regenerates cleanly (0 errors); rendered compose is valid YAML with both shibarium-mainnet (bor, --chain=shibarium) and shibarium-mainnet-node (heimdall) building from these Dockerfiles.
  • bor genesis-shibarium.json = chainId 109; heimdall genesis = heimdall-109 (both confirmed, not the Polygon-137 trap).

Merge together with the vibe-node PR; then deploy-compose-repo to rpc-de-10.

🤖 Generated with Claude Code

## Shibarium mainnet (chain 109) — build bor + heimdall from source shibaone publishes **no docker images** for the bone fork (only source + `.deb` config packages), so both clients must clone+build. This asset branch carries the Dockerfiles; the matching source branch is `shibarium-bone-fork-fix` on **vibe-node**. ### Changes - **`shibarium/bor.Dockerfile`** — clone `shibaone/bor@${BOR_VERSION}`, `make bor`, `cp build/bin/bor` (`golang:1.22.1`, mirroring upstream). Fixes the earlier alpine build + wrong `/src/build/bor` path. - **`shibarium/cometbft.Dockerfile`** — clone `shibaone/heimdall@${CL_VERSION}`, `make install`, then layer the CometBFT init entrypoint. Fixes `FROM shibaone/heimdall:v1.0.7-bone` — **that tag does not exist on any registry**, so the heimdall image build would have failed. ### Verified - `update.sh --filter shibarium.mainnet` regenerates cleanly (0 errors); rendered compose is valid YAML with both `shibarium-mainnet` (bor, `--chain=shibarium`) and `shibarium-mainnet-node` (heimdall) building from these Dockerfiles. - bor `genesis-shibarium.json` = chainId 109; heimdall genesis = `heimdall-109` (both confirmed, not the Polygon-137 trap). Merge together with the vibe-node PR; then `deploy-compose-repo` to rpc-de-10. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
claude added 2 commits 2026-06-19 11:46:54 +00:00
shibarium: add bone fork build-from-source assets bda550eef6 
- Update heimdall init.sh with heimdall-109 chain_id and mainnet seeds
- Update cometbft.Dockerfile with v1.0.7-bone version
- Add bor.Dockerfile for building shibaone/bor from source at v1.3.9-bone

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
shibarium: build bor + heimdall from source (no published images) ee21a0245e 
shibaone ships no docker images for the bone fork — only source + .deb config
packages — so both Dockerfiles must clone+build, not FROM a (nonexistent) image.

- bor.Dockerfile: clone shibaone/bor@${BOR_VERSION}, make bor, cp build/bin/bor
  (was: alpine + wrong /src/build/bor path). golang:1.22.1 like upstream.
- cometbft.Dockerfile: clone shibaone/heimdall@${CL_VERSION}, make install
  (was: FROM shibaone/heimdall:v1.0.7-bone — that tag does not exist on any
  registry), then layer the CometBFT init entrypoint.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sebastian merged commit 8c46b66bdc into main 2026-06-19 13:02:00 +00:00
sebastian deleted branch shibarium-bone-fork-fix 2026-06-19 13:02:01 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude cursor rob sebastian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#12
Delete Branch "shibarium-bone-fork-fix"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?