You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: