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.
Mainframe is the platform for decentralized applications. Resistant to censorship, surveillance, and disruption, the Mainframe network enables any application to send data, store files, manage payments, run tasks, and more. With the exception of a catastrophic asteroid event or an aggressive alien invasion, the Mainframe network is simply unstoppable. We build with five fundamental principles as our guide. The Mainframe network is the messaging layer for the new web. This goes beyond human-to-human messaging. There are many use-cases and applications for reliably, privately, and securely routing data packets through the Mainframe peer-to-peer network. Mainframe is resistant to censorship, surveillance, and disruption. With the exception of a catastrophic asteroid event or an aggressive alien invasion, the Mainframe network is simply unstoppable. We build with five fundamental principles as our guide. The Mainframe platform is a developer-friendly SDK providing all these services in a secure peer-to-peer fashion. It is designed to be modular and pluggable, so developers and users can configure which projects they prefer to use for the underlying service layers. Our mission is to delight developers by providing an SDK that is well-documented, supported and backed by strong developer communities. Because it is not always clear which projects will gain the most momentum, and because developers often have varying preferences, we feel that it is important to design our underlying service architecture to be modular and pluggable, allowing developers and users to configure which projects they prefer to use for each service layer and abstracting away as much of the differences as possible. A single medium of exchange in the form of Mainframe tokens (MFT) is also used to improve the developer and user experience. Where underlying service layers cannot be retrofitted to accept MFT, we will implement atomic swaps between native service-layer tokens and MFT.