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

Potential unintended consequences for ref script fees #4594

Open
twwu123 opened this issue Sep 3, 2024 · 1 comment
Open

Potential unintended consequences for ref script fees #4594

twwu123 opened this issue Sep 3, 2024 · 1 comment

Comments

@twwu123
Copy link

twwu123 commented Sep 3, 2024

Transaction fees are being charged for inputs with reference scripts, despite the script not actually being used, and the transaction having no redeemers. It's possible that it is intentional as it creates more work for nodes regardless of whether the reference scripts are used or not. However, from my testing, I don't think any wallets accounts for this.

This means that, it is currently completely possible to ruin someone's day by sending them a lot of random utxos containing ada of different sizes (to maximize the chance they get selected for), and attach some reference scripts to these utxos. This could essentially lock up their funds until the wallets push out a fix.

@vsubhuman
Copy link

vsubhuman commented Sep 3, 2024

Main unclear issue is why a tx is being charged for a non-plutus input having a ref script in it when NO Plutus execution and L2 is involved? It's a regular transaction with only vkey witnesses. In this case the node technically does not even need to care whether a regular input has any script in it or not, because it is completely irrelevant to the transaction execution.

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

No branches or pull requests

2 participants