LogoLogo
Our WorkHelp CenterAbout Us
  • Developer Resources
    • ⚙️Web/HTML Implementation
      • Getting Started
      • Simple HTML Example
  • Native App Implementation
  • 🛠️API Resources
    • Verify
    • Claim
    • Recover
    • Tag Verifications
  • Protocol
    • 🖼️Overview
      • Technical Specs
    • 📜Smart Contracts
      • 🔓Locking Mechanism
      • 🔓Locked721
      • 🔑Access Control Roles
      • 📃Customizing the Locked721 Contracts
    • 📏Customizations
      • 🛳️Blockchain Deployment Options
      • 🪙Digital ID Options
      • 🗞️Product Metadata Options
      • 🔐Locking Mechanism Options
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Protocol
  2. Customizations

Blockchain Deployment Options

PreviousCustomizationsNextDigital ID Options

Last updated 10 months ago

Was this helpful?

Smart contracts can be deployed by Legitimate or by third parties. The primary reason to deploy your own smart contracts is if you want to make sure that the contract owner and deployer name on third party platforms properly reflect your own entity (i.e. Opensea).

Prerequisites

In the case of third party deployments, Legitimate's blockchain address (legitimatetech.eth on my EVM compatible blockchains) will need to be assigned the in order to perform unlock and claim functionality for our hosted services.

If token recovery and ownership reset is desired for processing returns or managing resales, the should be assigned as well.

📏
🛳️
API_DELEGATE_ROLE
TOKEN_RECOVERY_ROLE