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

view: expose source control in TransactionPlanner RPC #3002

Merged
merged 1 commit into from
Sep 11, 2023

Conversation

hdevalence
Copy link
Member

The transaction planner allows controlling the source of spent funds, but we didn't expose this to the TransactionPlanner RPC. This commit adds a new field to the protos that threads this parameter through.

@hdevalence
Copy link
Member Author

@conorsch would it be possible to merge this and deploy it as 0.60.1? It doesn't affect consensus at all, it's purely client-side.

The transaction planner allows controlling the source of spent funds, but we
didn't expose this to the `TransactionPlanner` RPC. This commit adds a new
field to the protos that threads this parameter through.
@hdevalence hdevalence force-pushed the planner-rpc-source-control branch from 6910092 to bc76de2 Compare September 11, 2023 20:23
@hdevalence hdevalence temporarily deployed to smoke-test September 11, 2023 20:23 — with GitHub Actions Inactive
@hdevalence hdevalence merged commit f882728 into main Sep 11, 2023
8 checks passed
@hdevalence hdevalence deleted the planner-rpc-source-control branch September 11, 2023 21:58
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.

1 participant