polymutex.eth

@maykelxyz Would you be interested in this issue? I think this would give you valuable experience for writing dapps, since this would be non-Walletbeat-specific code that does wallet connection stuff...

This would be useful to test all the test transactions used as part of the transaction legibility attribute. Very valuable for quickly testing new wallets on that, rather than having...

Agreed it's important. This should probably be an `enum` similar to the `License` enum, since a hardware wallet probably only has 1 such secure element chip, and it may be...

Bikeshedding names is always easy, but here goes: - I think "dApp Connection Support" should be renamed to "Web3 app support" - "Signing Intent Clarity" should be renamed "Clear signing",...

Another option here is to delete the attribute entirely, after having distributed the features it looks at across other attributes where it makes sense. For example, features like `rawEip712` and...

Agreed, it's a great set of security attributes. We should incorporate them into ours over time, and we should probably also link to Coinspect security ratings on per-wallet pages in...

Hi there, sorry for the delay. I've been on a semi-break for the last few weeks and am now starting to work more dedicated-ly towards Walletbeat. ### On collaboration As...

> Data Flow Both Ways Yes, agreed we should have shared identifiers. On Walletbeat, each wallet has an ID (e.g. `metamask`, `rabby`), then has one or more possible `Variant` (enum,...

> **Wallets to include** The list you have looks good. Agreed on not testing Daimo or Safe given their current state. Clave _is_ a wallet per [their FAQ](https://www.getclave.com/faq); I believe...

Hello again @juli and @matiassequeira! Just thought I'd write some thoughts and recaps on our discussions. ### WSR and Walletbeat as projects and their role in the wallet ecosystem The...