-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
Lucid txs fail due to underestimated budget? #109
Comments
Hey thanks for reporting this. If you catch another such tx send the cbor hex in here. Would be awesome🙏 It's also possible that you were just lucky and one tx indeed overspent the budget, because more UTxOs and tokens were involved in the tx. And the next one where you set |
We've experienced the same issue on multiple occasions with scripts that were passing easily before. cbor hex:
and likewise with |
Some more info that I forgot to mention. These txs are tried on the preview testnet. There are some txs that fail and when I try again succeed, and there are others that fail consistently (however they all succeed consistently when
|
Here's another failure of a very small transaction with the same outcomes:
Same results experienced on both Preview and Preprod |
I also tried checking the difference between the native uplc ex units and the blockfrost evaluate tx endpoint for
using
and got
|
@eddiemundo this was found and fixed in aiken-lang/aiken#89 We've made a new release for Aiken and Lucid just needs to release an update now. |
I am still experiencing the issue on the version 0.7.9. Has this ever been resolved?
// preprod network
const tx = await lucid
.newTx()
.collectFrom([utxo], redeemer)
.attachSpendingValidator(v) // PlutusV2
.payToContract(a, { inline: datum }, utxo.assets) // assets are just lovelace
.addSignerKey(address.paymentCredential.hash)
.complete() Interestingly enough using the as a temporary workaround I just did (:laughing:): priceMem: parseFloat(result.price_mem) * 2,
priceStep: parseFloat(result.price_step) * 2, |
Im experiencing this error with version 0.10.7.... Is there any other workaround besides modifying the packages-source or using nativeUplc: false?
|
Where you able to resolve
|
After upgrading from 0.6.2 to 0.6.9 when submitting certain txs I get
when I set
txPartial.complete({ nativeUplc: false })
then the tx works again.The cbor of a
tx
intx.submit()
that triggers this isThe text was updated successfully, but these errors were encountered: