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

[bible_pay]

** September 14th - Weekend Update **



Todd from Cameroon made me aware our POOM BIO was not showing up in listchildren.  This will be fixed in our next release due out tomorrow (in Main Net - Prod).

This will be a leisure upgrade that addresses:
- POOM Bio URL
- Excessive Memory Usage by biblepaycore wallet
- Bloated governance.dat file size and re-index on boot
- Apollon integration testing for deterministic sancs
- High network utilization by governance objects
- Better GSC creation during the first second/better voting
- Gobject contract cleanup/propagation on a fine degree (to reduce governance cache size) and decrease mnsync step 4 load time

This release is now being tested and we believe this will be available before the end of the weekend.
We will recommend that everyone upgrades (even though its not mandatory) as this will reduce biblepay's memory consumption and increase network efficiency.  
We will also recommend every sanctuary upgrades, as it is critical to provide quality service.

** All praise and glory to Yeshua Hamashiach ! **

One of our POOM miners BIO's:

https://biblepay.cameroonone.org/bios/cb1df8c7.htm

[bible_pay]

I asked TOKOK about the airdrop reward for these cases:

A)   User buys 1 mil over 7 days and holds it as of the last day of the competition, then sells it on SEPTEMBER 26th (one day after) on your exchange, for cash, does he get the reward?
B)   User buys 1 mil over 7 days and WITHDRAWS it on September 25th (one day before ending), does he get reward?

He replied:

Both A & B are eligible for the reward.

[bible_pay]

BiblePay
1.4.4.7 - Leisure Upgrade
(Mandatory upgrade for Sanctuaries)

- Fix OneClickMining initial crlf issue (Meaning that biblepay.conf will
not be corrupted if user starts with one-click-mining config)
- Add Payment Option 4 for Cameroon-One, and fix BIO URL
- Apollon Integration for Deterministic Sancs:  Add 'exec blscommand
mnppriv blsprivkey'.  This allows the user to set the deterministic
masternodeblsprivkey in the sanc biblepay.conf file.  NOTE: The
EncryptAES256 and DecryptAES256 were added to support this feature (this
is so no other node can discover your mnprivkey or your mnblsprivkey
during transmission or initialization).
- Update Health feature for Sanctuaries only:  Set healthupdate=1 to
enable, healthupdate=0 to disable, default is Enabled on Sanctuaries
only.  If this is enabled, you will see your Sanctuaries health status
(IE Best Block Hash, GSC voting level) in the pool.  This will be
valuable when we host with Apollon.
- Disconnect nodes who ask for too much gov data
- Fix governance.dat bloated file size, on boot.  Reindex governance.dat
on boot if > 25 megs.
- Clean up GSC contract data after 1 day.  Sanctuary Quorums:  Vote to
delete duplicate contracts.
- Decrease memory consumption (by purging gobject cache)
- Limit network bandwidth (by removing unecessary and expired govobjs)

** Note:  The sync time and network utilization will improve *after* people start utilizing the new version **

[bible_pay]

HODL'ers and Network Admins and Dash veterans, and sancs, post your opinion:

https://forum.biblepay.org/index.php?topic=448.new#new

[togoshigekata]

BiblePay Wordpress Website - Google Analytics
(Data is of the past 3 months 6/11/2019 to 9/8/2019)
Multiple Screenshots: https://imgur.com/a/Z5PyW3I





Rest of Data: https://imgur.com/a/Z5PyW3I

[bible_pay]

BiblePay Wordpress Website - Google Analytics
(Data is of the past 3 months 6/11/2019 to 9/8/2019)
Multiple Screenshots: https://imgur.com/a/Z5PyW3I





Rest of Data: https://imgur.com/a/Z5PyW3I

One thing that stands out to me is the massive number of Chinese users we have looking at the website - almost 30% (this 30% figure is based on distinct user count by Country  - not by language) which I find very interesting.  It basically means a third of our new users are Chinese.

That makes me feel very ashamed at how we primarily have English and poor translation throughout.  We do have Chinese in the core wallet, but no translation option in the pool - and the only translation on the web site is Google auto translate.

But being focused on Jesus I want to jump directly to another issue.  In China Christian persecution is rising at such a high rate with President Xi, that Chinese people are flocking to basements to have home church.  I just met a couple at church the other day that confirmed how bad it is.  We have the bible in our wallet.

I wonder if it would be useful for us to very quickly add a Chinese interpretion of the bible in the core wallet so it can be used in China as a bible?

[bible_pay]

Do we have any Chinese users here reading this thread that can help verify the Chinese Bible reader in the core wallet?

We're going to add a Chinese native translation of the Bible, so our Chinese wallet users can read the CNV directly from BiblePay-QT.

[bible_pay]

17:10:03

exec readverse GEN 1 CN


17:10:04

{
  "Command": "readverse",
  "Book": "GEN",
  "Chapter": 1,
  "Language": "CN",
  "GEN 1:1": " 起初，神創造天地。",
  "GEN 1:2": " 地是空虛混沌；深淵上一片黑暗；神的靈運行在水面上。",
  "GEN 1:3": " 神說：'要有光！'就有了光。",
  "GEN 1:4": " 神看光是好的，他就把光暗分開了。",
  "GEN 1:5": " 神稱光為晝，稱暗為夜。有晚上，有早晨；這是第一日。",
  "GEN 1:6": " 神說：'眾水之間要有穹蒼，把水和水分開！'事就這樣成了。",
  "GEN 1:7": " 神造了穹蒼，把穹蒼以下的水和穹蒼以上的水分開了。",
  "GEN 1:8": " 神稱穹蒼為天。有晚上，有早晨；這是第二日。",
  "GEN 1:9": " 神說：'天下的水要聚在一處，使旱地露出來！'事就這樣成了。",
  "GEN 1:10": " 神稱旱地為地，稱水的聚處為海。神看這是好的。",
  "GEN 1:11": " 神說：'地上要長出青草、結種子的蔬菜和結果子的樹木，各從其類，在地上的果子都包著核！'事就這樣成了。",
  "GEN 1:12": " 於是，地上長出了青草和結種子的蔬菜，各從其類；又長出結果子的樹木，各從其類，果子都包著核。神看這是好的。",
  "GEN 1:13": " 有晚上，有早晨；這是第三日。",
  "GEN 1:14": " 神說：'在天上穹蒼中，要有光體來分晝夜；這些光體要作為記號，定節令、日子和年歲；",
  "GEN 1:15": " 它們要在天上穹蒼中發光，照耀地上！'事就這樣成了。",
  "GEN 1:16": " 於是，神造了兩個大光體，大的管晝，小的管夜；又造了星星。",
  "GEN 1:17": " 神把這些光體安放在天上穹蒼中，照耀地上，",
  "GEN 1:18": " 管晝夜，分光暗。神看這是好的。",
  "GEN 1:19": " 有晚上，有早晨；這是第四日。",
  "GEN 1:20": " 神說：'水要滋長生物；地上和天空之中，要有雀鳥飛翔！'",
  "GEN 1:21": " 於是，神創造了大魚和在水中滋生各種能活動的生物，各從其類；又創造了各種有翅膀的飛鳥，各從其類。神看這是好的。",
  "GEN 1:22": " 神就賜福給牠們，說：'要繁衍增多，充滿海洋；雀鳥也要在地上增多！'",
  "GEN 1:23": " 有晚上，有早晨；這是第五日。",
  "GEN 1:24": " 神說：'地上要生出活物來，各從其類；牲畜、爬行的動物和地上的野獸，各從其類！'事就這樣成了。",
  "GEN 1:25": " 於是，神造了地上的野獸，各從其類；牲畜，各從其類；地上各種爬行的動物，各從其類。神看這是好的。",
  "GEN 1:26": " 神說：'我們要照著我們的形象，按著我們的樣式造人；使他們管理海裡的魚、空中的鳥、地上的牲畜，以及全地，和地上所有爬行的生物！'",
  "GEN 1:27": " 於是，神照著自己的形象創造人；就是照著神的形象創造了他；他所創造的有男有女。",
  "GEN 1:28": " 神就賜福給他們，對他們說：'要繁衍增多，充滿這地，征服它；也要管理海裡的魚、空中的鳥和地上所有走動的生物。'",
  "GEN 1:29": " 神說：'看哪！我把全地上結種子的各樣蔬菜，和一切果樹上有種子的果子，都賜給你們作食物。",
  "GEN 1:30": " 至於地上的各種野獸，空中的各種飛鳥，和地上爬行有生命的各種活物，我把一切青草蔬菜賜給牠們作食物。'事就這樣成了。",
  "GEN 1:31": " 神看他所造的一切都很好。有晚上，有早晨；這是第六日。"
}

[togoshigekata]

TOKOK BBP Trading Competition
https://tokok.zendesk.com/hc/en-us/articles/360000507042

11:00 on September 17，2019 (UTC+8)

BBP trading opens in 2 hours?
https://www.timeanddate.com/worldclock/timezone/utc8

=

Learn More about BBP Listing on Tokok:
https://www.reddit.com/r/BiblePay/comments/d39muh/biblepay_will_be_listed_on_tokok_exchange_on/

=

EDIT: I registered an account,
I see BBP in "Funds List"
I was able to deposit coins
I believe trading begins at 12:00 UTC+8

EDIT 2:
https://www.tokok.com/market?symbol=BBP_ETH

[bible_pay]

TOKOK BBP Trading Competition
https://tokok.zendesk.com/hc/en-us/articles/360000507042

11:00 on September 17，2019 (UTC+8)

BBP trading opens in 2 hours?
https://www.timeanddate.com/worldclock/timezone/utc8

=

Learn More about BBP Listing on Tokok:
https://www.reddit.com/r/BiblePay/comments/d39muh/biblepay_will_be_listed_on_tokok_exchange_on/

=

EDIT: I registered an account,
I see BBP in "Funds List"
I was able to deposit coins
I believe trading begins at 12:00 UTC+8

I just logged into the exchange and I see BBP in the "New" tab!

[SVK Noko]

Good Morning

It looks BBP/ETH trading is alive already on Tokok exchange.

[jsheets1970]

Is the pool down? Url is unreachable.

[bible_pay]

** Pool.biblepay.org is down with an unexpected hardware problem **

We are working on it.

God bless everyone.

[bible_pay]

** Pool.biblepay.org is down with an unexpected hardware problem **

We are working on it.

God bless everyone.

Ok, the pool is up.  Everything is still whirring.

[sukoyomi]

Good Morning

It looks BBP/ETH trading is alive already on Tokok exchange.

Yeah he is already live in Tokok and don't forget about the trading competition for top 50 trader. I would say it was the best move for gain volume in the new exchange, I'm sure people will pay attention.

[MIP]

Good Morning

It looks BBP/ETH trading is alive already on Tokok exchange.

Yeah he is already live in Tokok and don't forget about the trading competition for top 50 trader. I would say it was the best move for gain volume in the new exchange, I'm sure people will pay attention.

I see some bogus trading there on small quantities, sounds like a bot buying with one account and selling the same with the other, so the first account can reap the prize after buying millions (and selling millions with the second one).

I wonder if the exchange owners can detect this fraud and disqualify those accounts from the contest.

[bible_pay]

*** SANCTUARY VOTING ISSUES ***

I see a lot of proposals in this month with a missing forum thread URL for discussion (IE being populated with the domain only thereby circumventing a discussion).

I can "sort of" see Sun's URL and one of Togo's (the one with a BTCtalk thread on it) to be votable - but even in those cases - they don't allow questions to be posed about the work that was done, or the amount being requested etc.  So even those will be "hard" to vote on.

I would like to take this time to add a rule - that any proposal that is added - that you expect to be voted on - must be created with a dedicated discussion thread for it.

I recommend re-entering these proposals.

It would be a disgrace to vote up these proposals and set a bad precedent - so in this case assume that these will either not be voted on or voted down- unless they are corrected.

[bible_pay]

Good Morning

It looks BBP/ETH trading is alive already on Tokok exchange.

Yeah he is already live in Tokok and don't forget about the trading competition for top 50 trader. I would say it was the best move for gain volume in the new exchange, I'm sure people will pay attention.

I see some bogus trading there on small quantities, sounds like a bot buying with one account and selling the same with the other, so the first account can reap the prize after buying millions (and selling millions with the second one).

I wonder if the exchange owners can detect this fraud and disqualify those accounts from the contest.

Its too early to know if they are "bogus" or not;  What I see so far is a lot of trades being executed between the bid and ask, that are in the execution list and on the chart but not in the order book. 

I think Tokok might have some type of market maker program where they provide an edge for people to buy/sell off of the level 2 book (IE if you act as a market maker you take part of the trading fee, if you take liquidity you pay the fee etc).  Its not clear to me "who" is running the bot, if its an exchange bot, or a market maker jumps in on every new ticker (similar to pools who jump on new coins the moment they are released).

Someone would need to ask Tokok who runs this.  One thing I did notice, is the trade that is executed in-between the bid & ask just now did change the chart and volume.  So the other question is, do market makers get special privileges (to trade bots between the market that arent even part of the order book)?  (As these small trades dont go in the order book).

Lets see how it plays out when we get entered into the ETH page, hopefully more people from China/Hong Kong will come on board and be part of BiblePay.

[jc12345]

What is the impact on stability by running different version of nodes? I notice on the Cryptoid block explorer a wide range of versions running ranging from 1.4.3.2 to 1.4.4.7 and one unknown version number. Will the old ones just be ignored or are the differences not mandatory.

[bible_pay]

What is the impact on stability by running different version of nodes? I notice on the Cryptoid block explorer a wide range of versions running ranging from 1.4.3.2 to 1.4.4.7 and one unknown version number. Will the old ones just be ignored or are the differences not mandatory.

Basically, we have not had a hard fork consensus break since 1.2.0.1 (that changes the consensus rules), so we have these old versions still running because they can - and there is very little harm in running the old versions.  That's why you still see some older versions in 'versionreport' because we havent enforced the upgrade in a hard way - this is primarily driven because we are trying to keep the exchanges on the last mandatory as long as possible.  (They view it as a nuisance to upgrade and could delist us if we abused the privilege).

The more recent versions are more efficient with gobject propagation.  Some things we learned this year require us to add business logic on top of dash's logic to delete old objects.  Then we have the endeavor to upgrade to deterministic sancs (pushed by Dash .14) in the recent versions, with the turnkey providers not supporting deterministic, so we are now adding code and testing it that allows workarounds to upgrade to deterministic in steps, etc.

In about 90 days though we should have all this consolidated into the .14 branch and be "allowed" to push a mandatory again - that would cause everyone to upgrade to one single version.