migrate to RLNv2: update contract abstraction

[danisharora099]

Description

The js-rln library currently interacts with RLN v1 contracts. With the completion of the RLN v2 contract abstraction, we need to update js-rln to be compatible with the new contract architecture.

This update will:

• Ensure js-rln supports membership management functions as per RLN v2.
• Update the contract interactions to reflect new membership states (Active, GracePeriod, Expired, etc.).
• Align rate-limiting logic with RLN v2's dynamic rate allocation Support rate-limiting logic for memberships

---

User Story

• As a developer, I want js-rln to be compatible with RLN v2 so that I can integrate it seamlessly with dApps that use the latest contract version.
• As a Waku node operator, I want the RLN proof verification process in js-rln to align with the updated rate-limiting rules in RLN v2
• As a user of RLN-enabled applications, I want to interact with the RLN v2 contract without issues when registering, extending, or withdrawing memberships.

---

Proposed Solution / Feature Design

1. Upgrade Contract Interactions

• Update function calls in js-rln to align with the new RLN v2 contract methods.
• Implement handling for new membership lifecycle states.

2. Adapt Membership Management

• Ensure js-rln correctly registers, extends, and erases memberships based on RLN v2 rules.
• Implement logic to handle expired memberships and rate-limit reuse.

Notes

• resolved by feat(rln-v2): upgrade contract abstraction js-rln#110

[weboko]

@danisharora099 can you, please, specify scope of this task and attach PRs if present

[danisharora099]

@danisharora099 can you, please, specify scope of this task and attach PRs if present

updated

[fryorcraken]

Align rate-limiting logic with RLN v2's dynamic rate allocation.

@danisharora099 what do you mean on this logic? NOT for proof validation, right?

As a developer, I want js-rln to be compatible with RLN v2 so that I can integrate it seamlessly with dApps that use the latest contract version.

Nope, we don't need that

As a Waku node operator, I want the RLN proof verification process in js-rln to align with the updated rate-limiting rules in RLN v2.

Nope, we don't need that. I just need to be able to REGISTER a membership, and pass the resulting credentials to my wakunode2

As a user of RLN-enabled applications, I want to interact with the RLN v2 contract without issues when registering, extending, or withdrawing memberships.

yes

[danisharora099]

@danisharora099 what do you mean on this logic? NOT for proof validation, right?

This refers to supporting rate limit related methods from the contract: eg: currentTotalRateLimit, minTotalRateLimit, isValidMembershipRateLimit, etc

Nope, we don't need that. I just need to be able to REGISTER a membership, and pass the resulting credentials to my wakunode2

Yes, we descoped it out of this issue (as it doesn't align with our milestone), but wasn't updated part of the issue description here. Updated the description