GitHub/quartz
1
0
Fork 2
mirror of https://github.com/jackyzha0/quartz.git synced 2026-03-24 15:05:42 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

vault backup: 2022-12-20 14:48:50

Browse Source
This commit is contained in:
Jet Hughes 2022-12-20 14:48:50 +13:00
parent f670d1d16e
commit d9cde9fdab
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/notes/isolated scenarios.md
View File

@ -21,7 +21,9 @@ Within an existing closed BC with 10 participants. say we wanted to add another
- or: will need to look into HL Burrow but there might a way to have an on-chain smart contract voting system which automatically adds them depending on the vote
- I could think about how to implement such a smart contract
How could a bad actor try to get themselves on the chain? Could they dupe someone else into signing the entry contract on their behalf? Or could they bypass the contract? The genesis block of a new peer (in HL iroha) has to be the exact same as the genesis block of all other peers. Could the genesis block be like a sort of "key to the network. Maybe not because there is not much to stop one of the existing peers sharing the genesis block with third parties.
How could a bad actor try to get themselves on the chain? Could they dupe someone else into signing the entry contract on their behalf? Or could they bypass the contract? The genesis block of a new peer (in HL iroha) has to be the exact same as the genesis block of all other peers. Could the genesis block be like a sort of "key to the network. Maybe not because there is not much to stop one of the existing peers sharing the genesis block with third parties. But then even if a someone leaked the genesis block the existing nodes would have to be instructed to start intereacting with the new node. I think the genesis key idea is dumb. We do still have to get the genesis block to the new members though. I think this would just be included as part of a repository for spinning up a node.
How does a new node request to join the network. Would it be an off-chain application process? Or would they be able to start a node, maybe join a sort of "lobby" network which they use to apply and maybe test their node and maybe some other things. Then once their "application" is accepted, they are allowed in to the main network. Would the lobby network be a sub network within the main network or a totaly separeate network. If it was separate it would have to have its own
# Remove Member
What happens if one participant turned bad and the other wanted to remove them from the group. Ssay we havea grup of 10 participants in a closed blockchain system using a CFT consensus algorithm Then they can be voted out so that their vote is desregarded and so they cant view or access data on the chain. what if they require access to decuments stored on-chain which they dont have local copies of. I guess they wuld have access to a stored copy of the blockchain on their node. But then would this chain be considered valid by oters. they dont store the actual document on the blockchain – only a timestamped hash to prove they had that doc at this particular time. participats should keep local copies of documents. Can participants kick out the initiating authority? You would have some mechanism to ensure that they cant be kicked out. firstly there would have to be a vote to kick them out. unless they aren't actually needed. who are the people that look at the documents that are stored on the chain to check them. Some third party collectively employed by the group? the govt? maybe its required for each participant to sometimes go and check if other participants are being truthful.