It's kind of hard to take biblical hermeneutics on holiness seriously from someone who goes by "coinpimp321". Not that it makes your point incorrect but rather it seems to me that if you applied the same level of zeal towards the label placed on masternodes on the label you place on yourself (which is itself a temple of the Holy Spirit according to 1 Corin. 6:19) you would have to change your name. It obviously doesn't bother you nor do I think it should, instead why not extend the same level of grace you extend towards yourself towards those who have no problem with the label "sanctuary" on a masternode? To quote St. Augustine of Hippo, “In essentials, unity; in non-essentials, liberty; in all things, charity.”, so let's err on the side of liberty and charity and instead acknowledge that there is an essential difference between the attitudes and goals of the money changers in the Temple of Solomon and those that would be running sanctuaries on BiblePay.

Does anyone have any insight to the sudden sharp decrease in block subsidy that occurred this morning? Did blocks start generating too fast again and we triggered a major reduction? I'm not sure where the best place to watch overall hashrate trends/block gen trends but it seemed like an odd occurrence.

Very nice... gotta keep on mining lol. Still working up to 100K, but time will see that happen.

Been reading the github in my (rare) spare time and am starting to get a few for the codebase.

One thing I've never completely understood is how sanctuaries will be implemented. When they are established, how exactly will selections be made on which nodes become Sanctuaries? Is it a matter of putting in a stake?

pool2 came up this morning and I'm mining on it....in fact B_P was asking for people to move over to it.

Based on the responses I was getting from their site I'd suspect they are getting DDOSd.

Thanks! I just checked out the REPO and am looking over the protocol doc, then I'll dive into the "DOC" folder....seems to be the best way to get my feet wet (and to loosen my C++ muscles....I've been working in typescript and C# for the last few years much more than C++). I would be interested in joining the Slack channel... I'm also working (unsuccessfully at the moment) to convince my programming cohorts to take interest as well.

I moved my two that are up over. How can we confirm if we are on pool 1 or pool 2? I don't see anything in getmininginfo that would help and the pool2 website shows workers for pool 1 and pool 2 it seems.

I'm trying to get out from under a pile of work but it is my goal to become familiar with the github source so I can contribute. When I do, does the project just follow typical github fork/pr contribution pattern?

I moved myself to testnet but I have no peers to sync with. Do I need a different initial peer list?

I was literally floating a very similar concept around with my other developer friends earlier this week. I feel like there is a lot of value (and difficult problems) in the concept of trying to tie value to the information itself rather than to valuing the gatekeeper to the information. There would be a lot to learn in this about how information is actually valued. One major problem would be dealing with prevailing group bias in pivoting what people want to hear vs what the reality is but it still to me sounds like something worth trying. i really like the idea.

The other big advantage is that with the way that BBP works, every one of these big miners is putting up a lot of full nodes and actually is beneficial to the crypto as a network (although causing some minor early headaches on the pools themselves). This is unlike most others where you run a miner that just pulls from a stratum pool and you can have thousands of miners running on a single full node. The value of a crypto is found in the network it holds and one thing I like about BBP is how it incentivizes being a full part of the network through the way it hashes and mines.

ac9f6a4cddcbdb04acbb6c117ac847f1ae1365da0878e714fb416a6ff6dff6c2 is my hash for 7480 for both my Windows and Linux nodes that I've upgraded so looks like I ended up on the right chain.

Shutdown biblepay, delete your banlist file (in windows it's in %appdata%/Biblepaycore) and restart....see if that helps.

Well I mean low CPU power mine-able deflationary cryptos that donate 10% of their value to sponsor the poor are really a dime a dozen /s


I shutdown and deleted my banlist file in %appdata%/Biblepaycore/banlist.dat then restarted and had more luck getting the last 2 days

Clean blocks, chainstate and banlist install on Windows and it loaded fine with no errors. Seems to be back up and mining. I think I see a light at the end of the tunnel here. (OK so the pool is down, but at least my systems are working ok).

After running a -reindex the core now launches but the debug still shows issues.



It seems to be functioning but stuck on 2 days behind in the reindex report in the gui.

Sorry to add to the list of errors, but the Windows client on Windows 10( PRO 64bit - 1.0.3.2) had a bout of throwing handled exceptions. Client didn't crash and it seemed to recover but I thought you would want to see these:

---

2017-09-13 15:45:53 ProcessNewBlock : ACCEPTED
2017-09-13 15:45:53 89UpdateTip: new best=2809f4104b07d723c0f40c923b3d0cd30dbf58d520d231ed049f998d2b553f0f  height=7449  log2_work=48.978403  tx=11461  date=2017-09-13 15:30:44 progress=0.999908  cache=0.0MiB(4tx)
2017-09-13 15:45:53 ProcessNewBlock : ACCEPTED
2017-09-13 15:45:54 89

************************
EXCEPTION: St13runtime_error      
tinyformat: Not enough conversion specifiers in format string      
C:\Program Files\BiblepayCore\biblepay-qt.exe in ProcessMessages()      

2017-09-13 15:45:54 ProcessMessages(block, 191 bytes) FAILED peer=2
2017-09-13 15:45:54 89

************************
EXCEPTION: St13runtime_error      
tinyformat: Not enough conversion specifiers in format string      
C:\Program Files\BiblepayCore\biblepay-qt.exe in ProcessMessages()      

2017-09-13 15:45:54 ProcessMessages(block, 190 bytes) FAILED peer=2
2017-09-13 15:45:54 89

************************
EXCEPTION: St13runtime_error      
tinyformat: Not enough conversion specifiers in format string      
C:\Program Files\BiblepayCore\biblepay-qt.exe in ProcessMessages()      

2017-09-13 15:45:54 ProcessMessages(block, 191 bytes) FAILED peer=2
2017-09-13 15:46:04 P2P peers available. Skipped DNS seeding.
2017-09-13 15:46:04 dnsseed thread exit
2017-09-13 15:46:15 89

************************
EXCEPTION: St13runtime_error      
tinyformat: Not enough conversion specifiers in format string      
C:\Program Files\BiblepayCore\biblepay-qt.exe in ProcessMessages()      

2017-09-13 15:46:15 ProcessMessages(block, 190 bytes) FAILED peer=7
2017-09-13 15:46:15 89

************************
EXCEPTION: St13runtime_error      
tinyformat: Not enough conversion specifiers in format string      
C:\Program Files\BiblepayCore\biblepay-qt.exe in ProcessMessages()      

2017-09-13 15:46:15 ProcessMessages(block, 428 bytes) FAILED peer=7
2017-09-13 15:46:15 89

************************
EXCEPTION: St13runtime_error      
tinyformat: Not enough conversion specifiers in format string      
C:\Program Files\BiblepayCore\biblepay-qt.exe in ProcessMessages()      

2017-09-13 15:46:15 ProcessMessages(block, 190 bytes) FAILED peer=7
2017-09-13 15:46:15 89

************************
EXCEPTION: St13runtime_error      
tinyformat: Not enough conversion specifiers in format string      
C:\Program Files\BiblepayCore\biblepay-qt.exe in ProcessMessages()

---

Seems to be functioning without it, and maybe it's due to the mixed version network right now but I wanted you to see anyway.

--edit-- I'll try relaunching and restoring the wallet

--continuing--

After removing wallet.dat and having a new one built I have this happen after the conclusion which crashes the app:

2017-09-13 16:08:24  wallet               146680ms
2017-09-13 16:08:24 init message: Activating best chain...
2017-09-13 16:08:24

************************
EXCEPTION: St13runtime_error      
tinyformat: Not enough conversion specifiers in format string      
C:\Program Files\BiblepayCore\biblepay-qt.exe in Runaway exception      


If I delete the new wallet and copy the old wallet.dat that worked with 1.0.3.2 earlier but had the recoverable errors, the application crashes like it did with the new built wallet. config.conf looks ok.

Do you know when the Windows version will hit the website to DL? The reason I ask is that Endpoint Antivirus (my workplace's choice for antivirus) has red flagged the 64 bit version's download link (not the file but the link) so I have to go through a bunch of fun phone gymnastics to get it downloaded and copied over here.

I will do a git pull for linux at 10AM and start the recompile, that should give some time.

Totally understand, just something to keep in mind for other projects as well. I've been promoting BBP among some of my friends (They are in the Houston area while I am in the Tulsa area....so not far from DFW) because despite our varying beliefs all of us find something to like with the project (I personally was drawn to the novel hash concept at first but then really fell in with the root cause of helping others through charity). My intention (when I'm less buried by work) is to go through the github and become familiar with the inner-workings but until then I figure I can write a few letters to kids, run a few nodes, and just be involved however. I'll keep my eyes open for when you float requests.

Thanks again for your work and vision on this project.