Pages:
Author

Topic: Pushing Partially Signed Transactions to other Bitcoin Clients - page 2. (Read 2038 times)

legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
If so can you point me at the RPC API code where this is done.

I don't think source code is going to help you - but I think the new tool "bitcoin-tx" might be what you want to look into (I am not sure if there is much documentation about its use yet).
hero member
Activity: 906
Merit: 1034
BTC: the beginning of stake-based public resources

It can't do that (as I explained above).

You can create the raw tx using the RPC API (or the new tool bitcoin-tx) but you'd have to send the incomplete raw tx using a different method (such as via email).


Ah, misunderstood.

So you're saying one can create the partially signed TXs via the RPC API, but they have to be transferred via another medium/protocol?

If so can you point me at the RPC API code where this is done.

Thanks again, this is very useful.
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
How does a Bitcoin client start a multisig and notify another client to sign for it? Do you know where the source code for this is located?

It can't do that (as I explained above).

You can create the raw tx using the RPC API (or the new tool bitcoin-tx) but you'd have to send the incomplete raw tx using a different method (such as via email).
hero member
Activity: 906
Merit: 1034
BTC: the beginning of stake-based public resources
I don't think this can be done using any "standard" client (things like "coin-join" are somewhat similar and they require specialised software).

The raw tx RPC calls will let you build up the tx piece by piece but a non-complete tx is not able to be broadcast to the network (AFAIA).


Thanks.

How does a Bitcoin client start a multisig and notify another client to sign for it? Do you know where the source code for this is located?
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
I don't think this can be done using any "standard" client (things like "coin-join" are somewhat similar and they require specialised software).

The raw tx RPC calls will let you build up the tx piece by piece but a non-complete tx is not able to be broadcast to the network (AFAIA).
hero member
Activity: 906
Merit: 1034
BTC: the beginning of stake-based public resources
I'm trying to understand how transactions are signed sequentially for m-of-n. I'm trying to find out if there is a way to push (and/or pull) a partially signed transaction for m-of-n from one Bitcoin client to another. And if so is this done over a bind()ed TCP socket? Or can it also be done via something like an RCP API?

If so:
  • What triggers the transaction being sent?
  • Can you specify who the recipient is?
  • Can you point me to the code which implements this?
Pages:
Jump to: