[Tk of specification]

• Keywords: [keyword list]
• Status: draft
• Editor: [Author] [Emai]
• Protocol: Hyperpayment protocol. [Protocol Link] [Tk of specification]’s intro. Here is the short purpose of the implementation

License

Copyright © [year], [Author], and contributors.

This Specification is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License or (at your option) any later version. This Specification is distributed in the hope that it will be useful but WITHOUT ANY WARRANTY, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License and this program; if not, see http://www.gnu.org/licenses.

Change Process

This Specification is a free and open standard governed by the Ara Foundation. Any changes must be approved by consensus with the main editor.

Language

The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119 (see “Key words for use in RFCs to Indicate Requirement Levels”).

Goals

[Tk of specification] goals is the extended version of the intro with the example of the use cases.

It aims to:

• [list element]

The use cases for [Tk of specification] include:

• [list element]

[Categories]

Categories:

• Client
• Dependency
• Business

[Flow]

• [list element] [Resources]
• [list element]

[Splines]

• [list element] [Junctions]
• [list element] [Contracts]
• [list element]

Implementations and Further Reading

A software, and payment systems that supports this protocol. A softwares that follows the specification.