The conversation on this thread about the economics of our solution is going to be extremely entertaining. Deep down, I have very high confidence that the pieces of the puzzle fit together very nicely but I'll be more confident once the puzzle has been pulled apart and reassembled by greater minds than ours.

You're right.  We have a technical solution.  Only one way to find out if its works economically.

Glad to have you keeping an eye on us mate 

There will always have to be a way to cryptographically secure a blockchain and control the emission of coins. To that extent, mining isn't going anywhere.  Its just going to change shape.

In the predicted future of millions of decentralised blockchain services and applications, do you really think that it will be secured by millions of ASICs chomping through natural resources and taking up space?

Something like 60% of the Bitcoin network is based within 30mi of the 3 Gorges Dam. What is the cost of entry for a Bitcoin miner to set up large enough to turn a profit?

Whats the deal with X11? An ugly solution to one problem which has lead to an algorithm that is designed to be as inefficient as possible? How does that fit into the modern world?

If you ignore the fact that Crown is merge mined, it would cost $4,000 per hour to pay the fuel bill to mine Crown alone. I'm not sure I have enough digits on my calculator to work it out for Bitcoin.

There needs to be another way for blockchain to continue developing to the point of mass adoption.

For me to post here and say WE HAVE THE SOLUTION would be wrong.  That would be like me saying hey, the internet has reached peak development and be like this in 20 years time. It would be total bullshit...I just couldn't back up such a claim.  Why would technological progress just suddenly stop?

What I can say is that we have is a feasible and practical alternative to Proof of Work and Proof of Stake that we believe solves the major problems with those protocols.

EDIT:  Went on a bit of a posting rant.  Consolidated three messages into one. Normalisation ftw.

Well, I didn't sleep at all last night. What we have planned is still sinking in.

It looks like we're holding a meeting in London in the first week of December. Our team is spread from Vancouver to Sydney and lots of places in between so we'll be earning some airmiles for sure.

Looks like a few more people are buying CRW but still nobody selling. I wonder when the dam will burst?

We've just announced a two year programme of work.  I'm pretty glad that we haven't just gone to the moon based on one update.

Reserved

Update 17th October 2016

Building Foundations.

Progress continues on the Bitcoin Core update and our improvements to the Throne/Masternodes system. We expect work on the core update and service network improvements to continue throughout November with testing and release anticipated to happen in December 2016.

Service Network Growth.

The number of Thrones operating on the Crowncoin network grew to a record high of 276 in the last week. If you own 10,000 CRW we encourage you to operate a Throne to help us achieve our long term objectives. At current spot price a Throne generates about 20 USD profit per month after your hosting costs are deducted. If you need help setting up a Throne please ask on the BCT thread or contact Chaositec to take advantage of his excellent Throne hosting service.

Rebranding.

Crowncoin is to be renamed Crown to formalise the change in direction since it was launched in 2014. Defunctec and Crowncoin Knight will be leading this work and engaging the community separately. The decision has also been made to abandon our European centric theme while being sure to acknowledge and remember the origins of this project.

New Team Member.

The Crown core team has been joined by Urban Idler who brings with him a successful career in the US equity markets and a clarity of mind that is already helping the Crown team develop our future services. Being able to attract the likes of his talent and expertise is an honour for the Crown team.

Introducing Crown Revolution.

The Crown team are excited to announce Crown Revolution, a programme of work that is expected to begin in Q1 2017 and complete in Q4 2018.

Crown Revolution is a series of revolutionary releases that we believe will reshape the future of blockchain

Over the last two years, Chaositec, who is the architect of the concept, has been refining his vision and our preparations have reached the stage where the delivery phase can begin. We're delighted that the Crown network is where Chaositec's vision is going to be realised. Crown Revolution will be delivered in two stages.

Crown Revolution Stage 1

Crown Revolution Stage 1 will be a game changing improvement to the network. Currently, the vast majority of blockchain projects are secured by either Proof of Work or Proof of Stake. The Crown team do not believe that these two methods are the future of Blockchain. We have a third way.

Crown Revolution Stage 2

Crown Revolution Stage 2 will see the implementation of a solution to the blockchain block size problems and transaction volume limits that conventional blockchain technology is susceptible to. Stage 2 will also provide an API that will allow developers to deploy services using Crown Revolution.

Programme Approach

A series of reports and white papers will be written to explain the rationale and method behind the Crown Revolution vision and milestones. The release of these papers will be carefully timed to minimise the risk of losing our first mover advantage.

In addition to these reports and whitepapers we will continue to provide detailed updates as regularly as we have have something to share.

The team will choose a lightweight management methodology to use during the course of the programme of delivery. This will be announced at a later date.

In order to make this a success we need a strong community behind us and we recognise how essential regular open and honest communications are. This is a two year programme of work. There will be breakthroughs and setbacks and we need you with us all of the way.

We remain indebted to you for your support so far.

The Crown Team.

Our meeting went very, very well.

We are going to present our plans to the core team at 1700 UTC and if agreement is unanimous, I will be posting a special update several hours after that.

If you could contact Bittrex by email or twitter to ask that we are listed it would be appreciated.  They are currently observing us from a distance.

Thanks for setting that up. 

We're not too sure which pools merge mine Crowncoin at the moment but we've noticed our network hash rate exceed 4PH/s on a fairly regular basis so we're fairly sure it isn't just zpool mining CRW.

Is your pool only mining CRW?  Would probably make sense if you were mining other Sha256 coins with it too!

I think we currently have a liquidity problem. Nobody wants to sell their coins. I'm doing what I can by market selling my throne payments as they come in. Maybe the miners will be selling soon too.

If anything, it's a sure sign that crw is underpriced.

If you don't mind the relatively high hosting fees, setting up a Throne on Amazon is almost as easy as point and click thanks to urban_idlers efforts.

You can now build a VM with a prebuilt Crowncoin image in every Amazon region around the world.

ROI in less than one year IF the price doesn't increase.  I think it is likely that the price of CRW will increase over the next year 

Anybody who has 10,000 CRW can host a throne.

This would cost you approximately $150 to $200 at current market prices.  You would receive $20 per month income, after your throne hosting fees.

Throne owners selling some of their income. It's good...gradually improving liquidity

BOUNTY ANNOUNCEMENT

Somehow, Crowncoin has managed to survive thusfar without a Testnet! All testing to date has been done in hacked together sandbox networks.

I am offering a 3,500 CRW bounty to the first person to generate a Testnet genesis block and make the necessary changes to the code on github for us to test and include in next release. Our devs have it on their list but have other priorities right now and I'd rather get it in place sooner rather than later.

If you are planning on doing the work, please post here to say so in order to minimise the chance of duplication of effort.

Bounty will be paid once pull request is made, discussed and tested.

Its always nice to receive an email from Github showing quite how hard the dev team are working away 

Getting there step by step.

Commit Summary:

gitian: make linux qt intermediate deterministic
Qt: Fix monospace font in osx 10.9
rpc: Ignore and log errors during cancel
rpc: Add acceptors only when listening succeeded
Bump version to 0.9.2.1
Remove NumBlocksOfPeers
Version bump for 0.9.3
Don't poll showmyip.com, it doesn't exist anymore
Remove bignum dependency for scripts
AvailableCoins: acquire cs_main mutex
qt: fix 'opens in testnet mode when presented with a BIP-72 link with no fallback'
Avoid a segfault on getblock if it can't read a block from disk.
In -? output: -keypool, -gen, -genproclimit depend on ENABLE_WALLET
Clarify that redeemScript is often optional
Increase IsStandard() scriptSig length
Check redeemScript size does not exceed 520 byte limit
key.cpp: fail with a friendlier message on missing ssl EC support
Ignore too-long redeemScripts while loading wallet
base58: add paranoid return value checks
Update Debian packaging description for new bitcoin-cli
Add a new checkpoint at block 295,000
Add a way to limit deserialized string lengths
preliminary release notes for 0.9.3
Avoid querying DNS seeds, if we have open connections.
gitian: upgrade OpenSSL to 1.0.1i
qt: fix unicode character display on osx when building with 10.7 sdk
build: Fix boost build on some platforms
build: fix FDELT_TYPE configure check
libc-compat: add new symbol that's now needed
Update build-osx.md
gitian: Bump miniupnp version to 1.9.20140701
doc: Add list of contributors to 0.9.3
qt: Language update for 0.9.3
doc: mention translations in release notes
Add deeper XML checking to update-translation script
Filter translations through new update-translations script
Avoid repeated lookups in mapOrphanTransactions and mapOrphanTransactionsByPrev
Fix crashing bug caused by orphan(s) with duplicate prevout.hash
Limit CNode::mapAskFor
Avoid returning many "inv" orphans
doc: Remove outdated information about boost versions
build: Remove message about Ubuntu 13.10 when no boost sleep implementation found
remove useless millisleep
Stricter handling of orphan transactions
Make max number of orphan blocks kept in memory a startup parameter (fixes #4253)
Store fewer orphan tx by default, add -maxorphantx option
Update release notes
Update release notes
build: osx: Fix incomplete framework packaging for codesigning
Remove mention of MacPorts from OSX build docs
build: change cdrkit location in build-process.md
build: fix release name strings for gitian builds
osx: fix signing to make Gatekeeper happy (again)
Keep symlinks when copying into .app bundle
doc: Add instructions for consistent Mac OS X build names
build: Fix OSX build when using Homebrew and qt5
Refactor -alertnotify code
Make -proxy set all network types, avoiding a connect leak.
Limit the number of new addressses to accumulate
Disable SSLv3 (in favor of TLS) for the RPC client and server.
consensus: guard against openssl's new strict DER checks
gitian: openssl-1.0.1i.tar.gz -> openssl-1.0.1k.tar.gz
fail immediately on an empty signature
doc: Update release process for openssl bump
gitian: bump revision for OSX qt
Improve robustness of DER recoding code
qt: Pull updated translations from Transifex
doc: Update release notes for 0.9.4
Bump version to 0.9.4
doc: Properly format git commits in changelog
Implement BIP 66 validation rules and switchover logic
Backport of some of BIP66's tests
Raise version of created blocks, and enforce DERSIG in mempool
build: fix dynamic boost check when --with-boost= is used
Merge pull request #5780
Merge pull request #5762
Sanitize command strings before logging them.
Check pindexBestForkBase for null
Fix priority calculation in CreateTransaction
Merge pull request #5807
Final transifex pull for 0.9
Version bump to 0.9.5
build: fix osx determinism for OSX
Merge pull request #6169
Disable upnp by default
Revert changes
Dirty Merge 0.9 Bitcoin
Merge pull request #2 from Infernoman/dirty-merge-0.9
fix merge 0.9
remove keepass
Merge pull request #3 from Infernoman/dirty-merge-0.9
Fix dirty-merge-0.9
Fix dirty merge 0.9
fix dirty-merge-0.9
Merge master
Bump version
Fix dirty-merge-0.9

If Georgem put his code on github, I'm sure plenty of people would be submitting pull requests.

Each throne should receive about 6 or 7 payments a day.  Welcome to the throne holders club!

I don't think it will be long before they become even more profitable and much more expensive to buy 10k CRW.

lol, I sincerely hope that the signature campaign is only a tiny part of the recent price action