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

[togoshigekata]

Starting to update things,
What is the current block reward breakdown?

===

Is the Issues feature enabled on the latest github?
https://github.com/biblepay/biblepay-evolution

[miningguru]

I have no clue if this is the case but I have a sneaky suspicion CCEX might be the big seller on SX - as they had about 20 mil in the wallet.

Why it seems you cannot manage to list the coin in higher volume exchanges because if you won't bother listing then it will really hurt, the price will keep going down in the market.

[MIP]

I have no clue if this is the case but I have a sneaky suspicion CCEX might be the big seller on SX - as they had about 20 mil in the wallet.

Why it seems you cannot manage to list the coin in higher volume exchanges because if you won't bother listing then it will really hurt, the price will keep going down in the market.

We listed in other exchanges like Cryptobridge and never had the same volume than in CCex. Then SouthX continued but the question is if listing in a bigger exchange is going to help.

Which ones would you recommend?

[capulo]

hmm, all cpus on 100%, but hash counter and hps looks like frozen...
all computers have in log something like this (few hours no logs)
2019-06-28 11:38:51 ERROR: invalid header received
2019-06-28 11:38:51 ProcessMessages(headers, 162003 bytes) FAILED peer=15
2019-06-28 11:40:40 UpdateTip: new best=752dc4fc33500f43efa4b329bc0f4ef9961eb719bec22240814fb04415ce2e8f height=128310 version=0x2000000c log2_work=59.49476449 tx=1084070 date='2019-06-28 11:40:40' progress=1.000000 cache=0.0MiB(0txo)
2019-06-28 11:40:40 {PNB}: ACC  UpdateTip: new best=42d20a56cc4d004cd0a6c2b86a029569ce0b04f993cb326e5e9c6cfacf526ccb height=128311 version=0x2000000c log2_work=59.49478812 tx=1084071 date='2019-06-28 11:45:00' progress=1.000000 cache=0.0
MiB(0txo)
2019-06-28 11:45:01 {PNB}: ACC  CGovernanceManager::ProcessVote -- Unknown parent object 4a043c7edf65e99e7efc85dfa69bcd75595a2612c7fb65593d498b83758d6343, MN outpoint = 947a00fcdea075191232618e5c0bac9d12f0ecf8b1b106c07e98bd44de7760b7-1
2019-06-28 11:45:03 CGovernanceManager::MasternodeRateCheck -- Rate too high: object hash = 4a043c7edf65e99e7efc85dfa69bcd75595a2612c7fb65593d498b83758d6343, masternode = 947a00fcdea075191232618e5c0bac9d12f0ecf8b1b106c07e98bd44de7760b7-1
, object timestamp = 1561683839, rate = 0.000011, max rate = 0.000004
2019-06-28 11:45:03 MNGOVERNANCEOBJECT -- masternode rate check failed (after signature verification) - 4a043c7edf65e99e7efc85dfa69bcd75595a2612c7fb65593d498b83758d6343 - (current block height 128311)
2019-06-28 11:45:03 CGovernanceManager::ProcessVote -- Unknown parent object ef436eeaafea35f802e0e32d33e2f7a0d1f1ea15d5ae8ec27fbe77db307acd46, MN outpoint = 434f4baab9ecae5cd66436ac7b24db45417d49ebc1493c30987325536c067290-1
2019-06-28 11:45:05 CGovernanceManager::ProcessVote -- Unknown parent object caba0c2662e7d39745a5d90e8c28317b93e2e8d3376a77a093edad3d0116fd44, MN outpoint = 327855c76b14a1b052232db301d1fe4fced19bdc00dfdf0a3d326146f95c8d88-1
2019-06-28 11:45:07 CGovernanceManager::ProcessVote -- Unknown parent object 14d20b1fa74e5cc8313f19f2162faed5f24d75f0557de39db46b6f7c7ee338f2, MN outpoint = c6b8d8dcda70ac5a376a8c93fc2c392b6cbd103694ba2fec1548f8739d23e857-1
2019-06-28 11:45:28 ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: c982c3e05e4b59a9b559e26600e56bc621c8baa158439d63f7e4e5b97488125a, high-hash, proof of work failed (code 16)
2019-06-28 11:45:28 Misbehaving: 95.179.169.44:40000 peer=15 (91 -> 96)
2019-06-28 11:45:28 ERROR: invalid header received
2019-06-28 11:45:28 ProcessMessages(headers, 162003 bytes) FAILED peer=15
2019-06-28 11:46:11 ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: c982c3e05e4b59a9b559e26600e56bc621c8baa158439d63f7e4e5b97488125a, high-hash, proof of work failed (code 16)
2019-06-28 11:46:11 Misbehaving: 95.179.169.44:40000 peer=15 (96 -> 101) BAN THRESHOLD EXCEEDED
2019-06-28 11:46:11 ERROR: invalid header received
2019-06-28 11:46:11 ProcessMessages(headers, 162003 bytes) FAILED peer=15
2019-06-28 11:54:27 UpdateTip: new best=64dad8fc41f6e1831396c555c09ce184024ad83f6c463089f6092796a4141f85 height=128312 version=0x2000000c log2_work=59.49480937 tx=1084073 date='2019-06-28 11:54:26' progress=1.000000 cache=0.0MiB(0txo)
2019-06-28 11:54:27 {PNB}: ACC  CGovernanceManager::ProcessVote -- Unknown parent object 14ff4feb7d015a84f2d9565c7845237127bc9163ab9df190037b71f95fa14fbc, MN outpoint = 11c1ca208005e2b325a8ec544432d18afb4ef3b2e76d82761747ea438a0b0f54-1
2019-06-28 11:58:34 CGovernanceManager::SyncSingleObjAndItsVotes -- not syncing deleted/expired govobj: 051aee71db51fe4ac470ec65aaed9d13708b6e91dcdfb2ad182e05cd779065ae, peer=20
2019-06-28 11:58:36 CGovernanceManager::SyncSingleObjAndItsVotes -- not syncing deleted/expired govobj: 9800a21d825d0b40509dd993757d5380aa8a0f6282f3e5fc6532c6a1d8225371, peer=0
2019-06-28 12:07:47 UpdateTip: new best=c4658f4af2386c4ab444442d0dafb5dae2727d3f2d2730f637e954795fd70be0 height=128313 version=0x2000000c log2_work=59.49483398 tx=1084077 date='2019-06-28 12:07:56' progress=1.000000 cache=0.0MiB(0txo)
2019-06-28 12:07:47 {PNB}: ACC
 

[Sakic]

Yes Its frozen, I have same things in log, no block mined for 15 hours

[thesnat21]

I have no clue if this is the case but I have a sneaky suspicion CCEX might be the big seller on SX - as they had about 20 mil in the wallet.

Ouch I really hope that is not the case, but it did seem that C-CEX was doing an exit scam of some sort... 

[bible_pay]

Starting to update things,
What is the current block reward breakdown?

===

Is the Issues feature enabled on the latest github?
https://github.com/biblepay/biblepay-evolution

Current Block Reward - I have updated the wiki page (whew, we needed that):
https://wiki.biblepay.org/Economics

Issues Feature in BiblePay-Evolution branch - I have enabled issues and features:
https://github.com/biblepay/biblepay-evolution/issues

Thanks, lets make BiblePay Rock solid now.

[bible_pay]

I have no clue if this is the case but I have a sneaky suspicion CCEX might be the big seller on SX - as they had about 20 mil in the wallet.

Ouch I really hope that is not the case, but it did seem that C-CEX was doing an exit scam of some sort... 

Well, yes, that's scathing, but from their perspective, they had a 24 million BBP 'house balance'.  They posted a notice that they will be leaving by June 1st for re-organization, that everyone should withdraw the coins (as after this date, withdrawals will not be possible).  Whatever is left in the house balance after that date, they consider to be their assets.

So from their perspective they are probably liquidating and keeping the BTC.

But, know that I myself in no way shape or form would ever do this to anyone.  If I had an exchange I would allow 6 months to withdraw and I would be sending daily e-mails saying come and get your balance as these aren't my funds.

[bible_pay]

Yes Its frozen, I have same things in log, no block mined for 15 hours

Let me run my global report and verify we are rock solid, hang on.

[bible_pay]

Code:

hmm, all cpus on 100%, but hash counter and hps looks like frozen...
all computers have in log something like this (few hours no logs)
2019-06-28 11:38:51 ERROR: invalid header received
2019-06-28 11:38:51 ProcessMessages(headers, 162003 bytes) FAILED peer=15
2019-06-28 11:40:40 UpdateTip: new best=752dc4fc33500f43efa4b329bc0f4ef9961eb719bec22240814fb04415ce2e8f height=128310 version=0x2000000c log2_work=59.49476449 tx=1084070 date='2019-06-28 11:40:40' progress=1.000000 cache=0.0MiB(0txo)
2019-06-28 11:40:40 {PNB}: ACC  UpdateTip: new best=42d20a56cc4d004cd0a6c2b86a029569ce0b04f993cb326e5e9c6cfacf526ccb height=128311 version=0x2000000c log2_work=59.49478812 tx=1084071 date='2019-06-28 11:45:00' progress=1.000000 cache=0.0
MiB(0txo)
2019-06-28 11:45:01 {PNB}: ACC  CGovernanceManager::ProcessVote -- Unknown parent object 4a043c7edf65e99e7efc85dfa69bcd75595a2612c7fb65593d498b83758d6343, MN outpoint = 947a00fcdea075191232618e5c0bac9d12f0ecf8b1b106c07e98bd44de7760b7-1
2019-06-28 11:45:03 CGovernanceManager::MasternodeRateCheck -- Rate too high: object hash = 4a043c7edf65e99e7efc85dfa69bcd75595a2612c7fb65593d498b83758d6343, masternode = 947a00fcdea075191232618e5c0bac9d12f0ecf8b1b106c07e98bd44de7760b7-1
, object timestamp = 1561683839, rate = 0.000011, max rate = 0.000004
2019-06-28 11:45:03 MNGOVERNANCEOBJECT -- masternode rate check failed (after signature verification) - 4a043c7edf65e99e7efc85dfa69bcd75595a2612c7fb65593d498b83758d6343 - (current block height 128311)
2019-06-28 11:45:03 CGovernanceManager::ProcessVote -- Unknown parent object ef436eeaafea35f802e0e32d33e2f7a0d1f1ea15d5ae8ec27fbe77db307acd46, MN outpoint = 434f4baab9ecae5cd66436ac7b24db45417d49ebc1493c30987325536c067290-1
2019-06-28 11:45:05 CGovernanceManager::ProcessVote -- Unknown parent object caba0c2662e7d39745a5d90e8c28317b93e2e8d3376a77a093edad3d0116fd44, MN outpoint = 327855c76b14a1b052232db301d1fe4fced19bdc00dfdf0a3d326146f95c8d88-1
2019-06-28 11:45:07 CGovernanceManager::ProcessVote -- Unknown parent object 14d20b1fa74e5cc8313f19f2162faed5f24d75f0557de39db46b6f7c7ee338f2, MN outpoint = c6b8d8dcda70ac5a376a8c93fc2c392b6cbd103694ba2fec1548f8739d23e857-1
2019-06-28 11:45:28 ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: c982c3e05e4b59a9b559e26600e56bc621c8baa158439d63f7e4e5b97488125a, high-hash, proof of work failed (code 16)
2019-06-28 11:45:28 Misbehaving: 95.179.169.44:40000 peer=15 (91 -> 96)
2019-06-28 11:45:28 ERROR: invalid header received
2019-06-28 11:45:28 ProcessMessages(headers, 162003 bytes) FAILED peer=15
2019-06-28 11:46:11 ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: c982c3e05e4b59a9b559e26600e56bc621c8baa158439d63f7e4e5b97488125a, high-hash, proof of work failed (code 16)
2019-06-28 11:46:11 Misbehaving: 95.179.169.44:40000 peer=15 (96 -> 101) BAN THRESHOLD EXCEEDED
2019-06-28 11:46:11 ERROR: invalid header received
2019-06-28 11:46:11 ProcessMessages(headers, 162003 bytes) FAILED peer=15
2019-06-28 11:54:27 UpdateTip: new best=64dad8fc41f6e1831396c555c09ce184024ad83f6c463089f6092796a4141f85 height=128312 version=0x2000000c log2_work=59.49480937 tx=1084073 date='2019-06-28 11:54:26' progress=1.000000 cache=0.0MiB(0txo)
2019-06-28 11:54:27 {PNB}: ACC  CGovernanceManager::ProcessVote -- Unknown parent object 14ff4feb7d015a84f2d9565c7845237127bc9163ab9df190037b71f95fa14fbc, MN outpoint = 11c1ca208005e2b325a8ec544432d18afb4ef3b2e76d82761747ea438a0b0f54-1
2019-06-28 11:58:34 CGovernanceManager::SyncSingleObjAndItsVotes -- not syncing deleted/expired govobj: 051aee71db51fe4ac470ec65aaed9d13708b6e91dcdfb2ad182e05cd779065ae, peer=20
2019-06-28 11:58:36 CGovernanceManager::SyncSingleObjAndItsVotes -- not syncing deleted/expired govobj: 9800a21d825d0b40509dd993757d5380aa8a0f6282f3e5fc6532c6a1d8225371, peer=0
2019-06-28 12:07:47 UpdateTip: new best=c4658f4af2386c4ab444442d0dafb5dae2727d3f2d2730f637e954795fd70be0 height=128313 version=0x2000000c log2_work=59.49483398 tx=1084077 date='2019-06-28 12:07:56' progress=1.000000 cache=0.0MiB(0txo)
2019-06-28 12:07:47 {PNB}: ACC
 

