Swiss authorities have confirmed a case of #hantavirus identified in a passenger from the MV Hondius cruise ship.
He had responded to an email from the ship’s operator informing the passengers of the health event, and presented himself to a hospital in Zurich, Switzerland, and is receiving care.
In line with the International Health Regulations (IHR), WHO is working with relevant countries to support international contact tracing, to ensure that those potentially exposed are monitored and that any further disease spread is limited.
The type of virus in this outbreak has been confirmed as Andes hantavirus by the National Institute for Communicable Diseases @nicd_sa, South Africa and the Geneva University Hospitals @hug_ge, Switzerland
The support of the Institut Pasteur de Dakar @PasteurDakar, Senegal and the Administración Nacional de Laboratorios e Institutos de Salud @ANLIS_Malbran, Argentina has also been critical in responding to this event.
As of 6 May, there are 8 cases, 3 of whom are confirmed as hantavirus by laboratory testing.
WHO will continue to work with countries to ensure that the patients, contacts, passengers and crew have the information and support they need to stay safe and prevent spread.
Ethereum itself must pass the walkaway test.
Ethereum is meant to be a home for trustless and trust-minimized applications, whether in finance, governance or elsewhere. It must support applications that are more like tools - the hammer that once you buy it's yours - than like services that lose all functionality once the vendor loses interest in maintaining them (or worse, gets hacked or becomes value-extractive). Even when applications do have functionality that depends on a vendor, Ethereum can help reduce those dependencies as much as possible, and protect the user as much as possible in those cases where the dependencies fail.
But building such applications is not possible on a base layer which itself depends on ongoing updates from a vendor in order to continue being usable - even if that "vendor" is the all core devs process. Ethereum the blockchain must have the traits that we strive for in Ethereum's applications. Hence, Ethereum itself must pass the walkaway test.
This means that Ethereum must get to a place where we _can ossify if we want to_. We do not have to stop making changes to the protocol, but we must get to a place where Ethereum's value proposition does not strictly depend on any features that are not in the protocol already.
This includes the following:
* Full quantum-resistance. We should resist the trap of saying "let's delay quantum-resistance until the last possible moment in the name of ekeing out more efficiencies for a while longer". Individual users have that right, but the protocol should not. Being able to say "Ethereum's protocol, as it stands today, is cryptographically safe for a hundred years" is something we should strive to get to as soon as possible, and insist on as a point of pride.
* An architecture that can expand to sufficient scalability. The protocol needs to have the properties that allow it to expand to many thousands of TPS over time, most notably ZK-EVM validation and data sampling through PeerDAS. Ideally, we get to a point where further scaling is done through "parameter only" changes - and ideally _those_ changes are not BPO-style forks, but rather are made with the same validator voting mechanism we use for the gas limit.
* A state architecture that can last decades. This means deciding, and implementing, whatever form of partial statelessness and state expiry will let us feel comfortable letting Ethereum run with thousands of TPS for decades, without breaking sync or hard disk or I/O requirements. It also means future-proofing the tree and storage types to work well with this long-term environment.
* An account model that is general-purpose (this is "full account abstraction": move away from enshrined ECDSA for signature validation)
* A gas schedule that we are confident is free of DoS vulnerabilities, both for execution and for ZK-proving
* A PoS economic model that, with all we have learned over the past half decade of proof of stake in Ethereum and full decade beyond, we are confident can last and remain decentralized for decades, and supports the usefulness of ETH as trustless collateral (eg. in governance-minimized ETH-backed stablecoins)
* A block building model that we are confident will resist centralization pressure and guarantee censorship resistance even in unknown future environments
Ideally, we do the hard work over the next few years, to get to a point where in the future almost all future innovation can happen through client optimization, and get reflected in the protocol through parameter changes. Every year, we should tick off at least one of these boxes, and ideally multiple. Do the right thing once, based on knowledge of what is truly the right thing (and not compromise halfway fixes), and maximize Ethereum's technological and social robustness for the long term.
Ethereum goes hard.
This is the gwei.
Welcome to #MOONKIN on Ethereum🦉💎
Moonkin is a memecoin inspired by the Moonkin character from World of Warcraft a creature deeply connected to Vitalik Buterin, the creator of Ethereum. When Blizzard nerfed his favorite character, Vitalik experienced firsthand the pain of centralized control. That moment sparked the idea for Ethereum.
Moonkin isn’t just a meme it’s a nostalgic symbol, the spark that ignited an entire crypto civilization.
Moonkin doesn’t just live in the game. It lives in the heart of Ethereum.
Contract: 0x968dC061290f76f90B3b939cC9380D47d79A54C5
Telegram: https://t.co/8qa9KBw0Yz
Chart: https://t.co/46yNGWy7an