Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please document the rpc steps for creating a multisig transaction. #183

Closed
ytrezq opened this issue Sep 18, 2020 · 2 comments
Closed

Please document the rpc steps for creating a multisig transaction. #183

ytrezq opened this issue Sep 18, 2020 · 2 comments

Comments

@ytrezq
Copy link

ytrezq commented Sep 18, 2020

Bitcoin core never did it because of p2sh but since it s now the responsability of the sender.

I meaning using rpc.
This goes from how to assemble the output script to how to build the raw transaction and select the required txid and utxo (since it can t be done manually).

@CassClark
Copy link

Hi

Creating a multisig transaction is not really the responsibility of the node, rather it resides with the user’s wallet. Once a multisig transaction is created, it can be sent to the node via the sendrawtransaction RPC.

It may be worth you taking a look at ElectrumSV ( https://electrumsv.io/download.html ) or similar wallets.

@ytrezq
Copy link
Author

ytrezq commented Oct 31, 2021

@CassClark No ! There an rpc endpoint for doing it from the node. It s about documenting how to use it.

Plase reopen !

yvettep321 pushed a commit to yvettep321/bitcoin-sv that referenced this issue Apr 11, 2022
…est bitcoin-sv#183)

Bug/CORE-298 Bad Height Getminingcandidate OnArk
chrisgibson01 added a commit that referenced this issue Apr 21, 2022
…hreshold

Merge in SV/sv from SVN-1852_update_remove_redundant_code to Radiant

* commit 'c62dde7d82d85d650b9cc49d9d1d1fa984f174ce':
  remove unused params from IsDust/GetDustThreshold
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants