# Tackling CertifiedData in Motoko **URL:** \ **Category:** Language Support\ **Tags:** Motoko\ **Created:** [August 3, 2021, 12:17am UTC](https://forum.dfinity.org/t/tackling-certifieddata-in-motoko/6272 "2021-08-03T00:17:10Z")\ **Posts on this page:** 1\ **Showing post:** 36
**Author:** ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)\ **Post date:** [August 18, 2022, 10:08am UTC](https://forum.dfinity.org/t/tackling-certifieddata-in-motoko/6272/36 "2022-08-18T10:08:28Z")
> [@LightningLad91](#): > > I would like to draft a governance proposal requesting that DFINITY add this feature to their roadmap, or at least consider it in their horizon planning. I’m just not sure how that process works now given recent discussions on the topic. I want to respect y’alls processes. > [@Proposal: Remove the is\_self\_authenticating restriction on Neuron Ownership](https://forum.dfinity.org/t/proposal-remove-the-is-self-authenticating-restriction-on-neuron-ownership/14948): > > Given the upcoming t-ecdsa functionality going beta, and the HTTP interface enabling using canister signatures( [Tackling CertifiedData in Motoko - #32 by bjoern](https://forum.dfinity.org/t/tackling-certifieddata-in-motoko/6272/32)), the restriction on canisters not being able to hold neurons is a merely an inconvenience. A good bit of code needs to be written to enable either t-ecdsa ownership of neurons or certificate ownership. To avoid wasted effort, we recommend removing the restriction at the following lines that will enable canisters to hold neurons(deleti… --- _[View the full topic](https://forum.dfinity.org/t/tackling-certifieddata-in-motoko/6272)._