Walt.id | SIWE & NFT-based access management for web2 | Round 19

Project Name


Project Category

Build & Integrate

Proposal Earmark


Proposal Description

With this project we enable web2 companies or traditional applications to allow their stakeholders to access services with their wallets (via SIWE and Ocean Protocols data NFTs).

Our last project (Round 16) resulted in open source infrastructure (“NFT Kit”) that enables web3 service providers to make access to information, services, products or any other benefits dependent on the ownership of certain NFTs. In other words, it enabled the use of NFTs for authentication or even identification. This project (Round 19) will unlock wallet- and NFT-based access management and identification for a much broader group, namely for any web2 company building traditional / web2 applications. Moreover, we will offer a solution for implementing customizable verification policies to further enhance access management capabilities for target groups.

As a result, this project will extend our existing web3 authentication solutions with

* a protocol (“Sign in With Ethereum”)

* a component for bridging web2 and web3 (an OIDC-compliant Identity Provider, “IDP Kit”)

* a component for enabling customizable, machine-readable access policies.

which will provide legacy identity infrastructure with the ability to handle new web3 objects like wallets and NFTs.

At the end of the day, users will benefit from a seamless onboarding/sign up or authentication/login process for signing into any application with a one-click process based on their wallets and NFT. (Usernames, passwords, forms, uploads etc. will be rendered unnecessary.)

Grant Deliverables

(1) SIWE Library/Web Service: We will provide an open source library/web service (Apache 2) that implements Sign in with Ethereum (SIWE) in Kotlin to facilitate uptake by enterprises (who mostly use Java/JVM).

(2) “IDP Kit” Library/Web Service: We will provide an open source library/web service (Apache 2) that implements an identity provider (IDP) which will “sit between” traditional identity and assessment tools (e.g. KeyCloak) and web3 auth solutions (e.g. walt.id’s SSI Kit or NFT Kit). This IDP will then be able translate NFTs (and related verification results) into a token format that can be re-used by traditional tools.

(3) “Policy Engine” Library/Web Service: We will provide an open source library/web service (Apache 2) that implements a policy engine which allows developers to easily define customizable and machine-readable verification and access policies based on the “Open Policy Agent” (and REGO).

(3) Demo: We will provide a demo to showcase the project results (via command line and/or wallet)

(4) Documentation: Technical documentation of the project for developers.

Project Description

Walt.id offers developers and organizations an easy and fast way to adopt decentralized identity.All solutions are open source (Apache 2), based on open standards (W3C, DIF, OIDF, EBSI) and used by governments, public authorities and businesses across industries (e.g. banking and financial services, web3, education, HR, marketplaces):

  • SSI Kit for Issuers, Holders and Verifiers (incl. support for different types of keys, DIDs, VCs, data exchange protocols)
  • Wallet that enables developers to extend their (d)apps with SSI capabilities (Also, available for white labeling.)

Here also our website, documentation and GitHub.For more information visit our website or contact us.

Final Product

Growing portfolio of decentralized identity infrastructure solutions for developers and organizations.

Value Add Criteria

1. Usage of Ocean — how well might the project drive usage of Ocean. Measure with e.g. Data Consume Volume, # assets published, [TVL](https://www.nasdaq.com/articles/what-is-total-value-locked-2021-09-29), Network Revenue, # active users, # funded projects.

2. Viability — what is the chance of success of the project

3. Community active-ness — how active is the team in the community

4. Adding value to the overall community — how well does the outcome of the project add value to the Ocean community / ecosystem

Core Team

Dominik Beron

Role: CEO

LinkedIn: https://www.linkedin.com/in/dominikberon

Email: <dominik@walt.id>

Background: Serial entrepreneur with business and legal backgrounds.

Identity expert to the EU Commission and co-author of new EU identity standards (EBSI, ESSIF).

Philipp Potisk

Role: CTO

LinkedIn: https://www.linkedin.com/in/philipp-potisk

GitHub: https://github.com/philpotisk

Email: <phil@walt.id>

Background: Serial entrepreneur and experienced technical leader.

Over 15 years of experience in security and identity including biometric passports.

Severin Stampler

Role: Chief Architect & Engineer | Technical leader and developer.

LinkedIn: https://www.linkedin.com/in/severin-stampler-714605140

GitHub: https://github.com/severinstampler

Email: <severin@walt.id>

Background: Over 15 years of experience in computer science, software design and development (security, big data, AI/ML, …).

Fatima Beron

Role: People and Operations

LinkedIn: https://www.linkedin.com/in/fatima-beron-122a035b

Email: <fatima@walt.id>

Background: Serial entrepreneur, Ex-Deloitte Consultant, Former start-up COO, Forbes 30 under 30 (US, DACH).

Walid Khemiri

Role: Engineer

LinkedIn: https://www.linkedin.com/in/walid-khemiri-80324b144/

Email: <walid@walt.id>

Background: Experienced software developer in web3/blockchain space.


deltaDAO AG

Website: https://delta-dao.com

LinkedIn: https://de.linkedin.com/company/deltadao

GitHub: https://github.com/deltaDAO

deltaDAO AG will assist with knowledge-transfer within the Ocean and Gaia-X communities and regarding questions to the Ocean Tech Stack. deltaDAO AG will not receive any of the fundings raised within this proposal.

Funding Requested

Minimum Funding Requested

Wallet Address

Project Deliverables

Based on the partial funding (15k of 20k) we received for this grant we completed almost all the deliverables:

[X] SIWE Library
[X] “IDP Kit” Library
[X] Demo / Docs

The remaining / unfunded deliverables will be shipped if our new proposal (Round 21) is accepted:
[ ] Policy Engine

Project submitted deliverables:

Deliverable Checklist

Build / improve applications or integrations to Ocean

[X] Library/Web Service: We will provide an open source library/web service (Apache 2) that offers all functionality required for the verification of NFTs and access management.

[X] Wallet extension (MVP): We will extend our open source wallet with the ability to showcase and “present” NFTs for access management.

[X] Demo: We will provide a demo to showcase the project results (via command line and/or wallet)

[X] Documentation: Technical documentation of the project for developers.

All of these deliverables are published under the permissive Apache 2 license in our GitHub library: walt.id · GitHub.

We will further improve / add to this project - i.e. we will propose new related projects in future rounds.

Hi @walt_id, I’m reviewing your proposal for acceptance and I’m just a bit surprised there is nothing related to Ocean in the SIWE/NFT access management logic for Web2.

I really want to approve this so you guys can keep building but I’m seeing little to no implementation with the protocol’s stack. Something like supporting Ocean’s DataNFT in your library seems like a pretty low hanging fruit and something that I would expect based on your engagement with the protocol.

I’m waiting for an answer from the team before accepting the deliverables.

Hi @idiom-bytes, I fully understand that our current submission is hard to review. Let me explain:
First of all, my colleague who submitted the project ticked the wrong checkbox, so this is what we have completed:
[X] SIWE Library
[X] “IDP Kit” Library
[x] Policy Engine
[ ] Demo / Docs
The demo & docs are missing as we only were partly funded. However, without a demo & docs it is obviously hard to review what we implemented, specially in regard of the Ocean ecosystem.

In a nutshell, we have the implementation completed which allows the validation of Ocean data NFTs with the dynamic scripting language Rego (from the OpenPolicy engine). The Ocean data NFT integration is ready and documented here:

The usage of the Rego-based policies is demonstrated here in the scope of the Gaia-X Hackathon, where Ocean is also involved:

We are still planning to complete this last step “Demo & Docs” for providing a thorough documentation as well as a demo-use case, which will be presented in the Ocean Townhall. However, we would see this in the scope of a follow-up funding round as we only got partly funded this time.

What would you suggest the best way of going forward would be?
Thanks, Phil & walt.id team


Data NFTs (OceanProtocol) - Docs The Walt.ID team only got partial funding for the above proposal. This makes it tricky to fully judge their deliverables as it isn’t clear where the line would be drawm. However, they have added their implementation of Ocean’s Data NFTs into their docs with a strong explanation. Given this, I am moving to accept