Walletbeat contributors sync 2026-04-30

Attendees

  • polymutex
  • Ren
  • John
  • Lucila
  • Ranko X
  • 0xMattmatt

Work we said we’d do last meeting (2026-04-09)

  • polymutex

    • Data collection CLI [halfway there]
    • Apply to Brew [blocked on above as it will demo it]
    • Book tickets to whichever conference

  • 0xMattmatt

    • Finish security best practices attribute
    • Demo video to post & meeting w/Ren & Lucila
    • Blog posts for Walletbeat explaining attributes
      • Wallets status quo
      • Walletbeat’s goal (mission)
    • VISA approved

  • johngrantuk

    • Implement Release Process Transparency attribute after methodology discussions [in progress]

  • ren2140

    • Finalize Giveth app by April 15ᵗʰ
    • Continue to fill out data for base, uniswap, rainbow based on publicly available info
    • Demoing wallet research with 0xMattmatt & lucilajuliana

  • lucilajuliana

    • April content calendar
    • PRs for: logo SVG update, sidebar background color, new fonts, new favicon (hot fixes to the website so it looks as best as possible during the Giveth round)
    • Session with Darryl to get familiar with the codebase, classes and architecture of the walletbeat website
    • Session with 0xMattmatt about data entry
    • Two sessions per week with the branding team to finish the rebranded website before Berlin Blockchain Week

  • darrylyeo

    • Systematization of CSS rules (fonts/colors)
      • Meet with Lucila
    • Website bundle size fix (no inline SVGs on homepage)
    • Flower-y rating system component
      • Keep iterating on shapes + rendering methods
      • Match Figma design

Work that was done despite not being planned

  • 0xMattmatt

    • Going on X space and shilling Walletbeat for Giveth (got lots of donations from this!)
    • Walletbeat UI Navigation Bar
    • Windows environment setup
    • Added token transfers to transaction simulation tests
    • Brew Berlin draft
    • Security best practices attribute announcement

  • polymutex

    • Optimized SVGs
    • SVG-to-icon-font tooling

  • ren2140

  • darrylyeo

    • CSS codegen tooling

  • External contributions

  • Luci

    • Daily posts about the QF round on the X and Farcaster accounts
    • Daily RT to every walletbeat mention in X and Farcaster
    • With Matt, poly and Darryl, we participated in TheDAOfund’s X space where projects showcased what they are working on.
    • Wrote a telegram/signal group asking for support in the round and sent that to every relevant group.
    • Walletbeat’s Giveth profile was created linked to ren’s social wallet. That can’t happen again in the future. Walletbeat needs to have a social wallet for these use cases.

Initiatives & Updates

Conference attendance

  • At Berlin Blockchain Week: 0xMattmatt, polymutex, Tere. Others?
  • Is there any chance to get financial support for the plane tickets?

Giveth round ongoing

https://qf.giveth.io/project/walletbeat?roundId=16

QF multiplier looks pretty nice.

Redesign ongoing

Looking good: https://beta.walletbeat.eth.limo

Browser extensions requesting access on all pages

https://github.com/walletbeat/walletbeat/discussions/655

Coinspect data is open-sourced

https://github.com/coinspect/wallet-security-ranking

Wallet data leakage on startup by Ranko X

Walletbeat communications policy

Merged! Please remember to add all qualifying communication channels to the list.

Shefi curriculum to include Walletbeat

Update from Hester:

“Good news on Shefi through. Maggie has confirmed being open to include WalletBeat in the curriculum. Could you please discuss with the group:

I’d recommend coming up with two proposals for Shefi to evaluate what fits best in existing classes.“

Next few weeks

  • polymutex
    • Apply to Brew
    • … Data collection CLI
      • Demo to Ranko X
    • Create social wallet EOA
    • Hook up Hester/Maggie/Luci
  • 0xMattmatt
    • Synthesize 1TS security workshop results and encode in stage system
    • Speaker applications
      • Neocypherpunk
      • Web3 Summit
    • X stream
    • UI Redesign
  • johngrantuk
    • Release Process Transparency attribute
  • ren2140
    • continue to help with wallet research
  • lucilajuliana
    • Daily posts in X and Farcaster where the Call to Action is: Donate to walletbeat during the QF Round.
    • Keep working with matt and darryl on the UI redesign, making sure the site looks exactly as the figma design.
    • Finish and launch the rebranded site before Berlin Blockchain Week
    • Represent walletbeat in the next Giveth´s X space. Our goal is to ask for individual donations in the round and show that WB is backed by an strong team of contributors and it is not just poly!
    • We are crafting an elevator pitch to be useful in every situation: BD, networking, Spaces, interviews
  • darrylyeo
    • [add]

Walletbeat Contributors Sync Meeting Notes (AI-generated)

Date: 2026-04-30
Document Type: Official Meeting Record

Attendees

  • polymutex
  • 0xMattmatt
  • johngrantuk
  • ren2140
  • lucilajuliana
  • Ranko X
  • Absent but referenced: darrylyeo, Tere

Main Segments & Discussion Breakdown

1. New Contributor Onboarding & Data Collection CLI Alignment

  • Topic: Introduction of Ranko X and technical integration of his network traffic analysis methodology with Walletbeat’s data collection pipeline.
  • Purpose: Align Ranko’s independent wallet traffic benchmarking work with Walletbeat’s open-source research framework and establish a clear contribution path.
  • Problem & Solutions: Ranko has been capturing raw network traffic (pcap) for Android wallets (via Packet Capture Droid) and 31 Chrome extensions. Polymutex noted that Walletbeat’s repository does not use raw pcap files, preferring a structured JSON format containing request/response payloads and metadata. Solution: Polymutex offered to help build a conversion pipeline. Ranko can submit raw pcap files as PRs for now, while Polymutex completes the CLI’s automated capture and tagging features. The CLI is ~50% complete; it currently scans for recurring substrings across requests, calculates entropy scores to distinguish tracking identifiers (e.g., cookies) from static data, but lacks a final review/tagging interface.
  • Debate/Unresolved: Whether to prioritize manual proxy/Wireshark captures or wait for the CLI’s automated entropy-scoring feature to mature. No strong debate; agreed to parallel progress.
  • Actions:
    • polymutex to schedule a 1:1 walkthrough of existing tooling with Ranko.
    • Ranko X to continue Chrome extension analysis and submit findings via PR.
    • CLI development to continue, targeting the missing review/tagging module.

2. Review of Previously Assigned Deliverables

  • Topic: Status update on tasks committed to in the previous sync cycle.
  • Purpose: Track progress, identify blockers, and ensure alignment across research, frontend, and documentation workstreams.
  • Problem & Solutions:
    • 0xMattmatt: Completed the Security Best Practices attribute (covers key storage, secure RNG, platform hardening, manifest/permission analysis for browser/mobile/desktop). Demo video and two blog posts (status quo, mission) published. Visa for Berlin approved.
    • johngrantuk: Working on Release Process Transparency. Faced methodology complexity in defining subcriteria and pass/partial thresholds. PR is open; awaiting review feedback. Solution: Continue async methodology refinement on GitHub; finalize scoring thresholds next week.
    • ren2140: Giveth application finalized. Completed data entry for Rainbow & Base after obtaining questionnaire responses. Established a direct group chat with the Base team for ongoing research collaboration.
    • lucilajuliana: Completed April content calendar, deployed hotfixes for the Giveth round, and held architecture/design system syncs with Darryl & Matt. Working with the branding team to finalize the rebrand pre-Berlin.
    • darrylyeo (absent): Systematized CSS rules. Homepage bundle size remains high (~36MB, down from 50MB). Flower-shaped rating component needs Firefox compatibility fixes and Figma alignment.
  • Debate/Unresolved: Darryl’s bundle size optimization and rating component UI still require iterative polish. John’s attribute methodology needs final threshold agreement.
  • Actions:
    • johngrantuk to finalize Release Process Transparency PR.
    • darrylyeo to continue bundle size reduction and rating component fixes.
    • polymutex to potentially draft the Order Flow Transparency attribute next.

3. Unplanned Accomplishments & External Contributions

  • Topic: Recognition of ad-hoc work completed outside the initial roadmap, including external bounty submissions.
  • Purpose: Document value-added contributions and external ecosystem impact.
  • Problem & Solutions:
    • 0xMattmatt completed UI navigation bar merge, Windows environment fixes, added token transfer scenarios to transaction simulation tests, drafted the Brew Berlin speaker proposal, and announced the security attribute on X.
    • polymutex implemented SVG optimization and an automated SVG-to-icon-font pipeline to reduce frontend bundle size.
    • darrylyeo built CSS codegen tooling.
    • External Bounty: A contributor successfully demonstrated wallet vulnerability to a lying L1 RPC proxy (which tricks wallets into displaying inflated USDC balances). They created a demo video and upstreamed a PR to the Enkrypt wallet integrating the Helios light client for on-chain balance verification. Issue: The wallet team has not yet responded to the PR. Solution: Document the contribution publicly; note that lack of response is on the wallet maintainer, not the contributor.
  • Debate/Unresolved: None. Consensus to publicly highlight the bounty work.
  • Actions:
    • Publicly credit the L1 RPC proxy contributor.
    • Continue expanding transaction simulation test coverage.

4. Quadratic Funding (Giveth) Round & Treasury Strategy

  • Topic: Ongoing Giveth QF round performance, matching multiplier strategy, and donation compliance.
  • Purpose: Coordinate donation campaigns, ensure anti-sybil compliance, and plan matching fund maximization.
  • Problem & Solutions: QF round currently has ~$300 donated. Giveth’s anti-sybil mechanisms flag funds that recirculate (e.g., treasury → donation address → treasury). Polymutex explicitly advised against trying to game the metrics.
  • Debate/Unresolved: Treasury levels are low, creating tension between funding operations, conference travel, and QF donations.
  • Actions:
    • lucilajuliana to maintain daily social posts with QF donation CTAs.

5. Berlin Blockchain Week & Conference Logistics

  • Topic: Attendee planning, speaker applications, and travel funding for Berlin Blockchain Week (June 10–22), specifically Neo Cypherpunk (June 14) and Brew Privacy Conference (June 20).
  • Purpose: Coordinate a unified project presence, explore travel stipends, and align speaker submissions.
  • Problem & Solutions: Matt, Polymutex, and Tere are confirmed. Lucila (Argentina) and John (UK) are interested but face travel cost constraints. Conference organizers rarely cover long-haul flights. Solution: Apply as a unified Walletbeat team rather than individuals to increase chances of speaker stipends. Submit speaker applications via GitHub markdown for synchronization.
  • Debate/Unresolved: Uncertainty around organizer funding for non-local attendees. Team agreed to pursue unified applications and parallel grant research.
  • Actions:
    • polymutex to research travel/stipend opportunities.
    • Team to submit unified speaker applications for Brew & Neo Cypherpunk.
    • johngrantuk to verify date compatibility.

6. Technical & Research Updates

  • Topic: Browser extension permissions methodology, Coinspect dataset integration, and follow-up on wallet startup traffic leakage.
  • Purpose: Incorporate new open data, refine privacy scoring methodology, and validate research reproducibility.
  • Problem & Solutions:
    • EIP-6963 Permissions: GitHub discussion raised whether default accessOnAllUrls permissions should hurt privacy scores. Matt explained that EIP-6963 (wallet discovery) naturally requires broad page access to scan for provider scripts. Solution: Matt is prototyping a wallet that maintains privacy-by-default permissions while correctly implementing EIP-6963 to determine if the permission is strictly necessary or abused.
    • Coinspect Data Open-Sourcing: Coinspect released their wallet security ranking dataset under a permissive license. Covers ~15–20% of Walletbeat’s criteria (mainly security UI/features). Solution: Import pipeline to bypass redundant manual testing for security attributes. Researchers will check Coinspect’s data first before testing those specific attributes.
    • Ranko’s Traffic Analysis: Wallet developers (e.g., Edge co-founder) found the initial startup leakage data informative but disorganized. Solution: Ranko will release Part 2 focusing on Chrome extensions, explicitly aligning with Walletbeat’s scoring workflows to improve rating accuracy.
  • Debate/Unresolved: How to fairly score extensions that require broad permissions solely for EIP-6963 compliance without penalizing standard behavior.
  • Actions:
    • 0xMattmatt to prototype EIP-6963 + privacy-by-default setup and update the GitHub discussion.
    • polymutex to create a GitHub issue for the Coinspect data import pipeline.
    • Ranko X to align Part 2 research methodology with Walletbeat’s attribute workflows.

7. Communications, Partnerships & Team Development

  • Topic: SheFi curriculum integration, dedicated project wallet setup, and internal public speaking training.
  • Purpose: Expand educational outreach, streamline partnership logistics, and improve team’s external representation.
  • Problem & Solutions:
    • SheFi Partnership: SheFi (women in crypto) wants to include Walletbeat in their onboarding curriculum. Hester (EF) requested content proposals and a point of contact. Solution: Draft two tiered proposals (high-level onboarding vs. technical deep dive). Polymutex will directly connect Lucila with SheFi’s Maggie to reduce communication hops.
    • Project Wallet: Giveth profile was linked to Ren’s personal social wallet. Solution: Polymutex will generate a dedicated Walletbeat EOA/social wallet for future campaigns, holding minimal funds strictly for signing/login.
    • Public Speaking: Lucila proposed an internal, optional workshop to help contributors confidently pitch Walletbeat’s mission in elevators, Spaces, and interviews. Solution: Lucila to organize; Polymutex offered to participate.
  • Debate/Unresolved: Curriculum content scoping and wallet custody logistics. Agreed to keep the project wallet minimal and strictly operational.
  • Actions:
    • polymutex to introduce Lucila ↔ Hester/Maggie directly.
    • Team to draft two SheFi content proposals.
    • polymutex to deploy dedicated Walletbeat EOA.
    • lucilajuliana to organize optional public speaking training.

High-Level Summary

This sync meeting served as a comprehensive progress review, technical alignment session, and strategic planning checkpoint for Walletbeat. The team successfully onboarded Ranko X, whose independent network traffic analysis work may be integrated into Walletbeat’s research pipeline alongside the in-development data collection CLI. Significant technical progress was reported: the Security Best Practices and Release Process Transparency attributes are nearing completion, the frontend bundle size is being optimized via SVG-to-icon-font automation and CSS codegen, and external bounty work successfully demonstrated L1 RPC proxy manipulation vulnerabilities with a proposed Helios light client fix.

Operationally, the project is actively engaged in a Giveth Quadratic Funding round, with strong matching multipliers. The team is coordinating a unified presence at Berlin Blockchain Week, focusing on the Brew Privacy Conference and Neo Cypherpunk, while exploring speaker stipends and travel funding. Ecosystem partnerships advanced notably with SheFi’s inclusion of Walletbeat in their educational curriculum and the strategic import of Coinspect’s newly open-sourced security dataset, which will streamline ~15–20% of manual wallet testing.

Moving forward, the team will finalize pending attributes, launch the rebranded website pre-Berlin, execute unified conference applications, and strengthen external communication through targeted social campaigns, curriculum proposals, and optional internal public speaking training. The meeting reinforced Walletbeat’s commitment to methodological rigor, open data sharing, and legitimate, community-driven funding.