Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

List example Merkle campaigns in the "Deployment Addresses" for airdrops #265

Open
PaulRBerg opened this issue Feb 7, 2025 · 3 comments
Open

List example Merkle campaigns in the "Deployment Addresses" for airdrops #265

PaulRBerg opened this issue Feb 7, 2025 · 3 comments
Labels
effort: epic Multi-stage task that may require multiple PRs. priority: 2 We will do our best to deal with this. type: feature New feature or request. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.

Comments

@PaulRBerg
Copy link
Member

We should list example Merkle campaigns in the "Deployment Addresses" for airdrops:

Image

This is not an easy thing to do, but I think it'd be very helpful, for two reasons:

  1. Transparency and documentation for all our airdrop contracts

  2. It'd solve the problem of source code verification for Merkle contracts — there have been several cases in which users pinged us manually to verify the Merkle contract code.

Achieving this would require us to deploy some dummy campaigns every time MerkleFactory is deployed, but I think it's worth it.

cc @sablier-labs/evm
@PaulRBerg PaulRBerg added effort: epic Multi-stage task that may require multiple PRs. priority: 2 We will do our best to deal with this. type: feature New feature or request. work: clear Sense-categorize-respond. The relationship between cause and effect is clear. labels Feb 7, 2025
@smol-ninja
Copy link
Member

Good idea. As for the examples, would it be OK to pick address of an already deployed merkle campaign?

@andreivladbrg
Copy link
Member

This is not an easy thing to do, but I think it'd be very helpful, for two reasons:

it can be automated when deploying the factory contract, but adding it now would take time.

@PaulRBerg
Copy link
Member Author

We don't have to do this now. We can do it after Airdrops v1.4.0 is audited and deployed in March/April.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: epic Multi-stage task that may require multiple PRs. priority: 2 We will do our best to deal with this. type: feature New feature or request. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@smol-ninja @PaulRBerg @andreivladbrg