pull down to refresh
0 sats \ 0 replies \ @03937eba84 17 Aug 2022 \ on: Christopher David on Arcade City and Decentralized Ride Sharing. bitcoin
Feels like there are holes in Chris's story, or it might not be totally accurate.
-
How does somebody go from driving full-time for Uber in 2015, to having enough tech skills to found and launch a genuine decentralized protocol on ETH, when easy-to-use Solidity tools weren't really available until 2017, for a problem as complex as Ride Sharing? The ICO was launched November 2016. Vitalik's dad joins his project, and they only raise $600K? My vapour-ware spider senses are going off.
-
I'd like to hear the other side of that story about the devs stealing his funding. We only got one side. Pretty bold claims. The other blockchain should have proof. The ecosystem was smaller back then, we/somebody could track them down and ask them to share their side. He also mentions the parity hack. Well, which was it - did the devs steal your funding? Or were you hacked?
-
"We've got parallel development going on...I'm on UX...and we've got SuperTestNet..." - 36:38 But, for some reason, he copied SuperTestnet's bullrun repo to ArcadeCity's bullrun org, instead of forking it. The README, says arcade city, uses bullrun. But Chris almost tries to frame this like they are a team working on front-end/back-end. 100% of the commits for the first repo, are from Super and Zaprite. Maybe Super can shed some light.
-
There are people on the internet who claim to have been scammed by Christopher David. Not going to link to the posts, in case they are lies. But it's out there if you want to dig it up and judge for yourself.
-
He says in the video that they "finally...figured out the proper stack". I'd like somebody technical to interview him on his prior stacks. What exactly did he build in the past? There was a token sale. Some development happened, before the theft. There should be some open-source assets out there, probably some solidity files, even if abandoned. Christopher should have been able to open-source it, especially if the project pivoted so hard as to change the tech-stack and abandon a token. Where is that code? There is a "v5", which used Solana, and USDC, but that would be way after tech that could have been built in 2017.