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.