Does it recover, and still attach to main net and mine?  That could just be one peer connection being disconnected.

Im running 1018 on my external node with 383 connections and its mining, so it should be safe now.

One thing I forgot to mention:
Once you get everything set up, on the web site side, you have to click 'Switch to TestNet' every time you log in otherwise the pages, the reports, the hashes, everything will be against the wrong tables.  TestNet hashes against pool testnet, Main hashes against pool Main, but the GUI is all consolidated and relies on the user choosing the network ID every time they log in.

To test this:

Click 'switch to testnet', then click Block distribution and you should see the testnet distribution.

Good morning all!

Alright the pool is deployed here, so you can create web accounts and miners now:

http://pool.biblepay.org

Looks like testnet is running properly and I have a couple testers connected to my node.

So now go ahead and follow the instruction in the OP and lets see where our snags are.

I mined overnight against the testnet pool, and it worked for the most part but I did find a bug in 2 of the block payouts (out of the 12 I mined) these two block payouts were zero, and for some reason, when the pool asked the testnet external node for the block subsidy it returned zero - so if you look in the block distribution, you will see what Im talking about- so I will work on that today (while we test more blocks)-  I have a feeling its a race condition where the miner solved the block but the external node didnt even know about it yet, or something like that.

As far as open sourcing the pool: Yes, I am willing to do that, because it would also be nice to have more than one biblepay pool for users to hit, so all the users dont pound my server alone.  I think after about 100 concurrent users, my servers going to be pretty busy.  The main thing we have to address before its open sourced is to get the payout algorithm working reliably so we can tell if anyone makes a fraudulent compile and therefore the pool will catch that and still pay a rock solid hash reward back and the other thing that needs done, is to ensure the pool has sql injection protection on it, so no hacker can come in and steal the pools BBP balances - when I feel those are solid then we can post the code.

Great!   I have to head to sleep, but Ill be back around 9am or so.

Baby Step 1 is complete: I deployed an external testnet node.  Note that testnet is port 40001, while main is 40000.

The addnode is the same as main (node.biblepay.org).  The addnode is compiled in the wallet so no need to add it.

Lets check to see if we are all syncing.  Im on block 195 in testnet.  Anyone have any connections?

v1.0.1.8 is now available for download also: www.biblepay.org.


Lets verify we are actually connecting and syncing in testnet, and then we can move on to baby step 2.

Hi Everyone!

Biblepay Volunteers needed for TestNet Pool Testing:

https://bitcointalk.org/index.php?topic=2070177.new#new

Note: I am still in the process of deploying the pool now - so please wait until I edit the topic to inform everyone that 1.0.1.8 is ready to download and the poolurl is actually ready for traffic (ETA : 4-16 hours).

Yeah I saw that I had over 400 connections this morning on the external node, so I had to set maxconnections to 450.  Definitely gaining interest.  I wish I had time to buy a XEON server and do some hps benchmarks between linux and windows.  We will need to do this soon...

We are all just donating our resources for this test; dev starts with 0 bbp also and wrote the pool for free; just looking for free help from existing BBP community.  But, we welcome you to come on in and join us, here is our main thread:

https://bitcointalk.org/index.php?topic=2042657

Thanks.

Welcome Bible Pay Users,

As you know we have had an exponential increase in interest and network hashing against Bible Pay since the launch, and now it is very hard to solo mine.  As a result, our Dev Team is writing a customized Bible Pay pool.

(The custom pool is necessary since we have a proprietary hash function that is resistant to ASIC and GPU mining.  In addition in the future the algorithm will be extended to raise the bar even higher, by requiring the full nodes to hash transaction lookups based on deterministic hash outputs, requiring the miners to be full nodes).

The purpose of this thread is to invite users to help test the pool from Test Net, to ensure it is ready for primetime.

We need to test things like: Hash Rate measurements, fair block payouts in the block distribution table, an accurate payment distribution at the time the block is solved, mining from many miners under one miner name to one pool, mining from multiple miners to one pool, the isolation of testnet from main net, the ability to withdraw BBP from the pool, the reliability of the pool, the reliability of the client miner, the fallback to solo mining if the pool is down, etc.  I will add more specific test cases and welcome any test cases.

