Olivia
Online
Алексей 🇷🇺
@AlekseiCardano
Москва, Россия
Joined October 2018
110 Following
95 Followers
401 Posts
@TSherwinMagic Обожаю эти видосы))
Who to follow
@garaevruslan03 Не дослушал до конца, Мытищи есть в перспективе?
@hybrydtheory Дорога домой
@trushentsia Недавно из пакета такого документы переложил в вб-шный))
@gambala_codes Шутки шутками, а я сходил к лору, потом загрузил снимок в грока и попросил его написать заключение если бы он был Лором. Теперь я подозреваю что мой лор тоже гроком пользуется, результаты практически идентичные
@kogmak Пф, ответ же в самом сообщение - смотреть надо на тех у кого так же или хуже и полегчает. А эта призрачная морковка, которая недостижимо висит впереди только потратит твои силы на бег за ней. Учись получать удовольствие от того в той точке которой находишься.
The dingus who broke Cardano did nothing illegal.
It’s a permissionless network.
Cope and seethe.
One thing is certain: the recent attack on Cardano proved we can work together and find solutions quickly when it matters most.
Cardano just survived one of the biggest attacks in its history. @KpunToN00b allegedly unintentionally exploited a vulnerability in the node software (one previously seen on testnet) and forked the mainnet chain. Both versions continued running without halting, demonstrating the network’s resilience.
Yes, this incident caused significant financial, emotional, and reputational damage. But it wasn’t malicious, and the person responsible came forward immediately to help fix it.
Now here’s my question: If we’re so proud of our superior blockchain architecture, decentralization, and on-chain governance, shouldn’t we prove it? Let’s decide on-chain whether this person should face legal prosecution.
Think about recent incidents in the traditional world – CrowdStrike, AWS, Cloudflare. The FBI most likely didn’t go after the employees of these companies who made mistakes or didn’t understand the consequences, even though the damage was far worse than what happened on Cardano.
We have the tools to handle this the web3 way. Let’s use them - create a vote on chain to determine whether the perpetrator has to be prosecuted or not.
So what do you think, @Cardano community?
@RealAllinCrypto Read this
Okay, Cardano Community, someone has to start calling things by their proper names. Let that be me. I, Fell-x27, am writing this on my own behalf, not on behalf of any project.
0) As a wallet developer and as someone who has literally devoted everything to the Cardano ecosystem - I was just as stressed as everyone else about what was happening. And believe me, I was risking far more than the vast majority of those who consider themselves "victims." Cardano is what allows me to support my family, buy food, and literally live - not just "a stuck $1,000 exchange order."
You don’t need to tell me how hard your morning was. Mine was several times worse. Please read everything that follows with this in mind. Thank you.
1) In fact, nothing truly terrible happened. The network did not die and did not even stop. What actually happened was a split into a bugged fork and a clean fork. The bugged fork got slightly ahead because most nodes were running the buggy version. The clean fork didn’t stop - it continued operating and producing blocks, just more slowly than the bugged one. Your transaction would have gone through not in 20 seconds, but in 20 minutes. Almost like Bitcoin.
The only real problem was inconsistency, because you couldn’t guarantee the recipient was on the same fork as you. And by the way, this is standard behavior for any blockchain. If you ever wondered "why exchanges check the number of confirmations," here’s your answer.
However, a fix was deployed extremely quickly, and the network healed itself exactly as it’s supposed to. Everything went according to the expected safety mechanisms.
The fact that some multipool - which already harms decentralization and makes millions for free - happened to earn slightly less for one day will not make it go broke or ruin its life. Stop fanning the drama. Nobody died. The network did not collapse. Those claiming they were "liquidated because of this" are simply looking for someone else to blame for their leveraged trading. You were not liquidated because of @KpunToN00b. You were liquidated because of your own greed.
The ADA price, in case you didn’t notice, didn’t react at all. It stayed around 0.4. The incident was resolved almost instantly. Within just a couple of hours measures were implemented, and by the evening the fork was eliminated by the protocol itself. Do not exaggerate. Everyone was scared - sure. @KpunToN00b was scared no less. But it’s already in the past.
2) @IOHK_Charles is acting as if Cardano is his personal property and someone tried to break his toy. But that’s not the case. @IOHK_Charles is not the owner nor the CEO of Cardano. Not anymore.
Cardano is a decentralized network that belongs to no one. What *he* does own is IOG and a monopoly on developing cardano_node (for now) - which is precisely why a single bug was able to impact such a large portion of the network.
@IOHK_Charles, maybe call the FBI to investigate your QA process that allowed such a bug to slip through.
Also, the way you present your assumptions as facts - using the volume of your account - does not look good. For example, the preview-network bug was not discovered by @KpunToN00b. One moment you’re calling for an investigation, and the next you’re publicly assigning guilt and telling stories about events and motivations you know nothing about. And you’re dragging personal issues into it.
Charlie, for heaven’s sake, the world does not revolve around you. Seriously. Not everything happens for you, because of you, in your name, or about you. Accept that.
3) @KpunToN00b is not some movie villain trying to break something. For most people he’s just a Twitter avatar, but he’s not just an account. He is a kind, thoughtful, intelligent, empathetic person. One of the best QA engineers I know. Someone always ready to help without asking for anything in return. Someone trustworthy, someone who has never wished harm to anyone. I know this because - unlike you - I’ve known him for years.
Meanwhile, lots of people are trying to farm views and citations on this issue, running a bullying-PR campaign. Yes, he may not have perfect relationships with everyone - that happens, right @bigpey? I’m also not a fan of how benefits in the ecosystem are distributed between developers and influencers in favor of the latter, even though the ecosystem is built on the former. So what? That doesn’t make me a good or bad person - it’s just an opinion about something. Same with @KpunToN00b.
Don’t inject personal motives where there are none. Don’t pretend to be the only and ultimate victim. It’s not true, and it’s manipulative.
Maybe it’s time to turn off the witch-hunt mode and return to the real world?
5) @KpunToN00b acted without malicious intent. His goal was to test whether a node would accept a transaction into the mempool or reject it. There was no intention to publish it. He made a mistake. He regrets it. He is in a state of self-blame right now, and you are only making it worse.
That day I faced the possibility that by the evening I could lose everything my family’s well-being depends on. But I do not hold a grudge and I am not picking up a torch. I know he never meant to harm anyone - neither me nor you. And I want you to understand that too.
Yes, we all got nervous. Yes, everyone is venting emotions. Many are doing it here. It was difficult for every one of you. Now imagine what it’s like for one single person who is taking all of that weight onto himself.
Yes, the mistake was serious - but it benefited the ecosystem. It improved communication channels between SPOs and developers. It highlighted the risks of centralized development and the need for alternative node implementations (hello, @Amaru_Cardano!).
Consider it a fire drill. If (when?) something truly dangerous happens, we will be prepared. We know how to act. For God’s sake, we survived the ITN, which was dying in convulsions, but we stabilized it. And we handled yesterday’s incident. Which means we can handle anything.
We proved that a decentralized system made of thousands of independent components can, in a critical moment, act as a single entity for the common good. And that’s remarkable. Put the pitchforks down. Go home. Cardano is still running without interruptions.
Okay, Cardano Community, someone has to start calling things by their proper names. Let that be me. I, Fell-x27, am writing this on my own behalf, not on behalf of any project.
0) As a wallet developer and as someone who has literally devoted everything to the Cardano ecosystem - I was just as stressed as everyone else about what was happening. And believe me, I was risking far more than the vast majority of those who consider themselves "victims." Cardano is what allows me to support my family, buy food, and literally live - not just "a stuck $1,000 exchange order."
You don’t need to tell me how hard your morning was. Mine was several times worse. Please read everything that follows with this in mind. Thank you.
1) In fact, nothing truly terrible happened. The network did not die and did not even stop. What actually happened was a split into a bugged fork and a clean fork. The bugged fork got slightly ahead because most nodes were running the buggy version. The clean fork didn’t stop - it continued operating and producing blocks, just more slowly than the bugged one. Your transaction would have gone through not in 20 seconds, but in 20 minutes. Almost like Bitcoin.
The only real problem was inconsistency, because you couldn’t guarantee the recipient was on the same fork as you. And by the way, this is standard behavior for any blockchain. If you ever wondered "why exchanges check the number of confirmations," here’s your answer.
However, a fix was deployed extremely quickly, and the network healed itself exactly as it’s supposed to. Everything went according to the expected safety mechanisms.
The fact that some multipool - which already harms decentralization and makes millions for free - happened to earn slightly less for one day will not make it go broke or ruin its life. Stop fanning the drama. Nobody died. The network did not collapse. Those claiming they were "liquidated because of this" are simply looking for someone else to blame for their leveraged trading. You were not liquidated because of @KpunToN00b. You were liquidated because of your own greed.
The ADA price, in case you didn’t notice, didn’t react at all. It stayed around 0.4. The incident was resolved almost instantly. Within just a couple of hours measures were implemented, and by the evening the fork was eliminated by the protocol itself. Do not exaggerate. Everyone was scared - sure. @KpunToN00b was scared no less. But it’s already in the past.
2) @IOHK_Charles is acting as if Cardano is his personal property and someone tried to break his toy. But that’s not the case. @IOHK_Charles is not the owner nor the CEO of Cardano. Not anymore.
Cardano is a decentralized network that belongs to no one. What *he* does own is IOG and a monopoly on developing cardano_node (for now) - which is precisely why a single bug was able to impact such a large portion of the network.
@IOHK_Charles, maybe call the FBI to investigate your QA process that allowed such a bug to slip through.
Also, the way you present your assumptions as facts - using the volume of your account - does not look good. For example, the preview-network bug was not discovered by @KpunToN00b. One moment you’re calling for an investigation, and the next you’re publicly assigning guilt and telling stories about events and motivations you know nothing about. And you’re dragging personal issues into it.
Charlie, for heaven’s sake, the world does not revolve around you. Seriously. Not everything happens for you, because of you, in your name, or about you. Accept that.
3) @KpunToN00b is not some movie villain trying to break something. For most people he’s just a Twitter avatar, but he’s not just an account. He is a kind, thoughtful, intelligent, empathetic person. One of the best QA engineers I know. Someone always ready to help without asking for anything in return. Someone trustworthy, someone who has never wished harm to anyone. I know this because - unlike you - I’ve known him for years.
Meanwhile, lots of people are trying to farm views and citations on this issue, running a bullying-PR campaign. Yes, he may not have perfect relationships with everyone - that happens, right @bigpey? I’m also not a fan of how benefits in the ecosystem are distributed between developers and influencers in favor of the latter, even though the ecosystem is built on the former. So what? That doesn’t make me a good or bad person - it’s just an opinion about something. Same with @KpunToN00b.
Don’t inject personal motives where there are none. Don’t pretend to be the only and ultimate victim. It’s not true, and it’s manipulative.
Maybe it’s time to turn off the witch-hunt mode and return to the real world?
5) @KpunToN00b acted without malicious intent. His goal was to test whether a node would accept a transaction into the mempool or reject it. There was no intention to publish it. He made a mistake. He regrets it. He is in a state of self-blame right now, and you are only making it worse.
That day I faced the possibility that by the evening I could lose everything my family’s well-being depends on. But I do not hold a grudge and I am not picking up a torch. I know he never meant to harm anyone - neither me nor you. And I want you to understand that too.
Yes, we all got nervous. Yes, everyone is venting emotions. Many are doing it here. It was difficult for every one of you. Now imagine what it’s like for one single person who is taking all of that weight onto himself.
Yes, the mistake was serious - but it benefited the ecosystem. It improved communication channels between SPOs and developers. It highlighted the risks of centralized development and the need for alternative node implementations (hello, @Amaru_Cardano!).
Consider it a fire drill. If (when?) something truly dangerous happens, we will be prepared. We know how to act. For God’s sake, we survived the ITN, which was dying in convulsions, but we stabilized it. And we handled yesterday’s incident. Which means we can handle anything.
We proved that a decentralized system made of thousands of independent components can, in a critical moment, act as a single entity for the common good. And that’s remarkable. Put the pitchforks down. Go home. Cardano is still running without interruptions.
Okay, Cardano Community, someone has to start calling things by their proper names. Let that be me. I, Fell-x27, am writing this on my own behalf, not on behalf of any project.
0) As a wallet developer and as someone who has literally devoted everything to the Cardano ecosystem - I was just as stressed as everyone else about what was happening. And believe me, I was risking far more than the vast majority of those who consider themselves "victims." Cardano is what allows me to support my family, buy food, and literally live - not just "a stuck $1,000 exchange order."
You don’t need to tell me how hard your morning was. Mine was several times worse. Please read everything that follows with this in mind. Thank you.
1) In fact, nothing truly terrible happened. The network did not die and did not even stop. What actually happened was a split into a bugged fork and a clean fork. The bugged fork got slightly ahead because most nodes were running the buggy version. The clean fork didn’t stop - it continued operating and producing blocks, just more slowly than the bugged one. Your transaction would have gone through not in 20 seconds, but in 20 minutes. Almost like Bitcoin.
The only real problem was inconsistency, because you couldn’t guarantee the recipient was on the same fork as you. And by the way, this is standard behavior for any blockchain. If you ever wondered "why exchanges check the number of confirmations," here’s your answer.
However, a fix was deployed extremely quickly, and the network healed itself exactly as it’s supposed to. Everything went according to the expected safety mechanisms.
The fact that some multipool - which already harms decentralization and makes millions for free - happened to earn slightly less for one day will not make it go broke or ruin its life. Stop fanning the drama. Nobody died. The network did not collapse. Those claiming they were "liquidated because of this" are simply looking for someone else to blame for their leveraged trading. You were not liquidated because of @KpunToN00b. You were liquidated because of your own greed.
The ADA price, in case you didn’t notice, didn’t react at all. It stayed around 0.4. The incident was resolved almost instantly. Within just a couple of hours measures were implemented, and by the evening the fork was eliminated by the protocol itself. Do not exaggerate. Everyone was scared - sure. @KpunToN00b was scared no less. But it’s already in the past.
2) @IOHK_Charles is acting as if Cardano is his personal property and someone tried to break his toy. But that’s not the case. @IOHK_Charles is not the owner nor the CEO of Cardano. Not anymore.
Cardano is a decentralized network that belongs to no one. What *he* does own is IOG and a monopoly on developing cardano_node (for now) - which is precisely why a single bug was able to impact such a large portion of the network.
@IOHK_Charles, maybe call the FBI to investigate your QA process that allowed such a bug to slip through.
Also, the way you present your assumptions as facts - using the volume of your account - does not look good. For example, the preview-network bug was not discovered by @KpunToN00b. One moment you’re calling for an investigation, and the next you’re publicly assigning guilt and telling stories about events and motivations you know nothing about. And you’re dragging personal issues into it.
Charlie, for heaven’s sake, the world does not revolve around you. Seriously. Not everything happens for you, because of you, in your name, or about you. Accept that.
3) @KpunToN00b is not some movie villain trying to break something. For most people he’s just a Twitter avatar, but he’s not just an account. He is a kind, thoughtful, intelligent, empathetic person. One of the best QA engineers I know. Someone always ready to help without asking for anything in return. Someone trustworthy, someone who has never wished harm to anyone. I know this because - unlike you - I’ve known him for years.
Meanwhile, lots of people are trying to farm views and citations on this issue, running a bullying-PR campaign. Yes, he may not have perfect relationships with everyone - that happens, right @bigpey? I’m also not a fan of how benefits in the ecosystem are distributed between developers and influencers in favor of the latter, even though the ecosystem is built on the former. So what? That doesn’t make me a good or bad person - it’s just an opinion about something. Same with @KpunToN00b.
Don’t inject personal motives where there are none. Don’t pretend to be the only and ultimate victim. It’s not true, and it’s manipulative.
Maybe it’s time to turn off the witch-hunt mode and return to the real world?
5) @KpunToN00b acted without malicious intent. His goal was to test whether a node would accept a transaction into the mempool or reject it. There was no intention to publish it. He made a mistake. He regrets it. He is in a state of self-blame right now, and you are only making it worse.
That day I faced the possibility that by the evening I could lose everything my family’s well-being depends on. But I do not hold a grudge and I am not picking up a torch. I know he never meant to harm anyone - neither me nor you. And I want you to understand that too.
Yes, we all got nervous. Yes, everyone is venting emotions. Many are doing it here. It was difficult for every one of you. Now imagine what it’s like for one single person who is taking all of that weight onto himself.
Yes, the mistake was serious - but it benefited the ecosystem. It improved communication channels between SPOs and developers. It highlighted the risks of centralized development and the need for alternative node implementations (hello, @Amaru_Cardano!).
Consider it a fire drill. If (when?) something truly dangerous happens, we will be prepared. We know how to act. For God’s sake, we survived the ITN, which was dying in convulsions, but we stabilized it. And we handled yesterday’s incident. Which means we can handle anything.
We proved that a decentralized system made of thousands of independent components can, in a critical moment, act as a single entity for the common good. And that’s remarkable. Put the pitchforks down. Go home. Cardano is still running without interruptions.
@CardanoSaint You categorically don't consider the possibility that he did it by accident and sincerely repents? Of course, it's easier to hate someone the crowd is talking about. I thought our community was smarter.
@RealSaidov Dear Umed, I don't know your contribution to Cardano, but I know Homer as a responsive, cheerful, and intelligent member of the community. I've known him for many years and never seen any negative traits in him. You should reconsider promoting the hunt for a member of our family.
I found out I was already blocked by Homer J, though I’m not sure when it happened. Either way, I think this whole situation was handled smoothly thanks to the dev teams’ quick response, the fast actions from the SPOs, and the community sharing information in real time.
I was genuinely impressed by how strong and proactive the Cardano community can be.
But issues like this really shouldn’t happen again. Even if Homer J had something to do with it, the focus shouldn’t be on blaming him. It should be on making sure incidents like this can’t happen in the first place. A network needs to stay stable and resilient no matter what kind of issue or attack it faces.
Cardano will face a lot more attacks from different directions in the future. But I’m confident it’ll survive them, and each attempt will only push the ecosystem to evolve and mature even faster.
Last Seen Users on Sotwe
Trends for you
Most Popular Users
Elon Musk 
@elonmusk
241M followers
Barack Obama
@barackobama
119.2M followers
Cristiano Ronaldo
@cristiano
112.1M followers
Donald J. Trump
@realdonaldtrump
111.8M followers
Narendra Modi
@narendramodi
107.1M followers
Rihanna
@rihanna
98M followers
NASA
@nasa
92.2M followers
Justin Bieber
@justinbieber
91.2M followers
KATY PERRY
@katyperry
88.5M followers
Taylor Swift
@taylorswift13
82.4M followers
Lady Gaga
@ladygaga
73.9M followers
Virat Kohli
@imvkohli
71.2M followers
Kim Kardashian
@kimkardashian
70.2M followers
YouTube
@youtube
68.7M followers
Bill Gates
@billgates
64.4M followers
Neymar Jr
@neymarjr
64.1M followers
The Ellen Show
@theellenshow
62.4M followers
CNN
@cnn
61.8M followers
Selena Gomez
@selenagomez
61.6M followers
X
@x
60.8M followers