nishuzumi / collider Goto Github PK

./collider --base-fee 11 --funding-wallet xxx --miner cpu --primary-wallet xxx --ticker infinity

INFO Starting collider...
INFO Using mainnet
INFO Primary wallet address: xxx
INFO Funding wallet address: xxx
INFO Bitwork info:
Ft Into
Ticker: infinity
Max mints: 3333
Max supply: -1
Mint amount: 9999
Mint bitworkC current: 888888888.14
ERROR failed to parse response into JSON due to error decoding response body: invalid type: string "0d5exxxxxxxxxxxxxxxxxxbi0", expected unit at line 1 column 14680
ERROR failed to parse response into JSON due to error decoding response body: invalid type: string "0d5exxxxxxxxxxxxxxxxxxbi0", expected unit at line 1 column 14680
ERROR failed to parse response into JSON due to error decoding response body: invalid type: string "0d5exxxxxxxxxxxxxxxxxxbi0", expected unit at line 1 column 14680
ERROR failed to parse response into JSON due to error decoding response body: invalid type: string "0d5exxxxxxxxxxxxxxxxxxbi0", expected unit at line 1 column 14680
ERROR failed to parse response into JSON due to error decoding response body: invalid type: string "0d5exxxxxxxxxxxxxxxxxxbi0", expected unit at line 1 column 14680
thread 'main' panicked at src/main.rs:205:10:
wait until utxo error: ExceededMaximumRetries
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

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.

日志如下：
Commit mining: [00:10:45] Hash rate: 363.66M/s
INFO 🔍 Commit hex: 010000000001010b1820e8547b1a32010f069bbca9088207b621f86fc3b18edd2fa530864d24e100000000000000000002442c000000000000225120ec15264aab628b110ce0b93950b0842d298e27c702f49089e121ff8601aa0fb28a9100000000000022512031eb12727fd16b9c41d40270999ee74b12fdf7918052ec12865771d5af37cb090140582dfdf0bf66f95934f510e54d227dac3c85c7b81eb777048e67040772e5ffa1e29743938b3718648d777c013593ee4f11fede58edf547f12eaacf4dbac4223f00000000
ERROR the request to https://ep.nextdao.xyz/proxy/blockchain.transaction.broadcast failed due to error sending request for url (https://ep.nextdao.xyz/proxy/blockchain.transaction.broadcast?params=%5B%22010000000001010b1820e8547b1a32010f069bbca9088207b621f86fc3b18edd2fa530864d24e100000000000000000002442c000000000000225120ec15264aab628b110ce0b93950b0842d298e27c702f49089e121ff8601aa0fb28a9100000000000022512031eb12727fd16b9c41d40270999ee74b12fdf7918052ec12865771d5af37cb090140582dfdf0bf66f95934f510e54d227dac3c85c7b81eb777048e67040772e5ffa1e29743938b3718648d777c013593ee4f11fede58edf547f12eaacf4dbac4223f00000000%22%5D): error trying to connect: unexpected EOF
INFO 🔍🎺 Commit tx broadcasted successfully! 🚀 https://mempool.space/tx/a5bc74f171e737a1a211b81e27e930e04128219e55dc3cf3b67aa68ad34158cc
INFO 🔓 Reveal hex: 01000000000101cc5841d38aa67ab6f33cdc559e212841e030e9271eb811a2a137e771f174bca50000000000fdffffff010f27000000000000225120dc2f46c62768c6977b586825af2906ce8bf8c37f1312b54874330b2baad668660341c440dfcaac60c51d4e45ac339c44921bd4bbec88d02f5ecd25b61e3457e1b1473fcac18adabf7131aa408e4bcaa557ec9a554af411f98b38f4f28ebcff9bfa41834b20029179c6d6bc7a6bb362f050a26eec52a49924151e3fd784a43f406d6e32d23aac00630461746f6d03646d741ca16461726773a16b6d696e745f7469636b657268696e66696e6974796821c0029179c6d6bc7a6bb362f050a26eec52a49924151e3fd784a43f406d6e32d23a00000000
INFO 🔓🎺 Reveal tx broadcasted successfully! 🚀 https://mempool.space/tx/4c9a899d7b8fd5614eae3c994840ed8309b2a70796368d9dca20eeace368d370
INFO 🎉 Eureka! 💥 The Collider has successfully smashed the problem and computed the result! 🧪✨

Commit hex: 0100000000010163343fba9f5865b5962d9bdf41804c55ad6b474b30b39fc3d5943d665777017601000000008513a2bd02102e0000000000002251209b3f4ab0e4902bb5b9156f00f346a68688a5f8d7897c8f31d944d40cbf20707d1a05000000000000225120c8d05f4129b6ece5a23cf7817e26913398b9ae24eb3d081ca0b28436763b41970140a6090f17d8af6ad64be1c47418cf0ec7d6e672511140f6f5497fbd8fa2c8b4a0118f41144ae8b525a01009720461537cc1c5f46cc0f2f675cf829f858967fb1d00000000

ERROR the request to https://ep.atomicalmarket.com/proxy/blockchain.transaction.broadcast failed due to error sending request for url (https://ep.atomicalmarket.com/proxy/blockchain.transaction.broadcast?params=%5B%220100000000010163343fba9f5865b5962d9bdf41804c55ad6b474b30b39fc3d5943d665777017601000000008513a2bd02102e0000000000002251209b3f4ab0e4902bb5b9156f00f346a68688a5f8d7897c8f31d944d40cbf20707d1a05000000000000225120c8d05f4129b6ece5a23cf7817e26913398b9ae24eb3d081ca0b28436763b41970140a6090f17d8af6ad64be1c47418cf0ec7d6e672511140f6f5497fbd8fa2c8b4a0118f41144ae8b525a01009720461537cc1c5f46cc0f2f675cf829f858967fb1d00000000%22%5D): error trying to connect: tcp connect error: 由于目标计算机积极拒绝，无法连接。 (os error 10061)

error: 由于目标计算机积极拒绝，无法连接。 (os error 10061)
thread 'main' panicked at src\main.rs:266:10:
broadcast commit tx error: ExceededMaximumRetries
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

ERROR failed to parse response into JSON due to error decoding response body: invalid type: string "aabbcc7c57b8fdf3bcb9a876a56a9fd9d3a318ccfec6e3b98435c187e53f46adi0", expected unit at line 1 column 581

只要一运行，就报这个错误

先生您好，我是专注于web3岗位的猎头Adam，我这里有适合您的前端岗位。远程办公，工资发u。您感兴趣吗？

wx：Tiny4030