completed
Tribal DIDs=Indigenous Sovereignty
Current Project Status
Complete
Amount
Received
$352,800
Amount
Requested
$352,800
Percentage
Received
100.00%
Solution

Using AtalaPrism SDK, integrate DID wallet features in Āhau, the tribal identity DApp made for, by, with Maori, indigenous people of Aotearoa (New Zealand) to enable issuance of verifiable credentials

Problem

Tribal identity systems, in place for millennia, are not yet recognised by states/institutions creating national DIDs, excluding indigenous population’s pre-colonial norms, rules, rights & sovereignty

Impact / Alignment
Feasibility
Auditability

Geneva

3 members

Tribal DIDs=Indigenous Sovereignty

Please describe your proposed solution.

<u>Introduction</u>

In Aotearoa (New Zealand) the state has drafted a new Digital Identity Services Trust Bill that will define the rules for how institutions and organisations in Aotearoa will recognise and trust someone's digital identity. It intends to revolutionise how Banks, Universities, Health care providers, Schools, Passport issuers and other public services work.

The draft Bill states that the “Rules will incorporate Te Ao Māori perspectives of identity” as part of its legislative purpose. To what extent this happens is still being determined. Our capability, as Maori, to develop our own systems of identity to be interoperable with other institutional identity systems will be a contributing factor.

This project proposes we develop a Tribal DID, in alignment with these draft Identity management standards to empower Maori to have their Tribal Identity practises recognised by organisations and institutions and their rights to sovereign identity, as Maori, and its legitimacy, enshrined.

<u>Why its (very) important</u>

This is an exciting time for our Maori communities. The Government (of the last 200+ years) has the opportunity and responsibility to organise itself to operate alongside existing Tribal governance systems, practices and authority. The work Āhau, the Indigenous Identity DApp, has undertaken over the last 4 years is a significant step towards ensuring this opportunity is realised.

Āhau is well on the way to enabling its communities to be recognised issuers of verifiable identity credentials. Enabling this important technological advancement to take place will speed along the future which delivers Maori the self-determination and self-governance we have the right to.

Āhau is a scuttlebutt based dapp used by tribal communities to identify and register community members, preserve cultural heritage and histories, and grow individual and collective identity. Our next step is to use AtalaPrism’s SDK to integrate digital identity wallet features in the Āhau DApp.

Our goal is to provide tribal communities with the ability to issue verifiable credentials to their tribal members. Tribal members will then be able to present these credentials to third parties to use as a reliable and trusted form of identity verification.

<u>Context</u>

Māori (indigenous people of New Zealand) are a collectivist society connected by tribal groupings called Whanau (immediate family), Hapu (extended family groups), and Iwi (‘tribes’ of broader, related whanau). In the early years of our colonisation, during the British invasion of Aotearoa, the English sought to establish a treaty agreement known as Te Tiriti o Waitangi or The Treaty of Waitangi between The British Crown and the tribal chiefs of Aotearoa.

Many chiefs of Aotearoa, agreed to peace and signed Te Titiri in good faith so that the Crown would cease unlawful attacks, confiscation of Māori land, and enforce greater control over English settlers. Te Tiriti also provided for the right to Rangatiratanga or self-determination and self-governance for Maori.

However, the British did not honour Te Tiriti, and today Aotearoa, now named New Zealand (by the New Zealand Company which made a business of colonising Aotearoa) is now governed by a Government setup by the English Crown. Less than 5% of the land remains in Māori hands.

While Aotearoa bears this dark history, the Crown has established a process for reconciliation and apologies. As Māori we are now progressively imbuing our cultural systems (with varying degrees of friction and speed) into legislation, courts, education, health and many other parts of society.

Identity is foundational for Māori communities in identifying tribal members and how we connect with each other. Māori identity is also foundational to the future of our society as a whole. Our people being able to prove who they are, via a means which is aligned culturally to them, is a crucial element of all future interactions aiming to restore trust; to instantiate indigenous human rights; and, with integrity, live up to the egalitarian image our country has acquired globally.

Providing a solution for tribal communities to reaffirm their cultural systems of identity and integrate this with the Digital Identity Services Trust Framework is critical to the future we want to create. It will not only acknowledge Māori’s right to establish and confirm their identity, it will also provide an opportunity for institutional models of identity to expand their understanding and systems of identity to be more inclusive of community issued credentials.

This advancement can and (we hope) will, have ripples across the world. Community issued credentials are applicable to many people, in many contexts and countries, not least to those who are part of this Project Catalyst community.

