Odin.fun has outlined another week of development work, reporting 111 commits and 36 pull requests during its Week 33 update, alongside the release of two features and a long-running investigation into its authentication and access systems.
The latest update focuses on private community chat, Redis caching, staking changes and improved monitoring of two-factor authentication (2FA) adoption.
Private community chat is now live, with the feature covering per-channel infrastructure, a live feed and gated content through a locked panel. The system also supports access revocation during an active session, allowing permissions to be removed without requiring users to reload the page.
According to the development update, access controls are enforced at both the frontend and backend levels. Odin.fun also said its end-to-end testing suite now authenticates using a real token rather than a mock, giving the team a way to test the access system under conditions closer to actual use.
The team has also introduced Redis caching for comment upvotes and community reads. The implementation was designed around potential database and cache failures rather than treating them as secondary concerns.
Each vote now uses a dual-write approach, while cached counters are removed if the corresponding database write fails. The system also prevents an invalid comment ID from interfering with vote handling, while cache misses are served directly from the primary database.
Odin.fun said the work was designed to ensure that failures in one part of the system do not produce misleading information elsewhere. That approach is particularly relevant for vote counts and community activity, where stale or incorrect cached data could otherwise affect what users see.
The staking interface has also been refactored. A shared useStakeForm hook has been extracted from the interface, leaving the StakeDialog as a thinner component. The change is intended to simplify the underlying implementation and make the staking flow easier to extend.
A change has also been made to how withdrawal fees are handled. The fee is now prepaid when a user stakes rather than being deducted at the point of withdrawal. Users extending a lock are also asked to choose the intended action before proceeding.
The refactoring work resolved 10 circular imports, according to the update, addressing dependencies within the codebase while changes were being made to the staking system.
Monitoring has received attention as well. Odin.fun has introduced a gauge that measures actual 2FA adoption on a 15-minute cadence. The team also corrected a metric that had previously been labelled “user cancelled”. It was actually recording instances where the canister had declined an action.
The distinction matters for interpreting operational data. A user choosing to cancel an action represents a different behaviour from an action being rejected by the underlying system, and combining the two could give developers an inaccurate picture of how users interact with 2FA.
The development update also refers to a three-month investigation that has now produced what the team describes as a real answer, although the post does not provide extensive detail about the mystery in its summary of the week’s work.
Taken together, the changes show a week focused heavily on infrastructure, access controls, data reliability and developer maintenance alongside new user-facing functionality. Odin.fun’s update follows its stated approach of building in public, giving users and developers a view of the technical work taking place behind the platform.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion