Duelbits publishes two things most operators publish neither of: a closed list of the coins it accepts, with a stated consequence for sending anything else, and a table pairing coins with networks. Bitcoin is in the list and in the table, against the Bitcoin network. For a reader weighing whether to bring BTC here, those two documents answer the acceptance question without ambiguity.
They answer nothing else. The quality of the lobby, the pace of a payout review, the way an edge case is handled -- none of that is in a network table, and this page does not pretend to know it. What is worth the rest of the page is the thing both documents exist because of: a crypto transfer has no way back.
Two documents that answer two different questions
The coin list answers "will this be credited at all". It is closed, and the operator says plainly that other tokens may be permanently lost. The network table answers "by which route", which for Bitcoin is a single entry.
Keeping those apart is useful because they fail differently. A coin outside the list is simply not recognised. A recognised coin sent by a route the operator does not run is recognised and still gone. Duelbits is one of the few on this site that documents both halves rather than one.
No undo, and what that does to the order of care
A Bitcoin payment is final once a block carries it, and nothing in the arrangement leaves room for a reversal: there is no intermediary who holds the funds, no settlement delay during which an instruction can be withdrawn, and no account relationship on the sending side that could be invoked.
So the attention belongs in front of the payment. That sounds obvious and is not how most people are trained: card and bank payments teach that errors are fixed afterwards, by someone whose job it is. Here there is no afterwards and no someone.
One practical consequence is worth stating. A test transfer is not timidity, it is the only rehearsal available. It costs a small network fee and it converts an unknown into a known before the amount that matters moves.
What the documents leave out
No welcome figure, no wagering condition, no licence reference and no deposit floor appear on this page. The operator's pages were readable only with a full set of browser headers, and what came back were the coin list and the network table. That is the honest extent of it.
No score either. A well-documented cashier is a point in an operator's favour and it is not a rating, and a number out of ten would quietly claim to have weighed things we have not looked at.
On the screen
Confirm the coin against the closed list, then confirm the route against the table, then confirm the address against the screen. Three checks, each answering a different way of losing money.
Keep the transaction id afterwards. It is the one piece of evidence that outlives the tab.
What this page states about Duelbits was read at help.duelbits.com, the operator's own coin list and network table. The cashier screen inside an account is the current version and wins over anything written here.
Questions readers ask about this operator
Is Bitcoin on Duelbits' accepted list?
Yes, and it also appears in the operator's network table against the Bitcoin network.
What does the operator say about coins outside the list?
That sending them may mean permanent loss. The list is closed, which is what makes it useful.
Why does a test transfer help?
Because an irreversible payment offers no other rehearsal. A small amount confirms the route before a larger one moves.
Is a licence detail given here?
No. None was found in the operator's own material, and a licence is not a fact to take second-hand.
Related pages
Where to go from this operator.
Payments — every statement the twelve make about the coin, side by side
BetFury — the operator before this one on the shelf, read the same way
Sportsbet.io — the next operator on the shelf, with its own statement and its own gaps
Payment gone wrong — which failures a support desk can repair and which finished at broadcast
