Need Help with Bitcoin Script Failures

4 replies 219 views
orbit_viperFull Member
Posts: 33 · Reputation: 286
#1Apr 20, 2021, 01:48 AM
So, I tried to mint some SATS tokens on the Bitcoin network using the Ordinals protocol and BRC20 standards, and I did it through some Go language software. I didn't change anything in the software, so it probably just sent the raw data as it is. My plan was to do 500 minting transactions without realizing there’s a limit of 25. Then I got hit with this error: "Send error, reveal send error, 25 transaction hashes could not be parsed, sendrawtransaction RPC error: {"code":-26,"message":"too-long-mempool-chain, too many descendants for tx 369a184f3e941a501b99a2865f6c1db09f39af379ef8c63fb52689e37e3376a7 [limit: 25]"}: maximum hash string length is 64 bytes." Because of this, only 25 out of my 500 transactions went through. The other 475 transactions didn’t use the sent ‎0.00002914 btc, and I never got the tokens I was trying to mint. Is there any way to deal with the Bitcoin scripts that didn’t do what they were supposed to do?
5 Reply Quote Share
ColdAlphaSenior Member
Posts: 242 · Reputation: 1420
#2Apr 20, 2021, 07:48 AM
When mining you need to be connected to a mining pool if I'm not mistaken.
6 Reply Quote Share
mark_whaleSenior Member
Posts: 238 · Reputation: 968
#3Apr 20, 2021, 02:03 PM
About a week ago, you asked a similar question and received a few answers, I don't know why you think posting the same question again is going to solve your problem if you didn't even engage in the other thread. Perhaps try getting help from the sat minting groups or channels, they may have much better knowledge and experience. How about executing the minting transactions in batches of 25 due to the limit? Have you tried that?
1 Reply Quote Share
gr3g.0rbitHero Member
Posts: 1025 · Reputation: 2646
#4Apr 20, 2021, 02:13 PM
This isn't about a failing script, it's just your input(s) already have 25 unconfirmed parent-children chain. The default limit is 25: https://github.com/bitcoin/bitcoin/blob/master/src/policy/policy.h#L62-L63 I suspect that the other part of the error ("maximum hash string length is 64 bytes.") is unintended since it's expecting a TXID.
1 Reply Quote Share
orbit_viperFull Member
Posts: 33 · Reputation: 286
#5Apr 20, 2021, 05:34 PM
Thanks so much for your help. I have one last question. I've been reading a lot for days and I'm so confused, I can't think logically. Do I need to enter witness information in this new transaction I am sending, or is it enough to just enter the scriptPubKey? If I need to be a witness, what do Item 1 and Item 3 represent in the example you gave? And finally, I would like to point out this: The script I use creates a new wallet for each new minting transaction. Do I need the private key of these wallets to resend unexecuted outputs from the main transaction as we discussed? Or is it enough to use my own wallet's private key which performs the main transaction with 500 outputs? And finally, as an example, can you show me how to generate the raw code for just one of these operations? Thank you very much for your support.
0 Reply Quote Share

Related topics