feature: Dogecoin Node Deployments & Fantom Integration Support#3492
feature: Dogecoin Node Deployments & Fantom Integration Support#3492SparshGarg999 wants to merge 2 commits into
Conversation
This addresses issue openai#3488 by providing: 1. Dockerfile and configuration template for Dogecoin node deployment. 2. Custom Fantom RPC client (examples/fantom_integration.py) with gas estimation and smart contract interactions. 3. Multi-chain deployment compliance documentation. Signed-off-by: Sparsh Garg <76697238+SparshGarg999@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a6c8b13191
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| server=1 | ||
| txindex=1 | ||
| rpcuser=dogeuser | ||
| rpcpassword=dogepassword |
There was a problem hiding this comment.
Because this template is copied directly into the image and is described as a staging/production deployment config, every node gets the same well-known RPC password. If the RPC port is published or reachable from another container, which the rpcallowip entries below explicitly allow, any peer can authenticate as dogeuser and invoke Dogecoin Core RPCs, including admin/wallet methods when a wallet is present. Generate the RPC credentials at deployment time or inject them from a secret instead of shipping a fixed password.
Useful? React with 👍 / 👎.
| RUN mkdir -p /home/dogecoin/.dogecoin | ||
|
|
||
| # Expose standard P2P and RPC ports | ||
| EXPOSE 9332 9333 19332 19333 |
There was a problem hiding this comment.
These are not Dogecoin Core's standard ports: mainnet RPC/P2P defaults are 22555/22556 and testnet defaults are 44555/44556. With the image exposing and the config using 9332/9333/19332/19333, a node deployed as a “standard” Dogecoin node will not match normal firewall, peer, or RPC-client configuration, so clients and inbound peers using Dogecoin defaults will fail to connect unless they know about the custom ports.
Useful? React with 👍 / 👎.
…mplate Signed-off-by: Sparsh Garg <76697238+SparshGarg999@users.noreply.github.com>
|
I have updated the Dockerfile and configuration template to use Dogecoin Core's standard P2P and RPC ports (22555/22556 for mainnet, and 44555/44556 for testnet) instead of Litecoin ports. I also removed the hardcoded |
1 participant
Changes being requested
This Pull Request introduces first-class Docker deployment configuration for Dogecoin Core nodes, an RPC integration client and example for Fantom Opera blockchains, and detailed regulatory compliance documentation, implementing all requirements from #3488.
Key Components Introduced:
Dogecoin Node Deployments (
docker/dogecoin/):debian:12-slimthat downloads, extracts, and sets up official Dogecoin Core (dogecoind) binaries. Includes a nativeHEALTHCHECKchecking node synchronization and state usingdogecoin-cli getblockchaininfo.rpcallowipsettings for Docker networks), index settings (txindex=1), and Mainnet/Testnet port specifications (9332/9333vs19332/19333).Fantom Blockchain Integration (
examples/fantom_integration.py):FantomClient) to communicate with the Fantom Opera mainnet and testnet.httpxto trigger standard JSON-RPC methods (eth_blockNumber,eth_getBalance,eth_estimateGas,eth_gasPrice, and read-onlyeth_callfor contract queries).Compliance Review (
docs/compliance-multichain.md):Additional context & links
Closes #3488