BiblePay - New Coin Launch - Official Thread - page 83.

oliwer21

full member

Activity: 126

Merit: 100

Quote from: slovakia on September 13, 2017, 04:37:48 AM

what is Immature Balance on POOL?

Its "not confirmed" it should be mature in 24h and you can payoff it.

BTW 5k coins of reward per block on pool and huge drop of hash is worth of mine for small miners...
@inblue what is your best cpu on witch you got such big hash?
My profit per block droped from 200+ to round 30... feelsbadman
Have anyone noticed that pool adress had yesterday aditional sings when was opened?

slovakia

full member

Activity: 770

Merit: 100

Quote from: ?? on ??

I can not synchronize my wallet. I want to re-pump the blocks. Give please the list of nodes.

for me working this
addnode=node.biblepay.org
addnode=137.74.0.113
addnode=37.59.14.211
addnode=94.23.196.50
addnode=94.23.12.37
addnode=91.121.83.119
addnode=188.165.193.28

what is Immature Balance on POOL?

inblue

full member

Activity: 462

Merit: 103

I just discovered a very useful command:

Code:

getchaintips

Code:

[
{
"height": 7403,
"hash": "d4be35faa8907ea8ed864ae492c25c5671cc19863270fecf501fd592cada08ab",
"difficulty": 379.9904871916831,
"chainwork": "0000000000000000000000000000000000000000000000000001769fcb695cb4",
"branchlen": 0,
"status": "active"
},
{
"height": 7277,
"hash": "44b03913f666bf563146b63ebf2d5c3c985149128ab524d7d66f712cbe13fd33",
"difficulty": 0.001746781667724304,
"chainwork": "0000000000000000000000000000000000000000000000000000000b87bba393",
"branchlen": 252,
"status": "headers-only"
},
{
"height": 7195,
"hash": "fdda0190500497237aa7a02b7d7d3b0c6907a868e3e6a08e39f32b7846f4c826",
"difficulty": 0.004355675118676943,
"chainwork": "0000000000000000000000000000000000000000000000000000000d738715f2",
"branchlen": 54,
"status": "headers-only"
},
{
"height": 7181,
"hash": "67d46eea7155a4c112edc8d44cbeff178a2f000ebccde53f65a344355dbeb274",
"difficulty": 35.85249517036227,
"chainwork": "0000000000000000000000000000000000000000000000000000010ab91e7f44",
"branchlen": 1,
"status": "valid-headers"
},
{
"height": 7181,
"hash": "334491104c0108e1ef69f25e20f7ce881fd05ffe232035ca4fdbe5890b9a12df",
"difficulty": 35.85249517036227,
"chainwork": "0000000000000000000000000000000000000000000000000000010ab91e7f44",
"branchlen": 1,
"status": "valid-fork"
},
{
"height": 7178,
"hash": "ae1d4b1b6aac1313ed873278869cd92d68d3deab9140a0343b239ebc8d5b4621",
"difficulty": 0.00284443264647385,
"chainwork": "0000000000000000000000000000000000000000000000000000000d17095463",
"branchlen": 37,
"status": "headers-only"
},
{
"height": 7163,
"hash": "1f09f77b8b2d0d689effff01d1d7f181d85490b8cc6442a3f7fc92f315c4180c",
"difficulty": 0.001591352444876824,
"chainwork": "0000000000000000000000000000000000000000000000000000000d17ac5594",
"branchlen": 22,
"status": "headers-only"
},
{
"height": 7157,
"hash": "585b188cb78522c0c5b3a07d4cc893ed4378a8d74f987f0151e2d279f0457968",
"difficulty": 0.6628937306548522,
"chainwork": "0000000000000000000000000000000000000000000000000000000f7ea0fa13",
"branchlen": 16,
"status": "valid-fork"
},
{
"height": 7045,
"hash": "6c7371021d292252c030073f8b9faf69bf5ca136849202756315fff6c3a3d880",
"difficulty": 0.001775789883045804,
"chainwork": "0000000000000000000000000000000000000000000000000000000b7d7b39c8",
"branchlen": 9,
"status": "headers-only"
},
{
"height": 6109,
"hash": "0000055d3f5ba3c9b7fd615822555d7b4087455374da204830123f319b391d45",
"difficulty": 0.005306311368116459,
"chainwork": "00000000000000000000000000000000000000000000000000000008a849201f",
"branchlen": 1,
"status": "valid-headers"
},
{
"height": 5680,
"hash": "00000281a69a4f0d9c0c7ae7610736785205542a84331e035f7b97889702203f",
"difficulty": 0.006903401966151241,
"chainwork": "0000000000000000000000000000000000000000000000000000000792083d42",
"branchlen": 1,
"status": "valid-headers"
}
]

So does anyone have an idea what do these statuses mean? We have "active" (that one is pretty obvious), "headers-only", "valid-headers" and "valid-fork".

nananaminer

newbie

Activity: 42

Merit: 0

Quote from: seasonw on September 13, 2017, 03:43:35 AM

Quote from: nananaminer on September 13, 2017, 03:18:25 AM

Quote from: canonical on September 13, 2017, 02:27:21 AM

I've just taken a look at my workers for the first time today and it appears all my workers have been down for sometime. Restarting the daemon (I'm on linux) doesn't restart mining; something is wrong. I nuked one of the instances of biblepay that I have by deleting .biblepaycore (except biblepay.conf) and let the blockchain resync. Once sync'ed, it won't mine and gives "HEALTH_DOWN" when I check 'getmininginfo'.

Here's the latest extract from 'debug.log':

------
2017-09-13 06:17:27 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:17:27 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:17:27 Misbehaving: 45.76.85.130:40000 (50 -> 100) BAN THRESHOLD EXCEEDED
2017-09-13 06:20:53 ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7141.000000 pindexPrev 16265e604f37754bec$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (0 -> 50)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7142.000000 pindexPrev be3a96f7b585a3c6e3$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (50 -> 100) BAN THRESHOLD EXCEEDED
------

Reading the previous posts, this isn't quite the same as what other people have reported. I 'clearbanned' like someone else mentioned, but it doesnt seem to change anything. 'Thoughts?

I have both of these problems lol. My miners constantly go off the pool and I think they are not reverting to solo mining, because it still says poolmining=true, but the pool doesn't recognize them. When I restart them, they go on the pool briefly and then drop again.

Same problem for me since yesterday. Been pulling the miners online every half hour before they go offline. Doesn't switch to solo mining either.
Dev is doing a great job but wish all the changes such as algo, difficulty adjustments etc were first tested on the testnet first before multiple mandatory fixes.
Also not sure what the pool's reward system is like right now, seems erratic.

@bible_pay Any chance of fixing the difficulty adjustment sooner, the difficulty is increasing exponentially and block rewards are at 25% now.

Yes, I agreed that fixing of block rewards should be the top priority, because it is too low now.

And I would think after this lesson, dev really have to test any changes in testnet before release it, there are too many unknown issues occurred. I don't mean to criticize and I really appreciate dev's effort, I think dev must be busy on fixing these issues now Grin

Glad all of us are agreeing on this.
Dev is doing a tremendous job, his openness and commitment to the project is the reason I started engaging with BiblePay in the first place.
Hope the dev finds time to get through these fixes.

inblue

full member

Activity: 462

Merit: 103

Quote from: nananaminer on September 13, 2017, 03:35:40 AM

Quote from: inblue on September 13, 2017, 03:25:15 AM

Quote from: nananaminer on September 13, 2017, 03:18:25 AM

@bible_pay Any chance of fixing the difficulty adjustment sooner, the difficulty is increasing exponentially and block rewards are at 25% now.

No, it's better that rewards are as small as possible.

Because:

Quote from: bible_pay on September 12, 2017, 09:34:34 AM

At this point we are harder to mine, and have less reward per block, so the exchange being a free market should take that into account and BBP may increase in value.

Definitely understand the supply vs demand side but at the same time the difficulty bug will eventually will be fixed in few months and when its back to 20k rewards, the equation will change. Current situation is good for short time gain but in order for the coin to prolong through years it has to have consistency.

You should read the dev's post here, it certainly isn't a bug but an intended feature, only it's less than the dev imagined. TLDR: He said it will be left like that and that a slight adjustment could be made sometime in the future, if necessary. So I doubt there will be 20k rewards again.

seasonw

hero member

Activity: 714

Merit: 500

Quote from: nananaminer on September 13, 2017, 03:18:25 AM

Quote from: canonical on September 13, 2017, 02:27:21 AM

I've just taken a look at my workers for the first time today and it appears all my workers have been down for sometime. Restarting the daemon (I'm on linux) doesn't restart mining; something is wrong. I nuked one of the instances of biblepay that I have by deleting .biblepaycore (except biblepay.conf) and let the blockchain resync. Once sync'ed, it won't mine and gives "HEALTH_DOWN" when I check 'getmininginfo'.

Here's the latest extract from 'debug.log':

------
2017-09-13 06:17:27 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:17:27 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:17:27 Misbehaving: 45.76.85.130:40000 (50 -> 100) BAN THRESHOLD EXCEEDED
2017-09-13 06:20:53 ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7141.000000 pindexPrev 16265e604f37754bec$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (0 -> 50)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7142.000000 pindexPrev be3a96f7b585a3c6e3$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (50 -> 100) BAN THRESHOLD EXCEEDED
------

Reading the previous posts, this isn't quite the same as what other people have reported. I 'clearbanned' like someone else mentioned, but it doesnt seem to change anything. 'Thoughts?

I have both of these problems lol. My miners constantly go off the pool and I think they are not reverting to solo mining, because it still says poolmining=true, but the pool doesn't recognize them. When I restart them, they go on the pool briefly and then drop again.

Same problem for me since yesterday. Been pulling the miners online every half hour before they go offline. Doesn't switch to solo mining either.
Dev is doing a great job but wish all the changes such as algo, difficulty adjustments etc were first tested on the testnet first before multiple mandatory fixes.
Also not sure what the pool's reward system is like right now, seems erratic.

@bible_pay Any chance of fixing the difficulty adjustment sooner, the difficulty is increasing exponentially and block rewards are at 25% now.

Yes, I agreed that fixing of block rewards should be the top priority, because it is too low now.

And I would think after this lesson, dev really have to test any changes in testnet before release it, there are too many unknown issues occurred. I don't mean to criticize and I really appreciate dev's effort, I think dev must be busy on fixing these issues now Grin

nananaminer

newbie

Activity: 42

Merit: 0

Quote from: inblue on September 13, 2017, 03:25:15 AM

Quote from: nananaminer on September 13, 2017, 03:18:25 AM

@bible_pay Any chance of fixing the difficulty adjustment sooner, the difficulty is increasing exponentially and block rewards are at 25% now.

No, it's better that rewards are as small as possible.

Because:

Quote from: bible_pay on September 12, 2017, 09:34:34 AM

At this point we are harder to mine, and have less reward per block, so the exchange being a free market should take that into account and BBP may increase in value.

Definitely understand the supply vs demand side but at the same time the difficulty bug will eventually will be fixed in few months and when its back to 20k rewards, the equation will change. Current situation is good for short time gain but in order for the coin to prolong through years it has to have consistency.

Looks like my miners went to solo as well when it got dropped from the pool and mined a few blocks.
What's the command to see all the block mined by a certain daemon?

inblue

full member

Activity: 462

Merit: 103

Quote from: nananaminer on September 13, 2017, 03:18:25 AM

@bible_pay Any chance of fixing the difficulty adjustment sooner, the difficulty is increasing exponentially and block rewards are at 25% now.

No, it's better that rewards are as small as possible.

Because:

Quote from: bible_pay on September 12, 2017, 09:34:34 AM

At this point we are harder to mine, and have less reward per block, so the exchange being a free market should take that into account and BBP may increase in value.

inblue

full member

Activity: 462

Merit: 103

One of the miners seem to have switched to solo mining since it found a block, and I've discovered a new error:

Code:

2017-09-13 07:15:00 generated 5000.00
2017-09-13 07:15:00 89UpdateTip: new best=e900b62013cea73df955c0edc8f56f56af5439acc8020970191bba58f4760344  height=7374  log2_work=48.185504  tx=11349  date=2017-09-13 07:14:50 progress=0.999999  cache=0.0MiB(1tx)
2017-09-13 07:15:00 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.

nananaminer

newbie

Activity: 42

Merit: 0

Quote from: canonical on September 13, 2017, 02:27:21 AM

I've just taken a look at my workers for the first time today and it appears all my workers have been down for sometime. Restarting the daemon (I'm on linux) doesn't restart mining; something is wrong. I nuked one of the instances of biblepay that I have by deleting .biblepaycore (except biblepay.conf) and let the blockchain resync. Once sync'ed, it won't mine and gives "HEALTH_DOWN" when I check 'getmininginfo'.

Here's the latest extract from 'debug.log':

------
2017-09-13 06:17:27 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:17:27 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:17:27 Misbehaving: 45.76.85.130:40000 (50 -> 100) BAN THRESHOLD EXCEEDED
2017-09-13 06:20:53 ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7141.000000 pindexPrev 16265e604f37754bec$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (0 -> 50)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7142.000000 pindexPrev be3a96f7b585a3c6e3$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (50 -> 100) BAN THRESHOLD EXCEEDED
------

Reading the previous posts, this isn't quite the same as what other people have reported. I 'clearbanned' like someone else mentioned, but it doesnt seem to change anything. 'Thoughts?

I have both of these problems lol. My miners constantly go off the pool and I think they are not reverting to solo mining, because it still says poolmining=true, but the pool doesn't recognize them. When I restart them, they go on the pool briefly and then drop again.

Same problem for me since yesterday. Been pulling the miners online every half hour before they go offline. Doesn't switch to solo mining either.
Dev is doing a great job but wish all the changes such as algo, difficulty adjustments etc were first tested on the testnet first before multiple mandatory fixes.
Also not sure what the pool's reward system is like right now, seems erratic.

@bible_pay Any chance of fixing the difficulty adjustment sooner, the difficulty is increasing exponentially and block rewards are at 25% now.

inblue

full member

Activity: 462

Merit: 103

Quote from: tiras on September 12, 2017, 04:09:24 PM

Quote from: inblue on September 12, 2017, 03:32:47 PM

Quote from: m4tsby on September 12, 2017, 03:27:26 PM

You dont happen to have that Xubuntu setup do you? Im still unable to run. I could send you some BBP!

I keep getting this error:
make: *** No targets specified and no makefile found. Stop.

Not sure where the holdup is. I tried in /Biblepay and in /SRC..made sure I was sudo.. linux new to me however.

Before make you need to run ./autogen.sh and ./configure

@inblue , which linux distro are you using for BBP miner ?

Ubuntu 16.04.2 LTS (amd64)

seasonw

hero member

Activity: 714

Merit: 500

Quote from: inblue on September 13, 2017, 02:36:23 AM

Quote from: cryptocurrencyfreak on September 13, 2017, 02:16:35 AM

My linux miners show up briefly once started but eventually disappear from the pool website. These are the last few logs:

Code:

