17 lines
1.2 KiB
Markdown
17 lines
1.2 KiB
Markdown
|
Reputation is comprised of non-fungible tokens associated with specific forum graph post -> author edges.
|
||
|
|
Therefore in principle, all information about the context of a given rep token can be derived by inspecting the forum graph.
|
||
|
|
However, in practice, the computational costs and the difficulty of preserving complete records will increase over time.
|
||
|
|
It is for this reason that we compute the current value of a given rep token and store that value.
|
||
|
|
Although the value could be recomputed when needed, it would be (unpredictably) expensive and time-consuming to do so.
|
||
|
|
|
||
|
|
In its current, singular form, all instances of reputation within a given DAO have equal power, assuming equal numeric value.
|
||
|
|
|
||
|
|
However, the question arises: what would it take to support the ability to initiate a validation pool in which the power of a reputation token
|
||
|
|
depends on something more than just its numeric value?
|
||
|
|
|
||
|
|
This would be something specified when a validation pool is initiated.
|
||
|
|
|
||
|
|
Suppose we support the notion of distinct types of reputation within a given DAO.
|
||
|
|
Let's say we have reputation type A and B.
|
||
|
|
Let's say we have a validation pool that requires reputation type A to vote, and mints reputation type A.
|
||
|
|
That means governance is separated.
|