Awesome! Im very new to all this cryptocurrency stuff, like 1-2 month new I really like that this coin has a good cause I also like that there is a high amount of coins over a long span of time, makes it a lot more fair to give everyone a chance to jump in. And the governance/budget model from Dash is AWESOME. You have also been very active Rob! (look forward to a Slack team building up) ==== But yeah I worry about the average person. I think setting up a miner is a little too technical for most (having to deal with a config file / console commands). and trading for BBP has too many steps and can be scary, also the average person is probably going to be very intimidated by limit orders. But yeah Cryptocurrency in general has the issue of not being user friendly for the average person. ==== Currently I update the BiblePay reddit and twitter https://www.reddit.com/r/BiblePay/https://twitter.com/BiblePayAnd I wrote the mining guides for Windows and Linux https://www.reddit.com/r/BiblePay/comments/6umlqq/how_to_mine_biblepay_on_windows/ (1,600+ Views!) https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/ (600+ Views!) (I think I should probably put them on the wiki so everyone can edit and make them better) ==== I guess I could help out the Wiki now: http://wiki.biblepay.orgI was also thinking of writing a guide on how to buy BiblePay coins I haven't figured out how to market to non-crypto people, Ill keep thinking about it. One of my friends has been marketing some on christian facebook groups. Right now Ive been marketing BBP every now and then in cryptocurrency subreddits. I want to spread the word so everyone has a chance to be part of this! All in all, its cool that by owning coins, Im like a small part owner and Im motivated to see the value of those coins rise  I look forward to the future of BiblePay! |
|
|
|
|
@bible_pay youve been doing awesome work!
I was thinking about the average person yesterday,
I think we need an easy way to exchange fiat for BBP like Coinbase, not sure how easy or possible it is.
Right now to get BBP a user would have to create account on Coinbase, transfer money in, buy Bitcoin with market order,
Then set up account on C-CEX, transfer Bitcoin, then do limit order to buy BBP.
|
|
|
|
Hmm I cant seem to withdraw my BiblePay coins on C-CEX: https://c-cex.com/?p=bbp-btcWhen I click Withdraw button, loading symbol spins for a long time and then it brings me to an error page  I created ticket of issue with C-CEX support |
|
|
|
|
Weird, my one machine solo mining got a block reward, but it was only ~10,000 coins >.>
|
|
|
|
|
@bible_pay
Linux miner updated to v1.0.3.7 and mining
config set to pool.biblepay.org,
poolmining=false
block 7909
8 peers, only 1 peer v1.0.3.7
|
|
|
|
Today we have 3 fresh issues.
One, the Ddos is sort of under control, but the issue is becoming complicated, because there are a few type of attacks going on.
To isolate the problem, I upgraded the pool solution packet in the wallet in 1.0.3.7 - this is necessary anyway for technical reasons.
Id appreciate if some of the linux users can upgrade to 1037. Windows is compiling.
I cant access http://pool.biblepay.org/ in web browser "This site can’t be reached pool.biblepay.org took too long to respond. ERR_CONNECTION_TIMED_OUT" Upgrading my linux miner to version 1.0.3.7 |
|
|
|
We are on block 7777  @tiras Its just a Ryzen 1700 I got on Newegg "AMD RYZEN 7 1700 8-Core 3.0 GHz (3.7 GHz Turbo) Socket AM4 65W YD1700BBAEBOX Desktop Processor" and I installed Ubuntu Server 16.04 I think its running at 3.65GHz What type of machine is this? User Name Miner Name Hashes Per Second Hashes Per Second2 tiras tirasworks_bbp7 82846.46 39640.09 |
|
|
|
|
interesting, its back up again, near top of leaderboard now, interesting, sorry!
|
|
|
|
|
My linux miner on v1.0.3.5 hasnt been kicked off the pool but I have noticed that the Hashes Per Sec 2 for my linux miner has been slowly dropping all day today to where now its barely even anything, weird
|
|
|
|
When will be available the wallet c-cex.com??? I wrote "Maintenance..."
C-CEX is waiting for us to give them green light to upgrade. I want to ensure the ReadBlockFromDisk error is Dead before I green light them. Overnight, I made an update internally to the pool server with new code. Now I am burning it in. We will have to wait until I have time to parse the logs and ensure the error is dead. Unfortunately I'm still seeing them in the log: $ grep ReadBlockFromDisk .biblepaycore/debug.log
2017-09-15 11:25:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367325)ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7728.000000 pindexPrev 10c6e6494f851852a84d7b424d9f6a49d495641ebf2c295ab968a945360304d1
2017-09-15 11:25:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367533)UpdateTip: new best=610dfee89fba5d159dda3220ccd13bd34e7d4d61ecf30f748078a3c5c9a19fc9 height=7730 log2_work=50.41704 tx=11888 date=2017-09-15 11:25:28 progress=0.999999 cache=0.0MiB(192tx)
2017-09-15 12:09:39 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3367930)UpdateTip: new best=7979ac51d3e5863b78ad97bf10f27d9abb02595c6645c4993eec1eb9f3900b4a height=7733 log2_work=50.43361 tx=11897 date=2017-09-15 12:09:29 progress=0.999999 cache=0.0MiB(207tx)
2017-09-15 14:32:38 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3384546)UpdateTip: new best=bacafa8b5f5c929807fc3017dc41d38309d60de986263120e650e5ca666abdf6 height=7745 log2_work=50.509954 tx=11920 date=2017-09-15 14:32:32 progress=0.999999 cache=0.0MiB(14tx)
2017-09-15 14:33:55 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3384546)UpdateTip: new best=e3f5a72080b15fffa2ebd24d0533972104799f6cd9521b15f49f391512634a0c height=7746 log2_work=50.511569 tx=11921 date=2017-09-15 14:33:43 progress=0.999999 cache=0.0MiB(15tx)
2017-09-15 15:05:55 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3388192)UpdateTip: new best=68c4363a9102ae032eb12689f037a3b0844a38b89b6d200352b08ec7166432e9 height=7751 log2_work=50.530253 tx=11932 date=2017-09-15 15:05:45 progress=0.999999 cache=0.0MiB(23tx)
2017-09-15 15:51:57 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3390493)UpdateTip: new best=e1be025e9a1598121946284d0ba6da66884a7d679f3de9a85645d93d183fb4c9 height=7755 log2_work=50.555212 tx=11940 date=2017-09-15 15:51:04 progress=0.999995 cache=0.0MiB(11tx)
2017-09-15 16:38:39 ReadBlockFromDisk (Context MEMORIZEBLOCKCHAINPRAYERS): Errors in block header at CBlockDiskPos(nFile=0, nPos=3394676)UpdateTip: new best=625ed5a4e6ed12276e23f2a20c4fd728f0959a656f24922025c1a6dc17dc9a8b height=7758 log2_work=50.569175 tx=11951 date=2017-09-15 16:38:34 progress=1.000000 cache=0.0MiB(13tx)
What version are you using? Looks like dev commited version 1.0.3.5b 14 hours ago, which has potential fix for readblock error https://github.com/biblepay/biblepay/commits/master |
|
|
|
When will be available the wallet c-cex.com??? I wrote "Maintenance..."
C-CEX is waiting for us to give them green light to upgrade. I want to ensure the ReadBlockFromDisk error is Dead before I green light them. Overnight, I made an update internally to the pool server with new code. Now I am burning it in. We will have to wait until I have time to parse the logs and ensure the error is dead. Looks like you can still trade BBP on C-Cex: https://c-cex.com/?p=bbp-btcBut you can't withdraw or deposit BBP, so thats cool I didnt know maintenance mode meant you could still trade |
|
|
|
Upgraded to new 1.0.3.5 and tested the new build with linux miners, the miners are still dropping off from the pool as before . I'm pretty much running a recursive command as inblue does since yesterday. while [1]; do ./biblepayd -daemon && sleep 1300 && ./biblepay-cli stop && sleep 15; done Hmm, Im not sure if I agree with this; when I debugged yesterday, it was definitely the cache, and after 1035 the miner is definitely re-reporting every 6 mins; before the problem, my Vultr Nix box was dropping, After upgrade is not dropping; vultr nix log info showing it is working. Could you please try the latest version again without your script? My linux miner has been working great now since upgrading to 1.0.3.5 yesterday, doesnt get kicked off the pool anymore |
|
|
|
|
I noticed my linux miner seems to dissapear from the pool 10-60 minutes after restarting it, but it still says poolmining true
I do run the linux machine at 32 threads, is there still a thread limit on the pool?
Ill double check the debug.log but I think last time I checked nothing popped out at me.
|
|
|
|
What is the difference between Hashes Per Second and Hashes Per Second2
@bible_pay Is Hashes Per Second2 just a pool thing? Or is that a variable in the wallet/miner? I only see hashps with getmininginfo command |
|
|
|
************************
EXCEPTION: St13runtime_error
tinyformat: Not enough conversion specifiers in format string
biblepay in ProcessMessages()
2017-09-13 15:34:23 ProcessMessages(block, 191 bytes) FAILED peer=1
2017-09-13 15:34:23 89
************************
I got this error in 1.0.3.2 in debug.log, repeated many times, and it stopped syncing after that. The error started right after block 7099 has been synced. I am getting a similar error with Windows 32 bit v1.0.3.2 exe 2017-09-13 15:32:59 init message: Activating best chain...
2017-09-13 15:32:59
************************
EXCEPTION: St13runtime_error
tinyformat: Not enough conversion specifiers in format string
C:\Program Files (x86)\BiblepayCore\biblepay-qt.exe in Runaway exception
2017-09-13 15:33:02 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument
2017-09-13 15:34:21 |
|
|
|
|
"Christians remained the largest religious group in the world in 2015, making up nearly a third (31%) of Earth’s 7.3 billion people"
|
|
|
|
Im a little dissapointed on how many outgoing letters we have to our orphans. (We only had one person write one, and it doesnt even have enough upvotes to send it through the API).
I cant stress how important it is for us to send ONE letter to each distinct orphan every 60 days. We are supposed to be a compassionate organization - not a mining organization.
In light of this, a temporary solution (until we have a permanent sanctuary solution in place) is to encourage letter writing in the pool by charging a pool fee of 2% to any account holder who has not written a letter once per 60 days, unless, we have over N (being the distinct orphan count) of upvoted letters ready to be sent through the API at any given time.
So just to prepare everyone in advance, the rule would be something like this:
We have 74 orphans. If we have 74 positively upvoted outgoing letters over the last 60 days, there are no pool fees as the feature is not enabled. Once we are lacking, the feature is in force. When the feature is in force, any account holder who has not written one letter in the last 60 days is charged a 2% pool fee during block rewards. Users who have written a letter are skipped by.
This will be in effect by tomorrow.
I have been working with the API on facilitating inbound letters. We will have even more features once you have the ability to read the inbound letter and reply to it. These are things I simply cant manage myself - I am receiving mail from over 155 orphans in the mailbox - the entire bottom of my coffee table is full of 50 lbs of orphan welcome packets, pastor letters, crayon drawings, translator letters, orphan moving receipts, name changes, relatives of orphans moving down the street, something is coming every 15 minutes now, so I cant possibly keep up with all this so it must be automated and I need your help.
Once we have a little more time, I will enable the ability to add pictures to your outbound letters. In the mean time just write text letters as it is better to have something than nothing.
@bible_pay The column to write letters is missing from http://pool.biblepay.org/ >>> Orphans tab >>> Sponsored Orphan List? EDIT: OH, you have to right click the row and select Write Hmm how can we make that more intuitive / user friendly? |
|
|
|
|
Show Posts
