Hyperledger Public Sector White Paper
I. Introduction
1.1 What is Hyperledger
1.2 Public Sector
1.3 IMPACT STATEMENT:
II. Identity management for Governments
2.1 What is Identity Management
2.2 Use Cases
2.3 Recommendation Moving Forward
III. Compliance
3.1 What Is the Highly Regulated Transaction
3..2 Use Cases
* Land Entitlements
*Agriculture
3.3 Recommendations Moving Forward
IV. Governance
4.1 Governments Blockchain governance
4.2 Use cases
4.3 Recommendations Moving Forward
V. Conclusions
Notes 8
Introduction
https://docs.google.com/document/d/1qlYy3ql4QXldVMU_iKNdqsUDXMUS_naw01kNFCGGHig/edit#
...
Purpose of This Paper
The purpose of this paper is to derive pathways for the Public Sector when discovering the benefits of Blockchain Technology When discussing Blockchain thru a Public Sector lense, (3) important segments need addressing: (1) Identity Management for Public Sector
...
Across Governments [state the intended audience as precisely as possible. For most white papers, this will be a technical audience, not a business audience. Does their level of technical understanding matter? Are there some matters they should already understand before they can get anything from the current document? Can we point them to this kind of prerequisite information? Does it matter which framework(s) they are using: Fabric, Indy, Sawtooth, etc? Does it matter what issue they are trying to understand: security, interoperability, etc?]
1.1 Identity Management in Government 3
Identity management for Governments 4
2.1 What is Identity Management 4
2.3 Recommendation Moving Forward 4
3.1 What Is the Highly Regulated Transaction 6
3.3 Recommendations Moving Forward 6
4.1 Governments Blockchain governance 7
4.2 Use cases 7
4.3 Recommendations Moving Forward 7
...
What is Hyperledger
Public Sector
View file name Public_Sector.pdf height 250
IMPACT STATEMENT:
1 Identity Management in Government
2. Compliance
3. Governance
What is Hyperledger
Table 1: Summary of Hyperledger Frameworks:
FRAMEWORK | BRIEF DESCRIPTION |
HYPERLEDGER FABRIC | A platform for building distributed ledger solutions with a modular architecture that delivers a high degree of confidentiality, flexibility, resiliency, and scalability. This enables solutions developed with Hyperledger Fabric to be adapted for any industry. |
HYPERLEDGER SAWTOOTH | A modular platform for building, deploying, and running distributed ledgers. Sawtooth features a new type of consensus, proof of elapsed time (PoET) which consumes far fewer resources than proof of work (PoW). |
Comment From Sofia Terzi The frameworks that must be listed here should include also Iroha and Indy. Iroha is an engine that can run public sector's smart contracts and Indy is for the identity part of our whitepaper.
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.]
Introduction
What is Hyperledger
Table 1: Summary of Hyperledger Frameworks
FIGURE 1: THE HYPERLEDGER GREENHOUSE STRUCTURE
...
[This section doesn’t have to be written first, but it must be filled in before the publication is complete. This helps readers understand the scope of the white paper and whether it’s worth their time to read the entire publication.]
Public Sector
Public Sector Consortiums and Purpose of White Paper
IMPACT STATEMENT
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 Compliance
[same as above]
1.3 Governance
[same as above, if needed]
[Add a page break at the end of the Introduction]
Identity
Identity Management in Government
2. Compliance
3. Governance
2. Identity management for Governments:
Topics discussed in working group:
CROSS BORDER ID credentials.
No personal information interoperability and privacy management DID .
Information should not leave the boundaries (geo fencing) Cross countries boundaries.
Interoperability and privacy [If you need to list several points, consider using a set of bullets:
People
Places
Things - IOT
...
2.1
...
What is Identity Management in dealing with the Public Sector
2.2 Use Cases
[same as above]
2.3
...
[same as above, if needed]
[Add a page break at the end of this section]
[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.]
Governance
[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]
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
...
FRAMEWORK
...
BRIEF DESCRIPTION
...
SEE ALSO
...
HYPERLEDGER FABRIC
...
A platform for building distributed ledger solutions with a modular architecture that delivers a high degree of confidentiality, flexibility, resiliency, and scalability. This enables solutions developed with Hyperledger Fabric to be adapted for any industry.
...
6.2
...
HYPERLEDGER SAWTOOTH
...
A modular platform for building, deploying, and running distributed ledgers. Sawtooth features a new type of consensus, proof of elapsed time (PoET) which consumes far fewer resources than proof of work (PoW).
...
6.3
Recommendation Moving Forward
3. Compliance
3.1 What is the Highly regulated Transaction common with most dealing with the Public Sector
3.2 Use Cases
3.3 Recommendation Moving Forward
4. Governance
4.1 What is Blockchain Governance in dealing with the Public Sector
4.2 Use Cases
4.3 Recommendation Moving Forward
5. Conclusions
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]
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.]
...
[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
.01 VN.N published May,2019.
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.]
[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.]
...
| View file | ||||
|---|---|---|---|---|
|
...