Hyperledger Public Sector White Paper

1. Introduction

1.1 What is Hyperledger 

1.2 Public Sector:

1.3 IMPACT STATEMENT: 

2. Public Sector Environment 

2.1 Identity management for Governments

2.2  Interactions (Highly Regulated Transactions)

2.3. Regulations

2.4 Governance 

3.  Public Sector Mapping

4.  Use cases

4.1 Government Branch: Predatory Bank Loans

4.1.1 Description of Environment 

4.1.2 Description via four rings

4.1.3 Conclusions

4.2 Public Service :  Energy Sector Management 

4.2.1 Description of Environment 

4.2.2 Description via four rings

4.2.3 Conclusions

4.3 Community : Land Registry / Land Markets

4.3.1 Description of Environment 

4.3.2 Description via four rings

4.3.3 Conclusions

4.4 Public Enterprise : Grant Management

4.4.1 Description of Environment 

4.4.2 Description via four rings

4.4.3 Conclusions

5.  Conclusions

6. Recommendations

7. Acknowledgement

Introduction

1. Introduction

Purpose of This Paper

Government has served an important function, to maintain trusted information for member of its society. Blockchain technology can revolutions how agents collect and process information. 

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 lens, (3) important segments need addressing: (1) Identity Management for Public Sector

(2) Compliance, as seen though government transaction ,and/or viewed thru the Highly regulated transaction, and (3) Governance . These areas we see the most benefits blockchain can effect.

We will describe Use cases to show how blockchains are being utilized to improve the public sector.  How tools can help across governments World wide efforts . This whitepaper will tackle the issues by looking at the problem facing the Public Sector and what is being done today and what will our recommendation  for government when adopting blockchain in the public sector.

Intended Audience

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 What is Hyperledger 

What is Hyperledger 

Hyperledger is an open source collaborative effort created to advance cross-industry blockchain technologies. It is a global collaboration, hosted by The Linux Foundation, including leaders in finance, banking, Internet of Things, supply chains, manufacturing and technology. Hyperledger, as part of the Linux Foundation, provides technology leaders a uniquely open and collaborative international community from which to develop, validate, and field enterprise-grade blockchain technology solutions.

What is Hyperledger

Table 1: Summary of Hyperledger Frameworks:

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.

FIGURE 1: THE HYPERLEDGER GREENHOUSE STRUCTURE

[Add a page break at the end of this section]his white paper explains... [start with a brief topic sentence that sums up what’s in the document. This section “tells them what you’re going to tell them.”]

[In this section, provide a high-level introduction to the topic being covered. If the main body of the white paper will cover four different topics, name them each here, and point to the section where they are considered in more detail.]

[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.]  

1.2 Public Sector:

Public Sector

Definitions

Public sector organisations are businesses set up with the aim of providing a public service rather than making a profit., existing in all three layers of government ( Federal. State Local)

Public Sector is usually comprised of organizations that are owned and operated by the government and exist to provide services for its citizens, instead of working toward the goal of collecting a profit, public sector entities seek to provide services, regulate activities and enforce laws.

1. Funding for public services are usually raised through a variety of methods, including taxes, fees, and through financial transfers from other levels of government

   1. Examples of organizations in the public sector include:

      • Education (Schools, Libraries)
      • Electricity
      • Emergency Services
      • Fire Service
      • Gas and Oil
      • Healthcare
      • Infrastructure
      • Law Enforcement
      • Police Services
      • Postal Service
      • Public Transit
      • Social Services
      • Waste Management
   2. .

 PDF

1.3 IMPACT STATEMENT: 

IMPACT STATEMENT: 

Blockchain technology is relatively new technology and is in its very early stages of adoption. Questions need to be answered as to how the Public Sector and related industries  can  leverage blockchain technology in various verticals.  While there is a great hype and interest in the technology it is critical to ensure that initial deployments consider right use cases to demonstrate the effective use of technology.

The intent of this document is to help shape the role blockchain technology can have in optimizing what government can do for its citizens. By delving into three areas (Identity, Compliance issues and Governance ) we will draw conclusions as to how to structure blockchains, develop programs, and run these new system to best aid citizens the derive the optimal success. If  we understand how current use cases are leveraging this technology we can devise standards and guidelines for  governments on all levels to implement.

1 Identity Management in Government 

2.  Interactions

3. Compliance 

4. Governance 

2. Public Sector Environment 

2.1 Identity management for Governments

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

2.3 Recommendation Moving Forward

2.2  Interactions (Highly Regulated Transactions)

2.3. Regulations

 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

2.4 Governance 

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

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

.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.]

Public Sector SIG Whitepaper

• Created by Marta Piekarska on Monday, February 4, 2019

What should be the topic of the first Public Sector SIG Whitepaper? Please indicate topics of interest and willingness to work on it

You voted on Friday, February 8, 2019 

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

LikeBe the first to like this

• No labels
• Edit Labels

2 Comments

1. 

   Alfonso Govela

   
   

   A Mind Map to start our collective definition of "Public Sector" for our White Paper

    PDF

   • Reply
   • Like
   • Apr 25, 2019

   
   

2. 

   Bobbi Muscara

   
   

   Completed the transfer from Google drives, all work should be done on the Wiki page and comment place in this section. Please sign up for the sections you are sponsoring, Task Sign-up, Notes and Agenda

   Happy writing !

   Bobbi