lexdao / dripdrop Goto Github PK

We should create an new skin of DripDrop that involves two balance-based payment function examples,

(1) MemberDripDrop that includes "stakes" as another member value stored in Struct that determines what respective payout they get from a drip or drop. . .

(2) MemberDripDrop that includes more external reader function . . . such as fetching the balance distribution of an ERC-20 and then making a drip-drop to that array (this might just not be worthwhile . . . not clear)

Bounty 3 LXK ⚔️

Currently ETHDrop deploys with an initial array of accounts (members) that can be updated with new additions by the secretary role.

It would be great to also allow the secretary to remove members who might have changed accounts or otherwise should not be included in a drip or drop of ETH.

Airdrop sounds like an ICO thing, but dripDrop rains ETH and happiness.

Currently the member index starts at "0" per norm. This can be slightly confusing, when a member occupies the first spot in the array, but yet their assigned index is "0." This is a small nit, but reducing cognitive load FTW~~

• Bounty 0.3 LXK ⚔️

Continuing effort to unpack some of the payment functions of MemberDripDrop . . .

I think it would be good to breakout customDropETH single function smart contract example in this repo~~

Bounty 1 LXK ⚔️

Grab the latest version of IERC20 from https://github.com/OpenZeppelin/openzeppelin-contracts/tree/master/contracts/token/ERC20 and add to tknBatch.sol

I think it's useful to break out chunks of the MemberDripDrop for folks to grab. I have started an iteration of dropTKN here: https://github.com/lexDAO/Airdrop/blob/master/contracts/dropToken.sol

Can someone take a stab at similar format for dropETH in contract folder?

Bounty 1 LXK ⚔️