So with DVC set up in my new interstellar wallet the process to transfer XLM from my Statgazer wallet to make my purchase begins....
After grabbing the public key from the new interstellar wallet it was placed in the Account to receive in the Send area of my Stargazer wallet and the notice that came up unnerved me a bit and gave me pause...
"Recipient account isn't registered. Send a minimum amount of 20 XLM to activate it."
How did you get your SBD into the interstellar wallet, @satoshi0x and was there a minimum amount required?
Have you considered just using your private key to access your balance through interstellar.exchange directly? That's what I did.
Is that what they are referring to by importing a wallet as opposed to creating one? Not at desk top right now yet seem to remember them calling it "import".
How did you get your SBD to your interstellar wallet?
I just used SBD for an example in place of "DVC" to show someone how to add a coin to their interstellar.exchange Home panel. There is no "interstellar wallet" per say, it's just a menu that helps you access the tokens so they can be "sent to your wallet" - which is not on the exchange.
I used SBD for the example because I had already added DVC to my wallet before you asked me to write this tutorial and I wasn't going to delete the DVC (and untrust the asset - causing me more XLM to just reactivate it again) for the purpose of this tutorial because that'd be ridiculous - and I would've had to forfeit my 10,000 DVC tokens I have on Stellar as a part of that process.
I noticed that users of the Android/Google Play Store app for "Stargazer" are having issues sending funds as well. Read reviews here: https://play.google.com/store/apps/details?id=io.futuretense.stargazer.wallet&hl=en_US
Any insights as to Stargazer's demand @knotwork?
It also appears that Stargazer is not open source, and was in the middle of changing licensing on github, but they clearly say here that it is "not open source": https://github.com/future-tense/stargazer/commit/c498659039a20a2ae2b75bc578e24f6b64fa93b1
Could be an issue of compatibility that you'd be aware of more than I.