BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 124.

dave_bbp

jr. member

Activity: 405

Merit: 3

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 ...

MIP

newbie

Activity: 362

Merit: 0

Quote from: bible_pay on July 08, 2019, 01:01:07 PM

BiblePay
1.4.4.1 - Leisure Upgrade

- Enhance biblepay-miner to allow it to detect a stagnant share
condition when pool mining and recover.

MacOS and Linux binaries ready.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

BiblePay
1.4.4.1 - Leisure Upgrade

- Enhance biblepay-miner to allow it to detect a stagnant share
condition when pool mining and recover.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: bible_pay on July 08, 2019, 10:57:33 AM

Quote from: Gilligan_M on July 08, 2019, 12:07:48 AM

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

{

Code:

  "Command": "createabn",
  "xml": "ABN955da50c345e786f01b0fc45a3a7756252270b5323a30fc93e84d52bad2a1ab3H+VIC5AaZo5OAfO3igwcFxvYT3kITlHJ4yMTgOFp2H1oTE7O3GJYuXOxh5ZLrbs6qFF0k38YmL5SlpC8YEjB7CA=BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc125000",
  "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",
  "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": "ABNd62df5c17a643247b48283fca544dcf5132d05c20196d79eeeadde212e3bc33dICffHpHJ1tF9eg7h1bMloqIkhBNfj8+W5YUIr468yVDpAfWQ4f1atZZIBHuwKddlAQ20fYp2aIbp9J59xtCgIO4=BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc125000",
"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",
"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).

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Gilligan_M on July 08, 2019, 12:07:48 AM

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

{

Code:

  "Command": "createabn",
  "xml": "ABN955da50c345e786f01b0fc45a3a7756252270b5323a30fc93e84d52bad2a1ab3H+VIC5AaZo5OAfO3igwcFxvYT3kITlHJ4yMTgOFp2H1oTE7O3GJYuXOxh5ZLrbs6qFF0k38YmL5SlpC8YEjB7CA=BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc125000",
  "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",
  "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": "ABNd62df5c17a643247b48283fca544dcf5132d05c20196d79eeeadde212e3bc33dICffHpHJ1tF9eg7h1bMloqIkhBNfj8+W5YUIr468yVDpAfWQ4f1atZZIBHuwKddlAQ20fYp2aIbp9J59xtCgIO4=BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc125000",
"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",
"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!

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Gilligan_M on July 08, 2019, 09:52:40 AM

Quote from: ?? on ??

Quote from: slovakia on July 06, 2019, 10:57:22 PM

Quote from: Gilligan_M on July 06, 2019, 08:48:09 PM

I'm going to try litemode specifically, I didn't know about it!

dont worry, nobody Grin

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

.

Gilligan_M

newbie

Activity: 28

Merit: 0

Quote from: ?? on ??

Quote from: slovakia on July 06, 2019, 10:57:22 PM

Quote from: Gilligan_M on July 06, 2019, 08:48:09 PM

I'm going to try litemode specifically, I didn't know about it!

dont worry, nobody Grin

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?

harrisvan87

newbie

Activity: 81

Merit: 0

Quote from: yaronidon on July 08, 2019, 03:22:53 AM

Quote from: bible_pay on July 07, 2019, 01:31:53 PM

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.

Allowing two way authentication will solve this risk.
Maybe "Google Authenticator" ?

Yes, this is what i thinking & still no see any coin have feature require Email verify or GAuthenticator for transactions.

yaronidon

newbie

Activity: 23

Merit: 0

Quote from: bible_pay on July 07, 2019, 01:31:53 PM

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.

Allowing two way authentication will solve this risk.
Maybe "Google Authenticator" ?

Gilligan_M

newbie

Activity: 28

Merit: 0

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)

Here's what I see

Quote

01:00:36

getmininginfo

01:00:36

{
  "blocks": 130315,
  "currentblocksize": 3757,
  "currentblocktx": 3,
  "difficulty": 3402.413352531992,
  "errors": "",
  "pooledtx": 2,
  "chain": "main",
  "genproclimit": 7,
  "networkhashps": 317134.7016807758,
  "hashps": 120315.2779943156,
  "minerstarttime": "07-07-2019 23:54:00",
  "hashcounter": 2213266434,
  "pooledtx": 2,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "abninfo": "",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "required_abn_weight": 125000
}

01:01:26

exec createabn 125000 1

01:01:26

{
  "Command": "createabn",
  "xml": "ABN955da50c345e786f01b0fc45a3a7756252270b5323a30fc93e84d52bad2a1ab3H+VIC5AaZo5OAfO3igwcFxvYT3kITlHJ4yMTgOFp2H1oTE7O3GJYuXOxh5ZLrbs6qFF0k38YmL5SlpC8YEjB7CA=BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc125000",
  "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",
  "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..."
}

01:01:58

exec getabnweight 125000

01:01:58

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 175797.7341666667,
  "total_required": 371227,
  "weight 125000.00": 128177.9095601852,
  "total_required 125000.00": 74733
}

