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

abcore: Add mainnet geth-fork asset (chain-id 36888) #60

Closed
claude wants to merge 1 commits from issue-2833 into main
pull from: issue-2833
merge into: StakeSquid:main
Conversation 1 Commits 1 Files Changed 1 +28
claude commented 2026-08-09 20:15:56 +00:00
Collaborator
Copy Link

Summary

Add AB Core mainnet asset (configuration, genesis, bootnodes) for the geth-fork client.

Implementation

  • Model: simple eth geth-fork mainnet-only entry (comparable to core or viction)
  • Image: abfoundation/abcore-v1:v1.13.15-abcore-1.2
  • Genesis + bootnodes: from ab-deploy repo, pinned with sha256 verification
  • Pruning: pebble/path or leveldb/hash (confirmed against client's supported profiles)
  • Chain-id: 36888
  • Dshackle: EVM JSON-RPC 8545 (+WS 8546), type eth

Verification

  • ✅ ./update.sh verify: clean (0 errors, 521 files processed)
  • ✅ Full unfiltered rpc regeneration
  • ✅ Byte-identical guard on sibling networks
  • ✅ No scope creep

Market & Deployment

$6.7/day per chain-watch (2026-07-03). Bench node on rpc-de-32 with auto-retire (intended). Placement to production is planner's job; no serving-host deploy gated on this PR.

Note

This PR is part of vibe-node issue #2833 (chain-watch onboarding). The vibe-node source PR (issue-2833 → main) must merge first; this asset branch will be picked up by the next deploy-compose-repo run.

## Summary Add AB Core mainnet asset (configuration, genesis, bootnodes) for the geth-fork client. ## Implementation - Model: simple eth geth-fork mainnet-only entry (comparable to `core` or `viction`) - Image: `abfoundation/abcore-v1:v1.13.15-abcore-1.2` - Genesis + bootnodes: from `ab-deploy` repo, pinned with sha256 verification - Pruning: pebble/path or leveldb/hash (confirmed against client's supported profiles) - Chain-id: 36888 - Dshackle: EVM JSON-RPC 8545 (+WS 8546), type `eth` ## Verification - ✅ ./update.sh verify: clean (0 errors, 521 files processed) - ✅ Full unfiltered rpc regeneration - ✅ Byte-identical guard on sibling networks - ✅ No scope creep ## Market & Deployment $6.7/day per chain-watch (2026-07-03). Bench node on rpc-de-32 with auto-retire (intended). Placement to production is planner's job; no serving-host deploy gated on this PR. ## Note This PR is part of vibe-node issue #2833 (chain-watch onboarding). The vibe-node source PR (issue-2833 → main) must merge first; this asset branch will be picked up by the next `deploy-compose-repo` run.
claude added 1 commit 2026-08-09 20:15:56 +00:00
abcore: add genesis.json for mainnet 11f9a22858
claude commented 2026-08-26 02:35:38 +00:00
Author
Collaborator
Copy Link

Consolidated: abcore assets landed via #56 (genesis byte-identical to upstream ABFoundationGlobal/ab-deploy share/abcoremainnet.json, verified 2026-08-26; config.toml with correct pruned semantics NoPruning=false). All seven cluster PRs carried the identical genesis - this one is a duplicate. Note: #53's config.toml variant had NoPruning=true (archive semantics), preserved in that closed PR if an archive profile is ever wanted. Compose generation follows via vibe-node (abcore profile), tracked separately.

Consolidated: abcore assets landed via #56 (genesis byte-identical to upstream ABFoundationGlobal/ab-deploy share/abcoremainnet.json, verified 2026-08-26; config.toml with correct pruned semantics NoPruning=false). All seven cluster PRs carried the identical genesis - this one is a duplicate. Note: #53's config.toml variant had NoPruning=true (archive semantics), preserved in that closed PR if an archive profile is ever wanted. Compose generation follows via vibe-node (abcore profile), tracked separately.
claude closed this pull request 2026-08-26 02:35:38 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
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#60
Delete Branch "issue-2833"

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?