0xJustinTime

I know stuff before they happen.

The only sandwiches I like are the ones with ham and cheese in the morning with a cold orange juice.

[0xJustinTime @0xJustInTime]

@alessandrod Hi @alessandrod , tried to give a Reth NodeApi like shape on agave to handle fork maintenance hell.

Struggling to get some feedback and visibility, would you help me out plz?

https://t.co/ljsZbhfKFI

[0xJustinTime @0xJustInTime]

@jtriley2p @Maddiaa0 > yolo sign p256 keys
Words are cheap, prove a working “yolo” version that survives the same scrutiny as ZCAM’s chain.

[0xJustinTime @0xJustInTime]

@gakonst etherscan

[0xJustinTime @0xJustInTime]

@gakonst @scoutgamexyz fav, I think reth should be sponsoring it

[0xJustinTime @0xJustInTime]

@hasufl When will block building be opened to everyone?

[0xJustinTime @0xJustInTime]

@gakonst The discord history might help!

[Sahn Lam @sahnlam]

How Discord Stores Trillions of Messages

In 2015, Discord started using MongoDB to store messages. By November 2015, there were already 100 million messages that did not fit in RAM, causing unpredictable latency.

In 2017, Discord moved to storing billions of messages in a Cassandra database. By 2022, the number of stored messages had ballooned to trillions across 177 nodes.

But Cassandra was plagued by several serious issues.

- Hot partitions occurred when a small number of high traffic channels overwhelmed nodes, cascading latency across the cluster.

- Garbage collection pauses created latency spikes.

- Compactions fell behind, forcing expensive reads to query multiple SSTables.

- Maintenance like node repairs interrupted service.

Discord migrated to ScyllaDB for the following benefits:

- Written in C++ instead of Java, eliminating disruptive garbage collection pauses

- Shard-per-core model provides stronger workload isolation to prevent hot partitions from cascading latency across nodes.

- Reverse query performance optimized to meet Discord's needs

- They reduced nodes to 72 while increasing disk space per node to 9TB.

To further protect ScyllaDB, Discord:

- Built intermediary data services in Rust that limit concurrent traffic spikes

- Data services sit between the API and database, coalescing requests

- Query the database just once even if multiple users request the same data

- Rust provided fast, safe concurrency ideal for this workload

The results? Tail latencies down from 40-125ms to a steady 15ms. Database uptime improved from weekend-long outages to smooth sailing. The system easily handled World Cup traffic spikes, processing events like goals and penalties without breaking a sweat. Discord continues to scale, now reliably storing trillions of messages with ScyllaDB.

–
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/kNfv0DVDdf

[0xJustinTime @0xJustInTime]

@chainbound_ Can I get a 3 days trial plz?

[0xJustinTime @0xJustInTime]

@bertcmiller @LidoFinance What’s the block hash please?

[0xJustinTime @0xJustInTime]

@gakonst @fla63551709 Totally agree.
Etherscan is a static website, like if frontend devs didn’t have a mock-up to work from. Transaction action should be the first thing IMO. So much space for improvement.

[0xJustinTime @0xJustInTime]

@thal0x @thal0x where can I find the EOA involved in the scam?

[0xJustinTime @0xJustInTime]

9. This story teaches us how ninjing in the mempool can be applied to parties, or more globally life situations (be careful tho, never forget ethics!!).

[0xJustinTime @0xJustInTime]

How I ninjed my @letsraave ticket, a 🧵:

@StaniKulechov @LensProtocol @AaveAave

[0xJustinTime @0xJustInTime]

8. there I disguised me as a poor user that got locked from eventbrite and could not access again his pending order, and my ticket came to me quite fast!