I have been playing with thrones on AWS using micro instances of Ubuntu 16.04...

I stopped one of the thrones yesterday and put some dummy info into the Crowncoin.conf file and took an image of it.  Copied that image to all the other geographies I saw on AWS and made all those images public.

In the short term this is definitely not in my best interest for increasing the amount my thrones mine... but I'm not worried about that -- I am a newbie and learning from working with the coin and the software and it's not worth anything if we all don't help build the community around it and uses for it... and part of that is making the throne setup easier.  

Generally speaking, if you have your throne on a platform where you can take an image, you can launch a new instance from that image and then just update the crowncoin.conf file and restart crowncoind to sync the blockchain, and voila -- you have a new throne server set up (you still need to go back to the local wallet and start the throne to associate your wallet with the remote server so you can receive payments)...

Literally, if you want to play with AWS or already know it... log in and go to EC2 and launch an instance.  You will be able to choose from different sets of images, click the COMMUNITY AMI tab and then search for "CRW" -- the images I put out there are titled "CRW-THRONE-PRELOAD" and are listed as being "other Linux" operating system -- probably just because in building the throne we made modifications to the original Unbuntu.

In the next step you choose the size/power etc of your instance.  To build the new throne I had to use a "small" instance due to memory limitations, but the images can be installed and run on a "micro" instance -- so once I had the throne installed I took a snapshot and launched a new micro instance and have been running thrones on AWS as micro instances.  If you are new to AWS you may be eligible for "free tier" services -- which really just means that you get 750 hours a month for your first year free and the micro instance is eligible for the free tier -- so this basically translates to something like getting your first throne free and then it looks like the cost is around $10 per month per throne based on how my daily AWS bill is stacking up...  which isn't cheap - but if you can save hours spinning things up and this also makes you more agile when the upgrade goes out -- it could be worth it...  I'm new to all this and just learning.

Follow the AWS instructions for connecting to your instance (and if you have issues check you security setting in AWS -- they have their own firewalls outside the instance firewalls and you want to set those in a parallel fashion to the way the throne set up instructions limit access to port 22 and open up port 9340).

Once logged in to your instance type (what's to the left of the ">" is just symbolizing the prompt):
~> cd .crowncoin
~.crowncoin> nano crowncoin.conf

[this will open the editor and you can update the rpcuser, rpcpassword, external ip & throne private key to what you need or want them to be.]

type ctrl + o, and then return to save your changes.
type ctrl + x to exit the text editor.

~.crowncoin> chmod 444 crowncoin.conf

[locks the crowncoin.conf file]

~.crowncoin> cd
~> cd src/crowncoin/src
~src/crowncoin/src> ./crowncoind

[at this point is should tell you that the crowncoin server has started and it is syncing the blockchain... the good news is that it already has the blockchain up to 10/12/2016 -- so this shouldn't take long.]

if you want to check on the progress of the sync just type "./crowncoin-cli getinfo" -- but if you are trying to operate at peak efficiency, if it said the server is started it's started so now you can leave the session and go to your local wallet.  If you had already updated your throne.conf file there -- then just go to Help > Debug and click on the Console tab...

At the prompt in the console tab, type:
>throne start-alias [throne alias in quotes] [WalletPassPhrase]
such that if the throne alias were "Jack" and the passphrase were "Jill" (always fun to use the subjunctive case) you would type:
>throne start-alias "Jack" Jill

the console should inform you of your success... and if it doesn't, either you or I missed something...

This is my first time posting a Community AMI on AWS -- so I am kind of curious if it works.  What is of value to me is your trust and just making the world a little less frustrating -- so if this helps you and makes the throne set-up process easier -- that's awesome.

-UI

Filipino translation of this ANN can be found here: https://bt.irlbtc.com/view/1645906.0
kindly check and acknowledge.
long live the CROWNCOIN!

sent PM.

coinexchange.io has a pretty nice peer info page https://www.coinexchange.io/network/peers/CRW

I am personally looking forward to the new QT wallet look!

Just a bit more detail on the update on the Bitcoin core update.  We're aiming for 0.12 but getting there incrementally.  Work on the code is progressing brilliantly but we think we are going to need at least a month of testing before release. If I factor in some slack I expect that we will be releasing a wallet with new Bitcoin core in December.

Whilst we are updating the Dash code for Thrones, we are also making other changes to the service network. Some of these changes are standalone improvements to the solid foundation that Dash provides but others are going to be much more radical. I'll be sharing more details on this soon. Dash works very well indeed but we think there some things that need to be improved and some new features in order to support our roadmap.

What is the current price of CrownCoin?

Thanks alot!

750 CRW paid
216f032b5fa60dc061d564d00264a99d6cbf31a1d8ad717374dfb335912ce6d8

I'm not sure you updated the 'wallets' section to latest, this is the most important, thanks.

Not quite, your crowncoin.conf should look like this:

rpcuser=
rpcpassword=
listen=1
server=1
daemon=1
externalip=
throne=1
throneprivkey=

The only place for throneprivkeys and IPs is in throne.conf

EDIT:  You also don't *need* to have listen=1 in your crowncoin.conf.  It will only increase network traffic on your home connection and offer no benefit to the network when we already have 230+ full nodes.