Author

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

full member
Activity: 462
Merit: 103
pool is dead again, same like 2 days ago...
it is not coincidence...

I wonder if it's coincidence that a large proportion of the MN's have just just gone to WatchDog Expired states ??
Code:
ENABLED 36
NEW_START_REQUIRED 3
WATCHDOG_EXPIRED 83
PRE_ENABLED 0
UPDATE_REQUIRED 0
EXPIRED 0
https://biblepay.eu/

Those might be running 1.0.8.2.  If the node actually Stopped, their payments will stop.

Anyone who owns one of those 20 nodes, please come online and tell us what happened.

Either way you have to upgrade to 1.0.8.6 to stay up without a crash.

The problem was fixed in 1.0.8.6

On https://biblepay.eu/ we can see the version distribution which is actually protocol distribution, but as I see in GitHub commits, 70715 was introduced in 1.0.8.4? So they are probably not running 1.0.8.2 (right?), but also we don't know if they are running 1.0.8.4-5, or 1.0.8.6+. Maybe Virus can pull the version data to his site, if not, maybe protocol version can be increased with every version, if that makes sense? (I doubt it makes sense Smiley)

Either way, my MN went to EXPIRED state last night and it's on 1.0.8.7. When I checked it, the daemon had crashed. These are the last lines of debug.log before crashing:

Code:
2018-01-30 04:12:30 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HKq4s+Yl2VQ42mCFLy84mHKXx0Mludl3BZ+kq2Pv9KUKF3qTUIWWjPA8Yb/8Fg96MzKUfl+HntxlAsW7Di6Eizs=
2018-01-30 04:12:31 Disconnecting unauthorized peer with Network Time off by 7201.000000 seconds!^M
2018-01-30 04:14:37 Disconnecting unauthorized peer with Network Time off by 32401.000000 seconds!^M
2018-01-30 04:19:38 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=GxNu58oFKlDbVCwpq6cFO0iIAm0GUXP7qsPtVDh5oGY5ErU9GC1SmamKLoaNXr0tI1CJbqavmyU2WKGkTIz1f/I=
2018-01-30 04:19:38 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=G4TVJF+oPO5QE6+5xFPWn7w7P25i0zSCgoTSEdq/2u1ZZbwZQPjFfK+G8wz58ULVldQkUAZCUpUvqOqVEfAdrt4=
2018-01-30 04:20:40 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=GxNu58oFKlDbVCwpq6cFO0iIAm0GUXP7qsPtVDh5oGY5ErU9GC1SmamKLoaNXr0tI1CJbqavmyU2WKGkTIz1f/I=
2018-01-30 04:20:40 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=G4TVJF+oPO5QE6+5xFPWn7w7P25i0zSCgoTSEdq/2u1ZZbwZQPjFfK+G8wz58ULVldQkUAZCUpUvqOqVEfAdrt4=
2018-01-30 04:21:50 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HELzseIXLZTQQaCa2MqjUP9VpuCOlQ6zrgBrrRlmq6avSg1waraLOfbXYkYtLVs/c/T2xY6kwhuYN51+OuYOjjo=
2018-01-30 04:21:50 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HKq4s+Yl2VQ42mCFLy84mHKXx0Mludl3BZ+kq2Pv9KUKF3qTUIWWjPA8Yb/8Fg96MzKUfl+HntxlAsW7Di6Eizs=
2018-01-30 04:22:28 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HELzseIXLZTQQaCa2MqjUP9VpuCOlQ6zrgBrrRlmq6avSg1waraLOfbXYkYtLVs/c/T2xY6kwhuYN51+OuYOjjo=
2018-01-30 04:22:28 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HKq4s+Yl2VQ42mCFLy84mHKXx0Mludl3BZ+kq2Pv9KUKF3qTUIWWjPA8Yb/8Fg96MzKUfl+HntxlAsW7Di6Eizs=
2018-01-30 04:25:19 DSEG -- Sent 121 Masternode invs to peer 47696
2018-01-30 04:25:35 Disconnecting unauthorized peer with Network Time off by 14570.000000 seconds!^M
2018-01-30 04:27:14 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=GxNu58oFKlDbVCwpq6cFO0iIAm0GUXP7qsPtVDh5oGY5ErU9GC1SmamKLoaNXr0tI1CJbqavmyU2WKGkTIz1f/I=
2018-01-30 04:27:14 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=G4TVJF+oPO5QE6+5xFPWn7w7P25i0zSCgoTSEdq/2u1ZZbwZQPjFfK+G8wz58ULVldQkUAZCUpUvqOqVEfAdrt4=
2018-01-30 04:27:39 Disconnecting unauthorized peer with Network Time off by 3575.000000 seconds!^M
2018-01-30 04:28:01 Disconnecting unauthorized peer with Network Time off by 7200.000000 seconds!

