Exciting news everyone! We're thrilled to announce that our #Cardano stake pool, "Tempus," with the ticker TMS, has officially gone online! 🚀🎉 $ADA pool.pm/383b795108e351cb68a8…

⏲️ [#TMS] Tempus Epoch 605 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 12/12 🗓️ Estimated : 8.1 🎁 Luck : 148.15% 👀 Outlook Epoch 606 🧱 Assigned Slots : 7 🎁 Luck : 88.95% #Cardano

🧑‍💻 New SDK Release 🎉 We are excited to release Python SDK for Cardanoscan APIs. Developers can use this SDK to easily build apps on Cardano using Cardanoscan APIs. SDK - github.com/StricaHQ/cardanos… API Doc - docs.cardanoscan.io/

⏲️ [#TMS] Tempus Epoch 604 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 10/10 🗓️ Estimated : 8.1 🎁 Luck : 123.46% 👀 Outlook Epoch 605 🧱 Assigned Slots : 12 🎁 Luck : 148.15% #Cardano

⏲️ [#TMS] Tempus Epoch 603 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 7/7 🗓️ Estimated : 7.87 🎁 Luck : 88.95% 👀 Outlook Epoch 604 🧱 Assigned Slots : 10 🎁 Luck : 123.46% #Cardano

⏲️ [#TMS] Tempus Epoch 602 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 4/4 🗓️ Estimated : 9.05 🎁 Luck : 44.2% 👀 Outlook Epoch 603 🧱 Assigned Slots : 7 🎁 Luck : 88.95% #Cardano

⏲️ [#TMS] Tempus Epoch 601 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 6/6 🗓️ Estimated : 9.08 🎁 Luck : 66.08% 👀 Outlook Epoch 602 🧱 Assigned Slots : 4 🎁 Luck : 44.2% #Cardano

⏲️ [#TMS] Tempus Epoch 600 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 11/11 🗓️ Estimated : 8.51 🎁 Luck : 129.26% 👀 Outlook Epoch 601 🧱 Assigned Slots : 6 🎁 Luck : 66.08% #Cardano

⏲️ [#TMS] Tempus Epoch 599 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 16/16 🗓️ Estimated : 7.64 🎁 Luck : 209.42% 👀 Outlook Epoch 600 🧱 Assigned Slots : 11 🎁 Luck : 129.26% #Cardano

Who wants to be our 200th delegation? 😂

⏲️ [#TMS] Tempus Epoch 598 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 17/17 🗓️ Estimated : 24.89 🎁 Luck : 68.3% 👀 Outlook Epoch 599 🧱 Assigned Slots : 16 🎁 Luck : 209.42% #Cardano

⏲️ [#TMS] Tempus Epoch 597 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 23/25 (2x stolen) 🗓️ Estimated : 24.68 🎁 Luck : 101.3% 👀 Outlook Epoch 598 🧱 Assigned Slots : 17 🎁 Luck : 68.3% #Cardano

How things can change in a hour. 😂 Thanks again!

Really sad to see CF-delegation move on, but also very grateful for the time I was able to benefit from it. 🫡 Thanks @Cardano_CF Nearly 2400 blocks produced so far! 3000 here we come!

Sadly we cant post a epoch summory today because of the incident from 2 days ago. We are currently resyncing the CNCLI db for the next epoch again. Block production works flawless in the meantime.

Really sad to see another OG is retiring his pool.

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.

Upcoming: ADAM app will generate your yearly staking tax report 🗒️ You choose your wallet, a year and the currency. I will generate 5 reports before this feature goes live for free. Please DM me with your staking address, year 2020-2025 and currency 🇺🇸 🇪🇺 🇬🇧🇨🇭🇯🇵 🇨🇦 🇦🇺 🇮🇳 🇧🇷 🇿🇦 🇸🇬 🇳🇬 🇰🇷 🇮🇩 #cardano #spo #staking #ada

Due this incident, we had to upgrade our nodes immediately which may leads to some missed blocks in this epoch due a ledger replay. Its important to us to communicate such things in a transparent and honest way. Thanks for your support guys!

⏲️ [#TMS] Tempus Epoch 595 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 26/28 (2x stolen) 🗓️ Estimated : 24.35 🎁 Luck : 114.99% 👀 Outlook Epoch 596 🧱 Assigned Slots : 24 🎁 Luck : 99.01% #Cardano

⏲️ [#TMS] Tempus Epoch 594 👨🏼‍🌾 We have minted our last block this Epoch ⛏️ Blocks : 26/26 🗓️ Estimated : 24.34 🎁 Luck : 106.82% 👀 Outlook Epoch 595 🧱 Assigned Slots : 28 🎁 Luck : 114.99% #Cardano