Passport SDK v8
  • Overview
  • Account Lifecycle
  • Integration
    • Client Side Enablement
    • Credenza Presence (Optional Visual Elements)
    • Account Provisioning (Sign-up)
      • New Authentication System
      • Existing Authentication System - New Customer
      • Existing Authentication System - Existing Customer
  • Passport Subsequent Logins
  • Post-Login Capabilities
    • Account Information Access
    • Blockchain Wallet Access
  • Smart Contract Interactions
    • Instantiating The Contract Object (Server-Side)
    • Instantiating The Contract Object (Client-side)
    • Calling Contracts
  • Monetary Transactions
  • Appendix I: Passport Configuration Options
    • Credenza Core Web SDK (Auth)
    • Ethers.js
    • Installation
    • Usage
    • Passport Instance Properties
    • Passport Static Properties
    • Modes
  • Appendix IA: Transaction UI v3.0 (now part of Passport)
    • Installation
    • Usage
    • Apple Pay
    • Google Pay
    • Methods
    • Events
  • Appendix II: MetaMembership Contract Access
  • Appendix III: Ledger Contract Access
  • Appendix IV: Decentralized Commerce Configuration
  • Appendix V: Migration From Previous Passports
Powered by GitBook
LogoLogo

©2023 Credenza. All rights reserved.

On this page
  1. Post-Login Capabilities

Blockchain Wallet Access

Additionally, a web3 provider from the ethers library is generated, enabling participating websites to authorize blockchain transactions on behalf of users. Ethers, accessible at https://docs.ethers.io/v6/api/, offers a robust JavaScript abstraction of the blockchain. When combined with Credenza's libraries, it simplifies smart contract interaction to the level of any JavaScript library.

However, preceding Ethers, several native methods are available to query wallet assets and attributes directly, bypassing smart contract interaction. For instance, Passport features a method called getNFTs, designed to retrieve all NFTs owned by a wallet. In the context of token-gating, confirming NFT ownership can be invaluable for granting access to digital content or physical spaces.

Furthermore, Credenza manages a standard ERC20 utility token named CRED, serving as stored value (distinct from speculative cryptocurrencies). Invoking getTokens exposes all ERC20 tokens, including CRED, held by the logged-in user.

PreviousAccount Information AccessNextSmart Contract Interactions

Last updated 1 year ago