Recently, the Cardano network was put to the test due to a spam attack that threatened to disrupt its operations.
According to Fluid Token CTO Elraulito, Tuesday’s DDOS attack began at block 10,487,530, with each transaction executing 194 smart contracts. The attacker spent 0.9 ADA per transaction and filled each block with multiple transactions in an attempt to stress the network.
However, the attempt was unsuccessful and was mitigated before any damage occurred, and the network continued to function normally.
https://t.co/cxNveyOLDd pic.twitter.com/VuibaSPw67
— Charles Hoskinson (@IOHK_Charles) June 26, 2024
In response to the incident, Cardano founder Charles Hoskinson took to social media to offer an update from Intersect, a membership-based organization that supports the Cardano ecosystem, further amplifying the message with a YouTube video summarizing the incident.
In another tweet, Hoskinson responded with a GIF to a user’s tweet about Cardano’s resilience after the DDOS attack.
Network performance and impact
According to Intersect, the Cardano network has been under higher than normal load due to the spam attack. This has caused difficulties for some stake pool operators (SPOs), mainly due to the intensification of block height battles. Despite these challenges, the Cardano network has remained resilient.
We can also summarize the events with the following video: https://t.co/b5bt2PHo0b https://t.co/IP8jzduvF8
— Charles Hoskinson (@IOHK_Charles) June 26, 2024
The Cardano chain continued to operate as expected, with only a small impact on overall transaction times and some reduction in chain density.
While thanking the Cardano community for its rapid response and support in identifying the source of the spam attack on the Cardano mainnet, Intersect said it has coordinated a technical task force with ecosystem partners to identify potential solutions and integrate community efforts in solving the problem.
Looking ahead, the task force will work to identify and test a solution that mitigates this type of spam attack and will continue to update the community via Discord and social channels. Once a solution has been properly tested and deployed, the new version of the node that SPOs can upgrade to will be made public.