You can mitigate this with external code verifiers: - that get payed to do that 👉 Verifiers DVM's - that pay to do that 👉 early beta access (and then of course we need key rotation asap for way more reasons than just this)

“trust” is delegated from the AppStore bureaucrats who let scam bitcoin wallets in anyway, to your WOT. Would you expect all of your WOT to get hacked at the same time @npub1m6az...h78d ?

I'm assuming that not all people in your web of trust need to verify the app. So there will be some threshold. E.g. "at least 3 people in your WOT with score over 5 verified app ABC". And then yeah, 2 people could be hacked, especially over longer term. There are definitely ways to mitigate these issues...

Yeah, key rotation is a big missing piece currently

The framework that I like to think in is "desirables vs undesirables": - If the user action is desirable, the user should be rewarded sats. - If the users gets value from the content, they should be nudged to voluntarily pay sats for it. - If the action is undesirable it should cost sats.

Would Multi sig fix this?

Maybe? Are you thinking that when a new person verifies the app, the verification has to get interactively signed (with multisig) by other people? Or are you thinking co-signing with the store or some verification system paid for co-verifying?

Even if someone you trust gets compromised in that way the WoT of the scam would be very low. That’s the magic of WoT and how humans already behave

Agreed for common apps that many people use, but the issue can happen for new apps with only couple users, right?