• Time between block: 14 sec
• total block reward : 0.48 GOL
• Miner reward : 0.32 GOL / block
• GoldiamBox reward : 0.16 GOL / block
• Network ID : 1426
• rpc port : 2009
• Explorer: https://goldiamchain.io
• Explorer: https://explorer.goldiam.org

• 2009
• 52018 ( TCP / UDP )

List all accounts: personal.listAccounts

Unlock wallet: personal.unlockAccount(youraddress, passwd, duration)

Number of synced blocks (compare with some pool or explorer if you are fully synced): eth.blockNumber

Info about connected peers: admin.peers

Balance: web3.fromWei(eth.getBalance("youraddress"), "ether") or or web3.fromWei(eth.getBalance(eth.coinbase), "ether")

Send transaction: eth.sendTransaction({from: "address", to: "address", value: web3.toWei(1, "ether")})

  /usr/bin/ggol --rpc --rpcaddr 127.0.0.1 --rpccorsdomain * --rpcport 2009  --rpcapi "eth,net,web3"

[Unit]
Description=Ggol

[Service]
Type=simple
Restart=always
ExecStart=/usr/bin/ggol --rpc --rpcaddr 127.0.0.1 --rpccorsdomain * --rpcport 2009  --rpcapi "eth,net,web3"
[Install]
WantedBy=default.target

Official golang implementation of the Goldiam protocol.

Once the dependencies are installed, run

`make ggol`

or, to build the full suite of utilities:

`make all`

The ggol project comes with several wrappers/executables found in the cmd directory.

Going through all the possible command line flags is out of scope here (please consult our CLI Wiki page, but we've enumerated a few common parameter combos to get you up to speed quickly on how you can run your own ggol instance.

By far the most common scenario is people wanting to simply interact with the Goldiam network: create accounts; transfer funds; deploy and interact with contracts. For this particular use-case the user doesn't care about years-old historical data, so we can fast-sync quickly to the current state of the network. To do so:

$ ggol --fast --cache=512 console

This command will:

• Start ggol in fast sync mode (--fast), causing it to download more data in exchange for avoiding processing the entire history of the ggol network, which is very CPU intensive.
• Bump the memory allowance of the database to 512MB (--cache=512), which can help significantly in sync times especially for HDD users. This flag is optional and you can set it as high or as low as you'd like, though we'd recommend the 512MB - 2GB range.
• Start up ggol's built-in interactive JavaScript console, (via the trailing console subcommand) through which you can invoke all official web3 methods as well as ggol's own management APIs. This too is optional and if you leave it out you can always attach to an already running ggol instance with ggol attach.

As a developer, sooner rather than later you'll want to start interacting with ggol and the ggol network via your own programs and not manually through the console. To aid this, ggol has built in support for a JSON-RPC based APIs. These can be exposed via HTTP, WebSockets and IPC (unix sockets on unix based platforms, and named pipes on Windows).

The IPC interface is enabled by default and exposes all the APIs supported by ggol, whereas the HTTP and WS interfaces need to manually be enabled and only expose a subset of APIs due to security reasons. These can be turned on/off and configured as you'd expect.

HTTP based JSON-RPC API options:

• --rpc Enable the HTTP-RPC server
• --rpcaddr HTTP-RPC server listening interface (default: "localhost")
• --rpcport HTTP-RPC server listening port (default: 2009)
• --rpcapi API's offered over the HTTP-RPC interface (default: "eth,net,web3")
• --rpccorsdomain Comma separated list of domains from which to accept cross origin requests (browser enforced)
• --ws Enable the WS-RPC server
• --wsaddr WS-RPC server listening interface (default: "localhost")
• --wsport WS-RPC server listening port (default: 2018)
• --wsapi API's offered over the WS-RPC interface (default: "eth,net,web3")
• --wsorigins Origins from which to accept websockets requests
• --ipcdisable Disable the IPC-RPC server
• --ipcapi API's offered over the IPC-RPC interface (default: "admin,debug,eth,miner,net,personal,shh,txpool,web3")
• --ipcpath Filename for IPC socket/pipe within the datadir (explicit paths escape it)

You'll need to use your own programming environments' capabilities (libraries, tools, etc) to connect via HTTP, WS or IPC to a ggol node configured with the above flags and you'll need to speak JSON-RPC on all transports. You can reuse the same connection for multiple requests!

Note: Please understand the security implications of opening up an HTTP/WS based transport before doing so! Hackers on the internet are actively trying to subvert ggol nodes with exposed APIs! Further, all browser tabs can access locally running webservers, so malicious webpages could try to subvert locally available APIs!

Mining on the public ggol network is a complex task as it's only feasible using GPUs, requiring an OpenCL or CUDA enabled ethminer instance.

In a private network setting however, a single CPU miner instance is more than enough for practical purposes as it can produce a stable stream of blocks at the correct intervals without needing heavy resources (consider running on a single thread, no need for multiple ones either). To start a ggol instance for mining, run it with all your usual flags, extended by:

$ ggol <usual-flags> --mine --minerthreads=1 --etherbase=0x0000000000000000000000000000000000000000

Which will start mining bocks and transactions on a single CPU thread, crediting all proceedings to the account specified by --etherbase. You can further tune the mining by changing the default gas limit blocks converge to (--targetgaslimit) and the price transactions are accepted at (--gasprice).

The ggol library (i.e. all code outside of the cmd directory) is licensed under the GNU Lesser General Public License v3.0, also included in our repository in the COPYING.LESSER file.

The ggol binaries (i.e. all code inside of the cmd directory) is licensed under the GNU General Public License v3.0, also included in our repository in the COPYING file.