Pages:
Author

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

member
Activity: 84
Merit: 10
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:



Code:
Throne1 178.62.90.252:19340 5J7cqoGAZELHLzh1rP-----------------1ZQ1gXR8BywJVnk 2b8c08b8b1------------------------eb42695bf4ac6a5ec99a 1

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



Whats wrong?
remove the 1 on 19340 should? fix it default port for crw is 9340 Smiley
hero member
Activity: 693
Merit: 508
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:



Code:
Throne1 178.62.90.252:19340 5J7cqoGAZELHLzh1rP-----------------1ZQ1gXR8BywJVnk 2b8c08b8b1------------------------eb42695bf4ac6a5ec99a 1

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



Whats wrong?
hero member
Activity: 805
Merit: 500
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 man, first was chaositec - he got his account back, then defunctec - no response from the hackers and now you.  Sad

Looks like everyone wants hero accounts
newbie
Activity: 6
Merit: 0
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?


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.
hero member
Activity: 896
Merit: 553
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?
hero member
Activity: 896
Merit: 553
newbie
Activity: 6
Merit: 0
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.
legendary
Activity: 1358
Merit: 1002

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.
great work by everyone involved! we're on the right path

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.


Yes we have kept the requirements, and returns as 1/20th, shouldnt be more than a few weeks for first testing of systemnodes in testnet
member
Activity: 87
Merit: 10

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.
great work by everyone involved! we're on the right path

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.
member
Activity: 63
Merit: 10

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.
great work by everyone involved! we're on the right path
hero member
Activity: 805
Merit: 500

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.
hero member
Activity: 896
Merit: 553
Devs are working very hard. Keep it up. Undervalued project
member
Activity: 87
Merit: 10
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.  


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.

Makes sense. Thx!
legendary
Activity: 1358
Merit: 1002
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.  


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.
newbie
Activity: 50
Merit: 0
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.



Thanks!

Done!
member
Activity: 84
Merit: 10
Hey there, Crown Community.
We are looking for a person whom is skilled enough to do a fork of bitcore for Crown, You will be paid for the work you have done, and the amount paid will be confirmed beforehand. You’ll be required to fork bitcore related items examples of this are (insight block chain explorer, bitcore libraries, etc), You will be required to prove work that you’ve done this before, for another coin, or provide the required documents to show that you have coding skills in this ability, You will need to add auxpow header support to the bitcore code so that Crown can then use them for other items that will further give Crown access to more opportunities.

Please contact me via [email protected] if you are interested in working for Crowns Bitcore code.
Thanks Hypermist (Developer Of Crown)


newbie
Activity: 83
Merit: 0

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.


These few paragraphs basically sum up why I'm so excited about this whole project. Going way beyond being a cryptocurrency and actually developing a usable and accessible platform is the future. And Crown and its community are doing just that! Cheesy
newbie
Activity: 83
Merit: 0
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.


Unfortunately you'll have to go through this process twice if you want to vote on both events.

Thanks!

Done, whats the second event, I could only find one?

Oh I see, they've been merged. Will update my post. Thanks for voting!
member
Activity: 87
Merit: 10
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.  

Love seeing the consistent progress from Ashot on the system nodes.  Would just be great to have some visibility for the community into the work Artem & Chaositec are doing as well.  

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....

And when you think of it that way it is also obvious why having a cryptographer like Artem involved now is essential (thank you defunctec!).  

I've had to step back from actively working on CRW for personal reasons -- but this project is different than anything else I've come across in crypto, and has much more potential than anyone really appreciates (in my opinion).  

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.

I tend to read and think too much -- but the problem that we are really trying to solve with these networks isn't a "token" problem -- but to create a system for managing a Common Pool Resource -- a commons.  First off, you can't create a commons with an ICO -- it has to be built on top of a community... The most iconic work on this subject is probably Elinor Ostrom's nobel prize winning notes: https://en.wikipedia.org/wiki/Elinor_Ostrom -- and her principles for the management of common pool resources.  And within this -- all these guys who want to create a new internet are kind of screwing up too... sorry IPFS...  you aren't creating a network -- you are using a network to create a common pool resource.  The problem has been a problem of composition / framing...  and damn I have taken a beating from some for making this point -- because most of us have only read about one thing or another and we are too specialized in our knowledge.

A crypto-commons or kerckhoff social network (fuck the whole crypto-currency thing -- it's so 2009)... but a crypto-commons which is a common pool resource managed by the governance structure of the network and with it's resources allocated by the token which is intrinsic to the network... and where that commons has an interface on iOs & Android (2.6 B smart phones at current count) --- well this is a new sort of nervous system for, well, the world... and that is when your Ostrom needs to be informed by Stuart Kaufmann's insights into networks, complexity and evolution.  I was introduced to Kaufman by someone I met on the Crown Mattermost who used to work with him decades ago and suggested that an understanding of Kaufmann's work was what I was missing.... and he was right.  The key to Kaufmann is in understanding the characteristics of different network structures and the range between rigidity and chaos -- which helps one think about how to structure a network which is a mix of stability and chaos... or where you push the edges of the network to the edge of chaos, but keep the core of the network stable... there are plenty of examples of this in nature... the book to start with on Kaufmann is probably At Home in the Universe -- chapter 4.  Kaufmann's insights on networks actually help explain why 2 tiered governance structures are so common and stable -- a unified structure is too rigid, but as you get into 3 or more layers -- it gets exponentially more complex (roughly) to get agreements, so it becomes to unstable -- so 1 is too rigid, 3 is too fluid.... and it turns out that golidlocks was wise beyond her years.  

Then the final step in the back ground stuff -- is that Kaufmann ultimately connects to the importance of the sacred -- or something which is taken as given at the core of a system.  I think of this in terms of Gödel's incompleteness theorem -- we must start with an assumption and that assumption is what is sacred... for Crown, the assumption that I imagine that it starts with is that human agency and freedom are what is sacred -- or what is assumed to be good.  And this is where I lose many folks... and where I think most of crypto would say I am full of shit... but this is where the opportunity is too...  because there is some reason everyone is doing this?  For many it is probably a sort of gambling addiction and just fun -- but we are playing with amazing technologies which can do a lot more than laundering money and avoiding taxes or providing amusement...

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.
hero member
Activity: 615
Merit: 502
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.


Unfortunately you'll have to go through this process twice if you want to vote on both events.

Thanks!

Done, whats the second event, I could only find one?
Pages:
Jump to: