BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[thesnat21]

Hi everyone,
I'm quite bissy right now, sorry for the long time without any answers

About the question: Sadly, I still couldn't get Launchpad to use the old SSL Version, something that works ok on a local build :/
The error messages can be found in longer posts. Any Idea is welcome.

No worries.. we understand

I'm working on something that may help still using the older ver.  will let you know asap

[togoshigekata]

CameroonONE posted about us on Twitter:
https://twitter.com/CameroonONE/status/1010845995188588549

and in a Facebook video:
https://www.facebook.com/CameroonONE/videos/2006713989352627/

Awesome!

[thesnat21]

The fun/tease of mined blocks.... 

May the best fork win!

lol

[afeno]

CoinMarketCap Circulating Supply is Updated:
https://coinmarketcap.com/currencies/biblepay/
 

It seems that the volumes are wrong at CoinMarketCap. How are they getting those numbers? This info should be automatically pulled from the exchange. Right?

[Brian879]

CoinMarketCap Circulating Supply is Updated:
https://coinmarketcap.com/currencies/biblepay/
 

It seems that the volumes are wrong at CoinMarketCap. How are they getting those numbers? This info should be automatically pulled from the exchange. Right?

The 24h volume seems correct? it's just some days the volume is low (less than 1k like today), and some days it's much higher.

[hsb]

-rw-------  1 root root 49384969599 Jun 30 08:32 debug.log
-rw-------  1 root root       23158 May 10 10:01 fee_estimates.dat
-rw-------  1 root root     9341458 May 10 10:01 governance.dat

it's time to delete debug.log

[bible_pay]

-rw-------  1 root root 49384969599 Jun 30 08:32 debug.log
-rw-------  1 root root       23158 May 10 10:01 fee_estimates.dat
-rw-------  1 root root     9341458 May 10 10:01 governance.dat

it's time to delete debug.log

Hopefully the last time, forever...

120 more blocks and we should be back to non-spam mode.

[sunk818]

-rw-------  1 root root 49384969599 Jun 30 08:32 debug.log
-rw-------  1 root root       23158 May 10 10:01 fee_estimates.dat
-rw-------  1 root root     9341458 May 10 10:01 governance.dat

it's time to delete debug.log

add in biblepay.conf
shrinkdebug=1

this will shrink your debug.log every time you restart biblepay daemon

[znffal]

Hi all, a couple of new articles were just pushed on BiblePay News.


a) BiblePay June Monthly Superblock: Funded proposals. Medium link, Steemit Link.

b) BiblePay PR: A thank-you from CameroonOne. Medium link, Steemit Link.


Please share these stories with anyone who you think may be interested.
Watch this space, more stories to come throughout the month of July!

[jaapgvk]

Hi all, a couple of new articles were just pushed on BiblePay News.


a) BiblePay June Monthly Superblock: Funded proposals. Medium link, Steemit Link.

b) BiblePay PR: A thank-you from CameroonOne. Medium link, Steemit Link.


Please share these stories with anyone who you think may be interested.
Watch this space, more stories to come throughout the month of July!

Znffal, you make my life so much easier

All your articles will also be available on the renewed website. And these will most probably also be pushed to our Twitter and Facebook automatically.

And just a heads-up for everyone: the new website will go live this Sunday, so if you can't reach biblepay.org for some time you know the reason

[dave_bbp]

So obviously the whole chain is again complete bollocks right now due to the superblock collision. My Win10-Wallet (1.1.3.6) is constantly crashing, which is why I had to leave it closed and I hoped that the next superblock would be here sooner.
Now it appears that my lasts PODC update is approx. 25hours old. Does this automatically mean I will also miss the NEXT superblock payout?
Right now I managed to open the wallet with gen=0 and quickly force a PODCupdate. But this is too late, right?

[togoshigekata]

Last PODC superblock was at 55350, next one is at 55555
and we are currently at block 55515, so 40 blocks away,
assuming 15 min per block, about ~10 hours away

I got the explorer back up:
http://explorer.biblepay.org
I think mongodb crashed, added script to auto start it if it does crash

./biblepay-cli getblockhash 55513
6926e8ef326aba351bf0b6c43a3df67a76a30dd1d6c9c9312fa4c3c25c41ec1d
UPDATE: 66440144d097c4517d81fdee3ed87b8bd279d8a38be6e843bd4a196c3a571694

So apparently this config option, truncates the debug.log file to 200KB on start if its over 1MB in size
shrinkdebuglog=1
https://bitcoin.stackexchange.com/a/35766/30932
I have a crontab that starts biblepay every 2 minutes, (it exits if its already running)
Ill test and report back if this config option works

Theres also a way to set the logfile to /dev/null
https://bitcointalk.org/index.php?topic=46709.0

[orbis]

./biblepay-cli getblockhash 55513
6926e8ef326aba351bf0b6c43a3df67a76a30dd1d6c9c9312fa4c3c25c41ec1d

Togo, I think you've made some mistake. Or I'm really incapable
I've tried to make "clean install" 3 times on 3 PCs and I'm still not able to made your hash.
On my PCs I have still this:

Code:

getblockhash 55513
66440144d097c4517d81fdee3ed87b8bd279d8a38be6e843bd4a196c3a571694

Interresting is, that I received payout from purepool without problem on block 55504.
On your explorer is hash on block 55513 same as on my PCs.

Code:

http://explorer.biblepay.org/block/66440144d097c4517d81fdee3ed87b8bd279d8a38be6e843bd4a196c3a571694

So where is the problem?
Thanks.

[togoshigekata]

Looks like we are on different chains, I am not sure which chain is the correct chain though

EDIT:
getblockhash 55513
66440144d097c4517d81fdee3ed87b8bd279d8a38be6e843bd4a196c3a571694

I get same hash as you, looks like we are on same chain , maybe I was on bad chain previously

[orbis]

Looks like we are on different chains, I am not sure which chain is the correct chain though

EDIT:
getblockhash 55513
66440144d097c4517d81fdee3ed87b8bd279d8a38be6e843bd4a196c3a571694

I get same hash as you, looks like we are on same chain , maybe I was on bad chain previously

Nice. So,  just wait for next superblock and we'll see if the payout will come

[sunk818]

For small altcoins, I think having biblepay.org be checkpoint server is not a bad idea.

[jaapgvk]

For small altcoins, I think having biblepay.org be checkpoint server is not a bad idea.

I'm trying to understand what you're saying. Could you explain in more detail please?

[bible_pay]

For small altcoins, I think having biblepay.org be checkpoint server is not a bad idea.

After this superblock we wont need it at all; it was used and semi useful in POS, but with our POW base we wont need it.  

Its also far better for decentralization to not have it.

[togoshigekata]

Woah we got to PODC block 55555 solved it
and then jumped through 55556 to 55612 super fast! like 5-6 minutes!

[dave_bbp]

Woah we got to PODC block 55555 solved it
and then jumped through 55556 to 55612 super fast! like 5-6 minutes!

...however that was even possible.

Nice, so it seems to have sorted itself out again. I even got the PODC payment, so it seems like the 25 hour window between the PODC updates was no problem this time because it was way more than 25 hours between those 2 superblocks.
Now a small problem remains in my wallet: it shows the correct transactions in the "transactions" tab, but on the overview under "recent transactions" there are only a handfull of old ones (the latest from more than a week ago). Is there a quick way to fix this? Restarting the wallet didn't help. Otherwise I would make a reindex, which should solve the problem.