GitHub/quartz
1
0
Fork 2
mirror of https://github.com/jackyzha0/quartz.git synced 2025-12-27 23:04:05 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

vault backup: 2022-11-24 15:01:51

Browse Source
This commit is contained in:
Jet Hughes 2022-11-24 15:01:51 +13:00
parent eef48764e2
commit f98f78ea25
3 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
content/notes/blockchain-project.md
View File

@ -18,6 +18,7 @@ Blockchain technology falls into two distinct classes: open (permissionless) blo
- [ ] How is on-chain governance implemented?
- Smart contracts?
- [ ] Do we need to track the products physically?
- e.g., using IoT devices
- [ ] Who will be participating in the blockchain?
- Three major parties in food supply-chain: Market, Manufacturing, Agriculture
- Do I need to define this in more detail?
@ -30,6 +31,10 @@ Blockchain technology falls into two distinct classes: open (permissionless) blo
- Maintenance/Development of the codebase
- Inviting/banning participants
- [ ] Need to consider applications of decentralized identity technology
- [ ] What happens if a participant is caught being untruthful?
- Can they be automatically kicked out or is a vote required?
- How can we distinguish between mistakes and intentional deceit?
- Maybe a reputation system. This way one mistake is not fatal, and a reputation can be restored over time
# Notes
[think-writing/log](notes/think-writing.md)

5
content/notes/think-writing.md
View File

@ -257,3 +257,8 @@ What do I need to define so that I can design rules for the governance of my blo
I just started [this](notes/veracity-governance.md) document. I think I am going too much into detail about the external system.
In ethereum governance rules are the systems that allow the protocol to change. Do the governance rules in our permissioned chain need to cover anything else. So far I've identified two things that the governance need to manage:
- The process for change of the codebase/protocol
- The process for admitting a new participant
What happens if a participant is caught being untruthful? Can they be automatically kicked out or is a vote required? How can we distinguish between mistakes and intentional deceit?

2
content/notes/veracity-governance.md
View File

@ -28,6 +28,8 @@ Things to consider:
- What is the required infrastructure — NVM I think they just use a website/app to upload information
# Process for Change
Can/Should we use a system similar to EIPs/BIPs?
-
# Voting Protocol