From: Matt Whitlock <bip@mattwhitlock•name>
To: Chris Beams <chris@beams•io>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bug in 2-of-3 transaction signing in Bitcoind?
Date: Tue, 15 Apr 2014 12:45:52 -0400 [thread overview]
Message-ID: <82239971.BzVTldK5cU@crushinator> (raw)
In-Reply-To: <981A0A04-EAE7-45BE-81FC-92A40A6B2DA4@beams.io>
On Tuesday, 15 April 2014, at 6:39 pm, Chris Beams wrote:
> Looks interesting. Is the source available?
The intent is to open-source it. We will do so when I'm confident that we have all the kinks worked out.
Here's what it can do presently:
$ ./btctool
usage: ./btctool <function> [<args>]
encode16
Encode stdin to hex.
decode16 [<hex>]
Decode hex from stdin or string.
encode64 [<hex>]
Encode stdin or octets to Base64.
decode64 [<base64>]
Decode Base64 from stdin or string.
encode58 <version> [<hex>]
Encode stdin or octets to Base58Check.
decode58 [<base58>]
Decode Base58Check from stdin or string.
disassemble [<script>]
Disassemble hex script.
sha256 [<hex>]
Hash stdin or octets using SHA-256.
rmd160 [<hex>]
Hash stdin or octets using RIPEMD-160.
privkey [<hex>]
Derive private key from stdin or octets.
pubkey [<privkey>]
Derive public key from private key.
address [<pubkey>]
Derive address from public key.
address <m> [<pubkey>...]
Derive m-of-n P2SH address from public keys.
encrypt [<privkey>]
Encrypt private key per BIP38.
decrypt [<privkey>]
Decrypt private key per BIP38.
shares <m> <n> [<privkey>]
Distribute private key into m-of-n shares.
join [<share>...]
Join shares to reconstitute private key.
privkeys <k> [<privseed>]
Derive k private keys from private seed.
pubkeys <k> [<pubseed>]
Derive k public keys from public seed.
addresses <k> [<pubseed>]
Derive k addresses from public seed.
addresses <k> <m> [<pubseed>...]
Derive k m-of-n P2SH addresses from public seeds.
$ ./chaintool
usage: ./chaintool <function> [<args>]
init
Initialize a new cache file.
add <label> <pubkey>
Add a public key.
add <label> :<pubseed>
Add a public seed.
add <label> <m> {<pubkey>|:<pubseed>}...
Add public keys/seeds for m-of-n P2SH.
rm <label>
Remove a public key or seed.
ls
List public keys and seeds.
sync <blocksdir>
Synchronize with block chain.
tip
Print hash of block at tip of main chain.
getbalance [<label>...]
Get available balance.
listunspent [<label>...]
List unspent outputs in JSON.
createtx [<fee>] [<label>...]
Create transaction from address+amount pairs on stdin.
signtx <tx> [{<privkey>|<privseed>}...]
Sign transaction with private key(s)/seed(s).
prev parent reply other threads:[~2014-04-15 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 15:00 Matt Whitlock
2014-04-15 15:05 ` Mike Hearn
2014-04-15 15:11 ` Pieter Wuille
2014-04-15 15:22 ` Matt Whitlock
2014-04-15 15:30 ` Mike Hearn
2014-04-15 15:42 ` Matt Whitlock
2014-04-15 15:47 ` Mike Belshe
2014-04-15 16:27 ` Matt Whitlock
2014-04-15 16:39 ` Chris Beams
2014-04-15 16:45 ` Matt Whitlock [this message]
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=82239971.BzVTldK5cU@crushinator \
--to=bip@mattwhitlock$(echo .)name \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=chris@beams$(echo .)io \
/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