-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing Txs #1055
Comments
I confirmed on my full node that only However, there is not enough information about the two failed transactions to determine why they did not relay or confirm. Have you checked your log If you don't see anything there, it'd be helpful to have the raw hex of these failed transactions to look for bugs |
also, what is that UI your screenshot is from ?! |
Hey, @gwumkt can you please send the |
[W:2022-05-13T20:16:47Z] (net) Received reject (78.231.131.6:8333): msg=tx code=duplicate reason=txn-mempool-conflict hash=ebc303757e0ef98d4370bd684dd3dba3714c09797ee634f9c4bd0f6597c7704b. [W:2022-05-13T20:16:47Z] (net) Received reject (34.211.65.11:8333): msg=tx code=nonstandard reason=scriptpubkey hash=ebc303757e0ef98d4370bd684dd3dba3714c09797ee634f9c4bd0f6597c7704b. |
@gwumkt is ebc30... a transaction you sent from this wallet? |
Yes.. |
Okay but its not one of three transactions you indicated. I think we need to know more about your configuration and how you creating these transactions with bcoin. |
exactly the same.. { passphrase: pass, outputs: [{ address, value: Math.floor(amount * 1e8) }], rate: 20000 } |
Something is wrong because your output script is nonstandard. I can't find ebc303757e0ef98d4370bd684dd3dba3714c09797ee634f9c4bd0f6597c7704b on my node or block explorer, can you retrieve it and paste it here either as raw hex or JSON? |
i can just do another one, it always happening.. |
output of optionally add |
returning null i made another one now:
|
Ok this transaction has a mempool conflict, meaning your wallet is double spending for some reason. I also notice it is quite huge, 111 inputs! Can you think of a reason why your wallet would be re-using coins it has already spent? |
i used the zap option because this issue started, and since then i used it more because now all my txs failing |
Ok, when you use "zap" you are clearing unconfirmed transactions from your wallet BUT YOU CAN NOT clear valid transactions you have already broadcast to the network. This means your wallet is now out of sync with the network. You have a few options:
|
mmmm why its related to the unconfirmed once? how can i find them and maybe boost them? because before the fee wasnt set at all so it just did with random i guess |
There is no "random" fee but there is a hard-coded minimum as well as a built in fee-estimator. Its possible your stuck transaction paid too low a fee for the current fee environment. You may still need to wait a few days for the stuck TX to either confirm or clear, this is the nature of Bitcoin. I'll see if I can figure out any other solutions for you in the meantime. |
Thanks! |
Hi there,
Im having an issue that after i send txs and get the hash, they dont show on blockchain..
For example, i sent 3 txs one after another. same "rate" and diff amounts.
The rate for those 3 was set to 20000.
0.05 - 01d2a315083ff887177bd1b43f0d0af20c0b125ca1021d0972fbdbdbcb929da4
0.1 - 7969ab478ed017dbaa3c5b2505fa610dd8021a4709398ce4e7ecc413816e27e8
0.005 - fdc0ae4c81e9bfb0bc6ec87ea745f5f63d9c517275edd8a62bb8b005c5ef089c
the only tx visable on blockchain is the last one, the 0.005.
Req:
{ passphrase: pass, outputs: [{ address, value: Math.floor(amount * 1e8) }], rate: 20000 }
Server info:
{ "version": "2.2.0", "network": "main", "chain": { "height": 736192, "tip": "0000000000000000000405c3eb4af4ca6361275baa347c35c8afb6bef09a9d4b", "progress": 1 }, "indexes": { "addr": { "enabled": false, "height": 0 }, "tx": { "enabled": false, "height": 0 }, "filter": { "enabled": false, "height": 0 } }, "pool": { "host": "0.0.0.0", "port": 8333, "agent": "/bcoin:2.2.0/", "services": "1000", "outbound": 8, "inbound": 0 }, "mempool": { "tx": 0, "size": 0, "orphans": 0 }, "time": { "uptime": 2849245, "system": 1652437898, "adjusted": 1652437898, "offset": 0 }, "memory": { "total": 612, "jsHeap": 24, "jsHeapTotal": 28, "nativeHeap": 584, "external": 5 } }
The text was updated successfully, but these errors were encountered: