This document describes how terms of service (ToS) as well as other “legal agreement documents” are served, represented and rendered.
Different exchanges and backup/sync providers each have their custom legal agreement documents. As we don’t know all providers and they are not centrally registered anywhere, these documents can’t be hardcoded into wallet applications. Instead, these service providers expose endpoints that allow downloading the latest version of these legal agreement documents.
These documents must be rendered on a variety of platforms in a user-friendly way.
The service providers can output legal agreements in various formats,
determined via the
"Accept: " request header. The format provider must
text/plain mime type. The format provider must support
text/markdown mime type. Except for styling and navigation, the
content of each format of the same legal agreement document should be the
Legal documents with mime type
text/markdown should confirm to the
When wallets render
text/markdown legal documents, they must disable
embedded HTML rendering. Wallets may style the markdown rendering to improve
usability. For example, they can make sections collabsible or add a navigation side-bar
on bigger screens.
It is recommended that the
text/markdown document is used as the “master
document” for generating the corresponding legal agreement document in other
formats. However, service providers can also provide custom versions with more
appropriate styling, like a logo in the header of a printable PDF document.
text/markdown document should follow
the commonmark spec.
Main headlines (level 1) and their following content (until the next main headline)
will be shown as expandable sections in wallets.
The document must begin with a main headline:
# First Headline
First Headline ==============
We considered and rejected the following alternatives:
Html.fromHTML) support undocumented subsets that lack features we want, such as ordered lists. Defining our own HTML subset would also make authoring harder, as it forces authors of legal agreement documents to author in our HTML subset, as conversion tools from other format will not generate output in our HTML subset.
.rstto Markdown nicely.