Just wanted to let you know my miners have been going without issue since 1.4.4.1 upgrade, will keep an eye for when my ABN gets eaten and if the miner has any issue re-connecting to the pool once ABN weight is re-established.
Thanks, that sounds promising. Guess what, a PC found a block and all three miners continued onward with no ABN issues! Nice! (I also see a huge surge in pool blocks solved: 35 in only 12 hours - maybe this is what was missing). Now we need more Christians to find out about the wallet. I'm thinking about making a one page startup guide like someone here suggested a couple weeks ago. (To get started with a CPK & POG). We should also look into turnkey mining; maybe a pool option that charges a higher percentage but fronts the ABN weight for the miner would be good. (It might be a pretty high percentage, like 20% pool fees for no-abn, and 0-1% for with-abn, etc). I really like the idea of a pool with no/low abn requirements. This would allow for the adoption of the project by the small christian miners. Again though you would run into the issue of bots hammering the pool, so perhaps abn requirement in the pool is setup to the value of the faucet on the pool. This way you can eliminate the bots while achieving the goal of larger adoption. The higher percentage fee of 20% works fine in my mind and simply have a flag that can be set on the miner to indicate no-abn or use-abn. Just my 2 cents. Who would supply the ABN for the non-abn miners? Could this be a potential setup to "stake" for "interest" aka fees from the little miners? Some people just hodl and don't want to mine. So far the only idea I have is potentially dropping an extra 200K in the pool (from my pocket) and adding a checkbox to the user settings (if they want to be a funded miner or not) , and if these miners on training wheels solve too many blocks Id have to drop more in the pool to keep up, etc. But I have to think about this all the way through to ensure its technically feasible, because it requires us to change the client to support full block emission to be shot from the pool into the miner and back to the pool etc. I dont know about the interest; except that I know we cant lend crypto or they will steal it  . We have to lend the ABN transaction out to N miners at once etc. Funding it yourself to start off isnt' a bad idea, but why not opening up everybody to have the ability to make a GSC and fund it using their own like POGing, but without giving anything other than ABN. Fees can be collected and distributed appropriately to those offering ABN Wait, do you mean make it so "funded miners" (lets call them Funded Miners when they check the funded miners checkbox because they cant afford the ABN weight yet, or we can call them newbies), so funded miners will borrow an existing miners ABN, and if the pool receives a solution from a funded miner, we debit their block by 20% and reward it to the rest of the pool that has valid abns and who are mining? Thats not a bad idea, because the rich miners could then make more rewards and the poor miners could still mine. Maybe we make it automatic, so we share ABNs, but those who keep supplying a valid non-spent ABN make the block + bonus, those with no ABN get a block - debit. |
|
|
|
Just wanted to let you know my miners have been going without issue since 1.4.4.1 upgrade, will keep an eye for when my ABN gets eaten and if the miner has any issue re-connecting to the pool once ABN weight is re-established.
Thanks, that sounds promising. Guess what, a PC found a block and all three miners continued onward with no ABN issues! Nice! (I also see a huge surge in pool blocks solved: 35 in only 12 hours - maybe this is what was missing). Now we need more Christians to find out about the wallet. I'm thinking about making a one page startup guide like someone here suggested a couple weeks ago. (To get started with a CPK & POG). We should also look into turnkey mining; maybe a pool option that charges a higher percentage but fronts the ABN weight for the miner would be good. (It might be a pretty high percentage, like 20% pool fees for no-abn, and 0-1% for with-abn, etc). I really like the idea of a pool with no/low abn requirements. This would allow for the adoption of the project by the small christian miners. Again though you would run into the issue of bots hammering the pool, so perhaps abn requirement in the pool is setup to the value of the faucet on the pool. This way you can eliminate the bots while achieving the goal of larger adoption. The higher percentage fee of 20% works fine in my mind and simply have a flag that can be set on the miner to indicate no-abn or use-abn. Just my 2 cents. Who would supply the ABN for the non-abn miners? Could this be a potential setup to "stake" for "interest" aka fees from the little miners? Some people just hodl and don't want to mine. So far the only idea I have is potentially dropping an extra 200K in the pool (from my pocket) and adding a checkbox to the user settings (if they want to be a funded miner or not) , and if these miners on training wheels solve too many blocks Id have to drop more in the pool to keep up, etc. But I have to think about this all the way through to ensure its technically feasible, because it requires us to change the client to support full block emission to be shot from the pool into the miner and back to the pool etc. I dont know about the interest; except that I know we cant lend crypto or they will steal it . We have to lend the ABN transaction out to N miners at once etc. |
|
|
|
Could we also have a little more participation in testnet please? Specifically, not for rushing out our next release or testing 0.14, but more specifically for testing Cameroon-One and POG. Id like to certify that POG & Cameroon work properly within 30 days, so I can get back to Cameroon with Integration testing, and this will allow us to merge cameroon-one into prod as a Leisure release in .13 (our current branch) and get started with POOM mining. (This will allow miners to sponsor children at home and be rewarded in BBP).
https://forum.biblepay.org/index.php?topic=391.new#new |
|
|
|
Just wanted to let you know my miners have been going without issue since 1.4.4.1 upgrade, will keep an eye for when my ABN gets eaten and if the miner has any issue re-connecting to the pool once ABN weight is re-established.
Thanks, that sounds promising. Guess what, a PC found a block and all three miners continued onward with no ABN issues! Nice! (I also see a huge surge in pool blocks solved: 35 in only 12 hours - maybe this is what was missing). Now we need more Christians to find out about the wallet. I'm thinking about making a one page startup guide like someone here suggested a couple weeks ago. (To get started with a CPK & POG). We should also look into turnkey mining; maybe a pool option that charges a higher percentage but fronts the ABN weight for the miner would be good. (It might be a pretty high percentage, like 20% pool fees for no-abn, and 0-1% for with-abn, etc). |
|
|
|
Just wanted to let you know my miners have been going without issue since 1.4.4.1 upgrade, will keep an eye for when my ABN gets eaten and if the miner has any issue re-connecting to the pool once ABN weight is re-established.
Thanks, that sounds promising. |
|
|
|
BiblePay
1.4.4.1 - Leisure Upgrade
- Enhance biblepay-miner to allow it to detect a stagnant share
condition when pool mining and recover.
Since I installed the BBP wallet on a second machine to split up my coins and try to get a little extra mining in, my main wallet has had issues where it would get stuck on a block and will fall farther and farther behind my second wallet. The only fix is to rebuild from the blockchain. It sounds similar to this issue, so I can try the update myself and see what happens, but having two wallets on separate machines shouldn't be an issue, should it? Both machines are mining to the pool by the way. Thanks! I believe the problem is when we forced the sancs to upgrade twice this week, we've had a lot of failed votes and bad gobject traffic floating around. Please restart with -erasechain=1 and see if it sync to the top. Going forward I think we will be OK now that all the sancs upgraded and traffic is dying down. |
|
|
|
1) On exec health: No - that just means your local node assesses a different contract than the sancs (this is because 1440 is slightly different on the sanc side) - but if you upgrade your local node will assess the same contract and the warning will go away. Its harmless however, as long as the sancs have an agreed quorum.
2) Since your txid in block 129991 was actually One block higher than the previous superblock, you were paid in 130400 (exec analyze 129900 dave_bbp). The payment is in block 130400 vout 24 (for 3875). So basically payment occurs in the superblock following the superblock window the tithe occurred in (IE 129991 + 205 + 205 % 205) = 130400.
Thanks. Interesting, because my node is 1441. Actually, 130400 was when I expected the payment, but I received nothing. My transaction history is empty since 130394. I think I will restart my wallet with zapwallettxes and go to bed, maybe tomorrow the coins have arrived.  Yeah, if you are out of sync, your nodes health and PAM hash won't agree with the other nodes. Try to restart with 'erasechain=1'. People talked about the wallet repair option for resyncing, but there is a bug in the reindex routine. Erasechain kills the gobjects and thats what we want to be clear. |
|
|
|
Do you happen to have the TXID of that transmission? We missed a GSC payment this week due to broken-rule sanc issue (that 1440 addressed).
To answer your question though, exec health shows the next superblock at 130605 (the future). This contract contains all GSC transmissions from 130196-130400.
Sure, this is it: Date: 06.07.2019 17:38
Source: GSC-Transmission
To: POG_donations BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM
Debit: -2000.00000000 BBP
Transaction fee: -0.01483000 BBP
Net amount: -2000.01483000 BBP
Transaction ID: 276f5be64fa20f72cad78420ca1aa67897a71ea97a128108955a4480dab92db9
Output index: 1
Transaction total size: 1477 bytes
Height: 129991
Difficulty: 20442.75
Time: 07-06-2019 15:45:45
Subsidy: 2348.3544 btw: exec health for me shows "WARNING": "Our internal PAM hash disagrees with the network. " Could this be the problem? 1) On exec health: No - that just means your local node assesses a different contract than the sancs (this is because 1440 is slightly different on the sanc side) - but if you upgrade your local node will assess the same contract and the warning will go away. Its harmless however, as long as the sancs have an agreed quorum. 2) Since your txid in block 129991 was actually One block higher than the previous superblock, you were paid in 130400 (exec analyze 129900 dave_bbp). The payment is in block 130400 vout 24 (for 3875). So basically payment occurs in the superblock following the superblock window the tithe occurred in (IE 129991 + 205 + 205 % 205) = 130400. |
|
|
|
Quick question: How far behind are the POG (Smart Contract Rewards) after the POG (GSC Transmission) one makes?
I made my last GSC Transmission 2 days ago (block 129991). After that I appeared in the leaderboard for approx. a day and then disappeared (which is not unusual, as you explained earlier). I excpected some payment at block 130400 (at the latest), which went by 2 hours ago, but received nothing. Was I just "skipped" completely? Exec Roi stated a positive roi ...
Do you happen to have the TXID of that transmission? We missed a GSC payment this week due to broken-rule sanc issue (that 1440 addressed). To answer your question though, exec health shows the next superblock at 130605 (the future). This contract contains all GSC transmissions from 130196-130400. |
|
|
|
|
BiblePay
1.4.4.1 - Leisure Upgrade
- Enhance biblepay-miner to allow it to detect a stagnant share
condition when pool mining and recover.
|
|
|
|
Checking it again at 1:03AM EST, miner appears to have been running for quite some time but no longer on the pool / leaderboard. I will leave it running for the sake of figuring this out, hopefully. (and you can see too) 01:01:26  { "Command": "createabn",
"xml": "<MT>ABN</MT><abnmsg>955da50c345e786f01b0fc45a3a7756252270b5323a30fc93e84d52bad2a1ab3</abnmsg><abnsig>H+VIC5AaZo5OAfO3igwcFxvYT3kITlHJ4yMTgOFp2H1oTE7O3GJYuXOxh5ZLrbs6qFF0k38YmL5SlpC8YEjB7CA=</abnsig><abncpk>BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc</abncpk><abnwgt>125000</abnwgt>",
"err": "",
"coin_age_data_selected": "539.4800(332.31),1.2670(1.98),142.0700(229.76),27945.9915(18347.96),1000.0000(1670.23),1000.0000(1663.19),483.2776(453.48),1000.0000(3656.96),248.1900(139.70),152.3367(382.18),1000.0000(3662.71),799.0000(1325.54),5396.8587(11820.80),1000.0000(3652.70),1000.0000(3646.31),999.9000(4303.79),1000.0000(1668.78),1000.0000(1667.35),1000.0000(1665.94),1000.0000(6642.69),15.2924(38.69),28009.9000(61204.85),1000.0000(9155.65),969.1900(5442.83),132947.8760(14905.76),161576.6895(18115.59),",
"success": "2db0a0e676fa20ed4543902d142c949e30a9e6e7103d463520d7f7909ffc86aa",
"coin_age_data_pre_select": "539.4800(0.62)=[332.31] depth=133, \n1.2670(1.98)=[1.98] depth=413, \n142.0700(1.62)=[229.76] depth=330, \n27945.9915(0.66)=[18347.96] depth=142, \n1000.0000(1.67)=[1670.23] depth=346, \n1000.0000(1.66)=[1663.19] depth=345, \n483.2776(0.94)=[453.48] depth=197, \n1000.0000(3.66)=[3656.96] depth=767, \n248.1900(0.56)=[139.70] depth=121, \n152.3367(2.51)=[382.18] depth=529, \n1000.0000(3.66)=[3662.71] depth=768, \n799.0000(1.66)=[1325.54] depth=344, \n5396.8587(2.19)=[11820.80] depth=454, \n1000.0000(3.65)=[3652.70] depth=766, \n1000.0000(3.65)=[3646.31] depth=765, \n999.9000(4.31)=[4303.79] depth=902, \n1000.0000(1.67)=[1668.78] depth=346, \n1000.0000(1.67)=[1667.35] depth=346, \n1000.0000(1.67)=[1665.94] depth=346, \n1000.0000(6.64)=[6642.69] depth=1395, \n15.2924(2.58)=[38.69] depth=535, \n28009.9000(2.19)=[61204.85] depth=454, \n</EOF>",
"audited_weight": 132817.6637016593,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 328.48, Age: 0.61, Amount: 539.00, TxTime: 1562508955...Output #1, Weight: 225.26, Age: 1.59, Amount: 142.00, TxTime: 1562424552...Output #2, Weight: 6644.30, Age: 6.64, Amount: 1000.00, TxTime: 1561987541...Output #3, Weight: 9157.27, Age: 9.16, Amount: 1000.00, TxTime: 1561770421...Output #4, Weight: 1326.37, Age: 1.66, Amount: 799.00, TxTime: 1562418182...Output #5, Weight: 11787.14, Age: 2.18, Amount: 5396.00, TxTime: 1562372875...Output #6, Weight: 1666.37, Age: 1.67, Amount: 1000.00, TxTime: 1562417635...Output #7, Weight: 1666.37, Age: 1.67, Amount: 1000.00, TxTime: 1562417635...Output #8, Weight: 1666.37, Age: 1.67, Amount: 1000.00, TxTime: 1562417635...Output #9, Weight: 3651.89, Age: 3.65, Amount: 1000.00, TxTime: 1562246086...Output #10, Weight: 61183.45, Age: 2.18, Amount: 28009.00, TxTime: 1562372875...Output #11, Weight: 18393.24, Age: 0.66, Amount: 27945.00, TxTime: 1562504741...Output #12, Weight: 15121.18, Age: 0.11, Amount: 132947.00, TxTime: 1562551782..."
 { "Command": "createabn", "xml": "<MT>ABN</MT><abnmsg>d62df5c17a643247b48283fca544dcf5132d05c20196d79eeeadde212e3bc33d</abnmsg><abnsig>ICffHpHJ1tF9eg7h1bMloqIkhBNfj8+W5YUIr468yVDpAfWQ4f1atZZIBHuwKddlAQ20fYp2aIbp9J59xtCgIO4=</abnsig><abncpk>BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc</abncpk><abnwgt>125000</abnwgt>", "err": "", "coin_age_data_selected": "539.4800(567.60),1.2670(2.42),483.2776(664.33),248.1900(247.96),3245.5100(174.87),799.0000(1674.33),5396.8587(14176.37),5.2559(1.21),67260.2075(16220.25),1000.0000(9592.19),969.1900(5865.84),132947.8760(72942.36),161576.6895(88649.87),", "success": "dfa87aee9e86e1c56e8b91d7e1e1b595241818bae9a8916c205b96d1403394cd", "coin_age_data_pre_select": "539.4800(1.05)=[567.60] depth=225, \n1.2670(2.42)=[2.42] depth=505, \n483.2776(1.38)=[664.33] depth=289, \n248.1900(1.00)=[247.96] depth=213, \n3245.5100(0.05)=[174.87] depth=14, \n799.0000(2.10)=[1674.33] depth=436, \n5396.8587(2.63)=[14176.37] depth=546, \n5.2559(0.24)=[1.21] depth=55, \n67260.2075(0.24)=[16220.25] depth=55, \n1000.0000(9.59)=[9592.19] depth=1989, \n969.1900(6.05)=[5865.84] depth=1266, \n132947.8760(0.55)=[72942.36] depth=116, \n161576.6895(0.55)=[88649.87] depth=116, \n</EOF>", "audited_weight": 162222.840564486, "vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 73227.01, Age: 0.55, Amount: 132947.00, TxTime: 1562551782...Output #1, Weight: 88995.83, Age: 0.55, Amount: 161576.00, TxTime: 1562551782..." } Thanks, it appears you have given me more than enough to go on for the pool mining issue. On a side note, what made me apprehensive about believing we had a pool.biblepay.org problem, is Ive been running my bible_pay miner for weeks, and always see myself in the pool with 1 thread or 5 threads, and I havent received any complaints from anyone else yet (and I usually hear from Capulo pretty quickly if he falls out of the pool). But anyway what you have proven to me is we have a circumstance where your eyeseven miner asks for work, receives the work, starts hashing it for a while, and it either cant finish those particular guids, or for some reason, receives work that is too hard for it (I find that hard to believe because you are over 100KHPS) - another very strange phenomenon. But I think in this case, we need to take the bulletproof route; and what I will do is make a feature inside the biblepay miner, that keeps track of how much work it solved in the pool and if it feels it is going to fall out of the leaderboard, it will discard what its working on and ask for a new share (IE it will be persistent to get back in). This should solve the problem of communication fallout. Ill work on this today. Regarding the ABN, your 131K is very close to your audited 129K so we dont see an anomaly right now - if you solve a block please post the exec createabn 125000 and we will see whats up. Thanks! Please look forward to upgrading to v1.4.4.1, then testing to see if you ever fall out of the pool again. (It should be out in 2 hours). |
|
|
|
Checking it again at 1:03AM EST, miner appears to have been running for quite some time but no longer on the pool / leaderboard. I will leave it running for the sake of figuring this out, hopefully. (and you can see too) 01:01:26  { "Command": "createabn",
"xml": "<MT>ABN</MT><abnmsg>955da50c345e786f01b0fc45a3a7756252270b5323a30fc93e84d52bad2a1ab3</abnmsg><abnsig>H+VIC5AaZo5OAfO3igwcFxvYT3kITlHJ4yMTgOFp2H1oTE7O3GJYuXOxh5ZLrbs6qFF0k38YmL5SlpC8YEjB7CA=</abnsig><abncpk>BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc</abncpk><abnwgt>125000</abnwgt>",
"err": "",
"coin_age_data_selected": "539.4800(332.31),1.2670(1.98),142.0700(229.76),27945.9915(18347.96),1000.0000(1670.23),1000.0000(1663.19),483.2776(453.48),1000.0000(3656.96),248.1900(139.70),152.3367(382.18),1000.0000(3662.71),799.0000(1325.54),5396.8587(11820.80),1000.0000(3652.70),1000.0000(3646.31),999.9000(4303.79),1000.0000(1668.78),1000.0000(1667.35),1000.0000(1665.94),1000.0000(6642.69),15.2924(38.69),28009.9000(61204.85),1000.0000(9155.65),969.1900(5442.83),132947.8760(14905.76),161576.6895(18115.59),",
"success": "2db0a0e676fa20ed4543902d142c949e30a9e6e7103d463520d7f7909ffc86aa",
"coin_age_data_pre_select": "539.4800(0.62)=[332.31] depth=133, \n1.2670(1.98)=[1.98] depth=413, \n142.0700(1.62)=[229.76] depth=330, \n27945.9915(0.66)=[18347.96] depth=142, \n1000.0000(1.67)=[1670.23] depth=346, \n1000.0000(1.66)=[1663.19] depth=345, \n483.2776(0.94)=[453.48] depth=197, \n1000.0000(3.66)=[3656.96] depth=767, \n248.1900(0.56)=[139.70] depth=121, \n152.3367(2.51)=[382.18] depth=529, \n1000.0000(3.66)=[3662.71] depth=768, \n799.0000(1.66)=[1325.54] depth=344, \n5396.8587(2.19)=[11820.80] depth=454, \n1000.0000(3.65)=[3652.70] depth=766, \n1000.0000(3.65)=[3646.31] depth=765, \n999.9000(4.31)=[4303.79] depth=902, \n1000.0000(1.67)=[1668.78] depth=346, \n1000.0000(1.67)=[1667.35] depth=346, \n1000.0000(1.67)=[1665.94] depth=346, \n1000.0000(6.64)=[6642.69] depth=1395, \n15.2924(2.58)=[38.69] depth=535, \n28009.9000(2.19)=[61204.85] depth=454, \n</EOF>",
"audited_weight": 132817.6637016593,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 328.48, Age: 0.61, Amount: 539.00, TxTime: 1562508955...Output #1, Weight: 225.26, Age: 1.59, Amount: 142.00, TxTime: 1562424552...Output #2, Weight: 6644.30, Age: 6.64, Amount: 1000.00, TxTime: 1561987541...Output #3, Weight: 9157.27, Age: 9.16, Amount: 1000.00, TxTime: 1561770421...Output #4, Weight: 1326.37, Age: 1.66, Amount: 799.00, TxTime: 1562418182...Output #5, Weight: 11787.14, Age: 2.18, Amount: 5396.00, TxTime: 1562372875...Output #6, Weight: 1666.37, Age: 1.67, Amount: 1000.00, TxTime: 1562417635...Output #7, Weight: 1666.37, Age: 1.67, Amount: 1000.00, TxTime: 1562417635...Output #8, Weight: 1666.37, Age: 1.67, Amount: 1000.00, TxTime: 1562417635...Output #9, Weight: 3651.89, Age: 3.65, Amount: 1000.00, TxTime: 1562246086...Output #10, Weight: 61183.45, Age: 2.18, Amount: 28009.00, TxTime: 1562372875...Output #11, Weight: 18393.24, Age: 0.66, Amount: 27945.00, TxTime: 1562504741...Output #12, Weight: 15121.18, Age: 0.11, Amount: 132947.00, TxTime: 1562551782..."
 { "Command": "createabn", "xml": "<MT>ABN</MT><abnmsg>d62df5c17a643247b48283fca544dcf5132d05c20196d79eeeadde212e3bc33d</abnmsg><abnsig>ICffHpHJ1tF9eg7h1bMloqIkhBNfj8+W5YUIr468yVDpAfWQ4f1atZZIBHuwKddlAQ20fYp2aIbp9J59xtCgIO4=</abnsig><abncpk>BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc</abncpk><abnwgt>125000</abnwgt>", "err": "", "coin_age_data_selected": "539.4800(567.60),1.2670(2.42),483.2776(664.33),248.1900(247.96),3245.5100(174.87),799.0000(1674.33),5396.8587(14176.37),5.2559(1.21),67260.2075(16220.25),1000.0000(9592.19),969.1900(5865.84),132947.8760(72942.36),161576.6895(88649.87),", "success": "dfa87aee9e86e1c56e8b91d7e1e1b595241818bae9a8916c205b96d1403394cd", "coin_age_data_pre_select": "539.4800(1.05)=[567.60] depth=225, \n1.2670(2.42)=[2.42] depth=505, \n483.2776(1.38)=[664.33] depth=289, \n248.1900(1.00)=[247.96] depth=213, \n3245.5100(0.05)=[174.87] depth=14, \n799.0000(2.10)=[1674.33] depth=436, \n5396.8587(2.63)=[14176.37] depth=546, \n5.2559(0.24)=[1.21] depth=55, \n67260.2075(0.24)=[16220.25] depth=55, \n1000.0000(9.59)=[9592.19] depth=1989, \n969.1900(6.05)=[5865.84] depth=1266, \n132947.8760(0.55)=[72942.36] depth=116, \n161576.6895(0.55)=[88649.87] depth=116, \n</EOF>", "audited_weight": 162222.840564486, "vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 73227.01, Age: 0.55, Amount: 132947.00, TxTime: 1562551782...Output #1, Weight: 88995.83, Age: 0.55, Amount: 161576.00, TxTime: 1562551782..." } Thanks, it appears you have given me more than enough to go on for the pool mining issue. On a side note, what made me apprehensive about believing we had a pool.biblepay.org problem, is Ive been running my bible_pay miner for weeks, and always see myself in the pool with 1 thread or 5 threads, and I havent received any complaints from anyone else yet (and I usually hear from Capulo pretty quickly if he falls out of the pool). But anyway what you have proven to me is we have a circumstance where your eyeseven miner asks for work, receives the work, starts hashing it for a while, and it either cant finish those particular guids, or for some reason, receives work that is too hard for it (I find that hard to believe because you are over 100KHPS) - another very strange phenomenon. But I think in this case, we need to take the bulletproof route; and what I will do is make a feature inside the biblepay miner, that keeps track of how much work it solved in the pool and if it feels it is going to fall out of the leaderboard, it will discard what its working on and ask for a new share (IE it will be persistent to get back in). This should solve the problem of communication fallout. Ill work on this today. Regarding the ABN, your 131K is very close to your audited 129K so we dont see an anomaly right now - if you solve a block please post the exec createabn 125000 and we will see whats up. Thanks! |
|
|
|
I'm going to try litemode specifically, I didn't know about it!
dont worry, nobody  my win10 home working stable lol this miserably failed coin is still running? i thought all machines are shut down already... Your fud is quite transparent, and duly noted. This project is doing good things, and tons of machines are running. What happened to you to make you salty about it? God is cleansing the project. The ones who don't have the Love of God in them, and the ones who have trouble donating to the foundation are leaving, and the Righteous users are coming. Praise Jesus! We'll be over a million market cap any week now, anyway, so we are obviously successful . |
|
|
|
I am downloading 1.4.4.0b now, At the time that I reported the miner not being on pool, but mining via getmininginfo, it was pulling 100,000 hashes per second. After waiting an hour or so to see if it was just an un-updated pool, I restarted the miner and it was immediately on the pool thereafter, crunching as you see now. Will update this post with information from 1.4.4.0b for you, so keep an eye out. I don't want to spam the thread too much. 20:02:35  getmininginfo 20:02:35  { "blocks": 130269, "currentblocksize": 1501, "currentblocktx": 1, "difficulty": 2407.888051668461, "errors": "", "pooledtx": 0, "chain": "main", "genproclimit": 7, "networkhashps": 265541.0490871345, "hashps": 81753.38808795009, "minerstarttime": "07-07-2019 23:54:00", "hashcounter": 41985597, "pooledtx": 0, "chain": "main", "biblepay-generate": true, "poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ", "poolinfo2": "Submitting Solution 07-08-2019 00:00:36; Submitting Solution 07-08-2019 00:00:35; Submitting Solution 07-08-2019 00:00:35; RMC_07-08-2019 00:00:37; RM_07-08-2019 00:00:37; RMC_07-08-2019 00:00:37; RMC_07-08-2019 00:00:37; ", "poolinfo3": "", "abninfo": "", "gsc_errors": "", "poolmining": true, "pool_url": " https://pool.biblepay.org", "required_abn_weight": 125000 } 20:02:42  exec getabnweight 125000 20:02:42  { "Command": "getabnweight", "version": 1.2, "weight": 255356.9379398148, "total_required": 370979, "weight 125000.00": 142029.679849537, "total_required 125000.00": 323153 } 20:02:53  exec getabnweight 125000 1 20:02:53  { "Command": "getabnweight", "version": 1.2, "weight": 255356.9379398148, "total_required": 370979, "coin_age_data_pre_select": "539.4800(0.40)=[215.12] depth=87, \n1.2670(1.77)=[1.77] depth=367, \n142.0700(1.40)=[198.89] depth=284, \n27945.9915(0.44)=[12272.19] depth=96, \n294524.5706(0.44)=[129341.71] depth=96, \n</EOF>", "weight 125000.00": 142029.679849537, "total_required 125000.00": 323153 } 20:03:14  exec createabn 125000 1 20:03:14  { "Command": "createabn", "xml": "<MT>ABN</MT><abnmsg>bfec7afc35f3bca25f5d78ca40d7aa8e987dcbab46d7f3a3ae7e5eebf0cca7b4</abnmsg><abnsig>H75UUbWR/kj2xAufY6yx6uCuk9RC1+J6p1lJf6E7ogC5LUZrtUh0BTsFLOADZqCm8wOMPlcs3MYngu2MyyYg1IY=</abnsig><abncpk>BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc</abncpk><abnwgt>125000</abnwgt>", "err": "", "coin_age_data_selected": "539.4800(222.29),1.2670(1.78),142.0700(200.78),27945.9915(12643.82),294524.5706(133258.47),", "success": "a23094a956bec4fb44ba22698831ae8d0883e475c9639fd8d7011b2dad17a2c6", "coin_age_data_pre_select": "539.4800(0.41)=[222.29] depth=88, \n1.2670(1.78)=[1.78] depth=368, \n142.0700(1.41)=[200.78] depth=285, \n27945.9915(0.45)=[12643.82] depth=97, \n294524.5706(0.45)=[133258.47] depth=97, \n</EOF>", "audited_weight": 134431.1009223263, "vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 134431.10, Age: 0.46, Amount: 294524.00, TxTime: 1562504741..." } Miner is currently mining and showing on pool. 1) Regarding the pool, at the time when you posted and said you were mining but not seen in the pool, the 5 shares had a timestamp of only about 10 minutes old, so from my end it appeared your miner requested 5 shares and didnt solve any yet. Once you have 1 solved share, you appear in the leaderboard. Maybe what happened is an hour earlier you were pool mining and your abn issue started, and you fell out of the pool. (On my end the pool eventually deletes the older work, after about 30 mins so to me it will look like you are completely not mining after we dont hear from you for about 30 mins). 2) Since your vin_coin_age is working correctly right now I dont see a discrepency in the createabn vin output. Please post again when this problem reoccurs (when "GotWeight" < audited weight). |
|
|
|
New update: 3:45PM EST miner turns off "LOW ABN" 15:44:07  getmininginfo 15:44:07

{
"blocks": 130235,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 4282.786613228499,
"errors": "",
"pooledtx": 0,
"chain": "main",
"genproclimit": 7,
"networkhashps": 262002.3948940885,
"hashps": 118954.7978212055,
"minerstarttime": "07-07-2019 18:59:24",
"hashcounter": 242256085,
"pooledtx": 0,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RMC_07-07-2019 19:42:47; RMC_07-07-2019 19:42:47; RMC_07-07-2019 19:42:49; RMC_07-07-2019 19:42:48; RMC_07-07-2019 19:42:48; RMC_07-07-2019 19:43:20; RMC_07-07-2019 19:43:20; ",
"poolinfo3": "CFW 07-07-2019 19:33:20; ",
"abninfo": "Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; ",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}
15:46:46

exec getabnweight 125000 1
15:46:46

{
"Command": "getabnweight",
"version": 1.2,
"weight": 194253.7346643519,
"total_required": 370979,
"coin_age_data_pre_select": "539.4800(0.23)=[126.34] depth=54, \n1.2670(1.60)=[1.60] depth=334, \n142.0700(1.24)=[175.50] depth=251, \n27945.9915(0.27)=[7669.35] depth=63, \n294524.5706(0.27)=[80830.48] depth=63, \n1000.0000(1.29)=[1288.10] depth=267, \n1000.0000(1.28)=[1281.06] depth=266, \n483.2776(0.56)=[268.91] depth=118, \n1000.0000(3.27)=[3274.83] depth=688, \n152.3367(2.13)=[324.10] depth=450, \n1000.0000(3.28)=[3280.58] depth=689, \n799.0000(1.28)=[1020.21] depth=265, \n5396.8587(1.81)=[9758.83] depth=375, \n1000.0000(3.27)=[3270.57] depth=687, \n1000.0000(3.26)=[3264.18] depth=686, \n999.9000(3.93)=[3922.05] depth=823, \n1000.0000(1.29)=[1286.66] depth=267, \n1000.0000(1.29)=[1285.22] depth=267, \n1000.0000(1.28)=[1283.81] depth=267, \n1000.0000(6.26)=[6260.56] depth=1316, \n</EOF>",
"weight 125000.00": 129872.9239930556,
"total_required 125000.00": 340984
}
15:50:18

exec createabn 125000 1
15:50:19

{
"Command": "createabn",
"xml": "<MT>ABN</MT><abnmsg>f48468a258dfc369c81448559366993acb9c7dd77447567b870751a0bfd5f4d7</abnmsg><abnsig>IGsWYe2cfjDO3FW0W/ZAC979+Q7NVh8WriFA6crA1NMZCCsVMTc4gG0WbyFzfqSjyEXLrs4cBuJDw6/WXkUYi54=</abnsig><abncpk>BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc</abncpk><abnwgt>125000</abnwgt>",
"err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=130627, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=106813.51",
"age_data": "539.4800(127.53),1.2670(1.60),142.0700(175.82),27945.9915(7731.13),294524.5706(81481.56),1000.0000(1290.31),1000.0000(1283.28),483.2776(269.98),1000.0000(3277.04),152.3367(324.43),1000.0000(3282.79),799.0000(1021.98),5396.8587(9770.76),1000.0000(3272.78),1000.0000(3266.39),999.9000(3924.25),1000.0000(1288.87),1000.0000(1287.43),1000.0000(1286.02),1000.0000(6262.77),15.2924(33.00),28009.9000(50563.70),1000.0000(8775.73),969.1900(5074.69),",
"tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=130627, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=106813.51"
}
I would have sent via PM but I am only permitted 1 per day as my account is still fresh. Edit: UPDATE: Miner eyeseven is mining 94k Hash/per sec as of 6:30PM (just checked it) with no weight issues, however it is not reported on the pool whatsoever. getmininginfo confirms "TRUE" for poolmining 1) So we are getting closer, but unfortunately the field I need to see (vin_coin_age) is not in your createabn output, because I just found out, when the createabn command fails with insufficient funds, we dont log that field. So I am rebuilding 1.4.4.0b with that field to see if it will allow you to report it on the next run. 2) I'll take a look at the eyeseven pool miner. Ok, 1.4.4.0b windows is deployed, please upgrade and then run the 'exec createabn 125000' again, lets see if it reveals anything between the 106K got weight and 130.6K weight it should actually get. B) I see eyeseven has requested 5 shares from the pool and is crunching them. The reason you arent in the leaderboard yet is eyeseven hasnt solved any; which is strange because some of these shares are very easy. So please check to ensure you havent turned off the miner, etc. Im really interested in this, because I see very few miners since enabling ABN. Id really like to know why your miner isnt solving any shares. Does it still show a high HPS in getmininginfo? |
|
|
|
New update: 3:45PM EST miner turns off "LOW ABN" 15:44:07  getmininginfo 15:44:07

{
"blocks": 130235,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 4282.786613228499,
"errors": "",
"pooledtx": 0,
"chain": "main",
"genproclimit": 7,
"networkhashps": 262002.3948940885,
"hashps": 118954.7978212055,
"minerstarttime": "07-07-2019 18:59:24",
"hashcounter": 242256085,
"pooledtx": 0,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RMC_07-07-2019 19:42:47; RMC_07-07-2019 19:42:47; RMC_07-07-2019 19:42:49; RMC_07-07-2019 19:42:48; RMC_07-07-2019 19:42:48; RMC_07-07-2019 19:43:20; RMC_07-07-2019 19:43:20; ",
"poolinfo3": "CFW 07-07-2019 19:33:20; ",
"abninfo": "Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=128744, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=103148.81; ",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}
15:46:46

exec getabnweight 125000 1
15:46:46

{
"Command": "getabnweight",
"version": 1.2,
"weight": 194253.7346643519,
"total_required": 370979,
"coin_age_data_pre_select": "539.4800(0.23)=[126.34] depth=54, \n1.2670(1.60)=[1.60] depth=334, \n142.0700(1.24)=[175.50] depth=251, \n27945.9915(0.27)=[7669.35] depth=63, \n294524.5706(0.27)=[80830.48] depth=63, \n1000.0000(1.29)=[1288.10] depth=267, \n1000.0000(1.28)=[1281.06] depth=266, \n483.2776(0.56)=[268.91] depth=118, \n1000.0000(3.27)=[3274.83] depth=688, \n152.3367(2.13)=[324.10] depth=450, \n1000.0000(3.28)=[3280.58] depth=689, \n799.0000(1.28)=[1020.21] depth=265, \n5396.8587(1.81)=[9758.83] depth=375, \n1000.0000(3.27)=[3270.57] depth=687, \n1000.0000(3.26)=[3264.18] depth=686, \n999.9000(3.93)=[3922.05] depth=823, \n1000.0000(1.29)=[1286.66] depth=267, \n1000.0000(1.29)=[1285.22] depth=267, \n1000.0000(1.28)=[1283.81] depth=267, \n1000.0000(6.26)=[6260.56] depth=1316, \n</EOF>",
"weight 125000.00": 129872.9239930556,
"total_required 125000.00": 340984
}
15:50:18

