Upgrade Library / Package Manager:

What is this?

This is an app whose purpose is to be an onchain upgrade library for diamond proxy contracts. With the app, users can deploy a new diamond, register an existing compatible diamond, and commit their diamondCut params as an Upgrade Package that can be easily reused by other registered diamonds. In the future, each package will also contain an optional front-end component / app that can be used on a diamond's homepage.

WIP: This project is continuously being worked on! That's the beauty of upgradeability :)

DEMO: https://odysee.com/@tjvs:9/0xpm-demo:a

Run the app:

1. start ganache: use the GUI and start a workspace with the following "server" settings...

2. start IPFS: use IPFS desktop to automatically run an ipfs node. This is only needed for pushing contract metadata to ipfs in the deploy.js script.

3. generate ABIs, address map, and dummy data into svelte project via:

cd hardhat && yarn && npx hardhat test

... abis will be generated via: hardat-diamond-abi and abi-exporter plugins. You may also turn off ipfs desktop now if desired.

4. start front-end:

cd web && pnpm i && pnpm run dev

---

[Legacy] OnTap Contracts - A Diamond for Storing Upgrade Presets

This is a simple WIP / concept project and there are no immediate plans other than testing, simplifying, and optimizing the contracts further. OnTap is the diamond name we will use for this example. This readme is more digestible if you have some familiarity with EIP2535 and the Solidstate contract library.

The Upgrade contract -- storing a package --

Each upgrade package is an external contract address that stores data in the format of a standard diamondCut ( ( address[], uint8, bytes4[] ), initializerAddress, initializerFunction ). A package can be installed and then uninstalled. The below image is a simplified version of this contract, which just implements a get() and set() functions. Please check out the 'external' folder for more info on the Install / Uninstall design.

Storage - A basic data structure

Moving on from the external Upgrade.sol storage contract; the main Storage library contract contains a solidstate compatible storage layout with some internal functions for easy access.

The logic

The logic folder contains the two main facets and a library for sharing code between modules...

Git contract

Git / IGit is the native facet of OnTap. It is the main access point for reading and writing upgrades and presets to this Diamond's storage.

Looking at the code: You can see that upon deployment, an address for the Upgrade.sol model is stored immutably. This address can then be used for cheaply deploying minimal proxies (storage contracts delegating calls to a single logic implementation), as seen in function commit(...).

PackageManager contract

PackageManager / IPackageManager is a diamond cutting facet which integrates itself with Git. It is to be used by other diamonds.

Looking at the code: Upon deployment, it stores the Diamond immutably so that our Diamond's git system can be accessed from other diamonds if they've connected this contract as a facet. It has 2 externally available methods for upgrading a diamond...

1. function install(..): install the upgrade package at account owner's name.
2. function uninstall(..): uninstall the upgrade package at account onwer's name.

Internal Library contract

The Library contract contains the internal functions that all upgrades can use. These internal functions can be shared among decentralized decision-making modules. For example: when Governance.sol calls executeProposal(..), it calls the Library._execute(..) internal function, sending through its 'proposalContract' (a minimal proxy of Upgrade.sol) to make the upgrade. Additionally, since a diamondCut(..) function can perform arbitary operations via its 2nd and 3rd params initializerAddress, initializerFunction, this method can also do things like mint new tokens, or add/remove/update any data in your diamond.

The OnTap Diamond

In the main diamond, most of the work is done in the constructor. The workflow of adding each facet can be found in the deploy script. The important bit is; Writable.sol is deployed in the constructor, because it has to store the diamond's address(this) via its own constructor.

The User's Diamond

The user's diamond is a lightweight, simplified solidstate diamond that accepts cuts in its constructor, so that it can use existing facets on deployment.

These contracts have not been thoroughly tested yet, but when they do, the contracts may change slightly.

Extra notes:

• The _library folder can be largely ignored, with the exception of its governance folder. It just contains any modules that can work with the OnTap diamond.
• The init folder contains the upgrade initializers. These contracts can perform arbitrary operations on the diamond via the diamondCut(..) 2nd and 3rd params initializerAddress, initializerFunction.

---

Basic Sample Hardhat Project

This project demonstrates a basic Hardhat use case. It comes with a sample contract, a test for that contract, a sample script that deploys that contract, and an example of a task implementation, which simply lists the available accounts.

Try running some of the following tasks:

npx hardhat accounts
npx hardhat compile
npx hardhat clean
npx hardhat test
npx hardhat node
node scripts/sample-script.js
npx hardhat help