Topic: [ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 156. (Read 317079 times)

Moving up nicely today

I want to see the Crown platform offer an easy entrance into "blockchain" for businesses that want to dabble in the technology and scale if they want to. I think different people and groups will take responsibility for different aspects of the application suite.  It is possible that the Crown legal entity will partner with companies already established in their respective fields.  Anyway, not too much I can say without divulging ideas I want to keep close to my chest for now.

In the meantime, testing, testing and more testing. I've got a new build machine arriving tomorrow.  Looking forward to tinkering with it.

Progress is impressive right now although I appreciate lots of it is behind the scenes. Kudos to infernoman for seemingly giving up on sleep to squash the last few bugs.

I think the denominations have been decided on already 

Nice suggestions though

Hello!!!

The smallest denomination of 1 CRW should be :

- CrownPenny ( pCRW or CRWp ) ,

- CrownCent   (cCRW or CRWc ).

I know, I'm a genius..

Good spot! We'll get added for sure

▲3.725 Ph/s

▲5.134 Ph/s

I'm looking forward to the future of Crown, small additions like travis are game changers for development.

Also looking forward to discussing the first proposal on where the governance funds should be spent, any ideas anyone?

Hey guys just letting everyone know where I'm at currently. I'm working on getting the build platform from bitcoin 0.13 implemented. The reason I'm doing that is for ease of use. Rather than having to build and test the clients on each individual OS. After I'm done all we'll have to do is test them. ARM, LINUX, OSX, and WINDOWS will be automatically built and from there released to Github. I've made good progress over the past day and am nearing completion of this.

Check out our Crown project history page! Moving up from a dream.

http://crown.tech/history

Slushpool proposal moving up again - 3.175 Ph/s now. Slushpool guys hopefully waiting for our new code, then we hopefully ready to go  

https://slushpool.com/proposal/detail/597/

Updates can be a ballache for sure.  Lets make sure we make this as easy as possible for people when testing is finished.

I have an issue with importing a wallet.dat into raspbian.

I have the wallet.dat on the OS, but I can't access /root/.crown to drop the wallet.dat into.

I know theres commands for this, but i'm really struggling!

Well a good night's sleep must have help me alot... I figured it out.

Without the ##

mv #path to wallet.dat# /root/.crown

Users tend to fall into these categories:


-Total newcomers to crypto (not many at the moment hopefully this is a growth crowd)
-Crypto users with some experience but who have never operated a Throne or Masternode before
-Crypto users with significant experience of Thrones/Masternodes.

We need to make sure we have all bases covered.

A good starting point would be to work on a series of guidance documents to be stored in the appropriate place.  (The Knowledge?) We can detail the basics through to more complex areas. 

I'm particularly interested in providing update scripts and instructions for effective and efficient compilation under Linux. We need to make it as easy as possible for people to update.  Step one for this would be to agree that we only use Git Master for upcoming releases.

One other thing I want to look into is a downloadable Raspberry Pi image containing Crown wallet, a recent sync of the chain and easy instructions on how to set up a throne.

Guys, insane job, well done. Website looks superb and the wallet too. Really looking forward to what comes next 

gz with new version)

Amazing effort of the Crown team!

White Paper
Summary
StoneHedge - urban_idler - Crown Team
January, 2016


In a series of 6 whitepapers, Crown outlines plans for a decentralised and incentivised application platform that will diverge from current Blockchain technology in a unique and revolutionary way.

The final product will be an open and decentralised application platform providing a cryptographically secure method for anybody with the inclination to harness the benefits of the next generation of Blockchain**.
**We will repeat blockchain over and over again like a chant, although what we really mean is the use of a tarball of software innovations which include secure hashing, a public key infrastructure, peer to peer networking, encryption/decryption, distributed databases, distributed consensus protocols, cloud computing, open source, git -- you get the idea.

Every social or business phenomena is marked by a transaction of some kind. Herein lies the key to truly diverse real world blockchain applications.

The Crown project challenges the current Blockchain paradigm, and instead envisions an alternative approach to attaining the holy grail of Blockchain.  The holy grail is product of great usefulness that achieves long term and wide spread adoption by providing valuable services and network security through a cryptographically secure and environmentally sustainable method.

The Crown team draws on people from diverse backgrounds who share a desire to innovate and a sense that the Blockchain Industry is not innovating enough to convince the world that it is better to work with Blockchain than without.  The wave of corporate investment has brought attention – but it has ironically slowed, rather than accelerated the development of trustless platforms.

There is a collective belief within the Crown team that Blockchain technology current sits in a position similar to the internet in the 1990s; with great potential but missing the innovations required to make it truly useful.  As we learn from the continuing evolution of the Internet, these innovations come in incremental steps.  
Whether this particular project succeeds, or fails -- our goal is for Crown to bring innovation back to the Blockchain.

The Crown Papers briefly introduce what the team is thinking and our goals for the project.  An outline of the papers follows:

Crown Paper 1.0 – Governance
In this paper the Crown team provides a brief background to the project and introduces governance concepts and outlines how the project will interact with both the technology and the community.

Crown Paper 2.0 – Introduction & Features
In this paper the Crown team introduces the key entities that will form Crown and the design principles that will be used along the development process.

Crown Paper 3.0 – Applications
In this paper the Crown team describes the vision for how applications will fit into Crown and how the platform will allow those applications will be enabled to operate as a business entity.

Crown Paper 4.0 - Combinations & Permutations
In this paper the Crown team explains what makes the project unique and details some of the proposed use models for the platform.

Crown Paper 5.0 - Symbols, Skyhooks & Survival
In this paper the Crown team muses about what it will take for the project to survive in the current ecosystem and the importance of a shared imagination.

Crown Paper 6.0 – Sharing & Open Teams
In this paper the Crown team contextualises the relationship between economic, social and technological change and what this means for technology such as Blockchain. This paper also describes the evolution of the Crown team and project and its immediate aims for the future.

.. it was only a matter of time before I started quoting myself...

But just to be more specific -- what I would have loved to have had was a weekly snapshot which I could have built a throne from.  Ideally the snapshot would come in 4 or more flavors -- arch, debian, Ubuntu, fedora...  and there would be build instructions for each flavor -- along with an explanation in English of what each command was doing/meant, and links to resources for further reading.  You could build from a script or from the snapshot -- or do a hybrid of building the system from the script and then bootstrapping the blockchain in...

I would also have loved a survey of cloud providers and also node operating businesses to refer to.

So once the current update is over this gives you a feeling for the kind of scaffolding and support which we hope to be able to put in place as the community grows and the codebase -- capabilities and uses, evolve.

Sound reasonable?