There are no viruses, nor are there any virus alerts.

Feel free to scan our software on Virustotal, which supports over 50 virus scanners and gives a true reading.



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


I am going to recommend your account be banned if you continue posting FUD here.

I actually upgraded that node node when I ran that command - but thats not the external node anymore, you must have an old IP logged.
This report only reports the last day of blocks solved by version, not the version by nodes live on the network.

There are 750 connected to the external node currently.  F7000 was in the last 4-5 versions but still it is better to be on the latest.

The "node.biblepay.org" has been moved to vultr, its been running the latest.

We pioneered a feature in biblepay called "RUN" this comes from the TRS-80 color computer run command, from the 80s, but I am thinking of changing it to Exec.

In the mean time, if you type run and then a command name, the rpc will run that block of code and respond with the JSON output.  What good is it you ask?  This is so our dev team can add reports to biblepay without writing lots of c++ code and an RPC command for every report lol.

Anyway, I see 80% have upgraded to 1029:


14:03:45

run versionreport


14:03:45

{
  "Version": "Popularity,Percent %",
  "1.0.1.9": "1; 0.49%",
  "1.0.2.2": "4; 1.95%",
  "1.0.2.3": "7; 3.41%",
  "1.0.2.4": "21; 10.24%",
  "1.0.2.5": "2; 0.98%",
  "1.0.2.6": "1; 0.49%",
  "1.0.2.7": "3; 1.46%",
  "1.0.2.8": "2; 0.98%",
  "1.0.2.9": "164; 80.00%"
}


Thats good, as we have a supermajority for F7000 in 10 blocks.

Rob

Obviously you are a naysayer, as the top 13 virus scanners show CLEAN for our 64 bit download:



Sorry, but we have organic growth here.

We wont be stopped and I have a whole belt full of bullets left.

Only 40 more blocks before F7000 hits.

Unfortunately Ill be in church when this happens.  (At least its happening during the sabbath).

I wish I could see how quickly the blocks click by and diff readjusts live, but I wont be around.  I have to rely on historical data.

If anyone wants to look at that, just start typing "showblock 7000", showblock 7001, etc.  And see how the block HR timestamp equalizes and how the difficulty level changes as we recover towards block 7015 (God willing).

Hi Slovakia,
Ive been deploying the 64 bit version to my vulture servers on 1030 without a problem using biblepay.com.  Let me know what specific problem you have with the 64 bit download?

We started a wiki page: wiki.biblepay.org.  We are still looking for a volunteer to write a hashrate comparison wiki page, let us know if there are any takers?   Right now, anyone can create a new page and the community can edit.

As far as slack, last night I started a slack team.  Next task: Invite members.  

Someone asked how Pay to Preach would work after the Sanctuaries are live.

One way to achieve this is we have anyone in our community (that feels they have an edifying testimony or sermon), to come forward and submit a proposal to preach (this is just a one page web questionnaire that sanctuaries use), submit it.  The "proposal ID" will go through the voting process.  If approved you will receive a link for a public slack room, date and time where you can come in and preach for an hour and our community can come and go - and you will be the owner of the private key of the reward.  We can probably reward more for actual video hosted rooms, but otoh, I think it would be edifying to have a lot of Christians asking questions at the end and this person running a Q&A.  (IE q&a format is also helpful).

How ironic, they are now advertising on this forum.
So obviously its not a "joke".

I think one of us should tell him he is risking hell fire.

I bet hes an atheist and doing this for profit only.

An NDE exists where a man went on a tour of hell, and Jesus showed him a pastor burning for stealing from the church kitty.  I would warn this dude that is exactly what hes doing right now.

EDIT:
Alright, I sent him a very, very bleak warning message, we will see how he takes it.

PS: I see they put the right person in charge as the "Trustee": Judas Iscariot, the one who "steals" from the money bag.

I forgot to mention this guys:

After block 7000, no changes occur in our Tithe blocks.  We still have the 1 in 10 tithe block sending 10% to the orphan foundation.

When the charity expense schedule actually changes is Two phases after the Sanctuaries go live, and then the 1st Superblock hits.

(Which is 2 phases ahead: 1 phase is sanctuary go-live, then proposals and budgeting, then the 1st superblock is scheduled, and at that moment-tithes are also stopped).  But of course, we still have a 10% budget for charity, just paid via voted superblocks instead of tithe blocks. 

You can, but I really don't want to be held responsible if a hacker breaks into the pool somehow and transfers it out, so I recommend withdrawing 80% monthly just to be safe.

Also, back up your wallet.dat file and store offsite, just in case.

If you ever go on vacation for a year, you can always recover to the top with just the old wallet.dat file.

Welcome aboard Bob!!

Well Im probably a typical miner as I have 4 machines configured and with all the programming I seldom have all 4 running but anyway, I have two 2 year old 6 core amds that hash at 85,000 per sec, and one dual proc xeon hashing at 190,000 per sec.  If they all stay on it generates about 30,000 BBP per month in the pool.  So probably about 10k BBP per month per CPU. 

Yeah, I agree, speaking of Joel Osteen, I think he made a fatal mistake by hiding when the flood hit, he should have been the first one to organize a group of minimum wage employees to get the doors open and invite everyone in even if the activities trash his church-- he shouldve filed claims later, I think his whole life calling up to this point was built up to be blessed with that big church and Be a blessing, not be a coward when people needed him.   I remember watching a video I think by Sundar Selvaraj a couple years ago, something about God
 giving the message that he will judge the megachurches, I will take them out, first Houston, then Florida then Atlanta.  I was just looking for Eddie Longs location in Atlanta, and its about 9 hours north of Miami.  However what I didnt know is Eddie died of cancer this year.  I mean no disrepect, and am saddened by that, obviously thats horrible.  But it almost feels as if this 'warning' is passing right now.

In the pool, I see the orphan bio dialog (from Orphan List | select row) opens way down below the bottom of the screen.

Fixing this right now.  I am also adding the ability to attach pictures to letters.

Yesterday, the code was completed to send the letters over to compassion and pay bounties to letter writers.

At first I thought the whole thing was an April fools joke.  I felt ill as if I wasted my time reading the whitepaper.  Especially towards the end, my thoughts were if this is real, the lead developer might be going to hell, then I thought, oh this is just a joke to see how many people go to contribute BTC on the ERC-20 page.  After reading it I see the site actually has an Ether token and a crowdsale page.  This is blasphemy.

Anyway, I almost destroyed my points but since this appears to be legit here they are:

Cons about tokenizing "Jesus":
- Using Jesus name to profit from without being actual disciples (similar to megachurch revenue but worse)
- Selling ERC-20 tokens up front as an ICO, with no promise of innovative value: IE a pump n dump scheme
- Claiming owning shares of the coin allows you to "be forgiven of sin" - blasphemy
- Not a grass roots effort - entire sham is an investor fundraiser PR event
- No propensity for any church to use the currency
- Provides no value add to the block chain, no new features
- Does absolutely no giving which is fundamental to picking up the cross
- Use case provides an example of funding a crusade and FAQ says "Not to do that" (contradicting its own use case)
- Wall Street Trader example - this did it for me - You are known by your fruits

They are not even a mosquito on our back.

Thanks for posting; I will read the whitepaper.

The risk is we go under at block 7000 because our big algorithm change.

Once that block comes to pass, then give it a few days to 'burn in' and let us reindex the chain, etc, send money back and forth, testing it in prod, and at that point it might be considered relatively safe.  We are starting at the absolute bottom of the barrel, so we cant go much lower.

I added a Bible Pay wikipedia service last night.  We can use this for one when we start churning out sanctuary documentation.
IE: How to create a sanctuary, run one, troubleshooting, Proposals, Voting, etc.

For now we have one page, if anyone wants to edit the main page and make it nicer, go for it.  I enabled inline images.

http://wiki.biblepay.org/

Plus, non-Christians are welcome to use it.  All of the greed based money will flow in if we ever increase by 500%.

I think once we have our core established, we can work on A) Making a liquid debit card for POS purchases, and B) floating this as an alternative investment for 401Ks.

**************** POOL PASSWORDS ******************

Regarding Password problems at the pool:
1) One problem was passwords cannot have certain special characters that blow out the cipherclass.  This has now been fixed.
2) If your password does not work, click Reset Password and follow the wizard.
3) If your e-mail is not working, send an e-mail to contact@biblepay.org to have the password temporarily reset.

Rob

Starting at Christmas, the charitable allocations change, and then the way it works with sanctuaries is:

15% total will be held back per block (this breaks down to 10% for charity and 5% for IT), and the tithe_blocks will be changed back to normal blocks with 0% going to charity.  The 15% can be spent any way the sanctuaries wish- as long as the IT expenses come out of the 5% and the charitable out of the 10% limits.  (Yes, the blocks do pay 10% back to the sanctuaries for being sanctuaries, and 75% to the miner).  So right now its: 90% to the miner, 10% to charity.  In the future: 10% to sanctuaries, 15% to charity and IT, and 75% to the miner.


Last night, I was doing some R&D work for biblepay, regarding instantiation of a new governance vote proposal for a new sanctuary.  I believe all the problems are solved, regarding the worries about people running away with money, and whose performing duties, and the multisig, and IT support for the duties etc.  As a sneak preview of how this will be tackled, any recurring expense, such as the orphan foundation premiums owed, will have to be re-entered once per quarter as a new Proposal.  So if we have 100 orphans being sponsored at $3800 per month, we will enter a proposal to pay the premiums for these orphans for up to 3 months at a time.  Once the proposal is approved (for $3800x3) by the sanctuaries, this becomes a budget item.  A budget item has a brand new wallet receiving address, and a designated person in charge of the duty to transfer the premiums to compassion.com.  The sanctuaries will approve the budgets or deny them by voting on them, and the escrow is auto-released in our superblocks on the superblock date of the month.  I can even put someone in charge of the compassion post at that point.  IT (Information Technology) will be responsible to set up the necessary support functions for orphans at "biblepay central".  Which is currently the pool.biblepay.org.  But as we develop our slack team, we can then break out subdomains for the orphans, so people can manage the  orphan letters at orphan.biblepay.org, etc.  I think the concept is now forming as a set of viable requirements at this point.  Im starting to merge the sanctuary code into testnet now.  We will have crude IT support available for the future of these functions in testnet in a month or so, and test all this together.  Im excited.