Post by arghzero

14aqJ2…oWGK Custodial · treechat

my bad had a math error with the fee calculation in that msg! should be a much more reasonable ~700k-ish sats if you try now.
(it wouldnt actually have charged that insane transaction fee btw, just had the wrong value in the pre-mint check 😅)

What the chain says
Block
931 415
Time
2026-01-11T10:40:31Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
arghzero

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Verified Custodial

Replies (5)

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Is this the first time it happend? Why did it do it lol its special now🥹🤣

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Is this the first time it happend? Why did it do it lol its special now🥹🤣

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

just one thing leading to another. originally we werent counting up all the bytes in the image that gets minted when we prepared a mint, which is what was causing your first try to fail because it was passing our balance check, but then there werne't quite enough funds to actually inscribe the whole image.
so to fix that i added some code to calculate how big the tx was going to end up before we actually try to broadcast, but i had a math error in that code, so it was coming back with the huge numbers you were getting. [[devlife]]

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Is it anything special lol

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Its still stuck on the spinning