Bitcoin’s ten-minute block time is an average, not a delivery promise.
A Bitcoin transaction first needs to be included in a block. New blocks arrive roughly every ten minutes on average, but any individual block can arrive sooner or much later. A low transaction fee can add further delay before inclusion.
For someone receiving BTC, “sent” and “confirmed” are different checkpoints. Bitcoin.org warns that unconfirmed transactions are not secure; additional confirmations make a transaction increasingly difficult to reverse.
The practical takeaway: check the transaction’s confirmation status, not just how long you have waited. Follow the receiving service’s confirmation requirements before treating a deposit as available.
Risk remains: neither a countdown nor a sender’s screenshot guarantees confirmation.
A bridge can remove a custodian without removing the risk of losing funds.
Crypto bridges connect separate blockchains. Some depend on operators holding assets or approving transfers; others rely more heavily on smart contracts and verification rules.
That distinction matters, but “trustless” is not a promise that software cannot fail. Ethereum.org identifies contract bugs and technology failures as bridge risks, while operator-dependent bridges can also introduce custody and censorship risks.
Before comparing fees, ask what you must trust: an operator, contract code, or both? Check the bridge’s documented security model rather than judging it by its label.
The practical limit: understanding those dependencies helps you assess risk. It does not guarantee a safe transfer.