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.

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

Implement a new Merkle campaign with variable claim amount #43

Open
smol-ninja opened this issue Jan 10, 2025 · 0 comments
Open

Implement a new Merkle campaign with variable claim amount #43

smol-ninja opened this issue Jan 10, 2025 · 0 comments
Labels
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.

Comments

@smol-ninja
Copy link
Member

As discussed in https://github.com/sablier-labs/company-discussions/discussions/85, implement a new merkle contract with the following features:

  • The amount of airdropped token depends on the claim timestamp.
  • Only works for ranged streams i.e. all streams begin at the same time.
  • Enforce expiry to be greater than end time of the vesting schedule.
  • Nomenclatures TBD.
function createMerkleVCA(
    MerkleBase.ConstructorParams memory baseParams,
    MerkleLL.Schedule memory schedule,
    uint256 aggregateAmount,
    uint256 recipientCount
)

Calculation of airdropped amount

$$\text{airdrop amount} = \text{claim amount} \cdot \frac{\text{block timestamp} - \text{start time}}{\text{total duration}}$$

Some questions

  1. Should it have start and cliff unlocks?
  2. What should the contract be called?
@smol-ninja smol-ninja added 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. labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.
Projects
None yet
Development

No branches or pull requests

1 participant