This document extends Metalabel Protocol Walkthrough to elaborate on the changes and additions in V1.1.

<aside> 🌈 This walkthrough is intended to be shared with Metalabel’s friends and neighbors, but some links to internal documentation won’t work.

Feel free to leave comments directly in Notion, or reach out on Discord / Twitter

</aside>

Overview

Metalabel Protocol V1.1 includes:

Technical fixes and slight implementation changes to the core protocol following the V1 audits
Removal of message storage entirely from the node registry and resource base contracts. The protocol only supports emitting events now
A new DropEngineV2 that adds onchain metadata and other features to record drops
Membership NFTs that can be issued to squad members by a metalabel admin
A combination waterfall+split is now known as a “revenue module” that can be deployed by metalabels as a single cataloged (composite) resource
A new controller contract batches up actions around setting up a metalabel and publishing a release for better metalabel admin onchain UX

Updated cluster architecture

Metalabel protocol overview (9).png

The following new features were added in Metalabel Protocol V1.1:

This builds on V1 of DropEngine, with additional features
Metadata is now stored onchain via SSTORE2, with several non-standard fields nested under a metalabel field related to structuring onchain record data