refactor: checkout v1.5.0 before build #89
Draft
Conversation
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
…and startup - Add new `start-sv2-tp.sh` script for improved bitcoind and sv2-tp startup - Update Bitcoin configuration files to enable IPC binding - Modify docker-compose files to use new startup script and environment variables - Update template-provider Dockerfile to use Sjors v1.0.2 of sv2-tp release - Simplify entrypoint commands in docker-compose configurations - Separate SV2 port and interval configuration using environment variables
- Update CI workflow to include rustfmt component for code formatting - Modify template provider startup script to use bitcoin-node with specific testnet4 configuration - Update docker-compose configuration for template providers and bitcoin nodes - Adjust sv2-roles dockerfile to use correct binary names - Improve network and RPC configuration for bitcoin nodes - Remove network-specific flags from entrypoint scripts - Standardize logging and configuration across services
- Refactor JDC, JDS, and Pool configuration files to align with v1.5.0 standards - Update coinbase reward script to use descriptor-based configuration - Modify network addresses and port configurations - Add full template mode and version support settings - Simplify and standardize configuration parameters across roles - Remove deprecated configuration options - Enhance configuration flexibility and readability
- Update coinbase reward script address in all config files to a new address - Modify pool signature to "average-benchmark" in pool configurations - Update config-c pool configuration for v1.5.0 compatibility - Add timeout configuration in config-c pool settings - Remove channel nominal hashrate from tproxy configuration - Update run-benchmarking-tool.sh script to clarify Bitcoin descriptor usage - Standardize configuration files across different roles and configs This change prepares the configuration files for consistent benchmarking across different SV2 roles and ensures compatibility with v1.5.0 configuration requirements.
- Install Clippy component during Rust toolchain setup - Ensure Clippy is available for static code analysis in CI pipeline
- Add new configuration parameter `min_extranonce_size` to JDC config - Set default value to 4 with valid range between 2 and 16
- Update dependencies to use Stratum v2 crates from v1.5.0 tag - Refactor imports and message handling to match new SV2 library structure - Add new proxy module with helper functions for message handling based on `demand-easy-sv2` - Replace `demand-easy-sv2` with individual SV2 crates from the main repository - Modify message parsing and channel handling to align with v1.5.0 changes - Remove unused dependencies and simplify Cargo.toml configuration
- Replace log and env_logger with tracing and tracing-subscriber - Update dependencies to use new stratum-common crate structure - Refactor import paths for SV2 message types and parsers - Add connection retry mechanism for server connection - Improve error handling and logging with tracing - Update main function to use tracing initialization - Add more detailed logging and error messages - Simplify dependency management by consolidating crate imports Motivation: Align with latest Stratum V2 library version and improve observability and error handling in the custom proxy implementation.
- Introduce new metrics for Job Declaration (JDC) workflow - Add metrics for mining job distribution and tracking - Implement connection health and channel management metrics - Create counters and gauges for tracking job tokens, declarations, and allocations - Add latency tracking for job token allocation and job declarations - Enhance observability for standard shares, mining jobs, and channel operations - Prepare metrics infrastructure for different proxy types (tp-jdc, tp-pool, translators) Improves system monitoring and provides deeper insights into SV2 proxy performance and behavior.
…ashboard - Extend Docker Prometheus Monitoring dashboard with new JDC performance metrics section - Add timeseries graphs for job declaration performance metrics - Include metrics for: * Total jobs declared * Successful job declarations * Job declaration errors * Job declaration success rate percentage - Add job declaration latency tracking graph - Enhance dashboard with detailed performance insights for JDC components
…acking - Modify JDC configuration to reduce share batch size from 10 to 1 - Update tproxy configuration to add `aggregate_channels` option - Refactor block submission handling in SV1 custom proxy - Add detailed logging and metrics tracking for successful block submissions - Implement block propagation time calculation using Prometheus metrics - Add authentication header to RPC requests if not already present - Improve error handling and logging for block submission process Enhances monitoring and configuration flexibility for SV2 proxy components, providing more granular control over mining operations and better tracking of block submission performance.
…deployment - Modify tproxy configuration to use '0.0.0.0' for downstream address - Update Prometheus scrape targets for SV2 components - Change service names in Prometheus configuration to match current deployment - Improve network configuration flexibility for distributed setup
- Modify `intercept_submit_share_success` to increment valid shares counter by 1 - Remove dependency on `new_submits_accepted_count` field - Simplify share tracking mechanism for more consistent metrics reporting - Ensure each successful share submission increments the counter exactly once
- Switch repository source from benjamin-wilson to average-gary fork - Modify comment to indicate reason for fork (timestamp validation fix) - Maintain existing Dockerfile structure and installation process
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.