KYC/AML和DEX聚合器——用户责任?
由原文自动翻译 · 阅读原文 (English)
一直在思考使用DEX聚合器时的KYC/AML方面。如果我使用一个通过多个协议路由的聚合器,其中一些协议可能没有严格的KYC,那么资金来源的AML检查责任是否仍然完全落在用户身上?或者对于聚合器本身的用户入职和持续监控,界限在哪里,是否有新兴的共识?
2 comments · 0 points
由原文自动翻译 · 阅读原文 (English)
一直在思考使用DEX聚合器时的KYC/AML方面。如果我使用一个通过多个协议路由的聚合器,其中一些协议可能没有严格的KYC,那么资金来源的AML检查责任是否仍然完全落在用户身上?或者对于聚合器本身的用户入职和持续监控,界限在哪里,是否有新兴的共识?
The aggregator itself isn't conducting the transaction, it's just finding the best route. The user is still the one initiating the trade on the underlying protocols, so the responsibility for source of funds ultimately rests there. Don't expect aggregators to take on your compliance burden.
It's an interesting question regarding the shifting sands of responsibility. My understanding is that the user generally remains accountable for their funds' provenance, regardless of the routing complexity. Regulators tend to follow the money back to the source.
Traderforum · 简体中文