Refactor to support merkle-service integration#48
Merged
Conversation
github-actions
Bot
added
fork-pr
👋 Thanks, @galt-tr!This pull request comes from a fork. For security, our CI runs in a restricted mode.
Thanks for contributing to bsv-blockchain/arcade! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces several significant updates to the project, focusing on adding new functionality for working with BUMP data, updating build and deployment processes, and introducing configuration files for development environments. The most notable changes are the addition of the
bumppackage for handling block data and Merkle path computations, simplification of the Dockerfile, and removal of theDEPLOY.mddeployment guide.Major new functionality: BUMP data handling
bumppackage with helpers to fetch and process block data from DataHub endpoints, including parsing binary block formats and computing Merkle paths. This includes robust error handling, per-attempt debug logging, and detailed unit tests for failure scenarios. (bump/datahub.go,bump/datahub_test.go,bump/helpers.go) [1] [2] [3]Build and deployment process changes
Dockerfileby switching to a two-stage build with a static Go binary, using Alpine 3.20, and removing explicit user setup, health checks, and configuration copy steps. The resulting image is smaller and easier to maintain.DEPLOY.md), which previously included instructions for Docker Compose and Kubernetes deployments, environment variables, and troubleshooting.Development and configuration
Makefilewith common development targets for building, testing, linting, running, and managing containers viapodman-compose.aerospike.confconfiguration file for local Aerospike development, specifying service, logging, network, and namespace settings.