There is a lot more of these errors repeated, this is just a snippet of the last ones. I hope this can help.
full member
Activity: 770
Merit: 100
I think we should stay away from Binance.  They seem to be run by Greedy non Christians.  

I got in touch with "Carlos - JP Support 1022" and explained how I was scammed by someone posing as Sr. Manager for Binance, created a ticket, sent the backing info and even created a new-coin application, and all I received back today was "Sorry, nothing we can do for you.  "  

They could care less.  


do you have any proofs? screenshots etc? if yes.... we can send to www.coindesk.com https://news.bitcoin.com etc ....  Wink
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
pool is dead again, same like 2 days ago...
it is not coincidence...

I wonder if it's coincidence that a large proportion of the MN's have just just gone to WatchDog Expired states ??
Code:
ENABLED 36
NEW_START_REQUIRED 3
WATCHDOG_EXPIRED 83
PRE_ENABLED 0
UPDATE_REQUIRED 0
EXPIRED 0
https://biblepay.eu/


Those might be running 1.0.8.2.  If the node actually Stopped, their payments will stop.

Anyone who owns one of those 20 nodes, please come online and tell us what happened.

Either way you have to upgrade to 1.0.8.6 to stay up without a crash.

The problem was fixed in 1.0.8.6

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I think we should stay away from Binance.  They seem to be run by Greedy non Christians. 

I got in touch with "Carlos - JP Support 1022" and explained how I was scammed by someone posing as Sr. Manager for Binance, created a ticket, sent the backing info and even created a new-coin application, and all I received back today was "Sorry, nothing we can do for you.  " 

They could care less. 

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
we still dont know what happens around block 27815 when pool gets alive
rob did you investigated this? root cause must be there Smiley

I didnt see anything funny, except more traffic, and now less traffic.  It has anti-ddos, but its possibly getting ddossed very hard.

I have to check the logs again, let me take a look.

full member
Activity: 770
Merit: 100
yes: more MN in watchdog expired  Huh
newbie
Activity: 39
Merit: 0
pool is dead again, same like 2 days ago...
it is not coincidence...

I wonder if it's coincidence that a large proportion of the MN's have just just gone to WatchDog Expired states ??
Code:
ENABLED 36
NEW_START_REQUIRED 3
WATCHDOG_EXPIRED 83
PRE_ENABLED 0
UPDATE_REQUIRED 0
EXPIRED 0
https://biblepay.eu/
full member
Activity: 462
Merit: 103
I'm wondering and I want to learn, what is "base_blockhash" in getmininginfo?
newbie
Activity: 491
Merit: 0
pool is dead again, same like 2 days ago...
it is not coincidence...
newbie
Activity: 491
Merit: 0
we still dont know what happens around block 27815 when pool gets alive
rob did you investigated this? root cause must be there Smiley
newbie
Activity: 84
Merit: 0
Yep, pool is being odd again. Not sure what problem is.
newbie
Activity: 81
Merit: 0
What happen with pool to finding blocks ? Again  Huh shares and rewards drop too much.
newbie
Activity: 81
Merit: 0
Pool just drop all shares fews hour ago ??
newbie
Activity: 491
Merit: 0
which exchange are we funding now? Smiley
and how many we have at 'pocket' ?

None in pocket yet, we're lining up funds in order to move quickly when the door opens.

Yobit - Is now questionable due to possible integrity issues that we're trying to verify or eliminate.

