Community driven Twitter Space being hosted on NFTs today at 6pm UTC https://twitter.com/benohanlon/status/1380466776320917506
Twitter
Ben serves IOHK's technical communities 🥑
A community-driven ideation session around #NFTs on Twitter Spaces today 6pm UTC. 🎙️ DMs open if you think you'd be a good speaker 📅 Add to calendar: evt.to/oeoodgmw. 🎨 Ideation board for people who want to suggest topics or questions reetro.app/board/5f…
SPO Digest is shipped! https://mailchi.mp/iohk/spo-digest-673450
Daedalus 4.0.5 is now available on Testnet, Flight, and Mainnet
Release notes: https://iohk.zendesk.com/hc/en-us/articles/900006675083
Release notes: https://iohk.zendesk.com/hc/en-us/articles/900006675083
Earlier today, you will likely have noticed a pause in block production of c.25m mins after the recent epoch boundary.
Some spike in CPU usage and network pause is to be expected, and this delay was well within modeled bounds. However, this pause was significantly longer than usual.
The network is functioning normally. However, over the next 24 hours, our engineers will profile the performance of the node to determine the cause, along with additional testing so we can mitigate and optimize as needed.
We’ll be sure to share our findings with you once we have determined next steps.
Some spike in CPU usage and network pause is to be expected, and this delay was well within modeled bounds. However, this pause was significantly longer than usual.
The network is functioning normally. However, over the next 24 hours, our engineers will profile the performance of the node to determine the cause, along with additional testing so we can mitigate and optimize as needed.
We’ll be sure to share our findings with you once we have determined next steps.
QUICK UPDATE: Last night we reported on the unexpectedly long pause at the epoch boundary.
After investigation today, the node team has now identified the likely root cause. This was due to the node repeating a computation that should have been done just once at the epoch boundary, due to the way the leaders slots are computed in the consensus rules.
We’ve seen positive results from initial tests on the node, and the team has now determined an update that should alleviate the issue at the next epoch boundary.
We’re continuing to test and will next move the update into QA for final testing. We’ll bring you a further update as soon as we have determined a timeframe for release. Thanks for your cooperation.
After investigation today, the node team has now identified the likely root cause. This was due to the node repeating a computation that should have been done just once at the epoch boundary, due to the way the leaders slots are computed in the consensus rules.
We’ve seen positive results from initial tests on the node, and the team has now determined an update that should alleviate the issue at the next epoch boundary.
We’re continuing to test and will next move the update into QA for final testing. We’ll bring you a further update as soon as we have determined a timeframe for release. Thanks for your cooperation.
UPDATE: On Thursday, we reported on the unexpectedly long pause at the epoch boundary.
After further investigation, we concluded this was due to the node repeating a computation that should have been done just once at the epoch boundary.
Yesterday, our engineers identified a fix to alleviate the issue. We’ve been doing extensive testing and QA today, and subject to final checks, we will be finalizing a point release (1.26.2) which we aim to release later today.
We’ll alert you as soon as this is available.
This will ensure that block producing nodes do not unnecessarily re-evaluate the stake distribution at the epoch boundary. We’ll also continue to optimize this through future releases.
We are asking that once the release is available, all stake pool operators install this update prior to the next epoch boundary, which take place on Tuesday 20th at 21:44:51 UTC.
Thanks very much for your support.
After further investigation, we concluded this was due to the node repeating a computation that should have been done just once at the epoch boundary.
Yesterday, our engineers identified a fix to alleviate the issue. We’ve been doing extensive testing and QA today, and subject to final checks, we will be finalizing a point release (1.26.2) which we aim to release later today.
We’ll alert you as soon as this is available.
This will ensure that block producing nodes do not unnecessarily re-evaluate the stake distribution at the epoch boundary. We’ll also continue to optimize this through future releases.
We are asking that once the release is available, all stake pool operators install this update prior to the next epoch boundary, which take place on Tuesday 20th at 21:44:51 UTC.
Thanks very much for your support.
NEW RELEASE COMING SOON: We have now fully QAd and tagged release 1.26.2 and will soon push it to our own pools before releasing it publicly. Please expect to see this new release drop within the next few hours.
PLEASE UPDATE YOUR NODES: Last night, after completing QA testing, we successfully released a new node version (1.26.2).
This will address the block production issues we encountered earlier this week, by ensuring that block producing nodes do not unnecessarily re-evaluate the stake distribution at the epoch boundary. We’ll also continue to optimize this through future releases.
We are asking all stake pool operators install this update prior to the next epoch boundary, which takes place on Tuesday 20th at 21:44:51 UTC.
Full release notes can be accessed here: https://github.com/input-output-hk/cardano-node/releases/tag/1.26.2
Please note: This point release is a recommended upgrade for all stake pool operators. It is not required for relays or other passive nodes, but feel free to update these too if you wish.
Thanks very much for your support and patience during this process, and see you all in the next epoch.
This will address the block production issues we encountered earlier this week, by ensuring that block producing nodes do not unnecessarily re-evaluate the stake distribution at the epoch boundary. We’ll also continue to optimize this through future releases.
We are asking all stake pool operators install this update prior to the next epoch boundary, which takes place on Tuesday 20th at 21:44:51 UTC.
Full release notes can be accessed here: https://github.com/input-output-hk/cardano-node/releases/tag/1.26.2
Please note: This point release is a recommended upgrade for all stake pool operators. It is not required for relays or other passive nodes, but feel free to update these too if you wish.
Thanks very much for your support and patience during this process, and see you all in the next epoch.
GitHub
Release Cardano Node 1.26.2 · IntersectMBO/cardano-node
This point release is a recommended upgrade for all stake pool operators. It is not required for relays or other passive nodes. It ensures that block producing nodes do not unnecessarily re-evalua...
A polite request to fill out our SPO Pulse survey for April https://input-output.typeform.com/to/ifq5D45Y. It helps us to gather feedback into one place and for this reason it's very important to the team.
Typeform
SPO Pulse - April 2021
We'd like your feedback.
Well, there we go. A good smooth ride over epoch boundary 261. Thanks to all SPOs who updated to 1.26.2 in good time. If you have yet to do so, please ensure you do over the next few days. We’ll still continue to improve and optimize but thanks to our engineers for a job well done. Onward! 🙏
SPO call tomorrow. Good news we upgraded the Zoom so we have more seats! Email invite has been sent https://mailchi.mp/iohk/spo-community-call
The Cardano Foundation’s delegation methodology is changing https://forum.cardano.org/t/the-cardano-foundation-s-delegation-methodology-is-changing/58465
Cardano Forum
The Cardano Foundation’s Delegation Methodology is Changing
The Cardano Foundation’s Delegation Methodology is Changing The Cardano Foundation would like to make an announcement regarding our delegation methodology. As many of you may be aware, our current delegation cycle has been delayed due to ongoing technical…
🚢 SPO Digest shipped https://mailchi.mp/iohk/spo-digest-673546
(Twitter Space is today... so click that button for calendar link!)
(Twitter Space is today... so click that button for calendar link!)
Announcement: https://twitter.com/IOHKMedia/status/1387051830442553351
Twitter
IOHK Media
We couldn't make you wait until Thursday! We're announcing our partnership with Ethiopia's Ministry of Education to create a blockchain-based national ID and attainment recording system. Rolling out to 5M students, this is the world’s largest blockchain deployment…
5 mins until we go live for Cardano Africa https://www.youtube.com/watch?v=yRjj662kJsk
YouTube
#CardanoAfrica – Join us for this very special event
This week we announced a historic deal with the government of Ethiopia to bring 5M young Africans to the #Cardano blockchain. Plus a deal to bring mobile connectivity and a financial identity to 100k people in Tanzania.
These are just the groundbreaking…
These are just the groundbreaking…
I've been away and a lot of the team are extremely busy on testnet related actives so we'll hold the regular SPO call next week same time on 13th May. In the interim any questions please drop them to me and we’ll do our best to bring you an update on the call.