Ǧinkgo release 0.2.0

vjrj · 18 June 2023 19:58

I’ve just published 0.2.0 version of G1nkgo that includes (mainly):

DU/G1 currency selection
Pending, failed and retry payments
Offline payments
Added checksum to public keys :XXX

and many other small enhancements and fixes.

https://git.duniter.org/vjrj/ginkgo/uploads/ea38a4dfd806a23a76f5aaa5e5db24a4/ginkgo-0.2.0.apk

For a full (and big) list:

vjrj · 27 June 2023 20:08

I just released version 0.2.1 of G1nkgo which includes:

Wallet names through Cesium Plus profiles (a ❥ is added to the end of the names to make it different from the name of your cesium or superbot wallet to avoid confusion)

Export of wallets via email/chat/etc
Improvements in the automatic management of nodes
Usability improvements
Apk:
https://git.duniter.org/vjrj/ginkgo/uploads/75f27d72744fdb7e300c16544320e18c/ginkgo-0.2.1.apk

More details of the fixes and improvements in:

vjrj · 1 July 2023 21:37

I have just published version 0.2.2 of G1nkgo that fixes the QR scanning of public keys and the new checksums in Payments and the editing of contacts with improvements (now you can share the qr of contacts more easily). . https://git.duniter.org/vjrj/ginkgo/uploads/486a416040dda82cd36fc00521be2a72/ginkgo-0.2.2.apk

I recommend its installation.

More info: 0.2.2 · vjrj / ginkgo · GitLab

flodef · 2 July 2023 12:13

The app is so cool. I just love it so much.
It’s the best onboarding tool ever. People around me love it too. And it’s getting better and better.
I’ll try to submit some bugs after intensive testing…
You’re doing a great job ! And very fast shipping as well. Congrats

vjrj · 2 July 2023 14:41

Thanks indeed for your message @flodef . I don’t have (and I don’t want to have) any metric of usage of G1nkgo so this kind de messages are really appreciated.

Maaltir · 2 July 2023 16:34

Merci pour cette application. Vraiment très simple à utiliser pour un débutant.

Petit souci parfois lors du payement, il faut repasser par le solde pour qu’il soit mis à jour.

Et, tout à coup, le solde s’affiche en DU, et du coup le payement semble compter en DUğ1 l’alors qu’il affiche Ğ1 non modifiable. Il faut alors passer par le mode expert pour préciser Ğ1 ou DUğ1.

Je pense que ce passage de Ğ1 à DUğ1 ne devrait pas être réservé aux experts.

J’ai voulu scanner un QR-code avec un montant, que j’imaginait afficher en Ğ1, alors que moi, j’étais configuré en DUğ1. Il n’y a pas eu de traduction de l’un vers l’autre.

Thank you for this application. Really easy to use for a beginner.

Sometimes when you pay, you have to go back to the balance to update it.

Suddenly, the balance is displayed in DU, and so the payment seems to count in DUğ1 l whereas it displays Ğ1 which cannot be modified. You then have to go to expert mode to specify Ğ1 or DUğ1.

I don’t think this switch from Ğ1 to DUğ1 should be reserved for experts.

I wanted to scan a QR-code with an amount, which I imagined would be displayed in Ğ1, whereas I was configured in DUğ1. There was no translation from one to the other.

vjrj · 15 July 2023 09:51

I just published version 0.2.3 of Ğ1nkgo that includes:

Fix for amount correct qr scanning
Fix for search of public keys with checksums (thanks Sandrisha for the feedback)
Add of contacts directly in Contacts (thx @SergeUme for the feedback)
Search duniter/cesium+ users also from Contacts
better june:// urls processing (thanks to FredMadeInZion for the feedback)
association of june:// to g1nkgo in Android
experimental write and read of NFC labels (using NFC tags for now)

https://git.duniter.org/vjrj/ginkgo/uploads/0e8179c01cc64d7ac40cafe1f09f453b/ginkgo-0.2.3.apk

flodef · 16 July 2023 23:05

Thank you so much for your nice answers and already fixing so many bugs…
If you got time, I would like to call you to chat about a project I have with g1nkgo. I think it could be fun

vjrj · 16 July 2023 23:28

Perfect!

flodef · 29 July 2023 18:05

Fun fact : I just realised that Ginkgo means “Bank” in Japanese

vjrj · 6 August 2023 22:57

I didn’t read this message

vjrj · 6 August 2023 23:06

I’ve just published the 0.2.4 version of G1nkgo.

It includes many bug fixes and enhancements and I recommend to install it. It includes among others: better nodes auto-update, offline payments issue fixed, VPN support, more import/export options.

More info:

Special thanks to @flodef and @bytes4life for their first contributions!

https://git.duniter.org/vjrj/ginkgo/uploads/cecfcbc79c758414425e874c94bb4d95/ginkgo-0.2.4.apk

vjrj · 20 August 2023 12:23

Dear all, I’ve just published a development version of Ğ1nkgo that includes support to multi-accounts (that includes passwords protected Cesium accounts).

Since the beginning Ğ1nkgo was designed to provide this kind of features, but it was not totally programmed or tested, and I wanted to focus into newbies users (without any type of wallet).

You can test this version here Private Seafile

I don’t have more time this weekend to test of improve it more, but you can try it. Please do a backup of your wallet before testing if you don’t have one.

Some screenshots:

PS: This version also solves some issues and adds some new small features (like qr scan button in payments, DU selector only in Info tab).

kimamila · 21 August 2023 08:17

Impressive UI! You really did a great job!

I hope you’ll allow me a few remarks and suggestions, without feeling offended?

Here are my observations and suggestions:

When setting a name for a Gnkgo account (the default one), it’s not evident that this name will be publicly visible. It might be more user-friendly to provide an option (perhaps a checkbox) for users to decide whether they want this name to be public. This can prevent users from inadvertently sharing sensitive information like “my wife’s birthday gift” or even more compromising details.
On the account card, only the first 8 characters of the public key are displayed. However, wallets like Cesium now use the format “nnnn…nnnn:chk”, which shows the first 4, the last 4, followed by a checksum. It might be less confusing to at least display the first and last characters of the public key.
Accounts with credentials (Salt/password) are not labeled as “Cesium accounts”. This can be misleading. Perhaps consider renaming them to “secured account”, “protected account”, or “account secured by a secret phrase and password, similar to Cesium”.
It would be helpful to have a visual indicator (like a locked icon overlaying the account card) to differentiate these secured accounts.
Transactions originating from a protected account should have added security measures (like a pattern/schema lock, PIN, etc.). Storing the private key directly on the mobile device poses significant security risks !

vjrj · 21 August 2023 08:29

Hi @kimamila thanks indeed for your comments as usual. I’ll try to take all into account.

About the last one, G1nkgo does not stores the protected accounts private key (only in memory). In this case, the user has to enter the passwords on each session on demand.

I maintain in memory the cesium wallets info here (that are requested when paying, for instance):

The way I detect if is a protected card or not is looking if I had persisted the seed (not in the case of Cesium accounts):

I trying not to compromise the current security of the cesium accounts (and this was one of the reason to not adding this before).

Again, merci! Anyway the new cesium version works great!

kimamila · 21 August 2023 08:48

ok, never mind. I forgot to relaunch the app, during my test.

I have a few more remarks (sorry!):

In the “balance” tab:
- The “menu” button doesn’t open the menu but reveals the balance (even though there’s already a button for that). It’s inconvenient for switching accounts, I think.
- Transactions from payments to multiple recipients don’t display the correct amount (the one to our account) or the correct recipient (probably the first one). See payments received from “Remuniter”.
- If I make a payment (for example, 100 G1), the transaction appears correctly, but the balance hasn’t been updated (by -100€).
- By the way, do you make sure that GVA doesn’t send you the same TX sources (already consumed, for example in my 100 G1 send) for the next payment? Is there a way to tell GVA to exclude certain TX sources? I feel like GVA doesn’t consider pending payments: can you confirm? Maybe you also don’t switch nodes regularly, which could explain these issues?
  If GVA uses the same sources for consecutive payments, then only the first payment can work: you’d have to wait for the 1st TX to be written so that the next TX generated by GVA is correct. Do you get what I mean?

Thanks to you, indirectly: it’s very motivating for me to work in a creative and active group. It challenges me (in a good way, I believe) and gives me or rekindles ideas!

Once again: you’re doing a great job!

flodef · 21 August 2023 12:45

It’s really hard for me to grasp this !
Can you tell me more ?
And where do you prefer to store your private key ?

kimamila · 22 August 2023 20:02

In my mind ?

vjrj · 26 August 2023 12:04

Thanks @kimamila for your comments.

The lib I use don’t allow more customizations. I have to find a UI alternative.

You are right. I use the GVA returned balance and the calculation depends from one node to other (In the past I calculated this via BMA queries and calculations).

The gva pay call is quite simple:

Looking in a /gva/playground:

I’m not sure if we can do it better from the client side.

And g1nkgo choose aleatory from the synced and reachable nodes, so maybe sometimes the same node was selected during fast payments:

PS: BTW Merci merci beaucoup for your donations

Frederic_Renault · 30 August 2023 13:17

During my last tests, G1nkgo 0.2.5-SNAPSHOT doesn’t get anymore comment from payment QRcode

For exemple :

which is of that kind june://DESTINATIONPUBKEY?comment=PREFIX:COMMENT
Is it because amount is needed ?

NB: This QRCode is produced and used by “G1 VOD Service” i am working on. So shown wallet monitors receiving payments with such comment then operate an action based on it. In this case (PREFIX=N1Kodi) it send back through Cesium+ messaging a link to watch a video.