Skip to content

Update the Mecenas example to cover contract bug #291

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

Open
mr-zwets opened this issue Mar 6, 2025 · 1 comment
Open

Update the Mecenas example to cover contract bug #291

mr-zwets opened this issue Mar 6, 2025 · 1 comment
Labels
documentation Relates to documentation tests Related to automated tests

Comments

@mr-zwets
Copy link
Member

mr-zwets commented Mar 6, 2025

The Mecenas contract allows for multiple contract inputs but this can lead to behavior as pointed out in telegram, we should update the examples & docs, and also the the Mecenas contract used in the automated tests

@mr-zwets mr-zwets added documentation Relates to documentation tests Related to automated tests labels Mar 6, 2025
@mr-zwets
Copy link
Member Author

mr-zwets commented May 4, 2025

further the mecenas contract has the actual relative timelock logic commented out

@kiok46 noticed it would best to restore this now that we have working tests for MockNet with local evaluation.
However, this raises a further question: how in the scenario can the UTXO age be set as to make succeeding and failing tests for relative locktime checks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Relates to documentation tests Related to automated tests
Projects
None yet
Development

No branches or pull requests

1 participant