Compatibility data: abra binance bitgo bitmex

_data/compatibility/abra.yaml

@@ -0,0 +1,85 @@
+---
+name: Abra
+internal_url: /en/compatibility/abra
+logo: /img/compatibility/abra/abra.png
+rbf:
+  tested:
+    date: "2018-12-06"
+    platforms:
+      - iOS
+    version: "5.4.0"
+  features:
+    receive:
+      notification: "na"
+      list: "false"
+      details: "false"
+      shows_replaced_version: "false"
+      shows_original_version: "false"
+    send:
+      signals_bip125: "false"
+      list: "untested"
+      details: "untested"
+      shows_replaced_version: "untested"
+      shows_original_version: "untested"
+  examples:
+    - image: /img/compatibility/abra/rbf/send-screen-default.png
+      caption: >
+        Sending Transaction - Default send transaction screen.
+    - image: /img/compatibility/abra/rbf/send-confirm.png
+      caption: >
+        Sending Transaction - Send transaction confirmation screen.
+    - image: /img/compatibility/abra/rbf/send-fee-notice.png
+      caption: >
+        Sending Transaction - Network fee notice details.
+    - image: /img/compatibility/abra/rbf/transaction-list-sent.png
+      caption: >
+        Sending Transaction - Transaction list screen showing sent transaction. No RBF notice.
+    - image: /img/compatibility/abra/rbf/transaction-details-sent.png
+      caption: >
+        Sending Transaction - Sent transaction details. No RBF notice. Note transaction sent without RBF flag. Transaction was not sent with RBF so no bumping available.
+    - image: /img/compatibility/abra/rbf/transaction-list-incoming-rbf.png
+      caption: >
+        Receiving Transaction Signaling RBF - Abra does not show unconfirmed transactions.
+    - image: /img/compatibility/abra/rbf/notification-incoming-replacement.png
+      caption: >
+        Receiving Replacement Transaction - When the replacement transaction receives 1 confirmation it appears in wallet. No RBF notice.
+    - image: /img/compatibility/abra/rbf/transaction-list-incoming-replacement.png
+      caption: >
+        Receiving Replacement Transaction - Transaction list screen. No RBF flag.
+    - image: /img/compatibility/abra/rbf/transaction-details-replacement-confirmed.png
+      caption: >
+        Receiving Replacement Transaction - Replacement transaction details.
+segwit:
+  tested:
+    date: "2019-04-11"
+    platforms:
+      - iOS
+    version: "5.11.1"
+  features:
+    receive:
+      p2sh_wrapped: "false"
+      bech32: "false"
+      default: "p2pkh"
+    send:
+      bech32: "false" 
+      change_bech32: "untested"
+      segwit_v1: "Bech32 not supported."
+      bech32_p2wsh: "false"
+  examples:
+    - image: /img/compatibility/abra/segwit/receive-screen.png
+      caption: >
+        Abra uses P2PKH addresses for receiving. 
+    - image: /img/compatibility/abra/segwit/send-bech32.png  
+      caption: >
+        Abra allows a bech32 address to be input and does not provide a warning.
+        However, the review button was not enabled until a non-bech32 address
+        was provided. The eventually sent transaction used exact change so
+        change address format was not determined.
+    - image: /img/compatibility/abra/segwit/send-bech32-qr.png  
+      caption: >
+        When using the QR code scanner, an error about address format was shown
+        when scanning a bech32 address.
+    - image: /img/compatibility/abra/segwit/send-non-bech32.png  
+      caption: >
+        When using a non bech32 address, the "Review" button is enabled. Button
+        is disabled when using bech32 address format.

_data/compatibility/binance.yaml

