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 - MIP

Pages: 1 ... 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17
Archived Proposals / Re: MacOS compiles - iOS version support machine
« on: June 04, 2018, 03:59:52 AM »
Ok a quick summary on the MacOS compile efforts

I could compile with the latest QT version, adding c++11 flags to the compiler and some tweaks on Txmempool source because of some obscure C++ quircks in boost 1.66+. The GUI-less daemon works wonderfully, but the biblepay-qt GUI crashes.

When debugging I saw it crashed at kjv.cpp when creating this huge b[31102] array with Bible's verses, at index 1223 .
I tried to change the static allocation with a unordered_map structure, hoping that C++ magic would come to the rescue. Little progress, it just crashed at verse 9010.

I found this guy from Norway at Discord that told me he had compiled and run the QT version without issues. The funny thing is that he had made exactly the same tweaks and flags I made, and he has the same OS version. The only difference is that he's using the GNU toolchain and I have the XCode toolchain, which could also be the same thing by just using a symlink.

I suspect of some compiling options so now I'm reviewing and comparing all the environment, versions, etc. one by one which looks like a lot of pain ahead :-D

EDIT: I saw that in MacOS the default stack size is 8MB. That would explain something. After increasing the stack size it still crashes, but it processes more verses. In fact if I comment the last 14000 verses application loads fine (but it's unable to load chain because of the failing PoW checks...). I'll keep on researching.

TestNet Discussion Archive / Re: iOS MOBILE WALLET - BETA TESTING
« on: June 04, 2018, 01:47:56 AM »
I'm getting comments that crypto wallets are not passing thru apple approval process unless the currency is "approved" by them. Nobody knows what this is but it seems that we have been lucky to even pass to beta stage.

I will call apple support to know more about this because before I started with this development I raised a ticket to them and they told me there would be no problem. But I don't want to be rejected in the latest step after all the hours we have invested on this.

I'll keep you posted.

EDIT: it seems they send you a standard questionnaire with some questions about the coin and the project. How the evaluate it and consider a coin is "approved" is a mistery.

I would need to know about your feedback so we can start this review process as soon as possible.

TestNet Discussion Archive / Re: iOS MOBILE WALLET - BETA TESTING
« on: June 01, 2018, 02:37:01 AM »
Sweet!  This is fabulous!

Ok, I'm running the iOS version in TestFlight.

So far so good.

I just recevied 111 bbp.

I will send it back to myself now.

The only enhancement I see so far is in Security Center, there are two references to "BRD" that I believe should be changed to "BBP".

Thanks dude.

In my spanish version I can't see those references to Bread. Could you please post a screenshot? Sometimes they are strings, sometimes icon resources... it's hard to find without a visual aid.

Thank you!

EDIT: I found it! fixing...

TestNet Discussion Archive / iOS MOBILE WALLET - BETA TESTING
« on: May 30, 2018, 09:53:44 AM »

This version is functionally the same as Android one so it will be easy to test.

It's currently under review so meanwhile I'll start gathering the brave ones that will want to do the TestFlight.

I need  email+name+second name in order to register you for beta.

When the build is approved by apple you will see a notification email with the invite for test.


Here some eye candy taken from my iPhone 8

I just leave a quick note to say that my windows wallet has stopped to send automatic PoDC updates a few days ago. I tried to restart and all that but to no avail.
Currently I'm doing it manually every 12h to keep on staking. I don't know where to start checking but when I have a bit more time I΄ll check the logs in case I see something evident.

Archived Proposals / Re: BiblePay mobile wallet (Android & iOS)
« on: May 12, 2018, 03:28:38 AM »

- I noticed wallet shows $0.00 per BBP, but does give me a correct dollar value for my total BBP coins

This is because I left 2 decimal places in some screens, but a single BBP is under $0,01 at the moment. That's why I left 4 decimal places on the total wallet. I'll take a look

- I noticed wallet shows Ƀ symbol in front of amount of BBP coins

Yeah I left this as it is, because of the "B" in Biblepay. The original code expects a one letter symbol, so until we find ours we can borrow it from Bitcoin (a bit pretentious I know)

Let me know if there is anything else I can do to help!

Thank you for your feedback and support!

I don't know how others feel, but I get confused by the amounts because net amounts are not shown. PODC updates especially showing spend very little, but sometimes take big starting amounts and end with big amounts. I think visually the QT does it right by showing the net amount. I think explorer should work the same way. Details should show gross amounts being moved around. I know this isn't exactly what the upgrade is to support, but if it is easy enough to add, I'm in support of it. It would add consistently to UX/UI between QT wallet and Explorer. btw, the green color for receiving and red for sending is a good visual hint that I enjoy.

QT wallet does it right because it knows that the change address is also yours. But Iquidus doesn't know. So that's basically why can't it make it work the same way.

We have waited until now, and after c-cex reopening we are not in such a hurry fortunately.

Where does Rob live? Our work has computer sales and have off-lease business Macs for sale sometimes. I'm in California. Shipping would be expensive for a desktop... I think mac Mini is likely the least expensive way to go, or a mac desktop if you wanted something a little more powerful. macbook pro/air is okay, but they are a premium cost wise.

compiling on freebsd macos is challenge every time.

In my case I'm from Spain. Ironically I got a good deal for a MacAir but it's coming from Los Angeles... It will take a while though.

Thanks for you offer anyway

Archived Proposals / Re: Compensation for Jaap's work with BiblePay
« on: May 08, 2018, 08:30:29 AM »
I think it's a good idea that one gets compensation for the efforts, and in your case they have been outstanding.

Not an exchange but do you want me to request for listing in

It’s a nice MN follow service. It’s pretty cool to control MN from several coins at the same time.

Archived Proposals / Re: BiblePay mobile wallet (Android & iOS)
« on: May 03, 2018, 04:49:49 AM »
LoL, I just finished the iOS version with the older interface and libs... and then the Bread developers push all the changes since January into the repo.

Good move, Mr. Murphy.  :o

Anyway I cannot test this latest version with the Mac VM because it depends on go-eth (the SPV client for Ethereum) and I cannot install this dependency in the VM, so we will stick to the original plan and launch the version we have, and then revamp it when we have the real Mac machine.

If all the chainparameter layers have been properly isolated, I could even make the wallet app BTC/BCH/ETH compatible (along with BBP) but I cannot make any promises until I see the code.

Edit: nope, they didn't isolate all chainparams properly so it would be a BBP+ETH wallet, at the most   :(

Archived Proposals / MacOS compiles - iOS version support machine
« on: May 03, 2018, 03:22:15 AM »
We had some pending topics that converged at the same point: the lack of a platform and dev license for MacOS and iOS compiles.

I sort of made the iOS version (development is practically over) with a rented VM at MacinCloud, but I had almost constant hang-ups and connection cuts. It has been a real pain.

The problem with this VM (apart the mentioned usability ones) is that you can't install any special packages or SDKs out of the "regular" ones. This invalidates the VM for permanent compile platform and also for a long-term maintenance tool for the iOS version.

Also, I could not test the phone's camera and QR scanning on the XCode simulator for obvious reasons.

As a result, I proposed Rob to purchase a second hand Mac to overcome all this limitations and start working on MacOS compiles and better iOS version maintenance.


- Purchase a 2nd hand Mac with at least i5 proc and 8GB
- Install development license
- Prepare MacOS signed builds.
- Test iOS with real hardware and then launch beta version.


- 2nd hand Mac (770€)
- Developer license for 1 year: (99€) --> already budgeted in Mobile app proposal = 0€
- Prepare and support MacOS builds: voluntary = 0€
- Test and launch iOS app: already budgeted, 0€

After 1 year, only new Apple developer licenses renewal (99€) would be proposed.

770€ (BTC @ 7700€) = 0,1 BTC (BBP @ 37sat) = 270270 BBP

I had thought to distribute this in a year's amortization, but I would require to create a proposal each month, and actually, after all the expenses I have for my daughter's knee problem, it would be a financial effort I can't assume.

Of course any other use for this Mac that you think we can implement to support Biblepay would be welcomed.

Proposal has been added to gobernance. Kindly consider your masternode vote. If possitive:

Code: [Select]
gobject vote-many 3a89aed047f627edee22853b8a7b3b3fbb5b6298d42ff78a495c4e38c0107fff funding yes
Thank you!

It seems that is still catching up (now it's on 29th April). In my pitiful PC it took far less time, but it's true that if mongodb can use only 1 cpu at a time, it could be an explanation.

The queries run fast, at the cost of a slower indexing, as forecasted.

From my side, work on this proposal is over.

TestNet Discussion Archive / Re: Android mobile wallet - TEST
« on: April 26, 2018, 03:09:42 PM »
Great job on the app, MIP! I have a suggestion.

Would the app work with a lower minSdkVersion? I'm worried that Android 6.0+ is probably not what most of the unbanked population have on their phone.

Furthermore, according to , Google recommends as a good practice to support about 90% of the active devices, while targeting your app to the latest version (targetSdkVersion).

Here is a nice pie chart of the version distribution:

So 90%+ would include 4.4, but I know that's a drastic difference in OS, so if the app doesn't work on 4.4, maybe you could at least include 5.0-5.1, since the OS is basically the same as 6.0, so the app should work, and that would increase the app penetration by a whole 23%, which is around 500 million users more. :) And probably a lot of the unbanked would be in that 500 mil.

This was commented and explained before. Android under version 6 lacks the security measures to protect the wallet keys against a theft or root attack, because it has no built in  encrypted storage.

And i fully agree with them. Why create an unsafe wallet thar can be tampered easily and you can lose thousands? I don't want to be responsible, even morally, of that.

Let's hope Androids under version 6 get outdated soon as tech advances and become more affordable.

Pages: 1 ... 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17