Closed nemo83 closed 1 year ago
inputIndex: -1
is definitely wrong. I'll investigate how that is possible
inputIndex: -1
is definitely wrong. I'll investigate how that is possible
Hey, any luck in finding the issue? I would really love to stick w/ helios in both onchain and offchain. Can I be of more help? Do you need more logs or examples?
I'll take a look at this as well
Issues has been identified and PR has been created for the fix. https://github.com/Hyperion-BT/helios/pull/77
Started to see:
error Error: submit tx failed: Error: 400:
0: {"provided":"4e0229f61667e1b96f9e25dd799c3d809c2180998b92581c94e74736caba7d0d","inferredFromParameters":"2d892ef1e40b2fa91912608158aa3fc57a5ebbcd75bb4387c7141ffb4ceb0319"}
Is this possibly related to the fix @lley154 ?
Very interesting error @nemo83, never seen that before. Is that from submitting the tx with a wallet or with an API like blockfrost
This is fixed, but unfortunately I have something new. Opening new ticket
I've recently update to helios 0.13.16 and implemented ref input (that doesn't seem to be related).
The code is a nft raffle systems and after 7 tickets being correctly sold, now many users (me included) are seeing the error
no datum data available
You shoudl be able to reproduce the error by attempting to buy a ticket on mainnet. https://www.easy1staking.com/nft-raffles# No need to actually sign the Tx, just press buy but never sign.
Here the tx json before calling finalise that eventually raises the error: