crowndev / crown-core

Core of Crown blockchain platform. Contribution repository is available by this link: https://gitlab.crownplatform.com/crown/crown-core. Github repository is a mirror.

Crown Platform 0.14.0

http://www.crownplatform.com

What is Crown?

Crown is both a leading digital token (known as CRW) and a self-sustaining blockchain platform for building and running economy applications. Our community uses the Crown Platform as a payment service, proof of data integrity and a support structure for projects ranging from cloud businesses to apps. As more users lend their talents and passion to the platform, Crown’s potential to promote innovation grows exponentially.

A Digital Token

CRW tokens are a type of cryptocurrency. Like bitcoins, CRW can be used to pay for a wide variety of products and services. CRW can also be traded against other altcoins through online exchanges.

Blockchain Application Platform

The Crown Platform utilizes two additional tiers of nodes that offer different roles: Masternodes process instant transactions while Systemnodes will host applications via the CrownPlatform. Members of the Crown Community can set up their own incentivized nodes to earn CRW while helping to maintain the network.

For more information, as well as an immediately usable, binary version Crown see https://crownplatform.com/wallet.

Community

Crown is ultimately a community-driven platform. Its potential to bring social and technological growth is contingent on the ideas and support its users provide. We invite you to lend your voice and imagination to this burgeoning platform and share in its success. Together, there’s no limit to what we can accomplish.

• Crown Forum: https://forum.crown.tech
• Discord: https://discord.gg/Tcrkazc
• Telegram: https://t.me/crownplatform
• Guides & How-to: https://forum.crownplatform.com/index.php?board=5.0

Governance

Crown’s governance system has two core functions: choosing platform direction and funding. Unlike blockchain projects that rely on donations and pre-mined endowments, Crown uses 25% of each block reward to fund its own development. This allocation of funds allows us to reward miners and node operators for their contributions without compromising the platform’s coding and optimization efforts.

Crown’s governance system also enables its community to vote on which changes (ranging from projects to network updates) will be implemented onto the blockchain. Any platform user can submit a proposal to grow or change the network.

• View proposals
• Learn how to create a proposal

Server Nodes

Crown uses two types of server nodes to build and protect its network — Systemnodes and Masternodes. Each of these dedicated servers are unique and provide vital infrastructure. By creating and running them, you can help our community grow while consistently earning CRW as a reward. With the switch from Proof of Work (PoW) to Proof of Stake (PoS) in v0.13 systemnodes and masternodes take over the responsibility of block generation from miners. This new generation process is referred to as "minting".

Masternodes

Masternodes supply substantial computing power to the Crown Platform, and have copies of the ledger stored and ready to distribute to the network if needed. Think of Masternodes as the stabilizing force behind Crown; they help us keep the network secure and running smoothly by tracking the ledger and confirming transactions at lightning speed with Instant Send. A Masternode requires 10,000 CRW collateral to run.

See also: Masternode Setup Guide.

Systemnodes

Systemnodes are empty-shell servers that are tasked with hosting specific services for the Crown network. The Crown Platform will use Systemnodes to host new economy applications created by members of the community, connecting them to the Crown Platform through an API. A Systemnode requires 500 CRW collateral to run.

See also: Systemnode Setup Guide.

Development

Report a Bug

Bugs can be reported via the Gitlab issues page: https://gitlab.crownplatform.com/crown/crown-core/issues, tech support channels in Discord or emailing [email protected]

When describing a bug please include following information:

• Issue summary - an issue header which outlines the actual defect to be solved
• Product - for example Desktop Wallet x64, Windows 10
• Build Found In - for example 0.13.4.0; this is very important as you may be using an old build and the issue may already have been resolved.
• Steps to reproduce - the steps to recreate exactly how the error occurred when you found the issue
• Expected behavior - what you would expect to see instead of the issue; this can be useful as it may trigger a conversation between yourself and the developer (or the team) about a better fix or possible solutions.

Procedures for bounty development

Crown core developers are working hard on bug fixes, platform enhancements, and new product features. Some of these tasks may be completed by talented community members through the bounty program. Bounties are posted to the wiki and can be picked up by anyone who wants to submit new code to the project repository. If you want to be directly notified of new bounties matching your specific skillset, fill out the short intake survey to get onto the InSource Community Job Board. If you have any questions regarding code submissions, please contact Artem Brazhnikov through Discord and ask about bounties.

