Add abcore/mainnet/pruned compose configuration #52
Reference in New Issue
Block a user
Delete Branch "issue-2880"
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?
Summary
Generated Docker Compose configuration for abcore mainnet pruned node deployment. This is the rpc asset PR corresponding to vibe-node issue #2880.
Generated files
rpc/abcore/abcore/abcore-mainnet-abcore-pruned-leveldb-hash.ymlrpc/abcore/abcore/abcore-mainnet-abcore-archive-leveldb-hash.yml(also generated for completeness)Configuration details
abfoundation/abcore-v1:v1.13.15-abcore-1.2Ready for merge and de-32 bench deployment.
(vibe-node issue #2880)
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.
Pull request closed