Closed bookmoons closed 5 years ago
@bookmoons Hi! What's the advantage of your refactored contracts over the current ones? The existing ERC20Airdrop.sol
has methods sendAirdrop
(for differing amounts) and sendAirdropEqual
, emitting event LogTokensTransferred
. They work fine for me so far. Example airdrop txn on ropsten What problems with them does your refactor fix?
I think the current code was intended as something temporary to build around, with something clean and complete to be built later:
The smart contracts are not finalised and solely serve to act as the building blocks for this use case.
This is a proposal to undertake that effort. Since the team has the upcoming token sale taking attention, I thought it might be valuable to get someone running on it.
It aims for something that can be comfortably deployed on the livenet. There may be changes needed, but it's intended as a first step. Everything is well commented, and it uses the condition oriented programming pattern recommended by Gavin. The name changes are cosmetic, following the same structure and just simplifying a little.
I wonder if the team would consider doing the Dropzone smart contract through the DDF. Since the frontend is being built in https://github.com/MyBitFoundation/MyBit-Network.tech/issues/147, maybe we could have the app live for the token sale.
bookmoons/dropzone
has something toward it, based on material on the website and the existing code. Coverage is 100%. Diff.The feature set seems to be like this:
Deriving from the current code, the interface is like this:
airdropIdentical
airdropVariable
There's 1 event emitted:
Airdrop