With a week of delay (I wanted to do this one week ago, but I couldn’t) I’ve just released 0.1.0.
A quite big release and IMHO stable:
https://git.duniter.org/vjrj/ginkgo/uploads/39e870ac1dc42548abb2b21dbacfd3f2/ginkgo-0.1.0.apk
Thanks/merci and sorry for the spam.
Nice! We now have to complete the translations on https://weblate.duniter.org/ ^^
Do you think it is ready to communicate a bit about it? (for example a video explaining Duniter 1.9 GVA, Durt, and the state of Ğ1nkgo)
Thanks a lot for your work, that’s impressive to see someone so new in the Ğ1 and already spending so much time on a brand new app! I hope we can find more people like you to release a v2 ready for migration 
J’attend avec impatience l’affichage en DUğ1.
Le DUğ1 est l’unité avec une propriété d’invariance temporelle.
À terme, le DUğ1 représentera toujours la même portion de la masse monétaire par membre. Ce qui en fait l’unité d’affichage idéale.
Est-ce que cet affichage sera bientôt possible ?
I look forward to the display in DUğ1.
The DUğ1 is the unit with a time invariant property.
Eventually, the DUğ1 will always represent the same portion of the money supply per member. This makes it the ideal display unit.
Will this display be possible soon?
I think so. For me the main issue is the gva cors issue, but I cannot do nothing currently.
Thanks to all of you for building this project and this community. I was looking for something like this for years. Just trying to help a bit.
I’ll start this if you finish the French translation. Deal? Seriosly, I was trying to publish something stable, and it was not a good moment to add this. But I will.
Done 
When you can
could you explain this issue ?
that’s maybe why I cannot request my node on http://127.0.0.1:30901/gva
Merci @Maaltir and @HugoTrentesaux for the translations. I’ve just released a maintenance version that includes your work (more to come after some rest):
https://git.duniter.org/vjrj/ginkgo/uploads/79d814eb197fb5969555226cae5296d3/ginkgo-0.1.1.apk
Thanks indeed also for the donations.
@kimamila I’m also certified (I’m just returning from a local market):
https://g1.duniter.org/wot/lookup/vjrj
Search for CORS in this thread. But basically, the web client cannot work well with gva nodes doing POSTS/OPTIONS calls (while it works for classic BMA). It’s a proxy configuration issue. For workaround this all the web gva calls passed for the g1nkgo.comunes.org proxy to the different gva nodes. I don’t like it, but it works … except for the fact that the gva nodes has a rate limit and I can imagine that my proxy is not whitelisted, so many web clients can be perceived it as a single IP and penalize it. How to fix it? Configuring the gva proxies as the duniter proxys allowing any CORS petitions, or, process the proxy x-forwarder client IPs, or other solutions.
Thanks again.
Added Italian and Basque language:
https://git.duniter.org/vjrj/ginkgo/uploads/06c32c0245567efbb4dfd3966dabd43c/ginkgo-0.1.2.apk
I love your App 
Thanks for your CORS explanation.
It is good GVA cannot be open to any IP
Is there a way to edit the proxy in the App parameters ?
what proxy technic are your using (nginx)? You have developped a special API server?
About “key backup”, what is the “crypto” used with “gesture capture”?
Would it be possible to use a numeric pad PIN instead?
Thanks
No, but the proxy is only used in the web version. The apk is connecting directly with the gva nodes.
Just a simple regexp nginx location to redirect /gva/some.domain.org/gva calls to the some.domain.org/gva nodes.
Currently I rethinking this part after @kimamila comment about using a duniter part.
I had another issue when trying to use your app on a g-market this weekend. The popup used to search for people or scan a QR code has very poor visibility outdoors. The green toolbar and the font color may need to be changed, don’t you think?
When you send a payment, the form is not clear (recipient and amount)
Anyway, my first payment succeeded!
The second seems to always failed. Dis you use GVA or BMA ? If BMA, make sure to not reuse same sources.
If GVA, please let us know. Maybe a issue
Added:
Added:
I did this on purpose, the internal state is paid, but you are right that it’s not clear. I want to improve this part in several ways.
This is a GVA issue. When you do a second payment too fast, the GVA nodes give an error that you don’t have balance (and you have). g1nkgo detect the wrong error, and show a retry message. But maybe it’s a durt error (I doubt more on this because @kapis experienced similar things in the superbot). I general have to wait a bit, and retry with success. It’s a bit annoying.
I have several GVA issues. For instance: This week I detected a more serious thing. I sent a transaction successfully, it was in the sending part of the history (I checked it twice) but and the end was not confirmed and added to the sent. This happened 3 times and worried me a bit. So I have to do something to recheck/retry transactions.
Where is the best place to report this kind of issues?
I’ve just published 1.0.3 of Ğ1nkgo:
https://git.duniter.org/vjrj/ginkgo/uploads/546701e0c156f7dc164e40a2ccfead80/ginkgo-0.1.3.apk
I’ve just published v0.1.4 with some fix:
https://git.duniter.org/vjrj/ginkgo/uploads/1788f8eb6f9ec85f7f1c67375ae3b0d8/ginkgo-0.1.4.apk
I’ve just published 0.1.5 with pending and failed transactions with retry (useful for lost payments that doesn’t pass from status sending to sent and are lost after some time):
https://git.duniter.org/vjrj/ginkgo/uploads/7395a07fbd1887ec1b42d5a929449d9c/ginkgo-0.1.5.apk
Quand peut-on espérer voir cette version ?
Je suis impatient.
When can we expect to see this version?
I’m looking forward to it.
Hi @Maaltir:
I have a stupid math round issue, and I don’t find time to test and fix it:
Trasfering a 0,01 DU, I get duplication tx because of the retry functionality (because the amount did not match):
Also I noticed a wrong amount in the notification, too:
It’s normal because I did a looot of changes. So I need to double testing this.
Hello
Il faut peut-être voir comment fait kimamila dans césium
Hello
Perhaps you need to see how @kimamila works in césium
The amount should always be stored as integer in cG1 with the base. Floats are only necessary for converting to/from UD and for displaying. This way you can avoid rounding problems.
