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

Add fundrawtransaction RPC call #1553

Merged

Conversation

torkelrogstad
Copy link
Contributor

As mentioned in #1500

Copy link
Collaborator

@Rjected Rjected left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This registers the command for btcjson and rpcclient, so one can issue these commands, but it does not actually expose the command externally, and I wouldn't call this complete without adding that functionality.

rpcclient/rawtransactions.go Outdated Show resolved Hide resolved
btcjson/chainsvrresults.go Show resolved Hide resolved
btcjson/chainsvrresults.go Show resolved Hide resolved
@torkelrogstad
Copy link
Contributor Author

This registers the command for btcjson and rpcclient, so one can issue these commands, but it does not actually expose the command externally, and I wouldn't call this complete without adding that functionality.

Are you talking about this line?

MustRegisterCmd("fundrawtransaction", (*FundRawTransactionCmd)(nil), flags)

That is necessary for the RPC client to call this method. You're right in that this is a client-side implementation of the RPC, not server-side. My use case is using the RPC client against a Bitcoin Core backend. If there's a better way of doing a client-only implementation I'm happy to change this, but I think this is the correct way of implementing a client-only RPC.

@Rjected
Copy link
Collaborator

Rjected commented Apr 2, 2020

This registers the command for btcjson and rpcclient, so one can issue these commands, but it does not actually expose the command externally, and I wouldn't call this complete without adding that functionality.

Are you talking about this line?

MustRegisterCmd("fundrawtransaction", (*FundRawTransactionCmd)(nil), flags)

That is necessary for the RPC client to call this method. You're right in that this is a client-side implementation of the RPC, not server-side. My use case is using the RPC client against a Bitcoin Core backend. If there's a better way of doing a client-only implementation I'm happy to change this, but I think this is the correct way of implementing a client-only RPC.

I was just referring to the fact that it was client only, and I guess more determining the scope of the PR, this is the correct way to implement client-only. Definitely put up an issue for server side because I think it's sort of a problem to have discrepancies in the supported commands for the client and server for too long.

@Rjected
Copy link
Collaborator

Rjected commented Jun 8, 2020

@torkelrogstad mind seeing if you can rebase to get the github actions to run?

@torkelrogstad
Copy link
Contributor Author

Rebased.

Copy link
Member

@jcvernaleo jcvernaleo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

@jcvernaleo jcvernaleo merged commit e4f5902 into btcsuite:master Jun 15, 2020
@torkelrogstad torkelrogstad deleted the 2020-03-18-fundrawtransaction branch June 16, 2020 07:22
@onyb onyb mentioned this pull request Jul 10, 2020
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

Successfully merging this pull request may close these issues.

3 participants