License

Crown Core is released under the terms of the MIT license. See LICENSE for more information or see http://opensource.org/licenses/MIT.

---

Copyright © 2009-2018, Bitcoin Core Developers

Copyright © 2014-2016, Dash Core Developers

Copyright © 2014-2020, Crown Developers

crown-core's Issues

Unable to sync blocks in v0.13.4

Please answer the following questions.

Which version of Crown are you using? (QT or Daemon) Please include the version number.

Crown Core version v0.13.4.0-bf750d3 (64-bit)

Please describe the expected behavior.

Unable to sync blocks, been stuck on the same one for over an hour. 6 Weeks behind.

Please describe the actual behavior.

Use the debug.log in your data directory if possible. Running Crown with debug=1 in your crown.conf will provide even more information.

2019-05-27 16:39:26 Added time data, samples 15, offset +0 (+0 minutes)
2019-05-27 16:39:26 nTimeOffset = +0  (+0 minutes)
2019-05-27 16:39:26 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:39:26 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:39:26 Misbehaving: 89.36.216.78:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:39:26 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:39:26 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:39:26 Misbehaving: 151.80.5.199:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:39:26 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:39:26 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:39:26 Misbehaving: 195.181.209.183:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:39:26 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:39:26 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:39:26 Misbehaving: 81.2.246.175:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:39:26 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:39:26 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:39:26 Misbehaving: 212.237.1.175:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:39:26 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390194, us=[MY IP]:62890, peer=19
2019-05-27 16:39:26 Added time data, samples 16, offset +0 (+0 minutes)
2019-05-27 16:39:26 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:39:26 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:39:26 Misbehaving: 139.99.199.13:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:39:27 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:39:27 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:39:27 Misbehaving: 194.182.85.110:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:39:27 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:39:27 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:39:27 Misbehaving: 217.61.3.7:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:39:28 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390194, us=[MY IP]:62891, peer=20
2019-05-27 16:39:28 Added time data, samples 17, offset -1 (+0 minutes)
2019-05-27 16:39:28 nTimeOffset = +0  (+0 minutes)

2019-05-27 16:43:29 CrownMiner started
2019-05-27 16:43:29 GUI: PaymentServer::LoadRootCAs : Loaded  178  root certificates
2019-05-27 16:43:29 GUI: QMetaObject::connectSlotsByName: No matching signal for on_editButton_clicked()
2019-05-27 16:43:29 GUI: QMetaObject::connectSlotsByName: No matching signal for on_startAllButton_clicked()
2019-05-27 16:43:29 GUI: QMetaObject::connectSlotsByName: No matching signal for on_editButton_clicked()
2019-05-27 16:43:29 GUI: QMetaObject::connectSlotsByName: No matching signal for on_startAllButton_clicked()
2019-05-27 16:43:30 CMasternodeSync::Process() - tick 1 RequestedMasternodeAssets 0
2019-05-27 16:43:30 CSystemnodeSync::Process() - tick 1 RequestedSystemnodeAssets 0
2019-05-27 16:43:35 CMasternodeSync::Process() - tick 6 RequestedMasternodeAssets 1
2019-05-27 16:43:35 CSystemnodeSync::Process() - tick 6 RequestedSystemnodeAssets 1
2019-05-27 16:43:35 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390198, us=[MY IP]:63022, peer=1
2019-05-27 16:43:35 Added time data, samples 2, offset +0 (+0 minutes)
2019-05-27 16:43:36 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:43:36 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:43:36 Misbehaving: 212.237.36.87:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:43:36 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390198, us=[MY IP]:63023, peer=2
2019-05-27 16:43:36 Added time data, samples 3, offset +0 (+0 minutes)
2019-05-27 16:43:37 connect() to 159.65.138.32:9340 failed after select(): Connection refused (61)
2019-05-27 16:43:38 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390198, us=[MY IP]:63025, peer=3
2019-05-27 16:43:38 Added time data, samples 4, offset +0 (+0 minutes)
2019-05-27 16:43:39 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390198, us=[MY IP]:63026, peer=4
2019-05-27 16:43:39 Added time data, samples 5, offset +0 (+0 minutes)
2019-05-27 16:43:39 +0  +0  +0  +0  +0  |  nTimeOffset = +0  (+0 minutes)
2019-05-27 16:43:39 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390198, us=[MY IP]:63027, peer=5
2019-05-27 16:43:39 Added time data, samples 6, offset +0 (+0 minutes)
2019-05-27 16:43:40 CMasternodeSync::Process() - tick 11 RequestedMasternodeAssets 1
2019-05-27 16:43:40 CSystemnodeSync::Process() - tick 11 RequestedSystemnodeAssets 1
2019-05-27 16:43:40 P2P peers available. Skipped DNS seeding.
2019-05-27 16:43:40 dnsseed thread exit
2019-05-27 16:43:40 spork - new faba8cfbbd1b7b5ca0518691625186d9c0d5188049cf88c50d2018ae8d6a751e ID 10003 Time 1 bestHeight 2329999
2019-05-27 16:43:40 spork - new b5e5af8b3d74e17b9952a0ec9e9a2300691fdf4ac9a97d7d26957c9504c10575 ID 10012 Time 1 bestHeight 2329999
2019-05-27 16:43:40 spork - seen faba8cfbbd1b7b5ca0518691625186d9c0d5188049cf88c50d2018ae8d6a751e block 2329999 
2019-05-27 16:43:40 spork - seen b5e5af8b3d74e17b9952a0ec9e9a2300691fdf4ac9a97d7d26957c9504c10575 block 2329999 
2019-05-27 16:43:45 CMasternodeSync::Process() - tick 16 RequestedMasternodeAssets 1
2019-05-27 16:43:45 CSystemnodeSync::Process() - tick 16 RequestedSystemnodeAssets 1
2019-05-27 16:43:45 spork - seen faba8cfbbd1b7b5ca0518691625186d9c0d5188049cf88c50d2018ae8d6a751e block 2329999 
2019-05-27 16:43:45 spork - seen b5e5af8b3d74e17b9952a0ec9e9a2300691fdf4ac9a97d7d26957c9504c10575 block 2329999 
2019-05-27 16:43:45 spork - seen faba8cfbbd1b7b5ca0518691625186d9c0d5188049cf88c50d2018ae8d6a751e block 2329999 
2019-05-27 16:43:45 spork - seen b5e5af8b3d74e17b9952a0ec9e9a2300691fdf4ac9a97d7d26957c9504c10575 block 2329999 
2019-05-27 16:43:45 receive version message: /Crown Core:0.13.2/: version 70057, blocks=2390198, us=[MY IP]:63029, peer=6
2019-05-27 16:43:45 Added time data, samples 7, offset +0 (+0 minutes)
2019-05-27 16:43:45 +0  +0  +0  +0  +0  +0  +0  |  nTimeOffset = +0  (+0 minutes)
2019-05-27 16:43:50 CMasternodeSync::Process() - tick 21 RequestedMasternodeAssets 1
2019-05-27 16:43:50 CSystemnodeSync::Process() - tick 21 RequestedSystemnodeAssets 1
2019-05-27 16:43:50 spork - seen faba8cfbbd1b7b5ca0518691625186d9c0d5188049cf88c50d2018ae8d6a751e block 2329999 
2019-05-27 16:43:50 spork - seen b5e5af8b3d74e17b9952a0ec9e9a2300691fdf4ac9a97d7d26957c9504c10575 block 2329999 
2019-05-27 16:43:50 spork - seen faba8cfbbd1b7b5ca0518691625186d9c0d5188049cf88c50d2018ae8d6a751e block 2329999 
2019-05-27 16:43:50 spork - seen b5e5af8b3d74e17b9952a0ec9e9a2300691fdf4ac9a97d7d26957c9504c10575 block 2329999 
2019-05-27 16:43:52 peer=7 using obsolete version 70052; disconnecting
2019-05-27 16:43:52 ProcessMessage(version, 107 bytes) FAILED peer=7
2019-05-27 16:43:52 connect() to 178.62.127.165:9340 failed after select(): Connection refused (61)
2019-05-27 16:43:53 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:43:53 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:43:53 Misbehaving: 142.93.113.188:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:43:53 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63034, peer=8
2019-05-27 16:43:53 Added time data, samples 8, offset +0 (+0 minutes)
2019-05-27 16:43:53 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:43:53 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:43:53 Misbehaving: 85.255.5.93:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:43:53 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:43:53 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:43:53 Misbehaving: 94.177.218.121:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:43:53 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:43:53 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:43:53 Misbehaving: 185.206.144.140:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:43:53 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:43:53 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:43:53 Misbehaving: 80.211.0.92:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:43:54 connect() to 144.217.115.122:9340 failed after select(): Connection refused (61)
2019-05-27 16:43:54 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:43:54 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:43:54 Misbehaving: 194.182.64.231:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:43:55 CMasternodeSync::Process() - tick 26 RequestedMasternodeAssets 2
2019-05-27 16:43:55 CSystemnodeSync::Process() - tick 26 RequestedSystemnodeAssets 2
2019-05-27 16:44:00 connect() to 188.166.61.51:9340 failed after select(): Connection refused (61)
2019-05-27 16:44:00 CMasternodeSync::Process() - tick 31 RequestedMasternodeAssets 2
2019-05-27 16:44:00 CSystemnodeSync::Process() - tick 31 RequestedSystemnodeAssets 2
2019-05-27 16:44:01 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63041, peer=9
2019-05-27 16:44:01 Added time data, samples 9, offset -1 (+0 minutes)
2019-05-27 16:44:01 -1  +0  +0  +0  +0  +0  +0  +0  +0  |  nTimeOffset = +0  (+0 minutes)
2019-05-27 16:44:01 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63042, peer=10
2019-05-27 16:44:01 Added time data, samples 10, offset +0 (+0 minutes)
2019-05-27 16:44:01 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:01 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:01 Misbehaving: 207.148.25.139:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:01 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:01 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:01 Misbehaving: 195.181.209.21:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:02 peer=11 using obsolete version 70054; disconnecting
2019-05-27 16:44:02 ProcessMessage(version, 107 bytes) FAILED peer=11
2019-05-27 16:44:02 peer=12 using obsolete version 70054; disconnecting
2019-05-27 16:44:02 ProcessMessage(version, 107 bytes) FAILED peer=12
2019-05-27 16:44:03 receive version message: /Crown Core:0.13.2/: version 70057, blocks=2390199, us=[MY IP]:63045, peer=13
2019-05-27 16:44:03 Added time data, samples 11, offset +0 (+0 minutes)
2019-05-27 16:44:03 -1  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  |  nTimeOffset = +0  (+0 minutes)
2019-05-27 16:44:03 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:03 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:03 Misbehaving: 45.77.227.174:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:04 receive version message: /Crown Core:0.13.2/: version 70057, blocks=2390199, us=[MY IP]:63046, peer=14
2019-05-27 16:44:04 Added time data, samples 12, offset +0 (+0 minutes)
2019-05-27 16:44:04 connect() to 145.239.238.64:9340 failed after select(): Connection refused (61)
2019-05-27 16:44:05 CMasternodeSync::Process() - tick 36 RequestedMasternodeAssets 2
2019-05-27 16:44:05 CSystemnodeSync::Process() - tick 36 RequestedSystemnodeAssets 2
2019-05-27 16:44:05 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:05 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:05 Misbehaving: 178.128.27.212:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:10 CMasternodeSync::Process() - tick 41 RequestedMasternodeAssets 2
2019-05-27 16:44:10 CSystemnodeSync::Process() - tick 41 RequestedSystemnodeAssets 2
2019-05-27 16:44:10 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63049, peer=15
2019-05-27 16:44:10 Added time data, samples 13, offset +0 (+0 minutes)
2019-05-27 16:44:10 -1  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  |  nTimeOffset = +0  (+0 minutes)
2019-05-27 16:44:11 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63050, peer=16
2019-05-27 16:44:11 Added time data, samples 14, offset +0 (+0 minutes)
2019-05-27 16:44:11 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:11 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:11 Misbehaving: 195.181.222.144:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:11 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:11 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:11 Misbehaving: 45.77.159.45:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:12 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63051, peer=17
2019-05-27 16:44:12 Added time data, samples 15, offset -1 (+0 minutes)
2019-05-27 16:44:12 -1  -1  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  |  nTimeOffset = +0  (+0 minutes)
2019-05-27 16:44:12 connect() to 54.37.108.26:9340 failed after select(): Connection refused (61)
2019-05-27 16:44:12 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:12 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:12 Misbehaving: 85.255.9.210:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:14 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63054, peer=19
2019-05-27 16:44:14 Added time data, samples 16, offset +0 (+0 minutes)
2019-05-27 16:44:14 connect() to 45.32.221.175:9340 failed after select(): Connection refused (61)
2019-05-27 16:44:15 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:15 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:15 Misbehaving: 185.203.117.121:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:15 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63056, peer=20
2019-05-27 16:44:15 Added time data, samples 17, offset +0 (+0 minutes)
2019-05-27 16:44:15 -1  -1  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  |  nTimeOffset = +0  (+0 minutes)
2019-05-27 16:44:15 CMasternodeSync::Process() - tick 46 RequestedMasternodeAssets 2
2019-05-27 16:44:15 CSystemnodeSync::Process() - tick 46 RequestedSystemnodeAssets 2
2019-05-27 16:44:15 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63057, peer=21
2019-05-27 16:44:15 Added time data, samples 18, offset +0 (+0 minutes)
2019-05-27 16:44:15 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:15 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:15 Misbehaving: 85.255.6.128:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:16 ERROR: AcceptBlockHeader : prev block (6aaeb69156627275414d6970148d696759ae991d3711972ad92573ddaa0b0471) invalid
2019-05-27 16:44:16 ERROR: ProcessNewBlock : AcceptBlock FAILED
2019-05-27 16:44:16 Misbehaving: 217.61.107.217:9340 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-05-27 16:44:16 connect() to 54.37.139.187:9340 failed after select(): Connection refused (61)
2019-05-27 16:44:17 receive version message: /Crown Core:0.13.4/: version 70057, blocks=2390199, us=[MY IP]:63059, peer=22
2019-05-27 16:44:17 Added time data, samples 19, offset +0 (+0 minutes)
2019-05-27 16:44:17 -1  -1  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  +0  |  nTimeOffset = +0  (+0 minutes)

