Very high deadlines?
-
@piezo Don't use the uray miner original code - use the slightly improved uray's miner code by dpreyl:
https://forums.burst-team.us/topic/113/uray-s-c-crossplatform-miner-64bit-ultra-low-ram-usage/2
-
@daWallet said:
@piezo Don't use the uray miner original code - use the slightly improved uray's miner code by dpreyl:
https://forums.burst-team.us/topic/113/uray-s-c-crossplatform-miner-64bit-ultra-low-ram-usage/2I use a 32bit machine for mining. So i download and compile dpreyl's modification (https://github.com/dpreyl/burst-miner/) like mentioned in your link. And this is exactly the version i got problems with and this topic is about.
Even if i put "submissionMaxDeadline" : 3888000, in my config file i get the same problem. :/
-
@piezo - I see you are still successfully mining and have increased your total mined from the initial 2 coins to 30 now. Are you still trying to switch mining packages due to the output of poc-miner not being desirable?
-IceBurst
-
This post is deleted!
-
@IceBurst said:
@piezo - I see you are still successfully mining and have increased your total mined from the initial 2 coins to 30 now. Are you still trying to switch mining packages due to the output of poc-miner not being desirable?
-IceBurst
This 30coins i mined with the modified poc-pool-miner.
@haitch said:
@piezo The reason you get the Really Bad message is that the POC miner ignores the pools minimum deadline request. And send in the ones it find, each incrementally better than the last. However you initial submit will be in the ten to thousands of years, and then they start getting better.
The Error message i got with the burst-miner (https://github.com/dpreyl/burst-miner/), not the poc-miner.
As i understand it, the tool reads all plots and looks for the best deadlines.
block#248164 s#:1187 bt:3020213 a6ddc9b0f1c37e05626ce59c9269ca2abeda99670b1006f6d004fc7cd12f237d MVSE-LLUM-6NW4-7JMXZ dl:15168 days 03:43:03 n:0 MVSE-LLUM-6NW4-7JMXZ dl:44490 days 10:30:14 n:1 MVSE-LLUM-6NW4-7JMXZ dl:40503 days 15:57:33 n:6 MVSE-LLUM-6NW4-7JMXZ dl:41878 days 13:42:15 n:20 MVSE-LLUM-6NW4-7JMXZ dl:3548 days 23:35:30 n:38 MVSE-LLUM-6NW4-7JMXZ dl:28676 days 12:19:32 n:50 MVSE-LLUM-6NW4-7JMXZ dl:17530 days 03:11:00 n:54 MVSE-LLUM-6NW4-7JMXZ dl:43381 days 09:27:30 n:364 MVSE-LLUM-6NW4-7JMXZ dl:14171 days 06:11:39 n:389 MVSE-LLUM-6NW4-7JMXZ dl:19080 days 07:47:35 n:712 MVSE-LLUM-6NW4-7JMXZ dl:37453 days 20:59:00 n:1210 MVSE-LLUM-6NW4-7JMXZ dl:14397 days 07:13:32 n:1682 MVSE-LLUM-6NW4-7JMXZ dl:3081 days 13:28:03 n:12701 MVSE-LLUM-6NW4-7JMXZ dl:335 days 23:42:48 n:511091 MVSE-LLUM-6NW4-7JMXZ dl:175 days 13:17:10 n:399431 plot read done. 6914838061871918860_0_500000_20000 = 520000 nonces MVSE-LLUM-6NW4-7JMXZ dl:64 days 02:03:08 n:1462486 MVSE-LLUM-6NW4-7JMXZ dl:57 days 04:11:53 n:3217375 MVSE-LLUM-6NW4-7JMXZ dl:28 days 05:43:51 n:3664966 plot read done. 6914838061871918860_500000_3800000_20000 = 3820000 nonces submitting nonce 3664966 for MVSE-LLUM-6NW4-7JMXZThan it looks for the best nonce (in this example nonce 3664966 with a deadline of 28 days 05:43:51.
Than it submitt this nonce with a deadline of ~28days and get the answer from the server that the deadline is x-thounsend of years.{"errorCode":1007,"errorDescription":"The deadline for your nonce is REALLY BAD: 180390 years, 2 months, 28 days, 3 hours, 25 mins, 50 secs - wrong block? are your plot files corrupted?"}And i don´t know why. :/
-
Sry for spamming, but now i figured out some interesting information.
If let mine my plots by the two different tools (1. burst-miner / 2. midified poc-pool-miner) on the same block, i get different results in:
1: Which nonce has the lowest deadline
2: How high is this deadlineIs this normal? I would assume that the result should be the same? Maybe the burst-miner do some wrong calculations and thats why the deadline from the pool and the burst-miner are so different. Is this possible?
-
@piezo That is a problem. Your deadlines are determined by two things.
- Your plot generated by your system which is seeded with your numeric ID
- The scoop provided by the pool server for pulling from your plot
If you are getting different deadlines from different miners the possibilities are:
- One miner is working on stale data (meaning an older scoop)
- One miner is busted in it's ability to mine
- The miners are on different networks (DEV VS Prod)
Hope this helps,
-IceBurst
-
Thanks for the answere, but iam still a bit confused as iam new to all of this. :)
So this means, that burst-miner (https://github.com/dpreyl/burst-miner/) is not campatible with the pool http://pool.burst-team.us:80 in general because of the different scoop?
Or could it be may compatible if i use another plotter? (i used dcct-cpu-plotter for my plots)?
-
@piezo Did you compare the miners on same block/round? If yes, at least the best deadline should be the same. Additional deadlines may vary, depending on miner plotfile read strategy/order.
-
@luxe said:
@piezo Did you compare the miners on same block/round? If yes, at least the best deadline should be the same. Additional deadlines may vary, depending on miner plotfile read strategy/order.
Yes, i compare the miners on same round/block. And no, unfortunately the best deadline differs with both miners. :/