Skip to main content
View all authors

Logbook 06/03

· 2 min read

This week we shipped the Vote Tab — a brand new section in Resonance where you can support or oppose curated claims and lists. We also made it easier for new users to get started with a guided first claim experience, and improved stability and performance across the app.

Logbook 27/02

· 3 min read

Big week on Sofia — we unified the transaction confirmation screen across the entire app, launched the Beta Season Pool (a shared vault funded by every certification), overhauled bookmarks with search and sorting, and shipped a major performance boost cutting the app's initial load by 535 KB. Page-level blockchain stats also got a full rewrite for better accuracy.

Logbook 20/02

· 3 min read

Massive week for Sofia — we shipped a full on-chain streak system with shared vault deposits, built a leaderboard with ENS resolution, introduced vote quests with Gold rewards, and completed a major refactoring that significantly cleaned up the codebase. The trending tab got a complete overhaul, and the onboarding tutorial now covers 12 steps.

Logbook 13/02

· 3 min read

Big week for Sofia — we cleaned up the entire codebase for better maintainability, introduced the ability to trust or distrust content, split the reward system into two currencies (Gold and XP), added a voting system in the Circle Feed, enabled profile sharing on X, and completely redesigned the user profile with badges, animations, and new visuals.

Logbook 06/02

· 2 min read

This week, we refactored the Account page into a tabbed layout with Stats, Quests and Achievements, shipped Bookmark V2 with on-chain certified badges, fixed on-chain certification sync issues, centralized all GraphQL queries into @0xsofia/graphql, built a Sofia Fee Proxy dashboard, and cleaned up legacy code (Ollama, WebSocket, YouTube/Google restrictions).

Logbook 30/01

· 3 min read

This week, we shipped full multi-wallet support — Sofia now discovers wallet providers via EIP-6963 (MIPD) and bridges multiple wallets (Rabby, MetaMask, etc.) and isolates all user data (tokens, bookmarks, quests, XP) per wallet address. We also securing postMessage origins, enforcing HTTPS for transactions, and adding crypto-based OAuth state. On the UX side, a complete onboarding flow with tutorial slides and bookmark selection is now live, alongside a new URL normalization layer that strips tracking params and uses page titles as atom names. Finally, we cleaned up the EchoesTab by excluding follow triples from group cards, fixed group levels from on-chain data, and removed legacy dead code.

Logbook 16/01

· 4 min read

During this development cycle, we focused on strengthening Sofia's core mechanics and finalizing several key systems. The main effort went into improving discovery logic, intention classification, and social linking, while stabilizing authentication and agent infrastructure.

This period was less about visible features and more about ensuring reliability, coherence, and long-term scalability across the product.

Logbook 19/12

· 2 min read

This week was dedicated to core infrastructure migration, authentication hardening, and on-chain verification foundations. We completed the migration of the extension authentication system to Privy, removing internal session wallets in favor of a secure external HTTPS flow. In parallel, the stack was fully migrated from ElizaOS to Mastra, improving modularity, performance, and agent orchestration while simplifying networking through an HTTP-based architecture. OAuth flows were secured via an external landing page backed by Cloudflare Workers, and the first version of our on-chain Proof of Human attestation system was implemented with gas abstraction for users.

Logbook 12/12

· 2 min read

This week focused on core foundational deliveries, including connecting the MCP Server to our agent and deploying the full Privy authentication flow for the Chrome extension. We also finalized the staking modal (with bonding curve options), optimized transactions using Sofia’s fee proxy, extended the Trust / Distrust system, and improved data integrity and UX reliability across triples creation and display.These features are not yet available to the public and will be pushed to production for alpha V2.