XDB & the DigitalBits Network

A Multi-Purpose Token on a Feature-Rich Network

XDB is a utility token that serves various functions on the DigitalBits network.

This diverse function set works to positively impact token velocity. In addition to the underlying framework and functionality of the DigitalBits network, policies have been put in place to enable the optimization of token velocity. Below we will explore the functions of XDB, and how this affects both token velocity and token supply.

We will use a red, yellow, and green system in diagrams below to reference token velocity.

Red refers to tokens that will likely never again enter the active token supply.

Yellow refers to tokens that have the ability to move but will generally not be active.

Green refers to liquid tokens that will actively move between entities on the DigitalBits network.

Protective Security Feature (Anti-Spam):

A minimum of 10 XDB need to be staked to activate an account and are exclusive to that respective account. This can be thought of as the “cost” of opening an account. Because these tokens are unable to move while the account holds tokens, they can be considered removed from the circulating supply. This works to slow token velocity and reduce the active supply of the token.

The transaction fees for use of the DigitalBits network are also paid using XDB and work to deter redundant transactions, inherently reducing the turnover of XDB. Transaction fees are returned to the algorithmic pool for future distribution per the rules underlying the algorithmic pool.

Bridge Token:

XDB can act as a bridge token to facilitate transfers and/or trades between asset pairings that may not have a large direct market. As a bridge token, XDB is able to interact with a number of different tokenized assets, creating the possibility for a large number of situations where it is both bought and sold — whether or not it is the beginning or end result in the transaction between other assets.

XDB is able to experience increased liquidity when a part of multiple asset pairings — but will also experience an increase in token velocity as it changes hands.

Conversely, the more brands that become available on the DigitalBits network will ultimately bring with them more accounts, all of which will be required to stake the necessary minimum of 10 XDB per account in order to activate. In this way, the network enables assets to move between entities, while slowing token velocity through the use of more tokens as the network gains traction.

Low cost payments & remittances:

Low cost payments and remittances are not novel use-cases of XDB — many tokens on the market are capable of doing this. Protocol’s that exclusively act as a “medium-of-exchange” are under threat from experiencing high token velocity and the token depreciating in value. XDB’s utility is not limited to payments and remittances, and as such, it is unlikely it will be utilized solely as a “medium-of-exchange” token.

Node Operator Program (NOP):

DigitalBits intends to launch a NOP that will require qualified node operators to stake a given amount of tokens in order to receive rewards. This amount must be maintained in order to remain involved in the program. The staked tokens will remain inactive as long as the participant belongs to the program, and will reduce the number of active tokens on the network — slowing token velocity. Conversely, XDB tokens that are paid out as rewards can be sold immediately — this appears to be the precedent when operators receive rewards — reference Bitcoin miners. If there is an immediate sale of tokens by these recipients, it will increase token velocity.

In the diagram below 1 000 000 XDB is given as an example amount for staking. As the NOP is currently under development, the official staking amount has yet to be determined. However, the relationship between required stake and rewards will result in more tokens being “staked” than paid out as rewards, netting an overall reduction in token velocity.

Algorithmic Dissemination:

Algorithmic dissemination is a novel method to the distribution of reserve tokens. DigitalBits was forked from the Stellar network. Stellar utilizes an inflationary method to distribute reserve tokens. As for the DigitalBits network, there is no inflation of the total supply of digitalbits (XDB) token. According to the Stellar protocol, XLM is distributed on a weekly basis — adding XLM to the network a rate of 1% annually. Under this approach, regardless of the state of the Stellar network, the circulating supply will continue to increase.

Each week, XLM tokens are distributed to accounts that receive in excess of 0.05% of the votes (1 lumen = 1 vote). Assuming account holders vote for themselves, they will receive a proportional distribution from Stellar’s inflation pool — maintaining the accounts relative wealth. However, this poses a threat to smaller account holders who do not meet the 0.05% requirement. Community members have set up pools to aggregate the votes of multiple smaller accounts to satisfy this requirement — however, the payouts are left up to the discretion of the party running the pool, which may be subject to fees or delays. To be clear this is not always the case, for example, the Lumenauts run pool pays out all inflation tokens to its members.

Conversely, DigitalBits algorithmic pool will use mathematical algorithms to distribute reserve tokens. By rewarding users for certain aggregate network and individual account usage, DigitalBits encourages the use of its blockchain and the XDB token. In this way, all network participants are eligible to receive rewards. Additionally, any tokens from the algorithmic pool that eventually get added to the circulating supply will be proportional to the activity on the DigitalBits network — and will only increase as network activity increases. With the supply of XDB also growing in relation to the network’s usage, XDB protects its token from the effects of inflation and ensures that the amount of tokens in circulation is suitable for the state of the network.