nishuzumi
Transaction Not Sending to Mempool
I'm encountering an issue where everything seems to function correctly with the GPU miner executing the bitwork, but when it comes to sending the transaction to the mempool, it fails to send. The transaction does not appear in the mempool as expected. I've attempted several troubleshooting steps without success, and I'm seeking assistance to resolve this issue.
Steps to Reproduce:
Start the GPU miner. Execute bitwork to process transactions. Attempt to send the transaction to the mempool. Expected Result: The transaction should be sent to and appear in the mempool without issues.
Actual Result: The transaction does not send to the mempool, nor does it appear within it.
Changed the RPC link to see if it would resolve the issue, but there was no change. Tried introducing the API key of the funding wallet in both WIF and HEX formats, neither of which resolved the issue.
This is a relatively common problem, and in the future there may be a multiple detection feature, but it is not done at the moment. You can open https://mempool.space/tx/push, then copy the content of the Commit Hex or Reveal Hex (depending on what transaction you have not been sent successfully), manually paste it into the push function of the mempool, and then push.
If your commit hex was not pushed successfully, you need to push both the commit hex and the reveal hex.
@lin1023 可以复制文字给我一下吗 谢谢
Reveal hex: 01000000000101269904823d989802fe619f2dacdf7638701069381b859c83cd7bbe8e888888880000000000fdffffff010f27000000000000225120fcf968cab58e8e8a2dd93c2c2d6d63aca0cd5806d99c5b8bdc33e23bbb281df203412883adc065eb9d3a10ddd57e2f197abe68ddcd928a6f442a374ada43533e68e4c03c8a12b04bfa3d1815edabc5d1e20968cf78430908685a855f482e1a5ef5a38376209499d904632d28bbbb98bcab64df12d2fc68b14f85ed389ca918064ff2111563ac00630461746f6d03646d7447a16461726773a468626974776f726b636c3838383838383838382e31346b6d696e745f7469636b657268696e66696e697479656e6f6e63651a00527a656474696d651a6602a6cd6821c09499d904632d28bbbb98bcab64df12d2fc68b14f85ed389ca918064ff211156300000000
Commit hex: 01000000000101f22e70658f22cc8bfcda9e0b9aada6a0cedb1c0690e1e48a4d750b2e3d6f3d9800000000008f8bfd1601762f000000000000225120a5cd969fe1d7e934ff0db0b5795ef768423b064e14da24f94e915766b980327201408f412687c3f3277767e9a8845ad9c42f8372a5feb18d8f91b8f32195b28eb9b56d987e065de53ecd33a0f1b082105b858952431b6437cba317a58cea7587d7a300000000
@lin1023 应该是utxo获取有点错误...不推荐使用任何铭文资产钱包和atom钱包作为funding wallet,抱歉之前忘记在readme中写这条了 ,目前已经更新了程序并且添加了readme
@Brunvelop @lin1023 create a telegram group https://t.me/collider_atomicals, let talk in there
I've managed to find a solution to the issue!
In my case, the problem was that my funding wallet contained UTXOs that were smaller than the minimum size required for mining, which rendered the transaction invalid. After consolidating these UTXOs into a single, larger UTXO, sending the transaction to the mempool went through without any issues.
I'm quite new to Rust, so I'm not confident enough to submit a PR with a fix, but I imagine it should be a straightforward fix. Perhaps something like ensuring that the UTXO used for mining is of sufficient size to mine the token or similar.
I've managed to find a solution to the issue!
In my case, the problem was that my funding wallet contained UTXOs that were smaller than the minimum size required for mining, which rendered the transaction invalid. After consolidating these UTXOs into a single, larger UTXO, sending the transaction to the mempool went through without any issues.
I'm quite new to Rust, so I'm not confident enough to submit a PR with a fix, but I imagine it should be a straightforward fix. Perhaps something like ensuring that the UTXO used for mining is of sufficient size to mine the token or similar.
feel free to submit pr, if there are problems I will help you to improve the code!