Creator DAO Airdrop Backend

yral-dapp / hot-or-not-backend-canister

Other

9 stars 6 forks source link

Open Natasha-GB opened 3 months ago

Natasha-GB commented 3 months ago

Building an airdrop flow to promote the Creator DAO feature. User will earn HOT tokens, COYNs and receive CDAO tokens created based on certain rules.

Natasha-GB commented 3 months ago

~Add sequence diagrams @Natasha-GB~ Added

harshita-srivastava-yral commented 2 months ago

harshita-srivastava-yral commented 1 month ago

harshita-srivastava-yral commented 1 month ago

This task is under review. Pending on @ravibazz . Once he has bandwidth he needs to review the PR

harshita-srivastava-yral commented 1 month ago

This is in progress and once this is reviewed by Ravi then he will be reviewing the PR for sharing link
We can get this closed today.

harshita-srivastava-yral commented 4 weeks ago

harshita-srivastava-yral commented 3 weeks ago

If we are going with the quing mechanism then it has to be scalable across Yral and other apps we are building
Not sure we want to invest that level of bandwidth into this
@rupansh-sekar-yral to evaluate the effort on quing if its 2 days then go for it
One option is to add Retry mechanism - 20 canisters/ 2-3 secs... After 20, it starts dropping until this que of 20 canisters is cleared.
1,500 canister per subnet per day is what we can do
How to solve for existing canister? - One proposed solution is slow down the upgrades

harshita-srivastava-yral commented 3 weeks ago

Retry option makes the most sense for now as per ICP folks. We are going ahead with it.
500*25 = 12500 trillion cycles required for this
0.3*20K per subnet (12 subnet total we have)
Looks too costly for now. We will keep an eye on proposal.
Aligned to have this as one time cost.
For every canister created once.

harshita-srivastava-yral commented 2 weeks ago

Use notify and there might be few cases where users might not get the airdrop amount
Deploy empty canister first then update the mapping