Marlowe
@marsbars
Although today’s TGE was less than perfect in many ways it was amazing to see the team operate when the chips are down. @joonatan.eth & @tomi leading from the front and solving multiple problems at the same time while pulling people in where needed to focus themselves on the next most pressing issue. @saska back channeling and being the hand of god on all channels. @alitiknazoglu data crunching and pulling info from all corners of the Phaver network. @poolboy manging and pushing the most important info from inside Phaver to the Phaver community at the right moment! @chriscomrie all over the creators & @brizzzyyy @greenhouse on fire. Everyone pulled out all the stops putting out multiple fires. The whole Phaver team (dev and shill) were incredible today despite our worst nightmare unfolding in real time. I believe we have a lot to be proud of and a lot to be bullish on 👌 It’s a privillage to be in the trenches with people of this caliber 👌 Cheers to hopefully many more trenches 🪖 LKP 🚀
3 replies
9 recasts
239 reactions
CryptoGrogu
@cryptogrogu
@marsbars out of interest from a technical perspective: what did you do to fix the issues you encountered and how did you/the team prepare for the tge in regard of infrastructure needed? I am asking, because i probably encountered several such TGEs of the last months which had severe issues at launch and I am asking myself if this could not have been avoided error proper preparation? You did know exactly how many people were eligible for an airdrop and you probably tested how much bandwidth and computer power a claim transaction needs. You can then extrapolate that to let's say 50% of the eligibile users and get enough resources from the hyperscaler you are hosting on. Monitor closely and scale up if needed. That's in very simple terms of course but you probably get my point. Don't get me wrong, I think the team did a good job in the end to tackle the issues but it was a bad user experience for many and I wonder if it could have been prevented.
1 reply
0 recast
0 reaction
CryptoGrogu
@cryptogrogu
@marsbars , @alitiknazoglu , @joonatan.eth anyone of you who can/wants to answer to my questions?
0 reply
0 recast
0 reaction
Tomi - Social DAO
@tomi
We had asked the provider (not our system, but a company that specialises in smart contract vesting & claiming) about the capacity and exact numbers - and they were confident that there should be no problem. Thought it was already battle-tested but unfortunately was not for this amount of claims. We had all our devs troubleshooting with them and took 2 hours to find a solution. Was not our system so we could not scale it ourselves.
0 reply
0 recast
0 reaction