Airdrop | contract #116
Airdrop | contract #116
Conversation
# Conflicts: # Cargo.toml # packages/shade_protocol/src/lib.rs
| pub airdrop_snip20: Contract, | ||
| // The airdrop time limit | ||
| pub start_date: Option<u64>, | ||
| // Can be set to never end | ||
| pub end_date: Option<u64>, | ||
| // Secret network delegators snapshot | ||
| pub rewards: Vec<Reward>, |
There was a problem hiding this comment.
Can we move rewards and snip20 into a handle like
Airdrop {
snip20,
Vec<Reward>,
}
Then in the storage you could store a users list of assets?
Trying to think of how this contract can still be useful post-airdrop, I believe we are planning to airdrop other tokens in the future such as synthetics
There was a problem hiding this comment.
Yeah sounds good, wdym by users list of assets?
There was a problem hiding this comment.
Just if there are multiple overlapping airdrops of different denoms, so one user could query all their pending funds at once.
We could also do future airdrops through the staking contract rewards but that would limit who we can airdrop to to just SHD stakers.
There was a problem hiding this comment.
I think it would be best to keep each airdrop separate, so each new coin is a separate airdrop contract
# Conflicts: # Cargo.lock # Cargo.toml # makefile # packages/network_integration/tests/testnet_integration.rs # packages/network_tester/Cargo.lock # packages/shade_protocol/src/lib.rs
Added a working airdrop contract, integration tests for it are also implemented