"Reorgs" and Associated Risks#
Transactions in a blockchain are packaged into blocks. Different blockchains have different rules for how to decide which transactions get packaged into a block, but they often include rules for invalidating recently generated blocks.This rewrite of history is called a "reorganization" ("reorg" for short) and invalidates any transactions included in the invalidated blocks. You can think of invalidated transactions that moved funds as transactions that "never happened".Such events can represent a security risk, because an attacker could use a cryptocurrency transfer as payment for a good or service, and subsequently trigger a reorg, thus invalidating his transfer (and getting his cryptocurrency back) while keeping the good or service he paid for.Confirmations#
To protect against reorg attacks, it's beneficial to wait for a number of confirmed blocks before recognizing a transfer as final. As more blocks are processed after a given block, the difficulty with which that block may be invalidated increases. Therefore, by choosing how many blocks to wait before recognizing a transfer, a receiver is able to balance speed (waiting very few blocks in order to process the transfer quickly while taking on risk of losing money due to a reorg) and security (waiting more blocks to minimize the risk of a reorg at the cost of slower transfer processing).The number of blocks you wait before considering a transfer as final is called the "confirmation number", which is typically different for different chains. WSPN Mint and its APIs use the following confirmation numbers for each supported chain. They are based on a variety of factors that WSPN has considered, including a given chain's historical performance, reorganizations, and overall architecture, and they do not reflect the blockchain networks' inherent requirements or limits.| Chain | Confirmations/Blocks | Approximate Time |
|---|
| Ethereum (WUSD,ETH) | 12 | ~3 minutes |
| Polygon (WUSD,MATIC) | 50 | ~2 minutes |
Confirmations and Transfer Status#
As soon as an incoming transfer is included in a block, the API will make it available for you (whether you poll the get transfers endpoint or subscribe to notifications). However, the transfer will have a running status and it will not credit the balance of the associated hosted wallet with the transfer amount until the required number of confirmations has been reached.At that point the transfer status will change to completed. If you have subscribed to notifications, you will receive a message indicating such status change.You might want to deem an incoming transfer completed before such a status change and fulfill your business process that depends on that transfer. But note that you will be doing so at your own risk, as you might never actually receive the funds in case there is a reorg before the number of confirmations has been reached.Please note that waiting for confirmations before crediting a wallet only applies for on-chain transfers, where the source is of type blockchain. Transfers between hosted wallets, where the source is of type wallet do not require waiting on confirmations and are credited instantly.
