Phygital Entity Agent (PEA)

Overview

PEAs take custody of NFC chips from Phygital Entity Providers (PEP) and distribute these manufacturer-enrolled chips to end-users or other projects building on the PEA's infrastructure.

Adding a PEA

PEAs are added exclusively through governance. The process to add a PEA involves:

1. Initial Setup: The PEA commits to a PAL name, creating a [pea].pal subdomain to identify all its projects. All project PAL names follow the format [project].[pea].pal.

   • The chosen name and a _peaOwner address are provided to the addAllowedPEA function on the PEARegistry.

2. Deploy PEARegistrar: The PEA then calls createNewPEARegistrar, deploying a new PEARegistrar contract owned by the _peaOwner address. This contract manages the PEA's projects. During this call, the PEA selects an implementation of PEARegistrarFactory. Once deployed, the implementation cannot be changed. PEARegistrarFactories are permissioned implementations added only by governance.

Project Management by PEAs

After deploying their PEARegistrar, PEAs can start adding projects with two methods:

1. Direct Addition: PEAs can directly add projects with brands or companies they have veted by using addProject on their PEARegistrar from the owner address of their PEARegistrar contrac.

2. Delegate to a Managing Contract: PEAs may change the owner of their PEARegistrar to another contract address. This new owner manages permissioning and other requirements the PEA imposes on projects using its infrastructure. This managing contract can then use addProject on the PEARegistrar to add projects.