bitcoinj also uses this convention.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software
Thanks Mike, and sorry to answer a bit late; it has been a busy couple
of weeks.
You are correct, a BIP39 seed phrase will not work in Electrum, and vice
versa. It is indeed unfortunate. However, I believe BIP39 should not be
followed, because it reproduces two mistakes I did when I designed the
Sigh. The wallet words system is turning into kind of a mess.
I thought the word list is in fact not a fixed part of the spec, because
the entropy is a hash of the words. But perhaps I'm misunderstanding
something.
The main problem regular SPV wallets have with BIP39 is that there is no
birth
On Wed, Mar 11, 2015 at 11:45 AM, Thomas Kerin m...@thomaskerin.io wrote:
I used BIP0090 as a place-holder, but I would like to request a BIP number
for this now.
We have had repeated problems in the past with people working on and
circulating prior draft proposals squatting on each others
The wallet words system isn't perfect for sure but it does help the user in two
main ways:
1) Assuming wallet devs ensure forward compatibility for _their_ wallet the
user knows they can recover their bitcoins using the same wallet software in
case of a Bad Thing Happening.
2) To an imperfect
On Wed, Mar 11, 2015 at 7:24 PM, Ricardo Filipe
ricardojdfil...@gmail.com wrote:
i guess you look at the glass half full :)
even though what you say is true, we should aim for wallets not to
require those instructions, by standardizing these things in BIPs.
let's hope bitcoin doesn't fail in
i guess you look at the glass half full :)
even though what you say is true, we should aim for wallets not to
require those instructions, by standardizing these things in BIPs.
let's hope bitcoin doesn't fail in standards as our industries have in
the past...
2015-03-11 19:04 GMT+00:00 Jim
I'm not convinced that wallet seed interoperability is such a great thing.
There is a wide variability in the quality and security level of wallet
implementations and platforms. Each new device and wallet software a user
types their seed into increases their attack surface and exposure to flaws.
Hi,
Perhaps at some point consider introducing something akin to a
'Bitcoin-Draft' (BD) status with some autoexpiry period?
I understand that the Internet Engineering Task Force (IETF)
http://www.ietf.org has the concept of 'Internet Drafts (ID)
http://www.ietf.org/ietf-ftp/1id-guidelines.txt
On Wed, Mar 11, 2015 at 11:24 PM, Pindar Wong pindar.w...@gmail.com wrote:
Perhaps at some point consider introducing something akin to a
'Bitcoin-Draft' (BD) status with some autoexpiry period?
I understand that the Internet Engineering Task Force (IETF) has the
concept of 'Internet Drafts
On Wed, Mar 11, 2015 at 11:50 PM, devrandom c1.sf-bitc...@niftybox.net wrote:
That said, I do agree that mnemonic phrases should be portable, and find
it unfortunate that the ecosystem is failing to standardize on phrase
handling.
The fact remains that there are several apparently unresolvable
Understood... perhaps just add something like:
'After copy-editing and acceptance,* a BIP number is assigned* and it will
be published here.'?
https://en.bitcoin.it/wiki/Bitcoin_Improvement_Proposals
p.
On Thu, Mar 12, 2015 at 7:34 AM, Gregory Maxwell gmaxw...@gmail.com wrote:
On Wed, Mar
ACK. CryptoCorp uses this method for our external signer service.
On 2015-03-11 04:45 AM, Thomas Kerin wrote:
Hi all,
I just created a PR on bitcoin/bips for a proposed standard for creating
standard multisignature P2SH addresses given m, and a set of public keys.
I'd like to offer that the best practice for the shared wallet use case
should be multi-device multi-sig.
Sure. But in practice people will want to have a pool of spending money
that they can spend when they are out and about, and also with one click
from their web browser on their primary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
I just created a PR on bitcoin/bips for a proposed standard for creating
standard multisignature P2SH addresses given m, and a set of public keys.
https://github.com/bitcoin/bips/pull/146
I used BIP0090 as a place-holder, but I would
Right you are!
I saw Thomas's email about Electrum 2.0 not supporting BIP39.
It seems he had the idea that the wordlist was a strict requirement yet it is
not, it is unfortunate that Electrum did not go the route of BIP39. The
wordlist is irrelevant and merely used to help build mnemonics.
Also
On Thu, Mar 12, 2015 at 2:41 AM, devrandom c1.sf-bitc...@niftybox.net wrote:
I think there are some important advantages to not being forced to use
the old wallet to send coins when switching wallets. The three I can
think of right now are: maintaining transaction history,
Just loading a key
Users will want to have wallets shared between devices, it's as simple as
that, especially for mobile/desktop wallets. Trying to stop them from doing
that by making things gratuitously incompatible isn't the right approach:
they'll just find workarounds or wallet apps will learn how to import
That's disappointing the Electrum 2.0 doesn't use BIP39.
From my interpretation of BIP39, wordlists DO NOT REQUIRE to be fixed between
wallet providers. There is some recommendations regarding the wordlists to
help with things such as predictive text, so mobile apps can easily predict
the word
On 2015-03-11 05:11 PM, Gregory Maxwell wrote:
On Wed, Mar 11, 2015 at 11:50 PM, devrandom c1.sf-bitc...@niftybox.net
wrote:
That said, I do agree that mnemonic phrases should be portable, and find
it unfortunate that the ecosystem is failing to standardize on phrase
handling.
The fact
On Wed, Mar 11, 2015 at 6:14 PM, Mike Hearn m...@plan99.net wrote:
- Electrum v2 with a version number but no date
- myTREZOR with no version and no date and BIP44 key derivation. Some
seeds I believe are now being generated with 24 words instead of 12.
- MultiBit HD with no
Yes I agree with this sentiment.
As for the version, don't forget we can kinda brute force our way to
determine a version, because lets say there is 10 versions, we can generate the
seed for all 10 versions and then check to see which seed was in use (has
transacted) and then use that seed. If
On Wed, Mar 11, 2015 at 10:12 PM, Thy Shizzle thashizn...@yahoo.com.au
wrote:
BIP39 is beautiful.
meh... the fact that you can't derive the seed phrase from the wallet seed,
and that the password key stretching is so weak as to be ineffectual
security theater bugs me. Feels like a pretty big
I agree that it's true that a static wordlist is
required once people have started using BIP39 for anything real and
changing the word lists will invalidate any existing mnemonics
^ This is incorrect I think Neill, the reason is that the only thing that
happens when you change the wordlist is
On Thu, Mar 12, 2015 at 02:16:38AM +, Thy Shizzle wrote:
That's disappointing the Electrum 2.0 doesn't use BIP39.
Agreed, but I don't know the full background on this.
Changing the wordlist in the future has ZERO effect on derived seed, whatever
mnemonic you provide will always generate
Hi, so I have my .NET node communicating on the P2P network just fine, so I
figured as I'll now start looking at making and validating transactions etc I
should probably migrate to test net. Now I see that we are up to the third
generation testnet testnet3, and I am sending my messages now
26 matches
Mail list logo
