Crown Forum

Recent Posts

Pages: [1] 2 3 ... 10
Three contests are active right now!
There is still enough time to secure your spot.
Play now
1 BTC Players (Wagering) Contest

Players (Wagering) Contest with 1 BTC Prize Pool has already started. Follow the Contests page!


1st Place - 0.30 BTC and 30 Days LEGEND
2nd Place - 0.20 BTC and 30 Days LEGEND
3rd Place - 0.15 BTC and 30 Days LEGEND
4th Place - 0.10 BTC and 30 Days LEGEND
5th Place - 0.08 BTC and 30 Days LEGEND
6th Place - 0.06 BTC and 30 Days LEGEND
7th Place - 0.05 BTC and 30 Days LEGEND
8th Place - 0.03 BTC and 30 Days LEGEND
9th Place - 0.02 BTC and 30 Days LEGEND
10th Place - 0.01 BTC and 30 Days LEGEND


Post your username for additional chance to win up to 0.1 ETH when 1BTC wagering contest finish.
The 60,000,000,000th Bet Giveaway has been finished! Congratulations to our 173 winners! Good job guys 👍 Today we have given away 82.2 ZEC (1.32 BTC) and 822 days VIP.

We will hit our 60,000,000,000th bet milestone in a few hours!
Join the party while its not too late!

I see the following:

- has 26% ROI
- has 11% ROI

So what will be the interest of running one MN instead of several SNs?

The Masternode (MN) ROI is lower but it requires less hardware.
The collateral for 1 MN = 10k CRW.

The Systemnode (SN) ROI is higher but each SN requires 1 VPS.
The collateral for 1 SN = 500 CRW.

A Crown MN has a vote in the network.

So if u look at current numbers:

Crown Masternode Earnings
Yearly ROI: 12.50% +2.07%
Daily: 3.42 CRW / $0.61
Monthly: 104.14 CRW / $18.54

Crown Systemnode Earnings
Yearly ROI: 27.80% +5.37%
Daily: 0.38 CRW / $0.07
Monthly: 11.58 CRW / $2.06

it depends what you want to achieve with your Masternode or Systemnode. It is true 20 Systemnodes cost the same as 1 Masternode (20 x 500 CRW = 10.000 CRW) but you need 20 times the infrastructure.
Help, Guides and Support / Where can I host a Crown Masternode or Systemnode?
« Last post by LuxoCrypto on December 07, 2018, 08:58:06 am »
It depends if you are looking for self hosting or for managed services.

- for managed services you could go for one of these:

- if you want to run your own VPS you can use:

- if you want to host locally try:
Two Year Anniversary of Luckygames  has been finished! Congratulations to our 140 winners and to the players who bought the gifts worth of 1.5 BTC in our Store! Thanks to everyone who joined! We hope you enjoyed the party :)

Proposals / Budget / Development Proposal November 2018
« Last post by LuxoCrypto on November 27, 2018, 11:18:12 pm »
Proposal Basic Information

Project Name: Development Proposal November 2018
Author: LuxoCrypto
Proposerís email address:
Funds requested: 45309 CRW/month for 1 month - 35309 CRW total
Proposal name: development-nov-2018
Proposal Hash:  f8edea905d93f28d9e79e72ebd25de404bf2682d44118a9e27788c1e4e86c21d
How To Vote YES:  mnbudget vote-many f8edea905d93f28d9e79e72ebd25de404bf2682d44118a9e27788c1e4e86c21d yes
How To Vote NO:  mnbudget vote-many f8edea905d93f28d9e79e72ebd25de404bf2682d44118a9e27788c1e4e86c21d no

You and your team
Artem, Ashot, LuxoCrypto, Volodymyr, Zhan

Project Details
This month the team is working on / has fixed the following (Gitlab issue #number):
- Implement basic sandbox capabilities for testing #231
- Crown Platforms Agents subsystem #211
- Simple NF token registration and timestamping #206
- Docker image generation fails #263
- Add Modern C++ support into build system #134
- Crown Platform Unique Address Prefix #210
- Analyze Headers-First-Sync merge code, possible Windows sync failure #183
- Crown old paperwallet addresses convertor #230
- Create a .dmg installer for Mac users #225
- Add version number to the wallet build zip files #226
- Agree on the budget redistribution and implement it #246
- Budget payment causes forks in testnet #258
- daemon stops processing blocks 1 before a superblock #253

Maintaining and optimizing the Core of the Crown blockchain platform.

Proposal timetable and turning point(s)
Nov 12, 2018 - Dev 7, 2018.

Acceptance criteria
Completing the issues explained in the milestone:

N.A. (force majeure excluded)

Funding requirements
The proposal is for 35309 CRW, paid with December's superblock.

- Discord:
- GitLab:

Additional comments

- 04 Dec 2018 : added hash
Help, Guides and Support / Upgrading nodes to v0.12.5.2
« Last post by higherbridge on November 27, 2018, 07:50:35 pm »
Crown Masternode/Systemnode Update Guide

Firstly, make sure your local wallet is on the latest version (find it at

All managed hosting providers will auto update (Node-VPS, NodeSupply, Crown-VPS and others). You may need to restart the nodes from your local wallet, we recommend you keep an eye on your nodes.

If you have access to your nodes' terminal then it is not managed and you need to do the following.

Copy and paste the following script into your terminal (through PuTTy or otherwise).

Code: [Select]
sudo apt-get install curl -y && curl -s | bash -s
This script will automatically look for the latest release. To check if the update worked, enter the following command into your VPS and check if the version is or later.
Code: [Select]
crown-cli getinfo
IMPORTANT: You might need to restart your nodes from your local wallet!
You do this by navigating to the Masternodes or Systemnodes tab in your wallet and either right-clicking a node and clicking 'Start MISSING' at the bottom of the screen. You can select the 'start all' check box in the pop-up that appears.
Beware that checking this box this will restart all your nodes and put them in the back of the queue, so make sure you've updated your nodes before performing this step!

If you start alias and crown-cli systemnode status or crown-cli masternode status returns waiting for remote activation please check that you have enough peers with the new version with crown-cli getpeerinfo. Should you not have any peers running the new version, do the following:

Code: [Select]
crown-cli stop
rm -rf ~/.crown/peers.dat
crownd -daemon

This will stop the client, clear your peers.dat and restart the client. Peers with the new version will be added automatically.

After this step, click start alias and check if the master- or systemnode is "successfully started".

If you have any trouble following the above guide, please email
Pages: [1] 2 3 ... 10