@@ -0,0 +1,71 @@
+---
+name: Binance
+internal_url: /en/compatibility/binance
+logo: /img/compatibility/binance/binance.png
+rbf:
+  tested:
+    date: "2018-11-06"
+    platforms:
+      - web
+    version: "n/a"
+  features:
+    receive:
+      notification: "false"
+      list: "false"
+      details: "false"
+      shows_replaced_version: "false"
+      shows_original_version: "false"
+    send:
+      signals_bip125: "false"
+      list: "untested"
+      details: "untested"
+      shows_replaced_version: "untested"
+      shows_original_version: "untested"
+  examples:
+    - image: /img/compatibility/binance/rbf/send-screen.png
+      caption: >
+        Sending Transaction - Default send (withdrawal) screen. No RBF options.
+    - image: /img/compatibility/binance/rbf/transaction-list-sent.png
+      caption: >
+        Attempting Transaction Replacement - Transaction not sent via RBF. No fee bump options.
+    - image: /img/compatibility/binance/rbf/transaction-list-incoming-rbf.png
+      caption: >
+        Receiving Transaction Signaling RBF - No unconfirmed transactions appear in transaction list.
+    - image: /img/compatibility/binance/rbf/transaction-list-replacement-confirmed.png
+      caption: >
+        Receiving Replacement Transaction - Replacement transaction only shows up after confirmation. Neither transaction shows before.
+segwit:
+  tested:
+    date: "2019-04-11"
+    platforms:
+      - web
+    version: "n/a"
+  features:
+    receive:
+      p2sh_wrapped: "false"
+      bech32: "false"
+      default: "p2pkh"
+    send:
+      bech32: "true" 
+      change_bech32: "untested"
+      segwit_v1: "Does not pass front end javascript validation"
+      bech32_p2wsh: "false"
+  examples:
+    - image: /img/compatibility/binance/segwit/receive-screen.png
+      caption: >
+        Binance receives via P2PKH addresses. 
+    - image: /img/compatibility/binance/segwit/send-screen.png
+      caption: >
+        Default send screen accepts a bech32 address.
+    - image: /img/compatibility/binance/segwit/send-address-error.png
+      caption: >
+        While Binance allows bech32 P2WPKH withdrawals, you cannot add a bech32 address
+        to your address book _from the send screen_. While attempting to add a bech32 address, after
+        the two-factor authentication code, an address error message appears.
+    - image: /img/compatibility/binance/segwit/send-p2wsh-error.png
+      caption: >
+        Bech32 P2WSH addresses cause a validation error from the send screen and address
+        book screens.
+    - image: /img/compatibility/binance/segwit/address-book-add.png
+      caption: >
+        Bech32 P2WPKH addresses can be successfully added using the address book functionality.

_data/compatibility/bitgo.yaml

@@ -0,0 +1,74 @@
+---
+name: BitGo
+internal_url: /en/compatibility/bitgo
+logo: /img/compatibility/bitgo/bitgo.png
+rbf:
+  tested:
+    date: "2018-12-06"
+    platforms:
+      - web
+    version: "n/a"
+  features:
+    receive:
+      notification: "false"
+      list: "false"
+      details: "false"
+      shows_replaced_version: "false"
+      shows_original_version: "false"
+    send:
+      signals_bip125: "false"
+      list: "untested"
+      details: "untested"
+      shows_replaced_version: "untested"
+      shows_original_version: "untested"
+  examples:
+    - image: /img/compatibility/bitgo/rbf/send-screen.png
+      caption: >
+        Sending Transaction - Default send transaction screen with fee options expanded. No RBF options.
+    - image: /img/compatibility/bitgo/rbf/sent-confirmation.png
+      caption: >
+        Sending Transaction - Send confirmation screen. Fee noted. No RBF note. Note Transaction was not sent with RBF flag enabled.
+    - image: /img/compatibility/bitgo/rbf/transaction-list-sent.png
+      caption: >
+        Attempting Transaction Replacement - Transaction list screen showing sent transaction. No RBF options. Note BitGo uses the Smartbit explorer to show transaction details.
+    - image: /img/compatibility/bitgo/rbf/transaction-list-incoming-rbf.png
+      caption: >
+        Receiving Transaction Signaling RBF - Unconfirmed transactions do not appear in BitGo transactions list.
+    - image: /img/compatibility/bitgo/rbf/notification-incoming-rbf.png
+      caption: >
+        Receiving Transaction Signaling RBF - Incoming transaction email. No RBF note.
+    - image: /img/compatibility/bitgo/rbf/transaction-list-replacement-confirmed.png
+      caption: >
+        Receiving Replacement Transaction - Since no unconfirmed transaction
+        appear, neither original nor replacement show until the replacement
+        transactions confirms.
+segwit:
+  tested:
+    date: "2019-04-12"
+    platforms:
+      - web
+    version: "n/a"
+  features:
+    receive:
+      p2sh_wrapped: "true"
+      bech32: "false"
+      default: "p2sh_wrapped"
+    send:
+      bech32: "true" 
+      change_bech32: "false"
+      segwit_v1: "Error occurs during sending process, after validation."
+      bech32_p2wsh: "true"
+  examples:
+    - image: /img/compatibility/bitgo/segwit/receive-screen.png
+      caption: >
+        BitGo's web wallet UI defaults to P2SH-wrapped segwit addresses.
+        Visually, the segwit logo is displayed next to segwit addresses with a
+        toolip indicating "Wrapped Segwit". While bech32 receive addresses are 
+        not possible in the UI currently, bech32 receive addresses can be generated using the API. 
+    - image: /img/compatibility/bitgo/segwit/send-screen.png
+      caption: >
+        BitGo's web wallet allows sending to bech32 addresses. Change addresses
+        are not bech32 native, but P2SH-wrapped segwit addresses.
+    - image: /img/compatibility/bitgo/segwit/send-v1.png
+      caption: >
+        BitGo's web wallet displays an error when attempting send to segwit v1 addresses.

