I think the point is to use this proposed extension/standard for a
kind of "seed management" function, set it up on an offline device (an
always offline laptop, or a modified hardware wallet) where you put
the master seed. And then you use this as a kind of seed manager and
transcript the seeds fo
I think your proposal is simply to use BIP32 for all derivations and
the observation that you can work with derived keys with the
corresponding suffixes of the path. I believe that this is a good idea.
But I don't think that simply writing a standard will help. It's just
one step. If all your wall
I have completely revised the wording of this proposal I hope to be clearer in
explaining the motivation and methodology.
https://gist.github.com/ethankosakovsky/268c52f018b94bea29a6e809381c05d6
Ethan
‐‐‐ Original Message ‐‐‐
On Friday, March 20, 2020 4:44 PM, Ethan Kosakovsky via bitco
Chris,
Thank you for taking the time to share your thoughts. I agree there are wide
considerations surrounding key handling and storage. I dont think my proposal
interferes with that perspective any more than BIP32 itself would. How keys are
handled is a separate matter than the cryptography of
I agree with the problem statement in this proposal, but not the proposed
solution.
The challenge of safely securing a seed for a single signature is not
insignificant. Blockchain Commons has published procedures that we consider
the current best practices for cold storage in a free book at
http:/
I like this proposal and I see it's value: "One seed to rule them all."
Not hard to implement either.
---
Peter D. Gray || Founder, Coinkite || Twitter: @dochex || GPG: A3A31BAD
5A2A5B10
On Fri, Mar 20, 2020 at 03:44:01PM +, Ethan Kosakovsky wrote:
> I would like to present a propos
I think my proposal can be summarized simply:
1. get a child private key, hmac it and get entropy bits.
2. Use that entropy to feed BIP39 to make a new mnemonic seed
Bitcoin Core hdseed is a private key, so we can also do the same steps here
1. get a child private key, hmac it and get entropy bi
Pavol,
Yes thank you. I find abstracts hard, I will try again.
Currently I need a separate BIP30 for many of my wallets. I cant have one
master seed for all my wallets because some are less safe than others and
storing the master in each environment will increase the chance it could be
comprom
On 20/03/2020 16:44, Ethan Kosakovsky via bitcoin-dev wrote:
> I would like to present a proposal for discussion and peer review
I read your proposal twice and I still don't know what kind of problem
are you trying to solve.
This should be obvious from the "Abstract" and it's bad if it's not.
I would like to present a proposal for discussion and peer review. It aims to
solve the problem of "too many seeds and too many backups" due to the many
reasons stipulated in the proposal text.
https://gist.githubusercontent.com/ethankosakovsky/f7d148f588d14e0bb4f70bb6afc509d0/raw/6da51e837b0e1f
10 matches
Mail list logo
