Author

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

jr. member
Activity: 235
Merit: 3
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.
full member
Activity: 770
Merit: 100
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
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.0

I 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

Yes, 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.

jr. member
Activity: 235
Merit: 3
Updated my explorer, coin supply matches "gettxoutsetinfo" command Wink

Same here - and we match now Smiley
2 out of 3 done!
full member
Activity: 1260
Merit: 115
Updated my explorer, coin supply matches "gettxoutsetinfo" command Wink
jr. member
Activity: 235
Merit: 3
There's an issue with the total circulating supply number from biblepay-central (which seems to be used by coinmarketcap). That number does not look right (987,825,928 BBP).

https://explorer.biblepay-central.org/ext/getmoneysupply

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.
jr. member
Activity: 235
Merit: 3
Bitcoin is the dominant cryptocurrency with the highest market cap and hashpower
and I assume most people buy and sell BiblePay with Bitcoin

Ive been seeing more threads/posts recently about people setting up Bitcoin Full Nodes,
so I decided I wanted to support Bitcoin and started running my own Full Node

https://en.bitcoin.it/wiki/Full_node

"Bitcoin Q&A: What is the role of nodes?" by Andreas M. Antonopoulos
https://www.youtube.com/watch?v=fNk7nYxTOyQ

https://bitcoin.org/en/bitcoin-core/

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...
full member
Activity: 1260
Merit: 115
There's an issue with the total circulating supply number from biblepay-central (which seems to be used by coinmarketcap). That number does not look right (987,825,928 BBP).

https://explorer.biblepay-central.org/ext/getmoneysupply

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?
newbie
Activity: 35
Merit: 0
There's an issue with the total circulating supply number from biblepay-central (which seems to be used by coinmarketcap). That number does not look right (987,825,928 BBP).

https://explorer.biblepay-central.org/ext/getmoneysupply


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.
full member
Activity: 1260
Merit: 115
Bitcoin is the dominant cryptocurrency with the highest market cap and hashpower
and I assume most people buy and sell BiblePay with Bitcoin

Ive been seeing more threads/posts recently about people setting up Bitcoin Full Nodes,
so I decided I wanted to support Bitcoin and started running my own Full Node

https://en.bitcoin.it/wiki/Full_node

"Bitcoin Q&A: What is the role of nodes?" by Andreas M. Antonopoulos
https://www.youtube.com/watch?v=fNk7nYxTOyQ

https://bitcoin.org/en/bitcoin-core/

https://bitcoin.org/en/full-node

https://bitcoin.org/en/full-node#network-configuration
jr. member
Activity: 235
Merit: 3
There's an issue with the total circulating supply number from biblepay-central (which seems to be used by coinmarketcap). That number does not look right (987,825,928 BBP).

https://explorer.biblepay-central.org/ext/getmoneysupply


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.
newbie
Activity: 82
Merit: 0
Hey sent you a DM Mr Dev.. can you get back to me!? many thanks.. Smiley
jr. member
Activity: 235
Merit: 3
There's an issue with the total circulating supply number from biblepay-central (which seems to be used by coinmarketcap). That number does not look right (987,825,928 BBP).

https://explorer.biblepay-central.org/ext/getmoneysupply



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.
full member
Activity: 1260
Merit: 115
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.0

I 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
newbie
Activity: 35
Merit: 0
There's an issue with the total circulating supply number from biblepay-central (which seems to be used by coinmarketcap). That number does not look right (987,825,928 BBP).

https://explorer.biblepay-central.org/ext/getmoneysupply

full member
Activity: 1260
Merit: 115
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.0
full member
Activity: 574
Merit: 104
I have another Sanctuary for sale at market value (0.00000040 BTC/BBP) = 0.62 BTC

All BTC will go to the New Exchange Fund. This fund has made it possible to get us listed on CryptoBridge and will be used to get us on more exchanges in the future Smiley

For more information on the CryptoBridge listing see:
https://forum.biblepay.org/index.php?topic=179.0

For more information on the New Exchange Fund see:
https://forum.biblepay.org/index.php?topic=97.msg3680#msg3680
full member
Activity: 1260
Merit: 115
My explorer has been very sluggish, CPU is maxing out, Im in the process of upgrading from 2 CPU to 4 CPU machine,
I will also remove the need for the port in the web address and also figure out a script to make sure biblepay daemon restarts if it crashes and also indexing of the explorer restarts if it crashes

Noxpost script for making sure explorer indexing doesnt get stopped:
https://bitcointalksearch.org/topic/m.37861985

Licht advice on using systemd to keep biblepay daemon running:
https://bitcointalksearch.org/topic/m.37757211

Licht advice using nginx:
https://bitcointalksearch.org/topic/m.32550673
https://bitcointalksearch.org/topic/m.36131492

===

If anyone is interested in running an explorer for BiblePay, here is my setup guide:
https://www.reddit.com/r/BiblePay/comments/7elm7r/iquidus_block_explorer_guide/
(Somehow my guide has 3,000+ views LOLWUT)

===

BiblePay currently has 3 explorers that I am aware of:
http://explorer.biblepay.org:3001/ by Togo
https://explorer.biblepay-central.org/ by Licht
https://explorebiblepay.com/ by Noxpost

Licht's is listed on CoinMarketCap,
Togo's is listed on C-CEX, Masternodes.Online and the Wiki
Theyre all listed on Discord, Reddit and Bitcointalk Announcement Post
full member
Activity: 1260
Merit: 115


VoskCoin shouted us out in a CPU Mining thread in Bitcointalk Mining section back in January:

"Best CPU Mineable Coins in 2018 and CPU Mining Guides"
https://bitcointalksearch.org/topic/best-cpu-mineable-coins-in-2019-and-cpu-mining-guides-updated-2683343

I made a couple posts there about us, if anyone else could also post about BiblePay that would be awesome!

===

VoskCoin featured us in a mining youtube video 3 months ago:

"How To INCREASE Cryptocurrency Mining PROFITS - Profitable Coins + Profit Switching"
https://www.youtube.com/watch?v=oM2dU29iUTY#t=337 (5 minutes 37 seconds)

and posted the video on our subreddit which was cool:
https://www.reddit.com/r/BiblePay/comments/88f6sn/biblepay_featured_as_a_unique_coin_to_mine_and/

===

VoskCoin just made a video about CryptoBridge today:

"CryptoBridge Review & Tutorial - Up & Coming Decentralized Cryptocurrency Exchange?"
https://www.youtube.com/watch?v=f4_OO3hNEZQ

===

Ive only watched VoskCoin a little and also follow him on Twitter, he seems like a pretty chill guy, and his doge is awesome.
he looks to be a big miner involved in mining lots of different coins and building lots of mining setups,
he has 63k subscribers on Youtube, 3.6k followers on Twitter and 3k+ members on Discord

Youtube:  https://www.youtube.com/channel/UCT44w6854K62cSiwA1aiXfw/featured
Twitter:  https://twitter.com/VoskCoin
Discord:  https://discordapp.com/invite/FGGmS2z

Its pretty cool he likes BiblePay, just wanted to make a summary post since hes shouted us out in the past twice now,
and he just made a video about the exchange we are about to get listed on
Jump to: