Our system might require to store some state. Understanding the usecases may impact our passkeys architecture?

Publishers want a private list of subscribers.

One of the most relevant incentives for publishers to use Seed is to build influence in the web of trust by collecting users' keys.

Both sides, the publishers and subscribers want to keep their relationship private.

Reputation Systems will require state

Seed Hypermedia Network is an open, permissionless network—anyone can join and participate freely. Maintaining openness requires some key elements:

Cryptographic primitives.

Object capabilities.

Peer-to-peer protocols.

Reputation systems.

Reputation, in particular, requires storing how other peers request, respond, and introduce other peers. Therefore, reputation systems require storing records of other actors’ behavior.

Does this make our Sites stateful?

Would storing these records introduce statefulness at the Site level, or can we maintain a purely local and ephemeral approach? Are passkeys a good opportunity to have every single participant easily authenticated in the network?