[ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 64.

urban_idler

member

Activity: 87

Merit: 10

with one masternode (=10.000 crown) u make about 20% per year

with one systemnode (=500 crown) u make about 60% per year

so with 3500 crowns on systemnodes u make the same like with 10.000 crowns on a masternode ....

or u make 3 times more money when u run 20 systemnodes compared to 1 masternode !

think about it !!!!

if u need a hoster for your systemnode i can recommend nodeshare, they really know what they do: http://nodeshare.in/coins/crown/installguide/

yup -- so the idea is to incent the addition of network capacity in the system node layer.

the most interesting part will be what this capacity will be used for over time -- the short-term rewards are just the use of simple skinner box dynamics to draw fourth resources, or bootstrap, what one would hope would be a "cloud" of several thousand nodes of compute capacity.

The value of any of these crypto networks is as a sort of open cloud. the token is simply the coordination mechanism. the limits are whatever the limits of the "shared imagination" of the community are... but to define a shared imagination one needs a more sophisticated governance system than proof of work, or the current proposal system...

it's not that complicated really -- just have to plan out and game out what a crypto system could be and not get stuck in what any of the existing solutions are.

I'm still fascinated that no one seems to care that the OTC derivatives community that created the financial crisis has seized control of bitcoin... idealism and values can be very plastic when money gets involved -- kind of why you need a better governance system than proof of work to have a genuine shared imagination and evolutionary community. anyway, life is strange.

orangegeuse

newbie

Activity: 12

Merit: 0

Quote from: TwistMaister on November 26, 2017, 05:45:22 PM

Quote from: orangegeuse on November 26, 2017, 11:53:16 AM

Quote from: Johnny00 on November 26, 2017, 03:44:47 AM

Quote from: orangegeuse on November 26, 2017, 12:39:25 AM

Anyone know the best way to run multiple systemnodes or multiple masternodes out of the same wallet?

You need different ip addresses for masternodes but can have the local wallet on one

Thanks for the reply, but I'm not fully understanding your suggestion. Here's what I did and please point out where I screwed up:

1. Created wallet
2. generated key
3. funded w/500 crown
4. grabbed output line
5. started systemnode w/ key value
6. started systemnode from my local wallet

I then went through steps 2-6 on the same wallet for a different systemnode on a different IP. However the new SN would never say that it was started properly (still waiting for remote activation). The original SN now showed the IP address of the second systemnode.

Trying to figure out where I screwed up. Thanks!

To run a system node, you need to have a computer that is 24/7 online - connected to the computer. This is mostly a server, or a VPS. Each systemnode needs a unique IP address. Therefore, it is not possible to run more than one Systemnode on the same computer/VPS.

Each systemnode needs to be tied to a local wallet. You can add any amount of Systemnodes to your local wallet.

For more information, see: https://www.youtube.com/watch?v=JGN5NUwwvCE

I understand that they need to be on servers running 24/7, that's easy. The procedure and guides all show a single-use, single-SN setup. They don't really address what to do for multiple SN running against your local wallet. I guess my frustration is that there are lots of "guides", but no real documentation about what each step in the process is doing. I get that Crown is pulling this out from the Dash project, but they seem to be going at this in a cowboy fashion. For example, what exactly does the genkey step do? Should one run genkey each time you setup a new SN, or is one OK? Should you create a new receive address each time, or can you recycle the same one. Etc etc

EDIT: FWIW, I was able to get multiple SN paying back to the same wallet by simply doing every single step over again (including a new receive address).

TwistMaister

newbie

Activity: 57

Merit: 0

Quote from: orangegeuse on November 26, 2017, 11:53:16 AM

Quote from: Johnny00 on November 26, 2017, 03:44:47 AM

Quote from: orangegeuse on November 26, 2017, 12:39:25 AM

Anyone know the best way to run multiple systemnodes or multiple masternodes out of the same wallet?

You need different ip addresses for masternodes but can have the local wallet on one

Thanks for the reply, but I'm not fully understanding your suggestion. Here's what I did and please point out where I screwed up:

1. Created wallet
2. generated key
3. funded w/500 crown
4. grabbed output line
5. started systemnode w/ key value
6. started systemnode from my local wallet

I then went through steps 2-6 on the same wallet for a different systemnode on a different IP. However the new SN would never say that it was started properly (still waiting for remote activation). The original SN now showed the IP address of the second systemnode.

Trying to figure out where I screwed up. Thanks!

To run a system node, you need to have a computer that is 24/7 online - connected to the computer. This is mostly a server, or a VPS. Each systemnode needs a unique IP address. Therefore, it is not possible to run more than one Systemnode on the same computer/VPS.

Each systemnode needs to be tied to a local wallet. You can add any amount of Systemnodes to your local wallet.

For more information, see: https://www.youtube.com/watch?v=JGN5NUwwvCE

orangegeuse

newbie

Activity: 12

Merit: 0

Quote from: Johnny00 on November 26, 2017, 03:44:47 AM

Quote from: orangegeuse on November 26, 2017, 12:39:25 AM

Anyone know the best way to run multiple systemnodes or multiple masternodes out of the same wallet?

You need different ip addresses for masternodes but can have the local wallet on one

Thanks for the reply, but I'm not fully understanding your suggestion. Here's what I did and please point out where I screwed up:

1. Created wallet
2. generated key
3. funded w/500 crown
4. grabbed output line
5. started systemnode w/ key value
6. started systemnode from my local wallet

I then went through steps 2-6 on the same wallet for a different systemnode on a different IP. However the new SN would never say that it was started properly (still waiting for remote activation). The original SN now showed the IP address of the second systemnode.

Trying to figure out where I screwed up. Thanks!

stonehedge

legendary

Activity: 1722

Merit: 1002

Decentralize Everything

Quote from: voxcon on November 26, 2017, 07:50:41 AM

Quote from: CHAOSiTEC on November 26, 2017, 07:08:04 AM

Crown Dev Team update:
-----------------------------------------------

We are working on the dns seed nodes, and sadly dns being what it is, those changes have not propregated through all dns caches and servers yet
we expect this to tak 24 - 48 hours

Temp solution:
go to this site and follow instructions (list is live node list)
http://api.node-vps.com/crown/getpeerinfo

Thanks a lot, that helped.
Even though i had to figure out how to add nodes through console.
To add nodes on your linux client use the following format:

Code:

crown-cli addnode 127.0.0.1:9340 add

Best regards,

Vox

Everything should be back to normal in a few hours. When the DNS changes have propagated you won't need to change anything.

voxcon

newbie

Activity: 8

Merit: 0

Quote from: CHAOSiTEC on November 26, 2017, 07:08:04 AM

Crown Dev Team update:
-----------------------------------------------

We are working on the dns seed nodes, and sadly dns being what it is, those changes have not propregated through all dns caches and servers yet
we expect this to tak 24 - 48 hours

Temp solution:
go to this site and follow instructions (list is live node list)
http://api.node-vps.com/crown/getpeerinfo

Thanks a lot, that helped.
Even though i had to figure out how to add nodes through console.
To add nodes on your linux client use the following format:

Code:

crown-cli addnode 127.0.0.1:9340 add

Best regards,

Vox

crowncoin_knight

hero member

Activity: 808

Merit: 500

Quote from: dex1 on November 26, 2017, 06:13:10 AM

Quote from: crowncoin_knight on November 25, 2017, 12:44:07 PM

alright I say it again, was just analyzing the 40 masternode coins out there:

1. Dash - 4500 nodes, marketcap 5 billion
2. PIVX - 2000 nodes, marketcap 180 mil
3. Crown - 2600 nodes (960 Tron masternodes, 1650 systemnodes), marketcap 27 mil

other masternode coins are left behind

Also, none of the coins out there have a dual node layer

No disrespect but you somehow managed to miss Blocknet which is actually number three and as well established coin, and Pura which
is number four but I've not heard of before.

Edit: Even if you combine CRW and CRW-SN you still will be number five with total market cap of $56.6 mil

I was rather looking at Number of Nodes instead of marketcap.

Pura - 988 nodes
Blocknet - 388 nodes

Crown 2700 nodes

CHAOSiTEC

legendary

Activity: 1358

Merit: 1002

Crown Dev Team update:
-----------------------------------------------

We are working on the dns seed nodes, and sadly dns being what it is, those changes have not propregated through all dns caches and servers yet
we expect this to tak 24 - 48 hours

Temp solution:
go to this site and follow instructions (list is live node list)
http://api.node-vps.com/crown/getpeerinfo

dex1

full member

Activity: 141

Merit: 116

Quote from: crowncoin_knight on November 25, 2017, 12:44:07 PM

alright I say it again, was just analyzing the 40 masternode coins out there:

1. Dash - 4500 nodes, marketcap 5 billion
2. PIVX - 2000 nodes, marketcap 180 mil
3. Crown - 2600 nodes (960 Tron masternodes, 1650 systemnodes), marketcap 27 mil

other masternode coins are left behind

Also, none of the coins out there have a dual node layer

No disrespect but you somehow managed to miss Blocknet which is actually number three and as well established coin, and Pura which
is number four but I've not heard of before.

Edit: Even if you combine CRW and CRW-SN you still will be number five with total market cap of $56.6 mil

voxcon

newbie

Activity: 8

Merit: 0

Hi guys,

I've just tried to setup a systemnode on a linux 14.04 VPS, but after running the systemnode.sh script my client isn't syncing with the network.

Code:

crown-cli getinfo

gives me the following output:

Code:

{
"version" : 120300,
"protocolversion" : 70051,
"walletversion" : 61000,
"balance" : 0.00000000,
"blocks" : 0,
"timeoffset" : 0,
"connections" : 0,
"proxy" : "",
"difficulty" : 1.00000000,
"testnet" : false,
"keypoololdest" : 1511688479,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,
"errors" : ""
}

How can i add nodes manually?

Any help is much appreciated.

Johnny00

hero member

Activity: 896

Merit: 553

Quote from: orangegeuse on November 26, 2017, 12:39:25 AM

Anyone know the best way to run multiple systemnodes or multiple masternodes out of the same wallet?

You need different ip addresses for masternodes but can have the local wallet on one

Jeerke

newbie

Activity: 12

Merit: 0

Quote from: Lyngaa on November 25, 2017, 05:04:54 PM

Hi,

i just started a systemnode, it has been running for 2d 04h 27m, but it has not "staked" jet, according to Crowncentral, on average 1 systemnode should "stake" once a day, is it just me that is impatient ?

Hi, is it in the meantime active at Crowncentral?
If not, send me a private message or send an e-mail to [email protected]

lezlaig

newbie

Activity: 3

Merit: 0

Quote from: Lyngaa on November 25, 2017, 05:04:54 PM

Hi,

i just started a systemnode, it has been running for 2d 04h 27m, but it has not "staked" jet, according to Crowncentral, on average 1 systemnode should "stake" once a day, is it just me that is impatient ?

When you start (or restart) a node, it joins the back of the queue, so it can take 48 (up to 60 on rare occasions) to get its first reward. After that it should be about once a day, yeah.

orangegeuse

newbie

Activity: 12

Merit: 0

Anyone know the best way to run multiple systemnodes or multiple masternodes out of the same wallet?

jeliman

full member

Activity: 227

Merit: 125

Quote from: coins1234 on November 25, 2017, 06:07:41 PM

Quote from: jeliman on November 25, 2017, 05:48:37 PM

Quote from: coins1234 on November 25, 2017, 05:40:29 PM

Quote from: jeliman on November 25, 2017, 05:28:27 PM

Quote from: coins1234 on November 25, 2017, 05:11:05 PM

Quote from: multiplied on November 25, 2017, 02:58:53 PM

Quote from: coins1234 on November 25, 2017, 12:50:58 PM

Quote from: coins1234 on November 25, 2017, 08:16:56 AM

Is Crown inflationary? Will the total supply increase by a percentage each year?

No what I mean is; Does the Total Supply increase yearly? Eg will the 42 mill increase on an annual basis?

If this is meant to be a block chain platform for services, it should be inflationary.

Crown is not inflationary, it's got a set supply cap of 42 million. There will never be more than 42 million Crown.

Why do you suggest it should be inflationary?

If the coins are not inflationary there is no incentive for people to sell their coins if the price rises. I am assuming Crown intend developers to create apps/services for the platform, if the coins are too expensive they cannot use the coins. The more Crown coins gain in value, the less chance for the system to actually take off....eventually no one will use Crown and the it will be worthless.

All other "platform" development cryptos eg ethereum/lisk/ubiq are inflationary.

42,000,000 Crown total
1 Crown = 100,000,000 Crown Satoshi.
42,000,000 x 100,000,000 = 4.2 quadrillion potential units.

Not all units will be available (Masternodes/Systemnodes), but supply and demand will determine a fair price for a unit. With so many potential units I see no risk what so ever in leaving the code as it is.
Even at 30% supply due to units locked in SN/MN, 1.2 quadrillion crown satoshis will be available for use..

Over a long period of time it will make a difference. There has to be a mechanism in place to incentivise the selling of coins for speculative holders. Capping the total supply benefits the holder of coins yes, but as a working project this is a significant flaw imo.

It'd be great to see some calculations regarding your concerns..

Also the incentive of inflation to make holders sell would not work. If we place 5% inflation say per year, but new use is rising by 50% a year, we're kind of back to square one.
There would need to be some sort of mechanism that balances out the % inflation rate (like a central bank, but in code.).
But by doing this we are playing with the fundamental principles of a crypto currency like Crown (changing total supply), when I really see no reason to do so.

Obv you have your reasons and are making your stance known, but virtually every other crypto for blockchain services/app (eg Ethereum/Lisk/Ubiq) runs with an inflationary policy. It's well known that the problem of be speculative investors holding onto coins is a big issue, hence why there is an annual increase in total supply.

An inflationary policy works over a number of years because the effects are accumulative.

"Obv you have your reasons and are making your stance known"
It's hardcoded into the code buddy, and part of the reason people have interest in crypto currency.

I just want to see some basic numbers on why Crown needs to be inflationary (Well known / Should be) are just words, personally I need some hard figures.

coins1234

newbie

Activity: 18