southXchange - They look good, told us we can be listed within a day. Now waiting for a response about how to access their listing application.

NEXT.EXCHANGE - This one also looks very good. znaffl is running an upvote campaign for a possible free (?) listing, but that could take a while to payoff. I suggest that if the listing fee is reasonable we should go with a paid listing to speed up the process. znaffl sent them an email yesterday requesting fee details, we're now waiting on a reply.

UPDATED: We currently have 283,000 BBP and $80 USD in the fund. That equals approx 0.13 BTC at current prices.

thats great, we should do NEXT for free and spend budget on another one Smiley

tip: for voting on NEXT, its just about cookies. if you delete cookies, you can vote again, or just use private feature of browser (should be same as deleting cookies) - bu use this carefully, not spam them with many votes in once. i'm adding one vote from time to time
full member
Activity: 406
Merit: 101
My machines just found another block. That's 4 blocks total now on solo mining across 3 machines, in around a week.
Hi remtiwk,

I also wanna try solo a shot. can you help me the way how to config wallet in linux to solo mining ? Have any way to combine HPS for many machine as one ?

To go solo, comment out pool and workerid in your biblepay.conf file (which is located in ~/.biblepaycore).

The easiest way to make them mine almost like they're mining as one is to copy one wallet to all machines.  Then you only have to check the wallet of one to see if any found a block.  Combining them truly as one has little benefit in my eyes but if you have a reason to, short of running the pool software and doing it that way, I'm unaware of any other way.
full member
Activity: 406
Merit: 101
SVK Noko may be trying link machines so they'll work together cooperatively like a pool does - to solve the block.

I guess, but really the math of it is that 4 machines working independently have an equal chance to solve a block at 4 machines working in unison.  Having a common wallet alleviates the need to check more than one machine to see if any of them succeeded.  That's why I'm curious if he has some other reason.
newbie
Activity: 81
Merit: 0
My machines just found another block. That's 4 blocks total now on solo mining across 3 machines, in around a week.
Hi remtiwk,

I also wanna try solo a shot. can you help me the way how to config wallet in linux to solo mining ? Have any way to combine HPS for many machine as one ?
member
Activity: 489
Merit: 12
Hi
I would like to ask for advice. When I want to link up few mining machines together on the local network for one wallet. How should I configure the biblepay.conf file?
Thanks.
If you want to share a wallet.dat across 5 machines, just copy the wallet.dat to each node.
Nothing goes in the biblepay.conf to link them together.

Hi Rob
Thanks for answer. But I don't want only share wallet. I was trying to link up the hashpower together as well. Any advise? Thanks.


Is there a reason you don't want to share a wallet?  Really that is by far the easiest way to combine the machines.  I'm sure there might be a technical way to actually make all the machines truly work as one, but from most experiences, you're better off running several machines of lower power than one machine of higher power.  That may have changed over time, but there's no drawback I have seen to running one wallet on multiple machines that you control.  Could you elaborate why you don't want to do that?

SVK Noko may be trying link machines so they'll work together cooperatively like a pool does - to solve the block.
newbie
Activity: 17
Merit: 0
My machines just found another block. That's 4 blocks total now on solo mining across 3 machines, in around a week.

how much hps?

My fastest machine is "hashps": 5853.199462096544
newbie
Activity: 29
Merit: 0
@SEO_Account & bible_pay

So what your are saying is if i had, or hired a server with say 4KHs capabilty and put it on the pool as one worker of 4KHs it would get as many shares for its single instance as 25 workers of 160Hs each. I have to say
that is not my experience. I hired a 6KHs machine from GTHosts for 1 day. It got about twice the shares that 1 of my 750Hs  got, but cost 30 times as much. No go there.

By integrity i understand you to mean that the system cannot be manipulated in the way i mean?

Thanks
Sorry i understand you're saying that the little miners would get more HPS2 but that this reflects their 'collective' performance as solo miners if they are not on the pool. But the difference seems to be very large in the pool.
If it were truly a large advantage in actually finding a block to have many small miners, perhaps we should be advising people with decent sized machines to split them up into many smaller workers?
Jump to: