[TESTNET BUG] Mining running but stops paying BTC #1797
Comments
paradigma-cl
added
bug
|
@paradigma-cl the thread that usually runs the miner You still have 1 spendable UTXO (1_732_500 sats), but the rest, about 0.2 BTC (20_000_000 sats) of what you have is no longer usable (related to #1783) |
|
@psq Here is the last log of thread(6) Append block 7d0d68c7288d18b7757baec34e7d9f5203942c2d48b08b85e9325e8d48ef0d20/3a660d505dee0e5b1fe1ad24c57e9dbe079fff2318a119dbaad1c817cca21628 off of 03c1be49989fabfbb2a959a9e01b2c2111d96ed5d7eb23313aff207f9a3e5fd7/61701a0e21e5c84cfd9b33bd140ab630f962fc7411a889b85fb55372f609a465 DEBUG [1596603701.033] [src/chainstate/stacks/db/transactions.rs:728] [ThreadId(6)] Process transaction 02dbc23fcc9ccf8bfa16fce1627f896e277cc52e1d20ade975cdc2ae4a38e96b (Coinbase) |
|
Thank you for the additional log @paradigma-cl, nothing strange seems to have happened to thread 6, and thread 1 also stopped processing anything. Looks like the root cause may be that Argon just stopped answering: and later on we see a number of in the original log, one about every 90s |
|
This may have been caused by this weekend's testnet outage. Does the problem persist? |
|
|
|
@psq Probably it is that, but I think that the equivalent of USD 1200 still is "some" money. So how to prevent that the expenditure gets transformed to smoke? Originally started with 0.5 BTC and goes down to 20% of that value. Is that how it works in general in the bitcoin mining? |
|
@paradigma-cl agreed, and that's fixable, and will get addressed one way or an other. There are some thoughts at #1783 and preferably implementing #1615 would also take care of it. |
|
This may a dup of #1783. The bitcoin node used by Argon just isn't that fast -- it takes a long time for it to reply all of the UTXOs to your miner node if you have used the same key to mine blocks for a long time. I get a timeout when I run |
|
@jcnelson as a temporary fix, we could set the amount used in the key registration to 11_000 (I think that's the amount used for commits, or whatever that amount is) and change Happy to create a PR for this if you think this could work. in the case of #1783, it was not timing out, just taking enough time to skip a block. If there's 0.1 BTC left, these would mean @paradigma-cl mined over 1_800 blocks and no UTXO is greater than 5_500. |
|
@paradigma-cl thank you for the submission 👍 |
|
@paradigma-cl |
|
@paradigma-cl any update on if this issue is reproducible? |
|
@paradigma-cl once this PR (#1848) is live on Krypton, this problem should disappear |
Describe the bug
Detected that the BTC balance has stopped decreasing at the value {"balance":0.22142} for address /btc/n3WmGv1fgjt8eMcCJuV21QNqgjTHnP9DBo . It has stayed in that value for several hours. The mining node looks like normal execution.
Steps To Reproduce
Running the mining node
Expected behavior
The BTC balance should continue to decrease as it have been several days.
Environment
stacks-node versionstacks-node 0.1.0 => 23.0.0.0 (master:afc748aa1, release build, linux [x86_64])Additional context
Please include any relevant stack traces, error messages and logs.
If you are encountering an issue with a smart contract, please include the smart contract code
that demonstrates the issue.
If you think this is eligible for a bug bounty, please check the relevant boxes below:
Critical, Launch Blocking Bugs
Consensus critical bugs
State corruption
Stolen funds
contract-call?Take control and/or bring network to a halt
Major, Launch Blocking Bugs
Major bugs
Minor, Non-launch blocking bugs
Minor bugs
logs_last10k.log.gz
The text was updated successfully, but these errors were encountered: