Dfinity Neurons Publicity Request

Developers
1

Dear @dfinity team,

Please make voting transparent for all Dfinity/ICA neurons by setting the visibility of the following neurons:

• 1–26
• 29–81
• 1000–1141
• 2000–2055
• 3000–3039
• 4000–4037

Neuron IDs are sourced from vpgeek.app.

(Set visibility to 2)

@diegop please comment.

Thank you!

2

Apologies for the follow-up. @domwoe , if you have a moment, I’d be grateful for any guidance on this. Thank you!

3

Hi @pixld8ta, it’s a great idea and community movement on your part!
People’s votes are usually private (see yesterday’s USA presidential election), but if you’re a politician or an influential institution, it’s worth letting people “watch your hands” and clearly communicating your views to avoid speculation (see Elon Musk).

Based on your request, feedback from my coworkers and other members of the ICP Hub Poland community, this NNS proposal has been submitted :slight_smile:

4

Thank you @pixld8ta for your suggestion, and @krzysztofzelazko for submitting an according motion proposal.

DFINITY’s perspective is as follows:

The motion proposal 133995 does not concern a change to the Internet Computer Protocol itself, but rather it suggests a modification in the behavior of an ecosystem participant (in this instance, DFINITY). In line with our voting guidelines, DFINITY will reject the motion proposal.

However, DFINITY is supportive of the underlying intent to make voting more transparent. To this end, DFINITY plans to make all its neurons public that hold significant voting power. Please note that neurons 27 and 28, which are most material in terms of voting power, are already public.

5

DFINITY could have waited closer to the end of the voting period to cast theirs, but I think we all know that would look bad on the chart :wink:

Anyway, thanks @bjoernek for your comment!

6

Hey @bjoernek,

Sorry, but I’m not quite following…

According to the guidelines in the proposal:

  1. Tangible - The proposal should be understandable and concrete.
    This proposal is very concrete—just set visibility to true.

  2. Achievable - The proposal should be something DFINITY believes is achievable.
    Definitely achievable! DFINITY already has plans for it.

  3. About the IC and in the interest of the IC
    Absolutely—this is a clear win for the community!

So it checks all three boxes, right?

2 Likes
7

As mentioned above, according to our voting guidelines, we believe that motion proposals should focus on changes to the protocol itself rather than prescribing actions for specific community members. Here are some relevant quotes from the forum post on the voting guideline

  • “NNS is intended to control the IC. NNS should not be used to make other community entities actively do X, but to improve the IC.”
  • "Furthermore, there should be a “path from proposal to code running on the IC”. This means that an NNS proposal to add a copy on the NNS Frontend Dapp to help new stakers would be valid… but an NNS proposal to “ask entity X to change their website to help new stakers” would not be valid.