Odin.fun fixes trading, community and session issues in busiest week of development

Odin.fun recorded 161 commits and 60 pull requests during its 34th week of development, making it the platform’s busiest week in a month.

Much of the work focused on resolving issues that were affecting the platform quietly rather than introducing prominent new features.

One change affects token comments. Comments now require users to hold the token they want to comment on. The holding check is cached through Redis for each user and token, with a 60-second time-to-live. Odin.fun said internal faults cannot be cached as a refusal, helping prevent temporary system errors from incorrectly blocking users. Legacy routes were deprecated after the new gate reached parity with the previous implementation.

Community earnings have also become easier to track. Communities receive a BTC fee from every trade made by their members, although there was previously no way to view those earnings directly. The latest update materialises the earnings hourly and makes them available through community statistics.

The development team also identified and corrected an issue with the trading panel’s fee calculations. The Buy/Sell interface had been estimating price impact using a 1% fee, while the canister charges 2.2% for the unbonded trading path.

As a result, users using the default 1% slippage setting could encounter failed unbonded purchases. The problem was not caused by market movement, but by the interface allocating an incorrect amount for fees. The fix has been made and is currently in staging.

Another update addresses session handling across browser tabs. Previously, logging out from one tab could leave an active session running in other tabs. Odin.fun has addressed this through the browser’s BroadcastChannel mechanism, allowing logout events to propagate across tabs and ensuring sessions are closed in the correct order.

The update reflects a week focused largely on reliability, consistency and visibility across the platform. Rather than concentrating on a single headline feature, the development work addressed several smaller issues affecting how users trade, participate in communities and manage their sessions.

Odin.fun described the approach simply: “Building in public, one week at a time.”