AdShares Whitepaper


Enterprise Service Chain (ESC) is a block chain based software tool facilitating high
volumes of simple transactions. In most cases, these transactions involve sending tokens
between accounts, as is done with other crypto currencies. The name is derived from the
concept of the Enterprise Service Bus in which a crypto currency is used as the protocol
of communication.

In ESC, the accounts are organized in hierarchical fashion. Each account is bound to a
local node and can be addressed by an unsigned integer smaller than 2^32. The number
of nodes is limited to 2^16. Blocks of transactions are created in regular intervals based
on the ‘Proof of Stake’ principle, whereby a small, fixed number of VIP nodes decide on
the composition of transactions included in the block. After each block is closed the set of
VIP nodes is selected based on the highest sum of tokens stored in accounts of the nodes
(delegated Proof of Stake). VIP nodes have total authority over nodes and accounts. If a
consensus between VIP nodes is reached, other connected nodes can be partially
paralyzed and their accounts modified.

Each node collects transactions signed by local accounts, combines them into a message
and submits the message to the block chain network. Nodes that submit conflicting
messages (double spend) are penalized heavily: permission from the master VIP node is
needed to restart the double spending node. Messages from two different nodes can be
processed in parallel without conflicts. All types of transactions, except one, require
submission via local node. The only exception is the particularly slow transaction of
‘recovery of funds’ that is needed in the case of local node failure or dispute. Hierarchical
organization of accounts enables the incorporation of ‘Know Your Customer’ (KYC)
procedures during account creation. In contrast to most other crypto currencies, there is
no intention to incorporate functionality that facilitates laundering of assets.

All transactions and messages are consecutively numbered and can be processed in
parallel within a block. Numbering reduces the size of message and transaction
identifiers, and as a result also the network traffic. An account can send funds to many
accounts in a single transaction, requiring 6 bytes for the target account and 8 bytes for
the amount.

AdShares Website
AdShares Whitepaper