no-side666
@no-side666
LOVELY REPOSTERS WILL BE REWARDED! CLICKY Fanclub has 3 levels of snipe protection on the contract layer so that this May 5th's debut mint will be favorable for real collectors. - Collection encryption until mint start - Max mints per transaction - Reveal delay on each token mint Let's dive into each of these ššļøšØ
1 reply
1 recast
1 reaction
no-side666
@no-side666
1/n - Collection encryption until mint start CLICKY Fanclub collection is built on DreamStack. DreamStack has contract functionality allowing for encryption of all components of a collection. Currently the UI only supports collection encryption.. but further UI work will make it easy for artists to protect all components up to and including a collection. The encryption of the collection hides the collection details of a collection's composition such as probabilities of tab, frame, and fork (all structural elements which you'll learn about) distribution and appearance of colorclasses. This means snipers would have to configure on the fly at mint start their strategy of sniping rare or desirable pieces. ...
1 reply
0 recast
1 reaction
no-side666
@no-side666
2/n - Max mints per transaction This is perhaps my favorite protection as this was very exciting to discover and implement!! There is a guard in the contracts using the new opcode TSTORE which tracks the number of free mints in a given transaction. CLICKY Fanclub is configured so there is a max of 3 free mints per transaction. This way.. it a sniper gets their batched transaction in during the free window.. their batched transaction couldn't mint all the free tokens. Snipers have to compete with everyone else for the free mints with this TSTORE mechanism! ...
1 reply
0 recast
1 reaction
no-side666
@no-side666
3/n - Reveal delay on each token mint This gadget I learned about while listening to a @chonksxyz spaces.. but I believe they learned it from @jalilwahdat and @_MouseDev . CLICKY Fanclub contract stores the block number when a token is minted, and after a secure delay (75 blocks), the rendering under tokenURI combines an offset revealBlock blockhash with the tokenId to get a seed for rendering the token. The degree to which a sniper would have to bribe a miner is really intractable and unlikely under these circumstances. As such, snipers won't be able to set bots to reject mints lacking rarity etc. Snipers have NO advantage here.
1 reply
0 recast
1 reaction