This EAS proxy will be the attester who will write the stamps into EAS attestations

See latest contract addresses and other deployment info—organized by chain ID—here.

• Optimism (0xa)
• Base Goerli (0x14a33)
• Linea Goerli (0xe704)
• Linea (0xe708)

The file has the following schema:

Fields marked with a pencil (✏️) are manually filled out, the rest are populated by scripts

{
  "[chainId]": {
    "issuer": {
      "address": "[✏️ test or production issuer address (see below)]"
    },
    "EAS": {
      "address": "[✏️ address of the EAS contract]"
    },
    "GitcoinAttester": {
      "address": "[address of the GitcoinAttester contract]"
    },
    "GitcoinVerifier": {
      "address": "[address of the GitcoinVerifier contract]"
    },
    "GitcoinResolver": {
      "address": "[address of the GitcoinResolver contract]"
    },
    "easSchemas": {
      "passport": {
        "uid": "[✏️ uid of the Passport EAS Schema]"
      },
      "score": {
        "uid": "[✏️ uid of the Passport score EAS Schema]"
      }
    }
  }
}

These are the addresses signing attestation data, the verifier only accepts attestations signed by the appropriate address.

The production address is used only in the production environment of the Passport app with mainnet chains. The testnet address is used with all other environments.

0x804233b96cbd6d81efeb6517347177ef7bD488ED

0x5f603Ed913738d9105bAf3BD981AA4750016B167

Note: the issuer address is not the attester address

Section 0: Onchain Data Overview

Section 1: Onchain Passport Attestation

Section 2: Onchain Stamp Attestation ⚠️ not used ⚠️

Section 3: New Chain Deployment Process

Section 4: Deployment with Verax

Section 5: Querying Passport Attestations Onchain

Section 6: Scoring Attestations Onchain