Err double spend chia

[help]DOUBLE_SPEND？ #4281

Comments

Eden0628 commented May 9, 2021

2021-05-08T17:55:26.219 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id 70cd3dc04739a6584b63bee0c8c0b64f78e56c79d894441a1ce121f80294e65b, status 3 error: Err.DOUBLE_SPEND
2021-05-08T17:55:26.221 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id d092c8e48315872fbc3c0401204001927a089e5f3049afde2e824e6264630eb4, status 3 error: Err.DOUBLE_SPEND
2021-05-08T17:55:26.223 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id 9b1803a8c7586a5778da1d6a1eb01adf304e7f32077eed162210d08b6fff98d3, status 3 error: Err.DOUBLE_SPEND
2021-05-08T17:55:26.225 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id 6861fb69c330afa470fd901967c5e6d1c09d3861147999b13d9d4dbed6852183, status 3 error: Err.DOUBLE_SPEND
2021-05-08T17:55:26.227 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id 1609dc42ac010697f6fed6f44194fbbc39e0ab2e07f4c5f4f1f97d1d4e585c4f, status 3 error: Err.DOUBLE_SPEND
2021-05-08T17:55:26.229 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id 9a3f77456fec51fce16b217a118ae185f6382e15958cf839511a8262fa8fc20f, status 3 error: Err.DOUBLE_SPEND
2021-05-08T17:55:31.873 full_node chia.rpc.rpc_server : WARNING Error while handling message: Traceback (most recent call last):
File «chia\rpc\rpc_server.py», line 212, in safe_handle
File «chia\rpc\rpc_server.py», line 200, in ws_api
File «chia\rpc\rpc_server.py», line 161, in open_connection
ValueError: Start client failed, or server is not set

The text was updated successfully, but these errors were encountered:

Muffexx commented May 10, 2021

please consider searching before creating new issues.
There are several issues regarding this topic e.g. #4164 #3917 #3696

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Farming with no result: status 3 error: Err.DOUBLE_SPEND #6175

Comments

Aerya commented May 28, 2021

Using chia-blockchain-gui 1.4.6 on Windows10. No firewall. Full node and harvester reported as connected.
I read others issues about this kind of error but i’m afraid i don’t farm anything from the beginning, even using the last rlz.

I’ve got 45 plots farming for a few weeks now and still no proof. In the DEBUG log I can see such errors:

The text was updated successfully, but these errors were encountered:

BonTron1 commented May 28, 2021

This has already been answered by the developers:

» I will explain why DOUBLE_SPEND is printed. Let’s say you have transactions A, B and C in the mempool. The mempool is where you keep transactions that people send, but have not been included in a block yet.
Let’s say you then get a new block, which includes transactions B and C. What do we do with the mempool? We create a new mempool, and try to add all transactions to it. When we add tx A, it validates with no problem. However when we try to add transactions B and C, they are no longer valid because they are trying to spend coins which have already been spent. Those transactions are conflicting with the same transactions that just got included. So that is how we clear the mempool from old transactions.
There are some differences with chia and other coins, because any 2 transactions can be combined. It’s possible that the block did not include B and C, but it included another transaction X, which is a combination of multiple transactions (BCD) for example. So in this case, transaction B was never included on chain, but a conflicting transaction was. So B is now considered a «double spend» and is no longer valid. So this is how we filter out things from the mempool when we get a new block: we just try adding them all again one by one.
We can remove these warnings so there is less confusion
«

Don’t count on a proof any time soon, the GUI states 2 years which could actually be 2-6 years in reality.

Post of pic of the connections under your «Full Node» tab, that can show more about your connection.

Aerya commented May 28, 2021

Thank you. As I said I already read this answer. I didn’t understand XCH=1 proof found. Moreover, I knew I wouldn’t get many XCH but I must admit it’s totally useless to farm less than 2-400 plots.

Источник

Wasn’t able to add transaction with id status 3 error: Err.DOUBLE_SPEND[help] #3917

Comments

exzver commented May 6, 2021

Please tell me, what is that? Version 1.1.4.

The text was updated successfully, but these errors were encountered:

MOVZX commented May 6, 2021

Your Internet is too slow to compete with another farmers.

exzver commented May 6, 2021

My internet is 300 mb/s, in all other programs everything is ok

iLexGit commented May 6, 2021

This has already been answered by the developers:

«MEMPOOL_NOT_INITIALIZED happens when you are just starting up your node. If you are still seeing this, restart the node.
I will explain why DOUBLE_SPEND is printed. Let’s say you have transactions A, B and C in the mempool. The mempool is where you keep transactions that people send, but have not been included in a block yet.
Let’s say you then get a new block, which includes transactions B and C. What do we do with the mempool? We create a new mempool, and try to add all transactions to it. When we add tx A, it validates with no problem. However when we try to add transactions B and C, they are no longer valid because they are trying to spend coins which have already been spent. Those transactions are conflicting with the same transactions that just got included. So that is how we clear the mempool from old transactions.
There are some differences with chia and other coins, because any 2 transactions can be combined. It’s possible that the block did not include B and C, but it included another transaction X, which is a combination of multiple transactions (BCD) for example. So in this case, transaction B was never included on chain, but a conflicting transaction was. So B is now considered a «double spend» and is no longer valid. So this is how we filter out things from the mempool when we get a new block: we just try adding them all again one by one.
We can remove these warnings so there is less confusion
«

Источник

[BUG] DOUBLE_SPEND error in Log #3773

Comments

InB4DevOps commented May 5, 2021

Describe the bug
The logfile contains these error messages:

To Reproduce

