Motion Request for Neuron Indexing

can you elaborate a bit around the internal discusssion of @rossberg points made earlier?

1 Like
  1. I believe it to be true that every neuron has a unique id, although I would need Dfinity to veridy this.
  2. I know of no way to tie a neuron id to its owners’ Principle ID for neurons created after Genesis. For Genesis neurons, I believe it is possible because I remember seeing them tied together on
  3. This is correct as far as I know. However a createdOn datetime is recorded when a neuron is created. I wonder if it’s possible to use that datetime and the ICP transaction history to figure out the account number feeding the ICP to the new neuron… seems like that might be possible.
  4. Currently the governance canister contains the voting history for recent proposals for each neuron. You can see this on the governance tab of the ICA dashboard (also accessible via the API for the dashboard). Of course, this is only true for known neuron ids (which is mostly genesis neurons)
1 Like

Probably a conversation for another day, but i think theres a good argument that recent voting history should be mandatory public. It would allow anyone to conduct a “recount” of any recent proposal and provide a second verification beyond the nns code audit. The real life example would be the equivalent of allowing hand recounts in democratic elections where the vote tally is close or there is reasonable doubt regarding the operation of a voting machine.

I think there are steps we could take to both protect privacy of neuron holders and increase transparency of neurons themselves.


Yeah, that’s a good point. I do hope there is further discussion on these ideas.

I thought DFINITY was going to abstain from voting on governance proposals. DFINITY and the ICA have been voting on multiple governance proposals recently. What has changed? Did DFINITY/ICA announce this change?


The foundation considers a motion proposal by the community a mandate to work on a topic and feed that topic into the roadmap process. As part of that process, a topic is first scoped, meaning it is investigated what the topic actually entails and how it can be realised. Part of that scoping is a conversion on this forum and then eventually another motion proposal to agree on the scope. We are preparing a blog post on how the foundation aims to manage the roadmap and how to work with the community on the roadmap and individual features such as working groups etc. So please bear with us for a bit for a better answer. Thanks!


A blog post in the the works on this.


This is great, thank you. I’m glad the foundation is thinking about these things.

1 Like

I’ve summed up my concerns that surfaced from engaging with this proposal: Formalization of proposals process

1 Like

Agree that transparency / equal access to this information is needed.

1 Like

@diegop @Kyle_Langham

The work you’ve done producing visibility into DFINITY neurons and voting power is amazing, and I want to thank you for this.

Any update on how or when this Neuron Indexing Proposal work (which passed last month on the NNS) might fit into the DFINITY roadmap for the next few quarters?


Hi all, (for context, I am a researcher in the NNS team)

Please know that this feature is on the NNS team todo list.
As we are at the last mile of the SNS feature, which is the big feature scheduled for the Carbon milestone, the NNS team is focused on shipping the SNS. We might thus only get to the neuron list afterwards.
I hope that makes sense. Please let us know if you have more questions!


No worries on my part… I believe the SNS is a more important priority.

The new neuron charts on the dashboard (and the governance canister capturing that data) provides a lot of value in the meantime.

Thanks for the update!