1/ Thank you to @IOHKMedia for writing a detailed and encouraging posts on optimizing Cardano performance, and what we can currently do as developers to improve it.
A thread on some things we're doing that fall in line with what is laid out in this post:
iohk.io/en/blog/posts/…
A thread on some things we're doing that fall in line with what is laid out in this post:
iohk.io/en/blog/posts/…
2/ "The reason for this oversaturation lies in the fact that...several users trying to purchase the same NFT and thus attempting to process transactions at the same time."
We enforce a limit of around a max of ~960 simultaneous Handle purchases within 30 minutes.
We enforce a limit of around a max of ~960 simultaneous Handle purchases within 30 minutes.
3/ "The reason for this oversaturation lies in the fact that...[NFT drops perform] simultaneous refund transactions to users who were unable to purchase the NFT."
We avoid this by processing refunds *after* the minting phase is complete for our initial beta sale, in batched txs.
We avoid this by processing refunds *after* the minting phase is complete for our initial beta sale, in batched txs.
4/ "But in the short to mid-term at least, this is a matter of building more efficient traffic systems rather than widening the roads."
We use SMS verification to throttle the inflow of users wishing to purchase a Handle, allowing no more than 120 users at a time.
We use SMS verification to throttle the inflow of users wishing to purchase a Handle, allowing no more than 120 users at a time.
5/ All-in-all the space is still early, as the post reads. We're all learning, and our approach is as experimental in its lifecycle as it is across the entire ecosystem.
As always we hope to be as transparent as possible, and hope to give the community detailed results.
As always we hope to be as transparent as possible, and hope to give the community detailed results.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
