Color theme, notes

This commit is contained in:
Ladd Hoffman 2023-01-04 14:30:15 -06:00
parent f944d19728
commit e34534675f
3 changed files with 30 additions and 13 deletions

View File

@ -4,17 +4,21 @@
- Distributing payments to participants
- Computing updates to forum graph
## Receiving payments
---
# Receiving payments
Business SC will need to implement a financial model.
---
# Excerpts from DeSciPubDAOArchit22July19PrintCut.pdf
> With todays prices, however, we will begin by programming this all off-chain and simplify the reputation tokens to be less dynamic in their evaluation. Next iteration improves the decentralization commensurate with practical realities.
# Questions
---
## Validation pool termination
# Validation pool termination
How do we want to handle this?
The validation pool specifies a duration.
@ -42,12 +46,32 @@ A given DAO can have a formula for deciding appropriate amounts.
---
#
The following was a code comment on `Business.submitRequest(fee, ...)`:
Implementing forum
> Fee should be held in escrow.
> That means there should be specific conditions under which the fee will be refunded.
> That means the submission should include some time value to indicate when it expires.
> There could be separate thresholds to indicate the earliest that the job may be cancelled,
> and the time at which the job will be automatically cancelled.
# Implementing forum
Does the following make sense?
We will link the forum to the bench
An author of a forum post /_ ? is always? can be? _/ a reputation holder.
This is what we call a member. Let's update that terminology to be `reputationHolder`.
That's too long, though. Let's rename it to `expert`.
So we want to aim for the situation where the author of a forum post is an expert.
For now let's try thinking of them as experts no matter what;
The strength of their expertise is meant to be represented by reputation tokens.
So each reputation token must be a contract.
Minting a reputation token means to construct an instance of such a contract.
The reputation contract then has its own lifecycle.
We can support dynamic reevaluation if the reputation contract
- has an interface that allows (securely) updating
- Define secure :: passes validation pool
- How shall it know the operation is occurring as part of an "official" validation pool?
It can verify a signature...
---

View File

@ -30,13 +30,6 @@ export class Business extends Actor {
};
}
/**
* Fee should be held in escrow.
* That means there should be specific conditions under which the fee will be refunded.
* That means the submission should include some time value to indicate when it expires.
* There could be separate thresholds to indicate the earliest that the job may be cancelled,
* and the time at which the job will be automatically cancelled.
*/
async submitRequest(fee, content) {
const request = new Request(fee, content);
this.requests.set(request.id, request);

View File

@ -1,5 +1,5 @@
body {
background-color: #2a5b6c;
background-color: #1b3d49;
background-color: #114754;
color: #b6b6b6;
font-family: monospace;