Notes

forum-network/notes/chain.md

@@ -28,3 +28,19 @@ cardano -- "dynamic availability"?
 staking pools -- does it make sense with reputation?
 what about for governance voting --
 do we want a representative republic or a democracy?
+
+---
+
+# Protocol brainstorming
+
+Each node must build/maintain a view of the history and/or state of the "smart contract" operations.
+
+Nodes must sign messages to each other with asymmetric keys.
+
+This is intended to be an open network that anyone can join.
+
+Each node must verify the results reported by other nodes, and themselves report results to other nodes.
+
+In order to receive payments, the network must solve the same problems that (other) block chains have solved, i.e. must prevent double-spend; must prevent tampering with the ledger.
+
+Storage may be ranked into tiers, where there is core data essential to the integrity of the ledger; ancillary data that is important or desirable for review of the ledger; and supplementary data that is of variable importants for particular use cases, but does not compose the core fabric of the system.

forum-network/notes/ecosystem.md

@@ -0,0 +1,27 @@
+# Ecosystem Health
+
+How do we incentivize and reward the producers and maintainers of infrastructure? Of essential goods and services?
+
+How do we reward pro-social behavior?
+
+How do we encourage creativity?
+
+Vision/Mission
+
+Craig: Give people tools to enable them to better express their values by collaborating
+
+truth
+good
+beauty
+
+thought
+action
+perception
+
+ideas
+knowledge
+beliefs
+
+utility
+
+evolution in the true sense -- most directions it can change will be detrimental

forum-network/notes/infrastructure.md

@@ -0,0 +1,5 @@
+At the base layer, we need a peer to peer protocol that allows new nodes to join the network and send and receive messages. It must protect against denial of service attacks. It must support the establishment of consensus, to varying strengths.
+
+We need a lightweight messaging solution to facilitate gathering information from the edges of the network, but we also need to protect against denial of service by malicious actors.
+
+[gossipsub](https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md) looks like a good protocol for this.

forum-network/notes/matrix.md

@@ -7,3 +7,28 @@ Matrix supports "Application Services", which are limited to funcion in a passiv
 Synapse, a Matrix server implementation, supports "Modules"
 
 The Matrix devs recognize the need for a robust reputation system and are in pursuit of funding and development for that purpose.
+
+```mermaid
+graph LR
+
+subgraph Matrix
+homeserver[Homeserver]
+chainClient[Blockchain<br/>connected<br/>client]
+publicClient[Public<br/>Matrix-only<br/>client]
+end
+
+blockchain[Blockchain]
+%% subgraph Blockchain
+%%   forum[Forum]
+%%   post[Post]
+%%   availability[Availability]
+%%   wsc[WSC]
+%%   pool[Validation<br/>Pool]
+%% end
+
+publicClient --> homeserver
+chainClient --> homeserver
+chainClient --> blockchain
+homeserver --> blockchain
+
+```

forum-network/notes/todo.md

@@ -0,0 +1,17 @@
+# signature verification
+
+# voting topologies
+
+# client implementations
+
+## example workflows
+
+- retroactive sign flip
+
+# storage scaling
+
+# blockchain underpinnings
+
+# reputation token lifetime / decay
+
+- active/passive

forum-network/src/classes/dao/forum.js

@@ -101,6 +101,10 @@ export class Forum extends ReputationHolder {
     return this.getPosts().reduce((total, { value }) => total += value, 0);
   }
 
+  // getLatestContract(type) { }
+
+  // getContract(type) { }
+
   async onValidate({
     pool, postId, tokenId,
   }) {