|EDEN| Garden Pool

#Cardano Stake Pool

DRep ID: drep1sy4x93yl9c6q59ewmhxpkumkjnlz8th4wfetddj8lzryvsu7hqk

📽️ YouTube: Telegram:

[|EDEN| Garden Pool @EdenGardenPool]

In this video, I explain the entire Cardano delegation cycle from beginning to end, including where rewards come from. This is important to understand for both delegators and stake pool operators.

#Cardano $ADA

https://t.co/iobmZ3McBb

[|EDEN| Garden Pool @EdenGardenPool]

New video on How to setup a Midnight validator (updated) https://t.co/deFRcq5plz via @YouTube

[|EDEN| Garden Pool @EdenGardenPool]

💯

[Medusa Wallet (MDS pool | Medusa DRep) @MedusaAdaWallet]

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.

[Intersect @IntersectMBO]

Following an issue identified in the Preview environment yesterday, Cardano is currently experiencing a technical issue now on Mainnet.

Currently block production has slowed, and we’re working closely with @Cardano_CF and @InputOutputHK as we coordinate a technical response.

Node operators

- If you are running Node version 10.3.1 or higher please upgrade to Cardano Node 10.5.2. Link to repository https://t.co/MuHcWKfT3r

- If you are running a Cardano node below version 10.3.1 you do not need to take any action

- Daedalus users are unaffected

Thank you!

[Koios @CardanoKoios]

Hey Cardano fam — we’ve got 2 tickets to the Cardano Summit in Berlin 🇩🇪 and we’re giving them away! 🙌
To enter:
💙 Like this post
🔁 Repost it

That’s it! We’ll pick the winners after the giveaway closes at midnight UTC on Nov 3rd!😎✨
#Cardano #CardanoSummit2025 #Koios #Berlin

[|EDEN| Garden Pool @EdenGardenPool]

Please get in touch with me if any issues arise during registration.

Beware of scams! Anyone asking for your information is a scammer!

[|EDEN| Garden Pool @EdenGardenPool]

Dear EDEN Delegators, my partner lost all of his ADA in the attack. He is unable to provide the funds for reimbursing the rewards directly. The reimbursement process will have to include monthly payments over 12 months. If you were affected, register here!
https://t.co/vYkiAzu1pJ

[|EDEN| Garden Pool @EdenGardenPool]

We are figuring out the recovery plan for going forward, including reimbursing the missed rewards.

Sorry about this, I wish I could have done more, but the crypto space is unforgiving and my partner got burned heavily 😞 Working on minimising the damage to our delegators.

[|EDEN| Garden Pool @EdenGardenPool]

Be careful with scams out there. Rewards reimbursement updates will come only from official channels - this X account and our Telegram group. And they will not involve you in registering on any suspicious portals!

This is an impersonator! Stay safe

[|EDEN| Garden Pool @EdenGardenPool]

@KrizajMatic He fell for an impersonation tactic of the scammer pretending to be a Cardano Foundation employee with a special staking offer.

[|EDEN| Garden Pool @EdenGardenPool]

Hello everyone. Recently, my partner's wallets got hacked for pools 1 and 3. It happened right before the epoch switch, and I was made aware only after, so the pools will lose 2 epochs of rewards instead of 1.

Yesterday, the other 3 pledge wallets got hacked as well.

[|EDEN| Garden Pool @EdenGardenPool]

@Straightpool4 They were different keys, definitely a case of social engineering. The impersonator was pretending to be a Cardano Foundation employee with a special staking offer.

[|EDEN| Garden Pool @EdenGardenPool]

@snj_peters Thank you, I forwarded your contact info to my partner.

[|EDEN| Garden Pool @EdenGardenPool]

@Leo_Delegator For anyone interested, please see this post: https://t.co/G63epgQ0rV

[|EDEN| Garden Pool @EdenGardenPool]

Hello everyone. Recently, my partner's wallets got hacked for pools 1 and 3. It happened right before the epoch switch, and I was made aware only after, so the pools will lose 2 epochs of rewards instead of 1.

