-
Notifications
You must be signed in to change notification settings - Fork 23
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
[BUG] - Transaction intentionally submitted with invalid Plutus script is never removed from mempool #973
Labels
bug
Something isn't working
Comments
@mkoura thank you for the info! In step two, you submit the transaction to a node. Is that node itself a block-producing node in this setup? |
@nfrisby The node I submitted the tx to is not a block-producing node. |
A first step could be to investigate whether the other nodes are rejecting this transaction, and if so find out why (by inspecting the nodes logs). |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Internal/External
Internal
Summary
In Babbage era, when building a Tx with invalid Plutus script and passing
--script-invalid
, the transaction submit succeeds and the Tx is placed in mempool. However the Tx is never removed from mempool.Steps to reproduce
Steps to reproduce the behavior:
No error is raised, transaction is accepted by node.
Expected behavior
A transaction is removed from mempool and included in a block, the collateral input is spent.
System info (please complete the following information):
Additional context
invalid_script_issue.tar.gz
The text was updated successfully, but these errors were encountered: