> No. That's way too complex for the exchange. The exchange has a process
> for how the ToS should be generated, the user should stick to that. I've
> text/markdown as a mime type and generates one from the RST specs. But
> we should not complicate the exchange logic with a markdown parser.
> That's too far.
ACK, Maybe we can somehow expose the wallet validation as a cli and the exchange operator can use that.
> No, I don't think so. Storing the ToS locally likely would make the
> wallet DB significantly larger (which also creates more traffic for
> backups!), and it's pretty rare that a user would really want to read
> the ToS offline after having agreed to them. Not to mention exchanges
> are likely to offer the ToS in multiple languages, and switching between
> them might also be desirable. So this one I don't see as a positive
> change, just extra code and data for no important use-case.
If the wallet and exchange has a conflict regarding the ToS the content is important so the wallet user does not depend on someone storing the tos.
Empty wallet size, almost 2mb
Wallet with some coins, 5.5 mb
This is a small wallet without purchases.
tos size is less than 20k
Gzipped version ~ 6K
I think size would not be a problem.