Overview
To maintain our zone’s compliance with applicable regulations and uphold our anti-money laundering (AML) and counter-terrorism financing (CTF) commitments, we request the development of a zone-level parameter for internal “zAccount → zAccount” private transfers within the Panther Protocol.
Purpose
This parameter will allow each zone operator to define a daily limit for internal zAccount transfers, ensuring zone-level flexibility to meet compliance and oversight requirements specific to different jurisdictions and operational policies.
Request to the Foundation
We request that the Foundation:
- Develop and implement a zone-level parameter within the protocol smart contracts that allows the daily limit for internal zAccount→zAccount transfers to be configured by the zone operator.
Compliance Rationale
Direct user-to-user private transfers, without appropriate monitoring, can fall within definitions of “money transmission” or trigger Virtual Asset Service Provider (VASP) or equivalent registration obligations under UK, EU, and FATF standards.
Providing a mechanism that can effectivley disable or limit these transfers at the zone level helps ensure regulatory compliance and mitigates associated risks.
This approach protects both the Panther Protocol and individual zone operators, while preserving functional flexibility for zones whose compliance configurations permit internal transfers.
Our Zone’s Intended Use of This Parameter
When this parameter is available and configurable:
-
Our DAO will vote to set the daily internal transfer limit for our zone to
0, effectively disabling zAccount→zAccount transfers in our zone. -
We will also remove the internal transfer option from our zone’s UI, so users have no frontend access to the feature.
-
These measures will be implemented specifically for compliance reasons, to ensure our zone does not offer functionality that lacks corresponding AML/CTF oversight measures.
Please may @reuben confirm the feasibility of this development request.