Conversation

Replying to

8) Even things seemingly technological and well defined have edge cases you wouldn't predict. We're incredibly careful to make sure that there are no large vulnerabilities, and that the exchange runs smoothly! No matter what, we have to make sure nothing can be too bad.

1

1

23

9) But even if you've secured everything vital, you can't predict everything disruptive. For instance, the most recent time that FTX had ~1 minute of GUI slowness, this was the cause:

1

2

27

10) Sure, you can hide the candy bowl from attackers, but that doesn't mean you won't wake up to graffiti on the outside. The point, really, is that there are a lot of things you won't predict. And some of those really matter. And sometimes the only way to find out is to try.

1

1

14

11)

recently started an interesting thread. The question: can Solana actually, really, support an on-chain, decentralized

? twitter.com/BrendanEich/st There were lots of interesting back and forths on it.

Quote Tweet

Replying to @mjpldn @m_j_po and 2 others

500M tweets/day (and growing) is 5787 tweets/sec. What is likely TPS for final tweet-txns (typos4evar ;-) of Solana given the contention from worst-case and average user load? Not 50KTPS. twitter.com/BrendanEich/st…

2

6

24

12) We could debate it forever, but that will never address some of the core questions: --Will RPC servers be overwhelmed? --What happens when everyone tweets at once? --What type of history do people want fast access to? And above all: would anyone actually use it?

1

13

13) And, really, most of the future of Serum, and of Solana, can't be answered analytically. It depends on what we do.

projectserum.medium.com

An Ultimate Vision for Serum

It’s easy to get lost in the weeds. Everything has strengths and weaknesses; what matters isn’t rattling them off or proving you know of…

1

22

14) So, we build. github.com/project-serum/ And, hopefully, we ship. projectserum.com/tokens

2

2

16

15) Sometimes people don't build, and they do well anyway. And it can be tempting to be bitter, or dismissive, or to stop trying. But that's not really the right thing to do. Really, the response is: "They had a huge head start. Imagine where they'd be if they also built?"

3

1

34

16) (As an aside: I'm incredibly proud of what our team has done the last two years, and how far we've gotten. We're not the only ones growing, though. And while we obviously take different approaches,

,

and @OKEx have fought hard for their success.)

1

19

17) Some projects are "blue chip" because they're old, and that's frankly worth a lot. Even if they never do anything innovative again, they have a large userbase and adoption. A few of these come to mind: coingecko.com/en/defi

2

13

18) The real danger zone -- the place you can't escape from, really -- is if you're new, and *also* don't build. Maybe that's what the world got wrong about

: it's new, and had tough times. But it never stopped building.

11:47 AM · Jan 11, 2021Twitter Web App

Replying to

19) And so when I look at a new project, I ask: --Does the world need this? --Will it be well done? and above all: --Will it keep pushing forward with all it has? Because in the end no one guesses exactly the right thing to build the first time.

1

4

25

20) Everyone has to iterate, and take feedback, and above all keep move forward, if they want to grow bigger than they are.

1

1

15

21) So I guess I disagree with

, in a sense. And it seems like some of the people around him disagree, too, in a similar way.

2

1

13

22) There are two secrets, really. One is to begin: for some things, it's the only way to learn. The other is to take what you learn from it, update, and iterate. Half the battle is in getting started; the other half is in pushing forward, as hard as you can.

9

31

138