Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Rob Andrews

Pages: [1] 2 3 4 5 6 7 8 ... 127
1
I was using 1429 because I didn't know that there is new version. I didn't found any mention about new version here ;)
Now I have 1431 and here are my answers:
A) Yes, I agree 1.4.3.1 has no extra boxes in the About page
B) I've got a message from my antivirus (Avast) that the file is clear and it's working good now
C) That debug.log is still there. BUT  this debug.log is not in %appdata%. It's in install DOC folder. Here is a screenshot: https://prnt.sc/nrhg7t This file is from end of the March and here is the beginning of that file:
Code: [Select]
2019-03-29 16:54:05 BiblePay Core version 1.4.0.5
2019-03-29 16:54:05 InitParameterInteraction: parameter interaction: -externalip set -> setting -discover=0
2019-03-29 16:54:05 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-03-29 16:54:05 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-03-29 16:54:05 GUI: QCssParser::parseHexColor: Unknown color name '#yellow'
2019-03-29 16:54:05 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-03-29 16:54:05 ***************************************** BIBLEPAY  ***************************************************
2019-03-29 16:54:05 ProdMode: Prod 0.000000BiblePayVersion 1.4.0.5 (BiblePay Core)

It's nice that the BiblepayEvo insttall file is on main page. But I have question for Ubuntu packages. Will they be ready on Evo start? Will be there any changes in repository or the ppa:biblepay-official/mainnet remains the same? Because I'm using packages for my VPS and it wouldn't be fair to be in a disadvantage :)

And I have another wish :) It would be nice to have smart contract reward txs on wallet main page Recent transactions list, because now they are only in tx page.

Hi Orbis,

Yes, your right, I forgot to tell everyone to test 1.4.3.1, good point.  The only new feature we didnt test here was 'leaderboard'.  1.4.3.1 will also show your individual diary entries (or all diary entries).

So yes - I found that log, good find.  It will be removed in 1.4.3.2.

On that GSC rewards being enabled to be on the overview page Recent, could you please add a github issue to the new evolution branch? 

So on our RPM releases, good news and bad news.  So MIP makes the RPMs normally, but we have an issue- one of the third party components in dash-evo will not build in an RPM (its an upstream problem actually).  So here is our plan:  We will compile and release MacOSX, Win64, Win32, Ubuntu16, and Ubuntu18 binaries and deploy all of them to the web site.  So the main thing we are missing is the ability to use a PPA on linux.  We expect to have this resolved within 90 days however but its a complicated problem and MIP is actively researching it. 

Ill post when I have some more builds ready so we can verify the debug is gone.


2
Hi,
after few days I'm back and I'm testing 64bit WIN version.
It's working good, but I've had problems with install.
My antivirus report it as Dyna:BitcoinMiner-CR [PUP]||mul and moved it to Virus vault.
But after set it as "trusted" it works good, mining and GSC is working good.

And maybe I found some bug.
There are Book and Chapter option in "About Biblepay Core" window, but they aren't working.
I cannot choose anything from it and it's empty.

And Rob you still didn't remove those old March debug.log from WIN install file and it's still more than 60MB big :)

A) Testing the latest version, I click Bible | Read Bible, click a book and chapter and I see the contents, so I do not see a bug here.  Please be sure you are testing 1.4.3.1.  EDIT: 1.4.3.1 has no extra boxes in the About page - please re-test.

B)  Antivirus:  This is common with cryptos that have miners - the algorithm makes a false positive for that section, however the scan will eventually return negative once we have more than 100 downloads, so this should be solved (just like our prior versions of biblepaycore.exe).

C) On the log, I don't believe we copy the installer contents to %appdata%, are you sure this debug.log is not your log, could you please delete it and reinstall our EXE and see if we write it again?  If we do, Ill do a more in-depth search to see how we could have left that in our build process - Im 50-50 on this, could you help us by checking?  EDIT:  Please be sure this installer is the 1.4.3.1 installer.  I cleaned up the build directory before building 1.4.3.1. 
    EDIT:  I just tested 1.4.3.1 windows install - we don't write the debug.log to the %appdata% directory - please test again.


EDIT:  One thing I didn't explain, I've been deploying the 1.4.3.0+ versions to:
https://www.biblepay.org | See the top level Downloads Menu | Evolution downloads

This might be the problem.





3
Production Proposals / May compassion recurring sponsorships 2019
« on: May 20, 2019, 01:06:40 pm »
We currently sponsor 55 @ $2090 per month.

Requesting 3.25MM.


4
Thank you for your acknowledgement! Glad to be part of this project and the community of believers in Jesus and hence happy to help in this small way!

The UI is great and, as far as I can tell, installs and runs on Windows 10 64-bit (I needed to addnode my own classic sancs for it to find the block source) and it took quite a while to load from scratch. I have currently got it mining on the pool
http://www.purepool.org/main/miner/BFwWN5ohJLcUAn1H9urqUqaA9oqPUBJtbh/

The first one (1.4.2.8 EVO on mainnet compiled in Ubuntu 18.04) is still crunching
http://www.purepool.org/main/miner/BD9gmJ5vmPJtDewo9NyqUT7fJQgV39AW7R/

There appears some typos under "JESUS' CONCISE COMMANDMENTS"
Pure and undefiled religion before our God and Father is to care for orphans and widows in their distress, and to keep oneself from being polluted by the world. (John 1:27) - ref is actually James 1:27

Do not Store up Treasures on Earth where moth and rust destroy, and where thieves break in and steal, but Store up treasures in heaven, For where your treasure is, there your heart will be also. (ref is missing - Matt 6:19,20a,21)

The "Help - About Biblepay" Tab has some unnecessary boxes at the bottom of the screen.

Ok, I fixed the bad bible reference and added the other reference.  Good find on the About page, that was pretty ugly.  Fixed.
These changes will be in the next release (probably tomorrows release).



Good point on setting up the POG & Healing campaigns in prod; I will set those up ASAP and we can at least join and see if they appear to be initialized.  We cant really test more on that yet until the GSC height passes (123,200) and we have some 4.5MM sancs running in prod (more than the min_quorum of 10 set up).


5
Loading from scratch, and seed node not found in prod-evo.


So I thought I would address these two issues separately:

1.  The loading from scratch is a little slow right now, but Evos block loader is different than classic.  Note that once the supermajority is on evo, Evo will actually transmit compact blocks (compressed) using more than one thread, so that should speed up the time for people syncing from zero at that time.

2.  Regarding being unable to find the seed node, I confirm that due to my current Evo expirimentation being on dns1-dns3, Ive caused most of the prod evo seed nodes to be down - it should not be affecting biblepay-classic however because we have more in classic.  Im currently fixing the problem, once we have those 3 up again this will be mitigaged - note that as long as an Evo node can find 1 node, it will immediately pull in the other "friends" and start syncing, so Im sure this will be resolved also.

3.  In the near future, probably around Thanksgiving, we can also create snapshots.  This will allow someone to sync in about 5 mins using a zip file and a couple clicks to get it bootstrapped (we might need a button in the wallet to make it easy to download the snapshot).


6
************************************************************************

                      THANK YOU ALL FOR TESTING BIBLEPAY - EVOLUTION

************************************************************************


Let us pray this version is the most stable and beneficial version for our Orphans and God's Kingdom.


Testing is not completely over, but I wanted to send a warm thank you to everyone who contributed in any way in this TestNet thread!



God Bless you All!


7
Thank you for your acknowledgement! Glad to be part of this project and the community of believers in Jesus and hence happy to help in this small way!

The UI is great and, as far as I can tell, installs and runs on Windows 10 64-bit (I needed to addnode my own classic sancs for it to find the block source) and it took quite a while to load from scratch. I have currently got it mining on the pool
http://www.purepool.org/main/miner/BFwWN5ohJLcUAn1H9urqUqaA9oqPUBJtbh/

The first one (1.4.2.8 EVO on mainnet compiled in Ubuntu 18.04) is still crunching
http://www.purepool.org/main/miner/BD9gmJ5vmPJtDewo9NyqUT7fJQgV39AW7R/

There appears some typos under "JESUS' CONCISE COMMANDMENTS"
Pure and undefiled religion before our God and Father is to care for orphans and widows in their distress, and to keep oneself from being polluted by the world. (John 1:27) - ref is actually James 1:27

Do not Store up Treasures on Earth where moth and rust destroy, and where thieves break in and steal, but Store up treasures in heaven, For where your treasure is, there your heart will be also. (ref is missing - Matt 6:19,20a,21)

The "Help - About Biblepay" Tab has some unnecessary boxes at the bottom of the screen.
Wow, well thank you very much kind sir!  I'm also impressed that you have created your own domain with notes.
Do I know you from anywhere or did you just recently find BiblePay?

Thats great the build is working on Win10; thanks goes to Dash for ensuring the base is cross-windows compatible (I mean registry and c++ pinvoke calls etc).

Thats awesome the two miners are still working, I did look at your first miner a couple times and that was very valuable for us.

Ok, let me fix these typos right now.  Good catch on the John 1:27, interesting.

I'll look at the unecessary boxes now also.

Thanks a lot for all your help btw, it was instrumental in creating a quality product!


8
I'm running 1.4.2.9-Evo on pool.biblepay.org now.

I PM'ed Licht with the problems and change requests.

Note that I will revert Pool.biblepay back to Classic tomorrow as Evo governance is not compatible with classic governance (IE we need to finish this governance cycle and rely on the pool to see votes and proposals, etc).


9
The 64-bit version seems to be running fine on my end thus far :)

Thanks, I appreciate it!

Yea I'm testing it now on the pool server and it looks like we do need a couple more classic functions that I thought we could retire to be added to Evo.  They will be out in a couple hours for the pools to continue testing (but these do not need to be tested by users or sancs).


10
We are now in the final phases of testing.

I think at this time it would be prudent for us to do a dry run - testing the things that will happen soon in prod.

For one I am writing the scripts to build the 32 & 64 bit version for windows and deploy to our website for download.

So far we have been running the 32bit windows version.  Ill build a 64 bit version now, and post the link and lets ensure this 64bit runs on our windows machines against prod.

Oncoapp and I already tested both pool mining pools and HTTPS communication.

I suppose I can be the guinea pig to test a couple Production sancs (using 4.5MM each).
Im currently deleting all the files on a couple VMs readying these VMs for Evo, once this is ready, Ill take the plunge and set up an Evo sanc in prod (in non deterministic mode, btw).

NOTE:  It is very important we make it clear that we Do Not want any sancs in Prod to upgrade to Evo until the announcement and cutover height is posted, as I want our monthly superblock to pay out properly  ;).

MIP, do you think we will have a Mac build available by June 2nd?  It would be nice to give them an upgrade path.

Ive already confirmed with GIN that they are ready to upgrade to Evo.

EDIT:

Ok, if anyone wants to test the 64 bit build on windows:
https://biblepay.org/biblepayevo64.exe


11
Production Proposals / Re: Restarting BLOOM Sponsorships - Uganda
« on: May 17, 2019, 01:46:28 pm »
My opinion is that the funding originally ran out at the end of 2018 because we shrank to such a small level at that time - with that new size  (as of Jan 1 2019) we probably would have proposed to scale down to 4.  But since then we have decreased in price even more (and we are currently sponsoring those 4:  Favor, Praise, Isaac and Musigale) for 3 months currently (we are prepaid with Sarah).

Imho, I think we could talk about renewing the same 4 (or maybe 2) of the kids we currently sponsor with SXS in July when they expire (through BLOOM), or asking BLOOM if you have any cheaper programs that we can afford (IE without boarding).

Also I would like to ensure that we have the names of the children being proposed in any proposal here, and the URL links to their bio's so we can be in compliance with the BiblePay system. 




12
Production Proposals / May payroll (Jan)
« on: May 17, 2019, 01:38:14 pm »
1.1.8.5-Mandatory Upgrade 

@biblepay
biblepay committed on Jan 27
 5   
Commits on Jan 23, 2019
1.1.8.4b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 23
 
1.1.8.4-Leisure Upgrade 

@biblepay
biblepay committed on Jan 23
 
Commits on Jan 21, 2019
1.1.8.3b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 21
 
1.1.8.3-Leisure Upgrade 

@biblepay
biblepay committed on Jan 21
 
Commits on Jan 14, 2019
1.1.8.2-Leisure Upgrade 

@biblepay
biblepay committed on Jan 14
 
1.1.8.1c-Leisure Upgrade 

@biblepay
biblepay committed on Jan 14
 
Commits on Jan 13, 2019
1.1.8.1b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 13
 
1.1.8.1-Leisure Upgrade 

@biblepay
biblepay committed on Jan 13
 
Commits on Jan 12, 2019
1.1.8.0b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 12
 
1.1.8.0-Leisure Upgrade 

@biblepay
biblepay committed on Jan 12
 
Commits on Jan 7, 2019
1.1.7.9b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 7
 
Commits on Jan 6, 2019
1.1.7.9-Leisure Upgrade 

@biblepay
biblepay committed on Jan 6
 
Commits on Jan 4, 2019
1.1.7.8q-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8p-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8o-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8n-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4

1.1.7.8m-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8l-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8k-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8j-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8i-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
Commits on Jan 3, 2019
1.1.7.8h-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8g-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8f-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8e-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8d-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8c-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8b - Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
Commits on Jan 2, 2019
1.1.7.7c-Leisure Upgrade 

@biblepay
biblepay committed on Jan 2
 
1.1.7.7b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 2
 
Merge branch 'master' of https://github.com/biblepay/biblepay

@biblepay
biblepay committed on Jan 2
 
1.1.7.7 - Leisure Upgrade 

@biblepay
biblepay committed on Jan 2
 
Merge pull request #63 from biblepay/develop 

@biblepay
biblepay committed on Jan 2
 
Merge branch 'master' into develop

@biblepay
biblepay committed on Jan 2
 
Commits on Jan 1, 2019
Added further error handling to Win ShellCommand in case boinccmd fails




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


140 hours
Capping at 3,000,000


13
Production Proposals / CAMEROON ONE May 2019
« on: May 17, 2019, 01:31:25 pm »
We have 11 children with cameroon one, we have donated $893 in 2019, and our annual due is $4026.00.

Requesting 5 million to shore up the deficit.


14
Production Proposals / Whale Revival
« on: May 15, 2019, 07:40:09 pm »
I'm considering the idea of starting an Orphan Whale Fundraiser.  I'm doing this partially because I feel we as a society are entering into the end times (Matthew 6:19, do not store treasures on earth but in heaven), (Rev 3:17 Hoarding in the last days), 1 Timothy 6:17 (do good with your blessings), and therefore I feel as if I should give back my retirement account back to the orphans (or to other good causes).

Obviously, this could be done as an individual alone, but I think that if we have a chance to design this fundraiser to 'increase the impact of the deal' where it makes a positive impact for BiblePay, and also for the giver then it is better to do this as a team for biblepay than alone.

Also, I have been reaching out to two of our vendors who offer Orphan early-termination insurance, meaning that they both guarantee the orphan will not be dropped from the benefits program if we pick them up and drop them (they will be subsidized by the insurance they carry or moved to another beneficiary).  Both Compassion.com and CAMEROON ONE offer this.

As far as a personal tax deduction, I believe it will be possible to receive the deduction if you give to Cameroon One.  As they will allow the check to be sent to them, and the orphan to be in the BiblePay account.  Compassion on the other hand does not accept checks from third parties therefore the tax deduction is not possible with them.

So here is what I am thinking as a rough idea:

I ask the community for an idea of how many orphans our whales are willing to sponsor each.
I agree to match an equal amount of BBP/USD to sponsor an equal amount of orphans (IE I match the whales commitments).
BiblePay sponsors an equal amount of orphans out of that monthly superblock also.

We then increase our orphan count by 1/6th of that number (IE we adhere to our 6 month buffer).  After BiblePay can no longer afford to pay, we scale back.

So an example looks like this:

Whales 1-5 decide to sponsor 40 orphans ($1600).
Rob matches this number (40) @ $1600.
The money raised goes directly to Cameroon One and Compassion (and those that pay cameroon one receive a tax deduction receipt).
We enter a proposal for BiblePay for $1600 that month also (benefiting 40 orphans).

With this combined action, we receive total funds to sponsor 120 children / 6 months  = 20 new orphans.
That same month, we sponsor N from Cameroon and Y from Compassion (depending on how many went with Cameroon).

BiblePay assumes liability for the children at that point going forward.

Note that the whales do not receive anything back for this (except a tax deduction) and a positive experience as a cheerful giver.


Thoughts?

Also would anyone be up for this?







15
Sanctuary Discussions / Bug Bounty Program
« on: May 11, 2019, 03:33:34 pm »
If anyone finds a critical security bug in BiblePay, please start by announcing it here.

We will work with you and reward up to 2 million BBP for the bug, depending on its systemic nature.


Pages: [1] 2 3 4 5 6 7 8 ... 127