I can't think of any that default to using uncompressed addresses.
Armory.
Topic: Can 1 private key create 2 addresses? (Read 370 times)
I can't think of any that default to using uncompressed addresses.
Armory. What does electrum create? Compressed or uncompressed?
Additionally, you'll find that most, if not all, "modern" wallets default to compressed... I can't think of any that default to using uncompressed addresses. 
What does electrum create? Compressed or uncompressed?
Compressed. It's much more practical for people to adopt compressed addresses as they are far more economical and segwit addresses derived from uncompressed keys are also non-standard.
What does electrum create? Compressed or uncompressed?
I don't remember any wallet specifically mention they used hybrid public key as well.
i don't think any wallet supports hybrid public key format at all. in fact i don't think that many people even know about it. i found it myself by accident looking at the source code of bitcoin core. it is one of those tiny details that are buried in the protocol and by the way it is non-standard and will be rejected if you try using it by this line (that's a standard-rule flag).
One legacy and one segwit. Can it?
Absolutely! Bitcoin uses the Elliptic Curve secp256k1 algorithm to calculate exactly one public key that goes along one private key. However the public key in turn can be used in different ways to make up a human readable format.In short:
Code:
1 Private Key -> 1 Public Key -> N addresses
Most used and standard address types:
- Legacy, P2PKH based on non-compressed public key
- Legacy, P2PKH based on compressed public key
- P2SH wrapped P2WPKH (Nested Segwit)
- Bech32 Native Segwit
But since addresses can be viewed as a readable form of an input script you could use the same public key to use more exotic and non-standard addresses like:
- P2SH-P2PK
- P2SH-P2PKH
- P2SH-1of1MultiSi
- P2SH-(locktime)
- 2WSH(locktime)
- ...
Basically you can come up with an umlimited amount of addresses all based on the same public key which is derived from a single private key. Internally however bitcoin does not use addresses so you should keep in mind every different type from above needs a different unlocking script.
1 private key create 2 public key (compressed and uncompressed),
actually each private key only creates one public key and that public key can be represented in 3 different forms: compressed, uncompressed and hybrid.
that public key in different form can be used in different scripts (which has virtually no limit in count) and create just as many addresses.
keep in mind that private key is just a number and public key is a point with (x,y) coordinate computed by adding G to itself private key times.
1 private key create 2 public key (compressed and uncompressed), which creates 5 type of addresses (P2PK, P2PKH, P2SH, P2WPKH & P2WSH). Take note that P2PK technically is just your public key.
However, there are various limitation which prevent specific public key/address combination, but i can't remember it.
However, there are various limitation which prevent specific public key/address combination, but i can't remember it.
2 legacy (compressed & uncompressed), 2 segwit (Native & Nested)
One legacy and one segwit. Can it?
Yes
Try this: https://iancoleman.io/bip39/
generate key and check different Derivation Path path.
Also this same key may generate compressed/uncompressed address (2 different ones).
One legacy and one segwit. Can it?
Jump to: