Ring signatures would be one method.

In the DT case: produce a list of N npubs that my WoT can verify work in the Nixon administration, tell your tale, then sign it with a ring signature that proves you’re one of the N npubs without revealing which one. Obviously N needs to be sufficiently high to make you feel safe.

A more generic case: make a list of N accounts that are widely perceived as having high generic Trust Scores (eg GrapeRank or some other metric), then use a ring signature using that list.

Reply to this note

Please Login to reply.

Discussion

I wrote a NIP for Ring Signatures with this exact use case in mind back in April:

https://github.com/nostr-protocol/nips/pull/1894

Were you collabing with waxwing at the time, or am I remembering something/someone else?

Will have a look

schnorr multisig can enable thousands of signers too...

I should learn more about schnorr

yeah, remembering this, i probably should extend my pure go and libsecp256k1 bindings to also do signature aggregation and verification in the way it's done with musig2 using schnorr

That works, but it isn't free. You are averaging the trust and burning a bit of everyone in the ring's anonymity. In the case of abuse you burn some amount of everyone's trust.

How you pick these high generic trust accounts? Are you choosing for a known audience?

Those questions will be highly specific to each use case. WoT is one of those areas where there will be few if any perfect solutions, only tradeoffs. But in many cases — once again, highly dependent on the particulars of the use case — the tradeoffs will be worth making. To answer your question: the person crafting the message chooses the audience, depending on the message being sent.