From: Mike Hearn <mike@plan99•net>
To: Levin Keller <post@levinkeller•de>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Export format for xpub
Date: Mon, 2 Feb 2015 12:33:26 +0100 [thread overview]
Message-ID: <CANEZrP3Tuw3mJLSuoOA4iOmg6u9sdh-E5NNm_FgdYs3Mx39znA@mail.gmail.com> (raw)
In-Reply-To: <CAG86ZOxYh+=rny3sPHeJ0qs6R=5frLXERKmwhVECGHo7tkrz3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2536 bytes --]
We generally don't edit BIPs like that after they've been written except to
add helpful links, examples etc and other things that don't add new
functionality. For this you'd write a new BIP. It doesn't have to be hard.
The process is:
1) Adapt the template BIP and fill it out with your motivation, design,
rationale and ideally some examples.
2) Post it here and ask Gregory for a BIP number. He will select one
through some magic algorithm I am still reverse engineering ;)
3) People will give feedback and try to spot problems in your spec.
I looked at what Andreas is doing a few days ago - basically it's just an
xpub string with a ?a=b&c=d query string added to the end, with a hierarchy
type specifier and something else I forgot, encoded into a QR code. So it
should be a very easy BIP to add.
Whilst you're at it you might want to add an HTTP POST based method,
though. Web apps scanning QR codes is kind of clunky compared to just
picking Coyno from a list in the wallet app and having it all
auto-magically activate.
On Mon, Feb 2, 2015 at 9:56 AM, Levin Keller <post@levinkeller•de> wrote:
> Hello everyone,
>
> I think this is my first email to this mailinglist so I will shortly
> introduce myself:
>
> I am Levin and the CEO of Coyno (www.coyno.com). Based in Berlin,
> mathematician. Bitcoiner since 2011.
>
> And now the reason for this email: Andreas (Schildbach) just released a
> new update of his wallet. It now provides an export functionality for the
> m/0' key in order to run read only copies on other devices. We already
> support the format on our website. Of course we would love for this to
> become standard. I also updated the Wiki article for Andreas' Wallet:
> https://en.bitcoin.it/wiki/Bitcoin_Wallet
>
> How do you like it? How does this format get standard? Shall I try to get
> a pull request to BIP32 passed?
>
> Cheers
>
> Levin
>
>
> ------------------------------------------------------------------------------
> 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 development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 3550 bytes --]
next prev parent reply other threads:[~2015-02-02 11:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 8:56 Levin Keller
2015-02-02 11:33 ` Mike Hearn [this message]
2015-02-02 12:38 ` Andreas Schildbach
2015-02-02 12:59 ` Pavol Rusnak
2015-02-02 14:17 ` Andreas Schildbach
2015-02-02 14:47 ` vv01f
2015-02-03 0:02 ` Andreas Schildbach
2015-02-02 14:56 ` Pavol Rusnak
2015-02-03 0:05 ` Andreas Schildbach
2015-02-03 0:22 ` Pavol Rusnak
2015-02-03 9:33 ` Levin Keller
2015-02-03 10:10 ` Pavol Rusnak
2015-02-03 10:37 ` Andreas Schildbach
2015-02-03 10:44 ` Pavol Rusnak
2015-02-03 10:35 ` Andreas Schildbach
2015-02-03 10:34 ` Andreas Schildbach
2015-02-02 12:57 ` Pavol Rusnak
2015-02-02 11:38 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP3Tuw3mJLSuoOA4iOmg6u9sdh-E5NNm_FgdYs3Mx39znA@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=post@levinkeller$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox