The Internet Computer should allow canisters to control ICP neurons

The 2 proposals have passed and the 2 neurons have been created :partying_face:

They currently only have stakes of 1 ICP and zero dissolve delay but we will submit proposals to increase their dissolve delays to 6 months and 8 years respectively, configure their following, and top them up with more ICP.

3 Likes

Just saying the OpenChat dashboard should be updated to display the neurons that the treasury controls. This info is currently missing. Maybe one day most icp in SNS treasuries will be handled this way

1 Like

Why would you risk the whole treasury in ICP? Thats pure insanity from a treasury management perspective.

1 Like

What do you mean by ‘risk the treasury’?

See the proposal details here - OpenChat Proposal: 492 - ICP Dashboard

Enough ICP is being left liquid to maintain OpenChat for at least ~2 years (provided ICP price doesn’t crash significantly).

Exactly. This can depend on the entire market btw as all prices are correlated, it doesnt have to involve ICP going to shit. Are you keeping 100% of your own money in ICP?

Am not calling out open chat, do whatever you want. Simply saying that it might not be such a great idea to bet your entire business on ICPs price.

1 Like

OpenChat’s treasury is made up of ICP and CHAT.

If we don’t stake some ICP into neurons we’re still reliant on the price of ICP not crashing.

By staking some of the ICP it means that we will have more ICP available overall and so are more resilient to price drops.

1 Like

So wait for stablecoins. No, do whatever you want. I just dont think its worth breaking the time aspect of staking just so people can earn yield from insane treasury management practices.

Hi Hamish,

I don’t know rust, but I think I can make out roughly how you got it working and it’s a pretty cool but hacky looking solution (I understand it has to be - due to the restrictions). Correct me if wrong but it looks like the canister talks to the neuron via the off chain ic-api:

request_url: format!("{IC_URL}/api/v2/canister/{nns_governance_canister_id}/call"),

This is a limitation right? If tommorow the api goes down - the canister can’t communicate with it anymore. That would mean the neuron and the funds are stuck?

Just wondering if you considered this and how would openchat get control back of the neuron if that happens (if it can happen).

That sends the request via an HTTP out call to the boundary nodes.

If the boundary node url changes for any reason that’s still fine, we’ll just need to update the canister to point to the new url.

2 Likes

You can view the full neuron details here - https://tktqu-nyaaa-aaaar-qackq-cai.raw.icp0.io/neurons

These details will be refreshed every 24 hours.