any control hash block 1 100 1000?
thanks
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 165. (Read 243386 times)
June 02, 2019, 05:29:29 PM
June 02, 2019, 05:28:33 PM
any good addnodes?
There is no need for an addnode.Checking our first seed node (dns1.biblepay.org) : UP
I keep having issues connecting to dns1.biblepay.org (connects then quickly disconnects)
Also, I noticed that and some others are on .2.9 version, while the download client is .3.1 are there any changes that need to be worried about in between?
Hmm, yes, I see you are right, I just upped the maxconnections to 865 on node1, and removed the banlist and restarted it.
So the only change in 1431 was we added the diary entries to the RPC 'leaderboard' command (to see your own entries). But anyone who downloaded the latest should have 1.4.3.1. The only people with 1429 are most likely the people who went from testnet directly to prod and didnt upgrade.
June 02, 2019, 05:22:28 PM
any good addnodes?
There is no need for an addnode.Checking our first seed node (dns1.biblepay.org) : UP
I keep having issues connecting to dns1.biblepay.org (connects then quickly disconnects)
Also, I noticed that and some others are on .2.9 version, while the download client is .3.1 are there any changes that need to be worried about in between?
June 02, 2019, 05:20:12 PM
guide http://wiki.biblepay.org/Create_Sanctuary_2 still showing 1,550,001 BBP and referring to the old version setup.
Any chance of having it updated ?
also, how do we migrate or consolidate 3 old sanctuaries to 1 evo one ?
apparently, trying to start old sanctuary using evo wallet doesn't work .
Any chance of having it updated ?
also, how do we migrate or consolidate 3 old sanctuaries to 1 evo one ?
apparently, trying to start old sanctuary using evo wallet doesn't work .
Ok, I updated the wiki.
As far as consolidating from 3 to 1:
Go to coin control
Unlock the 3 old unspent outputs that are locked (in Evo they might be unlocked automatically)
Check them
Spend them to a new transaction for 4,500,001 to a new receiving address labeled such as Tiras1-New (or whatever naming convention you prefer).
Copy the TXID and output ordinal into masternode.conf, replacing the old TXID-ordinal for one of your sanc entries, and also update the name to be the new name.
Delete the other 2 sanc entries in the config.
Restart.
Then verify your sanctuary starts. (Start missing, etc as usual).
thank you Rob!
I'm short of ~ 800K BBP to start another sanc ( MN ) .
Anybody willing to form a share is welcome .
800K can be split into 2 or 3 shares.
I'm guaranteeing regular payouts ( weekly or twice a week ) with transaction reports.
Will send a full refund of your share after enough funds accumulated to run a sanc on my own.
It will be interesting to see how many 'jump ship' during this upgrade.
I always had a feeling about 100 of those non-voting sancs were owned by someone who had no idea how to host a node.
Oh btw, I took your advice and applied for us at stocks.exchange the other day (and at yobit also).
June 02, 2019, 05:18:31 PM
any good addnodes?
There is no need for an addnode.Checking our first seed node (dns1.biblepay.org) : UP
June 02, 2019, 04:47:10 PM
any good addnodes?
June 02, 2019, 02:59:10 PM
guide http://wiki.biblepay.org/Create_Sanctuary_2 still showing 1,550,001 BBP and referring to the old version setup.
Any chance of having it updated ?
also, how do we migrate or consolidate 3 old sanctuaries to 1 evo one ?
apparently, trying to start old sanctuary using evo wallet doesn't work .
Any chance of having it updated ?
also, how do we migrate or consolidate 3 old sanctuaries to 1 evo one ?
apparently, trying to start old sanctuary using evo wallet doesn't work .
Ok, I updated the wiki.
As far as consolidating from 3 to 1:
Go to coin control
Unlock the 3 old unspent outputs that are locked (in Evo they might be unlocked automatically)
Check them
Spend them to a new transaction for 4,500,001 to a new receiving address labeled such as Tiras1-New (or whatever naming convention you prefer).
Copy the TXID and output ordinal into masternode.conf, replacing the old TXID-ordinal for one of your sanc entries, and also update the name to be the new name.
Delete the other 2 sanc entries in the config.
Restart.
Then verify your sanctuary starts. (Start missing, etc as usual).
thank you Rob!
I'm short of ~ 800K BBP to start another sanc ( MN ) .
Anybody willing to form a share is welcome .
800K can be split into 2 or 3 shares.
I'm guaranteeing regular payouts ( weekly or twice a week ) with transaction reports.
Will send a full refund of your share after enough funds accumulated to run a sanc on my own.
June 02, 2019, 02:52:28 PM
I think waiting does work in this case, but another way around to be sure is on the Sanc itself, stop it, delete the mnc*.* and gov*.* files and mnp*.* files (just the caches) and restart, and as soon as mnsync status passes 3, I believe your node will be more up to date (with the Sanc list).
EDIT: I don't see you in my Sanc list; try ensuring your controller does not have any banned peers first, then re-start the Sanc (with the Start button from the controller), its possible it needs a new re-broadcast done. It takes up to an hour sometimes to see it change, so this is probably normal.
Ok I did as you said and it didn't work when launching again (node not yet activated), but then I just activated once again from controller wallet and it activated instantly!
Thank you so much for all your help.
I do know -probably better than anyone else- about the incredible amount of time and effort that is behind this Evo release, and all I can say now is: God bless you my friend.
Thanks; We couldn't have done it without you!
June 02, 2019, 02:43:37 PM
I think waiting does work in this case, but another way around to be sure is on the Sanc itself, stop it, delete the mnc*.* and gov*.* files and mnp*.* files (just the caches) and restart, and as soon as mnsync status passes 3, I believe your node will be more up to date (with the Sanc list).
EDIT: I don't see you in my Sanc list; try ensuring your controller does not have any banned peers first, then re-start the Sanc (with the Start button from the controller), its possible it needs a new re-broadcast done. It takes up to an hour sometimes to see it change, so this is probably normal.
Ok I did as you said and it didn't work when launching again (node not yet activated), but then I just activated once again from controller wallet and it activated instantly!
Thank you so much for all your help.
I do know -probably better than anyone else- about the incredible amount of time and effort that is behind this Evo release, and all I can say now is: God bless you my friend.
June 02, 2019, 02:22:57 PM
almost all my miners are on block "blocks": 123036,
but i didnt mine anything, doesnot matter if fork or not
do i need to stake yet?
but i didnt mine anything, doesnot matter if fork or not
do i need to stake yet?
On staking, no not yet, we have to wait until block 123,200 for all sancs to upgrade first, then we assess conditions and release a game plan for the first GSC; but a thumb in the wind estimate is staking around 124,000.
June 02, 2019, 02:18:09 PM
If you are lower could you please try resyncing?
I tried resyncing and both controller wallet and MNs are ok now (block 123126, hash 7355d3ef0e69ddbae973912643185bcfe5fbbeef8d30f6726eec8047a89a4e5d)
So everything looks great, but when I finally activate the MNs, it says "success" in the controller wallet, and PRE_ENABLED, but in the MN VPS I see
Code:
$ biblepay-cli mnsync status
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1559500589,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
$ biblepay-cli masternode status
{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "209.250.243.91:40000",
"status": "Not capable masternode: Masternode not in masternode list"
}
}
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1559500589,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
$ biblepay-cli masternode status
{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "209.250.243.91:40000",
"status": "Not capable masternode: Masternode not in masternode list"
}
}
Is this expected and maybe I have to wait some time? (in previous classic it showed "active" right after activation from controller wallet)
Also, I checked collateral tx amount and also if it is old enough.
I think waiting does work in this case, but another way around to be sure is on the Sanc itself, stop it, delete the mnc*.* and gov*.* files and mnp*.* files (just the caches) and restart, and as soon as mnsync status passes 3, I believe your node will be more up to date (with the Sanc list).
EDIT: I don't see you in my Sanc list; try ensuring your controller does not have any banned peers first, then re-start the Sanc (with the Start button from the controller), its possible it needs a new re-broadcast done. It takes up to an hour sometimes to see it change, so this is probably normal.
June 02, 2019, 02:15:48 PM
almost all my miners are on block "blocks": 123036,
but i didnt mine anything, doesnot matter if fork or not
do i need to stake yet?
but i didnt mine anything, doesnot matter if fork or not
do i need to stake yet?
Yeah, this is because you were loyally mining through the governance block and your node marked the block as bad, and its a very convoluted explanation to say more - other than it is this way because Dash is erroring on the safe side with blocks, so the only way out of this, is to delete the normal blocks,evodb,chainstate,mncache,mnp* and restart and resync. Then you should hit the 123130 chain (diff is about 6K right now).
Sorry for the inconvenience. I resynced the pool to be on this chain.
June 02, 2019, 01:54:34 PM
If you are lower could you please try resyncing?
I tried resyncing and both controller wallet and MNs are ok now (block 123126, hash 7355d3ef0e69ddbae973912643185bcfe5fbbeef8d30f6726eec8047a89a4e5d)
So everything looks great, but when I finally activate the MNs, it says "success" in the controller wallet, and PRE_ENABLED, but in the MN VPS I see
Code:
$ biblepay-cli mnsync status
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1559500589,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
$ biblepay-cli masternode status
{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "209.250.243.91:40000",
"status": "Not capable masternode: Masternode not in masternode list"
}
}
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1559500589,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
$ biblepay-cli masternode status
{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "209.250.243.91:40000",
"status": "Not capable masternode: Masternode not in masternode list"
}
}
Is this expected and maybe I have to wait some time? (in previous classic it showed "active" right after activation from controller wallet)
Also, I checked collateral tx amount and also if it is old enough.
June 02, 2019, 01:51:41 PM
almost all my miners are on block "blocks": 123036,
but i didnt mine anything, doesnot matter if fork or not
do i need to stake yet?
but i didnt mine anything, doesnot matter if fork or not
do i need to stake yet?
June 02, 2019, 12:27:49 PM
guide http://wiki.biblepay.org/Create_Sanctuary_2 still showing 1,550,001 BBP and referring to the old version setup.
Any chance of having it updated ?
also, how do we migrate or consolidate 3 old sanctuaries to 1 evo one ?
apparently, trying to start old sanctuary using evo wallet doesn't work .
Any chance of having it updated ?
also, how do we migrate or consolidate 3 old sanctuaries to 1 evo one ?
apparently, trying to start old sanctuary using evo wallet doesn't work .
Ok, I updated the wiki.
As far as consolidating from 3 to 1:
Go to coin control
Unlock the 3 old unspent outputs that are locked (in Evo they might be unlocked automatically)
Check them
Spend them to a new transaction for 4,500,001 to a new receiving address labeled such as Tiras1-New (or whatever naming convention you prefer).
Copy the TXID and output ordinal into masternode.conf, replacing the old TXID-ordinal for one of your sanc entries, and also update the name to be the new name.
Delete the other 2 sanc entries in the config.
Restart.
Then verify your sanctuary starts. (Start missing, etc as usual).
June 02, 2019, 10:45:46 AM
guide http://wiki.biblepay.org/Create_Sanctuary_2 still showing 1,550,001 BBP and referring to the old version setup.
Any chance of having it updated ?
also, how do we migrate or consolidate 3 old sanctuaries to 1 evo one ?
apparently, trying to start old sanctuary using evo wallet doesn't work .
Any chance of having it updated ?
also, how do we migrate or consolidate 3 old sanctuaries to 1 evo one ?
apparently, trying to start old sanctuary using evo wallet doesn't work .
June 02, 2019, 09:56:58 AM
It appears the most hashpower solved blocks up to 123089, so in this case I think its best to re-sync your Evo node if you are stuck on 123,000 or 123,001.
Since after a while, most users are going to be syncing from zero, and approving that biblepay-classic superblock and veering on the chain with the 30,000 diff.
So please try re-syncing if you are stuck on 123,001.
And also delete your banlist.dat before restarting.
I'm syncing pool.biblepay.org in Evo mode now.
Since after a while, most users are going to be syncing from zero, and approving that biblepay-classic superblock and veering on the chain with the 30,000 diff.
So please try re-syncing if you are stuck on 123,001.
And also delete your banlist.dat before restarting.
I'm syncing pool.biblepay.org in Evo mode now.
Thank you for your guidance and instructions.
Right now our hash power is directed at pool.biblepay.org but it appears that it is wasted (very high error percentage). Would solo mining help, in this case?
Well actually through the night I disabled the pool, so it should not have been wasted (plus - when the client detects a bad pool connection it automatically solo mines).
Its just for the last 30 mins I was re-syncing pool.biblepay, but its actually synced now, so you should be hitting the pool and be on block 123098.
If you are lower could you please try resyncing?
Oh, on the global error percentages yes those will update over the next 15 mins. I think they were being pulled from the classic chain.
June 02, 2019, 09:48:23 AM
It appears the most hashpower solved blocks up to 123089, so in this case I think its best to re-sync your Evo node if you are stuck on 123,000 or 123,001.
Since after a while, most users are going to be syncing from zero, and approving that biblepay-classic superblock and veering on the chain with the 30,000 diff.
So please try re-syncing if you are stuck on 123,001.
And also delete your banlist.dat before restarting.
I'm syncing pool.biblepay.org in Evo mode now.
Since after a while, most users are going to be syncing from zero, and approving that biblepay-classic superblock and veering on the chain with the 30,000 diff.
So please try re-syncing if you are stuck on 123,001.
And also delete your banlist.dat before restarting.
I'm syncing pool.biblepay.org in Evo mode now.
Thank you for your guidance and instructions.
Right now our hash power is directed at pool.biblepay.org but it appears that it is wasted (very high error percentage). Would solo mining help, in this case?
June 02, 2019, 09:16:43 AM
It appears the most hashpower solved blocks up to 123089, so in this case I think its best to re-sync your Evo node if you are stuck on 123,000 or 123,001.
Since after a while, most users are going to be syncing from zero, and approving that biblepay-classic superblock and veering on the chain with the 30,000 diff.
So please try re-syncing if you are stuck on 123,001.
And also delete your banlist.dat before restarting.
I'm syncing pool.biblepay.org in Evo mode now.
Since after a while, most users are going to be syncing from zero, and approving that biblepay-classic superblock and veering on the chain with the 30,000 diff.
So please try re-syncing if you are stuck on 123,001.
And also delete your banlist.dat before restarting.
I'm syncing pool.biblepay.org in Evo mode now.
June 02, 2019, 08:59:56 AM
http://www.biblepay.org/wallet/
still exists, and the download link still works, you should probably remove them.
edit: and a google search for "biblepay wallet" goes directly to that page
still exists, and the download link still works, you should probably remove them.
edit: and a google search for "biblepay wallet" goes directly to that page
Fixed - note you will have to push ctrl-f5 to see the new version tag.
Jump to: