-
Notifications
You must be signed in to change notification settings - Fork 83
ENG-505 [DRAFT] local development setup #3858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
ENG-505 [DRAFT] local development setup #3858
Conversation
- Introduced a new system to monitor various operations within the Keep Core node, including wallet actions, DKG processes, signing operations, coordination procedures, and network activities. - Metrics are recorded through a new interface, allowing for optional integration without impacting performance when disabled. - Updated relevant components to wire in metrics recording, ensuring comprehensive coverage of critical operations. - Added documentation detailing implemented metrics and their usage. This enhancement provides better visibility into node performance and health, facilitating monitoring and troubleshooting.
- Updated and to include new addresses for WalletRegistry, Bridge, MaintainerProxy, and WalletProposalValidator. - Introduced new JSON files for deposit data and funding transaction information to support deposit and redemption processes. - Added various scripts for managing DKG processes, wallet requests, and operator registration, enhancing local development capabilities. - Included documentation updates for deployment and operational guidelines. These changes improve the setup for Ethereum interactions and streamline the development workflow.
| @@ -0,0 +1,13 @@ | |||
| ========================================== | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file seems like local dev output that shouldn't be in the repo.
|
|
||
| /** | ||
| * @title BridgeStub | ||
| * @notice Minimal stub implementation of Bridge contract for local development |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be worth adding a brief comment at the top explaining this is only for local dev/testing and should never be used in production, just to avoid any confusion downstream.
|
|
||
| [ethereum] | ||
| URL = "ws://127.0.0.1:8546" | ||
| KeyFile = "/Users/levakhnazarov/ethereum/data/keystore/UTC--2025-12-18T18-53-35.539381000Z--7966c178f466b060aaeb2b91e9149a5fb2ec9c53" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This contains a hardcoded local path and timestamp. Consider using a placeholder like <YOUR_KEYFILE_PATH> or moving this to configs/config.toml.SAMPLE instead of committing it to the repo root.
| # DisseminationTime = 90 | ||
|
|
||
| [storage] | ||
| Dir = "/Users/levakhnazarov/threshold/fork2/keep-core/data" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above, hardcoded absolute path. Might want to use a relative path or environment variable placeholder.
Add initial setup for local T network development
genesis.jsonfor blockchain initialization with predefined accounts and balances.setup-geth.sh,generate-genesis.sh,check-deployments.sh,deploy-ecdsa-tbtc.sh) to facilitate local development and contract deployment.This commit lays the groundwork for developers to easily set up and interact with the T network in a local environment.