When running
dfx sns propose --neuron-id=15949719352790841058 sns_init.yaml
I get the following error:
Any help appreciated.
Thanks,
James
1 Like
Maybe you’re asking for too much ICP? I dunno
1 Like
Hi @jamesbeadle we identified the issue and are working on a fix.
2 Likes
I don’t think the command cares about my min raise figure.
I no doubt have gone to high, better to go too high than too low though. I am happy to change to valuing the DAO in another way, please tell me how to do this as a discounted cash forecast method was applied.
Hah, sorry. Based on what I know about previous SNS raises though, I think a minimum of 150-200k ICP is probably a better idea. Remember the price has gone from $3 to $15 over the past six months and investors are still adjusting.
I don’t think the majority of SNS investors would look at a traditional business valuation to be honest, well I wouldn’t as I don’t understand them.
My advice would be to raise less and leave room in the tokenomics to support future raises. The questions I’d ask are more along the lines of “how will you cope when ICP is X price, and when your token is Y price”. We are riding a rollercoaster.
I completely understand why you would say that. Sure the price of $ICP has gone up but it’s not like the value of the services on the network don’t go up proportionally.
I think my setup is fine and a bit different to previous SNS raises. 80% of what I raise gets staked, I’ve got a lot more to setup than most DAO’s, marketing, merchandising etc… my game starts in August, not in a few years so just a ton to do.
If / when it fails I will at least have a rough idea of what the amount I can raise is and then can prepare a roadmap according to that figure.
2 Likes
When updating dfx I didn’t realise I needed to reinstall the extensions so I’m back to the same issue:
Perhaps you could try using a pem file without a password
dfx sns propose --network ic --neuron $NEURON_ID sns_init.yaml
Nah network isn’t an allowed option:
Also --neuron is actually neuron-id so not sure the docs are accurate or if i’m using the correct library.
Hi @jamesbeadle - the first half of the fix has been implemented in this PR. We are still working on the second half and will keep you posted.
Shouldn’t take long but it will be approx three weeks to get a new dfx release out during our release window (March 25-28). You can of course get the cutting edge by cloning and building locally, but the easiest thing to do is just use a plaintext identity instead of an encrypted one for local testing.
is the dfx server running (dfx start --background) ?
That is ridiculous, I am not looking to deploy locally (for the 20th time), testing is done, I am looking to being the SNS sale.
I have dozens of people waiting to promote, my project is nearly a year old, the code is done.
For me to not be able to begin the sale is insane?!?! Is that the point we are at now! How am I supposed to raise the money if I can’t plan things.
Again, I want to deploy the live SNS
Did you try with the network flag?
At least according to the sns-testing repo this should work: sns-testing/propose_sns.sh at 50dc6ee9fd997f71d6f907ebee3093c507797b00 · dfinity/sns-testing · GitHub
So this has been solved by remcodes.
So the steps I had to take:
- use an internet identity without a password
Use the following dfx command to pass the network:
$(dfx cache show)/sns propose --network=ic --neuron-id=15949719352790841058 sns.yml
3 Likes
glad it got sorted, and congratulations on the sale.