I confirmed that @rehrar is indeed a valid member representing the Cypherstack team from Stack Wallet.
→ Verify that Stack Wallet team contacted the Grin project · Issue #1222 · cypherstack/stack_wallet · GitHub
I agree, it would be best if @rehrar makes a post with more details.
Grin as a project does indeed not do marketing as @bruges mentions, nor do we recommend an option. We can put Stack Wallet as an option on our github pages, websites and it will be mentioned in the newsletter. This will however be in a neutral informative way. Grin never makes marketing, we just inform our community.
I see supporting Stack Wallet a bit as a gamble, it could work out, it might not.
If I like the details, I will support taking that gamble.
In all cases I think it would be good to let @rehrar make a more detailed proposal.
I will provide some example of details that we have not even touched upon:
- Will transactions communication over tor be supported
- Will copy paste slate-packs be support (must)
- Will RSR and SRS flow both be supported
- Will Stack Wallet use a central node
- Will there be an option to specify your own node etc
- Will there be a no logging policy
- Under what license does Stack Wallet publishes (e.g. Apache v2 license is preferred)
- What kind of derivation will you support, are you aware that grin use its entropy directly, not with hashing like in BIP39 seed derivation, meaning the seed can be converted back to a mnemonic phrase when the user asks for it? This might affect the security of Stack Wallet users.
- Will maintenance pull request be supported (yes was the answer in Telegram, but please lets write it also here in detail)