@polymutex.eth
Most things Walletbeat looks for can be evaluated in one of two ways:
1️⃣: "Just use the wallet bro": Check that a feature exists or not by using the wallet. Example: does it resolve ENS addresses when sending tokens? Does it have a token recipient address book somewhere?
2️⃣ "Black-box testing": Run the wallet in a controlled environment, observe its behavior.
- L1 provider independence: Block all network to all but the L1 RPC endpoint
- Data collection: Analyze network traffic
- Light client: Run with a lying RPC node and see if the wallet notices
But some features can't be tested by either:
- Which cryptographic library does the wallet use?
- Where is hot wallet private key material stored?
- How does an MPC wallet reconstruct the key?
- Is my orderflow data resold after being sent to a transaction simulation service?
1 reply
1 recast
4 reactions