"Private" and "compliant" are considered to be a tradeoff. They're not. Today we ship the proof. @0xPredicate is now the enforcement partner in the 𝐌𝐞𝐫𝐜𝐞𝐬 𝐂𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 𝐄𝐧𝐠𝐢𝐧𝐞. Gate and audit, both now in product. Compliance for private payments is two problems, and they sit on opposite sides of the transaction: - Before a transfer settles (should this happen at all?) - After it settles (what happened, when an auditor asks?) The "after" half has been live since March. Through the Compliance Dashboard, authorised parties can request to audit specific transactions for regulatory purposes. Nothing beyond those transactions is exposed. 𝗪𝗲'𝗿𝗲 𝘀𝗵𝗶𝗽𝗽𝗶𝗻𝗴 𝘁𝗵𝗲 "𝗯𝗲𝗳𝗼𝗿𝗲" 𝗵𝗮𝗹𝗳! Predicate now screens each confidential transfers against the operator's policy before they settle: sanctions, AML, CFT. Compliant transfers proceed. Non-compliant ones are rejected, with a reason returned to the user. The policy stays with the institution. Predicate enforces what the operator defines, on every transfer, and policies update as regulations change without touching the deployment. Clean division of labour: - @0xPredicate handles policy and enforcement. - @TACEO_IO handles private storage and controlled disclosure. Together: 𝐚 𝐟𝐮𝐥𝐥 𝐜𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞 𝐬𝐭𝐚𝐜𝐤 𝐰𝐢𝐭𝐡 𝐧𝐨 𝐩𝐥𝐚𝐢𝐧𝐭𝐞𝐱𝐭 𝐝𝐚𝐭𝐚 𝐭𝐫𝐚𝐢𝐥.