The sunrise problem in crypto compliance is the mismatch that arises when jurisdictions implement the Travel Rule at different times or with different requirements. An exchange may be legally required to exchange transfer information with a counterparty that is not yet subject to equivalent obligations or operationally prepared.
How mismatched obligations arise
Crypto transfers can cross borders while regulatory implementation remains local. One institution may have established messaging systems and mandatory information requirements, while another operates in a market where equivalent rules are not yet effective. Even institutions subject to Travel Rule obligations may differ in scope, required data, or technical connectivity.
The resulting gap is not simply a software compatibility issue. It can involve uncertainty about who must collect information, whether disclosure is lawful, and how the receiving institution will protect or use it. A supported message format cannot resolve these legal and operational questions on its own.
How operators handle the gap
An exchange should identify the relevant jurisdictions and assess the counterparty before deciding how to process a transfer. Procedures may require additional information, manual review, an alternative approved communication method, or restrictions where obligations cannot be satisfied. The appropriate response depends on applicable law and the exchange’s documented risk policy.
Operators should distinguish institutional counterparties from self-hosted wallets, because the relevant obligations and available controls may differ. They should also avoid assuming that a counterparty’s inability to use a particular network proves noncompliance. Staff need clear escalation routes for incomplete responses, conflicting requirements, and uncertainty about the recipient’s regulatory status.
Why ongoing review matters
The sunrise problem changes as jurisdictions update their rules and institutions adjust their processes. Exchanges therefore need maintained jurisdictional assessments, counterparty records, and change management procedures. Recording the basis for exceptions helps explain decisions later. Customer-facing instructions should accurately describe information requirements without promising that every transfer route will remain available under changing legal conditions.
