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.
ProximaX is an advanced extension of the Blockchain and Distributed Ledger Technology (DLT) with utility-rich services and protocols. Businesses, enterprises, and innovators can avoid costly and failure prone centralized architecture by utilizing an all-in-one sustainable platform which provides augmented secured services, content delivery, storage, and media streaming. The ProximaX protocol aims to offer DApp developers cost-efficient fault tolerant, multilayer, P2P cloud services including, but not limited to, blockchain-powered P2P storage and bandwidth. A fault-tolerant system is designed to ensure a system remains fully functional even when part of it is ‘down’ or unavailable. ProximaX will build a P2P cloud storage architecture with fault tolerance and a distributed database by removing the central entity and connecting all the servers (or nodes) in a mesh configuration. Failure of any single component of the mesh will have minimal effect upon the overall performance of the system. ProximaX protocol will ensure confidentiality and integrity of the data passing through a myriad of nodes. The use of distributed databases (DHT) ensures consistency and integrity throughout the network. ProximaX distributed file management system (DFMS) interfaces with NEM blockchain and works in four scenarios: 1. ProximaX Public DFMS with NEM Public chain 2. ProximaX Private DFMS with NEM Public Chain 3. ProximaX Public DFMS with NEM Private Chain 4. ProximaX Private DFMS with NEM Private Chain ProximaX will provide DApp developers with an easy-to-use SDK that abstracts the ProximaX protocol layer into a dynamic second layer on top of the NEM blockchain layer that can carry different unique DApp protocols. This will ensure that the DApp developers can build great P2P applications with the best possible security protocols without relying on points of central authority. It will empower developers to build apps and monetise in the ways they want without any unnecessary compliance pressure. This solution makes use of the NEM blockchain for value and hash transaction and the NEM cryptography framework to gain access to the ProximaX DFMS and work in a tightly integrated environment based on the above four scenarios.