Skip to content

Issues: sablier-labs/airdrops

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.

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

ENS subdomain for Merkle Airdrops deployments effort: low Easy or tiny task that takes less than a day. priority: 3 Nice-to-have. Willing to ship without this. type: docs Changes to documentation. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
#69 opened Feb 13, 2025 by PaulRBerg
Integrate price oracles into Merkle contracts effort: medium Default level of effort. priority: 1 This is important. It should be dealt with shortly. type: feature New feature or request. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
#66 opened Feb 10, 2025 by smol-ninja
Immediately transfer tokens when the vesting period has ended effort: high Large or difficult task. priority: 1 This is important. It should be dealt with shortly. type: feature New feature or request. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
#37 opened Jan 5, 2025 by PaulRBerg
Get rid of "optimized" foundry profiles effort: medium Default level of effort. priority: 2 We will do our best to deal with this. type: build Changes that affect the build system or external dependencies. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
#22 opened Dec 2, 2024 by andreivladbrg
Move bug bounty to Notion to avoid having to maintain it in multiple places effort: low Easy or tiny task that takes less than a day. priority: 2 We will do our best to deal with this. type: docs Changes to documentation. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
#9 opened Nov 20, 2024 by PaulRBerg
Write fuzz tests effort: high Large or difficult task. priority: 2 We will do our best to deal with this. type: test Adding, updating, or removing tests. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
#8 opened Nov 20, 2024 by PaulRBerg
Write invariant tests effort: high Large or difficult task. priority: 2 We will do our best to deal with this. type: test Adding, updating, or removing tests. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
#7 opened Nov 20, 2024 by PaulRBerg
ProTip! Type g i on any issue or pull request to go back to the issue listing page.