2017-09-13 05:49:40 89UpdateTip: new best=13db8243c2bdc0778c90b4570eda7ec1469daf435fa5f9da10e7ae1d9513d84$
2017-09-13 05:49:40 ProcessNewBlock : ACCEPTED
2017-09-13 05:49:46 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$
2017-09-13 05:50:45 connection from 175.204.123.147:51971 dropped (banned)
2017-09-13 05:51:34 DGW: Height 7392.000000, NewDiff 1b54a84f     nActualTimespan 1134.000000    nTargetT$
2017-09-13 05:52:09 connection from 218.71.239.70:57766 dropped (banned)
2017-09-13 05:53:41 ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 5478.000000 $
2017-09-13 05:53:41 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=1999285)
** ProcessGetData:Cannot load block from disk.
2017-09-13 06:01:23 DGW: Height 7392.000000, NewDiff 1b54a84f     nActualTimespan 1134.000000    nTargetT$
2017-09-13 06:02:47 connection from 218.71.239.70:57994 dropped (banned)
2017-09-13 06:05:26 connection from 77.106.146.145:54432 dropped (banned)
2017-09-13 06:05:31 89UpdateTip: new best=e45940fec237f88b0ee2a6f30d89d1875764f6a4ffe4180b52cbf03560ba874$
2017-09-13 06:05:31 ProcessNewBlock : ACCEPTED
2017-09-13 06:05:37 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$
2017-09-13 06:09:47 connection from 175.204.123.147:52249 dropped (banned)
2017-09-13 06:12:34 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 7392.00000$
2017-09-13 06:12:34 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3283261)Upda$
2017-09-13 06:12:34 ProcessNewBlock : ACCEPTED
2017-09-13 06:12:40 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$
2017-09-13 06:13:15 ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, pre$
2017-09-13 06:13:15 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:13:15 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (0 -> 50)
2017-09-13 06:13:15 ERROR: invalid header received 1f317d504e22a10b34d0a48334babd030c96265d5150b0129c9649$
2017-09-13 06:13:15 ProcessMessages(headers, 28677 bytes) FAILED peer=75
2017-09-13 06:13:44 ERROR:
CheckProofOfWork(): hash doesn't meet X11 POW Level, Prod 1.000000, Network main, PrevHeight 0

2017-09-13 06:13:44 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:13:44 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (50 -> 100) BAN THRESHOLD E$
2017-09-13 06:13:44 ERROR: invalid header received 9002b29834f151df58cd77f3cccb1b34e35c2e1bd1110cffa237ab$
2017-09-13 06:13:44 ProcessMessages(headers, 82 bytes) FAILED peer=75

Quote from: canonical on September 13, 2017, 02:27:21 AM

I've just taken a look at my workers for the first time today and it appears all my workers have been down for sometime. Restarting the daemon (I'm on linux) doesn't restart mining; something is wrong. I nuked one of the instances of biblepay that I have by deleting .biblepaycore (except biblepay.conf) and let the blockchain resync. Once sync'ed, it won't mine and gives "HEALTH_DOWN" when I check 'getmininginfo'.

Here's the latest extract from 'debug.log':

------
2017-09-13 06:17:27 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:17:27 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:17:27 Misbehaving: 45.76.85.130:40000 (50 -> 100) BAN THRESHOLD EXCEEDED
2017-09-13 06:20:53 ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7141.000000 pindexPrev 16265e604f37754bec$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (0 -> 50)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7142.000000 pindexPrev be3a96f7b585a3c6e3$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (50 -> 100) BAN THRESHOLD EXCEEDED
------

Reading the previous posts, this isn't quite the same as what other people have reported. I 'clearbanned' like someone else mentioned, but it doesnt seem to change anything. 'Thoughts?

I have both of these problems lol. My miners constantly go off the pool and I think they are not reverting to solo mining, because it still says poolmining=true, but the pool doesn't recognize them. When I restart them, they go on the pool briefly and then drop again.

Same issue happened to me on my ubuntu. After fixing the pool ip banning issue, now this is the cause that make my miner go off the pool. Same thought as inblue did, I don't think it reverted to solo mining. So, I have stopped some of my miners.

inblue

full member

Activity: 462

Merit: 103

