PIP-39 - Voucher Update + Internal transfer for Base deployment testing

Proposal Summary

This proposal introduces a parameter change for vouchers on both deployments (Polygon and Base) and initiates the re-enablement of internal transfers on Base.

  • On Base, which is still pre-live, changes can be implemented directly by the dev team without Snapshot-executed scripts.
  • On Polygon, changes will require a script to be executed following a Snapshot vote. Those script details will be provided in the final stages of this proposal.
  • Internal transfers will first be re-enabled on Base as a testing environment. Once changes are validated there, a future PIP will be required to enable internal transfers on Polygon, as that deployment needs a script executed via Snapshot.

Motivation

1. Voucher reserves

  • The recharge voucher system (rewarding users with a 50 PRP voucher) is fully depleted and must be refilled so users can continue to earn PRP when they receive recharge vouchers.
  • The account activation voucher system is also close to depletion and requires a similar adjustment to remain operational.
  • Increasing reserves on both Polygon and Base will ensure these systems last significantly longer than before and reduce the need for frequent refills.

2. Internal transfers and KYT

  • Internal transfers were previously disabled due to insufficient monitoring tools to safeguard users. The original intent was to re-enable them when more advanced monitoring tooling was available.
  • While the planned “advanced” tooling is still pending and depends on future zone-manager requirements, our current KYT integration with PureFi has been significantly enhanced and is now comparable to KYT standards used by established privacy protocols (notably privacy pools).
  • This improved KYT logic already applies to deposits and withdrawals and did not exist when internal transfers were disabled. It should now be sufficient to support the re-enablement of internal transfers in a controlled way.
  • Because Base is pre-live, it is an ideal environment for the dev team to implement and test these changes without requiring multiple governance steps.

Proposed Changes

1. Voucher reserve parameters

  • Increase the recharge voucher reserve to 50,000 PRP.
  • Increase the account activation voucher reserve to 1,000,000 PRP.

These changes are intended to make both voucher systems last much longer than before under current usage patterns.

On Polygon, the relevant scripts for adjusting these parameters will be prepared by the developers and included in the Snapshot vote so they can be executed if the proposal passes.

2. Internal transfers on Base

  • Enable internal user-to-user transfers on the Base deployment, using the same KYT logic currently applied to deposits and withdrawals.
  • Extend the KYT function to internal transfers via additional PureFi integrations and testing on Base.
  • Once Base has been sufficiently tested and the behaviour validated, a follow-up PIP will propose enabling internal transfers on Polygon, which will again require a Snapshot-executed script.

3. Internal transfer daily limit

  • Introduce a per-user daily internal transfer limit of $25,000, aligned with the existing daily deposit limit.
  • This limit is intended to provide meaningful flexibility for users while remaining defensible given our KYC (ID, name, liveness) and KYT requirements.
  • The same logic and limit should apply to Polygon once that deployment is ready to be updated.

Next Steps

Community feedback

Members are invited to review and comment on:

  • Whether the proposed voucher reserve amounts are appropriate (too high, too low, or about right).
  • Re-enabling internal transfers on Base.
  • The proposed $25,000 daily internal transfer limit.

Voting

  • PIP-39 will be published on Snapshot for a 3-day vote, with voting eligibility defined in PIP-7.
2 Likes

Great proposal…The 25K limit for the internal transfer makes perfect sense initially! Let’s put this to vote!