can some1 help me w/ mac throne setup?
watching project now and got myself some coins
thx
Here is a fast guide to setting up a throne on a Mac.Open your wallet
Click file->receiving addresses
Right click an address, or create a new one and right click that and copy address.
Go to the sending page and paste the address into the pay to section.
Send exactly 10,000 CRW to the address.
Go to the debug console (help->debug->console) and enter "throne genkey".
The output from that command is your throneprivkey. Copy it.
Brows to /Users/
/Library/Application Support/Crowncoin/
Open the file crowncoin.conf. If it is not there, create it yourself.
In your crowncoin.conf, enter:
throneprivkey=XXXXXXXX
throne=1
Replace the XXXXXXXX with the throneprivkey you just got.
You may also need to add:
throneaddr=
You may as well just put it there for good measure. You can find your ip by googling "Whats my ip?"
Restart the wallet and run "throne start" in the console (help->debug->console), and you're done.
(Written by stakebox, edited by me)
My windows wallet guide video is probably going to be out very soon.
Man i can't thank you enough for doing this, im not having a go here!
Theres a few issues with the setup guide..(not the guide itself but the reaults of it)
This sets up a throne on your local machine.
This limits you to only one throne. Crowncoin requires one unique ip address per throne. So using your home ip limits you to one throne. Also, if you power down your local machine your throne will go offline.
Having your throne connected to a VPS allows you to power down your pc and still run the throne.
Another issue is this creates an unstable full node network, not what we want.
I don't feel comfertable pointing people to this guide, its not best practice
I completely understand your opinion on this but maybe we should encourage people to set up how they prefer...they will probably want to update to a vps setup in the future when they realise they don't get paid when their PCs are turned off.
Maybe sensible to encourage people to take the easy option...I don't think it will be a problematic majority. We can always still advise to go the VPS route.
How about we implement masternode health scoring in the next version?
