_jhunsaker

what happens if there is a bug in geth (or any other client implementation - erigon/nethermind/reth/etc) that results in automated slashing?

does the client team reimburse the stake that was slashed?

if not, is that "fair"?

if they do, what if the slashing is widespread?

USDC is a verb

"I'll USDC you"

soon crypto as you know it will be co-opted by tradfi and then we can start anew

Some projects have been successful at leveraging Monad's mindshare to build their own.

The recipe is simple: just start making comparisons to Monad. No need to adhere to any sort of honest discussion. Apples to oranges comparisons are fine, because the readers won't think that hard anyways.

Individual accounts will do the same. "Monad sucks". Ok, then why are you posting about it? Leveraging mindshare again.

Often I'm asked if I like this or that project. Almost all the time I say "no opinion". Because if I had an opinion worth anything I'd put actual money behind it. (Although I might try to reason with them on the fly to be helpful.)

Irrational bag bias is huge in this industry. Most actually have very little conviction in their negative opinions they share on CT, otherwise there'd be a lot more short positions (respect to those that do). Far more projects go to zero than are successful (as it should be with startups), a lot of short opportunity there.

Don't get distracted by all this nonsense, just keep building.

L2s can continue to fight over preconf/miniblock latency - after 10ms, we'll see 1ms, then 100us, and so on (I wasn't kidding when I said L2s should sell datacenter space)

@monad_xyz is intended to be a globally-distributed L1 which will always be constrained by the laws of physics

there are some other L1s which actually have worse technical implementations but perform better because the majority of stake is concentrated in a region. Monad isn't intended to compete with that either

many of these demos you see are disingenuous - running one tx, waiting for finality, then running another tx, etc

that's not how computer games are actually implemented - latency is hidden in games by pipelining actions

if properly designed, a game can perform nearly the same for the user with 10ms latency or 100ms latency - the same techniques can and should be applied here as well

at @category_xyz we'll focus on building things like L1 preconfs, MCP, etc that bring the best performance possible for a global decentralized network

are there good examples of automated slashing that were truly from malicious behavior (as opposed to incompetence - such as accidentally running two nodes with same key)?

It never ceases to amaze me that hackers are smart enough to design and execute the hack but are often not smart enough to quickly secure and launder the funds (obviously this is a good thing)

Most annoying NYC visitor?
1. European tourist
2. Crypto bro-nerd

seems odd to try to apply any sort of valuation model to chains when they are clearly still 90%+ pure speculation

Solana replacing consensus is further evidence there are actually little to none technical moats in crypto.

idgaf chain

single sequencer? idgaf
ponzinomics? idgaf
copy/paste code? idgaf
misleading tech? idgaf
sketchy mm deals? idgaf
non-existent lockups? idgaf
multisig with my two friends? idgaf
centralized RWAs? idgaf

dm to angel

In trading we used to speculate: Will the fast get smarter or will the smart get faster?

The fast got smarter.

I think this will play out similarly in crypto.

Ethereum doesn't have outages because it's not even trying to push the boundaries of what's possible.

doing some late night TA

you can forget about mainnet now