Hi. Owner here. The details are it’s $20k without those stipulations and details, and the $16k without. Deliverables are a fully functional, and open source Grin Dart library (wrapper) that other Dart based wallets can use. That in addition to the integration with Stack Wallet itself.
I would agree. I don’t have strong opinion either way, but I think it makes more sense to just pay the $20k so they’re aren’t nebulous and ongoing duties of “the grin community” to promote stack wallet I guess.
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)
Totally fine to not do the marketing aspect. The price would then be $20k. To answer the questions:
We’re looking into Tor sends, but I try as hard as possible to have feature parity between all platforms supported (Windows, MacOS, Linux, Android, iOS). If something won’t work on mobile then I won’t put it in desktop either. Tor has historically given issue with mobile. That said, we have Arti integrated already for general Tor connections, so we’re looking into what it would take to utilize that as well for sends. This is a maybe.
Yes.
Wiesche did work on a Rust bridge that supports these, so yes.
We will run our node that is the default node.
Always. It’s for every coin integrated already and Grin will be no different.
I consider all user information toxic. I’m not paying in any way to secure it, so the only reasonable thing to do is not have it at all. Stack Wallet takes zero user data and we purge our servers every couple weeks if not sooner. There is no analytics or anything in the app, website, or anything else. I’m a cypherpunk.
Stack Wallet itself is published GPL. But all of our libraries and bridges are all published permissively (MIT). The plan is to publish a Grin FFI bridge library that other wallets can use also. These will be published MIT.
Discussing in Telegram what would be required of us here. Will update this post when we have things nailed down.
I think adding support for payment proofs woul be great.
Early payment proofs are to my knowledge only in the contract branch which is not yet ready according to @oryhp . Can we move early payment proofs to the main branch @tromp ? Working payment proofs for both SRS and RSR (requires early payment proofs), are a must IMO. Whether Stack Wallet will support early proofs likely depends on us getting them working in grin-wallet.
