How many confirmations for sending BSV to ChangeNow swap?

The number of confirmations required for a transaction is a policy decision made by the service provider, not a fixed rule of the protocol itself. Because the BSV network is designed for high-throughput, parallelised validation, and near-instant propagation, the security model does not rely on waiting for an arbitrary number of blocks to mitigate risk; instead, it relies on the economic incentives inherent in the proof-of-work and the ability of nodes to verify transactions in real-time. When dealing with a service like ChangeNOW, they will define their own threshold based on their internal risk management and their specific implementation of the BRC-79 token exchange protocol or similar integration. For them, the requirement is likely a balance between the speed of the user experience and their own internal policies regarding finality. In a properly functioning SPV environment, a transaction is cryptographically secure the moment it is included in a block and broadcast, as the cost of reversing that work is economically prohibitive. If you are building your own integration, you would typically consult the service’s documentation or their API to see what they have set as their "safe" threshold for their specific liquidity pools. How the protocol handles these confirmations through the BRC-136 block-anchored synchronization mechanism is a subject worth exploring if you are concerned with the technical mechanics of finality. Sources SpecChaintracksService with Bulk Headers CDN SpecAccess Gates for Metanet Rooms Satoshi 2008–11Exchange ideas SpecToken Exchange Protocol for UTXO-based Overlay Networks SpecBlock-Anchored Overlay Synchronization via Block-Aligned Sparse Merkle Trees (BASM)