Looks like its a JSON error expecting a value to be surrounded by double quotes, not sure if its related to the commands you entered in earlier? Alright, I just told the pool to release the current budget (this is a decentralized feature btw, its just a one page hex command that is a little technical, if I die Im sure someone here like Alex can figure it out, you then paste this 300,000 hex command into a valid masternode - any biblepay masternode and it kicks it over for the next superblock). This combines our winning proposals into a budget object and creates a superblock trigger for the next height. The budget TXID is updated on the current proposal records and they become budget proposal records in contrast to proposal records.
Anyway, the superblock is coming at block 24600 (getsuperblockbudget 24600).
|
|
|
Seeing my Sanctuary and a lot of Sanctuaries in list with WATCHDOG_EXPIRED status ~/.biblepaycore/watchman# cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py Traceback (most recent call last): File "bin/watchman.py", line 244, in <module> main() File "bin/watchman.py", line 191, in main perform_biblepayd_object_sync(biblepayd) File "bin/watchman.py", line 24, in perform_biblepayd_object_sync GovernanceObject.sync(biblepayd) File "lib/models.py", line 87, in sync (go, subobj) = self.import_gobject_from_biblepayd(biblepayd, item) File "lib/models.py", line 117, in import_gobject_from_biblepayd object_hex = biblepaylib.SHIM_deserialise_from_biblepayd(object_hex) File "lib/biblepaylib.py", line 204, in SHIM_deserialise_from_biblepayd obj = deserialise(biblepayd_hex) File "lib/biblepaylib.py", line 229, in deserialise obj = simplejson.loads(json, use_decimal=True) File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/__init__.py", line 533, in loads return cls(encoding=encoding, **kw).decode(s) File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py", line 370, in decode obj, end = self.raw_decode(s) File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py", line 400, in raw_decode return self.scan_once(s, idx=_w(s, idx).end()) simplejson.scanner.JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 1673 (char 1672)
|
|
|
BiblePay (BBP)- 10% mined coins always go to Charity (already sponsoring 180+ Orphans monthly) - ASIC-Resistant like Vertcoin/Groestlcoin (CPU Mining Only) - fork of DASH (Masternode Governance Model, Budget Proposals & Voting) - POBh Proof of BibleHash Algorithm, All Nodes are Full Nodes Learn More: https://bitcointalk.org/index.php?topic=2388064.0 Personally I'm a little uncertain if it fits the criteria or not. My concerns are: 1. Proven development team. Not sure we can conclude a development team is proven after less than six months. 2. Obvious use case. Any coin can be used for charity, and several have it as their main focus. I don't believe that a coin who's only use case is charity has much chance of wide spread adoption, and thus also will fail as a charity coin. Maybe togoshigekata can elaborate on this? Despite my above concerns, I believe it warrants a discussion about adding them to the list or not. Arguments have been made for all five criteria, and unless they are met by counter arguments, the coin should make it to the list. 6 months is to young to be added to the list.If this coin will be added there can be added dozens of coins and that wouldnt be the sense of the thread i think. The sense is to make a list with the best coins.Real longterm projects,fair,with a real usecase.Not any coins that is a little better then the rest.There are to many out there..
I also think they should not be added, but they made arguments for all 5 criteria so it's fair to discuss it before dismissing them I think. I don't believe we can have any criteria for how old the coin should be to be accepted. Some coins go through a lot of development before they launch. But in this case I think they are to young to deserve the label proven. I base this on the age of the coin + one more argument that I did not make above; One of the arguments this is a proven team, was that the lead dev has 20 yours of coding experience. That is a good starting point of course, but does not make him a proven blockchain dev. We have several code monkeys in BitBay with a life long coding experience. They are very talented, but there is still a lot they don't know about blockchain. The reason that is not a problem in BitBay is that they have David to go to for guidance and code review. I don't see any experienced blockchain devs listed in the argument for BBP being proven team. Thank you for the responses! The Lead Developer has so far remained anonymous, but has claimed he has past experience working on another successful cryptocurrency. If he does ever reveal himself or his past work, I will post back. Here are details about the team he is building for BiblePay: https://www.reddit.com/r/BiblePay/comments/75hozh/slack_team/Here is lead dev talking about integrating with Stratis: https://www.reddit.com/r/BiblePay/comments/7i9pfp/stratis_fork/=== Use Case wise, there are definitely other charity coins: Bunnycoin: https://coinmarketcap.com/currencies/bunnycoin/Donationcoin: https://coinmarketcap.com/currencies/donationcoin/Cleanwatercoin: https://coinmarketcap.com/currencies/cleanwatercoin/Wishcoin: https://bitcointalk.org/index.php?topic=2250891.0 (ICO starts Feb 20th 2018) Dogecoin: has a charity foundation and has donated to provide clean water: http://foundation.dogecoin.com/Solarcoin: has some coins in reserve to go to environmental charities There are also websites you can visit and leave open to mine Monero to go to Charity https://www.charitymine.org/https://donateyourtab.to/https://mineforcharity.com/If you guys know about or find any more charity coins, please let me know! === Also BiblePay has goal to spread Christianity and has budget allocated for Pay to Preach/Priest, as well as in-wallet prayers, and rewards for listening/reading/watching Gospel links. And lead dev has more ideas to spread Christianity: https://www.reddit.com/r/BiblePay/comments/7du3kg/spreading_the_gospel_knowing_jesus/There are some other Christian coins: JesusCoin - is a joke coin ChristCoins - Pre-mined ICO, will reward for reading the Bible on their website which is really cool === Thank you for reading and giving feedback! I will post back if lead developer unmasks himself. Thanks!
|
|
|
BiblePay (BBP) is a new CPU Mining Only coin that I believe has a lot of future potential worth - 10% mined coins always go to Charity (already sponsoring 180+ Orphans monthly) - ASIC-Resistant like Vertcoin/Groestlcoin ( CPU Mining Only) - fork of DASH (Masternode Governance Model, Budget Proposals & Voting) - POBh Proof of BibleHash algorithm, All Nodes are Full Nodes Launched July 23rd 2017, Market Cap ~1 million https://bitcointalk.org/index.php?topic=2388064.0
|
|
|
BiblePay (BBP)- 10% mined coins always go to Charity (already sponsoring 180+ Orphans monthly) - ASIC-Resistant like Vertcoin/Groestlcoin (CPU Mining Only) - fork of DASH (Masternode Governance Model, Budget Proposals & Voting) - POBh Proof of BibleHash, All Nodes are Full Nodes Launched July 23rd, 2017 - Market Cap ~1 million https://bitcointalk.org/index.php?topic=2388064.0
|
|
|
This may come from my lack of knowledge about superblocks, I think they have something to do with this, Ill dig into it. === "I'm no expert but I believe superblocks are created every x blocks where x is about a month long. Proposal owners predesignate payment addresses. Superblocks create funds based on the requested amount from proposals that passed (up to the monthly maximum) and send them to the addresses. If more funding was successfully requested than can be afforded by the budget I think higher net yes vote proposals have priority. Any proposals that passed but didn't get funded (due to lack of funds) must be resubmitted the next month." https://www.reddit.com/r/dashpay/comments/65vkza/what_are_super_blocks_how_do_they_come_into/"During the month, anybody can make a budget proposal to the network. If that proposal is approved by at least 10% of the masternode network, then at the end of the month a series of "superblocks" will be created. At that time, the block rewards that were not paid out (10% of each block) will be used to fund approved proposals. The network thus funds itself by reserving 10% of the block reward for budget projects." https://www.dash.org/governance/=== https://github.com/biblepay/biblepay/blob/853affd8c070bfbfd8069abd4e4e8fc83f30afb9/src/masternode-payments.cpp#L104=== BiblePay Proposals http://forum.biblepay.org/index.php?board=5.0Pool >>> Left tab Governance >>> Proposal List https://pool.biblepay.org/Anyone can create a proposal and request payment of BBP coins for work! (But I believe now we may be in the BUDGET phase for current proposals, so you can still propose work for next month right now)
|
|
|
BiblePay (BBP)- 10% mined coins always go to Charity (already sponsoring 180+ Orphans monthly) - ASIC-Resistant like Vertcoin/Groestlcoin (CPU Mining Only) - fork of DASH (Masternode Governance Model, Budget Proposals & Voting) - POBh Proof of BibleHash, All Nodes are Full Nodes Market Cap ~1 million https://bitcointalk.org/index.php?topic=2388064.0
|
|
|
BiblePay (BBP)- 10% mined coins always go to Charity (already sponsoring 180+ Orphans monthly) - ASIC-Resistant like Vertcoin/Groestlcoin (CPU Mining Only) - fork of DASH (Masternode Governance Model, Budget Proposals & Voting) - POBh Proof of BibleHash Algorithm, All Nodes are Full Nodes Launched July 23rd 2017, current market cap ~1 million https://bitcointalk.org/index.php?topic=2388064.0
|
|
|
BiblePay is CPU Mining Only coin, 10% of mined coins go to charity to sponsor orphans
|
|
|
You dont necessarily need GPUs or ASICs to mine, some coins are CPU mineable, like BiblePay
|
|
|
Rob thank you again for all of your hard work!!! These challenges make BiblePay even stronger. But I am sorry you bear the majority of the work/burden. I will keep continuing to help as much as I can.
It seems like we will continually have to deal with those that are misinformed, mean, attacking and trolling. You mentioned in the beginning of the project that there may even be coordinated attacks on BiblePay going forward. There has been more FUD spreading recently on the Reddit from two new accounts, as well as investor above who is a new account.
===
If you believe that BiblePay is a scam, or that Rob is a scammer, then why not walk away?
|
|
|
Recapping the pool issues: We had two different problems hit the pool at once: instability, this is what Tiras reported days ago, and inconsistent hash readings, this has to do with your shares relative to other people.
Tiras, Tom both reported similar things- where random workers would drop off the list.
I found the root cause of the problem for the instability. Its now fixed, I believe permanently.
Next, Ill check on the HPS relative to others...
Pool issues fixed...
You should not see any missing workers in the pool, if one is missing, before posting here please restart the node once, and ensure it is running 1.0.7.1. 1.0.7.1 is now required by the pool for solutions to be correct.
I'll add two more columns to the pool for easier troubleshooting and for some new information...
Just when the pool was catching up with its deficit (I was about to lower the fee down to .04 from .05) as it was within -400,000 deficit range (for Slovakia thats how much was Lost since inception not counting the faucet that I spent 150K on), someone has hacked the pool last night. There is no trace of entry on the box, or a request for the withdraw in the logs, but this means the pool is not going to be cheap again for a while. If you prefer to solo mine due to the fees, I understand, go for it. Im not out to make a profit. Anyway, if anyone wants to try to trace the hacker, here is the info for some of the withdraws in the middle of the night around 02:02am CST US time: https://biblepay-explorer.org/address/BA6wJpAbA4WCNK9X1UwgnweCSCXCGYPZ71Id prefer to work in slack on the finer details. Alex when you wake up please ping me. unfortunately that means we have to write yet another system that requires withdrawals to go through a whole different server.
Ill work on this all day today and possibly unto the night to try to get the withdraws working again guys.
bible_pay if you using VULTR: they can monitoring loggin to your machine
Yeah, I am using Vultr? Are they known to steal the passwords from crypto configs or config files? If so maybe I should switch hosts. Either way its going to be so locked down tonight nothings coming out of the box but encrypted traffic, but please fill me in on vultr... Pool Fees: 18%
I'm a little overloaded right now, but here is a quick update: Im running a database maintenance script, and had to consolidate your balances owed into one more succinct record (in contrast to thousands of "mining_credit" records), this caused the server to think your balances are immature. All you have to do is subtract the two numbers and you will see the total owed is still the same as before the script was started. Ill take a look at putting it back to the way it was by tomorrow, but either way it will work itself out within 24 hours. Next, I have an idea how we can prevent the pool from being a hacking target. In the Python pool, they require a valid receiving address in order to mine. I think what we will do in the future is forcefully send your rewards out every time a block is solved - to your address on file. Give me a couple weeks to look into that feature, it may take a while to get that completely working, but I think that feature will button down the pool. The 18% fee is just temporary. Hopefully you realize this is in order to keep the pool running.
|
|
|
I wanted to diversify, Bitcoin has problems, but it does have first mover advantage and name recognition. But there are other coins trying different strategies and targeting different industries and functionality.
|
|
|
BiblePay (BBP)- 10% mined coins always go to Charity (already sponsoring 180+ Orphans monthly) - ASIC-Resistant like Vertcoin/Groestlcoin (CPU Mining Only) - fork of DASH (Masternode Governance Model, Budget Proposals & Voting) - POBh Proof of BibleHash Algorithm, All Nodes are Full Nodes Launched July 23rd 2017, current market cap ~1-2 million https://bitcointalk.org/index.php?topic=2388064.0
|
|
|
|