Any steps to reproduce the behavior?

Opening application results in this behaviour without any interaction

Please add your crown.conf file

(be sure to exclude or anonymize private data (tokens/passwords))

debug=1

Thanks

masternode help needed asap

Hi @Infernoman, We need help with our masternodes. Please reply to [email protected] ASAP.

Systemnode die unexpected

Which version of Crown are you using? (QT or Daemon) Please include the version number.

latest

Use the debug.log in your data directory if possible. Running Crown with debug=1 in your crown.conf will provide even more information.

added:

disablewallet=1
keypool=0

No errors in debug.log

linux: dmesg:

crown-legacysig[15831]: segfault at 108 ip 000000000069689c sp 00007ff2415b46b0 error 4 in crownd[400000+810000]

Any chance you can check running it with disablewallet=1
I think running MN/SN with wallet enabled just adds CPU load to scan addresses in the wallet...
Another solution to minimize CPU load would be to keep wallet enabled and set keypool=0 to have only 1 address in the wallet for scanning

dumpprivkey <6fdc546d-62a6-49ef-95a3-abdc8f8e1fb0>

dumpprivkey <1PhRyhGwNToV3F7pVQ8Wmjy44brTPmrcD5>

BreadWallet

With headers first synchronization added we can now start looking into other ports of the wallet for IOS/Android.

systemnodes endup with corrupted BC after shutdown

So I shutdown a node via cli stop and then start it again and it tells me BC is corrupted and need to reindex
Anybody experiencing that? If not then maybe my OVH VPS is corrupting the files, that makes no sense

0.13.2.0 getblocktemplate error

crown-cli getblocktemplate
error: {"code":-7,"message":"Out of memory"}

conf parse error

Hey me again :)

I'm sure i've added the correct information into the conf file with the right spacing etc but i'm getting a parse error when starting core :/
Any tips ?

Test

Test

Sporkkey

Currently unable to load the spork key into the client, makekeypair was used to generate the spork and alert keys. Alerts currently untested.

Local IP Thrones

Only one or two seem to be getting onto the network, most of them are not relayed and should be completely ignored. Only thing i've found of much difference concerning local addresses is in dash 0.12.1.x and there seems to be no mention of it anywhere on their github.

https://github.com/dashpay/dash/blob/v0.12.1.x/src/masternodeman.cpp#L905

Please add option to disable logging to debug.log

Please add

fPrintToDebugLog=GetBoolArg("-printtodebug", true);

Don't have to update documenation ie daemon help. But I don't think we need waste CPU and IO to write all those useless logs like InstantX::ProcessConsensusVote

think even Bitcoin devs should add argument to disable all logging is someone wants... writing to /dev/null and other trick to prevent logging is still using CPU to process them in the daemon

