|
|
|
|
|
togoshigekata
|
 |
June 07, 2018, 01:01:44 PM |
|
Just an upcoming FYI:
I've been working on fixing the cascading superblocks bug and would like to test this in testnet, however, this is going to be one of those harder to test features, since this requires more than 10% of testnet sanctuaries to vote on the daily and the weekly (testnet has the weekly budgets instead of monthly) superblock...
So, please if you had a testnet masternode up at one time we might need your help soon, as I believe we will need about 5 sancs in testnet.
I'll make a testnet thread once this is compiled. We can also test all features slated for the end of June.
One nice feature we have coming is faster boot time. We now have the prayers loading on their own thread, so the boot should be 50% faster.
***Testnet June 2018 Mandatory Upgrade Testing Thread***https://forum.biblepay.org/index.php?topic=190.0I jumped the gun, BiblePay v1.1.2.5+ is not on Github yet, so wait for it to be released first: https://github.com/biblepay/biblepay/commits/master |
|
|
|
noxpost
Jr. Member
 Offline
Activity: 235
Merit: 3
|
|
June 07, 2018, 01:13:19 PM |
|
So actually the interesting thing is that Iquidus (the base for the block explorers) can calculate the total coin supply in several different ways. Here's what the config says: // how to calculate current coin supply // COINBASE : total sent from coinbase (PoW) // GETINFO : retreive from getinfo api call (PoS) // HEAVY: retreive from heavys getsupply api call // BALANCES : total of all address balances // TXOUTSET : retreive from gettxoutsetinfo api call I assume that the gettxoutsetinfo call is the most accurate one, but to match the other explorers as closely as possible, I didn't end up using that in mine. Togo and I noticed some differences between the 3 explorers and the api call, but the closest was COINBASE. If you look at https://explorebiblepay.com the total supply is reported via the COINBASE (PoW) mechanism. I'd be happy to change it to txoutset, which I still think is the most accurate, but then we'd have 3 explorers with 3 wildly different reports of supply. I haven't tested this myself, but I am willing to guess that biblepay-central is using GETINFO (PoS) instead. Perhaps Togo/Licht/myself should get together and agree on a way of reporting supply within the block explorers. |
|
|
|
|
cf_mm
Newbie
Offline
Activity: 82
Merit: 0
|
|
June 07, 2018, 01:17:01 PM |
|
Hey sent you a DM Mr Dev.. can you get back to me!? many thanks..  |
|
|
|
|
noxpost
Jr. Member
Offline
Activity: 235
Merit: 3
|
|
June 07, 2018, 01:18:43 PM |
|
In addition to my previous post, I'll say that the biblepay-central explorer looks to be having some pretty significant other problems right now. I just saw a latest transaction page of blocks in all kinds of strange order. It looks like there's a reindex/rebuild going on. I still maintain that the difference in coin supply reporting, while normally minimal, is easily fixed by standardization - but of course, it assumes all 3 of us have the same data and are using the same calculation style. |
|
|
|
|
|
|
Brian879
Newbie
Offline
Activity: 35
Merit: 0
|
|
June 07, 2018, 01:27:06 PM |
|
In addition to my previous post, I'll say that the biblepay-central explorer looks to be having some pretty significant other problems right now. I just saw a latest transaction page of blocks in all kinds of strange order. It looks like there's a reindex/rebuild going on. I still maintain that the difference in coin supply reporting, while normally minimal, is easily fixed by standardization - but of course, it assumes all 3 of us have the same data and are using the same calculation style. gettxoutsetinfo is the most accurate and should be the same for everyone. On top of that, it is also not affected by any reindexing so it probably should be configured that way. It would be nice for biblepay-central to use that as it is used by coinmarketcap to determine the max supply of BBP (and therefore its market cap). Any signification variation of the data provided provided by biblepay-central would impact the market cap displayed there. |
|
|
|
|
|
togoshigekata
|
|
June 07, 2018, 01:29:58 PM |
|
So actually the interesting thing is that Iquidus (the base for the block explorers) can calculate the total coin supply in several different ways. Here's what the config says: // how to calculate current coin supply // COINBASE : total sent from coinbase (PoW) // GETINFO : retreive from getinfo api call (PoS) // HEAVY: retreive from heavys getsupply api call // BALANCES : total of all address balances // TXOUTSET : retreive from gettxoutsetinfo api call I assume that the gettxoutsetinfo call is the most accurate one, but to match the other explorers as closely as possible, I didn't end up using that in mine. Togo and I noticed some differences between the 3 explorers and the api call, but the closest was COINBASE. If you look at https://explorebiblepay.com the total supply is reported via the COINBASE (PoW) mechanism. I'd be happy to change it to txoutset, which I still think is the most accurate, but then we'd have 3 explorers with 3 wildly different reports of supply. I haven't tested this myself, but I am willing to guess that biblepay-central is using GETINFO (PoS) instead. Perhaps Togo/Licht/myself should get together and agree on a way of reporting supply within the block explorers. gettxoutsetinfo is the most accurate and should be the same for everyone. On top of that, it is also not affected by any reindexing so it probably should be configured that way.
It would be nice for biblepay-central to use that as it is used by coinmarketcap to determine the max supply of BBP (and therefore its market cap). Any signification variation of the data provided provided by biblepay-central would impact the market cap displayed there.
My explorer uses BALANCES, should I edit it to use TXOUTSET? |
|
|
|
noxpost
Jr. Member
Offline
Activity: 235
Merit: 3
|
|
June 07, 2018, 01:36:12 PM |
|
Interesting - what's the load like on that? Did you need a separate machine? I know it needs a lot of disk space, but I'm guessing the CPU load isn't crazy... |
|
|
|
|
noxpost
Jr. Member
Offline
Activity: 235
Merit: 3
|
|
June 07, 2018, 01:36:40 PM |
|
So actually the interesting thing is that Iquidus (the base for the block explorers) can calculate the total coin supply in several different ways. Here's what the config says: // how to calculate current coin supply // COINBASE : total sent from coinbase (PoW) // GETINFO : retreive from getinfo api call (PoS) // HEAVY: retreive from heavys getsupply api call // BALANCES : total of all address balances // TXOUTSET : retreive from gettxoutsetinfo api call I assume that the gettxoutsetinfo call is the most accurate one, but to match the other explorers as closely as possible, I didn't end up using that in mine. Togo and I noticed some differences between the 3 explorers and the api call, but the closest was COINBASE. If you look at https://explorebiblepay.com the total supply is reported via the COINBASE (PoW) mechanism. I'd be happy to change it to txoutset, which I still think is the most accurate, but then we'd have 3 explorers with 3 wildly different reports of supply. I haven't tested this myself, but I am willing to guess that biblepay-central is using GETINFO (PoS) instead. Perhaps Togo/Licht/myself should get together and agree on a way of reporting supply within the block explorers. gettxoutsetinfo is the most accurate and should be the same for everyone. On top of that, it is also not affected by any reindexing so it probably should be configured that way.
It would be nice for biblepay-central to use that as it is used by coinmarketcap to determine the max supply of BBP (and therefore its market cap). Any signification variation of the data provided provided by biblepay-central would impact the market cap displayed there.
My explorer uses BALANCES, should I edit it to use TXOUTSET? Sure, let's do it - I'll change mine as well and we'll restart them. |
|
|
|
|
|
togoshigekata
|
|
June 07, 2018, 01:42:54 PM |
|
Updated my explorer, coin supply matches "gettxoutsetinfo" command  |
|
|
|
noxpost
Jr. Member
Offline
Activity: 235
Merit: 3
|
|
June 07, 2018, 01:44:00 PM |
|
Updated my explorer, coin supply matches "gettxoutsetinfo" command Same here - and we match now 2 out of 3 done! |
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 07, 2018, 02:39:01 PM |
|
Just an upcoming FYI:
I've been working on fixing the cascading superblocks bug and would like to test this in testnet, however, this is going to be one of those harder to test features, since this requires more than 10% of testnet sanctuaries to vote on the daily and the weekly (testnet has the weekly budgets instead of monthly) superblock...
So, please if you had a testnet masternode up at one time we might need your help soon, as I believe we will need about 5 sancs in testnet.
I'll make a testnet thread once this is compiled. We can also test all features slated for the end of June.
One nice feature we have coming is faster boot time. We now have the prayers loading on their own thread, so the boot should be 50% faster.
***Testnet June 2018 Mandatory Upgrade Testing Thread***https://forum.biblepay.org/index.php?topic=190.0I jumped the gun, BiblePay v1.1.2.5+ is not on Github yet, so wait for it to be released first: https://github.com/biblepay/biblepay/commits/masterYes, I'll be announcing it soon as soon as all the bullet points are added to the page but Im waiting for one. I still have at least one feature Bhavani is checking in to merge in, then it needs compiled then Ill post it here. Its hung up on a small technical problem. Might take a day or so to get to the point where I can post it here, but thanks for being on top of things. |
|
|
|
|
slovakia
|
|
June 07, 2018, 02:41:50 PM |
|
noxpost how much space will be ready for 3 years? thanks new explorer i mean. will be enough this
Intel Atom N2800 2c/4t 1.86GHz 4GB DDR3 1066 MHZ 1TB 100 Mbps
we are ready for TESTNET
|
|
|
|
noxpost
Jr. Member
Offline
Activity: 235
Merit: 3
|
|
June 07, 2018, 03:43:02 PM |
|
noxpost how much space will be ready for 3 years? thanks new explorer i mean. will be enough this
Intel Atom N2800 2c/4t 1.86GHz 4GB DDR3 1066 MHZ 1TB 100 Mbps
we are ready for TESTNET
Well, the current explorer doesn't use much space. I just checked my mongodb and the storagesize is about 160MB. Even at pretty good growth, I think that you'll have plenty. A full node of bitcoin requires something like 140GB of space to store the entire chain history, if that helps the comparison. |
|
|
|
|
Lichtsucher
Jr. Member
Offline
Activity: 219
Merit: 3
|
|
June 07, 2018, 04:28:13 PM |
|
Hi all, I have the task of working on my explorer this weekend. Don't know why the indexing is making such problems there. I will try to setup the explorer from zero an again, maybe this fixes the problems |
Purepool Biblepay Pool (https://www.purepool.org)
Mining How-To (https://www.biblepay-central.org/en/mining-how-to/)
|
|
|
MIP
Newbie
Offline
Activity: 362
Merit: 0
|
|
June 07, 2018, 10:34:05 PM |
|
Hi all, I have the task of working on my explorer this weekend. Don't know why the indexing is making such problems there. I will try to setup the explorer from zero an again, maybe this fixes the problems Remember we need the getuxos API patch for iquidus, for the mobile wallets paper key import feature to work. |
|
|
|
|
pagalo
Newbie
Offline
Activity: 52
Merit: 0
|
|
June 08, 2018, 06:53:54 AM |
|
Hello,
I'm trying to withdraw from pool.biblepay.org but it responds the following.
Sorry, Invalid Destination Address (Code: 65002)
Is there any problem with the pool?
It also shows the same PCs as working and missing...
Thanks in advance
|
|
|
|
|
|
togoshigekata
|
|
June 08, 2018, 08:09:46 AM
Last edit: June 08, 2018, 08:36:28 AM by togoshigekata |
|
seems like BiblePay crashes randomly every few weeks,
(Anyone know how I can automate it to restart Biblepay if BiblePay crashes and to delete the explorer/tmp/index.pid file as well?)
This is a bit "rough" in that I should have parameterized the working directory, or at least made it a variable, but here you go: #!/bin/bash fname="/home/biblepay/explorer/tmp/index.pid" if [[ -f "$fname" ]]; then pid=$(</home/biblepay/explorer/tmp/index.pid) echo $pid ps -p $pid > /dev/null r=$? echo $r if [ $r -eq 0 ]; then exit 1 else rm $fname fi fi I added this to crontab to run periodically. In cases where the index.pid is still there but the process is gone, it simply removes the index.pid file. Hope this helps. I dont know bash at all (nor do I barely know any linux haha), but just to be sure I understand: -f is checking if the file exists index.pid is the indexing lock file with its process ID number inside of it ps -p checks if the process is running $? is the value of the last output that ran and since the previous value is going to dev/null, its the exit code status "0 for successful executions and 1 or higher for failed executions." and so if the process is still running, the bash script just exits, otherwise the process is done and the index.pid file gets removed COOL! So looks like the file doesnt need a .sh extension, if you have "#!/bin/bash" at the top then linux knows its a bash script chmod +x to set it as executable === Also I successfully used nginx to forward nodejs port 3001 to port 80 https://eladnava.com/binding-nodejs-port-80-using-nginx/=== Now I just need to figure out how to restart biblepayd if it crashes, systemd seemed a little complicated, I may just use an infinite while loop bash script LOL |
|
|
|
|
