EosDAC is currently an ERC-20 standard token on the Ethereum blockchain. Once the EOS platform launches, the ERC20 token contract will be frozen and the ledger will be transferred over to EOS through a process, defined by the launch team, that will be described on the eosDAC website and social media channels. BlockMaker Ltd has created a total token supply for eosDAC of 1,200,000,000. These tokens represent the community members of eosDAC, who will own and control the DAC (Decentralised Autonomous Community) once it is launched on the EOS blockchain in June 2018. EosDAC will seek to have it’s tokens listed on a number of major cryptocurrency exchanges. 75% of eosDAC tokens (900,000,000) have been allocated for an airdrop to EOS token holders. All EOS token holders holding over 100 tokens* at the end of Day 300 of the EOS crowdsale (April 15th 2018, 01:00:00 UTC) will receive 1 eosDAC token for each EOS token that they hold, these tokens will be transferred directly into their Ethereum (ERC20 compatible) wallet. The actual airdrop will be made as soon as possible after this date and after we have run necessary tests and checks. All Ethereum accounts that have 100 or more EOS tokens in them at the snapshot on the 15th April will automatically receive the airdrop. Any accounts with less than 100 tokens will not automatically receive the airdrop but will be eligible (until 15th May 2018) to apply using eosdac.io/airdrop. While eosDAC will now include Crypto Exchange wallets in the airdrop, you will need to contact your exchange directly to check that they will distribute the eosDAC tokens to an eosDAC wallet under your control. If your exchange is not prepared to do this you would need to withdraw your EOS tokens to an exchange that does support the eosDAC airdrop, or better still to an ethereum address for which you have the private key. Most exchanges will support airdrop distributions as long as they receive enough customers requesting them to.
VITE - A Next Generation High-performance Decentralized Application Platform DAG Ledger Transactions in Vite are grouped by accounts. That is, each transaction only changes the state of one single account. Send transactions are separated from receive transactions, thereby obviating the need to wait for a transfer to be complete before the initiation of another transaction. The hierarchical design of the consensus algorithm allows horizontal scalability in consensus groups. Asynchronous Architecture Vite splits transactions into transaction pairs according to a 'request-response' pattern. The writing and verification of transactions are asynchronously decoupled, thereby supporting ultra-high throughput. Inter-contract communications are based on an asynchronous messaging model. Reactive Contract Message-Driven With an event-driven architecture, every smart contract is viewed as an independent service. Contracts communicate via messages without sharing state. Solidity++ Solidity++’s syntax is compatible with most of that of Solidity. The new syntax supports asynchronous semantics, contract scheduling, and provides a series of standard libraries, such as string manipulation, floating-point operations, basic mathematical operations, containers, sorting, and so on. Integrated Decentralized Ecosystem End-to-end system for value transfer Vite itself is a decentralized exchange that supports digital asset issuance, cross-chain value transmission, and inter-token transactions based on the Loopring protocol. A quota-based resource allocation mechanism allows light users to pay zero fees and gas. Users can obtain computing resources in multiple ways. Vite also supports quota leasing. dApp Mini Programs The Vite client features an engine for creating HTML5-based decentralized mini programs. This engine simplifies the process of dApp development and deployment.