Mining before sync.

dashpay@ac488d7

Nothing Relevant just testing

Start all (systemnodes and masternodes) should warn and query before starting a running node

Please answer the following questions.

Which version of Crown are you using? (QT or Daemon) Please include the version number.

Crown-qt v0.12.3.0-da38c36 (32-bit)

Please describe the expected behavior.

Start All (and Start Alias) should warn the user if an already running node is about to be restarted and ask if they really want to do that or if they're happy to miss out on potentially several days' rewards.

Please describe the actual behavior.

Start All blithely does what it was asked to do. Any already running nodes will get their active timer reset to 0 and go to the end of the reward queue. For a systemnode the user misses out on several days worth of rewards.

Use the debug.log in your data directory if possible. Running Crown with debug=1 in your crown.conf will provide even more information.

Nothing gets logged.

Any steps to reproduce the behavior?

Click Start All in the systemnodes tab with an already running node. Lose several days rewards.

Please add your crown.conf file

(be sure to exclude or anonymize private data (tokens/passwords))

N/A

Please add your masternode.conf if necessary.

(be sure to exclude or anonymize private data (tokens/passwords))

N/A

Chinese translation of the coin name in qt

Now the coin name is translated to "达世币", which actually means "Dash Coin" ("达" pronounces "da", "世" pronounces "shi", and "币" means (not pronounces) coin). I found that in Dash, every translation doesn't translate the coin name, except for Chinese. The same goes for Bitcoin.

I suggest translating into "Crown币"，or simply "Crown", or "王冠币" or "皇冠币". Note that "冠" itself means crown, but Chinese like to use double-character words so it looks better to add a "王" (means king) or "皇" (means emperor) before it.

MN Voting is not being registered on the first vote

Pulled from Gitlab - https://gitlab.crownplatform.com/crown/crown-core/issues

Link - https://gitlab.crownplatform.com/crown/crown-core/issues/161

Bootstrap

Is there a chance a new bootstrap could be provided ?

systemnode rewards

Hi guys,

My systemnode has been up for 1day and 14hr but it hasn't generated anything yet?
How come.

Write documentation for NFTs

Pulled from Gitlab - https://gitlab.crownplatform.com/crown/crown-core/issues

Link - https://gitlab.crownplatform.com/crown/crown-core/issues/332

Alerts

https://github.com/duality-solutions/Dynamic/commits/master?after=Y3Vyc29yOvdu7252tnxniVC4GdQZvegcZfu%2FKzY5

Systemnodes die without logs

Which version of Crown are you using? (QT or Daemon) Please include the version number.

v0.12.5.3

I didn't have such problems on previous release.
Last logs from SN

System log

I don't know how to debug more...

Getblocktemplate for superblocks

dashpay@02b86cf

Before we go and enable superblocks let's at least make sure that when a superblock is found. the block doesn't get orphaned once enforcement is enabled. Without this the pool will not know to pay out the winning vote from the superblock, and without enforcement enabled the miner will be able to keep the reward from the superblock.

Implement RESTful API call for NF tokens creation with a timestamp

Pulled from Gitlab - https://gitlab.crownplatform.com/crown/crown-core/issues

Link - https://gitlab.crownplatform.com/crown/crown-core/issues/239

MN and SN sync error on 12.5.2 after blockchain download

Hi

MN and SN sync error on 12.5.2 after blockchain download