Install 1.1.4
let it farm for a few minutes
cat ./debug.log | grep ‘err’

Expected behavior
no error

Desktop:

• OS: Xubuntu 20.04
• CPU: Intel i5

The text was updated successfully, but these errors were encountered:

temicus commented May 5, 2021 •

Getting also very often UNKNOWN_UNSPENT or DOUBLE_SPEND
update to 1.1.4 has not fixed the issue

temicus commented May 5, 2021 •

I have just checked again — its really critical — as far as I can see this error (DOUBLE_SPEND) comes nearly every time by challenge attempt when my plots pass the filter :(((. so I suppose with this bug its not possible to win

MOVZX commented May 5, 2021

With this bug it’s impossible to win the block, so we’re doomed.

temicus commented May 5, 2021

mariano54 commented May 5, 2021

It’s not an issue. Transactions are being resubmitted sometimes. just ignore it.

ResulEkin commented May 6, 2021

It’s not an issue. Transactions are being resubmitted sometimes. just ignore it.

I afraid that; I think I am farming and wait but may be my farming does not work correctly. Also today I updated 1.1.4

InB4DevOps commented May 6, 2021 •

It’s not an issue. Transactions are being resubmitted sometimes. just ignore it.

I afraid that; I think I am farming and wait but may be my farming does not work correctly. Also today I updated 1.1.4

How do you know that your farming does not work correctly? 51 plots is really not much. It’ll take quite some time to win a block with those 51 plots — if ever.

search your log for ‘eligible’ and post results..

ResulEkin commented May 6, 2021

It’s not an issue. Transactions are being resubmitted sometimes. just ignore it.

I afraid that; I think I am farming and wait but may be my farming does not work correctly. Also today I updated 1.1.4
What can I do?

How do you know that your farming does not work correctly? 51 plots is really not much. It’ll take quite some time to win a block with those 51 plots — if ever.

search your log for ‘eligible’ and post results..

Firstly thank you for fast answer for my problem. I deleted current log and waiting now creating new log file for checking.

So you mean I can ignore this error and continue to plotting and farming.
I just need to know. Everything is ok on my full node.

Источник

[BUG] full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id #3696

Comments

Djomla003 commented May 4, 2021

beeing spamed in the debug.log file of chia with following output:

Based on the GUI everything is synced and working.

Does this BUG impact the block wins / chia wins?

The text was updated successfully, but these errors were encountered:

temicus commented May 4, 2021

Hey I have similar error:
2021-05-04T09:44:04.055 full_node full_node_server : WARNING Cannot write to closing transport XX 2021-05-04T09:50:40.660 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id XXXX, status 3 error: Err.DOUBLE_SPEND

hexslav commented May 4, 2021

Hello, next similar one, started popping out for me today

2021-05-04T11:05:21.327 full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id XXX, status 3 error: Err.MEMPOOL_NOT_INITIALIZED

Everything in GUI looks fine.
Cheers, have a good day!

ricki008 commented May 4, 2021

Somebody know the answer yet?? I’m having the same problem 🙁

LamichhaneKamal commented May 4, 2021

temicus commented May 5, 2021

still have it even after updating to 1.1.4

• this one now:
  UNKNOWN_UNSPENT and DOUBLE_SPEND

djdookie commented May 5, 2021 •

Same here, seeing this error in debug.log several times per minute. I think I get this error since v1.1.3 under Ubuntu.

SKYBILLS commented May 5, 2021

In Windows Gui also have same problems . Please Fixed it

iLexGit commented May 5, 2021

This is happening to me now that i have updated to 1.1.4, it didn’t happen before. IT HAPPENS EVERY TIME SOME OF MY BLOCKS PASS THE FILTER. EVERY. SINGLE. TIME.

zewort commented May 5, 2021

full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id XXXXXXXXXXX, status 3 error: Err.DOUBLE_SPEND

iLexGit commented May 5, 2021 •

Always «status error 3» followed by one of these two:

• UNKNOWN_UNSPENT
• DOUBLE_SPEND
• MEMPOOL_NOT_INITIALIZED

Also, to the dev that answers this, appart from saying this is going to be fixed or if it is a bug at all (maybe the 1.1.4 logging is more verbose). EXPLAIN WHY this happens or WHAT it is. If the community understands better how your network works and what casues the issues we will be here asking recurrent questions MUCH LESS. It is in everyone’s best interest. Just consider it.

Muffexx commented May 5, 2021 •

Sporadic Err.DOUBLE_SPEND might not be an issue.
Check #3773

Edit: I should have been more precise.

iLexGit commented May 5, 2021

Yeah mariano said this happens cause » Transactions are being resubmitted sometimes» but this is not sometimes. this is absolutely everytime I receive an uncompleted block . My log is absolutely full of lines like this. Also, why is this happening, how can this be solved and what has changed in 1.1.4 that makes this happen.

IDK but i feel like we should have a lot more information about how the network works, what it uses, etc

Muffexx commented May 5, 2021

I’m also having the same issue (Err.DOUBLE_SPEND) multiple times per minute.

hobbit6 commented May 5, 2021

I’m having this issue too, every few minutes I get Err.DOUBLE_SPEND

meaverick commented May 6, 2021 •

full_node chia.full_node.full_node: WARNING Wasn’t able to add transaction with id ### status 3 error: Err.DOUBLE_SPEND
version 1.1.4
windows 10

Cheshyr commented May 6, 2021 •

Ubuntu 20.04. Same issue. Was not present on 1.1.2, but took over my logs in 1.1.4. I assume the 1.1.2 errors were a misconfigured timelord, but not sure what the new stuff is.

Источник