vacp2p
/
rfc-index
mirror of https://github.com/vacp2p/rfc-index.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update and rename README.md to rln-interep-spec.md

This commit is contained in:
Jimmy Debe 2024-02-01 22:55:37 -05:00 committed by GitHub
parent cd8c9f45f4
commit 3f722d945c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
vac/48/README.md → vac/48/rln-interep-spec.md
View File

@ -9,7 +9,7 @@ editor: Aaryamann Challani <aaryamann@status.im>
contributors:
---
# Abstract
## Abstract
This spec integrates [Interep](https://interep.link) into the [RLN](https://rlnp2p.vac.dev/) spec.
Interep is a group management protocol that allows for the creation of groups of users and the management of their membership.
@ -25,7 +25,7 @@ RLN is used for spam prevention, and Interep is used for group management.
By using Interep with RLN, we allow users to join RLN membership groups without the need for on-chain financial stake.
# Motivation
## Motivation
To have Sybil-Resistant group management, there are [implementations](https://github.com/vacp2p/rln-contract) of RLN which make use of financial stake on-chain.
However, this is not ideal because it reduces the barrier of entry for honest participants.
@ -35,7 +35,7 @@ By modifying the RLN spec to use Interep, we can have Sybil-Resistant group mana
Since RLN and Interep both use Semaphore-style credentials, it is possible to use the same set of credentials for both.
# Functional Operation
## Functional Operation
Using Interep with RLN involves the following steps -
@ -43,16 +43,16 @@ Using Interep with RLN involves the following steps -
2. Verify reputation and join Interep group
3. Join RLN membership group via interaction with Smart Contract, by passing a proof of membership to the Interep group
## 1. Generate Semaphore credentials
### 1. Generate Semaphore credentials
Semaphore credentials are generated in a standard way, depicted in the [Semaphore documentation](https://semaphore.appliedzkp.org/docs/guides/identities#create-deterministic-identities).
## 2. Verify reputation and join Interep group
### 2. Verify reputation and join Interep group
Using the Interep app deployed on [Goerli](https://goerli.interep.link/), the user can check their reputation tier and join the corresponding group.
This results in a transaction to the Interep contract, which adds them to the group.
## 3. Join RLN membership group
### 3. Join RLN membership group
Instead of sending funds to the RLN contract to join the membership group, the user can send a proof of membership to the Interep group.
This proof is generated by the user, and is verified by the contract.
@ -77,28 +77,28 @@ Following is the modified signature of the register function in the RLN contract
)
```
# Verification of messages
## Verification of messages
Messages are verified the same way as in the [RLN spec](https://rfc.vac.dev/spec/32/#verification).
Messages are verified the same way as in the [RLN spec](../32/rln-v1/#verification).
# Slashing
## Slashing
The slashing mechanism is the same as in the [RLN spec](https://rfc.vac.dev/spec/32/#slashing).
It is important to note that the slashing may not have the intended effect on the user, since the only consequence is that they cannot send messages.
This is due to the fact that the user can send a identity commitment in the registration to the RLN contract, which is different than the one used in the Interep group.
# Proof of Concept
## Proof of Concept
A proof of concept is available at [vacp2p/rln-interp-contract](https://github.com/vacp2p/rln-interep-contract) which integrates Interep with RLN.
# Security Considerations
## Security Considerations
1. As mentioned in [Slashing](#slashing), the slashing mechanism may not have the intended effect on the user.
2. This spec inherits the security considerations of the [RLN spec](https://rfc.vac.dev/spec/32/#security-considerations).
2. This spec inherits the security considerations of the [RLN spec](../32/rln-v1/#security-considerations).
3. This spec inherits the security considerations of [Interep](https://docs.interep.link/).
4. A user may make multiple registrations using the same Interep proofs but different identity commitments. The way to mitigate this is to check if the nullifier hash has been detected previously in proof verification.
# References
## References
1. [RLN spec](https://rfc.vac.dev/spec/32/)
2. [Interep](https://interep.link)