2018-12-10 10:12:47 CMasternodeSync::Process - ERROR - Sync has failed, will retry later
2018-12-10 10:12:47 CSystemnodeSync::Process - ERROR - Sync has failed, will retry later
2018-12-10 10:14:07 dseg - we already asked 207.246.70.47:9340 for the list; skipping...
2018-12-10 10:14:07 sndseg - we already asked 207.246.70.47:9340 for the list; skipping...
2018-12-10 10:14:12 dseg - we already asked 78.47.95.38:9340 for the list; skipping...
2018-12-10 10:14:12 sndseg - we already asked 78.47.95.38:9340 for the list; skipping...
2018-12-10 10:14:17 dseg - we already asked 185.243.113.88:9340 for the list; skipping...
2018-12-10 10:14:17 sndseg - we already asked 185.243.113.88:9340 for the list; skipping...
2018-12-10 10:14:22 dseg - we already asked 80.211.220.176:9340 for the list; skipping...
2018-12-10 10:14:22 sndseg - we already asked 80.211.220.176:9340 for the list; skipping...
2018-12-10 10:14:27 dseg - we already asked 212.237.9.100:9340 for the list; skipping...
2018-12-10 10:14:27 sndseg - we already asked 212.237.9.100:9340 for the list; skipping...
2018-12-10 10:14:32 CMasternodeSync::Process - ERROR - Sync has failed, will retry later
2018-12-10 10:14:32 CSystemnodeSync::Process - ERROR - Sync has failed, will retry later
2018-12-10 10:15:52 dseg - we already asked 207.246.70.47:9340 for the list; skipping...
2018-12-10 10:15:52 sndseg - we already asked 207.246.70.47:9340 for the list; skipping...
2018-12-10 10:15:57 dseg - we already asked 78.47.95.38:9340 for the list; skipping...
2018-12-10 10:15:57 sndseg - we already asked 78.47.95.38:9340 for the list; skipping...
2018-12-10 10:16:02 dseg - we already asked 185.243.113.88:9340 for the list; skipping...
2018-12-10 10:16:02 sndseg - we already asked 185.243.113.88:9340 for the list; skipping...
2018-12-10 10:16:07 dseg - we already asked 80.211.220.176:9340 for the list; skipping...
2018-12-10 10:16:07 sndseg - we already asked 80.211.220.176:9340 for the list; skipping...
2018-12-10 10:16:12 dseg - we already asked 212.237.9.100:9340 for the list; skipping...
2018-12-10 10:16:12 sndseg - we already asked 212.237.9.100:9340 for the list; skipping...

logo.ico

switch to the dark logo for the .ico

protobuf 3.0 (byteswap) issue on macOS

dashpay@8c64c0a

need "systemnode genkey"

Please answer the following questions.

Which version of Crown are you using? (QT or Daemon) Please include the version number.

0.12.4.1

Please describe the expected behavior.

I noticed you removed "systemnode genkey" and "mastenode genkey". I'm assuming this because of a new feuture of GUI asking if to create a system node after 500 payment received, but the problme is "pay to many" I pay to 3 addresses in one transaction (used to do that and it works) the GUI asked about systemnode only for 1 node, now I want to fill systemnode.conf manually but there is no way to generate the key anymore

Peercoin mining issue

�[2017-01-26 02:30:10.299] [DEBUG] [default] - �[Pool peercoin Thread 16 Failed to submit potential auxiliary block: {"code":-1,"message":"ReadCompactSize() : size too large"}]

Peercoin has a mining issue focused on Crown. This related back to the size of the network headers? being too large. Crowncoin will refuse every block mined from peercoin with the message ReadCompactSize(): size too large. It also happens with other coins as well. But not nearly as often and other networks are at least mine-able.

Mac client icon reverts to terminal icon

Please answer the following questions.

Which version of Crown are you using? (QT or Daemon) Please include the version number.

QT v0.12.3.0-da38c36

Please describe the expected behavior.

When the client is running the icon is displayed correctly with the crown logo.

Please describe the actual behavior.

Use the debug.log in your data directory if possible. Running Crown with debug=1 in your crown.conf will provide even more information.

When the wallet is closed it displays a terminal icon.

Any steps to reproduce the behavior?

Open and close the MacOS

Crown wallet.

Please add your crown.conf file

(be sure to exclude or anonymize private data (tokens/passwords))

I don't believe this is necessary. It's always done this to me across 2-3 MacOS devices.

Please add your masternode.conf if necessary.

(be sure to exclude or anonymize private data (tokens/passwords))

Headers first sync bloat

Headers first seems to be bloating the chain by a pretty extreme amount. initial sync on a 3.5gb chain is coming in anywhere from 10-40gb. From what i've noticed the getheaders response "headers" from the peer is in excess of 2mb+ and sometimes larger.

Sending funds

Hi,

Im trying to move funds from an old systemnode but somehow i can't send it and it gives me an insufficient funds warning while i have 500 crw in the wallet.
How fix ?

IPV6 Nodes

Three commits are needed from what i can tell

Move broadcast creation to CMasternodeBroadcast
UdjinM6@8f9544c

Masternodes should be allowed to annonce ipv4 addresses only from now
dashpay@d0bee00

