feat(anchor-evm): add CLI options for EVM self-anchoring#748
Merged
Conversation
Add command-line options to ceramic-one daemon for configuring EVM-based
self-anchoring, eliminating the need for a centralized anchor service.
CLI Options:
--evm-rpc-url RPC endpoint for EVM chain
--evm-private-key Private key for signing (hex, no 0x prefix)
--evm-chain-id EVM chain ID (e.g., 100 for Gnosis)
--evm-contract-address Anchor contract address
--evm-confirmations Block confirmations to wait (default: 4)
All four required options must be provided together. Example:
ceramic-one daemon \
--evm-rpc-url "https://gnosis-mainnet.g.alchemy.com/v2/YOUR_KEY" \
--evm-private-key "your_private_key_hex_without_0x" \
--evm-chain-id 100 \
--evm-contract-address "0x231055A0852D67C7107Ad0d0DFeab60278fE6AdC" \
--anchor-interval 3600
Environment variables are also supported (recommended for production):
CERAMIC_ONE_EVM_RPC_URL, CERAMIC_ONE_EVM_PRIVATE_KEY, etc.
Additional changes:
- Add wait_for_pending_transactions() to handle tx from previous runs
- Deprecate --remote-anchor-service-url in favor of EVM options
- Use test_log::test(tokio::test) instead of manual tracing setup
- Add comprehensive CLI documentation to anchor-evm/README.md
- Add self-anchoring section to main README.md
- Run cargo fmt to fix formatting issues in daemon.rs and evm_transaction_manager.rs - Add #[allow(deprecated)] for intentional use of deprecated remote_anchor_service_url field
smrz2001
temporarily deployed
to
tnet-prod-2024
GitHub Actions
Inactive
Consolidate RPC URL configuration so that --evm-rpc-url is automatically used for both submitting anchors AND validating anchor proofs on that chain. Changes: - Add --additional-chain-rpc-urls for validating anchors from other chains - Deprecate --ethereum-rpc-urls (keep as hidden alias with warning)
smrz2001
had a problem deploying
to
tnet-prod-2024
GitHub Actions
Failure
smrz2001
temporarily deployed
to
tnet-prod-2024
GitHub Actions
Inactive
stbrody
approved these changes
Dec 8, 2025
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.
Add command-line options to ceramic-one daemon for configuring EVM-based self-anchoring, eliminating the need for a centralized anchor service.
CLI Options:
--evm-rpc-url RPC endpoint for EVM chain
--evm-private-key Private key for signing (hex, no 0x prefix)
--evm-chain-id EVM chain ID (e.g., 100 for Gnosis)
--evm-contract-address Anchor contract address
--evm-confirmations Block confirmations to wait (default: 4)
All four required options must be provided together. Example:
ceramic-one daemon
--evm-rpc-url "https://gnosis-mainnet.g.alchemy.com/v2/YOUR_KEY"
--evm-private-key "your_private_key_hex_without_0x"
--evm-chain-id 100
--evm-contract-address "0x231055A0852D67C7107Ad0d0DFeab60278fE6AdC"
--anchor-interval 3600
Environment variables are also supported (recommended for production):
CERAMIC_ONE_EVM_RPC_URL, CERAMIC_ONE_EVM_PRIVATE_KEY, etc.
Additional changes: