sounds llike no crown to me someone has to be one or else its ball less
a crown is not so democratic sounds like greece look that mess
Topic: [ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 201. (Read 317079 times)
October 04, 2016, 04:30:24 PM
Opinions for and against are currently split equally amongst the dev team.
sounds llike no crown to me someone has to be one or else its ball less
a crown is not so democratic sounds like greece look that mess
sounds llike no crown to me someone has to be one or else its ball less
a crown is not so democratic sounds like greece look that mess
October 04, 2016, 02:46:02 PM
Crowncoin Update 04/10/2016
Thrones/Masternodes
The number of Thrones has grown to 103 at the time of writing. At current price Thrones are currently earning $15pm before VPS hosting costs. If you own 10k+ or more coins then please consider setting up a throne. The more Thrones we have, the easier it is going to be for us to launch our service platform.
Crowncoin Mining
The network hash rate has increased from 600TH to 1.5PH since the last update. This is one of the highest network hash rates for any cryptocoin. We are keen to encourage more miners and pools to merge mine Crowncoin in order to further decentralise our mining resources and reduce influence by individual pools and miners. Please help us by contacting Coinwarz and other coin info sites to encourage them to list us on their sites.
Dark Gravity Wave was successfuly implemented in our last update. A big thank you to Chaositec for making this a success. Crowncoin's average block time is now a near perfect and consistent 63 seconds which is a huge improvement on our previous range of 10 seconds to 3 minutes!
Exchanges
We want to be listed on Bittrex. Bittrex are amenable to listing us but want to see more social media activity around Crowncoin before doing so. Please tweet them and message them and show that we have support!
Hard Fork Success
In addition to the successful implementation of DGW, we successful enforced version 90350 and above. This means that Throne payments are now enforced which will help protect Throne ROI.
Current Focus
We are working on a few known bugs with start-many, stop-many, start-alias and stop-alias. These will be fixed in the next release.
We are working with two new team members, a graphic designer and a QT specialist, to give our wallet a makeover.
In addition to the makeover we hope to introduce a much improved tool to make it easier to manage Thrones in the next release.
We are actively looking for new team members, particularly people who can pitch in with our upcoming bitcoin core update and people who are familiar with masternode code. Please contact me if you are able to help with these areas
Design and discussion continues on our first two major services. I'm hoping to be able to share a lot more information with you over the next month as the technical side makes more progress. In the meantime I'll drop the hint that Crowncoin will have a symbiotic relationship with other blockchain projects. I think it is safe to say that we are all extremely excited about what we are doing. Nobody has done anything like this in crypto so far.
Development Fund
Several core team members continue to donate all of their Throne payments to the dev fund. We are currently discussing whether it would be sensible to apportion a small amount of the block reward to the dev fund. Please let us know if you have any strong opinions on this. Opinions for and against are currently split equally amongst the dev team.
Awesome update, bump for visibility! Thrones/Masternodes
The number of Thrones has grown to 103 at the time of writing. At current price Thrones are currently earning $15pm before VPS hosting costs. If you own 10k+ or more coins then please consider setting up a throne. The more Thrones we have, the easier it is going to be for us to launch our service platform.
Crowncoin Mining
The network hash rate has increased from 600TH to 1.5PH since the last update. This is one of the highest network hash rates for any cryptocoin. We are keen to encourage more miners and pools to merge mine Crowncoin in order to further decentralise our mining resources and reduce influence by individual pools and miners. Please help us by contacting Coinwarz and other coin info sites to encourage them to list us on their sites.
Dark Gravity Wave was successfuly implemented in our last update. A big thank you to Chaositec for making this a success. Crowncoin's average block time is now a near perfect and consistent 63 seconds which is a huge improvement on our previous range of 10 seconds to 3 minutes!
Exchanges
We want to be listed on Bittrex. Bittrex are amenable to listing us but want to see more social media activity around Crowncoin before doing so. Please tweet them and message them and show that we have support!
Hard Fork Success
In addition to the successful implementation of DGW, we successful enforced version 90350 and above. This means that Throne payments are now enforced which will help protect Throne ROI.
Current Focus
We are working on a few known bugs with start-many, stop-many, start-alias and stop-alias. These will be fixed in the next release.
We are working with two new team members, a graphic designer and a QT specialist, to give our wallet a makeover.
In addition to the makeover we hope to introduce a much improved tool to make it easier to manage Thrones in the next release.
We are actively looking for new team members, particularly people who can pitch in with our upcoming bitcoin core update and people who are familiar with masternode code. Please contact me if you are able to help with these areas
Design and discussion continues on our first two major services. I'm hoping to be able to share a lot more information with you over the next month as the technical side makes more progress. In the meantime I'll drop the hint that Crowncoin will have a symbiotic relationship with other blockchain projects. I think it is safe to say that we are all extremely excited about what we are doing. Nobody has done anything like this in crypto so far.
Development Fund
Several core team members continue to donate all of their Throne payments to the dev fund. We are currently discussing whether it would be sensible to apportion a small amount of the block reward to the dev fund. Please let us know if you have any strong opinions on this. Opinions for and against are currently split equally amongst the dev team.
October 04, 2016, 12:42:00 PM
Team update:
You can see key facts of core Crowncoin team members here:
http://www.crowncoin.org/knights.php
You can see key facts of core Crowncoin team members here:
http://www.crowncoin.org/knights.php
October 04, 2016, 12:29:49 PM
IMHO 10% of the block reward should go to the Dev Fund. If we want to keep with the metaphor -- it's important to tithe to the church... The idea that 10% of the block reward is allocated toward infrastructure, innovation, or maintaining the "commons" is important. 10% of the block reward may not be the right number -- but it's probably not less than that.
Any open blockchain is a "public good" that needs to have a disciplined, transparent and systematic structure for supporting it -- or the investment which has been made in it's initial construction will obsolete or erode over time -- and the capital can't be an endowment, but should come as a flow of funds. This is really for psychological reasons, people twist themselves into all kinds of odd logics around spending from the income vs corpus of an endowment and expected future returns etc, so it's best to not even go there.
Not sure what the exact numbers are but at about 11 mm coins out and a 42 mm cap, the rough math would be that you'd be allocating 3.1 mm coins to the Dev Fund over the inflationary period of the currency. The interesting issue is if an allocation to the dev fund can help differentiate the currency by creating a well funded mechanism for development of the platform.
The trick there is that I think then the dev fund allocations/spending needs to be open to throne votes - or some sort of allocation process determined by the community, which might not be implemented initially for strategic/technical reasons -- but would be implemented at block X, or say when around 22 mm coins were out. In this way allocating 10% of the block reward to dev would involve allocating 1 mm coins to the discretion of the existing dev team and then 2 mm coins to the discretion of the community which is built around the network.
Just an idea... and worth keeping in mind that my thought on ideas is that the key to having good ideas is to have lots of ideas and listen to the feedback you get on them and keep iterating....
Any open blockchain is a "public good" that needs to have a disciplined, transparent and systematic structure for supporting it -- or the investment which has been made in it's initial construction will obsolete or erode over time -- and the capital can't be an endowment, but should come as a flow of funds. This is really for psychological reasons, people twist themselves into all kinds of odd logics around spending from the income vs corpus of an endowment and expected future returns etc, so it's best to not even go there.
Not sure what the exact numbers are but at about 11 mm coins out and a 42 mm cap, the rough math would be that you'd be allocating 3.1 mm coins to the Dev Fund over the inflationary period of the currency. The interesting issue is if an allocation to the dev fund can help differentiate the currency by creating a well funded mechanism for development of the platform.
The trick there is that I think then the dev fund allocations/spending needs to be open to throne votes - or some sort of allocation process determined by the community, which might not be implemented initially for strategic/technical reasons -- but would be implemented at block X, or say when around 22 mm coins were out. In this way allocating 10% of the block reward to dev would involve allocating 1 mm coins to the discretion of the existing dev team and then 2 mm coins to the discretion of the community which is built around the network.
Just an idea... and worth keeping in mind that my thought on ideas is that the key to having good ideas is to have lots of ideas and listen to the feedback you get on them and keep iterating....
The counter argument to this is the fact that a centrally controlled dev fund is opposed to the decentralisation ideal. Having said that, the name Crowncoin implies a monarchy and autocratic head of state
You mention Throne votes, does that mean you are familiar with DASH? Their decentralised governance mechanism was implemented at about the same time I left their team.
We are planning on uplifting the Crowncoin Throne code to use the latest DASH masternode code in the near future but we haven't decided whether we will be using their governance model. This is something that we need to discuss further as a community.
We also have half an eye on what form DASH Evolution will take. Some of the Crowncoin team had input into that project, it will be interesting to see how it is implemented.
October 04, 2016, 12:19:34 PM
You did a great job E1ghtspace! Thank you, this will let people set up thrones and make the Crowncoin blockchain grow more secure! Placing it on the web
I have finished uploading my tutorial!
Crowncoin Throne Setup Tutorial for Windows
Watch it here: https://youtu.be/XZJBC_2sQxk
I will also be making another tutorial to set up a throne on a VPS.
Crowncoin Throne Setup Tutorial for Windows
Watch it here: https://youtu.be/XZJBC_2sQxk
I will also be making another tutorial to set up a throne on a VPS.
October 04, 2016, 12:17:21 PM
Thank you for your opinion - looks like you are watching my brain through the blockchain, scary 😉😂
IMHO 10% of the block reward should go to the Dev Fund. If we want to keep with the metaphor -- it's important to tithe to the church... The idea that 10% of the block reward is allocated toward infrastructure, innovation, or maintaining the "commons" is important. 10% of the block reward may not be the right number -- but it's probably not less than that.
Any open blockchain is a "public good" that needs to have a disciplined, transparent and systematic structure for supporting it -- or the investment which has been made in it's initial construction will obsolete or erode over time -- and the capital can't be an endowment, but should come as a flow of funds. This is really for psychological reasons, people twist themselves into all kinds of odd logics around spending from the income vs corpus of an endowment and expected future returns etc, so it's best to not even go there.
Not sure what the exact numbers are but at about 11 mm coins out and a 42 mm cap, the rough math would be that you'd be allocating 3.1 mm coins to the Dev Fund over the inflationary period of the currency. The interesting issue is if an allocation to the dev fund can help differentiate the currency by creating a well funded mechanism for development of the platform.
The trick there is that I think then the dev fund allocations/spending needs to be open to throne votes - or some sort of allocation process determined by the community, which might not be implemented initially for strategic/technical reasons -- but would be implemented at block X, or say when around 22 mm coins were out. In this way allocating 10% of the block reward to dev would involve allocating 1 mm coins to the discretion of the existing dev team and then 2 mm coins to the discretion of the community which is built around the network.
Just an idea... and worth keeping in mind that my thought on ideas is that the key to having good ideas is to have lots of ideas and listen to the feedback you get on them and keep iterating....
Any open blockchain is a "public good" that needs to have a disciplined, transparent and systematic structure for supporting it -- or the investment which has been made in it's initial construction will obsolete or erode over time -- and the capital can't be an endowment, but should come as a flow of funds. This is really for psychological reasons, people twist themselves into all kinds of odd logics around spending from the income vs corpus of an endowment and expected future returns etc, so it's best to not even go there.
Not sure what the exact numbers are but at about 11 mm coins out and a 42 mm cap, the rough math would be that you'd be allocating 3.1 mm coins to the Dev Fund over the inflationary period of the currency. The interesting issue is if an allocation to the dev fund can help differentiate the currency by creating a well funded mechanism for development of the platform.
The trick there is that I think then the dev fund allocations/spending needs to be open to throne votes - or some sort of allocation process determined by the community, which might not be implemented initially for strategic/technical reasons -- but would be implemented at block X, or say when around 22 mm coins were out. In this way allocating 10% of the block reward to dev would involve allocating 1 mm coins to the discretion of the existing dev team and then 2 mm coins to the discretion of the community which is built around the network.
Just an idea... and worth keeping in mind that my thought on ideas is that the key to having good ideas is to have lots of ideas and listen to the feedback you get on them and keep iterating....
October 04, 2016, 12:06:11 PM
IMHO 10% of the block reward should go to the Dev Fund. If we want to keep with the metaphor -- it's important to tithe to the church... The idea that 10% of the block reward is allocated toward infrastructure, innovation, or maintaining the "commons" is important. 10% of the block reward may not be the right number -- but it's probably not less than that.
Any open blockchain is a "public good" that needs to have a disciplined, transparent and systematic structure for supporting it -- or the investment which has been made in it's initial construction will obsolete or erode over time -- and the capital can't be an endowment, but should come as a flow of funds. This is really for psychological reasons, people twist themselves into all kinds of odd logics around spending from the income vs corpus of an endowment and expected future returns etc, so it's best to not even go there.
Not sure what the exact numbers are but at about 11 mm coins out and a 42 mm cap, the rough math would be that you'd be allocating 3.1 mm coins to the Dev Fund over the inflationary period of the currency. The interesting issue is if an allocation to the dev fund can help differentiate the currency by creating a well funded mechanism for development of the platform.
The trick there is that I think then the dev fund allocations/spending needs to be open to throne votes - or some sort of allocation process determined by the community, which might not be implemented initially for strategic/technical reasons -- but would be implemented at block X, or say when around 22 mm coins were out. In this way allocating 10% of the block reward to dev would involve allocating 1 mm coins to the discretion of the existing dev team and then 2 mm coins to the discretion of the community which is built around the network.
Just an idea... and worth keeping in mind that my thought on ideas is that the key to having good ideas is to have lots of ideas and listen to the feedback you get on them and keep iterating....
Any open blockchain is a "public good" that needs to have a disciplined, transparent and systematic structure for supporting it -- or the investment which has been made in it's initial construction will obsolete or erode over time -- and the capital can't be an endowment, but should come as a flow of funds. This is really for psychological reasons, people twist themselves into all kinds of odd logics around spending from the income vs corpus of an endowment and expected future returns etc, so it's best to not even go there.
Not sure what the exact numbers are but at about 11 mm coins out and a 42 mm cap, the rough math would be that you'd be allocating 3.1 mm coins to the Dev Fund over the inflationary period of the currency. The interesting issue is if an allocation to the dev fund can help differentiate the currency by creating a well funded mechanism for development of the platform.
The trick there is that I think then the dev fund allocations/spending needs to be open to throne votes - or some sort of allocation process determined by the community, which might not be implemented initially for strategic/technical reasons -- but would be implemented at block X, or say when around 22 mm coins were out. In this way allocating 10% of the block reward to dev would involve allocating 1 mm coins to the discretion of the existing dev team and then 2 mm coins to the discretion of the community which is built around the network.
Just an idea... and worth keeping in mind that my thought on ideas is that the key to having good ideas is to have lots of ideas and listen to the feedback you get on them and keep iterating....
October 04, 2016, 12:01:21 PM
I have finished uploading my tutorial!
Crowncoin Throne Setup Tutorial for Windows
Watch it here: https://youtu.be/XZJBC_2sQxk
I will also be making another tutorial to set up a throne on a VPS.
Crowncoin Throne Setup Tutorial for Windows
Watch it here: https://youtu.be/XZJBC_2sQxk
I will also be making another tutorial to set up a throne on a VPS.
October 04, 2016, 08:25:10 AM
Crowncoin Update 04/10/2016
Thrones/Masternodes
The number of Thrones has grown to 103 at the time of writing. At current price Thrones are currently earning $15pm before VPS hosting costs. If you own 10k+ or more coins then please consider setting up a throne. The more Thrones we have, the easier it is going to be for us to launch our service platform.
Crowncoin Mining
The network hash rate has increased from 600TH to 1.5PH since the last update. This is one of the highest network hash rates for any cryptocoin. We are keen to encourage more miners and pools to merge mine Crowncoin in order to further decentralise our mining resources and reduce influence by individual pools and miners. Please help us by contacting Coinwarz and other coin info sites to encourage them to list us on their sites.
Dark Gravity Wave was successfuly implemented in our last update. A big thank you to Chaositec for making this a success. Crowncoin's average block time is now a near perfect and consistent 63 seconds which is a huge improvement on our previous range of 10 seconds to 3 minutes!
Exchanges
We want to be listed on Bittrex. Bittrex are amenable to listing us but want to see more social media activity around Crowncoin before doing so. Please tweet them and message them and show that we have support!
Hard Fork Success
In addition to the successful implementation of DGW, we successful enforced version 90350 and above. This means that Throne payments are now enforced which will help protect Throne ROI.
Current Focus
We are working on a few known bugs with start-many, stop-many, start-alias and stop-alias. These will be fixed in the next release.
We are working with two new team members, a graphic designer and a QT specialist, to give our wallet a makeover.
In addition to the makeover we hope to introduce a much improved tool to make it easier to manage Thrones in the next release.
We are actively looking for new team members, particularly people who can pitch in with our upcoming bitcoin core update and people who are familiar with masternode code. Please contact me if you are able to help with these areas
Design and discussion continues on our first two major services. I'm hoping to be able to share a lot more information with you over the next month as the technical side makes more progress. In the meantime I'll drop the hint that Crowncoin will have a symbiotic relationship with other blockchain projects. I think it is safe to say that we are all extremely excited about what we are doing. Nobody has done anything like this in crypto so far.
Development Fund
Several core team members continue to donate all of their Throne payments to the dev fund. We are currently discussing whether it would be sensible to apportion a small amount of the block reward to the dev fund. Please let us know if you have any strong opinions on this. Opinions for and against are currently split equally amongst the dev team.
Thrones/Masternodes
The number of Thrones has grown to 103 at the time of writing. At current price Thrones are currently earning $15pm before VPS hosting costs. If you own 10k+ or more coins then please consider setting up a throne. The more Thrones we have, the easier it is going to be for us to launch our service platform.
Crowncoin Mining
The network hash rate has increased from 600TH to 1.5PH since the last update. This is one of the highest network hash rates for any cryptocoin. We are keen to encourage more miners and pools to merge mine Crowncoin in order to further decentralise our mining resources and reduce influence by individual pools and miners. Please help us by contacting Coinwarz and other coin info sites to encourage them to list us on their sites.
Dark Gravity Wave was successfuly implemented in our last update. A big thank you to Chaositec for making this a success. Crowncoin's average block time is now a near perfect and consistent 63 seconds which is a huge improvement on our previous range of 10 seconds to 3 minutes!
Exchanges
We want to be listed on Bittrex. Bittrex are amenable to listing us but want to see more social media activity around Crowncoin before doing so. Please tweet them and message them and show that we have support!
Hard Fork Success
In addition to the successful implementation of DGW, we successful enforced version 90350 and above. This means that Throne payments are now enforced which will help protect Throne ROI.
Current Focus
We are working on a few known bugs with start-many, stop-many, start-alias and stop-alias. These will be fixed in the next release.
We are working with two new team members, a graphic designer and a QT specialist, to give our wallet a makeover.
In addition to the makeover we hope to introduce a much improved tool to make it easier to manage Thrones in the next release.
We are actively looking for new team members, particularly people who can pitch in with our upcoming bitcoin core update and people who are familiar with masternode code. Please contact me if you are able to help with these areas
Design and discussion continues on our first two major services. I'm hoping to be able to share a lot more information with you over the next month as the technical side makes more progress. In the meantime I'll drop the hint that Crowncoin will have a symbiotic relationship with other blockchain projects. I think it is safe to say that we are all extremely excited about what we are doing. Nobody has done anything like this in crypto so far.
Development Fund
Several core team members continue to donate all of their Throne payments to the dev fund. We are currently discussing whether it would be sensible to apportion a small amount of the block reward to the dev fund. Please let us know if you have any strong opinions on this. Opinions for and against are currently split equally amongst the dev team.
October 04, 2016, 06:29:33 AM
I'm just reposting the last update so new community investors can recap before I post a new update later today.
Crowncoin Update 11th September 2016
Thrones/Masternodes
Crowncoin is in the process of implementing a 2nd tier service network. 10,000 CRW is required as collateral to run a Throne. Thrones receive 40% of the block reward in return for providing a platform for services. At the time of writing, there are 115 Thrones on the Crowncoin network. If you have 10,000 CRW we encourage you to set up a Throne. The more Thrones we have in operation, the greater security our first services will have.
Crowncoin Mining
To our knowledge, Crowncoin is the only crypto currency to be sha256 mergemineable and also offer a masternode service network. In the last few weeks Crowncoin has been added to several multipools and at the time of writing our network hash rate is over 600Th. This is an increase of 400Th over our recent average.
Upcoming New Release
We will be performing a hard fork in the near future. The spork that we executed recently was only a 90% success due to the fact that some old versions of the wallet were not kicked from the network. The new update will remove the last three nodes that are operating on the incorrect version as we have been unable to contact the node owners.
Apart from the version enforcement, the new update will implement Darkcoin Gravity Wave Version 3. We decided to implement this due to the fact that a merge mineable coin requires rapid difficulty adjustments to compensate for large pools switching coins meaning that our hash rate can jump by a Petahash or more at a time. Our goal is a consistent block time.
A formal new release notification will be posted on BCT and Twitter in the next day or so.
The First Services & Next Steps
In order to implement our first services, we need to perform a Bitcoin Core update and update to the latest Dash masternode version. This is our primary focus for now. We would like to boost our team with more people with experience in these areas. If interested, please contact me by PM.
In an earlier post I alluded to the fact that several of the Crowncoin team have had ideas re-used by other crypto currencies without crediting the original authors. There are no hard feelings about this but in order to protect our own interests we have made the decision that we will only announce details of our plans shortly before we are close to releasing them. Expect these updates to take the form of a series of whitepapers and technical documents relating to milestones in our roadmap. Over time, these updates will provide the bigger picture.
In the meantime I am able to share the following information with you.
We have plans to implement two major services on our service network initially, alongside an API to allow other services to be developed. At the moment we plan to write our own API although we are watching Dash Evolution closely to decide whether we follow their path when the code is open source.
The first service we plan to implement has been in discussion and planing stages for over a year with several members of the Crowncoin team. It relates to Bitcoin. We believe we have solved a problem and hope to be testing that solution in the coming months.
The second service we plan to implement has potential to provide functionality to all other cryptocurrencies that choose to adopt it.
The first chunks of more detailed information about these services will likely be written by me and released to the community after the Bitcoin Core update and Throne/Masternode uplift is complete. I do not want to set timescale expectations right now as we are a new team and still finding our feet a little however we will set expectations more formally as soon as we can.
Please post any questions and we will do our best to answer you.
Thrones/Masternodes
Crowncoin is in the process of implementing a 2nd tier service network. 10,000 CRW is required as collateral to run a Throne. Thrones receive 40% of the block reward in return for providing a platform for services. At the time of writing, there are 115 Thrones on the Crowncoin network. If you have 10,000 CRW we encourage you to set up a Throne. The more Thrones we have in operation, the greater security our first services will have.
Crowncoin Mining
To our knowledge, Crowncoin is the only crypto currency to be sha256 mergemineable and also offer a masternode service network. In the last few weeks Crowncoin has been added to several multipools and at the time of writing our network hash rate is over 600Th. This is an increase of 400Th over our recent average.
Upcoming New Release
We will be performing a hard fork in the near future. The spork that we executed recently was only a 90% success due to the fact that some old versions of the wallet were not kicked from the network. The new update will remove the last three nodes that are operating on the incorrect version as we have been unable to contact the node owners.
Apart from the version enforcement, the new update will implement Darkcoin Gravity Wave Version 3. We decided to implement this due to the fact that a merge mineable coin requires rapid difficulty adjustments to compensate for large pools switching coins meaning that our hash rate can jump by a Petahash or more at a time. Our goal is a consistent block time.
A formal new release notification will be posted on BCT and Twitter in the next day or so.
The First Services & Next Steps
In order to implement our first services, we need to perform a Bitcoin Core update and update to the latest Dash masternode version. This is our primary focus for now. We would like to boost our team with more people with experience in these areas. If interested, please contact me by PM.
In an earlier post I alluded to the fact that several of the Crowncoin team have had ideas re-used by other crypto currencies without crediting the original authors. There are no hard feelings about this but in order to protect our own interests we have made the decision that we will only announce details of our plans shortly before we are close to releasing them. Expect these updates to take the form of a series of whitepapers and technical documents relating to milestones in our roadmap. Over time, these updates will provide the bigger picture.
In the meantime I am able to share the following information with you.
We have plans to implement two major services on our service network initially, alongside an API to allow other services to be developed. At the moment we plan to write our own API although we are watching Dash Evolution closely to decide whether we follow their path when the code is open source.
The first service we plan to implement has been in discussion and planing stages for over a year with several members of the Crowncoin team. It relates to Bitcoin. We believe we have solved a problem and hope to be testing that solution in the coming months.
The second service we plan to implement has potential to provide functionality to all other cryptocurrencies that choose to adopt it.
The first chunks of more detailed information about these services will likely be written by me and released to the community after the Bitcoin Core update and Throne/Masternode uplift is complete. I do not want to set timescale expectations right now as we are a new team and still finding our feet a little however we will set expectations more formally as soon as we can.
Please post any questions and we will do our best to answer you.
October 04, 2016, 04:38:40 AM
To me trading looks like a fairplay game.
Contact defunctec for signatures
some1 buying the own walls?
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
can u fix wallet in yobit?? it was 2 day maintenance and i cant deposit and withdraw
Yobit have been notified on several occasions. Send them a message telling them how mad you are
Yobit can easily add tons of sh*t coins in their exchange yet their always having a hard time fixing the wallet of every coin that having withdrawal and deposit problems.
We're pretty happy with C-Cex and I have been talking to Bittrex quite a lot about us being listed. That should happen sometime over the next few weeks if all goes to plan.
October 04, 2016, 04:19:07 AM
To me trading looks like a fairplay game.
Contact defunctec for signatures
some1 buying the own walls?
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
can u fix wallet in yobit?? it was 2 day maintenance and i cant deposit and withdraw
Yobit have been notified on several occasions. Send them a message telling them how mad you are
Yobit can easily add tons of sh*t coins in their exchange yet their always having a hard time fixing the wallet of every coin that having withdrawal and deposit problems.
October 04, 2016, 03:27:11 AM
To me trading looks like a fairplay game.
Contact defunctec for signatures
some1 buying the own walls?
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
can u fix wallet in yobit?? it was 2 day maintenance and i cant deposit and withdraw
Yobit have been notified on several occasions. Send them a message telling them how mad you are
October 04, 2016, 02:52:57 AM
To me trading looks like a fairplay game.
Contact defunctec for signatures
some1 buying the own walls?
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
can u fix wallet in yobit?? it was 2 day maintenance and i cant deposit and withdraw
October 03, 2016, 11:50:26 PM
To me trading looks like a fairplay game.
Contact defunctec for signatures
some1 buying the own walls?
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
easy pump forsure
edit - how did I do the signatures?
in crown we trust....
October 03, 2016, 11:03:27 PM
Thank you for your supportive message, we are happy that new people are starting to watch this closely and community is slowly growing.
For what it's worth, wait as long as is appropriate to execute on your plan. It's more important to shoot and hit the target slowly at a regular pace than it is to rush off a quick succession of bullets/announcements.
A regular rhythm also plays the role of setting expectations and creating momentum. Just making consistent steps forward -- much like the last few you have made, with introducing the thrones and also DGW. The value proposition seems to be that CRW is a stable base for a variety of activities/applications -- so the message of stability and consistency is probably important.
Excellent support documentation is also probably essential - kind of gilding the lily, but in terms of facilitating adoption, good clear documentation is one of those things that is usually not done well. What E1GHTSPACE has done with the videos is a great illustration of one way of doing good documentation -- nice work. Good documentation pays close attention to process and helping the user understand the steps and purpose of each step so that they develop a generalized knowledge of the software.
Looking forward to seeing where you guys are taking this -- whenever you get around to it. Don't rush it.
A regular rhythm also plays the role of setting expectations and creating momentum. Just making consistent steps forward -- much like the last few you have made, with introducing the thrones and also DGW. The value proposition seems to be that CRW is a stable base for a variety of activities/applications -- so the message of stability and consistency is probably important.
Excellent support documentation is also probably essential - kind of gilding the lily, but in terms of facilitating adoption, good clear documentation is one of those things that is usually not done well. What E1GHTSPACE has done with the videos is a great illustration of one way of doing good documentation -- nice work. Good documentation pays close attention to process and helping the user understand the steps and purpose of each step so that they develop a generalized knowledge of the software.
Looking forward to seeing where you guys are taking this -- whenever you get around to it. Don't rush it.
October 03, 2016, 10:20:37 PM
I am rendering an intro for my future Crowncoin Videos, I think it looks (and sounds) really cool.
You'll be able to see it in my throne tutorial video which will (hopefully) be uploaded in a few hours.
You'll be able to see it in my throne tutorial video which will (hopefully) be uploaded in a few hours.
October 03, 2016, 04:30:10 PM
Quick update on Throne income.
Current income per month per masternode is around $13.50, minus any VPS costs.
Current income per month per masternode is around $13.50, minus any VPS costs.
October 03, 2016, 03:13:52 PM
You'll be pleased to know, e1ghtspace is working on a Throne (Masternode) setup guide. 
October 03, 2016, 11:46:44 AM
For what it's worth, wait as long as is appropriate to execute on your plan. It's more important to shoot and hit the target slowly at a regular pace than it is to rush off a quick succession of bullets/announcements.
A regular rhythm also plays the role of setting expectations and creating momentum. Just making consistent steps forward -- much like the last few you have made, with introducing the thrones and also DGW. The value proposition seems to be that CRW is a stable base for a variety of activities/applications -- so the message of stability and consistency is probably important.
Excellent support documentation is also probably essential - kind of gilding the lily, but in terms of facilitating adoption, good clear documentation is one of those things that is usually not done well. What E1GHTSPACE has done with the videos is a great illustration of one way of doing good documentation -- nice work. Good documentation pays close attention to process and helping the user understand the steps and purpose of each step so that they develop a generalized knowledge of the software.
Looking forward to seeing where you guys are taking this -- whenever you get around to it. Don't rush it.
A regular rhythm also plays the role of setting expectations and creating momentum. Just making consistent steps forward -- much like the last few you have made, with introducing the thrones and also DGW. The value proposition seems to be that CRW is a stable base for a variety of activities/applications -- so the message of stability and consistency is probably important.
Excellent support documentation is also probably essential - kind of gilding the lily, but in terms of facilitating adoption, good clear documentation is one of those things that is usually not done well. What E1GHTSPACE has done with the videos is a great illustration of one way of doing good documentation -- nice work. Good documentation pays close attention to process and helping the user understand the steps and purpose of each step so that they develop a generalized knowledge of the software.
Looking forward to seeing where you guys are taking this -- whenever you get around to it. Don't rush it.
Jump to: