Walletbeat sync 2026-04-09

Attendees

polymutex
REN2140
Hester (EF)
Teresa
Patrick
Darryl
0xMattmatt
johngrantuk on vacation today

Work we said we’d do last meeting (2026-03-19)

Work that was done despite not being planned

0xMattmatt
- Wallet IDs are now slug-style in site URLs
- Implemented duress resistance attribute
- Attribute announcements
  - Duress Resistance
  - Privacy Hygiene
- Windows issue problem
polymutex
- Try out new release of omnipin which fixes some bugs but now hits new ones, reverted
ren2140
- Added Uniswap Wallet skeleton + a PR to add some attributes easily parsed from existing source code
  - Giveth grant application (deadline april 15th)
darrylyeo
- Schema: simplify per-attribute outcome metadata field types
teresa
branding guidelines
External contributions

Initiatives & Updates

Are we on track?

polymutex to discuss

Tracker of tasks to launch: https://cryptpad.fr/sheet/#/3/sheet/edit/16422db4b3147f4c29f8c818b7a5f8e0/

https://cryptpad.fr/sheet/#/2/sheet/edit/IdVH5PCrqQxJKpu4LgcQsNi9/

ETHCC happenings

Hester to discuss

Recording of workshop: https://www.youtube.com/watch?v=Cl6fiSNDDhw

Workshop results: https://github.com/walletbeat/walletbeat/tree/beta/resources/talks/2026-03-ethcc/hesterbruikman-1ts-workshop

Branding / marketing

New look for social media!

Recovery & Unruggability attribute update

Post by 53bo: https://github.com/walletbeat/walletbeat/discussions/598

Website branding guidelines & UX progress

Teresa to discus

Walletbeat communications policy

Reminder to please acknowledge: https://github.com/walletbeat/walletbeat/pull/575

Next few weeks

polymutex
- Yes, still the data collection CLI
- Apply to Brew
- 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
johngrantuk
- Implement Release Process Transparency attribute after methodology discussions
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 after this call
lucilajuliana
- [add]
darrylyeo
- Systematization of CSS rules (fonts/colors)
  - Meet with Lucila
- Website bundle size fix (no inline SVGs on homepage)
  - Resolve browser compatibility issues with new shape() rendering technique (Firefox)
  - Re-evaluate raw data format / possible redundancy in Astro component boundaries
- Flower-y rating system component
  - Keep iterating on shapes + rendering methods
  - Match Figma design

Walletbeat Meeting Minutes (AI-generated)

Date: 2026-04-09 Project: Walletbeat (Ethereum Wallet Rating Initiative)

1. Attendees

Present:

polymutex
REN2140 (Ren)
Hester (Ethereum Foundation)
Teresa (Tere, Branding/Design)
Patrick (Cyfrin)
Darryl (UI/Engineering)
0xMattmatt (Michael, Testing/Research)

Absent (Work Discussed):

johngrantuk (On vacation; methodology updates discussed)
lucilajuliana (Branding/UI; work discussed)
davide (Research; work discussed)

2. Main Call Segments

Segment A: Introductions & Technical Onboarding

Topic: Roll call, introductions for new attendees (Tere), and troubleshooting audio/video issues.
Purpose: To integrate new branding contributors into the main sync and resolve connection glitches.
Problems & Solutions:
- Problem: Significant technical difficulties occurred during the call. polymutex experienced screen-sharing crashes (memory limit in browser) specifically when 0xMattmatt shared his screen, likely due to high-resolution buffers. There were also initial microphone glitches.
- Solution: It was determined that high-resolution presentations cause browser memory crashes on the host’s end. For future presentations, presenters should use lower-resolution screens or expect the host to drop out and rejoin.
Unresolved Questions: None.
Action Items:
- Tere: Continue integrating into the branding workflow.
- Team: Be mindful of screen resolution during future demos to prevent host-side crashes.

Segment B: Review of Previous Action Items (2026-03-19)

Topic: Status check on commitments made in the previous meeting.
Purpose: Accountability for the launch timeline and deliverables.
Problems & Solutions:
- Problem: polymutex acknowledged a delay in finishing the Data Collection CLI.
- Problem: The team originally targeted EthPrague for the initial launch/presence. polymutex decided to skip this event to prioritize the Berlin Blockchain Week (BBW) conference, as the project would be in a more fully launched state by then.
- Resolution: The launch timeline is effectively shifted towards BBW. Treasury funds are available for conference attendance if volunteers are found for Prague.
Unresolved Questions:
- 0xMattmatt: Availability for EthPrague/VISA is unclear, but focus has shifted to BBW.
Action Items:
- polymutex: Prioritize CLI completion, but acknowledge it may be deprioritized if BBW is the target.
- Team: Review the Launch Tracker (Cryptpad) to update status colors (Green=Done, Yellow=In Progress, Red=Not Started).

Segment C: Unplanned Work & Technical Progress

Topic: Reporting on work completed outside the original plan, specifically regarding the website, wallet integrations, and testing tools.
Purpose: To ensure untracked progress is documented and technical debt is addressed.
Problems & Solutions:
- Problem: The Walletbeat website bundle size was reported to be approximately 50MB for a static page, which is unsustainable.
- Solution: Darryl is working on removing inline SVGs and optimizing component boundaries (Astro). A PR exists to fix this.
- Problem: Omnipin integration issues. polymutex tested a new release that fixed previous bugs but introduced new ones.
- Solution: The update was reverted. The team is currently not using Omnipin until stability is proven.
- Progress: 0xMattmatt successfully deployed test contracts and updated the testing suite to use them. Wallet IDs on the site are now slug-style for better URL structure.
Unresolved Questions: Browser compatibility for new CSS shape() rendering techniques (Firefox) needs evaluation.
Action Items:
- Darryl: Resolve bundle size fixes and check browser compatibility for new CSS techniques.
- 0xMattmatt: Continue implementing attributes.

Segment D: Methodology, Attributes & Standards

Topic: Development of specific rating attributes and discussion of relevant Ethereum standards.
Purpose: To align the technical implementation of wallet scoring criteria.
Problems & Solutions:
- Topic: Release Process Transparency. johngrantuk has posted initial methodology on GitHub (Issue #580), covering reproducible builds, signed builds, and provenance.
- Topic: ERC 7730 & 7213. Discussion arose regarding these “Clear Signing” standards. Patrick needed to be consulted on details.
- Solution: The discussion regarding the specific ERCs was tabled until Patrick is available. The team agreed the current methodology (transaction scanner clarity) inherently covers the user outcome of these standards, but supporting the standard specifically is a step forward.
- Topic: Account Recovery/Unruggability. Updates proposed by user 53bo regarding requiring an onchain way to initiate social recovery (vs. reconstructing key fragments in memory).
- Solution: The team is reviewing if this should be a requirement or a possibility. Discussion is ongoing in GitHub Discussion #598.
Unresolved Questions: Whether to make onchain social recovery a hard requirement for the attribute.
Action Items:
- johngrantuk: Implement Release Process Transparency attribute post-methodology discussion.
- polymutex: Review 53bo’s proposal on recovery attributes.
- Ren & 0xMattmatt: Sync on wallet research methodology.

Segment E: ETHCC Workshop Feedback

Topic: Results from the workshop Hester conducted at EthCC.
Purpose: To validate the methodology against community feedback and assess sentiment.
Problems & Solutions:
- Observation: The workshop generated no controversy, which is viewed as a positive indicator that the methodology is sound.
- Data Point: The “Stage Spread” metric was highlighted (difference between max and min group rating for an attribute). Source Code Availability had a high spread, indicating significant community disagreement on its importance compared to other attributes.
- Observation: The format was engaging, but security attributes are too numerous for a single session.
- Solution: Future workshops should focus on narrower topics (e.g., Privacy or Transparency) to allow participants to grasp the full context.
Unresolved Questions: How to track and publicly disclose the list of wallet teams who attended the workshop (per Communications Policy).
Action Items:
- Hester: Compile and submit the list of attending wallet teams for public disclosure.
- Team: Plan similar focused workshops for future conferences (Brew, etc.).

Segment F: Branding & Design (Teresa/Tere)

Topic: Branding guidelines, logo, and UI implementation status.
Purpose: To finalize visual identity before the full launch.
Problems & Solutions:
- Problem: Figma designs are static and do not reflect interaction states (hover, click).
- Solution: The team acknowledged this gap. The Figma files are considered a reference for the “look”, but interaction mechanics need to be documented in code or separate specs.
- Progress: New social media logos and branding guidelines were presented and approved (“miles better”).
Unresolved Questions: None.
Action Items:
- Teresa: Finalize attribute icons (Column F of tracker) and submit to repo.
- Darryl: Sync with Lucila on UI development to ensure Figma-to-Code translation accounts for interaction mechanics.

Segment G: Policy, Communications & Next Steps

Topic: Communications policy acknowledgement and upcoming timeline.
Purpose: To ensure compliance with project governance and set the path for the next 3 weeks.
Problems & Solutions:
- Issue: Not all attendees have acknowledged the Communications Policy (PR #575).
- Solution: Reminder issued for all members to review and acknowledge.
- Issue: Grant application deadline for Giveth is approaching (April 15th).
- Solution: Ren is finalizing the application. If an EOA is needed, it can be sourced from the Treasury, potentially with a “finder’s fee” for the work.
Unresolved Questions: None.
Action Items:
- All: Acknowledge Communications Policy (PR #575).
- Ren: Submit Giveth grant application by April 15th.
- 0xMattmatt: Prepare blog posts explaining attributes for SEO/site content.
- polymutex: Apply to speak at Brew conference and book tickets for the chosen conference.
- Lucila: Record the next sync session for social media clips.

3. High-Level Summary

The April 9th Walletbeat sync meeting served as a milestone review prior to the project’s intended launch at Berlin Blockchain Week. The team successfully reviewed the previous month’s deliverables, confirming significant progress on technical infrastructure (test contracts, testing suite, branding assets) despite a delay in the Data Collection CLI.

Key technical decisions included the reversion of the Omnipin integration due to new instabilities and the identification of a major performance bottleneck (50MB bundle size) on the static website, which Darryl is tasked to resolve. Methodologically, the team validated their approach through feedback from Hester’s EthCC workshop, noting high community alignment on security practices but varied opinions on “Source Code Availability.”

The project timeline is effectively shifting from EthPrague to Berlin Blockchain Week to ensure a more mature launch. Actionable priorities for the next three weeks include finalizing the Giveth grant application, acknowledging the new Communications Policy, and preparing for a focused “Privacy/Transparency” workshop format at future conferences. The meeting concluded with a commitment to record future sessions for marketing assets and a scheduled follow-up in three weeks.