Lets put long debugs within the code tags to keep forum cleaner, thanks man.


Anyway, I did run the global report and we have no forks (we are all on block 128331 with 36.9K diff) and none of my sancs are crashed with any SAN errors, so I think these two errors are *relatively* isolated.

Its possible your node was in a state where it failed to leave ABN.  To ensure you are back in heat mode only, please do this:
rm blocks -r
rm chainstate -r
rm evodb -r
rm gov*.dat
rm mnc*.dat
rm mnp*.dat

rm SAN/* -r
Very important, remove the contents of SAN and restart.

Then all gobjects will resync and Im sure you will be in heat mode only after this.

[bible_pay]

I have no clue if this is the case but I have a sneaky suspicion CCEX might be the big seller on SX - as they had about 20 mil in the wallet.

Why it seems you cannot manage to list the coin in higher volume exchanges because if you won't bother listing then it will really hurt, the price will keep going down in the market.

In addition to what MIP said, we are not at all against moving onto bigger exchanges, if you have any special contacts feel free to notify them to notify us or me (rob@biblepay.org).
I hope you realize most exchanges charge about $60,000 to be listed.  We need to be very strategic in our choices.

We do have a new exchange fund, that accumulates funds, and it is publically viewable on our pool web site.

We have an offer to be on FUBT for 3 btc, but we are saving slowly and evaluating very carefully for the next exchange.

I have personal contacts at Bittrex and Poloniex myself; Poloniex is still evaluating my submission.  I've only used up 1 of my bullets at Bittrex so far, deliberately - Im waiting for the right timing to contact the senior management there - probably around the end of the year.

We are open to more ideas.

[capulo]

I have no clue if this is the case but I have a sneaky suspicion CCEX might be the big seller on SX - as they had about 20 mil in the wallet.

Ouch I really hope that is not the case, but it did seem that C-CEX was doing an exit scam of some sort... 

Well, yes, that's scathing, but from their perspective, they had a 24 million BBP 'house balance'.  They posted a notice that they will be leaving by June 1st for re-organization, that everyone should withdraw the coins (as after this date, withdrawals will not be possible).  Whatever is left in the house balance after that date, they consider to be their assets.

So from their perspective they are probably liquidating and keeping the BTC.

But, know that I myself in no way shape or form would ever do this to anyone.  If I had an exchange I would allow 6 months to withdraw and I would be sending daily e-mails saying come and get your balance as these aren't my funds.

the main problem was, that they stops supporting people. so if anyone get locked, then he cant withdraw money. i was trying whole month to raise ticket, but without success... i was locked and i'm still locked with all funds there. so it is funny from them to write : withdraw your money if people are locked and they wont unlock them:)

[bible_pay]

I have no clue if this is the case but I have a sneaky suspicion CCEX might be the big seller on SX - as they had about 20 mil in the wallet.

Ouch I really hope that is not the case, but it did seem that C-CEX was doing an exit scam of some sort... 

Well, yes, that's scathing, but from their perspective, they had a 24 million BBP 'house balance'.  They posted a notice that they will be leaving by June 1st for re-organization, that everyone should withdraw the coins (as after this date, withdrawals will not be possible).  Whatever is left in the house balance after that date, they consider to be their assets.

So from their perspective they are probably liquidating and keeping the BTC.

But, know that I myself in no way shape or form would ever do this to anyone.  If I had an exchange I would allow 6 months to withdraw and I would be sending daily e-mails saying come and get your balance as these aren't my funds.

the main problem was, that they stops supporting people. so if anyone get locked, then he cant withdraw money. i was trying whole month to raise ticket, but without success... i was locked and i'm still locked with all funds there. so it is funny from them to write : withdraw your money if people are locked and they wont unlock them:)

Yeah, thats deceptive if that actually happened to a lot of people, thats horrible and deceptive.

[sunk818]

Is there a way to at least get back same gsc we sent? Some people are saying they donate 2000 and get back only 800 in daily reward.

[thesnat21]

Ouch I really hope that is not the case, but it did seem that C-CEX was doing an exit scam of some sort... 

Well, yes, that's scathing, but from their perspective, they had a 24 million BBP 'house balance'.  They posted a notice that they will be leaving by June 1st for re-organization, that everyone should withdraw the coins (as after this date, withdrawals will not be possible).  Whatever is left in the house balance after that date, they consider to be their assets.

So from their perspective they are probably liquidating and keeping the BTC.

But, know that I myself in no way shape or form would ever do this to anyone.  If I had an exchange I would allow 6 months to withdraw and I would be sending daily e-mails saying come and get your balance as these aren't my funds.

Yes this is a valid/fair assumption. 

I took issue when they started delisting coins with 30 days notice and expected people to log in to see which were removed. (no more emails / public announcements)

I guess it's off topic in a way, I started feeling like our association with them is a net negative (even more so at the end as we were the only coin listed)

oh well it's in the past, and we cannot change what has been done..

[bible_pay]

Is there a way to at least get back same gsc we sent? Some people are saying they donate 2000 and get back only 800 in daily reward.

Donations or Tithes mean they are gifts from the heart to the foundation.

If anyone expects it back it was not a donation.

I suggest you inspect your heart, and find what part of you could be missing the teachings of Jesus, and make an adjustment there.

BiblePay isn't about making people rich or rewarding miners with profit - those things come later if God blesses us - and after you help children first.

[SEO_Account]

Is there a way to at least get back same gsc we sent? Some people are saying they donate 2000 and get back only 800 in daily reward.

It's fairly easy to calculate what you will get back from a donation

[pagalo]

Hello,

I have moved to new version 9c but I haven't solved any block since 128234.
Is this normal?

I usuale get 10-20 block with 30PCs

[bible_pay]

Is there a way to at least get back same gsc we sent? Some people are saying they donate 2000 and get back only 800 in daily reward.

It's fairly easy to calculate what you will get back from a donation

Yes, and also, in any business including mining, part of the participants job is to add all costs and this wouldn't be any different.

[bible_pay]

Hello,

I have moved to new version 9c but I haven't solved any block since 128234.
Is this normal?

I usuale get 10-20 block with 30PCs

Looking at the pool, I see 2 blocks solved on 1439 over the last 6 hours, so I don't see a problem.