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
136 reactions
Marlowe
@marsbars
Great question ser! ๐ค Despite having @poolboy who had been a part of a previous token launch (with Radix) and @tomi who has has a lot of experience with the traditional ICO at Goldman we thought it better to go with a service that specialized in offering token claims. We unfortunately didnt have the resources to build the claim portal ourselves we decided to vet multiple partners who could help us with the launch and claiming. There were a few that were vetted including TokenSoft and and TokenOps who were the last two standing. We decided to go with TokenOps as they seemed like the best option. As you know claiming didnโt go as planned when they should have due to being put though a purpose built platform for facilitating token claims. Preparation could have of course been better of course but the team has been juggling multiple issues and progressing multiple fronts to just make a CEX listing possible ๐ The claiming system had knowledge of how many people needed to claim but where I beliโฆ
0 reply
0 recast
0 reaction
Marlowe
@marsbars
Thank you ser!
0 reply
0 recast
0 reaction
Joonatan | Phaver CEO
@joonatan.eth
We and Tomi have been joking about our days based on the difficulty levels of the old PC game Doom where the last tiers were โIโm too young to dieโ and โnightmareโ, today we concluded that someone modded a new tier just for us. ๐ซ But still standing and still building. And still bullish.
0 reply
0 recast
9 reactions
Poolboy
@poolboy
Tough times never last, only tough people last ๐ฆ ๐ช๐ช๐ฆ
0 reply
0 recast
9 reactions
ali.base.eth
@alitiknazoglu
๐ค๐ผ๐
0 reply
0 recast
1 reaction
MrBitcoin
@mr3itcoin
100% Agreed! โจ๐ Feel free to take a look at my page, I do a-lot of Phaver Ai-Art & Phaver Memes! Would be much appreciated!! ๐ซถ๐ฆ
0 reply
0 recast
1 reaction
Denizz
@denizeth.eth
LKP๐ฆ๐ฆ๐ฆ๐
0 reply
0 recast
0 reaction
Muaz Asik
@muwery
Lets go team. We love u..
0 reply
0 recast
0 reaction
Paubee ๐ต
@paubee-warp
LKP ๐ฅ
0 reply
0 recast
0 reaction
Kriepto ๐ง๐ช
@farcastor.eth
No worries, everything turned out fine. Donโt pay attention to the fudders, they wonโt make Phaver great. True Phaverians were patient and understanding... and had empathy for all your good intentions. And now everything is okay. Thank you so much and congratulations once again. ๐๐๐ฅ๐ฆ
0 reply
0 recast
6 reactions
sidneyakpaso.base.eth
@iamsidneyakpaso
$SOCIAL ๐ฆ @phaverapp & $SOCIAL LFG ๐ฅ๐ฆ๐
0 reply
0 recast
1 reaction
Emre
@emrex
LKP๐ซถ๐ป๐ฆ
0 reply
0 recast
0 reaction
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
