# Ğ1nkgo v2 support progress, plan and pubkeys/address proposal

**URL:** https://forum.duniter.org/t/g1nkgo-v2-support-progress-plan-and-pubkeys-address-proposal/12617
**Category:** Ğinkgo
**Tags:** v2s, ss58, ginkgo
**Created:** [27 October 2024 20:59 UTC](https://forum.duniter.org/t/g1nkgo-v2-support-progress-plan-and-pubkeys-address-proposal/12617 "2024-10-27T20:59:48Z")
**Posts on this page:** 1
**Showing post:** 14

<div class="post-metadata">

### Author: ![vjrj](https://forum.duniter.org/user_avatar/forum.duniter.org/vjrj/32/8487_2.png) [@vjrj](https://forum.duniter.org/u/vjrj)
#### Post date: [17 November 2024 19:48 UTC](https://forum.duniter.org/t/g1nkgo-v2-support-progress-plan-and-pubkeys-address-proposal/12617/14 "2024-11-17T19:48:14Z")

</div>

To be more clear: I think we should avoid this type of migration in our current wallets and public keys (and addresses).

My ideal is to migrate the network to v2 and that the users do not see more than improvements. The use of bip39 is not necessary for existing wallets IMHO. In other words: We should continue asking for pass/passphrases to old wallets (or nothing for ginkgo/superbot basic wallets) and only use bip39 in new accounts (if we don’t find nothing more usable). Derivations? Not now for them.

---

_[View the full topic](https://forum.duniter.org/t/g1nkgo-v2-support-progress-plan-and-pubkeys-address-proposal/12617)._