[ANN][CRW] CROWN (MN-PoS) | Platform | NFT framework | Governance | Masternodes

[stonehedge]

Some really nice dev progress happening.

We've identified a few minor issues with Throne code which will be sorted soon.  In the meantime, the 2nd tier of the Crowncoin network is stable and paying out like clockwork.

26 days until enforcement.  When we get closer to the day I will be releasing a whitepaper with details of the first service that will be delivered on the Crowncoin service network.

High network hash rate, rising price, profitable masternodes and a blossoming service network.  The future is bright.

[defunctec]

NOT NECESSARY FOR MINERS

I have tested the new wallet build that infernoman kindly donated
to Crowncoin.

Looks like it works, only 1 Throne per IP address from now on

I will post new wallet builds when I have them all.

[stonehedge]

NOT NECESSARY FOR MINERS

I have tested the new wallet build that infernoman kindly donated
to Crowncoin.

Looks like it works, only 1 Throne per IP address from now on

I will post new wallet builds when I have them all.

Good work.

51 masternodes/thrones active today.

[domob]

Looks like it works, only 1 Throne per IP address from now on

Note that a potential issue with that is IPv6.  From all thrones listed by my node currently, all with IPv6 address belong to the same /64.  It depends on the hosting company, but AFAIK, it would fit well to the design of IPv6 if a hosting company provided individual customers with such a range to use by default.  In other words, with IPv6 you can quite probably run multiple thrones on a single VPS, which somewhat defeats the purpose of having a diverse set of masternodes.

[jk9694]

Looks like it works, only 1 Throne per IP address from now on

Note that a potential issue with that is IPv6.  From all thrones listed by my node currently, all with IPv6 address belong to the same /64.  It depends on the hosting company, but AFAIK, it would fit well to the design of IPv6 if a hosting company provided individual customers with such a range to use by default.  In other words, with IPv6 you can quite probably run multiple thrones on a single VPS, which somewhat defeats the purpose of having a diverse set of masternodes.

Not sure I see the issue here.  IPv6 is how things are moving, although it will take some time for adoption in the US.  With IPv6 each device (a vps in this instance) is allocated a single address.  Each IPv6 address is a public address, as the specification with IPv6 is there are no private addresses.  Enough addresses for every device in the world, multiple times over.

Also, while they may be in the same block, the location is not known as there is no geo-location on IPv6.  Many hosts offering IPv6 use a single tunnel for the traffic which is why you see this.

[ether19]

Malayalam Translation done!

https://bitcointalk.org/index.php?topic=1577656.new#new

Check it out! 

[domob]

Note that a potential issue with that is IPv6.  From all thrones listed by my node currently, all with IPv6 address belong to the same /64.  It depends on the hosting company, but AFAIK, it would fit well to the design of IPv6 if a hosting company provided individual customers with such a range to use by default.  In other words, with IPv6 you can quite probably run multiple thrones on a single VPS, which somewhat defeats the purpose of having a diverse set of masternodes.

Not sure I see the issue here.  IPv6 is how things are moving, although it will take some time for adoption in the US.  With IPv6 each device (a vps in this instance) is allocated a single address.  Each IPv6 address is a public address, as the specification with IPv6 is there are no private addresses.  Enough addresses for every device in the world, multiple times over.

Also, while they may be in the same block, the location is not known as there is no geo-location on IPv6.  Many hosts offering IPv6 use a single tunnel for the traffic which is why you see this.

I'm not an expert here, but I think that the "routable" part of IPv6 is only up to /64 (i. e., half the full address).  Of course, it is still up to hosters to actually dispense addresses and implement routing in their own network - but it definitely is not true anymore that a single VPS always gets only a single IP, and that extra IPs cost money.  I just looked at the documentation for OVH as example, and it seems to indicate that each customer automatically gets a full /64 in IPv6 space (see http://help.ovh.com/Ipv4Ipv6).

Note that I'm not necessarily saying that something needs (or can) be done here, just wanted to point that out.

[jk9694]

Note that a potential issue with that is IPv6.  From all thrones listed by my node currently, all with IPv6 address belong to the same /64.  It depends on the hosting company, but AFAIK, it would fit well to the design of IPv6 if a hosting company provided individual customers with such a range to use by default.  In other words, with IPv6 you can quite probably run multiple thrones on a single VPS, which somewhat defeats the purpose of having a diverse set of masternodes.

Not sure I see the issue here.  IPv6 is how things are moving, although it will take some time for adoption in the US.  With IPv6 each device (a vps in this instance) is allocated a single address.  Each IPv6 address is a public address, as the specification with IPv6 is there are no private addresses.  Enough addresses for every device in the world, multiple times over.

Also, while they may be in the same block, the location is not known as there is no geo-location on IPv6.  Many hosts offering IPv6 use a single tunnel for the traffic which is why you see this.

I'm not an expert here, but I think that the "routable" part of IPv6 is only up to /64 (i. e., half the full address).  Of course, it is still up to hosters to actually dispense addresses and implement routing in their own network - but it definitely is not true anymore that a single VPS always gets only a single IP, and that extra IPs cost money.  I just looked at the documentation for OVH as example, and it seems to indicate that each customer automatically gets a full /64 in IPv6 space (see http://help.ovh.com/Ipv4Ipv6).

Note that I'm not necessarily saying that something needs (or can) be done here, just wanted to point that out.

Agreed.  It is the nature of the beast at this point.  I can tell you that all of the nodes that I host, are in fact a single IP per VPS.  I host 430+ for DarkNet, 25+ for TransferCoin, and about 20 or so for CrownCoin.  

[e1ghtSpace]

Did you guys want me to make a video on how to set up your own throne?

[defunctec]

Did you guys want me to make a video on how to set up your own throne?

Hi mate, I think we would like a video doing, we just need to sort a bounty out.

We have bigger plans though, we would like you to work on Crowncoins back end, help us compile wallets and help test new fixes/features.

Would you like to join the team?

[defunctec]

Throne count currently at

52

[crowncoin_knight]

Increasing steadily!

Anybody to come up with a Throne hosting service?

Throne count currently at

52

[defunctec]

Nice price action on c-cex

https://c-cex.com/?p=crw-btc

[crowncoin_knight]

Crowncoin is an undervalued project. Its great to see some interest lately.
The market cap rise is a sign that Thrones supernodes are seen as a positive move.

Nice price action on c-cex

https://c-cex.com/?p=crw-btc

[stonehedge]

Crowncoin is an undervalued project. Its great to see some interest lately.
The market cap rise is a sign that Thrones supernodes are seen as a positive move.

Nice price action on c-cex

https://c-cex.com/?p=crw-btc

I suppose its about time I started to write a white paper about our plans for the Crowncoin application platform!

[stonehedge]

I'm looking to set up something for us to help track bugs and issues.

I was planning on using Jira but it is too advanced for our purposes and isn't free any more.

I was planning on installing https://www.bugzilla.org/ on a VPS and using that.

Any thoughts?

Does anybody know a good free bug tracking tool?

[stonehedge]

PLEASE SUBMIT BUG REPORTS TO:

http://crowncoin.spreadx.eu

[jk9694]

Increasing steadily!

Anybody to come up with a Throne hosting service?

Throne count currently at

52

I currently host Thrones, and master nodes for DNET, DASH, and TX.  Thrones are currently 650 CRW a month, with a monthly price re-adjustment.  I am still working on the frontend, but feel free to contact me for more information.

Thanks

[defunctec]

PLEASE SUBMIT BUG REPORTS TO:

http://crowncoin.spreadx.eu

Added to OP, thanks for your hard work 

[stonehedge]

As a project we need more people to set up thrones.

Thrones are around the most profitable masternodes that you can operate, this means it should be fairly easy to convince people to get one.  At this coin price, a throne has an income of $0.40pd or $12.

As more thrones are set up there is the added benefit of an increasing price effect which will undoubtably snowball when we annouce the first services in about one month's time.

Does anybody have any suggestions on how we can attract more people to set up Thrones?