[Ops post] What went out this week
5 Releases - 27 commits
Hey Foxes! Here’s a roundup of what the team pushed live last week — plus one open release
fix: assets fuzzy search (#9789)
feat: make search assets only (#9786)
feat: regenerate asset data 06/26/2025 (#9795)
fix: refetch next accounts activities and resume on rehydration (#9727)
chore: update app translations (#9782)
fix: action center polish (#9779)
fix: copy state on mobile app (#9780)
feat: regenerate asset data 06/25/2025 (#9781)
fix: net worth wrapping and breaking alignment on mobile loading (#9765)
fix: bridge from ethereum to arbitrum with rfox (#9773)
feat: rfox bridge max dp in “Send FOX” (#9771)
fix: thorchain utxo Tx use fast sats/B (#9769)
feat: regenerate asset data 06/24/2025 9768
fix: thor streaming progress 9759
feat: new desktop seed phrase challenge 9758
fix: remove duplicate key in english language file 9757
feat: regenerate asset data 06/23/2025 9755
feat: refactor mobile seed phrase challenge 9756
fix: price impact bits 9751
feat: add base to phantom wallet 9754
feat: human readable action center copies 9738
feat: regenerate asset data 06/21/2025 (#9752)
feat: regenerate asset data 06/20/2025 (#9748)
fix: dont feed lodash big numbers (#9746)
Operational Notes from a product guy:
Work continues behind feature flags and in other repos with focuses on Mayachain support, the notification center, and agentic work. The action/notification center goes out Monday/today! We had some sanity checks thanks to operations and keen eyes from apo, found an empty state that means it needed some love, and are generally happy wiring up the last pieces all through next week. The app is more welcoming now and easier to use. The modernization continues.
[Product] General product check in. Strategy, notes, testing and hype.
Maya has it’s affiliate, I think we’re good for Monday launch. Notification center too, pending we’re happy with placeholder text or a welcome notification. ( i prefer the latter but that’s what grooming is for.)
We kicked off mobile without doing a proper side by side breakdown. This cause a bit of a momentum shift and problems. Apologies there, we are learning about how to best use linear and change up some process. Goals are efficiency, documentation/comms, and focusing on productivity, if we can nail the balance we should be really cooking with gas.
Next cycle should have some healthy spiking on the agent, as we’re on our third framework and have done a ton of groundwork exploring the quagmires on LLM tooling. Once we find an architecture that outputs deterministic data and has an optimistic path, we should get much faster on iteration here.
To wit, marketing and product are going to just go talk to users anyway. Cultivating hype, and validating that we’re being useful. FBL got out of the office this week to talk with builders, needless to say, we’re going towards utility first. We have validated utility internally, but we’re needing more refinement extrenally. if you’d like to see how we’re targeting specific people to talk to about specific things, please check out the agentic wiki. It’s so many documents now that I’ve pushed it front and center onto the product workstream for us to refer back to and update often.
The DAO’s inflection touchpoint is coming along too, we hit 4 years in a couple week 
. From values we get pillars, from pillars we get goals, from goals we get momentum and we all agree (or revise our commitment level) reaching a level of execution that we’re capable of.
Process & Research & Team
Look, things getting buttery.
Product has updated both the linear issue template and mocked out a process overlook. We need a retro, making sure that we are targeting velocity and not bottlenecking everyone. Apo and I asked ourselves who is responsible for filling the cycle? right now it’s both of us, instead of delineating more. We’re giving that process another view, so each one feels like it build on momentum. Thinking it looks like weekly review of code quality of life, having tickets for “needs discussion” which fit into grooming or another touchpoint, and a check on outstanding product work that is medium or above priority.
Spec updates:
- Spec Ratio is at: 2.83
Spec Backlog
Cycle breakdown is now estimated, accurately reflecting our process and workload.
We’ll get better at pre-grooming. still a work in progress.
Other feature process:
- add a feature you’d like to see at shapeshift.canny.io and bring your friends for upvotes
- Response KPI :
couple of leaking support issues onto canny.
- Response KPI :
- **specs board**
G to the M