Select Page

What are the standard ports for DigiByte integration?

DigiByte uses the following ports:
RPC Port: 14022
P2P Port: 12024
Both are TCP
We recommend that you do NOT firewall outbound connections from these
ports. However, they will function fine with restrictions / NAT for inbound
connections, should you not want to seed to other nodes.

Do you have any good practices in integration with your wallet
for deposits and withdrawals?

We recommend 6 confirmations for deposits / withdrawals (90 seconds).
Notifications usually occur within 2-3 seconds, with blocks being every 15
seconds
digibyte.conf should not allow access to an IP address that is not part of the
RFC1918 specification. If possible, use SegWit transactions

Assuming that we will have 10 million users, how many
wallets do you recommend we should have? Should we divide
wallets / servers for different tasks, eg. address generating,
deposit handling, withdrawals?

It genuinely depends on the capacity of the server, and the optimization of
the software integrating with it. Look at your Litecoin / VertCoin server
utilization for a good performance indication for you to base your DigiByte
node from.

What parameters are recommend during installation / running a
wallet?

We recommend connecting to more than just the default number of nodes,
specifically adding:
addnode=seed1.digibyte.io
addnode=seed2.digibyte.io
addnode=seed3.digibyte.io
addnode=seed.digibyte.io
addnode=seed.digibyteprojects.com
addnode=digihash.co
addnode=digiexplorer.info
addnode=seed.digibyteguide.com
addnode=seed-1.us.digibyteservers.io
We would also recommend adding:
txindex=1

What are the required hardware resources to run a single
node?

A single node can happily seed on hardware as low as an Intel Atom with 2GB
RAM and 20GB HDD at present, so the wallet will run on almost any Windows,
Linux or OSX computer. However this is probably less than ideal for an
Enterprise-grade production environment.
For comparison, a quad-core 1.8Ghz Intel Atom with 2GB of RAM and a 2GB
Swapfile will handle connections from approx 200 peers to the wallet, with
the majority of that limitation being CPU-bound.
With this in mind we recommend you consider additional overheads for your
own API calls etc and where possible you should always run digibyted on
either bare-metal or a VM that has a solid-state drive.
Also, you should consider future growth of the blockchain, where now it is
~10GB, future growth requirements would suggest you actively monitor
whatever server you run this on for drive-space usage etc.

Once your server is in production, you may also want to look at clearing the
debug log, by running a command similar to this as the user running your
wallet:
$ cd ~/.digibyte && rm -f debug.log && ln -s /dev/null debug.log
However keep in mind that doing-so will severely limit your troubleshooting
abilities down the line, should an issue rise, so perhaps make note of this in
your /etc/motd
Also, the wallet can be run as a non-privileged user from within their home
directory, and sudo access is not required at any time.

What are practices to backup / restore wallet?

As per Litecoin / Bitcoin, backing up the private keys or wallet.dat is sufficient.
We recommend where possible you use a 2-of-3 multisig wallet.

Are there any known restrictions or issues we should know?

We are in the process of changing newly generated wallet addresses from
the “D” prefix to “dgb1”, and from “3” to “S” for MultiSig addresses, however
legacy addresses will continue to be supported so please allow for both.
Please see release notes:
https://github.com/digibyte/digibyte/releases/tag/v.6.16.1
As of 6.16.x, all wallets are also created as hierarchical deterministic (HD)
wallets.
As of 6.16.x, getinfo has been replaced by:
• getblockchaininfo
• getnetworkinfo
• getwalletinfo
• getmininginfo

Do you have a sample digibyte.conf that you would
recommend?

Yes:
# Place this config in the following path:
# ~/.digibyte/digibyte.conf
server=1
listen=1
daemon=1
txindex=1
rpcallowip=127.0.0.1
maxconnections=400
addnode=seed1.digibyte.io
addnode=seed2.digibyte.io
addnode=seed3.digibyte.io
addnode=seed.digibyte.io
addnode=seed.digibyteprojects.com
addnode=digihash.co
addnode=digiexplorer.info
addnode=seed.digibyteguide.com
addnode=seed-1.us.digibyteservers.io

Do you have any APIs we can use to integrate with the DigiByte Blockchain?

We recommend you run an Insight blockchain explorer server, then use the
APIs documented here:
https://github.com/bitpay/insight-api
A quick setup example would be for you to create a new linux user, and run
the following:
useradd digibyte # Create a new user for the service to run as — DO NOT RUN AS ROOT
su – digibyte
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.8/install.sh
| bash
# Exit your terminal session and log in again to apply the profile changes

exit
su – digibyte
nvm ls-remote # Find the latest LTS
nvm install v8.10.0 # Install the latest LTS
npm install -g digibyte-node # install DigiByte Node
digibyte-node create explorer
cd explorer
digibyte-node install insight-digibyte-api
digibyte-node install insight-digibyte-ui
digibyte-node start
This will start up the digibyte-node service in the foreground of your terminal.
We would recommend checking in ~/explorer/digibyte-node.json to confirm
the port it is running on.
The service should be listening on TCP Port 3001, which you can browse to
http://ip.address:3001/insight/
You will want to add the suggested nodes above in to
~/explorer/data/digibyte.conf
PLEASE NOTE: This digibyte.conf is different from that used by the standard
digibyte wallet.
Finally to run this as a background process, you may want to:
npm install pm2 -g
pm2 start digibyte-node — start

What are the advantages of running a node?

We recommend all exchanges / products run their own node they can use for
API calls, especially if they are expecting any sort of decent volume. This can
be run inside a virtualized environment without any additional configuration
requirements.
Running your own node will allow the best possible performance for your
product.

Although there are hundreds of thousands of DigiByte nodes, very few run
the Insight API on top of it for Blockchain integration. In addition, the
DigiByte Foundation was not an ICO and cannot sustain all of the server
needs for the entire community directly.

Do you have a running testnet?

Yes, please set:
testnet=1
In your digibyte.conf
The testnet operates on TCP12025.

Who should we contact for additional technical support?

All of our developers and most of our community operate out of Telegram.
You can use:
https://t.me/DGBSupport
Or if your matter is for a broken package etc that requires a developer:
https://t.me/DigiByteDevelopers

Can you confirm details for the DigiByte logo that we should
be using?

You can download the DigiByte logo in a variety of formats from:
https://github.com/digibyte/digibyte-logos
Please ensure you are using the updated Logo which was released in
October 2017.

What is the download link for the official Wallet?
The Wallet can be downloaded from:
https://github.com/digibyte/digibyte/