Here is the location to download the latest wallet:

www.biblepay.org
Note, in order to pool mine, you will need at least v1.0.1.8 of the wallet (both daemon and qt should work fine).

How to set up the configuration for pool mining:

On windows, navigate to %appdata%\biblepaycore.  On linux, navigate to ~/.biblepaycore.

Edit the biblepay.conf file, and place the following lines in the config:

poolport=80
pool=http://pool.biblepay.org <- Note this URL is not live until approx Monday Aug 7th (Dev is deploying the pool tonight)
workerid=the_worker_id (explained below)
gen=1
genproclimit=10


After upgrading biblepay and modifying the config, biblepay wallet will automatically revert to solo mining if it cannot connect to the pool, even if the pool goes down for maintenance while you are on vacation.

Next, you will need to configure the Web site side of the pool.

In your web browser navigate to the Pool URL (see pool= above), and click Register, and create a web account.
After that, go the Main menu, then Account, and add a Miner.
(The Notes textbox may be filled in with something personal, like Rooftop linux i686 etc.)
Save the miner record.
Take the name of the miner (IE the worker ID), and edit your config file, setting it where we have "workerid=" in the above example and restart biblepay.

Next, check your mining stats as you normally would (IE check getmininginfo), you may do this by clicking Tools | Information | Console, and then type "getmininginfo".

The pool exposes a few lines of text for debugging purposes, the PoolInfoLine1 is just populated with the current Pool URL if your node is pool mining, and the Pool Miner Guid is populated in Line2.  Note this is just technical info and you do not need to know this.  This is useful if the pool goes down and you want to know if you are pool mining or not.  We have a field called "pool mining: true/false" that sums up what the miner is doing.  If any thread is successfully pool mining, the value is true, otherwise its false.

Please hold off on mining against the main chain In pool mining mode until we fully test the client.  Mining on the main chain in the pool could result in lost BBP, as the pool will sign the block and have no idea who to pay currently (until we verify the distribution system works).  NOTE: To disable the pool settings once you are done testing on that node for the day (IE if you want to mine on the main chain outside of the pool) just put an x in front of the pool= entry in your config file and restart in prod mode.  (IE xpool=pool.biblepay.org).

To start your client in testnet mode do the following:

cd c:\program files (x86)\biblepaycore
biblepay-qt -testnet
The background should be green if in testnet.  Please do all of the testing in testnet.
Note on the above biblepay.conf configuration settings:
You will need to copy the biblepay.conf settings from the biblepay.conf file down to the \testnet3\biblepay.conf file (IE just let the coin start, it will create the file, close the wallet, open the config, copy the setting rows, paste them into the target file, restart the coin).

(I realize this is convoluted, but Biblepay/Bitcoin have the settings coalesced like this for a certain reason so its easier for us to go through the double settings now rather than change the coalesce rules.)

Note that this version of the miner updates the hashmeter more slowly to squeeze out as much performance as possible, so be patient when re-running getmininginfo, as it is delayed approximately 30 seconds before a change occurs.

Alright, good luck everyone, lets make this a great pool.

As of Aug 6th at 20:00 CST US time, the pool has not yet been deployed.  I will edit this message as soon as the website is ready for you all to create accounts.

On mac it might be in:
~/.biblepaycore

Anyway, if you do a find, try : find -f biblepay.conf

Good luck.

Project Update:

Other than the pool project, I wanted to let you all know that within 30 days, I am going to launch a professional logo design campaign on one of the design sites with a $700 reward, and we can all vote on the logo we like as a community.  This will give us a more professional website, icons, splash, in wallet background, and should increase interest in Biblepay.

After that, I have a collaborator that Ive worked with in the past, a pro wallet graphics designer, that will give us a professional facelift for the in-wallet design (this gives us a vertical toolbar, exchange and block explorer buttons, syncing spinner, etc).  Id rather have our logo finished
 first however, and have a presence on an exchange before we work this phase, but I just wanted to let you all know that the version we are running is the initial version to get started and as a community we are going to have a very professional wallet in the long run.

Guys, you dont really need all those addnodes, the wallet will find em automatically.

First just try 'node.biblepay.org' and 'biblepay.inspect.network' and then just add more if you dont sync.

Glad you are still chugging away at this.  Hey if you did get it to build, could you please tell me the two things you needed and Ill add them to the repo. 

Ive been busy working on the pool; the pool is very close but there is a socket issue in windows preventing the pool from working properly, but its working on linux.  Ill keep you all posted; its very close.

Hmm, interesting.  My nix box is tied up in a build right now, but Ill try to reproduce asap.

In the mean time the only thing I can suggest is to pull down the bitcoin latest in a separate dir and try their cross compile build and see if we are missing anything.  Most likely whatever the cause is there will fix ours.  Im doing cross compiling builds now but inside gitian.  Also if anyone else has any suggestion please offer us suggestions.

First, do you definitely have the mingw64 toolchain installed?

sudo apt-get install g++-mingw-w64-i686 mingw-w64-i686-dev g++-mingw-w64-x86-64 mingw-w64-x86-64-dev

Wow, that is a lot buddy.  I think we inadvertently created a coin that rewards for having PC hardware that can perform math functions fast.  (The future - raising the bar per se would eventually include diskindex lookups also but would not necessarily slow down these guys with fast servers and raid arrays and ramdisks etc).  

Anyway to make a comment as I have not studied the xeon yet, I am making the assumption that his speed is coming from being able to perform the AES512 encrypt and the md5 quickly in the CPU- these are math based functions.  The xeon is apparently doing this 10* faster than us in parallel, somehow.

Good luck.  These are interesting aspects.

 =-=-=-=-=-=-=-=-

On the progress of our two projects:

On the Pool:  We need a customized pool as our miner wont run outside of qt.  We are in the process of writing one.  Its now 90% complete and in pre-alpha testing.  I will start a new thread for testnet pool testing soon, and we can test this out.  I think it should be ready for testing within a couple days now- need to do a lot of calibration testing next.


On the Exchange:  I did get a-hold of ccex, and during Skype everything was positive so far, but we were cut off before we could do a build test.  Im trying to reach him again.  Hes on the other side of the world so please be patient.  If I were to guess, I would think within 7 more days we will potentially have a presence on ccex, but I cant guarantee it yet.

I believe I see whats happening here -

Weve had such a large increase in users but when a new user is just getting started, their peers.dat file is still empty, so you only know about one node.

The node.biblepay.org was exceeding its connection limit, so I just added this to the config (if we have any other external node volunteers out there):
maxconnections=300

Now I see the connections are increasing; please try again.

Try clicking on Tools | Peers and ensure you have no peers banned, reset wallet, delete banlist.dat, and ensure you are on 1017.
Your config file is good enough - and your telnet appears to be working.

Its working for over 250 people - that leads me to believe it is something on your end that is interfering with the network.

node.biblepay.org

Please check your firewall port 40000
telnet node.biblepay.org 40000

Node is already compiled in the wallet.

Yes you are correct; I am doing this for free and will risk my own capital if I want to 'speculate' on Biblepays exchange price .  Im also going to write the pool and run one of the pools for free (on a side note, running a pool will probably cost about $50 a month + code maintenance, because it appears its going to have a lot of chatter between the server and the 250 or so miners).

As far as taking the miner out of the wallet, I think its important to compensate the full nodes with the block subsidy and not become the next hardware energy wasting network- its our chance to be more efficient.  If each node costs $20 a month in electric, then the subsidies will float around $20 a month in return for running a node (in contrast to paying miners with black boxes who have no intention to run a full node).  The full node is important to broadcast blocks and keep the network running.  As far as 'its just a matter of time' before someone ports it, I think we do have the capability to restrict the miner to a full node by at the very minimum requiring it to do diskindex lookups on things from the hash function, things that cannot be ascertained by black boxes.  Over time this type of network should provide more value to each coin.