_data/compatibility/bitmex.yaml

@@ -0,0 +1,50 @@
+---
+name: BitMEX
+internal_url: /en/compatibility/bitmex
+logo: /img/compatibility/bitmex/bitmex.png
+rbf:
+  tested:
+    date: "2018-11-05"
+    platforms:
+      - web
+    version: "n/a"
+  features:
+    receive:
+      notification: "na"
+      list: "false"
+      details: "false"
+      shows_replaced_version: "false"
+      shows_original_version: "false"
+    send:
+      signals_bip125: "false"
+      list: "untested"
+      details: "untested"
+      shows_replaced_version: "untested"
+      shows_original_version: "untested"
+  examples:
+    - image: /img/compatibility/bitmex/rbf/send-screen.png
+      caption: >
+        Sending Transaction - Send Transaction screen. Transactions sent out of BitMEX are not RBF signaled. BitMEX only accepts confirmed transactions.
+segwit:
+  tested:
+    date: "2019-04-12"
+    platforms:
+      - web
+    version: "n/a"
+  features:
+    receive:
+      p2sh_wrapped: "false"
+      bech32: "false"
+      default: "p2sh"
+    send:
+      bech32: "false" 
+      change_bech32: "false"
+      segwit_v1: "Bech32 not supported."
+      bech32_p2wsh: "false"
+  examples:
+    - image: /img/compatibility/bitmex/segwit/receive-screen.png
+      caption: >
+        BitMEX uses a static P2SH address per user account.
+    - image: /img/compatibility/bitmex/segwit/send-screen.png
+      caption: >
+        BitMEX does not support sending to native bech32 addresses.

en/compatibility/abra.md

@@ -0,0 +1,6 @@
+---
+layout: page
+permalink: /en/compatibility/abra/
+---
+{% assign tool = site.data.compatibility.abra %}
+{% include templates/compatibility-page.md %}

en/compatibility/binance.md

@@ -0,0 +1,6 @@
+---
+layout: page
+permalink: /en/compatibility/binance/
+---
+{% assign tool = site.data.compatibility.binance %}
+{% include templates/compatibility-page.md %}

en/compatibility/bitgo.md

@@ -0,0 +1,6 @@
+---
+layout: page
+permalink: /en/compatibility/bitgo/
+---
+{% assign tool = site.data.compatibility.bitgo %}
+{% include templates/compatibility-page.md %}

en/compatibility/bitmex.md

@@ -0,0 +1,6 @@
+---
+layout: page
+permalink: /en/compatibility/bitmex/
+---
+{% assign tool = site.data.compatibility.bitmex %}
+{% include templates/compatibility-page.md %}