bitgo.yaml

---
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
        tooltip 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.