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-30 15:09:38

Browse Source
This commit is contained in:
Jet Hughes 2022-11-30 15:09:38 +13:00
parent c2b98dd537
commit 542666d433
3 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/notes/media.md
View File

@ -7,6 +7,8 @@ tags:
# Albums
Andrew Wasylyk - Fugitive Light And Themes Of Consolation
nathan salsburg
maggie nicols
# Books
- 2022

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

@ -359,11 +359,11 @@ Meeting with david
- kicking out one or more participants
- forking due to not trusting or agreeing with other participants
- what if one participant is a bad actor and the other want to remove them, but the bad actors vote is required
- The idea of tethering a closed blockchain to a public blockchain is worth considering
- Rather than acting directly as a source of truth, a blockchain as applied to the veracity project should act as a store of records that can then be used by relevant authorities make decisions – which can then be recorded on the chain
- The idea of tethering a closed blockchain to a public blockchain is worth exploring further
- Within the veracity project (or outside it), rather than acting directly as a source of truth, a blockchain should act as a store of records that can then be used by relevant authorities to make decisions – which can then be recorded on the chain
- maybe consider something related to a reputation system like ebay (talk to andrew), trademe, etc
- regarding scope: this is something I need to think about. Does it make sense to have a closed blockchain with 100s or 1000s of participants. This is somewhere where we would like have a small group of validator nodes and many less-priviledged participant nodes
- my role is this project is exploratory. By considering many small scenarios, I might eventually find one which breaks the existing architectures and I can then work on a solution for that.
- i should spend some time to try and get the prolog kernel working
- regarding scope: this is something I need to think about. Does it make sense to have a closed blockchain with 100s or 1000s of participants. This is somewhere where we would likely have a small group of validator nodes and many less-priviledged participant nodes
- my role is this project is exploratory. By considering many small (or big) scenarios, I might eventually find one which breaks the existing architectures and I can then work on a solution for that.
- I should spend some time to try and get the prolog kernel working
- try rolling back to an earlier version
- also test the aforementioned scenario using a small network of ~10 participants

1
content/notes/veracity.md
View File

@ -15,7 +15,6 @@ Blockchain technology falls into two distinct classes: open (permissionless) blo
- It is then maintained by the participants
- [ ] 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?