Also added internal analytics instrumentation across the app.
PostHog screen tracking now gives us visibility into:
• navigation flows
• feature usage
• drop-off points
Helps us decide what to build next.
Battle of Tokens XIV
Another battle, as always I will dig and make a long post, article or AMA with the winner!
1. @microstaking $MICRO
2. @liminalcash $LIL
3. @ThatAmberVibe $AMBERVIBE
4. @aleistera $ALEISTER
Reminder that 50 real votes even on second place I will check out.
Had a Great conversation with @0xJackMarsh from @liminalcash, it’s amazing to share the mindset with Neobank founders in the Space.
Have a Great time in Brazil and Keep building for the real Brazilian users 🙏🇧🇷
This week we shipped and improved:
✓ Linked bank account visibility
✓ Recipient transaction transparency
✓ Identity verification reliability
✓ App animations and readability
Thanks to everyone testing and sending feedback.
Keep breaking things for us 😅
GM ! This week in infrastructure:
RBE build fixes, Kafka bump, CD preflight phases, RBAC deployment fixes, gVisor node pools, CI cache corruption resolved.
None of this ships to users.
All of it matters.
We built internal Claude skills for our own eng team.
/release, /ticket, /pr, /audit, /investigate, all running in-house.
The same AI we're shipping to users is part of how we build. Devs built tools to let anyone code; core banking engineers build tools to let anyone do finance.
GM ! An AI agent that can initiate payments needs hard constraints.
We built ambiguity resolution, volatile data guardrails, and sandboxed execution before we built the UI.
Security architecture first. Features second.
What's actually inside Nim right now:
gVisor sandboxed execution.
JWT enforcement.
Brave Search integration.
Redis → Postgres confirmation queue migration.
Mem^0g memory extraction.
Not released to the general public yet.
Almost ready.