EOS Block Producers Crash After RAM Fault

Several block producers of the recently-launched EOS temporarily crashed after running into a RAM-related limitation.

Sounding the alarm on July 7th, 2018, top block producer EOS New York took to Twitter to explain the issue.

Some Block Producers crashed when RAM usage on EOS exceeded 1GB tonight.

According to EOS New York, the issue occurred when the platform's net RAM consumption exceeded 1GB - temporarily disabling a number of unnamed block producers.

Theoretically, EOS block producers can support up to 64GB of RAM capacity collectively.

Where faulty hardware may have been responsible, it would appear human error was the root cause - EOS New York explaining the block producers failed to configure their nodes correctly.

Initially, EOS New York claimed that the error highlighted a violation of the blockchain's reproducer agreement - a prospective block producer's code of conduct.

Where EOS intends to challenge Ethereum with high-throughput decentralized applications, it would require large quantities of RAM to offer such performance.

"EOS New York will not purchase or sell RAM for speculative purposes. We believe that the resources available on the EOS platform are meant to be used for their utility, not their ability to generate gains. EOS New York will use RAM for development reasons, either for our own projects or the projects of others which we support."

Block producer EOS Nation sees things differently, however.