Sending Dogecoin with SSP
This guide walks you through sending Dogecoin from an SSP wallet end to end. There are five steps, one signing prompt on the device that initiates the send, and one co-signature confirmation on the second device. Once you know the screens it takes under a minute, and Dogecoin's roughly one-minute blocks mean your transaction usually confirms fast.
It's written for anyone about to send their first DOGE transaction — and worth re-reading before your hundredth, because the address-checking habits are what keep funds safe. If you haven't set up your wallet yet, start with Setting up your first SSP wallet.
Before you start
Three prerequisites — none of them optional.
- Both paired devices are powered on and unlocked. SSP's 2-of-2 model needs signatures from both. If one device is dead, charging, or asleep, the send won't complete.
- You have the recipient address from a trusted source. Copy it — don't type it. Dogecoin addresses start with a capital D and are long; manual entry invites typos that send funds to the wrong wallet permanently. Trusted sources include the recipient's verified channel, an invoice from a service you control, or a freshly-generated address from your own second wallet.
- You've decided on a fee tier. SSP shows the current network estimate, but the priority you pick is yours: faster confirmation costs more, cheaper transactions can sit unconfirmed during congestion. More on Dogecoin's fees in step 3.
Step 1: Open the send screen
On the mobile app, tap the Send button on the home screen. On the browser extension, click Send in the top action bar.
If your SSP wallet holds multiple chains, the next screen asks you to pick the asset. Select Dogecoin from the list. Confirm the correct sub-account — SSP supports multiple accounts per chain, and the balance at the top of the send screen is for that specific account, not the wallet total. If it's lower than you expect, back out and check which account you're sending from; funds in another account are not spendable here.
Step 2: Paste the recipient address
Paste the recipient's Dogecoin address into the address field. Then — before you do anything else — verify the first 6 characters and the last 6 characters against the trusted source you copied from. Read them out loud if you need to. If even one character is off, stop, clear the field, and re-copy from the original source.
This isn't paranoia. It's defence against address poisoning: an attacker generates a new address whose first and last characters look almost identical to one you've used before, then sends you a dust transaction so it appears in your history. The next time you copy "the same" address from your transaction list, you copy theirs instead, your send goes to the attacker, and there is no recovery.
Always copy from the original trusted source, never from history, and always check the first and last 6 characters. For the broader pattern, see Phishing attacks targeting crypto users.
Step 3: Enter the amount and review the fee
Enter the amount to send. You can type in DOGE or your local fiat — SSP converts in real time at the current rate. The screen also shows the spendable balance and an estimated total including fee, so you can see at a glance whether you have enough.
Below the amount, SSP shows three fee tiers:
- Low — cheapest, but the transaction may sit in the mempool longer during congestion.
- Normal — the default; typically confirms within the next 1–2 blocks (about 1–2 minutes).
- High — pays a premium for the very next block. Useful for time-sensitive transfers or exchange deposits with deadlines.
One Dogecoin quirk: the nominal fee looks large next to Bitcoin. Dogecoin uses a higher minimum fee — often on the order of ~0.01 to ~1 DOGE — so you might see "1 DOGE" where a Bitcoin fee is a tiny fraction of a coin. Don't let the big number alarm you: in fiat terms a Dogecoin transaction is typically very cheap. The Low / Normal / High tiers still trade cost against confirmation priority exactly as on any other chain, and the model in Bitcoin fee strategy in SSP carries over directly.
Step 4: Sign on both devices
This is where SSP's 2-of-2 model fires. The transaction needs an independent signature from each of your paired devices before it can be broadcast.
On the initiating device (the one you've been using so far), review the summary one last time — recipient, amount, fee — and tap Confirm. The device signs locally; it does not yet broadcast.
Switch to the second device. Within a few seconds it should display a pending signing request — the same recipient, amount, and fee, with an Approve / Reject choice. Verify it matches the initiating device, then tap Approve. The second device signs and the two signatures are combined.
If the second device doesn't show the prompt within ~15 seconds:
- Make sure the SSP app is in the foreground (not just running in the background).
- Check that battery saver / data saver isn't blocking background sync.
- Confirm both devices have internet — Wi-Fi or mobile data; SSP needs a connection on each side to relay the request.
You can safely retry from the initiating device if needed. Until the second signature is in, no funds have moved. If the two-device requirement is new to you, What is 2-of-2 multisig? explains why it matters.
Step 5: Watch the broadcast
Once both signatures are collected, SSP submits the transaction to the Dogecoin network. The send screen flips to a Pending state and shows the transaction id (txid) — tap it to open a block explorer such as Blockchair.
Then wait for confirmations — on Dogecoin you won't wait long, since blocks arrive roughly once a minute:
- Casual transfers, small amounts — 1 confirmation (about a minute) is usually enough.
- Exchange deposits — most credit after a handful of confirmations; check the exchange's policy. On Dogecoin that still clears in minutes.
- Large transfers — many recipients wait for more depth before treating funds as final, but the fast blocks keep the wait short.
You can close the app now. The transaction is on the network; SSP doesn't need to stay open for it to confirm.
Dogecoin-specific notes
A few things worth knowing about Dogecoin — none of them change the flow above:
- Addresses start with
D. A standard Dogecoin address is a long string beginning with a capital D. If yours starts with anything else, it isn't a Dogecoin address — stop and re-copy. - Fast blocks, fast confirmations. Dogecoin's ~1-minute block time is among the fastest of the major UTXO chains, which is why step 5 resolves so quickly compared with Bitcoin. Its higher nominal fee (often ~0.01 to ~1 DOGE) still stays small in fiat — a property of the network, not an SSP setting.
- The same self-custody model as every SSP coin. Your keys are split across your two devices, so Dogecoin gets the same 2-of-2 protection as the rest of your wallet, and the send flow matches other UTXO coins — see Sending Bitcoin with SSP and Sending Litecoin with SSP.
For the protocol and the wider community, the official home is dogecoin.com.
Sending via a connected dApp
If the send is triggered by a browser-based dApp rather than initiated inside SSP, you're using <span id="[walletconnect](/academy/how-to/sending-bitcoin-with-ssp#walletconnect)"></span>WalletConnect — the open protocol that lets external dApps request signatures from your SSP wallet via QR code or deep link.
The flow is the same from step 4 onward: both devices must independently sign before the transaction broadcasts, and the dApp itself never sees your keys — it just gets the signed result.
The difference is in steps 2 and 3: the dApp pre-fills the recipient address, amount, and sometimes the fee. Your job changes from entry to observation — verify that the recipient and amount you're asked to sign match what you intended to authorise in the dApp. If anything looks off, reject the request and start over from the dApp side.
Related reading
- For the security model behind the two-device flow, see What is 2-of-2 multisig?.
- Sending other UTXO coins? Compare Sending Bitcoin with SSP and Sending Litecoin with SSP.
