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

thats not the problem, but yes wrong port

the problem is, you have a new empty line in your masternode.conf file, remove it and you will be fine

it seems my account was affected during the bitcointalk database leak, and someone decrypted my password. Not a big deal, if the person offers me a chance to purchase it back i'll do so just to keep the credibility of the account intact.

remove the 1 on 19340 should? fix it default port for crw is 9340

I tried to set up a CRW MN on a VPS and the remote installation went fine and it's up and running. However, I edited the crown.conf file as per instructions like this:




The when I try to start the crown-qt on my Mac I get this message:



Whats wrong?

Looks like I'm the second member of the team to have fallen victim to losing their bitcointalk account. Please ignore any messages from Infernoman.

That sucks. What happened?

Looks like I'm the second member of the team to have fallen victim to losing their bitcointalk account. Please ignore any messages from Infernoman.

Thanks for the update.  From the activity in the GitHub, it looks like we are close to being able to play with the System Nodes in the testnet to work out the bugs?  Is the planned collateral requirement for the System Nodes still 500 CRW? thx.

great work by everyone involved! we're on the right path

Crown Atomic Weekly Update 6.10.2017

After we discussed and approved some Atomic ideas, we continued working on the design and looking for solutions to the technical challenges. Artem has deduced common rules to cover different Atomic use cases and finalized the new operational codes workflow design. Many different design ideas were considered and combinations of them to find the best solution.

We hope this workflow will be able to handle all identified use cases and probably will be a solution for some new use cases that will be developed by Atomic users. Also the identity registration & verification algorithm has been designed and documented, there are different variations of the algorithm depending on the amount of versifiers, initiator of the process etc.

Now we are working on specifying details of application management, service subscriptions, Masternode licensing etc.

All specification is being compiled to one document, this document will be released once the first version of the application layer is in testnet.

We are still in the process of finalising the documentation, but are moving along in a good pace. we have worked out a way to require more than one 'entity' for ID verification, and have worked out a solution for licenseer 'entities'. but currently its too early to discuss any deeper details about these.

Artem, Defunctec and i are working on getting the possible best solutions into version 1, and will after we have finished version 1, reassess if some things needs to change, or evolve.

Alot of things needs to be considered, so that we keep things within laws, but also get as much decentralisation as possible, and i am sure more ideas will evolve as we finish up the first version.. this is a process over time, not a 1 shot finished part of atomic.

We dont want to go too deep into the exact implementations until we have it in testnet, because we want to have first mover advantage.

Nice to see different local communities getting set up.  

For the dev team -- anything more that can be discussed in terms of what the original "skeleton keys" are evolving into, specifically around how the network will "license" different "agents" to enable the different capabilities discussed in Atomic, but in a what should be amore distributed and resilient way than other solutions?  A drawing or 1 pager on this would be awesome to help people (including me) -- understand....

Also -- this helps the developing network of ambassadors start to plan how an initial communications and education role in a local community would be able to develop into a business.  Snoops 2nd reddit update expressed that better than I ever could.  

Hi all,

To gain a bit more traction in publicity around Crown, an event has been added to Cryptocurrency Calendar.
Please vote on the event to increase notability.

• Visit http://www.coinmarketcal.com
• Click on Explore Events
• Search for "CRW"
• Validate the event

Thanks!

I don't think people who haven't been to one of the meetings quite get the scope of the project, and the potential of using different keys to unlock different capabilities within a crypto systems -- and not just using the keys to sign a transfer of tokens, but having more uses for the keys and more uses for the tokens too....

[...]

Every other decent project I looked at (including bitcoin and ethereum) has been "captured" by some limiting factor -- either a fundamental architecture problem or an core economic community or interest group or a specific application.  By building on lessons the core team learned from other projects and also just working quietly during this year's coin frenzy -- Crown may be in the process of managing to sneak up on the competition... or that is what I would like to believe.

[...]

You just have to step into a different frame and imagine what could be if you start with the idea that human agency should be sacred and encouraged, and that we have a network structure which can be designed with evolutionary principles to be both self-governing and stable at the core and dancing on the edge of chaos with different agents out on the edges, and owned by no one, but governed by itself following the principles we have learned from observing the goverance of other common resources in societies over centuries.

Just an idea... this is the shared imagination referred to in the first of the crown papers.  But it doesn't exist yet -- people have to build it.