From 3687fd67e02764f1cabb721ad056fcb15225f955 Mon Sep 17 00:00:00 2001 From: toktar Date: Thu, 21 Dec 2023 15:49:53 +0300 Subject: [PATCH 1/2] Update README.md Signed-off-by: toktar --- indy-besu/README.md | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/indy-besu/README.md b/indy-besu/README.md index ea03d4a25..79f1f04c1 100644 --- a/indy-besu/README.md +++ b/indy-besu/README.md @@ -1,8 +1,21 @@ -# Indy ledger - +**This is not an official Indy Ledger code yet, but an experimental proof of concept (PoC). The goal is to prove a possibility to use Indy Besu as a foundation for Indy Ledger and show how it can be done. +The code and PoC may be moved to a separate Indy repository later for further development.** + +# Indy Besu ledger + +## Plan for making this code official +Proposed by @TelegramSam in #1826 +- Work is created in new repositories + - I understand a previous conversation decided to put the work in indy-node. I think this decision should be changed. + - This will help the work move faster with less community bottlenecks. +- Related work should be clearly labeled as experimental or research + - This includes a did method definition, for example +- Advance the project so that we are able to test the properties of the project, including speed, scale, bandwidth, processor load, and energy use. +- Delay commitment to the new approach until we reach sufficient confirmation of approach validity. + ## Goals and ideas -* Provide a replacement for [Hyperledger Indy](https://www.hyperledger.org/projects/hyperledger-indy) ecosystem that provides support for verifiable credentials: +* Prove a possibility of replacement for [Hyperledger Indy](https://www.hyperledger.org/projects/hyperledger-indy) ecosystem that provides support for verifiable credentials: * Components to replace: * Distributed ledger: [Indy Node](https://github.com/hyperledger/indy-node) and [Indy Plenum](https://github.com/hyperledger/indy-plenum) * Client library: [Indy SDK](https://github.com/hyperledger/indy-sdk/tree/main) From 5f7e0f55390e1c51130bf8a2a68de0f5b3d7f78d Mon Sep 17 00:00:00 2001 From: toktar Date: Thu, 21 Dec 2023 16:22:48 +0300 Subject: [PATCH 2/2] Update README.md formatting Signed-off-by: toktar --- indy-besu/README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/indy-besu/README.md b/indy-besu/README.md index 79f1f04c1..81f47a82a 100644 --- a/indy-besu/README.md +++ b/indy-besu/README.md @@ -5,13 +5,13 @@ The code and PoC may be moved to a separate Indy repository later for further de ## Plan for making this code official Proposed by @TelegramSam in #1826 -- Work is created in new repositories - - I understand a previous conversation decided to put the work in indy-node. I think this decision should be changed. - - This will help the work move faster with less community bottlenecks. -- Related work should be clearly labeled as experimental or research - - This includes a did method definition, for example -- Advance the project so that we are able to test the properties of the project, including speed, scale, bandwidth, processor load, and energy use. -- Delay commitment to the new approach until we reach sufficient confirmation of approach validity. +>- Work is created in new repositories +> - I understand a previous conversation decided to put the work in indy-node. I think this decision should be changed. +> - This will help the work move faster with less community bottlenecks. +>- Related work should be clearly labeled as experimental or research +> - This includes a did method definition, for example +>- Advance the project so that we are able to test the properties of the project, including speed, scale, bandwidth, processor load, and energy use. +>- Delay commitment to the new approach until we reach sufficient confirmation of approach validity. ## Goals and ideas