The Interview
Worst case scenario would be 40k+ transactions a second, will be possible quite soon and i hope we can publically prove that (we will have a budget for it). I'd like to show rather than tell. Hoping to hit 1M transactions a second in another year, maybe less.…
These statistics are a safe bet. If it takes off on the market, Mitya will roll out the upgrades faster, speeding up the process.
Removing the "if", it'll be more or less what i said
Removing the "if", it'll be more or less what i said
Forwarded from .
This media is not supported in your browser
VIEW IN TELEGRAM
86 BILLION transactions a day.
More than HALF A TRILLION API requests. (wishful thinking)
Insane API traffic (Dapp)
More than HALF A TRILLION API requests. (wishful thinking)
Insane API traffic (Dapp)
And the people delusionaly promote WEB3, following this system that was dead on arrival.
How to spot a quack on crypto: mentions of WEB3.
How to spot a quack on crypto: mentions of WEB3.
I'm very glad that Mitya's squad is immediately straying from WEB3 towards debots, we shall celebrate its complete abscence.
A debot is, simply put, an app you download from the blockchain that interacts with it, using your device to calculate.
It's all very safe.
It's all very safe.
It's the third future whale to rival Google Play and App Store.
Quote me on this if you like.
Quote me on this if you like.
This whale won't give a fuck about your phone model, what it's running on. It will just WORK.
The Interview
This whale won't give a fuck about your phone model, what it's running on. It will just WORK.
Not microwaves of course, but you get the picture
Hacking WEB3 is simple:
Hack the DNS, shoving another server in its place.
The servers where the WEB3 application is hosted, then faking the code and transactions you sign.
Come to the owner's place and fuck him in the ass.
Many similar scenarios which isn't a problem. Here's the worst part:
Containing WEB3 (the server, admins, threats, ddos protection, abuse protection, provider conversations) is VERY EXPENSIVE for a big project.
All that deanonymizes the owner, people will come to him and he will replace the code to fuck over all his customers.
Hack the DNS, shoving another server in its place.
The servers where the WEB3 application is hosted, then faking the code and transactions you sign.
Come to the owner's place and fuck him in the ass.
Many similar scenarios which isn't a problem. Here's the worst part:
Containing WEB3 (the server, admins, threats, ddos protection, abuse protection, provider conversations) is VERY EXPENSIVE for a big project.
All that deanonymizes the owner, people will come to him and he will replace the code to fuck over all his customers.
The Interview
Hacking WEB3 is simple: Hack the DNS, shoving another server in its place. The servers where the WEB3 application is hosted, then faking the code and transactions you sign. Come to the owner's place and fuck him in the ass. Many similar scenarios which…
- Put a couple thousand a month into your mid WEB3 project
- The admin sells data to criminals
- You and your customers are fucked
- The admin sells data to criminals
- You and your customers are fucked
Dapp is bliss, confidence that everything will be fine, that the hash of the app is what you asked for. You can't fake anything. It's the oasis in the desert.
I was driving, listening (for the second time) to the Default Block podcast with Mitya