Quote from: cryptocurrencyfreak on September 13, 2017, 02:16:35 AM

My linux miners show up briefly once started but eventually disappear from the pool website. These are the last few logs:

Code:

2017-09-13 05:49:40 89UpdateTip: new best=13db8243c2bdc0778c90b4570eda7ec1469daf435fa5f9da10e7ae1d9513d84$
2017-09-13 05:49:40 ProcessNewBlock : ACCEPTED
2017-09-13 05:49:46 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$
2017-09-13 05:50:45 connection from 175.204.123.147:51971 dropped (banned)
2017-09-13 05:51:34 DGW: Height 7392.000000, NewDiff 1b54a84f     nActualTimespan 1134.000000    nTargetT$
2017-09-13 05:52:09 connection from 218.71.239.70:57766 dropped (banned)
2017-09-13 05:53:41 ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 5478.000000 $
2017-09-13 05:53:41 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=1999285)
** ProcessGetData:Cannot load block from disk.
2017-09-13 06:01:23 DGW: Height 7392.000000, NewDiff 1b54a84f     nActualTimespan 1134.000000    nTargetT$
2017-09-13 06:02:47 connection from 218.71.239.70:57994 dropped (banned)
2017-09-13 06:05:26 connection from 77.106.146.145:54432 dropped (banned)
2017-09-13 06:05:31 89UpdateTip: new best=e45940fec237f88b0ee2a6f30d89d1875764f6a4ffe4180b52cbf03560ba874$
2017-09-13 06:05:31 ProcessNewBlock : ACCEPTED
2017-09-13 06:05:37 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$
2017-09-13 06:09:47 connection from 175.204.123.147:52249 dropped (banned)
2017-09-13 06:12:34 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 7392.00000$
2017-09-13 06:12:34 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3283261)Upda$
2017-09-13 06:12:34 ProcessNewBlock : ACCEPTED
2017-09-13 06:12:40 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$
2017-09-13 06:13:15 ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, pre$
2017-09-13 06:13:15 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:13:15 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (0 -> 50)
2017-09-13 06:13:15 ERROR: invalid header received 1f317d504e22a10b34d0a48334babd030c96265d5150b0129c9649$
2017-09-13 06:13:15 ProcessMessages(headers, 28677 bytes) FAILED peer=75
2017-09-13 06:13:44 ERROR:
CheckProofOfWork(): hash doesn't meet X11 POW Level, Prod 1.000000, Network main, PrevHeight 0

2017-09-13 06:13:44 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:13:44 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (50 -> 100) BAN THRESHOLD E$
2017-09-13 06:13:44 ERROR: invalid header received 9002b29834f151df58cd77f3cccb1b34e35c2e1bd1110cffa237ab$
2017-09-13 06:13:44 ProcessMessages(headers, 82 bytes) FAILED peer=75

Quote from: canonical on September 13, 2017, 02:27:21 AM

I've just taken a look at my workers for the first time today and it appears all my workers have been down for sometime. Restarting the daemon (I'm on linux) doesn't restart mining; something is wrong. I nuked one of the instances of biblepay that I have by deleting .biblepaycore (except biblepay.conf) and let the blockchain resync. Once sync'ed, it won't mine and gives "HEALTH_DOWN" when I check 'getmininginfo'.

Here's the latest extract from 'debug.log':

------
2017-09-13 06:17:27 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:17:27 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:17:27 Misbehaving: 45.76.85.130:40000 (50 -> 100) BAN THRESHOLD EXCEEDED
2017-09-13 06:20:53 ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7141.000000 pindexPrev 16265e604f37754bec$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (0 -> 50)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7142.000000 pindexPrev be3a96f7b585a3c6e3$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (50 -> 100) BAN THRESHOLD EXCEEDED
------

Reading the previous posts, this isn't quite the same as what other people have reported. I 'clearbanned' like someone else mentioned, but it doesnt seem to change anything. 'Thoughts?

