jasonmeinzer.eth 🎩↑
@jasonmeinzer
@bountybot $50 initial $USDC bounty for the best suggestion on a high-level v1 framework for implementing $CLANKERINDEX distributions. Deadline 11/29/2024. Details are posted below via a reply to this cast. Reply directly to this cast with questions, etc. Thanks in advance for any consideration!
17 replies
3 recasts
11 reactions
Jhon
@jhonc.eth
Data Preparation (Off-Chain): The data for the Top 50 wallets and their respective distribution amounts is prepared manually (e.g., using Google Sheets or CSV). A final file containing the addresses and amounts is uploaded to the smart contract using no-code interface tools like Remix. Smart Contract for Distribution: A minimalist Solidity contract allows distributions to the Top 50 wallets in a single transaction or in small batches to reduce costs. Transparency and Verification: Distribution data (addresses and amounts) is published in the smart contract or displayed on a public dashboard generated using tools like Dune Analytics.
4 replies
0 recast
0 reaction
gatedude.eth
@gatedude
What if the top 50 wallet changes? Like the top holder becomes the least holder and you've already uploaded the addresses, how do you go about that?
3 replies
0 recast
2 reactions
jasonmeinzer.eth 🎩↑
@jasonmeinzer
Good question @gatedude and thanks for the feedback @jhonc.eth. Simple rolling averages are often a go-to method... ... and believe you me that we've been working on these types of frameworks for years on tangental projects and have several methods vetted for determining the distros. To be clear the scope of this bounty is strictly for the actual execution of the distros themselves (not calculating the distros - which is an assumed input for this bounty as a simple Top 50 list). That said, in all scenarios, all methodology data will be transparent on our Dune and aside from clearly communicated static snapshots, there are quite a few methods to iterate on including but not limited to simple rolling or time-weighted avg. balance snapshots, holding/staking-based eligibility requirements, simple randomized snapshots, etc.
0 reply
0 recast
1 reaction
jasonmeinzer.eth 🎩↑
@jasonmeinzer
88 $DEGEN
0 reply
0 recast
1 reaction
Jhon
@jhonc.eth
There are two possible approaches to address this scenario: Updatable Smart Contract: Design the smart contract to allow updates to the addresses and amounts before executing the distribution. This could include a review period for participants to ensure transparency and accuracy in the data before any transfer is made. Create a New Contract for Each Distribution: This is the most commonly used approach, as it ensures that each distribution is independent and tailored to the most up-to-date information. While it may be less time-efficient, it provides greater flexibility and simplicity in handling changes.
0 reply
0 recast
0 reaction
