Walletbeat sync 2026-02-26

Attendees

  • polymutex
  • hester (EF)
  • 53bo
  • 0xmattmatt
  • Seb (Cyfrin)
  • Davide | Seiryu
  • Johngrantuk

Work we said we’d do last meeting (2026-02-05)

  • polymutex

    • Demo wallet data collection CLI, write guide about it
    • Rate 2 wallets’s data collection using it
      • 25% done…
    • Close out 1TS security benchmark discussion
      • More activity came in as a result of sending the “last call” announcement :)
    • Add 1TS security benchmark as additional ladder (not displayed on site, just to represent it in code)
      • Blocked on above
    • Submit EthCC talk proposal (deadline: February 20th)
    • Respond to Coinspect (#215)
    • PR reviews

  • 0xMattmatt

    • Finalize January Monthly Ecosystem Update (#495)
    • Transaction legibility update
      • Add transaction outcome as a factor
      • Add decoded calldata as a factor
      • Added safe transactions for rate passing
    • Write Walletbeat testing contract
      • To deploy
    • Finish wallet test page
      • App Isolation
      • Tx Simulations
      • Scam Alerts
      • Incorporate that into the Transaction Legibility (& simulation) attribute
    • Documentation guide for better contributing
    • Demo w/ Polymutex data gathering tool
    • Backfill using data gathering tool (Just two or three wallets for familiarity)
    • Windows Development Environment (done by polymutex)

  • ren2140

    • Set up development environment
    • Reach out to TBA to fill out questionnaire
    • Submit pull requests for TBA and Gridplus questionnaire responses
    • Create group chats with wallet teams
      • Created GridPlus Telegram chat

  • lucilajuliana & Pablo

    • Content calendar for February and March
      • Done February
      • Tomorrow for March
    • Set up PR review workflow for social media threads (High priority)
      • Using GitHub Discussions instead
    • Execute on social media strategy
    • Talk proposals for EthCC & others
    • Content creation calendar for Walletbeat Road Show across main crypto events
      • Shared list of events we should attend

  • davide

    • Sent research in to the EF, nethermind, etc
    • Next week: publish!
      • Parts: priority fee for normal transfers (used: Rabby, MetaMask, Phantom). Baseline: blocknative priority fee.
      • Next: More on orderflow for swaps.

Work that was done despite not being planned

  • darrylyeo
    • Typesystem cleanups
  • 0xMattmatt
    • Add wallet rating data for Rainbow and MetaMask
    • Fix “Maintenance” column showing up for software wallets
    • Fix table order as noticed by Ambire.
  • polymutex
    • Fix dev environment for Windows contributors
    • Convince the EF to send the next grant funding milestone
  • johngrantuk
    • Added Railgun to private transfers attribute
  • External contributions
    • Ambire: Data updates for transaction legibility

Initiatives & Updates

ETHCC attendance

1TS slot for 55 minutes (not guaranteed) to discuss security benchmark and user safety properties.

  • [polymutex] Should probably buy tickets.
  • [luci] Want to go too, also there is Paris Blockchain Week right afterwards

Account recovery attribute

[s3b0 to discuss] Thread: https://farcaster.xyz/53bo/0x6e1d2f1a

Outreach

Branding / marketing

Current idea: breaking down the rating system as a flower 🌸

https://www.figma.com/design/fRFH2XbtyWwaBw1BRP96eh/Walletbeat?node-id=0-1&p=f&t=H8NN00lbIRIEJDhZ-0

Social media

Content calendar updates https://github.com/walletbeat/walletbeat/discussions/520

Mattmatt threads https://docs.fileverse.io/0xbf80c3d83c7f1ed9938e677fae318bc5d950a2a3/2#key=czFgsivW9FDRiHHNvThVM_wjim9japJ3EGVyanY4GRm0ohOb4bM_PyitJStmxq6p

Coinspect

Movement on https://github.com/walletbeat/walletbeat/issues/215

[polymutex to discuss]

Wallet security news

[polymutex to discuss]

Next few weeks

  • polymutex
    • Close out 1TS security benchmark discussion
    • Finish up wallet data collection CLI
    • Add verifiability dimension to Evaluations (#503)
  • 0xMattmatt
    • Deploy test contract, waiting for social media assets
    • Finish wallet testing webpage: Scam alerting, transaction simulation tab
    • Contribution guide
    • New attribute: Private key handling
    • Intake questionnaire
  • ren2140
    • Submit pull requests for TBA and Gridplus questionnaire responses
    • Continue to reach out to more teams for questionnaire responses and group chat invites
  • lucilajuliana & Pablo
    • To do: report KPIs in first week of March
    • Set up PR review workflow for social media threads (High priority)
    • Review with poly the walletbeat conference plans for 2026
    • Deliver and execute the Social Media Calendar for March
    • Apply to give a talk at the Crecimiento Pop Up city (Replicate Poly´s talk but in spanish to reach a new audience)
    • Coordinate X space with 2 projects that reached out to do it.
  • john
    • Finish markdown PR
    • Pick up issues as needed/able

AI-generated summary

Attendees

  • polymutex (meeting host, leading technical discussions)
  • Hester (EF) (discussed ERC7730 and WalletCon)
  • 53bo (discussed account recovery attribute)
  • 0xmattmatt (discussed transaction legibility, testing suite)
  • Seb (Cyfrin)
  • Davide | Seiryu (presented research on priority fees)
  • Johngrantuk (Railgun integration and Markdown PR)
  • Lucilajuliana (handled social media content)

Main Segments of the Call

1. Check-in on Previous Action Items

  • Topic: Review of tasks from the last sync.
  • Purpose: Track progress and identify blockers for upcoming work.
  • Problem: Several items were incomplete due to unforeseen complexities (e.g., security benchmark discussion generated more input, CLI development took longer than anticipated).
  • Solutions Proposed:
    • Polymutex prioritized closing the security benchmark discussion next week despite delays.
    • Mattmatt confirmed transaction legibility updates were complete but blocked on social media assets (logo) for deploying the testing contract.
  • Unresolved Questions:
    • Security benchmark discussion remained open due to ongoing community input (e.g., ERC7730 debate).
    • CLI development was “close to complete” but not yet “super usable” for bulk editing.
  • Follow-up Actions:
    • Polymutex to finalize security benchmark discussion.
    • Mattmatt to deploy testing contract once logo assets are ready.
    • Polymutex to add “verifiability” as a separate dimension to the rating system (Issue #503).

2. WalletCon and EthCC Attendance Planning

  • Topic: Attendance at Ethereum-related events (EthCC and WalletCon).
  • Purpose: Coordinate travel plans and leverage events for community engagement.
  • Problem: Uncertainty about EthCC’s 1TS workshop slot (55 minutes, not guaranteed) and timing conflicts with WalletCon (scheduled for March 31).
  • Solutions Proposed:
    • Polymutex agreed to “default yes” for EthCC attendance and to buy tickets promptly.
    • Lucilajuliana proposed replicating Polymutex’s talk in Spanish at Buenos Aires’ Crecimiento Pop Up City to reach new audiences.
  • Unresolved Questions:
    • Whether to attend WalletCon was deferred due to unclear slot availability.
    • EthCC attendance: no final confirmation of workshop slot.
  • Follow-up Actions:
    • Polymutex to purchase EthCC tickets immediately.
    • Lucilajuliana to coordinate with organizers for the Spanish-language talk in Buenos Aires.
    • Shared event list for 2026 (e.g., Berlin Blockchain Week) to prioritize attendance.

3. Transaction Legibility and Testing Suite Updates

  • Topic: Refinements to transaction legibility criteria and testing contract deployment.
  • Purpose: Improve wallet evaluation methodology for transaction transparency.
  • Problem: Wallets often failed to display transaction outcomes (e.g., token transfers, Safe transactions) or decode call data fully.
  • Solutions Proposed:
    • Added “transaction outcome” as a factor (e.g., wallets must preview Safe transaction execution, not just signer confirmation).
    • Explicitly required decoding of Safe’s inner calldata (not just top-level calls).
    • Expanded criteria to include ERC-1155.
  • Unresolved Questions:
    • Whether to audit the testing contract (current version is un-audited and strictly for testing).
    • How to handle “trusted protocols” beyond Aave/USDC (e.g., DEX swaps, complex smart contracts).
  • Follow-up Actions:
    • Mattmatt to deploy the testing contract once logo assets are ready.
    • Expand testing to cover more protocols (e.g., DEXs, NFT marketplaces) and include scam alert testing.
    • Add screenshots to PRs as proof of wallet behavior (Issue #503).

4. ERC7730 Standard Discussion

  • Topic: Inclusion of ERC-7730 (“Clear Signing”) in wallet safety framework.
  • Purpose: Determine if the standard should be formally integrated into Walletbeat’s criteria.
  • Problem: Current criteria require “structured display of call data” but don’t specify standards like ERC-7730.
  • Solutions Proposed:
    • Polymutex emphasized focusing on user benefits (e.g., avoiding hex-only call data, copy-paste functionality) rather than mandating specific standards.
    • Hester suggested ERC-7730 could solve call data presentation issues, but adoption is nascent.
  • Unresolved Questions:
    • Whether to wait for broader ERC-7730 adoption before incorporating it.
    • How to handle competing standards if they emerge.
  • Follow-up Actions:
    • Delay formal inclusion of ERC-7730 until more community guidance is available.
    • Continue evaluating solutions based on user outcomes (e.g., “Is call data human-readable?” vs. “Is ERC-7730 implemented?”).

5. Outreach to Wallet Teams and Communication Policies

  • Topic: Engaging wallet developers (TBA, GridPlus) and establishing communication channels.
  • Purpose: Streamline data collection and collaboration with wallet teams.
  • Problem:
    • GridPlus and TBA questionnaires were completed, but communication was siloed (e.g., separate Telegram chats).
    • Risk of “closed channels” conflicting with Walletbeat’s open-source ethos.
  • Solutions Proposed:
    • Ren proposed creating a standardized questionnaire template for new wallet onboarding.
    • Polymutex suggested formalizing policies for communication channels (e.g., all discussions archived in GitHub for auditability).
  • Unresolved Questions:
    • How to balance private collaboration with public transparency.
    • Whether to use GitHub Discussions, Fileverse, or other tools for PR reviews.
  • Follow-up Actions:
    • Ren to submit PRs for GridPlus and TBA questionnaire responses.
    • Create a policy for communication: all approved content must be archived in the repository (not just in external tools).
    • Use GitHub templates for PR reviews instead of Fileverse (as it’s still alpha).

6. Branding and Visual Design Updates

  • Topic: Redesigning the wallet rating visualization.
  • Purpose: Simplify the complex rating system into an intuitive visual format.
  • Problem: Current pie charts were too fragmented and hard to interpret at a glance.
  • Solutions Proposed:
    • “Flower theme” concept: five attribute categories as petals, individual attributes as seeds.
    • 3D renders for social media previews and a redesigned website layout.
  • Unresolved Questions:
    • Finalizing the logo (still in progress).
  • Follow-up Actions:
    • Figma design iterations (linked in meeting notes).
    • Use the flower diagram as a social media preview image.

7. Coinspect Data Collaboration

  • Topic: Integration of Coinspect’s wallet security data.
  • Purpose: Leverage existing security research without creating conflicts of interest.
  • Problem:
    • Initial proposal to share raw numerical scores conflicted with Walletbeat’s need for objective, independent evaluation.
  • Solutions Proposed:
    • Polymutex clarified Walletbeat would only use raw checklist data (yes/no answers for features), not Coinspect’s weighted scoring methodology.
    • Used analogy to explain why delegating methodology is problematic.
  • Unresolved Questions:
    • Coinspect has not yet responded to the latest message.
  • Follow-up Actions:
    • Wait for Coinspect’s response and ensure data sharing focuses on raw checklists (not scoring).
    • Link to Coinspect’s work in attributes section.

8. Social Media Strategy and KPIs

  • Topic: February/March content calendar and social media performance.
  • Purpose: Measure engagement and plan future outreach.
  • Problem: Current PR review workflow for social media threads was inefficient.
  • Solutions Proposed:
    • Lucilajuliana executed February calendar (high-quality follower growth).
    • Proposed using GitHub templates instead of Fileverse for PR workflows.
  • Follow-up Actions:
    • Deliver March content calendar by early March.
    • Report KPIs for February in the first week of March.
    • Replicate Polymutex’s talk in Spanish for Buenos Aires event.

9. Priority Fee Research (Davide)

  • Topic: Wallet behavior analysis for priority fees and transfers.
  • Purpose: Provide data-driven insights for wallet optimization.
  • Problem: Lack of standardized analysis on how wallets handle priority fees.
  • Solutions Proposed:
    • Davide tested Rabby, MetaMask, and Phantom using BlockNative’s priority fee baseline.
    • Focus on “pure transfers” (excluding MEV noise) for initial phase.
  • Unresolved Questions:
    • How to extend research to swaps/order flow (Phase 2).
  • Follow-up Actions:
    • Publish research early next week (shared privately for feedback first).

10. Account Recovery Attributes

  • Topic: Redefining wallet security criteria for account recovery.
  • Purpose: Align with Ethereum’s self-sovereignty principles.
  • Problem: Current language was too specific (e.g., “seed phrase”) and excluded modern solutions (e.g., Passkeys).
  • Solutions Proposed:
    • 53bo proposed “passing” for wallets supporting social recovery or threshold signatures.
    • Polymutex emphasized user outcomes (e.g., portability, recoverability) over specific tech (e.g., “seed phrase”).
    • Avoiding naming specific providers (e.g., Google/Apple) to prevent vendor lock-in.
  • Follow-up Actions:
    • 53bo to create a GitHub issue summarizing revised language.
    • Focus on “number of dependencies” for recoverability (e.g., no single point of failure).

High-Level Summary of the Call

This meeting focused on progress tracking, technical refinements to Walletbeat’s evaluation methodology, and strategic planning for community engagement. Key outcomes included:

  • Technical Progress:

    • The Wallet Data Collection CLI is near completion but requires further refinement for bulk editing.
    • Transaction legibility criteria were expanded to include Safe transaction inner calldata decoding and broader token standards (ERC-721/1155).
    • A testing contract is ready for deployment pending logo assets, with plans to add scam alerts and transaction simulation features.

  • Community Engagement:

    • EthCC attendance is prioritized (tickets to be purchased), with Lucilajuliana planning a Spanish-language talk in Buenos Aires.
    • Outreach to TBA and GridPlus yielded questionnaire responses, but communication policies must be formalized to avoid siloed channels.
    • New contributor Johngrantuk successfully integrated Railgun support and is working on Markdown PRs for structured data.

  • Methodology Clarifications:

    • Walletbeat will not adopt Coinspect’s scoring methodology but may incorporate raw checklist data.
    • Account recovery criteria were revised to focus on user outcomes (e.g., portability) rather than specific tech like “seed phrases”.
    • ERC-7730 was deferred for future consideration pending broader adoption.

  • Branding and Operations:

    • A “flower” visual design (petals for categories, seeds for attributes) is in progress for the rating system.
    • Social media KPIs for February showed strong growth, with March calendar preparation underway.
    • Davide’s priority fee research (focusing on pure transfers) will be published next week.

The meeting concluded with clear action items for all attendees, emphasizing the need to close the security benchmark discussion, finalize data collection tools, and balance open collaboration with transparency. No major unresolved conflicts remained, though Coinspect’s response and ERC-7730 adoption require ongoing monitoring.