Also validate net addr on masternode broadcast creation
dashpay@795338c

PoS Sanbox

Pulled from Gitlab - https://gitlab.crownplatform.com/crown/crown-core/issues

Link - https://gitlab.crownplatform.com/crown/crown-core/issues/330

a small comment issue

I found a small issue in this repo when improving POW check in my bitcore-lib-crown repo.

In line 120 of chainparams.cpp,

bnProofOfWorkLimit = ~arith_uint256(0) >> 32;  // Crown starting difficulty is 1 / 2^12

This must be introduced by dash, because Dash code is:

https://github.com/Crowndev/crowncoin/blob/9c40441a7ba6dfaf19be5c987c219fc89cce539b/src/chainparams.cpp#L125

Because crown starting difficulty is 1, unlike Dash's 1/4096, so I think the comment should be:

bnProofOfWorkLimit = ~arith_uint256(0) >> 32;  // Crown starting difficulty is 1 / 2^0

Bitcore NFT RPC API wrapper

Pulled from Gitlab - https://gitlab.crownplatform.com/crown/crown-core/issues

Link - https://gitlab.crownplatform.com/crown/crown-core/issues/329

Vote for an empowered agent

Pulled from Gitlab - https://gitlab.crownplatform.com/crown/crown-core/issues

Link - https://gitlab.crownplatform.com/crown/crown-core/issues/233

Cleanup old dash files, and files that are no longer being used.

There's still quite a bit of leftover files left from dash and bitcoin 0.9 that need to be cleaned up. Anyone with build experience that could route through these, and remove them, would be greatly appreciated.

2000 CRW

start-alias crash

Using start-alias / start-missing /start-all may crash the wallet.

Change crowns -> cSats

Just text that needs to be replaced. Watch out for statements that don't need to be changed. Only the unit indicator "crowns" should be changed to "cSats".
500 CRW

systemnode won't start after update to v0.12.5.2

updated hot wallet QT and VPS binary, and systemnode privatekey, and it just won't start keep saying:

"status" : "Not capable systemnode: Hot node, waiting for remote activation."

systemnode output

Hello,

i'm running the the wallet locally and generated a key
now that i send the crown to my wallet and type "systemnode outputs"
It doesn't show anything, although the CRW is in my wallet.

Not sure how i have gone wrong here.

Can Crown support prune blockchain?

Can Crown support prune blockchain same as BTC, LTC, DGB, ...?

Fix travis builds

All travis builds fail.

6 different compilers 2000 CRW each. 12000 CRW Total

How to compile?

I used Dash documentation and I was able to compile on Ubuntu 16 but compiled version by me complains about missing libdb_cxx-4.8.so while on the same machine binaries provided by you works just fine.
Also my binaries let say crownd is 113MB in size while yours 11MB, I don't know how to compile in release mode. I was unable to compile for windows on Ubuntu 16 despite having all the dependencies installed. I tried may approaches using documentations from Crown source code, using public doc deom Dash and Bitcoin, all quite similar, so after whole day of trying I just got linux binaries no matter what.

So could someone provide with detailed documentation how to compile to get same results as you do? I don't need dependencies ie sudo apt install libventxxx, just final compilation commands
./autogen ... what flags for ./configure or make and so on

InstantX doesn't work

Not sure if it's something that will be included in future releases, Personally I like this one.
MIN_INSTANTX_PROTO_VERSION needs to be changed in instantx.h to enable this. otherwise it will be enabled when we pass protocol version 70103.

Crown Platforms Agents subsystem

Pulled from Gitlab - https://gitlab.crownplatform.com/crown/crown-core/issues

Link - https://gitlab.crownplatform.com/crown/crown-core/issues/211

Wallet sync gets stuck very often

Pulled from Gitlab - https://gitlab.crownplatform.com/crown/crown-core/issues

Link - https://gitlab.crownplatform.com/crown/crown-core/issues/315

dumpprivkey in windows 10 doesn't seem to work

tried different syntaxes and in both a windows 10 wallet as well as a wallet on a VM, the dumpprivkey doesn't work in the debug console window.

SCRIPT_ADDRESS / PUBKEY_ADDRESS Details

I am after help to find out the SCRIPT_ADDRESS and PUBKEY_ADDRESS decimal values for crown.

Is anyone able to provide me these details?