<u>Use case one: Trusted by Tribes</u>

Working with a number of related Māori communities we will design the process for issuing, presenting and verifying, Verifiable Credentials (VC’s) in alignment with tribal identity processes.

These VC’s will be provided from one tribe and will be accepted by another tribes as a relying party

Image File

<u>Use case two: Trusted by Government</u>

After successfully designing and understanding the tribal processes for verifying identity and issuing VC’s, we will work with the Government rules development team to facilitate the design of the process of accepting tribal VC’s as a verified form of identity.

Image File

<u>Use case three: Trusted by Organisations</u>

After designing the process so that the Government can recognise tribal communities as trusted sources of identity, and enabling Āhau to be recognised as a DID infrastructure provider we’ll then work with a number of organisations to facilitate the design of the process for them accepting VC’s through Āhau as a recognised form of Identity verification.

Image File

<u>Identity Compliance</u>

The team from digital legal systems labs will lead the testing of the rules design process against the digital identity standards and rules. This will be developed in a way that not only helps Āhau to identify areas of compliance but also is a tool that other identity systems can use to support the development of identity systems in Aotearoa.

<u>AtalaPrism in Āhau</u>

We will have a developer participate in the AtalaPrism Pioneer Programme to get early access to the SDK. Our team will then develop the frontend and backend for dapp integration with the SDK

<u>Identity Pilots</u>

With the technical infrastructure in place we will roll out a number of tests with the different use cases mentioned above.

<u>Application rollout</u>

Upon successful delivery of the pilots we will initiate an application wide rollout to deliver features to all communities and users.

<u>References</u>

https://www.legislation.govt.nz/bill/Government/2021/0078/latest/LMS659576.html

<https://dl.acm.org/doi/fullHtml/10.1145/3446983.3446992#:~:text=A%20DID%20acts%20as%20an,for%20undoubtedly%20proving%20an%20identity>

Please describe how your proposed solution will address the Challenge that you have submitted it in.

This proposal supports the Challenge to develop “a thriving ecosystem of different DApps, products and integrations for the community to use that increasingly become the better alternatives over current centralized providers” in two important ways.

First, most importantly, Tribal DIDs are not only a ‘better alternative’, they are a human right.

Integrating an authentic indigenous identity platform for people who maintain ancient polycentric governance practices with Cardano products will be significant.

Delivering Mori Tribes with Sovereign Identity which is interoperable with existing centralised systems provides a model for, and can develop into, far more advanced solutions for many colonised people.

Āhau is mainly used by indigenous communities in Aotearoa but is also being explored in other parts of the world. This solution, built on top of Cardano will enable a new audience, critical to the establishment of true diversity in its ecosystem, to connect with the potential and opportunities Cardano offers.

Second, the intention of developing this product, using draft legislation being proposed by a state is an important use case for Cardano.

Presenting a working DApp to a Government which meets all the requirements that that Government is proposing in its draft bill will enhance Cardano’s brand and reputation. Demonstrating without doubt that Cardano’s intention really is “to make the world better for all”.

We’ve already demonstrated we do what we say we’ll do, and have achieved significant success to date with Āhau.

We look forward to taking next steps towards that better world as part of the Project Catalyst DApps and Integrations Challenge cohort.

What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?

<u>Technology Risk</u>

AtalaPrism SDK is still in it early phases so its hard to tell how stable it is, and how it easily it will intergrate to with Āhau. To mitigate this risk we will be participating in the pioneer programme working directly with the AtalaPrism team to solve technical challenges we face. We will also continue to look for alternative DID stacks as part of our technical research

<u>Communications Risk</u>

The project has three core contributing teams. This includes the design team, the development team, the legal team. The coordination and commuinciation between these teams needs to be clear to ensure that we are all working towards the same clear objectives. For this reason we have an experienced project manager as a part of the team to ensure that the coordination and communication between teams is clear with regular checkins and updates.

<u>Scope Creep</u>

With every digital project its important not to let the scope of the project grow outside of the initial project objectives. Our product owner will be responsible for ensuring that the design, development and legal teams stay within the requirements of the project in an agile manner with small functional slices being developed and delivered throughout the project.

<u>Compliance Risk</u>

This projects aims to demonstrate how traditional cultural identity systems meet Government and industry standards and can be interoperable with newly proposed systems. One risk around this project is that the cultural practises of identity management and recognition do not align with the Government and business standards.

This risk will be mitigated by the legal team who’ll identify areas of noncompliance and provide recommendations for how the cultural systems may be changed to comply. The project also aims to provide recommendations that communicate to the Government digital identity standards design team how the proposed standards themselves may be changed to align with cultural systems, in accordance with the goals of the legislation and rights of indigenous people.

