PAL Overview
This section provides an overview of the Phygital Abstraction Layer (PAL), a distributed and extensible phygital system based on smart contracts and middleware.
The Phygital Abstraction Layer (PAL) is a distributed, open, and extensible phygital system based on a set of smart contracts and middleware. It allows for the seamless integration of physical and digital experiences, providing unique phygital interactions for users.
Using PAL Services, users can:
Track the custody history of the chip embedded in their product, ensuring that they are holding verified merchandise.
Utilize a registry and resolution service that enables decentralized authentication, claims, and redirection for secure chips.
Brands can easily push new content to their chipholders, enhancing user engagement and providing updated information or exclusive experiences.
By leveraging PAL, users and brands benefit from a secure, transparent, and dynamic way to manage and interact with phygital objects.
The PAL is designed not just to connect the physical and digital sides in a single entity, but to make such a connection regular and publicly available. For this purpose, it should provide the infrastructure for producing phygitality together with the ecosystem built over it.
Clarify them below. Here are several levels, each with its own operation.
Start with the most general one.
1. What registers all entities involved in the protocol, or Phygital Entity Register (PER), which:
- defines the rules for connecting and disconnecting the nodes;
- sets the logic for processing phygital transactions they perform;
- contains a complete list of all phygital objects, their resolvers*, creators, and current owners;
* Resolver attaches the digital component (i.e., the blockchain address) to a physical object, and can be a smart contract or phygital bridge.
2. What sources the blank chip, or Phygital Entity Provider (PEP):
- orders the chips from the factories;
- controls their security and guarantees their compatibility with PAL services;
- supplies them to the creators of phygital objects;
- ensures their functionality in the respective projects deployed on the protocol.
3. What creates a phygital object, or Phygital Entity Agent (PEA):
- runs a separate domain on the protocol for its projects;
- specifies permissions and functional conditions for them;
- programmes and embeds chips in its phygital objects;
- distributes the latter to end users;
- tracks the history of transactions with them;
- takes charge of the user experience;
Last updated