-- a little later

01:15:44

getmininginfo

01:15:44

{
  "blocks": 130317,
  "currentblocksize": 3271,
  "currentblocktx": 1,
  "difficulty": 3677.54493643139,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 7,
  "networkhashps": 324545.4355387435,
  "hashps": 121125.9936056351,
  "minerstarttime": "07-07-2019 23:54:00",
  "hashcounter": 2338162764,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
  "poolinfo2": "RMC_07-08-2019 05:15:17; RM_07-08-2019 05:15:00; RMC_07-08-2019 05:15:01; ",
  "poolinfo3": "CFW 07-08-2019 05:15:17; CFW 07-08-2019 05:15:00; CFW 07-08-2019 05:15:01; ",
  "abninfo": "[125000 ABN OK] Amount=74733.00, Weight=132544.16; ",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "required_abn_weight": 125000
}

http://prntscr.com/obxfso

Screenshot of what I see

UPDATE: 9:56AM EST

Appears that miner is still mining strong, but not on the pool. left it on overnight 100% without resetting it.

Quote

09:56:35

getmininginfo

09:56:35

{
  "blocks": 130393,
  "currentblocksize": 11364,
  "currentblocktx": 16,
  "difficulty": 2955.198957214071,
  "errors": "",
  "pooledtx": 15,
  "chain": "main",
  "genproclimit": 7,
  "networkhashps": 372130.0120916371,
  "hashps": 117775.5137088829,
  "minerstarttime": "07-07-2019 23:54:00",
  "hashcounter": 5954088921,
  "pooledtx": 15,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "abninfo": "",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "required_abn_weight": 125000
}

09:56:40

exec getabnweight 125000 1

09:56:40

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 183923.064525463,
  "total_required": 371227,
  "coin_age_data_pre_select": "539.4800(0.98)=[528.86] depth=211, \n1.2670(2.35)=[2.35] depth=491, \n483.2776(1.30)=[629.62] depth=275, \n248.1900(0.93)=[230.14] depth=199, \n799.0000(2.02)=[1616.90] depth=422, \n5396.8587(2.56)=[13788.53] depth=532, \n5.2559(0.17)=[0.85] depth=41, \n67260.2075(0.17)=[11385.93] depth=41, \n1000.0000(9.52)=[9520.31] depth=1975, \n969.1900(5.98)=[5796.19] depth=1252, \n132947.8760(0.48)=[63386.79] depth=102, \n161576.6895(0.48)=[77036.59] depth=102, \n",
  "weight 125000.00": 183923.064525463,
  "total_required 125000.00": 371227
}

Update: Reset Windows miner @ 10:08AM EST, so I can start earning on the leaderboard again
Update: As of 11:18AM EST it appears that my miner fell from the leaderboard and is no longer on the pool again, but still mining.

Quote

11:18:35

getmininginfo

11:18:35

{
"blocks": 130405,
"currentblocksize": 2026,
"currentblocktx": 2,
"difficulty": 775.0927461642589,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 7,
"networkhashps": 357649.0856816549,
"hashps": 132768.2163555576,
"minerstarttime": "07-08-2019 14:08:34",
"hashcounter": 557687051,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RMC_07-08-2019 15:17:51; RMC_07-08-2019 15:17:49; RM_07-08-2019 15:17:49; ",
"poolinfo3": "CFW 07-08-2019 15:17:51; CFW 07-08-2019 15:17:49; CFW 07-08-2019 15:17:48; ",
"abninfo": "",
"gsc_errors": "",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}

11:30:06

getmininginfo

11:30:06

{
"blocks": 130407,
"currentblocksize": 1877,
"currentblocktx": 2,
"difficulty": 1436.494250413131,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 7,
"networkhashps": 358750.1958186541,
"hashps": 133332.6693198584,
"minerstarttime": "07-08-2019 14:08:34",
"hashcounter": 652192352,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RMC_07-08-2019 15:29:59; RMC_07-08-2019 15:30:00; ",
"poolinfo3": "CFW 07-08-2019 15:29:59; CFW 07-08-2019 15:30:00; ",
"abninfo": "",
"gsc_errors": "",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}

11:30:12

exec getabnweight 125000 1

11:30:12

{
"Command": "getabnweight",
"version": 1.2,
"weight": 210779.5870949074,
"total_required": 374472,
"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",
"weight 125000.00": 210779.5870949074,
"total_required 125000.00": 374472
}

11:30:26

{
"Command": "createabn",
"xml": "ABNd62df5c17a643247b48283fca544dcf5132d05c20196d79eeeadde212e3bc33dICffHpHJ1tF9eg7h1bMloqIkhBNfj8+W5YUIr468yVDpAfWQ4f1atZZIBHuwKddlAQ20fYp2aIbp9J59xtCgIO4=BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc125000",
"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",
"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..."
}

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Gilligan_M on July 07, 2019, 06:53:07 PM

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.

Quote

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",
"weight 125000.00": 142029.679849537,
"total_required 125000.00": 323153
}

20:03:14

exec createabn 125000 1

20:03:14

{
"Command": "createabn",
"xml": "ABNbfec7afc35f3bca25f5d78ca40d7aa8e987dcbab46d7f3a3ae7e5eebf0cca7b4H75UUbWR/kj2xAufY6yx6uCuk9RC1+J6p1lJf6E7ogC5LUZrtUh0BTsFLOADZqCm8wOMPlcs3MYngu2MyyYg1IY=BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc125000",
"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",
"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).

Gilligan_M

newbie

Activity: 28

Merit: 0

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.

Quote

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",
"weight 125000.00": 142029.679849537,
"total_required 125000.00": 323153
}

20:03:14

exec createabn 125000 1

20:03:14

{
"Command": "createabn",
"xml": "ABNbfec7afc35f3bca25f5d78ca40d7aa8e987dcbab46d7f3a3ae7e5eebf0cca7b4H75UUbWR/kj2xAufY6yx6uCuk9RC1+J6p1lJf6E7ogC5LUZrtUh0BTsFLOADZqCm8wOMPlcs3MYngu2MyyYg1IY=BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc125000",
"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",
"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.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Gilligan_M

newbie

Activity: 28

Merit: 0

New update: 3:45PM EST miner turns off "LOW ABN"

Quote

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",
  "weight 125000.00": 129872.9239930556,
  "total_required 125000.00": 340984
}

15:50:18

exec createabn 125000 1

15:50:19

{
  "Command": "createabn",
  "xml": "ABNf48468a258dfc369c81448559366993acb9c7dd77447567b870751a0bfd5f4d7IGsWYe2cfjDO3FW0W/ZAC979+Q7NVh8WriFA6crA1NMZCCsVMTc4gG0WbyFzfqSjyEXLrs4cBuJDw6/WXkUYi54=BKRvN9RQhgiN5y2A5EsjR9n7ySqEWkphwc125000",
  "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

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: realdantreccia on July 07, 2019, 02:06:46 PM

Can someone help me figure out why I have no hashps showing up?

Code:


{
  "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).

realdantreccia

hero member

Activity: 667

Merit: 517

Fuck BlackRock

Can someone help me figure out why I have no hashps showing up?

Code:

{
"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"?

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: harrisvan87 on July 07, 2019, 01:25:56 PM

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.

harrisvan87

newbie

Activity: 81

Merit: 0

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.

harrisvan87

newbie

Activity: 81

Merit: 0

Quote from: bible_pay on July 07, 2019, 01:12:26 PM

Quote from: harrisvan87 on July 07, 2019, 01:05:57 PM

Quote from: Gilligan_M on July 07, 2019, 11:58:28 AM

Quote from: harrisvan87 on July 07, 2019, 11:54:14 AM

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 check log saw during a week have Anonymus connected by TV Trojan. maybe they copy the wallet.dat and try decrypted. Because during this week we have some update SANC and Cold Wallet also need type passpharse. But if the screen was capture still ****** so maybe wallet was decrypted or keylogger.

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 124. (Read 243468 times)