At the moment the community and the airdrop owner can cancel a given airdrop, if you want the community to be able to do that, who gets sent the refund tokens, currently it is msg.sender, but I think it should always go to the creator of the airdrop

Lets take advantage of the error function arguments

@Kieran-Autaway can we have Bill work on this

working on it

solidity-coverage: v0.7.22

Instrumenting for coverage...

DarwinDrop.sol
TestErc20Token.sol

Compilation:

Error in plugin solidity-coverage: TypeError: Cannot read properties of undefined (reading 'settings')

Disregard

Please whitelist this address from fees:

0xe4e672ED86b8f6782e889F125e977bcF54018232

we need to simulate a complete upgrade cycle starting at the dao submiting a proposal ,aproval and upgrade

Since we are going to allow for drop fees in darwin , we need to Create/Mod to move the Tokens from the user into the contract.

ALso the front end need to make sure the contract has an ample darwin allowance from the user -> drop contract ( this must happen in the front end

This needs to be deployed fully live with no testnet now that it is ready to go.

    if (msg.value > ethSpent) {
        payable(msg.sender).transfer(msg.value - ethSpent);
    }

Are we NOT charging for airdrops besides promoted ones?

and that the wrong way of sending eth

airdropPromotionPriceEth

I think we need to refactor this variable

@SomeTimesIInvent

When a user pays for a DROP in darwin , what is the disposition of these tokens