|
BiblePay
1.4.4.9 - Leisure Upgrade
- Add CPK and height params to 'exec sentgsc cpk height' report. This
allows you to audit a CPKs sent GSC/ABN transmissions per superblock
height.
- Add roi target_bbp_tithe to 'exec roi amount' report. This shows the
ROI for a specific bbp tithe amount.
- Add 'exec cameroon_payments [xml/auto]'. This report shows payments
sent to cameroon one for POOM - NOTE: This report only shows payments
sent via 'exec paycameroon'.
- Added block range result to 'leaderboard' rpc command.
- Added automatic change of up to 10 outputs for each created abn.
Note: We do not create change if the change will be less than the
minimum ABN amount. You may set the key -changequantity=nnn to change
the default to up to 50 outputs. (All this is for is to let ABN change
age in smaller distributed chunks - thereby utilizing coin-age more
efficiently for the next abn).
- Fix crash at startup in OSX (MIP)
- Add nonstandard port # to global health report.
** This is the windows release. MIP will announce when linux/mac is ready. **
|
|
|
|
|
We have a new feature in the pool called "Sanctuary Health" (under Reports | Sanctuary Health Report).
This report shows a list of Bad Sancs - sancs who are forked.
What's useful about this report (above the core wallets status per sanc is):
1. It detects forks - we can see if a sanc is off the chain (in contrast to showing ENABLED and actually being unhealthy).
2. It gives us a percentage of network health (IE if all the sancs are at the same best block, we know the % of health for the entire network).
3. It gives you an alternative block number and blockhash to check independent of the explorers - technically one that is the most reliable because its for 100+ nodes.
4. It detects geographical outages. If a segment of our network is out, we will see a swath of people with invalid PAM hashes at the same time.
5. It will be valuable for our GSC voting levels and gobject propagation. If all the votes are in agreement (or generally, almost exactly the same) then we know we have 100% GSC health. We can add a GSC health % to the report later.
I'm modifying it now to handle nonstandard port #s.
We currently have a health level of 97% and 100% health level for gobject propagation, meaning Im happy that 1.4.4.8 is addressing the gobject problem.
I also see less network utilization per day.
EDIT: Btw, the reason we only show 116 active sancs so far is this report only works with 1.4.4.8+ protocol version. We are waiting for those remaining sancs to upgrade.
|
|
|
|
CameroonOne is the Boston branch that focuses on the Cameroon-Africa children (where Hilary and Todd works), but they are owned by OneTrack Intl. From what I understand when we ask for a new child to be sponsored, Todd reaches out to One Track and they provide the new child. I'm currently searching for children in Israel. God says in Genesis 12:3, I will bless those that bless you, and curse those that curse you (to Abraham). I feel like if we start blessing Israel, we can see our project be blessed. |
|
|
|
anybody got some reward in trading comeptition on tokok?
i bought about 5m so i believe i was pretty high in rank, but no reward yet
Yeah I got 9574 cool, finaly today i got reward  021909271540298654328 BBP 100000.00000000 0.00000000 2019-09-27 09:40:29 Completed Activity/Airdrop so i was third? Congratulations. I don't know who won personally. |
|
|
|
Togo, can you please ask someone to ask CryptoBridge to put us in maintenance, or ask them for us?
Task completed, CryptoBridge has been notified in their Discord, in private #bbp channel with CryptoBridge admins If you and/or MIP are interested in joining into that channel, just let me know and I will ask them to add you in CryptoBridge Discord: https://discordapp.com/invite/H6Qt2dQThat Bridge guy has been treating his own customers with discord and very high level of contempt. If u let him deprave this coin also, I will leave and close the door behind me. Public expressions of detestation demonstrated in a closed channel is a sort of conduct which makes him look like an angry social worker. Too much beverage in his stomach confused his neurocortex capabilities. Thanks; Togo, let us know if he is disrespectful to you. |
|
|
|
I'm sorry if the comment is offense to you or Dev.
I just conveyed the information what we discussed.
This information does not affect my confidence in TOKOK, because I currently use it as a BBP deposit and trading other coins.
It’s just that I don’t think we have a clear understanding of China’s domestic market information, and that their mainstream direction is on which side.
No problem my friend, I'm sorry I came across harshly. If you can find any of the major exchanges in China that have a low quote, or are willing to list us, please enter us and I will be happy to finish the integration. |
|
|
|
** Notice of New BiblePay version coming soon **
Someone asked recently if these old versions were harming biblepay.
I've been doing analysis of governance propagation and I'm coming to the conclusion that these old versions *are* hurting biblepay.
I'm seeing that the reason we have excessive traffic and a failure to replicate objects is the high percentage of nodes that never upgraded (25%-50% are running a version that has different gobject propagation rules).
In light of this we will be having a mandatory upgrade soon (within 7 days).
Please keep an eye on this thread.
The reason why I asked is that sometimes older nodes are problematic with some other coins. If I want to run a node, will the new mandatory upgraded wallet compile on Ubuntu 19.04? I am trying to get a away from Ubuntu 14/16. In our case it was just a matter of trying to get mileage out of this last mandatory "era" but we're pressed to force it. I assumed 95% would upgrade when we released that version with the gobject rules, but what actually happened, (I believe), is a lot of miners kept the old version for some reason, and Im seeing that they aren't forwarding our gobjects. If they are in a diverse location, this means we have pockets of areas where the objects dont get forwarded. Ill have to ask MIP on that question; MIP do you know if our binaries support 19.04? |
|
|
|
|
** Notice of New BiblePay version coming soon **
Someone asked recently if these old versions were harming biblepay.
I've been doing analysis of governance propagation and I'm coming to the conclusion that these old versions *are* hurting biblepay.
I'm seeing that the reason we have excessive traffic and a failure to replicate objects is the high percentage of nodes that never upgraded (25%-50% are running a version that has different gobject propagation rules).
In light of this we will be having a mandatory upgrade soon (within 7 days).
Please keep an eye on this thread.
|
|
|
|
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. it is not bot or someone, it is just fake volume generator. it is generating orders between buy and sell. if buy will be 200 and sell 201 then it will stop, you can try. same with eth, ltc or other coins, just check. same was on qiex. I'm not sure I come to the same conclusion. The IT dept of Tokok sent me a 100meg "program" and asked me if I wanted to be a market maker. It requires a massive amount of setup. It has a lot of rules. I wasn't particularly interested in it because I've got a backlog and more important things to do for God. But it sort of appears to be the same thing being run by someone else - they put in a certain amount of risk capital, IE .50 BTC, add in the business logic and let it run and it executes these through the API. The thing I don't know about is if those trades in between bid-ask are "real" on a level2 book. Someone should ask Tokok if they really debit/credit balances with those (for professional traders etc). |
|
|
|
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. Thanks for the reply and it makes sense. Have you considered reducing the coin supply from 1.78bn to a lesser amount of say 1.78m? A lesser number of coins are almost always more preferable and of interested to the market. I also looked at the links to the exchanges to try and analyse the trading patterns and noticed that the C-CEX link on p1 does not work. Thanks for the update: I removed QIEX and C-CEX and added Tokok. As far as the supply count: I personally believe in the original 5~ billion max supply for a few reasons. One, I feel people who don't care about BBP lose more coins per year (IE coins that people could care less about if they accidentally lose the wallet or throw away the PC) - because they are dealing with tiny numbers. I think over time, this will result in higher prices for us. But more importantly, I think we will design a novel service that will use up all of our coin supply- over the long term. For one, we have an announcement coming at the end of the month, for a new product called DSQL that will act as a utility (allowing people to buy and sell BBP for gas-type transactions in a decentralized database). The other larger use case is we are investigating document mining. If we ever make this part of the mining algorithm, miners will prove allocated space and users will lease the space for Christian storage, etc. Once we have this and church tithing I think we will be able to setup an environment where each currency unit becomes much rarer. On an unrelated side note, Sun asked if I believe in DGW: Yes, I still personally like DGW also. The document storage sounds interesting. Although several other coins have done something similar ( Storj comes to mind). Will the storage reside on the mining nodes or somewhere on the cloud and rights protected by the crypto and blockchain? Things that come to mind are distribution of gospel music and storage of biblical texts. What was interesting with other storage projects is that it becomes almost impossible to ensure that the content stays on topic. A content storage container on the Internet will very quickly become eg. a pornographic content store. Yes, there are a few other coins that lease space out for decentralized storage, although its not clear which are in production (I read a few months ago there were still technical problems with each solution). We will be the first in production with reverse DNS and a decentralized SQL server. We will be the first with human readable URLs. The data will not be stored at cloud providers; it will be stored in zones across BiblePay BMS nodes. In the first baby step, a volunteer will have to host a BMS node and run it on a piece of hardware such as a sanctuary and expose port 443. But in the future as we design BIPFS mining, a miner may host a zone on their home machine potentially (this is completely unknown at this point) but I would imagine 10-20 miners hosting the same zone for durability. As far as MPIAA, GDPR, RIAA takedown requests, the person leasing the storage will need to post a collateral transaction before they use BIPFS for storage. Potentially $10-$20 or so minimum in a DSQL account, and each DSQL account is linked to the CPK. Our server will automatically deduct fees from that account as time passes or as it is used. If someone finds a hash pointing to porn we have a page - called a takedown request page - where the hash gets inserted in the DSQL table - in the takedown list permanently (this makes BMS physically delete it and block it). I think what we can do is sieze the account of the person who did it and donate it to the foundation as a penalty, etc. So because we will be the first with true decentralized reverse dns, we will be able to police this as we receive complaints. I agree that we should probably make this a Christian oriented service and potentially not open to the whole of internet content. We can control this by setting the fees appropriately. If its expensive to host a video no one will host a video. But we can host the Christian Treasure Trove (IE the protected data that the Antichrist will try to scrub), including end-time and rapture videos, gospel songs, and Vatican documents at a discount, etc. |
|
|
|
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. Thanks for the reply and it makes sense. Have you considered reducing the coin supply from 1.78bn to a lesser amount of say 1.78m? A lesser number of coins are almost always more preferable and of interested to the market. I also looked at the links to the exchanges to try and analyse the trading patterns and noticed that the C-CEX link on p1 does not work. Thanks for the update: I removed QIEX and C-CEX and added Tokok. As far as the supply count: I personally believe in the original 5~ billion max supply for a few reasons. One, I feel people who don't care about BBP lose more coins per year (IE coins that people could care less about if they accidentally lose the wallet or throw away the PC) - because they are dealing with tiny numbers. I think over time, this will result in higher prices for us. But more importantly, I think we will design a novel service that will use up all of our coin supply- over the long term. For one, we have an announcement coming at the end of the month, for a new product called DSQL that will act as a utility (allowing people to buy and sell BBP for gas-type transactions in a decentralized database). The other larger use case is we are investigating document mining. If we ever make this part of the mining algorithm, miners will prove allocated space and users will lease the space for Christian storage, etc. Once we have this and church tithing I think we will be able to setup an environment where each currency unit becomes much rarer. On an unrelated side note, Sun asked if I believe in DGW: Yes, I still personally like DGW also. |
|
|
|
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. |
|
|
|
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. |
|
|
|
|
*** 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.
|
|
|
|
Hi , im from Brazil and i can not verify my cell number. someone can give me some BBP ?
BJqUAoGJ2ohVJYsnhfQBUyhfjwDq8FGjNS
Sent. Welcome aboard! |
|
|
|
** 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. |
|
|
|
|
** Pool.biblepay.org is down with an unexpected hardware problem **
We are working on it.
God bless everyone.
|
|
|
|
I just logged into the exchange and I see BBP in the "New" tab! |
|
|
|
|
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": " 神看他所造的一切都很好。有晚上，有早晨；這是第六日。"
}
|
|
|
|
|
Show Posts