I have both of these problems lol. My miners constantly go off the pool and I think they are not reverting to solo mining, because it still says poolmining=true, but the pool doesn't recognize them. When I restart them, they go on the pool briefly and then drop again.

canonical

full member

Activity: 136

Merit: 100

I've just taken a look at my workers for the first time today and it appears all my workers have been down for sometime. Restarting the daemon (I'm on linux) doesn't restart mining; something is wrong. I nuked one of the instances of biblepay that I have by deleting .biblepaycore (except biblepay.conf) and let the blockchain resync. Once sync'ed, it won't mine and gives "HEALTH_DOWN" when I check 'getmininginfo'.

Here's the latest extract from 'debug.log':

------
2017-09-13 06:17:27 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:17:27 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:17:27 Misbehaving: 45.76.85.130:40000 (50 -> 100) BAN THRESHOLD EXCEEDED
2017-09-13 06:20:53 ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7141.000000 pindexPrev 16265e604f37754bec$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (0 -> 50)
2017-09-13 06:20:54 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7142.000000 pindexPrev be3a96f7b585a3c6e3$
2017-09-13 06:20:54 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:20:54 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 06:20:54 Misbehaving: 149.56.43.244:57462 (50 -> 100) BAN THRESHOLD EXCEEDED
------

Reading the previous posts, this isn't quite the same as what other people have reported. I 'clearbanned' like someone else mentioned, but it doesnt seem to change anything. 'Thoughts?

cryptocurrencyfreak

newbie

Activity: 37

Merit: 0

My linux miners show up briefly once started but eventually disappear from the pool website. These are the last few logs:

Code:

2017-09-13 05:49:40 89UpdateTip: new best=13db8243c2bdc0778c90b4570eda7ec1469daf435fa5f9da10e7ae1d9513d84$
2017-09-13 05:49:40 ProcessNewBlock : ACCEPTED
2017-09-13 05:49:46 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$
2017-09-13 05:50:45 connection from 175.204.123.147:51971 dropped (banned)
2017-09-13 05:51:34 DGW: Height 7392.000000, NewDiff 1b54a84f     nActualTimespan 1134.000000    nTargetT$
2017-09-13 05:52:09 connection from 218.71.239.70:57766 dropped (banned)
2017-09-13 05:53:41 ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 5478.000000 $
2017-09-13 05:53:41 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=1999285)
** ProcessGetData:Cannot load block from disk.
2017-09-13 06:01:23 DGW: Height 7392.000000, NewDiff 1b54a84f     nActualTimespan 1134.000000    nTargetT$
2017-09-13 06:02:47 connection from 218.71.239.70:57994 dropped (banned)
2017-09-13 06:05:26 connection from 77.106.146.145:54432 dropped (banned)
2017-09-13 06:05:31 89UpdateTip: new best=e45940fec237f88b0ee2a6f30d89d1875764f6a4ffe4180b52cbf03560ba874$
2017-09-13 06:05:31 ProcessNewBlock : ACCEPTED
2017-09-13 06:05:37 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$
2017-09-13 06:09:47 connection from 175.204.123.147:52249 dropped (banned)
2017-09-13 06:12:34 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 7392.00000$
2017-09-13 06:12:34 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3283261)Upda$
2017-09-13 06:12:34 ProcessNewBlock : ACCEPTED
2017-09-13 06:12:40 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we ar$
2017-09-13 06:13:15 ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, pre$
2017-09-13 06:13:15 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:13:15 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (0 -> 50)
2017-09-13 06:13:15 ERROR: invalid header received 1f317d504e22a10b34d0a48334babd030c96265d5150b0129c9649$
2017-09-13 06:13:15 ProcessMessages(headers, 28677 bytes) FAILED peer=75
2017-09-13 06:13:44 ERROR:
CheckProofOfWork(): hash doesn't meet X11 POW Level, Prod 1.000000, Network main, PrevHeight 0

2017-09-13 06:13:44 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 06:13:44 Misbehaving: [2001:0:9d38:6abd:30d5:3e2e:5033:846c]:11527 (50 -> 100) BAN THRESHOLD E$
2017-09-13 06:13:44 ERROR: invalid header received 9002b29834f151df58cd77f3cccb1b34e35c2e1bd1110cffa237ab$
2017-09-13 06:13:44 ProcessMessages(headers, 82 bytes) FAILED peer=75

slovakia

full member

Activity: 770

Merit: 100

Quote from: Ginzink on September 13, 2017, 12:37:35 AM

Hi,

I sendt biblepay from pool and my wallet to C-Cex yesterday but they have not showed up yet. Starting to get worried. I have double checked and wallet address is correct and matching my ledger in C-Cex.
It is confirmed with over 80 confirmations according to my wallet.
Transaction ID.
28a82d9638da94be05512400d309deb54f5a2a3fb46d48804a07ec0fca28dd06-000

CCEX Their wallets is Out of sync

Ginzink

full member

Activity: 462

Merit: 118

Hi,

I sendt biblepay from pool and my wallet to C-Cex yesterday but they have not showed up yet. Starting to get worried. I have double checked and wallet address is correct and matching my ledger in C-Cex.
It is confirmed with over 80 confirmations according to my wallet.
Transaction ID.
28a82d9638da94be05512400d309deb54f5a2a3fb46d48804a07ec0fca28dd06-000

slovakia

full member

Activity: 770

Merit: 100

NetDiff is brutal and growing to the moon hahahaha......

bible_pay pool didnt mine no block? Roll Eyes

this is real rewards for blocks or cos my wallet is still empty

seasonw

hero member

Activity: 714

Merit: 500

My ubuntu miner keep banning pool ip, and I always get 0 hashrate in the pool. I have removed the banlist.dat and restart my biblepayd with whitelist:

Code:

biblepay/src/biblepayd -whitelist=108.61.204.234 -daemon

But after some time, I still see 108.61.204.234 being banned in debug.log. Any clue?

seasonw

hero member

Activity: 714

Merit: 500

Quote from: bible_pay on September 12, 2017, 08:31:22 PM

Quote from: seasonw on September 12, 2017, 07:59:33 PM

Quote from: bible_pay on September 12, 2017, 07:45:28 PM

Quote from: seasonw on September 12, 2017, 07:30:46 PM

Pool is having problem in last few hours, some of my miners dropped from pool. The message in miner did not show revert to solo mining, but somehow 1 of my machine manage to mine a block Grin

I found inconsistent block rewards, usually it was nearly 20000 (199xx), but why sometimes I have 20000, and the last mined block get only 5832?

About 30 minutes ago I was monkeying with the sessionstate and it knocked everyone off for about 15 mins, they are all back, lucking the block was solved 1 minute before they got booted.

Anyway, unrelated to that, the low reward is happening now due to the diff > 300. See the prior forum page we were discussing that this morning.

One miner pointed 100 servers at the pool today.

Oh I see, so any problem with the diff value or this is normal due to large network hashrate now? (Sorry I have searched a few page back on this thread but did not find the discussion about this, just ignore me if it was answered)

And wow, big miners are coming now, biblepay is getting popular Grin

I think its partially due to the algorithm change. I believe the algorithm change increased the diff from .05 to 100.00. The other part from 100-400 or so is probably the miner with 100 servers. I'll try to add a few more metrics to the pool that show total miner participation, total kh/s, and things like that. Then maybe Happy can jump in and formulate a change for the call to networkhashps.

The code was already in GetBlockSubsidy to lower the subsidy when the diff rises, but it was never expected to rise from .01 to 500, I actually expected the subsidy to drop to about 17000 between now and Christmas. So we might have to adjust that slightly in the next mandatory.

Noted, thanks for your effort and detailed explanation, dev. Hoping great success to biblepay Wink

Topic: BiblePay - New Coin Launch - Official Thread - page 83. (Read 119833 times)