Galxe Passport combines encrypted identity credentials with a non-transferable token
- last updated
Galxe Passport is a non-transferable identity NFT that records completed identity verification for quests with a Passport Holder requirement. Its token stays with the wallet that receives it. Private identity information sits in a separate encrypted credential, while a holder check confirms possession of the NFT. Some quests also require a recent successful facial check. Participation depends on the precise credential condition, and Passport ownership does not complete a quest's other tasks.
In short: A recent-verification requirement depends on the successful facial-check timestamp, so holding the Passport NFT may not satisfy that condition.
Recheck the holding wallet before paying again
A quest that accepts Passport Holder status normally checks the wallet that owns the token. An unmet requirement calls for distinguishing an ownership mismatch from a request for newer facial verification.
Reading the requirement and comparing wallet addresses leave the Passport unchanged. These checks come before another paid verification or a revocation transaction.
- If the requirement concerns ownership, compare the participating address with the wallet that holds the NFT.
- If the addresses differ, establish the correct wallet connection without attempting to transfer the token.
- If the requirement specifies a recent facial check, compare its condition with the last successful verification timestamp.
- If a new facial check is necessary, review its charge before confirming payment.
- If revocation is under consideration, account for the reminting waiting period before authorizing deletion.
Checking the holding wallet incurs no verification charge. Facial re-verification carries a separate charge and, when successful, updates the verification timestamp. Repeating a holder check cannot refresh that timestamp. If facial re-verification fails, it leaves the timestamp unchanged. Quests that accept the existing verification remain available if their other requirements are met.
Token ownership, signed credentials, and identity proofs
The Passport NFT, the encrypted identity credential, and a zero-knowledge proof perform different jobs. The NFT records verification completion on BNB Chain. The credential contains identity claims that an issuer signs, allowing a verifier to authenticate their origin. A zero-knowledge proof can establish a selected condition without disclosing every underlying claim. The ownership record is public, and the identity claims are encrypted. Applications specify which form of evidence they accept.
Galxe credentials cover many kinds of activity. Passport supplies identity-related evidence within that broader system; quest participation can require additional credentials with different meanings.
Can a Passport token be transferred to another wallet?
A Passport token cannot be transferred to another wallet. The soulbound restriction applies to the NFT itself. Its ownership record associates the verification token with the receiving address, making an ordinary NFT resale or gift unavailable. A wallet interface that displays a send option does not override the contract's behavior. Authorization also does not provide a workaround: the contract rejects token approvals and operator approvals. The Passport NFT contract rejects calls to its public transfer functions.
Password encryption and the Private Data Vault
The Private Data Vault stores encrypted identity material and signed credentials separately from the public NFT. A user-selected password protects the credential, while the issuer's signature establishes its origin and integrity. Encryption limits access to the contents, while a valid signature lets a recipient authenticate the signed claims. The password is consequently part of data access, not a substitute for wallet ownership. Sharing decrypted identity information requires a separate consent decision from demonstrating ownership of the token.
The verification provider must process identity documents to assess them. The issuance process also involves retrieving verification information before client-side encryption. Protection of the stored encrypted credential therefore does not mean that no service ever processes personal information.
A Passport password protects identity data. A wallet's recovery phrase controls access to the wallet; the two secrets have different purposes.
What does a quest learn from Passport Holder status?
A Passport Holder check establishes that the NFT exists in the relevant wallet, without disclosing the holder's personal identity through that check. The token contains no personally identifiable information. Its public existence still identifies a wallet as holding a verification token, so this privacy boundary concerns identity contents, not invisibility of blockchain ownership. A quest's other requirements can concern separate activity or account information. Holding Passport satisfies the named ownership condition, while those additional requirements retain their own meaning.
Identity verification and duplicate-account resistance
Passport V3 onboarding uses a self-custodial wallet compatible with the Ethereum Virtual Machine (EVM), alongside identity documents and a selfie that Sumsub checks. Applicants must be at least 18. Identity verification is unavailable in Crimea, the Donetsk People's Republic, the Luhansk People's Republic, Cuba, Iran, North Korea, and Syria. Know Your Customer, or KYC, describes that identity-verification process. An approved document establishes information about its holder; the facial check helps connect the submission to the person completing verification. The non-transferable token then makes that completed check usable as a wallet credential. This combination supports resistance to Sybil activity, in which one participant presents multiple identities or accounts to obtain repeated access.
Identity verification introduces a dependency on the provider's assessment and the application's acceptance rules. A valid cryptographic proof authenticates a claim from its issuer; it does not independently establish the truth of every real-world fact. Likewise, a wallet's quest history does not replace an identity check. Choosing quests without a Passport condition remains an alternative when identity verification is unnecessary for the intended activity.
Verification timestamps and credential versions
Passport verification records include the first and most recent successful selfie checks, along with the successful-check count. Projects can use this information to require a sufficiently recent facial verification. A holder condition and a freshness condition therefore express different requirements. The V2.1 credential schema also includes document expiry, the time difference between initial and latest verification, and the most recent revocation time. Those fields belong to that schema; they do not establish a universal refresh schedule or an identical field layout for every later integration. Passport V3 retains facial re-verification and timestamped checks while using Sumsub for onboarding.
What determines the cost of keeping Passport usable?
Passport costs depend on initial identity verification, any paid facial re-verification, and the fee-waiver eligibility that applies to the account. A quest's freshness condition can create a need for another facial check. Payment settles the verification charge; successful verification determines the resulting credential state. Verification fees are non-refundable, including when an identity document is declined. The charge shown before payment matters because a paid submission can still fail review.
Galxe+ Premium and Unlimited include a Passport verification benefit, while Mini does not include a free Passport. The waiver covers one ID verification; subsequent ID verifications carry the standard fee. A subscription also has its own cost and conditions, so compare its eligible benefit with paying for the identity check alone.
Selective disclosure beyond token ownership
Galxe Identity Protocol supports proofs that disclose selected credential conditions, such as an age or identity-related attribute, to a verifier. The application chooses the condition and the trusted issuer, so proof compatibility and acceptance remain integration-specific. A request for decrypted identity data involves broader disclosure than a proof of one condition. Both can support an identity workflow, with different privacy consequences.
Reusable verification also requires an application that accepts it. Transak's integration with Passport V3 uses its KYC Reliance infrastructure to reuse verification information during onboarding. That integration illustrates a supported relationship, not universal acceptance by every application. Its workflow can pass a verification token or verified KYC data to the receiving service. An NFT ownership check alone does not describe that data-sharing arrangement.
Portability concerns reuse of accepted verification evidence. It does not make the Passport NFT transferable.
Revocation and wallet access limits
Revocation changes the Passport's status to revoked and introduces a waiting period before reminting. It is a consequential change, so it differs from correcting a wallet connection or completing a newer facial check. The revocation process requires authorization and a confirmed transaction before the dashboard shows revoked status. A submitted transaction alone does not establish completion. Changing wallets also leaves prior quest claims subject to their original account rules; reminting Passport does not recreate those claims. The wallet-bound credential remains separate from a project's quest history.
Galxe Passport: common questions
-
How many verification attempts are available before another Passport payment?
- Passport verification permits an initial attempt and one retry. If both fail, another payment is required to restart the process. A further payment does not ensure approval.
-
Is another identity document enough to obtain a second Passport?
- Alternative documents do not permit a second active Passport for the same identity. The restriction concerns the person, even when different documents contain that person's details.
-
How can a forgotten Passport password be reset?
- A Passport password reset requires identity checks, which can include facial re-verification or full verification. The first reset is free; subsequent attempts carry a fee. Resetting the password upgrades the account to Passport V3. The process restores access to encrypted identity data; it does not recover a lost wallet recovery phrase.
-
What can cause Passport verification to reject a readable document?
- A readable document can still be expired, invalid, incomplete, previously used with another wallet, or show suspected alteration. Image quality is one part of the verification assessment.
-
When does a pending Passport application count as verified?
- A pending application has not completed the required identity checks. Sumsub communicates the review outcome by email. Approval of both the ID and selfie is required before completing Passport creation.
-
Does the ID country in Passport V2.1 establish my place of residence?
- The V2.1 ID country field identifies the country that issued the identity document. It does not establish current residence or nationality. An application's geographical condition must refer to the appropriate attribute, rather than treating these different facts as interchangeable.
-
What is the credential type ID for Passport V2.1?
- Passport V2.1 uses credential type ID 10001 for its defined claim structure. This identifies a credential type, while a token ID identifies an individual NFT. The type ID applies specifically to V2.1 and does not establish the schema that every later integration accepts.