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.
Beam Mimblewimble is a scalable, fungible, and confidential cryptocurrency based on the Mimblewimble implementation. WHY BEAM? Core features include complete control over your privacy, All transactions are private by default, No addresses or other private information are stored on the blockchain, Superior scalability due to compact blockchain size, Opt-in Auditability, Support online and offline transactions, atomic swap, hardware wallets integration. Governance model No premine, No ICO. Backed by Treasury Establishing a non-profit foundation to govern the protocol after Mainnet launch How does it work? Wallets’ owners create new transaction using secure channel either online or offline Both wallets participate in signing the transaction using Schnorr protocol Wallet sends transaction to node Each transaction contains a list of Inputs and Outputs represented by Pedersen Commitments, as well as explicit fees and kernels. Each transaction also contains non-interactive zero knowledge range proof to verify that the output transaction value is positive Transaction is verified by the node Each transaction is verified with respect to the recent blockchain state which is stored as a Merkle Tree. The root hash of the tree is recorded in block header along with a proof of work. In addition, each node periodically creates compacted history to allow ‘fast sync’ of new and existing nodes. Transaction is added to the mining pool A block is mined every minute and is sent back to the node for verification and distribution. Mined blocks containing the new transactions are sent to the known peers A valid block that is extending the longest chain is accepted as a new Tip and propagated further until full consensus is reached. Fast sync When a new node connects to the network for the first time it can request compacted history containing only system state and blockchain headers. There is no need to retrieve the entire transaction history.