Objectives
Main Objectives:
- Provide privacy on transactions / balances.
- Enable Smart Contracts.
- Scalable blockchain for daily usage.
- Easy to integrate for developers.
Other Objectives:
- Issue custom assets identical to the native XEL.
- POW algorithm designed as CPU / GPU friendly.
- Decentralization.
- Simple to use.
Network
- Coin Name: XELIS (XEL)
- Average Block Time: 15 seconds
- Maximum Block Size: 1.25 MB
- Block Reward: up to ~ 1.46 XEL
- Maximum Supply: 18.4 million
- Minimum Transaction Fees: 0.0001 XEL per kB
- Atomic Units: 8
- Block Dev Fee: 10%
Roadmap
BlockDAG
Provide scalability by using a DAG structure instead of a linear blockchain. Up to several chains in parallel, each block can have multiple parents.- 1.Reduce the rate of orphan's blocks when miners find a block at the same time. Instead of choosing one block, both blocks are included in the DAG.
- 2.Height is not unique anymore and can have multiple blocks.
- 3.Topo Height (topological height) is the new and unique height for a block which is ordered by the DAG.
- 4.Stable height is the last height in which the order of the DAG cannot change.
- 5.Different types of blocks:
- Sync: It is at a stable height and is the only block at its height (or the only ordered block at this height and doesn't have a lower cumulative difficulty than previous blocks).
- Side: Its height is less than or equal to the height of the past 8 topographical blocks. Its block rewards are reduced to 30%.
- Orphaned: This block was not ordered in the DAG and has no topographical height (it's transactions are not executed).
- 6.Up to 3 previous blocks (called TIPS)
- Circulating Supply is re-calculated each time the block is reordered because it is based on DAG order.
Client
Protocol
XELIS integrates, along with BlockDAG, a method to accept multiple occurrences of the same transaction (TX) and execute it only once. Instead of excluding the entire block due to a collision with another BlockDAG branch for a TX, we simply refrain from executing the TX and retain its hash.
The same TX can be contained in multiple blocks only if:
- TX must not be executed at a stable height.
- TX is not already included in the same chain branch (previous blocks).
During the generation of the DAG order (linking unique topoheight to a block hash), the first block being ordered will execute the TX first.
This feature allows the acceptance of other branch tips even if transactions are the same and prevent more orphans blocks when branches are merged.
Socials