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. PAL Overview
  3. PAL Network Architecture

Common Architecture Flow

This page outlines the Common Architecture Flow within the PAL network, detailing the key processes and interactions among network participants.

Common Flows

The PAL network architecture outlines key processes involving the issuance, integration, tracking, and interaction with NFC-enabled phygital objects. Here's an overview of the common flows:

  1. Issuance and Distribution of NFC Chips: Phygital Entity Providers (PEPs) produce and register NFC chips within the PAL protocol before distributing them to Phygital Entity Agents (PEAs).

  2. Integration and Minting of NFC Chips: PEAs receive NFC chips from PEPs, embed them into physical objects, and mint these chips, registering the objects within the PAL protocol.

  3. Ownership Tracking and Management: Phygital Object Owners acquire NFC-enabled objects, using the PAL network to verify authenticity and track ownership, which updates in the protocol as objects change hands.

  4. End-User Interaction and Experience: Service Consumers interact with phygital objects via NFC-enabled devices, triggering digital experiences such as content access and authenticity verification, blending the physical and digital realms seamlessl.

Flow
Steps

Issuance and Distribution of NFC Chips

- PEP produces NFC chips.

- PEP registers NFC chips in the PAL protocol.

- PEP distributes NFC chips to PEAs.

Integration and Minting of NFC Chips

- PEA receives NFC chips from PEP.

- PEA embeds or attaches NFC chips to physical objects.

- PEA mints NFC chips, registering the physical objects in the PAL protocol.

Ownership Tracking and Management

- Phygital Object Owners acquire physical objects with embedded NFC chips.

- Phygital Object Owners use PAL network to verify authenticity and track ownership.

- Ownership and possession details are updated in the PAL protocol as objects change hands.

End-User Interaction and Experience

- Service Consumers interact with phygital objects using NFC-enabled devices.

- Scanning the NFC chip triggers a digital experience:

such as accessing exclusive content

or verifying authenticity.

- Service Consumers enjoy a seamless integration of the physical and digital worlds facilitated by the PAL network.

PreviousPAL Network ArchitectureNextPhygital Entity Providers (PEPs)

Last updated 5 months ago