features of a Fabric ledger: Query and update ledger using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only best implemented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concatenation of org.papernet.paper, Issuer and Paper properties. This structure

features of a Fabric ledger: • Query and update ledger using key-based lookups, range queries, and composite key queries • Read-only queries using a rich query language (if using CouchDB as state database) imple- mented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concate- nation of org.papernet.paper, Issuer and Paper properties. This structure

features of a Fabric ledger: Query and update ledger using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only best implemented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concatenation of org.papernet.paper, Issuer and Paper properties. This structure

features of a Fabric ledger: • Query and update ledger using key-based lookups, range queries, and composite key queries • Read-only queries using a rich query language (if using CouchDB as state database) imple- mented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concate- nation of org.papernet.paper, Issuer and Paper properties. This structure

features of a Fabric ledger: • Query and update ledger using key-based lookups, range queries, and composite key queries • Read-only queries using a rich query language (if using CouchDB as state database) imple- mented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concate- nation of org.papernet.paper, Issuer and Paper properties. This structure

features of a Fabric ledger: Query and update ledger using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only best implemented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concatenation of org.papernet.paper, Issuer and Paper properties. This structure

features of a Fabric ledger: Query and update ledger using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only implemented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concatenation of org.papernet.paper, Issuer and Paper properties. This structure

features of a Fabric ledger: • Query and update ledger using key-based lookups, range queries, and composite key queries • Read-only queries using a rich query language (if using CouchDB as state database) imple- mented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concate- nation of org.papernet.paper, Issuer and Paper properties. This structure

features of a Fabric ledger: Query and update ledger using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only best implemented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concatenation of org.papernet.paper, Issuer and Paper properties. This structure

features of a Fabric ledger: • Query and update ledger using key-based lookups, range queries, and composite key queries • Read-only queries using a rich query language (if using CouchDB as state database) imple- mented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concate- nation of org.papernet.paper, Issuer and Paper properties. This structure