Skip to main content

Compliance

We are building Platus so that privacy is usable for legitimate users, while making it difficult to misuse for sanctions evasion, terrorist financing, or laundering funds from exploits.

v1 Compliance Framework​

In our initial release, Platus applies a risk-based screening process to deposits before they enter the protocol.

Deposit Screening & Risk Evaluation​

Every deposit entering Platus enters a mandatory 4 hour settlement queue. During this window, our risk engine evaluates the source address against multiple risk vectors:

  • Sanctions screening: Checking against OFAC SDN lists and other applicable sanctions programs
  • Exploit monitoring: Flag addresses associated with protocol hacks, bridge exploits, or other confirmed thefts
  • Behavioral analysis: Identify patterns consistent with address poisoning, wash trading, or sybil behavior
  • Temporal analysis: Recently funded addresses with minimal on-chain history

No Custody Risk​

Critically, rejected deposits are never at risk. If a deposit is flagged or the settlement window expires without approval, users can immediately withdraw their funds to the depositing address.

At no point does Platus or any offchain actor in the system, gain custody of user funds. We cannot freeze assets. We cannot redirect transactions. We can only evaluate whether a deposit meets our risk criteria before it enters the shielded pool.