Pool fees lowered to 15%, hoping for the best.
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 739. (Read 243376 times)
January 01, 2018, 11:15:04 AM
January 01, 2018, 11:13:40 AM
Just as a very crude start, we need to make a wiki page for this soon, but for a reference as to exactly when our block numbers kick over for our next monthly deflation target:
Block AccumulatedDepreciationLevel Subsidy
06150 .0150 14775
12300 .0300 14550
18450 .0450 14325
24600 .0600 14100
30750 .0750 13875
So what this means is at block 24600, the same block as our superblock, our monthly deflation measure kicks in and lowers the subsidy from ~14325 to ~14100.
Block AccumulatedDepreciationLevel Subsidy
06150 .0150 14775
12300 .0300 14550
18450 .0450 14325
24600 .0600 14100
30750 .0750 13875
So what this means is at block 24600, the same block as our superblock, our monthly deflation measure kicks in and lowers the subsidy from ~14325 to ~14100.
Didn't get any response on my question about info on setting up master node so I did read the readme in the latest download but the wiki link went to 404 error. When you update the wiki don't forget to update the link in the readme in the latest download. Way back I mined enough coins to masternode and have held them so I am looking forward to getting that done as soon as I can but I just can't find any info at the website or github thus far...
Hopefully this link answers all your questions:
http://wiki.biblepay.org/Create_Sanctuary
January 01, 2018, 11:10:32 AM
Just as a very crude start, we need to make a wiki page for this soon, but for a reference as to exactly when our block numbers kick over for our next monthly deflation target:
Block AccumulatedDepreciationLevel Subsidy
06150 .0150 14775
12300 .0300 14550
18450 .0450 14325
24600 .0600 14100
30750 .0750 13875
So what this means is at block 24600, the same block as our superblock, our monthly deflation measure kicks in and lowers the subsidy from ~14325 to ~14100.
Block AccumulatedDepreciationLevel Subsidy
06150 .0150 14775
12300 .0300 14550
18450 .0450 14325
24600 .0600 14100
30750 .0750 13875
So what this means is at block 24600, the same block as our superblock, our monthly deflation measure kicks in and lowers the subsidy from ~14325 to ~14100.
Didn't get any response on my question about info on setting up master node so I did read the readme in the latest download but the wiki link went to 404 error. When you update the wiki don't forget to update the link in the readme in the latest download. Way back I mined enough coins to masternode and have held them so I am looking forward to getting that done as soon as I can but I just can't find any info at the website or github thus far...
January 01, 2018, 11:04:02 AM
Just as a very crude start, we need to make a wiki page for this soon, but for a reference as to exactly when our block numbers kick over for our next monthly deflation target:
Block AccumulatedDepreciationLevel Subsidy
06150 .0150 14775
12300 .0300 14550
18450 .0450 14325
24600 .0600 14100
30750 .0750 13875
So what this means is at block 24600, the same block as our superblock, our monthly deflation measure kicks in and lowers the subsidy from ~14325 to ~14100.
Block AccumulatedDepreciationLevel Subsidy
06150 .0150 14775
12300 .0300 14550
18450 .0450 14325
24600 .0600 14100
30750 .0750 13875
So what this means is at block 24600, the same block as our superblock, our monthly deflation measure kicks in and lowers the subsidy from ~14325 to ~14100.
January 01, 2018, 11:01:42 AM
So far, from what I can see the Watchman is now skipping over the deleted object and we should not be receiving errors any longer. Mouse, do you want to verify that with one of your non-patched nodes?
I didn't do anything and my sanctuary says 'ENABLED' again. Do I still have to restart my sanctuary?
All credit to Jesus for our work.
January 01, 2018, 10:54:22 AM
So far, from what I can see the Watchman is now skipping over the deleted object and we should not be receiving errors any longer. Mouse, do you want to verify that with one of your non-patched nodes?
I didn't do anything and my sanctuary says 'ENABLED' again. Do I still have to restart my sanctuary?
January 01, 2018, 10:50:50 AM
So far, from what I can see the Watchman is now skipping over the deleted object and we should not be receiving errors any longer. Mouse, do you want to verify that with one of your non-patched nodes?
January 01, 2018, 10:50:07 AM
still dont understand why any MN is still alive and receving rewards and the majority of others is dead = this doesnt look fair
Its fair, I appreciate that.
Alex has tested this, please take with him.
January 01, 2018, 10:47:08 AM
still dont understand why any MN is still alive and receving rewards and the majority of others is dead = this doesnt look fair
January 01, 2018, 10:43:25 AM
is my MN alive when watchdog is expired? my voting failed 
Yes, the watchdog only affects payments.
Oh, it looks like we already have a supermajority and deleted the object. I re-voted to delete on one that I had received success earlier, and now receive the same error.
You can vote on one of the old proposals if you want, and see it still works.
Alright, we have to wait for the Pool to upgrade, and I have a lunch appointment today so please everyone be patient for 4 hours and we will take this up this afternoon.
In the mean time, go ahead and issue the start-many commands to restart your sanctuaries, so we can try to get rid of the watchdog expired errors.
January 01, 2018, 10:40:39 AM
is my MN alive when watchdog is expired? my voting failed
https://i.imgur.com/3ItNX8e.png
watchman issues
https://i.imgur.com/WRWGv2G.png
https://i.imgur.com/3ItNX8e.png
watchman issues
https://i.imgur.com/WRWGv2G.png
January 01, 2018, 10:36:54 AM
So in a nutshell what mouse and I have found is the code that somehow passed in test (I have no clue how we successfully minted a superblock) has a bad character at the end of the superblock trigger, that offends Watchman, and prevents Watchman from importing the gobject, and then throws python errors.
So part of the solution was to modify BiblePay core to allow the pool to create a good superblock trigger in prod.
However, we have one bad superblock trigger in prod floating around all the sanctuaries.
Guys, help me out here, lets delete the bad superblock trigger now, and see if it is cleared out, please execute this command from all your sanctuaries:
gobject vote-many 1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1 delete yes
After we see it is cleared, we will create a new superblock trigger this afternoon and re-vote on the budget.
(This will invalidate the current budget).
All credit goes to the most high God: Yeshua Hamashiach.
So part of the solution was to modify BiblePay core to allow the pool to create a good superblock trigger in prod.
However, we have one bad superblock trigger in prod floating around all the sanctuaries.
Guys, help me out here, lets delete the bad superblock trigger now, and see if it is cleared out, please execute this command from all your sanctuaries:
gobject vote-many 1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1 delete yes
After we see it is cleared, we will create a new superblock trigger this afternoon and re-vote on the budget.
(This will invalidate the current budget).
All credit goes to the most high God: Yeshua Hamashiach.
January 01, 2018, 10:29:09 AM
okik, ill go test it on my test server
and Masternodes is offline now? cos i see watchdogs expired
Yeah thats my post #2190, Im looking at this issue now.and Masternodes is offline now? cos i see watchdogs expired
rpcgovernance.cpp
line 114: sJson += GJE("type",sType,true,false); // Must be an Int
is including a delimiter, "type\":2,}]]"
in my case, I have changed the file "biblepaylib.py"
227 def deserialise(hexdata):
228 json = binascii.unhexlify(hexdata).replace(",}]]", "}]]")
229 obj = simplejson.loads(json, use_decimal=True)
230 return obj
Yeah, good find, I found it also, but lets fix this one step at a time, I want to evaluate if its better for us to delete the bad gobject and create a new trigger next.
So far, I fixed the original line of code that caused the problem (the one you noted in rpcgovernance.cpp), and Im doing a build with it. Only the Pools need to upgrade (that would allow me to emit a new superblock trigger).
Please wait for directions on the watchman side, as I need to test deleting the original offending gobject trigger....
Edit: Mouse, are you interested in becoming a biblepay programmer?
January 01, 2018, 09:54:31 AM
okik, ill go test it on my test server
and Masternodes is offline now? cos i see watchdogs expired
Yeah thats my post #2190, Im looking at this issue now.and Masternodes is offline now? cos i see watchdogs expired
rpcgovernance.cpp
line 114: sJson += GJE("type",sType,true,false); // Must be an Int
is including a delimiter, "type\":2,}]]"
in my case, I have changed the file "biblepaylib.py"
227 def deserialise(hexdata):
228 json = binascii.unhexlify(hexdata).replace(",}]]", "}]]")
229 obj = simplejson.loads(json, use_decimal=True)
230 return obj
January 01, 2018, 09:34:21 AM
okik, ill go test it on my test server
and Masternodes is offline now? cos i see watchdogs expired
Yeah thats my post #2190, Im looking at this issue now.and Masternodes is offline now? cos i see watchdogs expired
January 01, 2018, 09:33:49 AM
I have a side project for someone who might want to track our Deflationary feature and make a monitoring department out of it:
If someone wants to grab the code and take a look at GetBlockSubsidy, you will see a function in there that decreases our emission by 1.5% per month or 19.5% per year.
It would be nice to post here the next block we decrease our subsidy, then we can make a wiki page out of it to refer to in the future.
I think even though this sounds simple, this will be a large component of the cornerstone of success here at biblepay.
Then once per month we can all look forward to the deflationary block number to hit, and realize the subsidy is going down by 1.5% and therefore everyone gets a "raise" theoretically.
If someone wants to grab the code and take a look at GetBlockSubsidy, you will see a function in there that decreases our emission by 1.5% per month or 19.5% per year.
It would be nice to post here the next block we decrease our subsidy, then we can make a wiki page out of it to refer to in the future.
I think even though this sounds simple, this will be a large component of the cornerstone of success here at biblepay.
Then once per month we can all look forward to the deflationary block number to hit, and realize the subsidy is going down by 1.5% and therefore everyone gets a "raise" theoretically.
January 01, 2018, 09:30:12 AM
okik, ill go to test it on my test server
and Masternodes is offline now? cos i see watchdogs expired
and Masternodes is offline now? cos i see watchdogs expired
January 01, 2018, 09:29:09 AM
update 1073 is out? 
Its a feature Alex is testing overnight; you will have to ask him if it works or not, dont download things that arent announced for Prod yet. It requires a key to turn on.
January 01, 2018, 09:25:14 AM
update 1073 is out?
January 01, 2018, 09:21:07 AM
On this Watchman issue in python, thanks for all the posts, I have that error on my sanctuary also.
So Im working on reproducing now, and Im in slack with Alex working with him on the underlying data.
Ill let you all know as soon as we figure out what is wrong.
Togo, thanks for your help. So the good news is the proposals are all still there, and our "gobject list all triggers" is still in the sanctuaries for block 24600. So this is a new situation, checking....
So Im working on reproducing now, and Im in slack with Alex working with him on the underlying data.
Ill let you all know as soon as we figure out what is wrong.
Togo, thanks for your help. So the good news is the proposals are all still there, and our "gobject list all triggers" is still in the sanctuaries for block 24600. So this is a new situation, checking....
Jump to: