Scientists Develop Eye-in-a-Care-Box Device to Keep Whole Eyes Alive and Responsive to Light for 10 Hours After Death, Advancing Future Transplant Possibilities
Transplant surgeons have long mastered procedures for hearts, lungs, and kidneys, yet the whole eye remains an elusive target for successful transplantation. The extracted eyeball rapidly loses oxygen, causing light-sensitive retinal cells to die before surgeons can even prepare the organ for surgery. In a groundbreaking development, an experimental perfusion device has enabled biologists to slow tissue degradation and preserve the light response in pig eyes for up to 10 hours after the animal’s death.
The ECaBox Perfusion System
The device, named Eye-in-a-Care-Box (ECaBox), features a 3D-printed housing that holds the extracted eye. A flexible tube is inserted into the ophthalmic artery, and a pump continuously delivers an oxygenated nutrient solution while sensors regulate pressure and flow rate. This artificial circulation mimics the blood supply that normally nourishes ocular tissues during life.
Retinal Vulnerability and the 2024 Transplant Milestone
The retina—a thin layer of neural tissue lining the back of the eye—converts light into electrical signals that travel via the optic nerve to the brain. Even brief interruptions in blood flow damage this complex structure, sharply reducing transplant viability. Interest in eye transplantation surged after a 2024 procedure in which a man received a combined face and left-eye transplant following severe electrical trauma. Although vision did not return, the donor eye regained blood flow and retained retinal light responses, proving that reperfusion is possible but underscoring the remaining hurdle of optic-nerve reconnection.
Experimental Design and Pig-Eye Results
After the clinical case, researchers tested whether whole-eye preservation ex vivo could extend the window for potential transplantation. Pig eyes obtained from a nearby slaughterhouse were placed on ice and delivered to the lab within 2.5 hours of death. One group was connected to ECaBox; controls were stored at 4 °C without perfusion. After 24 hours, ECaBox eyes showed markedly better preservation of cells and vessels. In 90 % of correctly cannulated specimens, colored dye confirmed uniform perfusion through arteries, veins, and capillaries. Electroretinography detected electrical responses to light flashes in 15 of 36 perfused eyes, with several still reactive 10 hours post-mortem. Responses faded once the pump was stopped, confirming that the oxygenated solution sustained cellular function.
Timing and Human-Eye Validation
Delay proved critical: initiating perfusion more than five hours after death caused significantly greater vascular damage. The team then evaluated 12 human eyes from six post-mortem donors; one eye per pair received ECaBox support while the other served as a control. Perfused human specimens again demonstrated superior tissue architecture and cell viability, although electroretinography was not performed due to ethical and logistical constraints.
Future Applications and Remaining Challenges
Developers envision a portable operating unit that would allow immediate cannulation beside the donor, minimizing ischemic time. While ECaBox cannot yet solve optic-nerve regeneration—necessary for image-forming vision—it offers immediate value for studying retinal diseases such as age-related macular degeneration. Large-animal eyes preserved ex vivo provide access to the macula, absent in rodents, enabling drug testing without live-animal procedures. Further work will determine maximum preservation duration and confirm light responses in rapidly connected human retinas.
Related articles
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.