Skip to content

Latest commit

 

History

History
95 lines (92 loc) · 3.71 KB

coinbase.md

File metadata and controls

95 lines (92 loc) · 3.71 KB
layout permalink name internal_url logo rbf segwit
page
/en/compatibility/coinbase/
Coinbase
/en/compatibility/coinbase
/img/compatibility/coinbase/coinbase.png
tested features examples
date platforms version
2018-11-05
web
n/a
receive send
notification list details shows_replaced_version shows_original_version
false
false
false
false
true
signals_bip125 list details shows_replaced_version shows_original_version
false
untested
untested
untested
untested
image caption
/img/compatibility/coinbase/rbf/send-screen-default.png
Sending RBF Transaction - Default send transaction screen.
image caption
/img/compatibility/coinbase/rbf/send-confirm.png
Sending RBF Transaction - Send transaction confirmation screen. Shows fees. No RBF flag. Transaction sent without RBF signaled.
image caption
/img/compatibility/coinbase/rbf/transaction-details-sent.png
Bumping RBF Transaction - Transaction not sent with RBF so no bumping possible.
image caption
/img/compatibility/coinbase/rbf/transaction-details-sent-2.png
Bumping RBF Transaction - After a period of time the View Transaction link shows up.
image caption
/img/compatibility/coinbase/rbf/transaction-list-incoming-rbf.png
Receiving RBF Transaction - Incoming RBF transaction list. No RBF label.
image caption
/img/compatibility/coinbase/rbf/transaction-details-incoming-rbf.png
Receiving RBF Transaction - Incoming RBF transaction details. No RBF label. Further transaction details are at BlockCypher explorer which does not label RBF transactions.
image caption
/img/compatibility/coinbase/rbf/transaction-list-incoming-replacement.png
Receiving Bumped RBF Transaction - After bumped transaction confirmed, the bumped transaction then shows up and is credited. Original transactions stay as pending (even after 100 confirmations).
tested features examples
date platforms version
2019-04-11
web
n/a
receive send
p2sh_wrapped bech32 bech32m default
true
false
false
p2sh_wrapped
bech32 bech32m change_bech32 segwit_v1 bech32_p2wsh
true
false
true
Fails address validation client side in the UI.
true
image caption
/img/compatibility/coinbase/segwit/receive-screen.png
Coinbase does not have an explicit option for receiving to bech32. Coinbase uses p2sh wrapped segwit addresses for receiving.
image caption
/img/compatibility/coinbase/segwit/send-screen.png
Coinbase allows sending to either wrapped or native segwit addresses. There is also visual validation of the address format.
image caption
/img/compatibility/coinbase/segwit/transaction-details-sent.png
Transaction details screen shows the bech32 address. However, the link for that address uses a block explorer (BlockCypher) which shows an error as it does not support bech32 addresses.
image caption
/img/compatibility/coinbase/segwit/change-address.png
Coinbase uses bech32 for their change addresses, even when the send is going to non bech32.

{% assign tool = page %} {% include templates/compatibility-page.md %}