https://drive.google.com/drive/folders/1TON-iQo2wQWfFS9Gq8knHW1O9rMTV6od

OUTLINE: 

Whitepaper:

Hyperledger [title, as few words as possible]

Purpose of This Paper

The purpose of this white paper is to define how a blockchain-based solution can help telecommunication service providers settle cross-charging payments efficiently and quickly by reducing friction and removing intermediaries.  The final deliverable is a Proof of Concept (PoC) that demonstrates the functionality of the Minimum Viable Product (MVP).

[If something is NOT covered that a reader might reasonably expect to find here, say so. From then on, use the construction... “Any further discussion of (said topic) is beyond the scope of this document.”]

Intended Audience

The primary audience of this white paper are network operators who are interested in reducing the cost of cross-charging settlements, as well as technical people who are interested developing the PoC.

Introduction 3

1.1 subsection--topic 1 3

1.2 subsection--topic 2 3

1.3 subsection--topic 3 3

Title for topic 1 4

2.1 subsection--topic 1 4

2.2 subsection--topic 2 4

2.3 subsection--topic 3 4

Title for topic 2 5

Title for topic 3 6

4.1 subsection--topic 1 6

4.2 subsection--topic 2 6

4.3 subsection--topic 3 6

Title for topic 4 7

5.1 subsection--topic 1 7

Table 1: Summary of Hyperledger Frameworks 7

5.2 subsection--topic 2 7

5.3 subsection--topic 3 7

Conclusions 8

Notes 8

VN.N published [month, year].

This work is licensed under a Creative Commons Attribution 4.0 International License

creativecommons.org/licenses/by/4.0

Acknowledgements

[list all the contributors to the white paper in alphabetical order by LAST name. Many working groups keep a list of members or contributors on their wiki pages or their minutes. Don’t include anyone’s name without their okay.]

1.  Introduction

This white paper will describe the inefficiencies and problems of the current system telecommunication network operators use to settle charges amongst themselves.  The paper will also propose a solution based and a PoC based on Hyperledger to make the system more efficient and cost effective.  

1.1 subsection--topic 1

[If needed, break up the Introduction in subsections. Always have at least 2 subsections, 1.1 and 1.2 or else this numbering system looks unnecessary.]

1.2 subsection--topic 2

[same as above]

1.3 subsection--topic 3

[same as above, if needed]

[Add a page break at the end of the Introduction]

1. Title for topic 1

[Start this section with a brief paragraph that describes what’s in this section. This helps readers know if they need to read this or they can skip it to go onto another topic they’re more interested in.]

[If this section introduces some vocabulary or some fundamental concepts they need to understand before they can benefit from the following sections, say so right at the start.]

If you need to list several points, consider using a set of bullets:

• Item 1

• Item 2

• Item 3

[By default, list items in alphabetical order. if you prefer to use some order, state it: in order of size, in order by first on the market, and so on.]

2.1 subsection--topic 1

[If needed, break this section up in subsections. Always have at least 2 subsections, 2.1 and 2.2 or else this numbering system looks unnecessary.]

2.2 subsection--topic 2

[same as above]

2.3 subsection--topic 3

[same as above, if needed]

[Add a page break at the end of this section]

1. Title for topic 2

[Start this section with a brief paragraph that describes what’s in this section. This helps readers know if they need to read this or they can skip it to go onto another topic they’re more interested in.]

[To include a diagram, insert the diagram right into the GDoc. Then give it a number (Figure 1, Figure 2, etc.) and a short, clear title and then reference it in the text:

As shown in Figure 1, the Hyperledger Greenhouse incubates a number of different frameworks (on the top level) and tools (on the bottom level).]

[When the white paper is prepared for publication, the designer can recreate the graphic to look nicer and use the Linux Foundation color scheme.]

FIGURE 1: THE HYPERLEDGER GREENHOUSE STRUCTURE

[Add a page break at the end of this section]

1. Title for topic 3

[Start this section with a brief paragraph that describes what’s in this section. This helps readers know if they need to read this or they can skip it to go onto another topic they’re more interested in.]

4.1 subsection--topic 1

[If needed, break this section up into subsections. Always have at least 2 subsections, 4.1 and 4.2 or else this numbering system looks unnecessary.]

4.2 subsection--topic 2

[same as above]

4.3 subsection--topic 3

[same as above, if needed]

[Add a page break at the end of this section]

1. Title for topic 4

[Start this section with a brief paragraph that describes what’s in this section. This helps readers know if they need to read this or they can skip it to go onto another topic they’re more interested in.]

5.1 subsection--topic 1

[To include a table, create the table right in the GDoc. You can use the table below as a starting point. Give it a number (Table 1, Table 2, etc.) and a short, clear title and then reference it in the text:

As shown in Table 1, different Hyperledger frameworks have different purposes. You can see more about each framework in the section shown.]

[When the white paper is prepared for publication, the designer will recreate the table to look nicer and use the Linux Foundation publication template.]

Table 1: Summary of Hyperledger Frameworks

5.2 subsection--topic 2

[same as above]

5.3 subsection--topic 3

[same as above, if needed]

[Add a page break at the end of this section]

1. Conclusions

This white paper explained... [sum up the white paper briefly. This section “tells them what you told them.” Although this may seem repetitive, some people flip to the back of a document to see “the bottom line” and what they might have missed.]

Further Resources

[In this section, list any further resources or interesting reading that might illuminate the topic more. Include enough detail so that a reader could easily locate that source, including URLs if appropriate.]

Notes

[Although GDocs can’t do Endnotes, the designer will move all your footnotes here. In every footnote, provide the AUTHOR(s), the article or document TITLE, the PUBLISHER, the DATE, and if you have it, the PAGE NUMBER. For a website, include the URL and RETRIEVED ON DATE.]

POINTS TO COVER

1. Motivation / Problem
2. Barriers
3. Customer Groups
4. Opportunities

5. Solution:
     Platform 
     Team
     Road map

6.  Mission
7.  Use Cases
8. Conclusion

Whitepaper Standards Contributed by Learning Materials Development Working Group, Gordon Graham and Bobbi Muscara