To enable regtest, use the -regtest option. To enable testnet, use the dogecoind -testnet. When not specifying any network, Mainnet is the network used by default. Regtest : The regression test network, to test with only local peers and create blocks on-demand.
Mainnet : The main network where real transaction operate. Multiple networks are built-in for this purpose. When trying out new things, for example to test your application that interacts with the Dogecoin chain, it is recommended to not use the main Dogecoin network. You can see a more concrete example here. Using dogecoind -help will display all available configuration parameters that can be added as arguments: There are two ways to change the configuration. There are many parameters that can be configured to tune your node to your liking. The vout structure will give you information about where the transaction output. To have an overview of the available commands, use the help command: The Dogecoin Core installation provides the dogecoin-cli tool to interact with the JSON-RPC from the command line, and the interface is exposed over HTTP on port 22555, so that other tools and libraries can interact with it. Introduction to the JSON-RPC APIĭogecoin Core exposes a JSON-RPC interface that allows you to request information about the network, blockchain and individual transactions, send transactions to the networks and manage your wallet. The RPC server is not exposed with dogecoin-qt until you activate the -server option as a startup argument, but inside the GUI application, you can use all the commands explored below (without dogecoin-cli) by going to Help -> Debug window and inside the popup window selecting the tab Console. Note: The rest of this guide assumes the use of an headless node. This operation will take many hours to complete, but you are now part of the Dogecoin network! Your node is now running and starts with a synchronization process that downloads the entire blockchain from other nodes. Use -help to see all available options for each executable. Detailed logging is recorded in debug.log, located in the data directory.
0 kommentar(er)
