pal-docs
  • Abstract
    • What is PAL
      • Social Relevance of Phygitality
      • Phygital Abstraction Conceptual Framework (PACF)
        • Primitives
          • Phygital Object
          • LINK
    • PAL Overview
      • PAL Network Architecture
        • Common Architecture Flow
      • Phygital Entity Providers (PEPs)
        • Phygital Entity Register (PEPRegistry)
      • Phygital Entity Agent (PEA)
        • PEA Process Overview
        • Issuing New Entity
    • Phytgital Services
      • Phygital Object Resolution as process
      • Default Phygital Resolution
        • PAL NFC Resolution and Validation Process
        • Off-Chain Data Fetching
        • Resolution Data Encoding
        • Resolution States
      • Reverse Phygital Resolution
  • Core protocol
    • PAL Contracts
      • PAL Agent Register Contract
      • PAL Entity Registry Contract
  • Enhansion
    • Additional Use Cases: Phygital Abstraction Layer Enhansion
      • Phygital Authentication
      • Advanced Resolvers
      • Gasless Phygital Resolution
      • Multichain Address phygital resolution
      • EVM compatible Chain Address phygital resolution
  • Application
    • PAL Guidlines
      • Front-End Design Guidelines
      • Guide for DApp Developers
      • Deployment Guidelines
      • Layer 2 & Offchain Resolution
Powered by GitBook
On this page
  1. Abstract
  2. Phytgital Services

Default Phygital Resolution

Overview of PAL Resolution for NFC Chips

The PAL system ensures that all NFC chips can resolve to a service, be it an IPFS-based app or a standard web app. The resolution process involves two main steps:

Step 1: Verify NFC Chip Registration

Validating NFC chip registration in PAL involves several key pieces of data:

Data Category
Description

Project Merkle Leaf Data

Includes the Merkle leaf index, chipId, enrollmentId, lockinPeriod, serviceId, and tokenUri.

Project Merkle Proof

Validates the NFC chip's position in the project structure.

PEA Certificate

Authenticates the NFC chip's registration.

Custody Proof

Confirms the NFC chip's possession status.

Manufacturer Merkle Proof

Confirms the NFC chip's origin.

Due to the volume of data required for validation, storing it all on-chain is impractical. Instead, it's stored off-chain to ensure cost-effectiveness and data integrity.

Step 2: Return a Service Address for the NFC Chip

Returning a service address is simpler as it's a small data set, easily managed and stored on-chain through the ServiceRegistry. This address allows services to connect directly to the validated NFC chip.

PreviousPhygital Object Resolution as processNextPAL NFC Resolution and Validation Process

Last updated 7 months ago