Skip to content

update compute_additions_with_cost() to use run_puzzle() #16661

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

arvidn
Copy link
Contributor

@arvidn arvidn commented Oct 19, 2023

Purpose:

This should make it more accurate with regards to the cost of conditions and possibly a little bit faster. It will now assume that the hard fork has activated, for purposes of validating the puzzle+solution and computing the cost of conditions

Current Behavior:

new conditions like SOFTFORK and the unknown condition codes with cost (introduced with the hard fork) are not taken into account when computing the cost.

New Behavior:

The new conditions are taken into account (unconditionally) when computing the cost, as if the hard fork has activated.

…. This should make it more accurate with regards to the cost of conditions and possibly a little bit faster. It will now assume that the hard fork has activated, for purposes of validating the puzzle+solution and computing the cost of conditions
@arvidn arvidn requested a review from Quexington October 19, 2023 11:17
@arvidn arvidn added the Fixed Required label for PR that categorizes merge commit message as "Fixed" for changelog label Oct 19, 2023
@arvidn
Copy link
Contributor Author

arvidn commented Oct 19, 2023

it seems we have a lot of tests exercising this function with invalid puzzles, and still expect to get the created coins returned..

@arvidn arvidn mentioned this pull request Oct 19, 2023
@arvidn arvidn removed the request for review from Quexington October 20, 2023 08:17
@arvidn
Copy link
Contributor Author

arvidn commented Oct 20, 2023

the main challenge with this change is that we run unmatched offers to find their output coins, even though they are invalid. This change will just fail the whole puzzle rather than making a best-effort guess at what the output coins of a matched offer would be

Copy link
Contributor

github-actions bot commented Dec 4, 2023

This PR has been flagged as stale due to no activity for over 60 days. It will not be automatically closed, but it has been given a stale-pr label and should be manually reviewed by the relevant parties.

@github-actions github-actions bot added the stale-pr Flagged as stale and in need of manual review label Dec 4, 2023
@github-actions github-actions bot added the merge_conflict Branch has conflicts that prevent merge to main label Dec 12, 2023
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

1 similar comment
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot removed the stale-pr Flagged as stale and in need of manual review label Dec 13, 2023
Copy link
Contributor

This PR has been flagged as stale due to no activity for over 60 days. It will not be automatically closed, but it has been given a stale-pr label and should be manually reviewed by the relevant parties.

@github-actions github-actions bot added the stale-pr Flagged as stale and in need of manual review label Jan 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed Required label for PR that categorizes merge commit message as "Fixed" for changelog merge_conflict Branch has conflicts that prevent merge to main stale-pr Flagged as stale and in need of manual review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant