Integrate name transfer service #537
Comments
Is this issue still applicable? |
Yes -- there's still people who will need help migrating names from older browser versions, and we still don't have a tool for it. I have a script that can output the requisite private keys, and then that can be sent over to a local blockstack API endpoint to do the transer/update, but we would need to flesh it out and document it before declaring victory there. |
Is this an REST call we could add to the |
No -- it's mostly javascript actually -- it takes the 24 word mnemonic and turns it into a private key hex string, which can then be passed to a REST call. This could be done by the browser, or it could be a tiny CLI script. I'd prefer not to add any more REST calls to |
I've started work on a tool to let people calculate their private keys for older keychain formats here: https://github.com/blockstack/blockstack-browser/tree/feature/migration-tool |
@kantai has written some components of a transfer service which are currently located here:
https://github.com/kantai/blockstack-transfer-service
It includes code to migrate names from core wallet and portal pre-
v0.9.0
. Code for wallets after that and beforev0.10.0-alpha.1
is not yet written.Browser page
We'll need to put this together in the browser. The interface of the app should be pretty simple:
textarea
to pastewallet.json
or mnemonic to migrate or button to migrate current browser wallet. If current wallet, user will need to enter their password.Subsidizer service
We need a subsidizer service based on this test subzidizer with a hot wallet: https://github.com/kantai/blockstack-transfer-service/blob/master/python-service/test_subsidizer.py
@kantai will need code from Onename to finish implementing this.
The text was updated successfully, but these errors were encountered: