Oisy’s latest update, v1.3.7, is now out in the wild, and while it’s not a complete overhaul, it brings a string of changes designed to make life smoother for the everyday user. No fireworks, no dramatic overpromises—just tangible tweaks and community-fuelled improvements that nudge the app in the right direction.
The big ticket this time? A bit of friendly bribery. Sprinkles Episode 3 introduces a refer-a-friend option that gives users the nudge to drag their mates along for the ride. There’s a clear quid pro quo: you get 10% of whatever your friend earns, and they keep the full amount of their reward. It’s automatic, and it requires zero convincing beyond a shared interest in holding, logging in and sending tokens. This follows the same playbook as previous Sprinkles campaigns, rewarding straightforward actions rather than asking people to jump through hoops. It’s simple. It’s working.
The Sprinkles programme is proving to be a sticky one, especially for users who like passive rewards and light-touch interaction. Now, that slight push to get others involved turns each user into a de facto ambassador—without the hard sell.
Beyond incentives, the update gives users better visibility and control over the networks they’re using. With the new ‘Manage Tokens’ function, there’s now a tidy way to view and manage active networks. It means quicker loading times and less noise, especially useful if you’re bouncing between multiple chains. It’s one of those under-the-bonnet tweaks that doesn’t shout, but makes a difference immediately for anyone who’s used to things slowing down or cluttering up.
A new filtering tool also enters the mix, addressing a small but meaningful pain point. It’s now possible to filter tokens and views by active network. Multichain is good. Multichain with filters is better. If your screen ever felt like a garden full of everything at once—useful but messy—this change allows users to focus only on what’s relevant. Cleaner views, less cognitive load, no faffing about trying to locate a token on the wrong chain.
The token list layout has been improved as well, geared towards better usability ahead of more chains being added soon. There’s no need to relearn anything; it just looks better and functions with less friction. Visibility of the relationship between tokens and their respective chains is clearer, and that goes a long way when you’re trying to keep track of assets across a growing number of networks.
Login, too, has had a bit of a refresh, specifically for Internet Identity (II) users. The login now redirects from the previous domain (ic0.app) to internetcomputer.org. For anyone concerned, the change is cosmetic at first glance, but it matters from both a security and branding standpoint. If your identity doesn’t appear straight away, there’s a minor extra step—re-enter manually—and after that, everything runs as it always did. The experience remains unchanged where it counts, but it’s a smoother, better-signposted road to get there.
Each of these updates on its own is modest. Together, they signal a commitment to making Oisy less of a tool and more of a place you want to return to regularly. The update isn’t trying to revolutionise the way people interact with the platform. It’s aimed at refining the experience. Quicker access. Cleaner interfaces. A clearer path to rewards. It’s the kind of release that gives the impression that the people building it are listening—and that’s been confirmed, not just claimed.
Just before the release went live, the Oisy community caught a critical issue and flagged it. That heads-up helped the team patch the problem before the wider announcement. This kind of dialogue between users and developers doesn’t happen everywhere, but when it does, it’s often the secret ingredient that keeps platforms afloat while others stumble on small bugs that go unaddressed. It’s not flashy, but it’s effective.
There’s an honesty to how this update has been rolled out. No chest-beating. No unnecessarily inflated language. Instead, there’s a straightforward breakdown of what’s changed and why it matters. It’s respectful of the user’s time and attention, which—given how crowded the digital wallet space is—can’t be underestimated.
Version 1.3.7 won’t blow the doors off. It doesn’t need to. It brings meaningful polish, community-driven fixes, and rewards that make sense. It prioritises the user in ways that are subtle but noticeable.
With multichain support on the rise and more assets being added all the time, these improvements seem to be laying the groundwork for something bigger, even if that’s not shouted about. Filtering tools and network visibility features aren’t flashy, but they make more sense the more you use them. The infrastructure is getting stronger—quietly.
It’s also worth pointing out the tone of communication here. Instead of jargon-filled patch notes or long-winded marketing speak, the release notes speak plainly. There’s a kind of everyday honesty to them that mirrors the update itself. There’s even a dash of humility, acknowledging the community’s role in catching issues before launch, which is rare and welcome. It sets a tone: this isn’t a walled garden, and user input isn’t just a checkbox for engagement metrics.
There’s also a degree of intentional restraint. Many platforms use updates like this to push things you don’t want. New banners, nagging notifications, or “helpful” prompts that overstay their welcome. Oisy has gone in a different direction. What’s new is useful, not intrusive. That might seem like a low bar, but when so much of tech nudges users into attention traps, it’s worth noticing when something avoids that entirely.
For those already familiar with Oisy, this version builds on the experience without getting in the way. For newcomers, it’s an easier point of entry than previous iterations. You can get in, find what you need, and—if you fancy a reward—share it with someone else and both walk away a bit better off.
It’s software doing its job without trying to reinvent the wheel mid-rollout. No grand mission statements, no overwrought vision pieces—just a better version of what was already there, shaped by the people who use it and refined by the people who build it. There’s something refreshing in that.
As things stand, v1.3.7 feels like a product maturing in small, steady ways, the kind that actually count. It doesn’t demand headlines, but it does deserve the nod it’s getting from the people paying attention.
