You either bow to the hype machines of ETH, SOL, OTHERS-- chained by narratives, network effects, and endless gas wars – or you stand with the underdog that's rewriting the game: SAITO.
True Web3, scalable to terabytes, decentralized for real.
@coinbureau
I am grateful to Shai for sharing Saito with his community and encourage everyone to read Shai's tweet and work through his example. It will help you understand Saito.
His "attack" is easily debunked. If U1 and U2 both double-broadcast 2 transactions per protocol, when B adds the extra hop to the final one it receives, B now produces more slowly than C which has both and does not add the extra hop. The dutch clock auction prefers the faster block for obvious reasons. B earns nothing in expectation.
But is this enough? No -- our problem fairly obviously shifts from incentivizing forward-propagation to avoiding simultaneous block production. This requires private mempools. But how can we have private mempools without block producers simply spending their own money to produce blocks, with B stealing any unknown transactions in C's block to make the theft costless and profitable in expectation?
This is the much harder problem that routing work solves. The sybil paper shows that forward-propagation is rational because this is necessary for private broadcast to be costly in at least one dimension. We have a multidimensional optimization problem that requires the blockchain to do something Shai will probably not understand for another decade -- price the value of collusion in equilibrium.
Just dropped an oversized update today in which:
David talks about York and beyond. Presenting to the doyens of Mechanism Design.
Richard promotes the Open internet pod, again!
https://t.co/rQSVHsDKf9
We talk ATOMIC SWAPS on Saito and what this means for Defi, RWAs and more.
And we bring it all together to explain how the dev work relates to strategy for the rest of the year. Alpha - it's all about bringing usage and value on Chain!
Listen in for details. (Spoiler there will be campaigns, rewards and need for Saito for key activities across Saito.) Stay tuned and watch our channels for more.
The guys are back at it with a new update!
Lots of interesting tidbits:
Positive feedback in York, Refactor Work, and of course
The Open Internet Pod 🤓
Cool. $200B in volume on a chain where 3 validators can freeze your perps mid-trade.
Hyperliquid built a NASCAR track in a shopping mall and called it decentralization. 🟥
Saito is out here solving WHY blockchains can't scale without selling out to node cartels — and nobody's writing the article.
Volume means nothing if the infrastructure beneath it is just TradFi with extra steps. 👀
WHY AREN'T YOU USING $SAITO YET?! 🟥
Be honest bruv... your "decentralized" L1 runs on AWS, dies when Infura sneezes, and pays validators to do
NOTHING while the nodes carrying your data get paid in exposure. You know it's a lie.
You just paid for the bag and can't admit it. Saito doesn't need your cope.
Tell me I'm wrong. 👇
Fresh update out!
This one is a bit of a fireside chat with David and Richard going over the many threads occupying the team over the last couple of weeks.
We cover: Store, Core updates, NFT integration and app design, Outreach and what the hell is going on with all this internet closure.
https://t.co/qjfdg7haDP
500,000 blocks bundled.
Millions of transactions processed.
6 ATR cycles complete.
Saito’s economic loop keeps turning.
Another orbit around the sun of decentralized infrastructure.
After some advice I increased the price of my book. Much of the info described cannot be accurately found even on Grok.
Examples: Attack symmetry, collusion goods, private v public fees in blockchain. Also interesting insights on gems like Nano, Saito.
https://t.co/sOFK0dzsTc
@MohamedBinZayed Thank you for your reassuring message.
I appreciate the clear emphasis on the safety and security of all citizens. Thank you for recognizing the loyalty and support from the whole community—Emiratis and residents alike. Under your leadership, we stand United..
How do we create media networks and apps that are consumer facing instead of dopamine-harvesters for ad networks?
The typical young adult averages 6 hours and 20 minutes of screen time per day, and only 29% feel it positively affects their mental health first.
Set a reminder and join the conversation this Thursday 26th of Feb at 12 pm UTC
https://t.co/cZBBQx4aUH
We have been getting a lot of love for setting out Saito's vision for an open, peer to peer internet.
Clearly hitting a nerve with folks. Let's get a little love for our spaces - a sign substance is starting to win out over token hype.
https://t.co/JTwaoyWYIb
love that Saitozens know wechat. because... of course.
good reminder of what is King in the UI / UX space.
today was knee deep in compilation-pipeline mud. but it's serving a purpose.
figure that yelling at me will be productive for about the next week.
I posted this on RedSquare, but wanted to comment here on Twitter as well.
I am in the middle of an Arcade Refactor (screenshot attached) for reasons that we'll share in a week or two, but as part of the process I wanted to share a brief post requesting suggestions on RedSquare.
Why? Motivation for the post is that I'm not sure how we improve RedSquare further, but we will probably want to refactor it soon as well. And it seems to me that what is holding us back here is slightly the UI and design, but what else? I'd like to get a list of things that we really need to fix. And not necessarily feedback that takes the current UI "for granted" but looks deeper.
What is broken? Send hate.
As more context, one reason I'm working through the Arcade refactor is that I'd like us to have a way to make tweets / social-posts more visible within the Arcade itself, since we have a community of players who come for games and it would be nice to make posts (and blog posts, etc.) more visible across applications. The current refactor is trying to simplify and clean-up the module in order to flexibly and easily add new features we'll need for this as well as NFT-powered gaming among other things, but the process is inviting a reconsideration of RS as well.
If anyone has thoughts, please feel welcome to share. Cannot promise specific implementations but there's a chance to make more fundamental changes in the next month or two if we can dovetail the changes in with the other work that is planned as everything else we have under development comes out.