Aaryamann Challani

Something to note with interep is that it requires a trusted intermediary which collects auth tokens (which have pii) and id commitments, and adds them to the merkle tree, which...

Something to note with slashing is that the actual `identity_secret` of the malicious peer is not revealed. It is the `identity_secret_hash` from which the `id_commitment` is derived. Due to this,...

Since we have completed the [spec](https://rfc.vac.dev/spec/48/) as well as the [forum post](https://forum.vac.dev/t/using-interep-for-sybil-resistant-rln/169) I will close this issue. Please feel free to re-open when required!

Adding to the previous comment, having application specific validation would enable censorship, so I am not sure if that is the way forward for spam prevention.

RLN-Interep context: https://github.com/vacp2p/research/issues/147#issuecomment-1333121101 In the context of status communities, each community could have their own merkle tree and set of relayers (or maybe even one relayer) which adds the updated...

> I have proposal for this: https://hackmd.io/vSpt3sJ-RcOYjb6jLmkWDg > > It's based on off-chain RLN like I talked about in my last comment, and _seems_ like a good trade-off given the...

Agreed. there may be some further optimizations we can do over time, but let's close this and open a specific issue later

This PR fixes https://github.com/vacp2p/zerokit/issues/82

> See above Tracking here https://github.com/vacp2p/rfc/issues/560

@richard-ramos, please can you check if the nightly wasm artifact [here](https://github.com/vacp2p/zerokit/releases/tag/nightly) is suitable till we complete the steps you mentioned? Having a new release is preferred since we are breaking...