Content
@
0 reply
0 recast
0 reaction
jasonmeinzer.eth 🎩↑
@jasonmeinzer
500 $USDC Bounty! @bountybot build the go-to Dune dashboard for @rohkiofficial 5pm PDT 8-22-2024 deadline Details are posted below via a reply to this cast. Reply directly to this cast with questions, etc.
13 replies
1 recast
2 reactions
jasonmeinzer.eth 🎩↑
@jasonmeinzer
BACKGROUND RŌHKI is a next generation anime series that’s done 330+ ETH in sales volume. We seek a Dune engineering partner to build the v1 of a dynamic, go-to dashboard for our team to leverage as we scale. BOUNTY 500 $USDC to the best submission according to accuracy, integrity, scalability and usefulness; eligible dashboards meet minimum requirements. Airdrop gifts for eligible submissions that don’t win : ) DEADLINE 5pm PDT 8-22-2024 QUESTIONS Reply directly to this cast!
2 replies
0 recast
0 reaction
Ryan J. Shaw Ⓜ️🎩
@rjs
I've started working on this 🫡
1 reply
0 recast
1 reaction
jasonmeinzer.eth 🎩↑
@jasonmeinzer
Big W! Thanks for letting us know and don't hesitate to ask any/all questions - happy to help : )
2 replies
0 recast
1 reaction
Ryan J. Shaw Ⓜ️🎩
@rjs
Update: Also found issues with primary sales volume - the SoundEdition contracts are tricky because they don't store the value of the transaction, and you can mint multiple. Also, V1 doesn't have a Minted event, only V1_1+. This has two consequences: 1. you have to look at the ethereum tx table to get the value paid for the transfer from 0x0 (= mint) -- this is super duper slow 2. you need to count how many SoundEdition Transfer events occurred in the same tx -- as far as I can tell that's the only reliable way to handle multiple mints so that I get the correct value per mint alongside the token_id Alternatively, I could split token tracking (for determining unique collectors) and sales volumes rather than building a single table: token tracking would be built off individual transfers but not track the value of them (should be fast since no join on the ethereum tx table), whereas sales volumes would just sum the values associated with all transfers from 0x0 but won't track each token id.
1 reply
0 recast
0 reaction
jasonmeinzer.eth 🎩↑
@jasonmeinzer
Super astute call outs here and it looks like your approaches are proper... just a few extra thoughts in case they help: 1. I thought V1 had the sound_xyz_ethereum.SoundEditionV1_evt_Minted event table to fetch from... but regardless I would also note that the GSheet referenced makes note that it seems the "SoundEditionV2" contract (which the 'Citadel (ROHKI Theme)' track was minted from doesn't have any relevant event tables to fetch from... so yeah - the Sound contracts make things tricky 2. Regarding slowness/latency and such, not sure if this makes a difference but we're OK with this whole Dashboard only updating twice or even just once a day 3. (continued in next reply)
1 reply
0 recast
0 reaction
