ers-scripts

Scripts for deploying and interacting with the Ethereum Reality Service ("ERS") from the command line.

Introduction

ERS scripts can be used by all parties in ERS including Manufactures, Developers, Service Creators and End Users wishing to transfer associated chip PBTs.

Developers who wish to enroll chips in order to redirect them -- with or without the addition of contents -- should first create a Developer Registrar, then a Service and finally a Project. Depending on the type of Project you wish to create as a Developer, you may need to generate a custom CSV that maps metadata -- like images, names and descriptions -- to chips. If you are simply looking to redirect chips that are already mapped to ERS, you can probably skip this.

The primary ERS deployment lives on Base and we recommend testing on Sepolia (see Deployments). See the ERS docs for more information on ERS. See also ers-contracts for the latest ERS contracts.

Setup

1. Clone ers-scripts repo, install dependencies and build artifacts:

git clone https://github.com/arx-research/ers-scripts.git
cd ers-scripts
npm install yarn --global
yarn
yarn build

2. Set up an .env file:

cp .env.default .env

3. Fill out the REQUIRED fields in .env. You need:
   • A Supabase account in order to access Arx manufacturer enrollments,
   • A Filebase account in order to create tokenUri data for projects and upload content (may not be required in all cases, but highly recommended)
   • An Alchemy account to carry out RPC commands (or you can set up a custom RPC in hardhat.config.ts).
   • Private keys for the different roles, e.g. Developer and Service Creator. Make sure the associated accounts are funded to cover contract deployment and calling contract functions (e.g send some ETH on Sepolia or Base depending on where you will deploy to)

Note: ers-scripts expects you have git,node and the yarn package manager installed.

Using Scripts

ERS Scripts can be used by various participants including Manufacturers, Developers, Service Creators as well as end users. In most cases, Developers are seeking to add chips to the protocol and link them to Services they have created. This will involve creating a service, deploying a developer registrar (if they have not previously done this) and creating projects.

If using ers-scripts on localhost (not usually recommended, typically Sepolia is best for testing), see ManufacturerUsage.md for more details on creating a mock manufacturer and enrollment and review the Local Setup section below.

Typical Flow

1. Create a service: createService with the options indicated below. A service is the contentApp that you want to redirect a chip to (e.g. a decentralized app hosted on IPFS, a centralized app hosted at a URL).
2. Create a developer registrar: createDeveloperRegistrar claims a name (if available) and deploys an associated developer registrar through which projects can be deployed and chips added.
3. Create a project: createProject maps chips to a serviceId and adds associated tokenUriData (recommended, but optional). Once enrolled, the chip should redirect when tapped to the contentApp provided. Some content apps may be designed to render the tokenUriData.
4. Claim a chip: transferToken allows the end user of a chip to claim ownership of the associated chip PBT, which may or may not be necessary depending on the end use case.

Note: scripts build on each other, each step creating artifacts in task_outputs that can be easily selected for use in the subsequent steps. You may wish to backup task_outputs periodically as some artifacts, such as those used for building tokenUri data, may be difficult to rebuild from scratch if removed.

createService

This script creates a service that can be assigned to chips in the project enrollment process.

It will prompt you for several pieces of information:

1. service-name: The name of the service
2. content: URL/URI of the content app; in the case of a simple redirect this would be an http resource like https://app.arx.org where a chip may be scanned. For IPFS, this would be
3. append-id: Indicate whether chipId should be appended to the content app URL/URI. This is useful for NFT/PBT applications where every chip might reference unique metadata and required if you are using the output of the generateTokenUriData for tokenUri data in your project. Note this doesn't influence chip parameter data, e.g. https://app.arx.org?$chipInfo, which is passed regardless.

Arguments: network: The network you want to interact with (sepolia recommended for testing)

Example:

yarn createService --network [network]

Note that the resulting serviceId will be printed in the console as part of a successful transaction.

createDeveloperRegistrar

This script creates your named developerRegistrar in the .ers namespace (e.g. brand.ers).

It will prompt you for your desired developer name.

Arguments: network: The network you want to interact with (sepolia recommended for testing)

Example:

yarn createDeveloperRegistrar --network [network]

Note: Most common names are reserved, and if not reserved a name will be checked to match the enrolling developer address with the ENS owner address. If you would like to enroll using a reserved name, please contact [email protected] -- note that trademarks, well known brand names and domain history are all factors that will be considered when requesting a reserved name.

createProject

This script creates a project and enrolls chips in the project.

It will prompt you for several pieces of information:

1. Whether or not you wish to create a new project or add chips to an existing project; if you select an existing project, artifacts in task_outputs will be used to suggest options or you can manually enter the address of an existing project. (both cases will be chain specific based on the network argument)
2. How you would like to add tokenUri data: via a formatted CSV, using an existing URL, or skip. (this can be updated after contract deployment)
3. If you are on localhost, you will be prompted to select a manufacturer enrollment as well. For other chains this information comes from the hosted Arx enrollment data on Supabase.

You will be prompted to scan a QR code on your NFC-enabled smartphone; scan the QR code on your smartphone and follow the prompts to capture chip proof data. You can scan your chip by tapping it to the NFC reader on the back of your smartphone. Currently this script does not support 2021 Edition HaLo chips (Edition 23+ should work).

Arguments: network: The network you want to interact with (sepolia recommended for testing)

Example:

yarn createProject --network [network]

Note: If you are creating tokenUri data from a formatted CSV, make sure that you backup task_outputs. When chips are added to an existing project, task_outputs will be used to ensure that metadata from previously added chips is included in the final tokenUri data. If this data is missing, metadata with previously enrollment chips will be overwritten and their tokenUri will not resolve when looked up.

See example/tokenUriExample.csv for an example of how the CSV should be formatted. Note that in the example the minimum required fields have been completed; other fields will be dynamically added. Notes is for reference purposes and is not included when the tokenUri data is generated.

transferToken

This script transfers ownership of a chip that has been enrolled in a project.

You will be prompted by a QR code scanner to scan the chip to get the chipId and to create a transferToken signature. Scan the QR code on your smartphone and follow the prompts to capture chip data. You can scan your chip by tapping it to the NFC reader on the back of your smartphone.

Arguments: network: The network you want to interact with (sepolia recommended for testing)

Example:

yarn transferToken --network [network]

Troubleshooting

ers-scripts assumes prior knowledge of using a CLI interface as well as installing and managing software packages like node. Typically errors will occur in several cases:

• An incorrect environment varaible (e.g. bad API key, extra or missing character)
• An incorrect version of node (see package.json for the version requirements under the engines section)
• You are attempting to deploy to a non-existant network (note network names are case sensitive)
• You are attempting to run ers-scripts from the wrong directory
• You have insufficient ETH on the account you are trying to use to carry out an action (e.g. createService)
• The name you wish to register as a Developer is already taken
• The tokenUri input file you are using is incorrectly formatted

Visit the ERS Discord for further assistance or open an issue.

Deployments

See deployment artifacts in deployments/$CHAIN_ID for live contract addresses. Sepolia is currently the primary testnet deployment and Base the primary production deployment.

Concepts

1. Developers create a registrar in order to establish their place in the ERS namespace; for instance, Arx Research owns the arx.ers namespace and can deploy Projects within that namespace through their developer registrar.
2. Services are typically a web app or URI; the URI is updatable, however, once a chip is bound to its primary service only a user can change that primary service to another one (and only then after the lock in period expires). Most developers will deploy their own Service, but some may choose to redirect their chips to a pre-existing service managed by another Service Creator.
3. Projects bind chips to Developers and Services. They exist within a developer namespace, for instance tshirt.arx.ers. They allow rich content to be tied to chips in conjunction with a Service, and also will set the initial owner of a chip upon creation (by default ERS sets this to the Developer embedding a chip).

Local Setup

First, instantiate your localhost chain:

`yarn chain`

The localhost network should now ve running on the default port, 8545.

Next, deploy the ERS protocol on the localhost chain:

yarn deploy:localhost

The deployment script will try to reuse the existing deployment and run any deployments that were not run before. To see if there is an existing deployment for your environment you can check the deployments folder. If there is a sub-directory with the name of your environment, then there is an existing deployment.

If you want to make sure that you have a completely fresh local deployment, run:

yarn deploy:localhost:clean

Local Manufacturer Simulation

If you want to simulate adding Arx manufacturer enrollments which is necessary for a full local deployment, you will need to set up enrollments using the addManufacturerEnrollment task matching the Arx signers used to date (this data may also be retrieved by looking up a given chip ID in the public Supabase):

1. 0xeBC369ed2340fd2EB2391Aca09a6274997722aac
2. 0xaF98D82397e832A5945424648511886c15A61f36

See ManufacturerUsage.md for more information. The default options provided in the script for auth model and enrollment auth model should match HaLo chips and the Arx Supabase data.

Local Contract Development

Note: If you are working with locally modified ers-contracts you may need to link those contracts and rebuild in order to correctly redeploy.

1. npm link @arx-research/ers-contracts --force
2. yarn clean-artifacts
3. yarn build