Segwit Addresses
What are segwit addresses? Transactions that spend bitcoins secured by segregated witness (segwit) use less block weight than equivalent non-segwit (legacy) transactions, allowing segwit transactions to pay less total fee to achieve the same feerate as legacy transactions.
Tested: version 2.2.0 on macOS
Tested on: 2019-07-24
Receive support
- Does not allow receiving to P2SH-wrapped segwit
Does not allow the generation of P2SH-wrapped (either P2WPKH or P2WSH) segwit receiving addresses.
- Does not allow receiving to bech32 segwit addresses
Does not allow the generation of bech32 native (either P2WPKH or P2WSH) segwit receiving addresses.
- Default receiving address is P2PKH
This service generates legacy P2PKH receiving addresses by default.
Send support
- Allows sending to bech32 P2WPKH addresses
Allows sending to bech32 P2WPKH native segwit addresses.
- Allows sending to bech32 P2WSH addresses
Allows sending to bech32 P2WSH native segwit addresses.
- No sending or change capabilities
There are no sending capabilities for this service or sending does not generate change.
Usability
Click on a thumbnail for a larger image or to play its video.
Opendime has a single P2PKH receive address. It can send to bech32 addresses using the included balance.py script.
Replace-by-Fee (RBF)
What is Replace-by-Fee (RBF)? An unconfirmed transaction can be replaced by another version of the same transaction that spends the same inputs. Most full nodes support this if the earlier transaction enables BIP125 signaling and the replacement transaction increases the amount of fee paid. In terms of block chain space used, this is the most efficient form of fee bumping.
Tested: version 2.1.0 on macOS
Tested on: 2018-10-18
Receiving support
- No notification
There are no incoming transaction notifications for this service.
- Received transaction not labeled replaceable in list
Does not visually indicate that an incoming transaction has signaled RBF.
- Does not show transaction details
Does not show transaction details natively. Usually this means the service links to a block explorer for transaction details.
- Shows replacement transaction only
Only the replacement transaction is shown in the transaction list. No original transaction is shown.
Sending support
- Does not signal BIP125 replacability when sending transactions
Does not allow sending of BIP125 opt-in-RBF transactions in the interface.
- Not tested: Does transaction list show whether sent transactions signal RBF?
We were not able to test this because sending a BIP125 signaling transaction is not supported.
- Not tested: Does transaction details page show whether received transaction signals RBF?
We were not able to test this because sending a BIP125 signaling transaction is not supported.
- Not tested: Are replacement and original sent transactions displayed?
We were not able to test this because sending a BIP125 signaling transaction is not supported.
Usability
Click on a thumbnail for a larger image or to play its video.
Sending Transaction - Opendime does not have traditional wallet capabilities. You can either sweep the private key to use in a regular wallet or use the balance.py script to send all funds to an address.
Sending Transaction - There is a balance.py python script which can send a transaction using pycoin but does not specify RBF when creating a transaction.
Receiving Transaction Signaling RBF - Opendime uses a simple address explorer on opendime.com. No RBF Flag. OPENDIME’s simple transaction list explorer does not provide RBF flag notice. However there are links to other explorers on the page (Blockchain.info, Blocktrail, LocalBitcoins, BitInfoCharts, a BIP122 link).
Receiving Replacement Transaction - Transaction list screen when a transaction has been replaced. Bottom transaction is the replacement transaction. Original transaction does not show up in list anymore.