From: おのかちお <onokatio@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] MultiSig request URI proposal
Date: Thu, 4 Oct 2018 23:03:37 +0900 [thread overview]
Message-ID: <CAHm82F78NpV0UmyVMuka64Y1b0rwBO6FNj=KwAOm885d9q4xJg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
Hi.
I have an idea that subject.
There are already BIP 21.
But Multisig request URI is non exist.
My idea is below:
bitcoin-sigreq://{{rawtx}}?{{param}}
rawtx: raw transaction (encoded by base64)
param:
- pubkey={{public key for sign key pair}}
- hd_wallet_position={{path for HD wallet position}}
This URI scheme is used for multisig request from website to user's local
wallet.
How do you think ?
[-- Attachment #2: Type: text/html, Size: 640 bytes --]
next reply other threads:[~2018-10-04 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 14:03 おのかちお [this message]
2018-10-08 23:42 ` James MacWhyte
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='CAHm82F78NpV0UmyVMuka64Y1b0rwBO6FNj=KwAOm885d9q4xJg@mail.gmail.com' \
--to=onokatio@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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