Skip to content

feat: functionality to verifyAirdropReceivers#90

Open
yungwkndllc wants to merge 2 commits intomainfrom
validateAirdrop
Open

feat: functionality to verifyAirdropReceivers#90
yungwkndllc wants to merge 2 commits intomainfrom
validateAirdrop

Conversation

@yungwkndllc
Copy link
Copy Markdown
Contributor

This can eventually be used in the clanker.world frontend to validate receivers in a CSV and give warnings if a user is going to upload a CSV that will revert onchain...

Signed-off-by: yungwknd <yungwkndllc@gmail.com>
Signed-off-by: yungwknd <yungwkndllc@gmail.com>
import { isAddressEqual, stringify } from 'viem';
import * as z from 'zod/v4';
import { ClankerAirdrop_v4_abi } from '../../abi/v4/ClankerAirdrop.js';
import { ClankerAirdropv2_v4_abi } from '../../abi/v4/ClankerAirdropV2.js';
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a question for @CarterAppleton - which version we want?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably v2 as that's all the new ones - no real need to validate old ones as they're already deployed

Copy link
Copy Markdown
Contributor

@CarterAppleton CarterAppleton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might be missing the use case for this? If the merkle hash matches, then why would it revert onchain? Unless they get a really unlikely collision it should be impossible for them to upload an invalid csv/merkle root pair?

import { isAddressEqual, stringify } from 'viem';
import * as z from 'zod/v4';
import { ClankerAirdrop_v4_abi } from '../../abi/v4/ClankerAirdrop.js';
import { ClankerAirdropv2_v4_abi } from '../../abi/v4/ClankerAirdropV2.js';
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably v2 as that's all the new ones - no real need to validate old ones as they're already deployed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants