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 ... 7 8 9 10 11 12 13 [14] 15 16 17 18 19
Ok, I think I finished polishing, development is finished.

I sent the update to Lichtsucher so he can do a final test of the last version on his environment.

As soon as this is published in biblepay-central explorer, I will release the Android mobile app in Google Play.

Great job!  Im glad you got the API path to expose the UTXOs, and figured out a way to persist the UTXO value in the database!

Im sure Lich will be happy to resync his chain!


It's better to give it a good try first on a test environment, I want to be sure that this add-on is not impacting on the performance (it should not). However it will eat some storage, for example addresses collection takes about 180MB now and processing time for each transaction is slower than before.

I also found some glitches in PoDC staking addresses, as some UTXOs are not properly removed from the database array.
But we are quite close.

Archived Proposals / Re: BiblePay mobile wallet (Android & iOS)
« on: April 14, 2018, 01:56:53 PM »
About the iOS wallet, I had 2 possibilities:

- Use the same BRCore SPV client as in Android. This would mean "upgrading" all the iOS development to use this version.
- Use the last iOS version that compiles for me (build 156 from Nov 2017) and then adapt the older BRCore  version back to connect BiblePay network.

As I am more a "orange belt" in iOS development, and "black belt" in C/C++, I went with the second option.

First transaction sent from iOS!

I loaded the same wallet as the android app, so in fact you can see my other test transactions made in the last days from the Android device.

Here is the import transaction we made yesterday from a paper wallet in Android, as seen in the iPhone

UI is not the "cutting-edge" version.., but feature-wise it's exactly the same app we have in Android.

Now I will proceed to change colors, icons, strings, etc.

TestNet Discussion Archive / Re: Android mobile wallet - TEST
« on: April 14, 2018, 06:27:36 AM »
I've downloaded latest version and I have still there "Bitcoin Nodes" in advanced settings, but after clicking on that there is "Biblepay Nodes".
So I don't know if it is still bug, or I have bad version.

The version you have is fine for testing. The version with the label fix is still in develepment, I will wait until the paper wallet sweep is ready to publish a new one.

TestNet Discussion Archive / Re: Android mobile wallet - TEST
« on: April 13, 2018, 03:40:54 PM »
There is still old version (211) on your link.
And what about importing? How it looks?
Do you have any schedule for it? :)
After that it will be easy to make promo for Biblepay.
Print paper wallets with QRs and on the other side with QR code to Google play store :)
And then just fill with some coins and make giveaway on street or front of the church :)

I have to debug some problem with utxo maintenance in explorer code, that affects PoS transactions, and then some more tests with Lichtsucher. Then it will be a matter of hours to publish it.

Nevermind the 211 version, just take the one in the link, it's the last one.

TestNet Discussion Archive / Re: Android mobile wallet - TEST
« on: April 13, 2018, 09:34:51 AM »
A minor thing I noticed:

In the 'advanced settings' tab, the nodes are called 'Bitcoin Nodes' instead of 'BiblePay Nodes'.  If you click on it, it will display 'BiblePay-nodes'.

Noted and fixed in dev

Archived Proposals / Re: BiblePay mobile wallet (Android & iOS)
« on: April 13, 2018, 09:07:40 AM »
Say hello to the first transaction made by our BiblePay Android Wallet app, sweeping funds from a paper wallet QR private key.

Utxo info has been taken from my local block explorer webserver with the Iquidus upgrade patch.

Almost there!


I just wanted to say that you are doing a fantastic job. I will be voting for your proposals.
Also, I am not sure if others are like me, but I usually wait intil the last week before the superblock to vote, just so that I get a good idea of what is in the budget.


I agree, voting the last week should be the right approach, as several proposals could be competing for the same resources, and votes should work as a way to prioritize the most critical projects.

In this particular month, I think the only IT proposals are mine but there could be a month where this is not the case.

Archived Proposals / Re: Proposal idea: airdrop
« on: April 13, 2018, 02:18:25 AM »
This is very interesting, because even if we reach only a low % of  the total audience, that will be still a lot of new people interested in this project.

Proposal created. Kindly consider to vote for this proposal, included in this month IT budget, if you find it interesting:

gobject vote-many 03aa25b80bf951bcaaed1589a52c8cd8cf58893912df176c2b4bafef47d90296 funding yes

Thenk you

Plan B seemed to work. It's about maintaining a clear list of the address UTXOs.

It takes a bit more database space and longer to index (about twice the time) but the good point is that calling the getutxo API is 5 times faster than the other way. I don't expect the other queries to be affected.

As soon as I can contact Lichtsucher we will try to test it on a test environment.

Ok I tried to add outpoint info in inputs so with a simple query you could know if it's unspent or not.

However, there was a trap:  Iquidus explorer iterates through all transaction inputs, but doesn't record all of them, it creates only one per address and then accumulates the amounts over the same "virtual" input.  This is logical as it is what we expect to see in the user interface.

So my initial approach can't work.

My "plan B" approach is, when processing inputs, trying to recover back the original output  and "mark" it as spent, then save again.  It way harder to implement, but probably the only way to go without changing the database model drastically.


We need Iquidus explorer to support GETUTXO in its API.

It's required to support the paper wallet sweep in mobile versions. I expected Breadwallet to support this via some SPV functionality but it was not the case.


- Starting from current Iquidus Explorer master version, implement GETUTXO in explorer API{address}

Output format will be recognized by Biblepay mobile wallet.
(see sample in


- Fork Iquidus explorer project, install biblepaycore, install explorer on a dev ubuntu computer (2h)
- Change database load to store outpoint hash and index in transaction inputs (2h)
- Implement check_is_unspent as a query to know if an output has already been used (1h)
- Implement API route /ext/getutxos (2h)
- Explorer full load tests (2h)

Total Budget:
9h dev&test @40/h = 360
= 0,064285 BTC (@ 5600) = 173745 BBP (@37 sat)

Work is very advanced, and it works pretty fast. It will be a nice addition that few coin explorers have.

All code will be open sourced.

I will need Lichtsucher's help to update biblepay-central explorer. I don't know if you have a test environment before we go live.
A full reindex of the database will be required so expect a few hours downtime.

Archived Proposals / Re: BiblePay mobile wallet (Android & iOS)
« on: April 10, 2018, 12:32:54 PM »
MIP you are awesome for jumping on this!

Is the code open source?

Sure. But at the moment it's on dev branch. As soon as we go real I'll push it to master and probably we'll move it to biblepay github repository.

Archived Proposals / Re: BiblePay mobile wallet (Android & iOS)
« on: April 10, 2018, 10:12:17 AM »
Some quick updates:

I can't contact with Breadwallet devs asking about iOS repository updates. I'll wait a few days more.

Regarding Iquidus explorer, I will have to tweak the original node.js code so the transaction inputs can include the OutPoint info, which is required to implement a getUtxos API.
Of course after this update the explorer database will have to be rebuilt from scratch but well,.. that's progress.  8)

Pages: 1 ... 7 8 9 10 11 12 13 [14] 15 16 17 18 19