Content
@
0 reply
0 recast
0 reaction
LLC LLC ( 🎩 , ☮️ )
@legalmastermind
1/ Early Winds Phenomenon: There's a unique situation that I've seen occur a few times now, particularly with the DMT-NAT mints that are hosted on either Luminex/Unisat, where being among the first to mint a highly anticipated drop you may, in fact, be less likely to successfully inscribe. Revised Edition 🧵👇
1 reply
3 recasts
2 reactions
LLC LLC ( 🎩 , ☮️ )
@legalmastermind
2/ Though there is an exception: if you are lucky and the block clears as soon as you send at whatever sufficient s/vb value then, by the grace of the mempool, you are marked safe. If you are looking to inscribe another batch then, as you know, another block, another array of circumstances.
1 reply
0 recast
0 reaction
LLC LLC ( 🎩 , ☮️ )
@legalmastermind
3/ Now, on the other hand, a perplexing issue arises on the block(s): a highly anticipated mint of such likes goes live, for instance, note the remaining inscriptions and live timestamp on Luminex; note the s/vb values on mempool(dot)space.
1 reply
0 recast
0 reaction
LLC LLC ( 🎩 , ☮️ )
@legalmastermind
4/ What's different about this block? The former ones in the mempool have gone through in a span of 8-12 minutes yet this one in particular with the anticipated drop live is taking 25-35 minutes. How can this be a problem for those who got an early wind with no block that luckily insta-sent after sending to inscribe?
1 reply
0 recast
0 reaction
LLC LLC ( 🎩 , ☮️ )
@legalmastermind
5/ At the beginning of the block when you were looking to inscribe a batch at, lets say, s/vb values of 27 and 29, respectively, for medium and high prio. Throughout the span of that congested block the competent s/vb value for you not to get front run could double to quadruple.
1 reply
0 recast
0 reaction