exec createabn 125000 1
15:50:19

{
"Command": "createabn",
"xml": "<MT>ABN</MT><abnmsg>f48468a258dfc369c81448559366993acb9c7dd77447567b870751a0bfd5f4d7</abnmsg><abnsig>IGsWYe2cfjDO3FW0W/ZAC979+Q7NVh8WriFA6crA1NMZCCsVMTc4gG0WbyFzfqSjyEXLrs4cBuJDw6/WXkUYi54=</abnsig><abncpk>BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc</abncpk><abnwgt>125000</abnwgt>",
"err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=130627, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=106813.51",
"age_data": "539.4800(127.53),1.2670(1.60),142.0700(175.82),27945.9915(7731.13),294524.5706(81481.56),1000.0000(1290.31),1000.0000(1283.28),483.2776(269.98),1000.0000(3277.04),152.3367(324.43),1000.0000(3282.79),799.0000(1021.98),5396.8587(9770.76),1000.0000(3272.78),1000.0000(3266.39),999.9000(3924.25),1000.0000(1288.87),1000.0000(1287.43),1000.0000(1286.02),1000.0000(6262.77),15.2924(33.00),28009.9000(50563.70),1000.0000(8775.73),969.1900(5074.69),",
"tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=130627, UsingBBP=340984.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=106813.51"
}
I would have sent via PM but I am only permitted 1 per day as my account is still fresh. Edit: UPDATE: Miner eyeseven is mining 94k Hash/per sec as of 6:30PM (just checked it) with no weight issues, however it is not reported on the pool whatsoever. getmininginfo confirms "TRUE" for poolmining 1) So we are getting closer, but unfortunately the field I need to see (vin_coin_age) is not in your createabn output, because I just found out, when the createabn command fails with insufficient funds, we dont log that field. So I am rebuilding 1.4.4.0b with that field to see if it will allow you to report it on the next run. 2) I'll take a look at the eyeseven pool miner. |
|
|
|
Can someone help me figure out why I have no hashps showing up? 
{
"blocks": 130227,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 2130.164171713709,
"errors": "",
"pooledtx": 0,
"chain": "main",
"genproclimit": 2,
"networkhashps": 258953.0736721055,
"hashps": 0,
"minerstarttime": "07-07-2019 18:54:43",
"hashcounter": 0,
"pooledtx": 0,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RMC_07-07-2019 19:03:26; RMC_07-07-2019 19:03:25; ",
"poolinfo3": "",
"abninfo": "Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; ",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "http://pool.biblepay.org",
"required_abn_weight": 125000
}
Everything else seems fine? Not sure about the abn part as it doesn't seem like something I see needed to setup a biblepay.conf file to mine? Does this mean I cannot mine even though it says poolmining "true" and biblepay-generate "true"? poolmining=true and generate=true means your mining thread is running, and you are configured to pool mine, but you are not mining due to the error in "abninfo". Could you please paste your 'exec getabnweight 125000' and it should show the reason you are not mining. Minimum abn weight is 125,000. (Otherwise the miner fails to create a block). |
|
|
|
Hi Rob,
After combine some clue i think they can not decrypted cause hacker no need access my computer to send away BBP. I am never unlock the cold wallet, if send or start SANC wallet prompt the passphrase (as my remmber this still not unlock permanent the wallet ) and the character still * when i typing. So the last maybe got keylogger.
I was also thinking that if they transferred the physical wallet file they could have sent the BBP from their node (but sometimes hackers deliberately do things to throw you off). But anyway, I agree with you that the most likely scenario is the characters were logged- the first thing I would do is check all your running processes and see if any are Trojans or viruses. If you have a running process that is a virus, it could have an integrated keylogger and may have been running for a while on that system. They might have logged in with the same 6 character password into teamviewer (IE that might be how they discovered it) - the worm was first injected in your machine, ran as a keylogger, then they discover a password, then they install teamviewer server, then they log in with the pass, then try to steal anything they can find on the machine etc. |
|
|
|
Got hacking by teamviewer...
Woah, that's never good. Would you be willing to go into detail as to what happened so we can be on the lookout? Personally I did use teamviewer before to monitor a few PC's not at home, but since I've encrypted my wallet Hi Gilligan, yes by ping the Teamview ID and then try access by your password ( may be simple ). And copy to your computer: file teamview exe was infected (auto script open sessions ). Hi Rob, The wallet enrypted with 6 number can be decypted ? or maybe i lost by keylogger ( im try rechecking but no see any keylogger ). Anyway thanks for your effort investigate. The bitcoin wallet encryptor routine uses AES256 which is pretty strong, and hasnt been exploited. To answer specifically though, although 6 char password is not very strong for text, it should still be highly impossible for a hacker to brute force (because the AES with salt is dealing with 256 characters per byte, not just 36 from the keyboard). However even more specifically: If they had a copy of your wallet.dat for a few weeks they could do it (I read about a bounty once where a routine cracked an encrypted wallet over a couple weeks) but again that requires them to take your wallet.dat file for a while, then hack in later. Id lean more towards someone who had access seeing the passphrase typed somewhere. Was it left in a locked state also while you were gone, so you think they came in and issued the walletpassphrase command also? |
|
|
|
I seem to be having some ABN issues. 13:46:57  getmininginfo 13:46:57  { "blocks": 130216, "currentblocksize": 1000, "currentblocktx": 0, "difficulty": 1900.167625605944, "errors": "", "pooledtx": 0, "chain": "main", "genproclimit": 7, "networkhashps": 268524.8889887106, "hashps": 0, "minerstarttime": "07-07-2019 17:26:42", "hashcounter": 0, "pooledtx": 0, "chain": "main", "biblepay-generate": true, "poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ", "poolinfo2": "RMC_07-07-2019 17:46:03; RMC_07-07-2019 17:46:03; RMC_07-07-2019 17:46:03; RMC_07-07-2019 17:46:04; RMC_07-07-2019 17:46:04; RMC_07-07-2019 17:46:05; RMC_07-07-2019 17:46:05; ", "poolinfo3": "", "abninfo": "Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=147992, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=123914.50; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=147992, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=123914.50; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=147992, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=123914.50; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=147992, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=123914.50; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=147992, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=123914.50; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=147992, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=123914.50; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=147992, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=123914.50; ", "gsc_errors": "low abn weight 0", "poolmining": true, "pool_url": " https://pool.biblepay.org", "required_abn_weight": 125000 } 13:53:45  getmininginfo 13:53:45  { "blocks": 130216, "currentblocksize": 3627, "currentblocktx": 3, "difficulty": 1900.167625605944, "errors": "", "pooledtx": 3, "chain": "main", "genproclimit": 7, "networkhashps": 268524.8889887106, "hashps": 0, "minerstarttime": "07-07-2019 17:26:42", "hashcounter": 0, "pooledtx": 3, "chain": "main", "biblepay-generate": true, "poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ", "poolinfo2": "RMC_07-07-2019 17:52:22; RMC_07-07-2019 17:52:22; RMC_07-07-2019 17:52:22; RMC_07-07-2019 17:52:22; RMC_07-07-2019 17:52:23; RMC_07-07-2019 17:52:23; RMC_07-07-2019 17:52:24; ", "poolinfo3": "", "abninfo": "Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=149328, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=122826.18; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=149328, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=122826.18; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=149328, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=122826.18; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=149328, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=122826.18; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=149328, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=122826.18; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=149328, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=122826.18; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=149328, UsingBBP=369009.00, I=25, SpendingBBP=370978.00, NeededWeight=125000, GotWeight=122826.18; ", "gsc_errors": "low abn weight 0", "poolmining": true, "pool_url": " https://pool.biblepay.org", "required_abn_weight": 125000 } 13:55:27  exec getabnweight 125000 13:55:27  { "Command": "getabnweight", "version": 1.2, "weight": 163008.7054861112, "total_required": 370979, "weight 125000.00": 149328.4783101852, "total_required 125000.00": 369009 } As seen here... I'm going backwards in weight required over time(the way its calculated?), and I'm well above the needed weight... Windows miner, sorry if I'm spamming up the place I'm just kind of clueless and want to help make this run flawlessly. EDIT FOR exec getabnweight 125000 1 14:00:16

exec getabnweight 125000 1
14:00:16

{
"Command": "getabnweight",
"version": 1.2,
"weight": 163991.9556828703,
"total_required": 370979,
"coin_age_data_pre_select": "539.4800(0.15)=[82.37] depth=35, \n1.2670(1.52)=[1.52] depth=315, \n142.0700(1.15)=[163.92] depth=232, \n27945.9915(0.19)=[5389.76] depth=44, \n294524.5706(0.19)=[56804.95] depth=44, \n1000.0000(1.21)=[1206.53] depth=248, \n1000.0000(1.20)=[1199.49] depth=247, \n483.2776(0.48)=[229.51] depth=99, \n1000.0000(3.19)=[3193.25] depth=669, \n152.3367(2.05)=[311.70] depth=431, \n1000.0000(3.20)=[3199.00] depth=670, \n799.0000(1.20)=[955.04] depth=246, \n5396.8587(1.73)=[9318.65] depth=356, \n1000.0000(3.19)=[3188.99] depth=668, \n1000.0000(3.18)=[3182.60] depth=667, \n999.9000(3.84)=[3840.55] depth=804, \n1000.0000(1.21)=[1205.08] depth=248, \n1000.0000(1.20)=[1203.65] depth=248, \n1000.0000(1.20)=[1202.23] depth=248, \n1000.0000(6.18)=[6178.98] depth=1297, \n15.2924(2.12)=[31.74] depth=437, \n28009.9000(1.72)=[48216.97] depth=356, \n</EOF>",
"weight 125000.00": 150306.5097453704,
"total_required 125000.00": 369009
}
Thanks, but oops, Im falling behind on my own debug command, could you please post this: exec createabn 125000 I am looking for something that emits to compare with. |
|
|
|
|
Show Posts
