create account

Fractally White Paper Addendum 1 by dan

View this thread on: hive.blogpeakd.comecency.com
· @dan ·
$128.78
Fractally White Paper Addendum 1
![FractallyWhitePaperA1.png](https://images.hive.blog/DQmbBJjVdchuMQHmZz63aF6u8dpf72cPVQ2AMxE4VU7bgFJ/FractallyWhitePaperA1.png)

  

This post is an update to the ideas and concepts presented in the [ƒractally white paper](https://fractally.com) based upon lessons learned over the past 4 months of [community experimentation with the process](https://gofractally.com) using Hive as the ledger. Some of the principles that are guiding this update include:
 

1.  Limits of Precision of Subjective Judgement
2.  Scale Invariant Design (down to 20 people)
3.  Need to Average over Time
4.  Minimize Meeting Times    
5.  Predictable Token Supply
    

## Limits of Subjective Judgement

We have come to model people as a scientific instrument attempting to assess the relative value of each individual’s past contributions relative to their past recognition. Furthermore, each instrument has a different scale and we are attempting to integrate the different values of all community members to arrive at a consensus value. In the weekly meetings it is generally easy to identify the greatest and least contribution but harder to rank two people with similar levels of contribution. This is complicated by the fact that the same person ranking the same contributions may have different opinions on different days.

  

We can therefore assume that any given measurement has a wide margin of error and that many measurements are required in order to get a more accurate measure of community consensus.

  

We can also assume that not all people are equally skilled in making these value judgments so the average error over the entire population is likely much greater than the average error in the top half of the population. This skill in valuing contributions is likely pareto distributed and therefore fractal in structure. Meaning the top quarter of people are likely far better at making value judgments than the top half.

  

That said, even the most skilled individual is operating with limited information and would have a hard time distinguishing contributions. Therefore, if we apply the fractal governance pattern as outlined in the white paper with up to 5 rounds, the later rounds are likely to have amplified errors as fewer and fewer measurements are responsible for allocating a larger and larger percentage of the communities budget.

  

On the other hand, if we only have 1 round then the noise from the less skilled contributors will dominate. Under the model in the Fractally white paper a community would need to have at least 30 people to get to a second round consisting of just 5 people. These top 5 people will have a hard time accurately ranking each other leading to more noise.

## Scale Invariant Design

In an ideal world the rules for governance would not need to change as a community grows. This means that there should always be the same number of rounds regardless of community size. The design we present in this update will work with any community with at least 20 people participating every week.

### Round One

In the first round everyone is randomly assigned to groups of 5 or 6 people who must reach consensus on who contributed the least (Level 1) to who contributed the most (Level 6). Unlike how the current Genesis Fractal ranking system has been operating, the ranking order of the top 3 contributors (Level 4, 5 and 6) does not matter because the top 3 people from each group must advance to Round Two. Because the order of the top 3 contributors does not need to be agreed to in Round One, it should dramatically reduce the time it takes to reach a consensus.

### Round Two

In the second round the top 3 contributors from the first round are randomly grouped and they must reach consensus on who contributed the least (Level 3) to who contributed the most (Level 8). This round will operate in a manner similar to how the Genesis Fractal has currently been operating.

  
<center>
![image.png](https://images.hive.blog/DQmZRbpJpH1jmWans2RnrtSttwDHESup8QQ5CNismUpxLYs/image.png)
</center>

With this model the community is able to identify the top 9% of contributors in just two rounds. Critically there is always at least 3 groups in round two even with communities as small as 20 people. This means there will always be at least 3 people who achieve Level 8. After 4 months of experimentation we believe that the this may represent the limit of human judgment and that further ranking of the top 8 is more likely to introduce noise to the measurement and introduce incumbent advantage. If we assume the best people are reliably recognized by earlier rounds then each successive round will tend to promote a similar group of people. If we allow this group of people to push people further up the fibonacci sequence then they would tend to dilute the influence of earlier rounds and amplify the errors of individual measurements.

  

One of the caveats of this new model is that not everyone is promoted to Round 2 is guaranteed to get a Level greater than the highest level that wasn’t promoted from Round 1. This was done to reduce the incremental advantage between Level 3 and Level 4 of Round 1. Under a Fibonocci distribution that advantage was already going from earning respect of 3 to respect of 5 (a ~60/40 split of 8) but now the gap would also include the opportunity to reach Level’s 5 to 8. This could make it difficult for Round 1 participants to decide who should be Level 3. By making the lowest Level assigned by Round 2 equal to the highest Level assigned by Round 1 it removes the difference in Respect distributed in Round 1 between those they rank at Level 3 and those they promote to Round 2. This lets Round 2 groups resolve that difference.

  

The net effect is that unless you believe that you are likely to achieve Level 4 to 8 in Round 2 then you have nothing to gain by being promoted. Promotion to Round 2 requires participating in another meeting. In other words, by starting Round 2 at Level 3 we make it easier for Round 1 participants to reach consensus.

## Average over Time

One of the emotionally challenging aspects of the ranking process is that sometimes a group of 6 people is randomly assigned many of the top people from the community. When this happens someone has to be ranked lower even though they contributed far more than people in other groups. On the other hand, some groups are randomly assigned people who contributed very little and someone gets lucky and is ranked far higher than a top contributor. This is bad enough when there is only one round and it would be seriously amplified when multiple rounds are introduced if only the highest ranked individual was promoted to the second round.

  

This noise introduced by the necessary randomness combined with the limits in our ability to reliably compare relative values means that community members need to trust the process over time and not get discouraged (or overly optimistic) due to the results of any single week.

  

What we have learned is that a persons average Level is probably a more accurate means of ranking someones average contribution over time. This average integrates the opinions of not just one random group of 6 people, but potentially 6 to 12 random groups of people depending upon whether you average over 6 to 12 weeks.

  

Someone who reliably achieves a Level 8 every week is likely to be contributing far more value (with far greater consensus on that value) than someone who only averages a Level of 7.5. There is a bigger difference between an average Level 7.5 and 7.6 than between 7.4 and 7.5.

  

Under the design in the Fractally white paper Respect was distributed according to AVERAGE( FIBONACCI( LEVEL ) ). We now propose that Respect be distributed according to FIBONACCI( AVERAGE(LEVEL) ). This means we need a continuous Fibonacci function.

  
<center>![image.png](https://images.hive.blog/DQmWQAwRKGTSjHjyEKiJ9Da2698emsEMEasiXF7QGNsKMjk/image.png)</center>

  

A consequence of this averaging method is that no one can show up for only one week, get highly ranked, and earn a large amount due to the exponential nature of Respect rewards relative to Level. Instead, to climb the curve you must average a high Level over time. This should dramatically reduce the social costs of collusion/misjudgment in any single group.

  

It also means that you can earn something even on weeks you do not attend a meeting. Your average will fall by incorporating a Level 0, but you will never the less get some compensation. The end result is that the amount of Respect allocated to an individual from week to week is far more stable.

  

The chart below shows what would be earned each week if someone showed up and started achieving the highest Level (8) every week for 26 weeks and then left and being given a Level (0). Note that after 12 weeks of non-attendance someone would cease to be a member and their income would fall to 0. This graph does not factor in the loss of membership which would take precedence, but is intended to represent the relative shape of the curve.
<center>
![image.png](https://images.hive.blog/DQmNWRx2viKTopFyMUeUVyTgbsqp6oqUquuRy1HuMoafGLn/image.png)
</center>

The average is calculated as NEW_AVERAGE = (CURRENT_AVERAGE * 5 + NEW_LEVEL)/6. This moving weighted average is an approximation that is easy to calculate, but there are a number of different kinds of averages that could work in a similar manner. A pure moving window average would go from 0 to max in just 6 weeks and fall from max to 0 in 6 weeks whereas this function has more momentum to it which I believe may better approximate reputation.

  

# Token Distribution

One of the most frequent questions we are asked is what is the “token model” because the token model is one of the most critical considerations in estimating a valuation. Bitcoin has a token model that guarantees there will only ever be 21 million tokens and the rate of issuance will fall by 50% every 4 years. This simple model makes it easy for speculators to estimate supply and demand.

<center>
![image.png](https://images.hive.blog/DQmRhKsq4GSuvfygoSzwiidCGYJpEiQ5nY7nEgpsYXvt2Uw/image.png)
  </center>

The model presented in the Fractally White Paper was subject to many variables such as the number of community members participating any given week. This makes it challenging for people to model their rate of dilution which could change radically over time.

  

Under the original design, as the community reaches maximum size the rate of issuance becomes constant and the inflation rate approaches 0% APR. This means that the community does not decay the value of old contributions relative to current contributions and the token will eventually stagnate due to insufficient funding of necessary community maintenance activities. 

Furthermore, the token distribution is not initially biased toward the early adopters who take the most risk which means these early adopters will be rapidly diluted by the masses of late adopters who show up when the risk is greatly reduced.  

Given these two facts we propose a rate of issuance that falls by 50% per year (continuously) until the annual inflation rate reaches 5% APR at which point it remains constant. This 5% number is consistent with my theory of [Universal Resource Inheritance](https://moreequalanimals.com/posts/universal-resource-inheritance) (outlined in my book, [More Equal Animals](https://store.bookbaby.com/bookshop/book/index.aspx?bookURL=More-Equal-Animals&b=p_bu-ba-or)) where the resources of the world are fairly distributed over time from one generation to the next.

 

We also propose that the initial rate start at 1 million tokens per week. Given these parameters the token supply can be trivially graphed over the next 24 years.

  

The key difference between the inflation allocated by fractal governance vs the inflation of other currencies is that fractal governance is more likely to distribute the inflation to those producing public goods which grow the value of the currency instead of being syphoned off by insiders and graft.
<center>![image.png](https://images.hive.blog/DQmeW3XMDCsCtTEMXsmTVxSrZAmLsUnagzygAt9UQVexfaU/image.png)</center>

Given this token model is fixed, we need a way to map the dynamic amount of respect from the weekly meeting attendance onto this fixed supply. This is achieved by dividing the total tokens distributed on a pro-rata basis to the total respect allocated in the meetings. More generally, this can be modeled as two currencies where one allocates shares of inflation in the other currency. The inflation shares are burned when converted to the newly issued fixed-rate currency.

  

A community can then dynamically adjust how it issues shares in the inflation across weekly meetings, teams, block producers, social media content, liquidity rewards, and staking without impacting the bigger picture of a stable and predictable currency supply.

## Migrating Genesis Fractal

The Genesis Fractal has been running for a number of weeks and I would propose that the currency supply indiciated by the above model for that time period be pro-rata distributed among the respect holders who have participated thus far. Then going forward we can utilize the new model which more appropriately recognizes the early adopters who are making this all possible. With more respect for early adopters there is more incentive for people to join early and help us discover the most viable means of collaborating for our mutual benefit.

  
<sub>
<I>Disclaimer
Everything in this post is under development and presented for discussion purposes only. The final token distribution will depend upon the consensus of the Genesis Fractal.</I></sub>
👍  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 285 others
👎  ,
properties (23)
authordan
permlinkfractally-white-paper-addendum-1
categoryfractally
json_metadata"{"tags":["fractally"],"image":["https://images.hive.blog/DQmbBJjVdchuMQHmZz63aF6u8dpf72cPVQ2AMxE4VU7bgFJ/FractallyWhitePaperA1.png","https://images.hive.blog/DQmZRbpJpH1jmWans2RnrtSttwDHESup8QQ5CNismUpxLYs/image.png","https://images.hive.blog/DQmWQAwRKGTSjHjyEKiJ9Da2698emsEMEasiXF7QGNsKMjk/image.png","https://images.hive.blog/DQmNWRx2viKTopFyMUeUVyTgbsqp6oqUquuRy1HuMoafGLn/image.png","https://images.hive.blog/DQmRhKsq4GSuvfygoSzwiidCGYJpEiQ5nY7nEgpsYXvt2Uw/image.png","https://images.hive.blog/DQmeW3XMDCsCtTEMXsmTVxSrZAmLsUnagzygAt9UQVexfaU/image.png"],"links":["https://fractally.com"],"app":"hiveblog/0.1","format":"markdown","description":" Update to the ideas and concepts presented in the ƒractally white paper based upon lessons learned over the past 4 months."}"
created2022-07-15 22:20:33
last_update2022-07-15 22:20:33
depth0
children19
last_payout2022-07-22 22:20:33
cashout_time1969-12-31 23:59:59
total_payout_value64.426 HBD
curator_payout_value64.349 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length13,728
author_reputation155,470,101,136,708
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,893,239
net_rshares209,908,665,264,459
author_curate_reward""
vote details (351)
@aguerrido · (edited)
>... the later rounds are likely to have amplified errors as fewer and fewer measurements are responsible for allocating a larger and larger percentage of the communities budget. 

Not necessarily true. In the later rounds there will be fewer measurements but higher quality instruments. 

- So, in later rounds there is an _increase_ in error due to fewer measurements and a _decrease_ in error due to higher quality instruments. Those are two mutually competing factors. Also, self-ranking in the later rounds would tend to be detrimental to the positive effect of the second factor. Super interesting dynamics.
-	What about larger communities? A 1000 members community could justify a round 3, a 10K members community a round 4. Also, because Respect is allocated according to averages, those higher level rounds could take on larger time intervals. For example, once every month or every trimester, etc. Think about annual round 5 tournament of respect. Lol!


- As in all complex systems, noise at every level can be reduced through the incorporation of adequate feedback mechanisms. Not something that can be implemented now but super worth the effort exploring. 


-	Why the numbers 5 and 6 in the way average is calculated, why not 11 and 12 or something else?

Aside these comments, it looks like a great deal of effort and thought put into this addendum. It does feel like a significant experience/feedback based improvement. Great work guys. 

I'd say let's put it to test!
👍  ,
properties (23)
authoraguerrido
permlinkrfghvs
categoryfractally
json_metadata{"app":"hiveblog/0.1"}
created2022-07-23 04:31:03
last_update2022-07-23 04:35:45
depth1
children0
last_payout2022-07-30 04:31:03
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,484
author_reputation106,028,353,330
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id115,090,408
net_rshares1,472,550,161
author_curate_reward""
vote details (2)
@alwayswannafap21 ·
Wow very interisting
👍  
properties (23)
authoralwayswannafap21
permlinkre-dan-2022727t10564343z
categoryfractally
json_metadata{"tags":["fractally"],"app":"ecency/3.0.24-vision","format":"markdown+html"}
created2022-07-27 02:56:03
last_update2022-07-27 02:56:03
depth1
children0
last_payout2022-08-03 02:56:03
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length20
author_reputation22,402,432
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id115,194,067
net_rshares1,433,755,682
author_curate_reward""
vote details (1)
@frankbacon ·
rePOSTed
for @logiczombie
https://media.giphy.com/media/gfHPb7aHu68fTLgLeE/giphy.gif
👍  ,
👎  
properties (23)
authorfrankbacon
permlinkrf4u1p
categoryfractally
json_metadata{"users":["logiczombie"],"image":["https://media.giphy.com/media/gfHPb7aHu68fTLgLeE/giphy.gif"],"app":"hiveblog/0.1"}
created2022-07-16 21:22:39
last_update2022-07-16 21:22:39
depth1
children0
last_payout2022-07-23 21:22:39
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length84
author_reputation36,630,927,301,955
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,917,129
net_rshares-4,502,754,461
author_curate_reward""
vote details (3)
@hivebuzz ·
$0.03
Congratulations @dan! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s):

<table><tr><td><img src="https://images.hive.blog/60x70/http://hivebuzz.me/@dan/posts.png?202207160019"></td><td>You published more than 60 posts.<br>Your next target is to reach 70 posts.</td></tr>
</table>

<sub>_You can view your badges on [your board](https://hivebuzz.me/@dan) and compare yourself to others in the [Ranking](https://hivebuzz.me/ranking)_</sub>
<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>


To support your work, I also upvoted your post!


###### Support the HiveBuzz project. [Vote](https://hivesigner.com/sign/update_proposal_votes?proposal_ids=%5B%22199%22%5D&approve=true) for [our proposal](https://peakd.com/me/proposals/199)!
👍  , ,
properties (23)
authorhivebuzz
permlinknotify-dan-20220716t003539
categoryfractally
json_metadata{"image":["http://hivebuzz.me/notify.t6.png"]}
created2022-07-16 00:35:27
last_update2022-07-16 00:35:27
depth1
children0
last_payout2022-07-23 00:35:27
cashout_time1969-12-31 23:59:59
total_payout_value0.014 HBD
curator_payout_value0.015 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length847
author_reputation369,445,062,577,769
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,895,359
net_rshares51,072,261,630
author_curate_reward""
vote details (3)
@jaytaylor-node ·
properties (23)
authorjaytaylor-node
permlinkrf32sw
categoryfractally
json_metadata{"app":"hiveblog/0.1"}
created2022-07-15 22:36:36
last_update2022-07-15 22:36:36
depth1
children0
last_payout2022-07-22 22:36:36
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length10
author_reputation34,302,319,786
root_title"Fractally White Paper Addendum 1"
beneficiaries
0.
accounthiveonboard
weight100
1.
accountocdb
weight100
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,893,540
net_rshares2,015,376,192
author_curate_reward""
vote details (3)
@loviswater ·
It would be cool to have fractal observers could also rate, which could be shown before, after or during consensus.

Crowd sourced fact checking, and multiplying you n score.  Obviously this is a dream for sociology and psychology:). I knew that degree was a great pick.

Maybe for public or common goods meetings.
properties (22)
authorloviswater
permlinkrh05zw
categoryfractally
json_metadata{"app":"hiveblog/0.1"}
created2022-08-22 05:59:57
last_update2022-08-22 05:59:57
depth1
children0
last_payout2022-08-29 05:59:57
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length314
author_reputation7,905,281
root_title"Fractally White Paper Addendum 1"
beneficiaries
0.
accounthiveonboard
weight100
1.
accounttipu
weight100
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id115,925,733
net_rshares0
@lunaticpandora ·
How does this benefit Hive? Or are you just trying to use the fork of your old project as a launchpad for yet another project to leave behind?
👍  
properties (23)
authorlunaticpandora
permlinkre-dan-rf4gt2
categoryfractally
json_metadata{"tags":["fractally"],"app":"peakd/2022.05.9"}
created2022-07-16 16:36:39
last_update2022-07-16 16:36:39
depth1
children3
last_payout2022-07-23 16:36:39
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length142
author_reputation103,012,459,262,850
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,911,619
net_rshares2,328,939,990
author_curate_reward""
vote details (1)
@beerlover ·
<div class='pull-right'>https://files.peakd.com/file/peakd-hive/beerlover/yiuU6bdf-beerlover20gives20BEER.gif<p><sup><a href='https://hive-engine.com/?p=market&t=BEER'>View or trade </a> <code>BEER</code>.</sup></p></div><center><br> <p>Hey @lunaticpandora, here is a little bit of <code>BEER</code> from @isnochys for you. Enjoy it!</p> <p>Learn how to <a href='https://peakd.com/beer/@beerlover/what-is-proof-of-stake-with-beer'>earn <b>FREE BEER</b> each day </a> by staking your <code>BEER</code>.</p> </center><div></div>
properties (22)
authorbeerlover
permlinkre-lunaticpandora-re-dan-rf4gt2-20220729t210808801z
categoryfractally
json_metadata{"app":"beerlover/3.0","language":"rust","developer":"wehmoen"}
created2022-07-29 21:08:09
last_update2022-07-29 21:08:09
depth2
children0
last_payout2022-08-05 21:08:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length527
author_reputation25,840,105,692,251
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id115,267,321
net_rshares0
@isnochys ·
Thank you for your [witness vote](https://hivesigner.com/sign/account-witness-vote?witness=isnochys&approve=1)!
 Have a !BEER on me!
To Opt-Out of my witness beer program just comment STOP below
properties (22)
authorisnochys
permlinkre-re-dan-rf4gt2-20220720t211327z
categoryfractally
json_metadata"{"app": "beem/0.24.26"}"
created2022-07-20 21:13:30
last_update2022-07-20 21:13:30
depth2
children0
last_payout2022-07-27 21:13:30
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length194
author_reputation47,808,087,300,108
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id115,030,878
net_rshares0
@isnochys ·
Thank you for your [witness vote](https://hivesigner.com/sign/account-witness-vote?witness=isnochys&approve=1)!
 Have a !BEER on me!
To Opt-Out of my witness beer program just comment STOP below
properties (22)
authorisnochys
permlinkre-re-dan-rf4gt2-20220729t210753z
categoryfractally
json_metadata"{"app": "beem/0.24.26"}"
created2022-07-29 21:07:57
last_update2022-07-29 21:07:57
depth2
children0
last_payout2022-08-05 21:07:57
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length194
author_reputation47,808,087,300,108
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id115,267,314
net_rshares0
@machnbirdsparo ·
$0.03
"Told you there was a token plan"

"So we aren't just meeting to celebrate blockchain and gossip about how much faster we are than PoW... hmm... Oh great, room is going to get crowded..."
👍  , , ,
properties (23)
authormachnbirdsparo
permlinkrf47sl
categoryfractally
json_metadata{"app":"hiveblog/0.1"}
created2022-07-16 13:21:57
last_update2022-07-16 13:21:57
depth1
children0
last_payout2022-07-23 13:21:57
cashout_time1969-12-31 23:59:59
total_payout_value0.014 HBD
curator_payout_value0.014 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length187
author_reputation40,531,821,560,157
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,907,559
net_rshares50,222,311,119
author_curate_reward""
vote details (4)
@machnbirdsparo ·
"The net effect is that unless you believe that you are likely to achieve Level 4 to 8 in Round 2 then you have nothing to gain by being promoted."

Interesting and I believe original, and upon initial consideration, likely effective.
👍  ,
properties (23)
authormachnbirdsparo
permlinkrf48j0
categoryfractally
json_metadata{"app":"hiveblog/0.1"}
created2022-07-16 13:37:48
last_update2022-07-16 13:37:48
depth1
children0
last_payout2022-07-23 13:37:48
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length234
author_reputation40,531,821,560,157
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,907,854
net_rshares17,842,294,305
author_curate_reward""
vote details (2)
@mattlangston ·
$0.03
Feedback and clarification on this paragraph:

“We can therefore assume that any given measurement has a wide margin of error and that many measurements are required in order to get a more accurate measure of community consensus.”

This assumption requires clarification since repeated measurements only reduce statistical error.

There are two types of measurement error: 1) statistical error 2) systematic error

All measurement error is a combination of these two types of error and needs to be characterized and quoted separately in order to judge the merits of a proposed change to an experiment and its experimental apparatus.

Statistical error can only be reduced by adding additional measurements, while systematic error is always constant regardless of the number of measurements and is inherent to the experimental apparatus.

Systematic error can only be reduced by improving the experimental apparatus, which is part of what “Fractally White Paper Addendum 1” is proposing.

The proposed changes in this blog post hypothesize that reducing measurement error (a good thing) will be accomplished by reducing the systematic error (another good thing) by improving the experimental apparatus through the addition of a “high-pass filter” (aka a “high-value contributor filter”) to reduce low frequency noice (another good thing) in the form of a sliding/rolling window with the addition of a second consensus round populated with an improved source of signal.

The addition of a second consensus round improves the statistical error since it adds additional measurements to the experiment.

In conclusion, the proposed changes hypothesize that changing the experimental apparatus improve both the systemic error (through structural changes) and statistical error (through the addition of additional measurements).

I support the principle behind these changes when looked at through this perspective.

Someone (maybe me) could create a simple “measurement error calculator” for the fractally team to help them understand the pros and cons of this and future proposals. I would value this contribution. I may build this calculator unless someone beats me to it (which I encourage).
👍  , , ,
properties (23)
authormattlangston
permlinkrf4uhv
categoryfractally
json_metadata{"app":"hiveblog/0.1"}
created2022-07-16 21:32:45
last_update2022-07-16 21:32:45
depth1
children0
last_payout2022-07-23 21:32:45
cashout_time1969-12-31 23:59:59
total_payout_value0.014 HBD
curator_payout_value0.014 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length2,188
author_reputation428,906,950,775
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,917,279
net_rshares51,977,199,793
author_curate_reward""
vote details (4)
@mattlangston ·
Will there be an upcoming Genesis vote for the proposal in this blog post that is an all-or-nothing up-or-down vote by the Level 6 contributors from an upcoming weekly consensus meeting?

I think the answer is yes according to the [Interim Group Consensus Process](https://hive.blog/fractally/@dan/genesis-fractal-branding-and-interim-group-consensus-process). Is that right?

Here is the relevant section from this blog post.

> ### Reaching Consensus without a Council
>
> While the Genesis Community is still developing we lack enough people to form 12 teams of 12 as envisioned by the ƒractally white paper, yet we still need the means to reach consensus for community-wide decisions. Our current process is ad-hoc and we can do better. So I propose the following interim process for making community-wide decisions:
>
> 1. Before each weekly meeting any member who has previously ranked 5 or 6 for at least 3 weeks may introduce a proposal for consideration by the community. This proposal shall be posted as a link in the comment section of the hive post where we record the consensus results that week. Each qualifying member may only propose one item per week.
> 
> 2. After each weekly meeting (on the same video call), those who rank 6 may discuss the proposal, and if they approve they can reply to the comment with "Approve" or "Reject". If 2/3 of those who rank 6 that week approve then the proposal passes.
> 
> 3. If 2/3 of the Rank 6 fail to reach a consensus within 1 hour to either Approve or Reject then the Rank 6 individuals lose the respect they earned that week.
>
> This is an interim process can serve until modified using the same process or the automated workflow on fractally.com is ready.
properties (22)
authormattlangston
permlinkrf8s98
categoryfractally
json_metadata{"links":["https://hive.blog/fractally/@dan/genesis-fractal-branding-and-interim-group-consensus-process"],"app":"hiveblog/0.1"}
created2022-07-19 00:34:36
last_update2022-07-19 00:34:36
depth1
children1
last_payout2022-07-26 00:34:36
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,717
author_reputation428,906,950,775
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,972,299
net_rshares0
@mattlangston ·
Here is [the answer to my question](https://gofractally.com/posts/fractally-white-paper-addendum-1/comments/65547350?utm_source=manual):

> Yes, it will be all or nothing. Although, Dan could possibly be persuaded to make a last minute update before the official proposal. And of course, we can make changes and adjustments after the proposal is accepted (assuming it will be).
properties (22)
authormattlangston
permlinkrfa5s9
categoryfractally
json_metadata{"links":["https://gofractally.com/posts/fractally-white-paper-addendum-1/comments/65547350?utm_source=manual"],"app":"hiveblog/0.1"}
created2022-07-19 18:24:09
last_update2022-07-19 18:24:09
depth2
children0
last_payout2022-07-26 18:24:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length377
author_reputation428,906,950,775
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,991,715
net_rshares0
@mireyalara ·
$0.03
This is a great job. Looking for a fairer classification is not an easy ask, however I believe that with their proposal you make a significant change. 
👍  ,
properties (23)
authormireyalara
permlinkre-dan-2022715t221023646z
categoryfractally
json_metadata{"tags":["fractally"],"app":"ecency/3.0.30-mobile","format":"markdown+html"}
created2022-07-16 03:10:24
last_update2022-07-16 03:10:24
depth1
children0
last_payout2022-07-23 03:10:24
cashout_time1969-12-31 23:59:59
total_payout_value0.014 HBD
curator_payout_value0.014 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length151
author_reputation7,607,902,438,816
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,897,929
net_rshares48,699,757,394
author_curate_reward""
vote details (2)
@poshtoken ·
$0.01
https://twitter.com/Steemadi_/status/1548256058468343808
<sub> The rewards earned on this comment will go directly to the people( @steemadi ) sharing the post on Twitter as long as they are registered with @poshtoken. Sign up at https://hiveposh.com.</sub>
👍  ,
properties (23)
authorposhtoken
permlinkre-dan-fractally-white-paper-addendum-111345
categoryfractally
json_metadata"{"app":"Poshtoken 0.0.1","payoutToUser":["steemadi"]}"
created2022-07-16 10:40:00
last_update2022-07-16 10:40:00
depth1
children0
last_payout2022-07-23 10:40:00
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.014 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length257
author_reputation5,752,067,431,016,473
root_title"Fractally White Paper Addendum 1"
beneficiaries
0.
accountreward.app
weight10,000
max_accepted_payout1,000,000.000 HBD
percent_hbd0
post_id114,905,047
net_rshares47,958,044,478
author_curate_reward""
vote details (2)
@shakhruz ·
Перевод на русский язык Дополнения 1 к Белой Бумаге Фракталли - https://hive.blog/fractally/@shakhruz/belaya-bumaga-fractally-dopolnenie-1

Подписывайтесь на [мой телеграм канал](https://t.me/ashirov_public) чтобы узнавать подробнее о Фракталли и многом другом.
properties (22)
authorshakhruz
permlinkrfs49n
categoryfractally
json_metadata{"links":["https://hive.blog/fractally/@shakhruz/belaya-bumaga-fractally-dopolnenie-1"],"app":"hiveblog/0.1"}
created2022-07-29 11:08:12
last_update2022-07-29 11:08:12
depth1
children0
last_payout2022-08-05 11:08:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length261
author_reputation147,356,721,811
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id115,255,751
net_rshares0
@topsouls ·
Me encanta el post, ahora lo leeré.
👍  
properties (23)
authortopsouls
permlinkre-dan-rf3tm6
categoryfractally
json_metadata{"tags":["fractally"],"app":"peakd/2022.05.9"}
created2022-07-16 08:15:42
last_update2022-07-16 08:15:42
depth1
children0
last_payout2022-07-23 08:15:42
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length35
author_reputation7,527,340,477
root_title"Fractally White Paper Addendum 1"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id114,902,176
net_rshares2,144,367,762
author_curate_reward""
vote details (1)