Merge branch 'main' into envelope_service_unit_tests

README.md

@@ -7,16 +7,29 @@
                             \_|    \_____/\____/ 
 
 ```
+## Status
 
-# P8E — Provenance Contract Memorialization on DLT
+[![Latest Release][release-badge]][release-latest]
+[![Code Coverage][code-coverage-badge]][code-coverage-report]
+[![License][license-badge]][license-url]
+[![LOC][loc-badge]][loc-report]
 
-P8e provides a system for collaborative execution, consensus, and proof recording of business execution on a distributed ledger
-without revealing the contents of transactions.
+[code-coverage-badge]: https://codecov.io/gh/provenance-io/p8e/branch/main/graph/badge.svg
+[code-coverage-report]: https://app.codecov.io/gh/provenance-io/p8e
 
-## Smart Contract Engine, Indexer, Encrypted Object Store, Mailbox, etc (lots more stuff here)
+[release-badge]: https://img.shields.io/github/v/tag/provenance-io/p8e.svg?sort=semver
+[release-latest]: https://github.com/provenance-io/p8e/releases/latest
 
-Lee / Travis / Matt
+[license-badge]: https://img.shields.io/github/license/provenance-io/p8e.svg
+[license-url]: https://github.com/provenance-io/p8e/blob/main/LICENSE
 
+[loc-badge]: https://tokei.rs/b1/github/provenance-io/p8e
+[loc-report]: https://github.com/provenance-io/p8e
+
+# P8E — Provenance Contract Memorialization on DLT
+
+P8e provides a system for collaborative execution, consensus, and proof recording of business execution on a distributed ledger
+without revealing the contents of transactions.
 
 ## P8E-PROTO
 
@@ -27,20 +40,12 @@ and submitting to the blockchain for validation/recording.
 
 ## Provenance Blockchain
 
-All of the contract memorialization artifacts are stored within the `provenance-channel` DLT on blockchain.  Currently 
-blockchain operations are handled through the adminapi service.  Submitted contract memorialization requests are evaluated
-against the known global provenance state.  Chain of custody and control is enforced for all state transitions to ensure
-provenance of data is maintained.  Participants in transactions are identified by Affiliate certificate registrations on chain.
-
-
-### Contract Chaincode
-
-Contract chaincode provides an implementation of the contract ledger rules.  A  contract for memorialization is submitted
-in an `envelope` protobuf that contains a reference to the existing contract specification, affiliates involved with the request,
-and references to any existing resources on chain that are involved in the request.
+All of the contract memorialization artifacts are stored within [Provenance](https://github.com/provenance-io/provenance) DLT 
+on blockchain. Submitted contract memorialization requests are evaluated against the known global provenance state.  Chain 
+of custody and control is enforced for all state transitions to ensure provenance of data is maintained. 
 
-### Affiliate Chaincode
+## Contract
 
-The Affiliate ledger contains records for each affiliate that contains their permission roles and basic information along with a list
-of all known certificates and public keys for each affiliate.  These records are retrieved and compared against information provided
-to the contract ledger during memorialization.
+Contract provides an implementation of the contract ledger rules. A contract for memorialization is submitted
+in an `envelope` protobuf that contains a reference to the existing contract specification, parties involved with the request,
+and references to any existing resources on-chain that are involved in the request.