Please provide a detailed plan, including timeline and key milestones for delivering your proposal.

<u>Partners</u>

  • Tribal communities and members
  • DIA (The NZ Government Department of Internal Affairs – births, deaths, marriages department)
  • A Bank, A Credit union, Easycrypto

<u>Systems/teams</u>

<u>Phase one: Discovery and Design</u>

3 months Oct – Dec

  • Discovery/ Design
  • Confirm project team and partners
  • Project manager
  • Digital legal systems labs
  • Tribal communities
  • Department of Internal Affairs
  • Industry partners
  • User stories defining and UX
  • use case one trusted by tribes
  • use case two trusted by Government
  • use case three trusted by industry
  • wireframing of UI
  • the issuing of VC’s
  • the storage and management of VC’s
  • the receipt of VC’s
  • the verifying of VC’s
  • the sharing of VC’s
  • and a history of VC’s
  • Identity compliance research
  • Research identity rules and standards
  • Identify and define compliance measures
  • Technology research
  • AtalaPrism Developer Pioneer programme participation
  • Technology design and speciifcations

<u>Phase two: Development</u>

3 months Jan – Mar

  • Develop backend prototype
  • Integrate into Āhau
  • Develop UI
  • Develop API
  • Develop backend modules
  • Develop techincal documentation
  • build cardono into mobile app (EXTRA)
  • Node-js-mobile environment
  • build pilot installers
  • Run internal testing
  • Internal testing with team and our team tribes
  • Small adaptations of UI
  • develop process for legal compliance
  • Identify and model the relevant sections of the Digital-identity-services-trust-framework-bill
  • Analyse compliance challenges between the bill and Tribal DID’s processes.
  • Document the compliance challenges and communicate that to:
  • Tribal partners
  • Ahau project development team
  • The Government drafting teams

<u>Phase three: Piloting</u>

3 months Apr – Jun

  • Pilot use cases
  • Use case one: trusted by tribes
  • Tribes can issue VC’s to verified members
  • Tribal members can present VC’s to a relying party
  • Related tribes accept tribe issued VC’s a recognised source of identity
  • Use case two: trusted by Government
  • Government can accept tribe issued VC’s a recognised source of identity
  • Government can issue VC’s to tribal members
  • Use case three: trusted by industry
  • Industry partner can accept tribe issued VC’s a recognised source of identity

<u>Phase four: Deployment</u>

3 months Jul – Sept

  • Wallet features will be published application wide
  • User guides and videos will be developed to support use and feature onboarding and communicate the potential use cases for Māori communities
  • Application support will be provided for new uses

Please provide a detailed budget breakdown.

<u>Budget Summary</u>

Image File

<u>Comprehensive budget</u>

<https://clik.vc/didindigenoussovereignty>

Please provide details of the people who will work on the project.

Āhau NZ Ltd is a Māori owned and operated business in Aotearoa (New Zealand) building solutions by our people, with our people and for our people. Our team of developers have been working together on our distributed application for three years.

The team also includes project managers responsible for coordinating project partners and team ensuring the project remains on track in alignment with the budget and timeframes; and, a pool of contract user research, design, testing experts and community educators who work closely with our communities to ensure the product is aligned with tribal custom, practice and authority.

The team is led by:

<u>Ben Tairea</u>

<https://www.linkedin.com/in/ben-tairea/>

Ben is Kaiwhakahaere/CEO of Āhau. He is also the Deputy Chair on the Executive Council of Digital Identity New Zealand. Ben is experienced with the product and community development required to deliver on the project and the Digital Identity requirements and environment for which this solution will need to land to be a recognised identity solution in Aotearoa (New Zealand).

He is Project Lead and Product Owner responsible for the overall development and UX/UI design along with the implementation of the product by the community and industry partners.

<u>Mix Irving</u>

<https://twitter.com/whimful>

Lead Developer for Āhau, and Technical Lead for this project Mix has been programming for 10+ years, with 6+ of those working on distributed systems and secure scuttlebutt. He is responsible for the technical design, development and integration with the existing application. Mix will lead the development team.

<u>Hamish Fraser</u>

<https://hamish.dev>

Rules-as-code developer for Digital Legal Systems Labs. Previous experience working in both Central and Local Government, researcher involved in the Legislation as Code report, funded by the New Zealand Law Foundation. Owner of Software development company Verb (20 years). Hamish is responsible for the analysis and design of the rules-as-code components, documenting the compliance challenges and communicating those to enable product development.

