Walletbeat contributors sync 2026-10-08

Attendees

  • Michael
  • REN
  • polymutex
  • John
  • Matt
  • [add yourself]

What we said we’d do

  • polymutex

    • Finish Kohaku CLI data collection harness + audit
    • Unblock data collection for other wallets
    • Book flights / visa things

  • John

    • Finish Coinspect
      • WIP first part of last PR: mapping Coinspect tests to WB feature data
    • #884 after Coinspect
      • Not started

  • Ren2140

    • Continue to refine data for top 5 wallets and down (refTodo’s to fill in)
      • 63 ref todos down to 33
    • Help with any milestone related work for EF grant as needed
    • Help with theDAO fund application as needed

  • Michael

  • Lucila

    • Release of the 4 berlin interviews edited, posted in our YouTube channel and shared in our socials
      • Polar done, rest to go
    • Delivery of the October Content Calendar before the end of September.
      • Pushing on next week’s post to GitHub
    • research Zcash grants programs
      • Will post on discussion
    • Dao Fund grant application
    • UI issue tab non 0 stage: 1ˢᵗ priority
    • Got booth reservation at Devcon
    • Booth mockup renders: https://drive.google.com/file/d/1H8Ft5qsfsruZi4dtCxBzZYZWTFxzJJD2/view

  • Darryl

    • UI-related PRs (performance/layout work, reviewing other PRs)

  • Matt

  • Tere

    • Design developed of impact log page (in progress)
    • New icons (in progress)
    • Booth logo design
      • (graphics on screen for Booth depending on the program)
    • Memes
    • Open to pause contribution or allocate upon agreed fixed hours until confirmation of EF funds considering the treasury balance ❣️

Initiatives & Updates

Ethereum Foundation Funding Update

Grant is on, deadline coming up. KYC info submitted for funds recipient.

Progress for Milestone 1 (October 15):

Progress for Milestone 2 (November 30):

  • Formal launch (walletbeat.eth)
  • Donation page
  • Devcon Mumbai talks, workshops
  • Booth programming

Progress for Milestone 3 (January 31 2027)

  • Progress slider live on wallet pages
  • 2,000 followers on X
  • Net new additions to the impact log
    • Ideas how to get more “IMPACT”?
    • Badge system for wallets
      • Have to not be redundant with the progress slider

Octant application

Unfortunately we were rejected.

The DAO application

Update? Lucila & Ren

This application is milestone and impact based we’ll need to determine what we will propose for our grant, the grant must be fully funded before work can start. It will need to be different than what was proposed for the EF grant (to me something related to HW wallets makes sense). If we chose Hardware wallet ratings we’ll need to list:

  1. Build milestones (e.g. fully rate x hardware wallets on security attribute)
  2. Adoption milestones (e.g. at least x vendors ship an upgrade or process change that raises one of their walletbeat security ratings). We need a way to prove this, need to show the fix shipped + we caused it. An example of an adoption milestone could be a wallet implementing clear signing. The adoption milestone must be where at least a third of the funds for the grant proposal will be released

An example of what this could look like

  • Milestone 1 Build: x hardware wallets fully rated on security attributes - $35k
  • Milestone 2 Adoption: x vendors ship a fix to a gap walletbeat found at least x from ledger, trezor, keystone, gridplus - $35k
  • Milestone 3 Adoption: at least x vendors ship on device clear signing at least x is ledger or trezor - $20k

Relevant references:

→ Draft this. Need to define the precise scope of the grant, has to be security-focused and should have a coherent theme beyond generic “security”. Try avoiding conflict w/ Milestone 1’s Clear Signing Relaunch target

Devcon plans

Talks approved:

  • polymutex’s lightning talk on wallet software supply chain security
  • polymutex panel at Cypherpunk Congress
  • ren2140’s how-to-contribute talk given by Michael
  • Walletbeat launch talk (approved, but for lightning session)
  • Michael’s beyond clear signing talk
  • Darryl’s dependency-minimalism talk

Booth plans:

  • How many days? 2
  • Activities? → Luci
  • Ideas?
    • Sharing plan in the group
    • Website demos
    • Go through single wallet
    • Rambles about one specific attribute at a time
    • Wallet data entry workshop live
  • Call to action
    • Follow us on X
    • QR code for that to print
    • Stage icon stickers?
    • Logo sticker

Who goes? (Reminder: policy covers max 2 people per conference)

  • polymutex (no reimbursement needed so not counting in the total)
  • ren2140: Not going
  • Michael: Going
  • lucila: Check prices now
  • Darryl: Going

SheFi curriculum inclusion

Presentation, posting to GH. Will reuse it for social

Kohaku CLI network audit

Harness mostly done, collection not. Focusing on the generic wallet data collection first to meet milestone 1 of EF grant.

Next few weeks

  • polymutex

    • This weekend: finish enough of the data-collection pipeline to have colored rating slices on wallets with completed network captures.
    • If failing to meet this deadline: come up with some hacky way to interpret the data we already have by the 16th.
    • Travel visa.

  • John

    • Finish Coinspect
    • #884 after Coinspect

  • Ren2140

    • Grant application
    • Talk material for data entry (if time allows)

  • Michael

    • Clear signing WG attendance
    • Follow up w/ EF Grant
      • Get the milestone 1 sent
    • VISA
    • Data collection tagging
      • Priority for milestone 1
    • Help w/ Matt & Darryl UI issues

  • Lucila

    • Content for rest of the month (October)
    • Graphics on screen for Booth depending on the program
    • Lower priority: UI issues

  • Darryl

    • Traveling

  • Matt

    • Continue cleaning up issue backlog
    • Keep an eye on new issues / bugs
    • Provide EOA for funds

Main Segments of the Call

1. Welcome & the mobile crash fix

  • Topic: Opening; the website crash on mobile.
  • Purpose: Casual check-in; confirm the crash root-cause and fix.
  • Problem & Solutions: The crash was traced to the pie chart (metadata/random petal rendering), likely memory-related. Michael has been fixing it. Polymutex asked whether the petals would need to be given out — no.
  • Debate/Unresolved Questions: None.
  • Actions: Fix merged/verified; performance issues remain on the milestone list.

2. Review of last week’s action items (“What we said we’d do”)

  • Topic: Status roll-call against the prior meeting’s commitments.
  • Purpose: Accountability; early identification of blockers.
  • Problem & Solutions: Mostly on track. Completions: EIP tracker + clear signing meeting + data collection (Michael); Kohaku harness + collection, flights/hotel (polymutex); Coinspect mapping start (John); ref-TODO reduction (Ren); booth reservation + Zcash research + interviews (Lucila); svelte-check gating, UNRATED stage eval, deploy workflow fix, light-mode (Matt). Delayed: Kohaku audit & classification (polymutex), #884 (John), Trust Wallet/Bitget/Safe data input (Michael), DAO application (Lucila → Ren).
  • Debate/Unresolved Questions: Michael’s data collection is blocked on polymutex’s tagging agent, which still lacks safeguards and can over-tag. Polymutex’s wallet rating breakdown (#1237) not yet approved.
  • Actions: Continue per assignments; unblock the tagging agent; review #1237.

3. Coinspect import pipeline (John)

  • Topic: Mapping Coinspect tests to Walletbeat feature data.
  • Purpose: Understand the best approach to import Coinspect’s data into Walletbeat.
  • Problem & Solutions: Only one direct mapping from Coinspect tests onto Walletbeat feature data. Many Coinspect fields have no direct mapping but could be useful to add — which would also require updating the attribute logic. John asked for feedback on whether his mapping is too strict. Polymutex: don’t be overly strict — e.g., Coinspect’s “auto-lock in 20 minutes” doesn’t matter per se, but “does it auto-lock at all” does; if Coinspect says 20 minutes, that should count.
  • Debate/Unresolved Questions: Whether the theme matching is the right criterion, or whether the evaluation approach also needs to map onto Walletbeat’s evaluation; how strictly to map. John to digest polymutex’s feedback.
  • Actions: John to refine the mapping (less strict on specific values, more on the underlying property); decide whether to add new fields and update attribute logic; then #884.

4. Ref data for top-5 wallets (Ren)

  • Topic: Filling in missing refs for top-5 wallet data.
  • Purpose: Make the top-5 wallets look more detailed and credible.
  • Problem & Solutions: Good progress reducing ref TODOs (63 → 33). Polymutex suggested Ren could also work on the “wall”/lower-ranked wallets since the top-5 criteria are met; Ren free to choose.
  • Debate/Unresolved Questions: None material.
  • Actions: Ren to continue chipping away at refs; optionally extend below the top 5.

5. Treasury, compensation & funding pressure

  • Topic: Very low treasury; September payments; Tere’s pause offer.
  • Purpose: Flag the funding risk and ensure people get paid for work done.
  • Problem & Solutions: Treasury may not cover all month’s payments unless Milestone 1 is hit. September payments sent to everyone except Lucila, John, Matt (need EOAs) and Tere. Polymutex stressed compensation should happen regardless of funds; Tere offered to pause/allocate fixed hours pending EF funds.
  • Debate/Unresolved Questions: Whether payments can be sustained until EF disbursement; timing is the main risk.
  • Actions: Lucila, John, Matt to DM their EOAs; Matt to provide an EOA for funds. Hit Milestone 1 ASAP.

6. Milestone 1 breakdown & clear signing

  • Topic: Pre-launch issues, top-5 ratings, clear signing relaunch, UI performance.
  • Purpose: Confirm the team can actually deliver M1 (Oct 15).
  • Problem & Solutions:
    • Data collection/classification: The one gap for the top-5 ratings is data collection. Polymutex formally committed to Michael that by the end of the weekend there will be colored rating slices on wallets with completed network captures — implying the whole pipeline including interpretation. If that fails, a hacky manual fill-in from known data will be used to make the site look right.
    • Clear signing: Implementation is one of the last milestones for the Clear Signing WG. Wallets take time to adopt EIPs (e.g., 7702). The WG shared issue 3099 (spec test suite / benchmark standard), which Walletbeat should take ownership of. Michael will keep attending the WG meetings and present the EIP tracker.
    • UI performance: website crashes on mobile (pie chart), Firefox looks terrible, general slowness. Darryl away due to traveling; Michael has started the perf work. Polymutex noted a zero-gap layout issue on the EIP tracker at certain resolutions.
  • Debate/Unresolved Questions: For clear signing, whether a sufficient benchmark database alone covers the cases, or whether Walletbeat should also inspect open-source wallets’ code to see if they consume the ERC-7730 registry descriptors vs. rolling their own (wallets decode only some calldata, e.g. transfers/approvals, not all). Polymutex: do both — a strong benchmark database plus code inspection. Michael agreed.
  • Actions: Polymutex to deliver colored slices this weekend (else manual fill); Michael to keep attending WG + follow up on EIP tracker; fix the mobile crash & performance; Michael to look at the EIP tracker edge-gap layout.

7. Impact log, milestone 3 & social media strategy

  • Topic: How to generate real ecosystem impact and grow followers; the badge system.
  • Purpose: Address Milestone 3’s impact-log and follower targets, and the EF’s emphasis on visibly-evident impact.
  • Problem & Solutions:
    • Impact definition: Michael noted EF’s specific impact is quality impact (wallets changing behavior), not community impact — e.g., MetaMask/Ambire shipping changes. Clear-signing contributions may not count as net impact. The high-level goal is wallets actually changing their behavior.
    • Social media: Lucila plans to focus content on specific wallets (auditor-style threads: where a wallet fails/passes on each attribute, wallet-vs-wallet comparisons on a specific attribute like account portability) — formats that have historically had reach (e.g., the Rainbow-proxying finding post, ~30 likes). Polymutex agreed and noted the “follow me / check” thread was good; L2Beat-style deep dives work well; once launched, get other accounts to retweet. Also switch content mode for the conference, and consider a chat to share conference moments in real time.
    • Non-social impact avenues: more connections at the conference; showing wallet developers their rating page at the booth and explaining what to fix.
    • Badge system: Lucila suggested badges measuring wallet progress toward stage 2 / crypto values (inspired by the evaluator Frederick’s interest in how progress is measured). Michael initially worried it conflicts with the EF-requested progress slider. Resolution: badges highlight specific, topical items (e.g., clear-signing-supported stamp) that change over time, complementary to the EIP tracker and needing no extra data; the slider shows the overall journey. Polymutex: badges are specific attributes we want to highlight; slider is the long journey. Both can coexist.
  • Debate/Unresolved Questions: Whether badges are redundant with the slider (resolved: complementary). How exactly to convert conference presence into impact-log entries.
  • Actions: Lucila to pivot content to wallet-specific auditor threads and comparisons; plan conference-time content; Michael to push SheFi presentation and reuse for social; implement the badge system (topical stamps, complementary to the slider).

8. Octant rejection & the DAO fund application

  • Topic: Octant rejected; planning the DAO fund application.
  • Purpose: Keep the funding pipeline moving after the Octant loss; define the DAO proposal.
  • Problem & Solutions: Octant rejected (very selective). The DAO fund is milestone/impact-based, all-or-nothing, fully funded before work starts, with ≥1/3 of funds released via adoption. Scope debated (see Initiatives). Polymutex worried hardware-wallet adoption timelines are out of our hands; Michael worried about EF-grant overlap (clear signing is in EF Milestone 1). A coherent theme (transaction legibility, or clear signing broadly) was favored over “make wallets secure” (too vague to be fundable) or generic “EIP implementations” (too generic). Funding mechanics: 25% threshold for DAO funds, but 100% target regardless of source; outside donors/treasury can contribute; compare amounts against peer initiatives.
  • Debate/Unresolved Questions: Precise scope (hardware wallets vs. clear signing broadly vs. transaction legibility); the numbers (made up, to refine); whether to self-fund part of the 25% (treasury can’t right now); whether the DAO badge-holder vote differs from outside funding (Ren: the DAO vote allocates DAO ETH, but outside funders can also fund — the DAO won’t do 100%).
  • Actions: Ren to draft the application; brainstorm scope with Michael; define precise security-focused scope with a coherent theme; avoid conflict with EF clear-signing Milestone 1; don’t bucket adoption only to hardware wallets; refine funding numbers against peer projects.

9. Devcon talks, booth & travel

  • Topic: Approved talks, booth activities, who attends.
  • Purpose: Lock the Devcon presence and allocate the travel budget.
  • Problem & Solutions: Launch talk approved but only as a lightning session (disappointing; adapt). Michael taking Ren’s how-to-contribute talk to free slots. Booth: 2 days, activities by Lucila, CTA = follow on X + QR code + stickers. Who goes: polymutex (no reimbursement), Michael, Darryl (visa permitting); Ren not going; Lucila blocked on fronting reimbursement cost (treasury-dependent). Polymutex noted it’s odd to plan the booth without being there; will try to arrange reimbursement. Ren concerned about time split between the grant and the talk material (Michael offered help).
  • Debate/Unresolved Questions: Whether Lucila can attend (depends on upfront cost/reimbursement); whether three people is enough (yes, comfortably). Ren’s time allocation between grant and talk.
  • Actions: Lucila to check prices; put together the booth plan and share for feedback; Tere to make booth-screen graphics; Michael/Ren to coordinate on the how-to-contribute talk material; Michael to accept talk buttons.

10. SheFi, Kohaku & task allocation

  • Topic: SheFi presentation, Kohaku status, next-few-weeks assignments.
  • Purpose: Confirm remaining work and ownership.
  • Problem & Solutions: SheFi presentation to be pushed to GitHub and reused for social. Kohaku: harness done, collection not; focus on generic wallet data collection for M1. Matt open to being assigned — polymutex pointed him at the crash/perf issues (pre-launch tag) and the UI tag (incl. Firefox, the drawer idea, and possibly taking Darryl’s beta-navigation branch to completion with conflict resolution). Polymutex flagged some red pre-launch issues that may be closable.
  • Debate/Unresolved Questions: How long to wait for Darryl on the beta-navigation PR before Matt picks it up (coordinate in the group chat). Which red issues to close.
  • Actions: Matt to take pre-launch/perf + UI issues, review red pre-launch issues, and consider Darryl’s branch; Lucila to prioritize booth programming over UI issues; Ren to prioritize the grant then the talk; Michael to continue WG attendance, follow up with EF, visa, data-collection tagging (M1 priority), and help Matt/Darryl with UI.

11. Closing

  • Topic: Wrap-up.
  • Purpose: Confirm one more meeting before Devcon week.
  • Problem & Solutions: Hoping to have Milestone 1 done and be in a better funding state by then. Polymutex noted it’s a “sink or swim” situation.
  • Debate/Unresolved Questions: None.
  • Actions: One more sync before Devcon week; hit Milestone 1; improve funding state.

High-Level Summary of the Call

The call opened with a quick fix to the mobile crash (pie chart) and a largely on-track roll-call against last meeting’s commitments. The central theme was the funding crunch and the urgent need to hit EF Milestone 1 (Oct 15). The treasury is very low and may not cover all of this month’s payments unless Milestone 1 lands; September payments are outstanding for Lucila, John, and Matt (EOAs needed) and Tere. Tere has offered to pause/allocate fixed hours pending EF funds.

On Milestone 1, the main remaining gaps are data collection/classification (polymutex committed to colored rating slices on captured wallets this weekend, else a hacky manual fill-in), clear signing (Walletbeat to take ownership of the WG’s spec-test-suite issue #3099 and act as the social layer; whether to rely on a benchmark database vs. inspecting open-source wallets’ ERC-7730 descriptor consumption — both), and UI/performance (mobile crash, Firefox, general slowness — Michael picked this up since Darryl may not get to it in time). The top-5 software wallet ratings are otherwise finished.

Funding-wise, Octant was rejected (very selective), shifting focus to the DAO fund application — a milestone/impact-based, all-or-nothing grant requiring a security-focused theme with build and adoption milestones (≥1/3 of funds released on proven adoption). Ren will draft it, brainstorming scope with Michael; clear signing (broadly, not just hardware wallets) and a “transaction legibility” theme were favored over vague or overly narrow options, and care is needed to avoid overlap with the EF grant’s clear-signing Milestone 1.

On Milestone 3, the team aligned on a badge system (topical stamps, complementary to the EF-requested progress slider) and on a social strategy pivoting to wallet-specific auditor threads and comparisons (formats that have historically had reach), with the broader goal of real ecosystem impact (wallets changing behavior) rather than just community engagement. Devcon plans are largely locked: talks approved (launch talk downgraded to lightning — disappointing), booth activities and a follow-on-X call to action, with attendance set (polymutex, Michael, Darryl) and Lucila’s travel blocked on fronting reimbursement costs.

The call closed with clear per-person commitments focused on delivering Milestone 1 and stabilizing funding, plus a reminder of one more sync before Devcon week — framed by polymutex as a “sink or swim” moment, with the team thanked for hanging in.