The Grid - What can and can't be voted on

As we scale to include on and off-chain voting, we think it makes sense to establish rules on what is governable vs what is not governable. Obviously, tooling will need to be made for these things to make the information more human readable, but here is a starting framework for what smart contracts can be considered governable and not, and as on-chain voting is transitioned, this will allow for programmatic inclusion of these smart contracts. Current Draft is as follows.

Grid: Governable Resource Identifier


The Grid (Governable Resource Identifier) framework is used to classify governable smart contracts, routines, or processes. The purpose of the Grid is to define the location of the resource, the owner, the operator, as well as parameters that can be modified by governance and the process to do so.

Organizations that have been granted an OE Code through the process outlined in *P3 Number XX WIP can submit and manage their assets on the Grid.

Each resource on the Grid is identified by a unique file registered in this repository, which outlines the metadata specific to that resource in the network.


The grID identifies assets on the Grid as abstract entities representing bundles of one or more Digital Resources compiled for the purpose of some process in the Premia Ecosystem. A digital resource may be one or more smart contracts, nodes, modules, programs, or products in the Premia Ecosystem.

Current asset types can be found [placeholder].

It is not used to identify any specific instances or products which may exist primarily outside the Premia Ecosystem; however, in some circumstances, assets may overlap.

The primary purpose is for which assets in the ecosystem can be referenced in the P3 procedure, that can be controlled by governance or could be controlled by governance in the future under certain conditions.

Circumstances exist in which an owner, operator, or contributor may create some assets in the ecosystem, in which the governance process cannot be applied (for example tokenholder vote on use of an operator treasury).

As such, items like these should be managed off the grid.

Resources on the Grid can be modified via Zip, Proclamation, Notice, Workflow, or Technical processes.

Current processes types can be found under [placeholder]


On the Grid: Governable Assets (issued grID)

Off the Grid: Ungovernable Assets

OE Code: Organization approved via Governance

Cable: P3 Routine Operation

P3: Premia Publication Process

Grid Operations


The Grid Administrator has super user access of all assets on the Grid.

A Grid Operator can list or amend assets in which they are the owner of.

(Future State) Blue Descent governance is the default owner of all assets on the Grid, thus can add or remove grid operators or owners, as well as amend any parameter on the Grid through consensus vote.

The list of Current Grid Admins and Operators can be found on the registry.

Org Entity

An Organizational Entity is eligible to be granted an OE Code by Blue Descent Governance, and therefore to issue new Grids, if it claims to be:

  1. the owner of copyrights


  1. the operator of resource

The policies and procedures by which other types of organizations may become eligible to be granted an OE Code will be established by Blue Descent Governance.

grID Issuance

Blue Descent shall issue an OE Code to any eligible organizations that apply for such a code and agrees to comply with this Standard for implementing the Grid.

Blue Descent may assign a charge or bond for issuing an OE Code, on a reasonable and non-discriminatory basis, for cost recovery purposes and to ensure long-term alignment.

Releases to which an Org Entity can create a grID

An Organization shall issue a grID only if (with respect to the Digital Resource(s) included in that Release):

  1. it is the owner of the copyrights in the Digital Resources


  1. it is an exclusive licensee in respect of the copyrights in the Digital Resources


  1. it has been specifically authorized by either the copyright owner or the exclusive

licensee to compile a Release containing the Digital Resources

Resource Metadata & Naming Conventions

Each grID shall be named by its public key address.

When utilizing a proxy, two unique grIDs shall be issued, one for the proxy, one for the implementation contract.

Each grID shall have a set of Reference Descriptive Metadata associated with it.

This set is defined in Annex A and defines the parameters controlled by the operator and/or governance.

Process of Allocation of grIDs

An Organization may allocate a grID to each resource release for which it is responsible.

By creating a grID the organization retains the right on which parameters can be modified by governance, by the grID operator, or by the grID owner. Assigning a new grID to each asset is encouraged, even if no modifiable fields or functions are assigned.


Blue Descent shall, on a regular basis, carry out compliance procedures to ensure that all organizations remain in compliance with this specification. In circumstances where an organization is found not to be in compliance with this standard, Blue Descent shall require corrective action.

Blue Descent shall be responsible for publishing from time to time the form of its compliance procedures and the corrective actions it would require in the event of non-compliance. Blue Descent has the power to withdraw an OE Code from an Organization in the event of persistent non-compliance.

Parameter Change

Any identified attribute or function that can be modified through governance shall follow the appropriate cable procedure as outlined within this repository under the respective cable type.

Current processes (cable) types can be found under [placeholder]

##### Annex A

The following data elements make up the Reference Descriptive Metadata set associated with an asset issued on the Grid.


It is recommended to begin by forking the [templatePlaceholder]