<u>Tom Barraclough</u>

<https://www.brainbox.institute/projects>

Co-founder and principal consultant at Brainbox, Tom works at the intersection of law, public policy and digital technologies. He has led multiple public interest research projects including the Legislation as Code project, funded by the New Zealand Law Foundation, and has co-founded the Digital Legal Systems Lab. Responsible for the compliance and integration of Government identity standards and the development of compliance tools to support identity processes. This role will also work with the Project Lead and Product Owner to develop recommendations and advocate for any required changes to standards.

If you are funded, will you return to Catalyst in a later round for further funding? Please explain why / why not.

Yes, identity is just the first step in self-determination/self-governance for Māori and other indigenous communities.

We would like to integrate with DAO governance and finance systems in the future and think that the Cardano ecosystem could provide the tools, resourcing and systems to support these future objectives.

Please describe what you will measure to track your project's progress, and how will you measure these?

<u>Phase one: Discovery and Design</u>

Milestones

  • Confirm team and project partners
  • Outcome
  • Team agreements in place
  • Partner agreements in place
  • Responsibility
  • Project manager
  • Method of sharing
  • We will provide a project update in the townhall
  • UX designs for identity processes
  • Outcome
  • design diagram for DID exchange with tribes
  • design diagram for DID exchange with Government
  • design diagram for DID exchange with industry
  • Responsibility
  • Product owner
  • Method of sharing
  • Designs will be shared via our repo
  • UI wireframes
  • Outcome
  • Application designs for issuing DID’s
  • Application designs for the storage and management of DID’s
  • Application designs for the receipt of VC’s
  • Application designs for the verifying of VC’s
  • Application designs for the sharing of VC’s
  • Application designs for viewing the history of VC’s
  • Responsibility
  • Product owner
  • Method of sharing
  • Designs will be shared via our repo
  • Identity compliance research
  • Outcome
  • Report on the Bill with recommendations
  • Responsibility
  • Rules as code and Legal Lead
  • Method of sharing
  • Report will be available via the project repo
  • Technology research
  • Outcome
  • AtalaPrism Developer Pioneer programme participation
  • Technology specifications and designs
  • Responsibility
  • Technical lead
  • Method of sharing
  • Via the project repo

<u>Phase two: Development</u>

Milestones

  • Develop backend prototype
  • Outcome
  • CLI application prototype using for issuing, sending and verifying DID’s
  • Responsibility
  • Technical lead
  • Method for sharing
  • Via the project repo
  • Integration into Āhau DApp
  • Outcomes
  • Develop frontend components
  • Develop API
  • Develop backend modules
  • Develop technical documentation
  • Responsibility
  • Technical lead
  • Method for sharing
  • Via the project repo
  • Build pilot installers
  • Outcomes
  • Create separate installers for pilot teams
  • Responsibility
  • Technical lead
  • Method for sharing
  • Available via the project repo
  • Develop process for legal compliance
  • Outcomes
  • Expression of compliance rules in a Rules-as-code format
  • Responsibility
  • Rules as code and Legal Lead.
  • Method for sharing
  • Available via the project repo

<u>Phase three: Piloting</u>

Milestones

  • Deliver pilot use cases
  • Outcomes
  • Deliver pilot for use case one: Recognised DID’s between tribes
  • Deliver pilot use case two: Recognised DID’s with Government
  • Deliver pilot use case three: Recognised DID’s with industry partners
  • Responsibility
  • Project manager
  • Method of sharing
  • For each pilot a report will be written up defining the outcomes. These will be available via the project repo and Ahau website.

<u>Phase four: Deployment</u>

Milestones

  • Wallet features will be published application wide
  • Outcomes
  • DID wallet feature will be available in public DApp by all tribal communities and members
  • User guides and videos will be developed to support use and feature onboarding
  • Responsibility
  • Product owner
  • Method of sharing
  • Via the DApp and project repo and website

What does success for this project look like?

  1. Tribal communities in Aotearoa (New Zealand) will have the ability to issue Tribal DID’s that can be recognised by Government, institutions and organisations as an authoritative source of identity.
  2. Indigenous peoples around the world can also have their human rights honoured and do the same.

Please provide information on whether this proposal is a continuation of a previously funded project in Catalyst or an entirely new one.

This is an entirely new project.

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3m 24s
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4m 3s
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3m 48s
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2m 16s
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3m 14s
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3m 19s
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4m 59s
    Darlington Kofa
0:00
/
~0:00