Bringing Identity.com's Gateway Protocol to Harmony

Funding Proposals Grants
1

Name of Project

Gateway Protocol Migration to Harmony.one

Proposal overview

Identity.com’s vision is to create the most powerful and frictionless developer tools and protocol to perform decentralized identification.

The Gateway Protocol is a cross-chain oracle token model that enables any application operating on a decentralized ledger (such as a dApp) to add a permissioning layer that adheres to a set of pre-specified requirements.

This is achieved by requiring the presence of a specific and active Gateway Token (GT), which represents the adherence to predetermined requirements and is issued by one or more Gatekeepers belonging to a Gatekeeper Network. Gatekeepers issue Gateway Token’s to users after verifying that they satisfy the given requirements of the Gatekeeper Network. Examples of requirements include liveness, age, country of residence, IP address, investor status, and others.

Gatekeeper Token contracts can be deployed on any compatible chain, allowing integration on a wide range of blockchains and applications. Currently, the project is live on Solana.

We are currently deployed on Solana, and Civic is using this for their KYC and Bot protection services.
We are requesting $150k to start and complete the effort. We have four key milestones, as seen below:

  1. Migration of Gateway Protocol Program to EVN compatible Smart Contract.
  2. Tooling and Deployment on Harmony.one.
  3. Gateway Token Payment Design & Implementation on Harmony.one
  4. Smart Contract Security Audit (in-House / with Harmony.one)

Proposal ask

$150,000

Metrics for success

  1. Migration of Gateway Protocol Program to EVM compatible Smart contract.
    The following functionality will be ported in detail:
    a. Adding, Changing & Removing Gatekeeper Networks (or the properties of)
    b. Adding, Removing Gatekeepers from Networks (Token Issuers)
    c. Issue, Refresh, Freeze, Unfreeze, Expire, Revoke Gateway Token as Gatekeeper
    d. Verifying Gateway Token

  2. Tooling and Deployment on Harmony.one
    a. Getting familiar with Harmony.one Tooling (e.g. upgradability options, proxy contracts).
    b. Getting familiar with Harmony.one Environments
    c. Deployment of the Gateway Protocol to Harmony.one Testnet & Mainnet

  3. Gateway Token Payment Design & Implementation on Harmony.one.
    a. Measure token operations on Harmony.One in order to register Token Usage on-chain (possible third-party)
    b. Document settlement options for third parties.

  4. Smart Contract Security Audit (In-House / with Harmony.one?)

Metrics for success include the following:

  1. Gateway Protocol smart contracts operating on Harmony.one
  2. Rollout of at least one Gatekeeper Network (for KYC/AML)
  3. Integration of at least one Gatekeeper within the network (Civic?)
  4. Integration and support of at least one project as Harmony as a Gateway Token validator.

Level of Effort
Milestone 1: Migration to EVM Contract & Gateway Token Operations: 26 days, 2 resources, $43,680
Milestone 2: Deployment: 16 days, 1 resource, $13,440
Milestone 3: Design and Development of On-Chain Payment Option for Gateway Tokens on Harmony.one: 30 days, 3 resources, $75,600
Milestone 4: Smart Contract Security Audit: 10 days, 2 resources, $16,800

External links

1 Like
2

Thank you for working with us over the last few weeks and submitting a proposal to Harmony’s $300M Ecosystem Fund. @HarmonyUniverse and myself will be your representative.

We are in the process of reviewing and carefully scoping this proposal to fit the Harmony use case. We would also love :blue_heart: to have the Harmony community participate to ask questions and provide feedbacks.

3 Likes
3

Circling back here to have transparency in our discussion, the proposal here was due an outbound request from Harmony to Civic / Identity team. Harmony was originally looking for an Identity and/or KYC solution for ecosystem builders on Harmony. Upon discussing further with the Identity (and Civic) teams, we realized that there’s a fit for the grant use case at Harmony.

This revised form of the proposal is geared to enable a more integrated identity and KYC solution, starting with the integration into the grant orchestration of Harmony. We are working on gaining closure on this initiative to get an on-chain solution for KYC/Identity into the flow of our grant orchestration.

This would require some front-end work. We are working with another vendor to get grant orchestration in place – grant applications, funneling into a database, automated responses, tracking, followed by approvals which will then need a KYC solution. This is where Identity/Civic comes in nicely. The above grant orchestration is still being developed, quite far along, and I can imagine Identity/Civic will be a great fit thanks to this partnership.

@Phillip_Shoemaker does this proposal comes with a basic UI that can help us kick things off without the grant orchestration system in place?

4

The key focus of the grant is to implement the Identity protocol, which delivers, mostly, the protocol. Civic, on the other hand, can more easily port to Harmony with an existing Identity protocol implementation. With just Identity, we would implement a key portion of the UI for the dApp, which shows if you are verified or not. But the UI for the interaction with the Gatekeeper (the validation service) would be handled by the respective Gatekeeper, in this case Civic. Then there also needs to be a custom Harmony UI to orchestrate their KYC flows, which would also be done by the Gatekeeper.

5

We currently do not have the capacity to create the KYC flows. Checking with Questbook at this time. They’re not onboarded with Harmony yet at this time

6

I think we can ultimately create an interim KYC flows for Harmony.

7

We’re awaiting a grant orchestration system to review Identity.com’s integration process