Yesterday, the other 3 pledge wallets got hacked as well.

[|EDEN| Garden Pool @EdenGardenPool]

We are figuring out the recovery plan for going forward, including reimbursing the missed rewards.

Sorry about this, I wish I could have done more, but the crypto space is unforgiving and my partner got burned heavily 😞 Working on minimising the damage to our delegators.

[|EDEN| Garden Pool @EdenGardenPool]

The pools have been updated to owner wallets under my control so that this cannot happen anymore.

From a technical POV, everything is working properly. Unfortunately, I couldn't do anything to prevent my partner from getting scammed. He lost all of his pledge as of now.

[AAA Stakelovelace @ADA_stake_pool]

welcome to Cardano 💩show week, what a time we live in, why 💩show you might ask, well in no particular order we have:

*) none of the big entities willing to submit a gov action for a lower Net Change Limit value that majority of DReps are happy with so we're now getting to the phase where twitter nudging/reminders/mild panic starts...
*) a pool hiking up fees to 100% before submitting a retirement intent update to pool certificate or updating their pool description to that effect 🤦‍♂️
*) entity responsible for handling hundreds of millions of treasury Ada continuing to dodge some simple questions about their documentation and the fate of not-paid-out-to-community-projects funds...
*) we're still with super top heavy in DRep vote power, with ~14% with a single voter, top 10 now having almost 50% of power and couple of the founding entities in the mix including one with about 9%...
*) a pool with 375% saturation level that's part of a pool group that contains about 8 other almost-empty pools...
*) at least four different budgets that I can think of that mention Daedalus wallet maintenance/improvements...

anywho, time for a long weekend Easter break, have a good day everybody... 🐇🥚🍫

[AAA Stakelovelace @ADA_stake_pool]

@Catalyst_onX can you please answer the following questions based on these screenshots:
1) What is Catalyst Treasury, where is it located and what is its current balance?
2) The highlighted documentation snippets seem to be either vague or inconsistent, can you please clarify what happens to funds not paid out to funded proposals?
3) Who manages the staking of these two huge wallets that seem to contain ~60 of 102 million Ada withdrawn from treasury for Fund 12/13, who owns the earned staking rewards and where is all this documented currently?

Thanks in advance (cc'ing @InputOutputHK just in case)

[|EDEN| Garden Pool @EdenGardenPool]

@Catalyst_onX We need more transparency from you.

#Cardano community, inquiries have gone ignored for a while now. We won't get answers if you don't raise your voice.

[AAA Stakelovelace @ADA_stake_pool]

@Catalyst_onX can you please answer the following questions based on these screenshots:
1) What is Catalyst Treasury, where is it located and what is its current balance?
2) The highlighted documentation snippets seem to be either vague or inconsistent, can you please clarify what happens to funds not paid out to funded proposals?
3) Who manages the staking of these two huge wallets that seem to contain ~60 of 102 million Ada withdrawn from treasury for Fund 12/13, who owns the earned staking rewards and where is all this documented currently?

Thanks in advance (cc'ing @InputOutputHK just in case)

[Homer J @AaaStake]

Anyone knows who owns the accumulated rewards from 40+ million of presumably Catalyst Fund Ada being staked to some nameless pool? https://t.co/szV1lYxaQc

Is it a part of some Catalyst self-funding setup by design?

[|EDEN| Garden Pool @EdenGardenPool]

@BJJSebi @MidnightNtwrk "However, specifics like total supply, initial distribution, exact burn rates, or staking rewards for NIGHT, as well as the precise decay formula for DUST, have not been fully publicized yet."

[|EDEN| Garden Pool @EdenGardenPool]

Here is a video on how to set up a @MidnightNtwrk validator from scratch!

https://t.co/7w9ZxUrYJp

#Cardano #CardanoCommunity #CardanoGirls #MidnightNetwork

[Koios @CardanoKoios]

New Koios Release is now published. A bunch of new endpoints (including Calidus key support and pool groups). Thanks to all the requests/feedbacks received.
Please checkout the release notes for changelog and schedule.
https://t.co/cVE8XAAO6o