From a7c1d55afab796070e478a35aaa1dfd784690b01 Mon Sep 17 00:00:00 2001 From: Jet Hughes Date: Sun, 26 Feb 2023 17:49:15 +0900 Subject: [PATCH] vault backup: 2023-02-26 17:49:15 --- content/notes/veracity-summary.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/notes/veracity-summary.md b/content/notes/veracity-summary.md index 3c94f88b0..bc2528080 100644 --- a/content/notes/veracity-summary.md +++ b/content/notes/veracity-summary.md @@ -12,11 +12,11 @@ The aim of this project was to consider aspects of a closed public permissioned ### Scenarios There were three main scenarios that spend time to explore: Adding a new member, removing a member and accidental transactions. This process helped me to understand some of the intricacies of the system I was trying to conceptualise. Before this process I was lost in the infinite number of forms that a solution to our problem count take. By focusing one single aspect of the system I was forced to accept a basic framework of what the solution could be and use it to explore how a given scenario might occur -#### Adding a member +#### Adding a participant This was the first scenario I considered. Initally I wanted to explore how a group of participants might band together to create a fork of the chain. However, this seemed like an unecessarily complex scenario to begin with. The idea I came up with was to have a smart contract which is triggered when an application arrives, which then collects votes from the existing participants and accepts or rejects the application based on the outcome of the vote. We would also need to find some way of protecting the application process from a sort of DoS attack where the attacker flooded the system with applications. -#### Removing a member - +#### Removing a participant +This scenario occurs in two situations. Firstly when a participant wants to leave coluntarily, which can be handled easily, and secondly when a participant or group of participants agree to forcefully remove another participant or group of participants. ### Solidity Contract Near the end of the project before my break I decided to try to test the Add New Participant scenario. I decided to do this by making a smart contract that would run on the Iroha Blockchain. I could use the Hyperledger Burrow integration to run a smart contract in the Ethereum Virtual Machine, which could interact with Iroha.