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

[Stabycroc]

Why do you absolutely want me to leave this place and go elsewhere? Answer me directly, we will waste less time.

Your organization has representatives? who are they (name)?

sorry I dont respond to people with offensive tone, have a great day sir

Where is my offense as a hypotetic shareholdery i ask you a simple legal question for a guarantee to know a name to whom my business consensus will provide a consistent portfolio and you write to me "i offend you"?

Now it's going to be really offensive to compare with the original request. This way you may compare with sudden consistency. Is it a communication error in your area of evolution because you are not qualified or are you really stupid or is it congenital?

And thats why i call her lil mis do lil... she could and can never be professional.....very ungrateful people in this dev crew.

they fail to understand bct forum is the starting point of contact of any crypto coin and discord is a  gamer chat app.
This isnt a gamer coin ( there to busy on there high perch i help build on the front lines for years and killing the work i dont premining and making the coin a mastercrap coin.)
never needed to change orignal specs of crw apart from the devs didnt have many coins and wanted a way to collect some.....
the mastercrap vote system was all fake or scam proposals that they paid out and even mis to lil agreed most of them were fake...

Ive work hard to promo crw when it was a REAL good speced and sha coin.... more than any other in crw history..
1st devs couldn't speak engrish.
they had no hash in early days i provided the blockchain movement and promo to other top hash miners of those day to put some hash on it. i could write a 3 page doc of the work ive done for crw or got others to help CRw, but isn't worth the time. "that was then , this is now"" is the way these devs act toward people like me that helped crw since its 1st days of life.
Infernal did the rest to make crw hit the roof.

and then the so called devs that never did 1 day of promo or customer support in crws history in the crypto space, i know cuz b4 the time crw hit trex i was mod of the only site that traded crw at that time.
Mutli highly trusted and respected  and some not so respected  old guards of crypto can back this up....even the crw devs could but u would have to go on discord for them to tell u :_0

Put ya kids fund into something tht would be showing more respect

[Stabycroc]

It now makes sense to understand why everything seems so complicated. There is more truth in the "the legality and stakeholders of your project" here than in my utensil drawer.  I guess I'll call my granddaughter back and let her know that she should keep this job, because her "recently found tuition money" must be paid with snake oil and flying cars if I invest in your CRW.

they lost the backing of old guards of crypto when they started there self payout massive premines.... like ive stated on this thread before CEO's dont vote for there pays or pay rise so why should a so called "community run coin"" need to payout any? pretty much 4 people built crw to greatness and then devs changes spec without consulting major holders in any way to fill there back pockets of the 4 peoples hard work they done to help grow which was a community coins.

the moment they started premining to pay themselves it become a business. And using a failed mn system without any governance over it...ms and there endless self paying of superblock to polish there boots killed the value and general trust of CRW..

If u read back threw CRw forum ul see like with them trying to say its POS when its actually mn-pos at best....

there basic understanding of wat is wat in crypto land and wat meanz wat in crypto land is lol able that they dont listen to people that clearly do,  lost in their own no crypto clue bubble.... dw there not the only 1s that try..

i tried to warn em of legal issues but didnt want to listen lol, greed does that to people esp people that had others doing the front line work to then respec coin to be greedy and damge the hard work the front line community helpers had done for CRW..

Da ja
Stabycroc ;_)>>

[karimmamdouh]

hello guys


what is the best pool to mine crown now


please annyone help me

[crowncoin_knight]

hello guys


what is the best pool to mine crown now


please annyone help me

Crown is not PoW anymore, moved to MNPoS. You can stake it by setting up Masternodes or Systemnodes. First coin out there (as far as my knowledge goes) where nodes produce blocks

https://medium.com/crownplatform/crown-masternode-and-sytemnode-proof-of-stake-consensus-system-mnpos-e6780ef534b3

[paramind22]

hello guys


what is the best pool to mine crown now


please annyone help me

Crown is not PoW anymore, moved to MNPoS. You can stake it by setting up Masternodes or Systemnodes. First coin out there (as far as my knowledge goes) where nodes produce blocks

https://medium.com/crownplatform/crown-masternode-and-sytemnode-proof-of-stake-consensus-system-mnpos-e6780ef534b3

Why does it come up as the most valuable coin to mine today at Coinwarz?

[crowncoin_knight]

hello guys


what is the best pool to mine crown now


please annyone help me

Crown is not PoW anymore, moved to MNPoS. You can stake it by setting up Masternodes or Systemnodes. First coin out there (as far as my knowledge goes) where nodes produce blocks

https://medium.com/crownplatform/crown-masternode-and-sytemnode-proof-of-stake-consensus-system-mnpos-e6780ef534b3

Why does it come up as the most valuable coin to mine today at Coinwarz?

Seems that Coinwarz has not updated the information on their site, current Crown client is 0.13.2

[FlowLive]

Coinwarz still has not updated Curecoin showing up as SHA256 which it is not for the couple of weeks or months...

[crowncoin_knight]

Crown Platform Development update for May 2019 is here

First off, an apology: we aren’t able to release v0.13.4 by 6 May. Although the current release candidate solves the slow sync problem, fixes the display of immature rewards, fixes the address labels problem, and (added bonus) reduces the memory requirement, it has proved to be a bit unstable. It will be released as soon as the instability is resolved.

Now that MN-PoS is operational we are looking forward to the next developments in the evolution of the Crown platform. In order of arrival, and scale, they are:

Trezor integration
NFT framework
Codebase update


Trezor integration
This is an exciting development which brings the security of a hardware wallet to Crown users and offers the possibility in future to start masternodes and systemnodes without requiring a full desktop wallet.

It involves several components, some of which are completed and others which are nearly complete. The completed components are the new address prefixes in Crown v0.13 (“Jade”) and update of the Electrum-Crown wallet to understand the new address format. Changes to Bitcore to understand the new address formats are in progress and could be ready within two weeks. Bitcore will provide an Insight explorer which allows access to information in the Crown blockchain. The final component is the actual Trezor integration. Our target release date is June 2019.

NFT framework
This will extend the use-cases for the Crown platform and allow users to develop their own applications. Non-fungible tokens can be used in myriad ways. The initial framework version is expected in the “Emerald” release and will provide registration and timestamping facilities. One of the most basic applications of NFTs is recording proof-of-existence and we already have people interested in developing more complex applications. To facilitate this we aim to provide developer documentation ahead of the release, expected in testnet by July 2019.
Further development of the NFT framework will be guided by user feedback on the initial release.

Codebase update
Crown is based on Bitcoin core v0.10 and v0.11. In computing and crypto terms this is ancient. Bitcoin v0.18 was released on 2 May 2019.
Updating the codebase is a major undertaking with the principal benefit of making future maintenance easier. It will also enhance security and provide access to additional features. There is no estimated completion date yet but the project will take several months.

https://medium.com/crownplatform/development-update-may-2019-a53cc2c7eb55

[BOoOBa]

Indeed the performance is correct and ever-increasing, we have tested the stability, conclusive result

[Lighthousesat]

Crown Platform Development update for May 2019 is here

First off, an apology: we aren’t able to release v0.13.4 by 6 May. Although the current release candidate solves the slow sync problem, fixes the display of immature rewards, fixes the address labels problem, and (added bonus) reduces the memory requirement, it has proved to be a bit unstable. It will be released as soon as the instability is resolved.

Now that MN-PoS is operational we are looking forward to the next developments in the evolution of the Crown platform. In order of arrival, and scale, they are:

Trezor integration
NFT framework
Codebase update


Trezor integration
This is an exciting development which brings the security of a hardware wallet to Crown users and offers the possibility in future to start masternodes and systemnodes without requiring a full desktop wallet.

It involves several components, some of which are completed and others which are nearly complete. The completed components are the new address prefixes in Crown v0.13 (“Jade”) and update of the Electrum-Crown wallet to understand the new address format. Changes to Bitcore to understand the new address formats are in progress and could be ready within two weeks. Bitcore will provide an Insight explorer which allows access to information in the Crown blockchain. The final component is the actual Trezor integration. Our target release date is June 2019.

NFT framework
This will extend the use-cases for the Crown platform and allow users to develop their own applications. Non-fungible tokens can be used in myriad ways. The initial framework version is expected in the “Emerald” release and will provide registration and timestamping facilities. One of the most basic applications of NFTs is recording proof-of-existence and we already have people interested in developing more complex applications. To facilitate this we aim to provide developer documentation ahead of the release, expected in testnet by July 2019.
Further development of the NFT framework will be guided by user feedback on the initial release.

Codebase update
Crown is based on Bitcoin core v0.10 and v0.11. In computing and crypto terms this is ancient. Bitcoin v0.18 was released on 2 May 2019.
Updating the codebase is a major undertaking with the principal benefit of making future maintenance easier. It will also enhance security and provide access to additional features. There is no estimated completion date yet but the project will take several months.

https://medium.com/crownplatform/development-update-may-2019-a53cc2c7eb55



Thanks for the update! Looking forward to this release myself. started a new wallet to setup new masternode on May 1st. The sync is still over 4 years out. At this rate it will take a couple months to sync up lol. Hopefully yall get the bugs out of it so we can keep moving forward.

Thanks again for your hard work in keeping CRW working and progressing!

[crowncoin_knight]

Awesome video interview with Jose aka Crownfan from CrownPlatform during the Coinfest UK event in Manchester in April 2019

https://vimeo.com/334693605


Few words also on the Interview at CoinFest:

- Crown is a network for decentralised money and applications. We are working on further decentralised registries to leverage all the potentials of Bitcoin Core and combine them with frameworks that are typical of other chains such as Ethereum  / EOS.

- Crown is not only unique for trying to reach these technical goals, it is also unique in the way we organise to reach them. In this sense, the way is also our goal. We can only leverage the technology we are building if we also use it and integrate it in our own lifes. Devs fx do this as they live from the value they generate for Crown by building on it. So do many other dozens of contributors who accept CRW, who design new use cases or who have social relations on and through the chain.

- We always need to ask ourselves how the technology we are building and using impacts and changes our social and cultural ecosystems.

- The Crown governance system is one of the few working examples. It is not in the custody of anyone and depends on the totality of MN votes.

- We now have over 2000 mining nodes who can produce blocks without the need for centralised pools or middlemen.

- More important milestones are coming up.

- this Interview was just a side gig. The NFT presentation video will be up shortly. Its more informative and longer. Looking forward to it.

[R30]

Dear crown community!
I read the intro on https://crown.tech/learn-more-about-crown and I didn't find any special stuff.
Could someone tell me as easy as possible about crown progress with links please?
P.S. I know another similar platform - shiftnrg but they already have working dapps, but haven't masternodes unfortunately.
Cheer!

[crowncoin_knight]

Dear crown community!
I read the intro on https://crown.tech/learn-more-about-crown and I didn't find any special stuff.
Could someone tell me as easy as possible about crown progress with links please?
P.S. I know another similar platform - shiftnrg but they already have working dapps, but haven't masternodes unfortunately.
Cheer!

Key aspects

1. We just transited from a BTC mergemined PoW to a crypto industry first all-node-staking PoS protocol demonstrating our community strength / will to innovate during a bear market and making our stakeholder structure decentralized in a true way.
https://medium.com/crownplatform/crown-masternode-and-sytemnode-proof-of-stake-consensus-system-mnpos-e6780ef534b3

2. We have a clear vision for Crown: a blockchian-as-a-service model, where anybody who wants to work with blockchain is invited to build their ideas: ranging from registering any physical or digital asset using NFTs, build/host an applicaiton, transact value, or create any use case imaginable on the Crown chain. Leaving the future of blockchain tech on natural, community-driven forces rather than pushing one usecase and telling people how it should be used.
https://medium.com/crownplatform/crown-blockchain-platform-overview-f1aff7d341a8

3. Our next development goal is the release of NFT's which will enable the registration of any asset on the Crown Blockchain, our solution is nearly already (in private testnet of our tech lead Artem), you can watch the QA with our tech Lead Artem here:
https://medium.com/crownplatform/artem-ashot-dev-q-a-99c27ab64c84

4. We are a community driven platform of approximately 5k users mostly from the western part of the world with largest communities coming from the US, UK, Netherlands, Germany, Czech Republic, Spain, Korea, Brazil, Italy, Australia and New Zealand. There is no centralized team, but rather a decentralized model of contributors, our communication channels are open and transparent. Our community meets in person 3 to 4 times a year since December 2016 when we met for the first time in London.
https://medium.com/crownplatform/crown-coinfestuk-2019-april-4th-5th-6th-2019-d5210bca6a05
https://medium.com/crownplatform/malta-blockchain-summit-review-8d9108ba41e7
https://medium.com/crownplatform/crown-meeting-culminates-with-use-case-focused-community-meetup-at-the-blockchainhotel-in-essen-c496f08df715
https://medium.com/crownplatform/crown-miami-meetup-recap-6a154fa2342d
https://bitcointalk.org/index.php?topic=815487.msg24536634#msg24536634
https://bitcointalk.org/index.php?topic=815487.msg21189347#msg21189347
https://bitcointalk.org/index.php?topic=815487.msg18823814#msg18823814
https://bitcointalk.org/index.php?topic=815487.msg17094738#msg17094738


5. We have a decentralized governance proposal system, which enables the development of Crown to be independent and self-sustainable
https://crown.tech/governance/
https://medium.com/crownplatform/decentralized-governance-readjustment-f8c119c632f4

6. Our blockchain is powered by over 2k of nodes - masternodes and systemnodes: the community is fully in charge of the future of the blockchain
https://medium.com/crownplatform/crown-mn-and-sn-rates-of-roi-f317247c208


7. Our development repositories are open to the public
https://medium.com/crownplatform/crown-core-team-goes-public-with-repositories-and-workflow-3b5fcc5278b0


8. Our blockchain was fairly launched in October 2014 during the pre-ICO times in a fully transparent way
https://bitcointalk.org/index.php?topic=815487.0

9. We are not an anonymous platform, our identities are faces are known to the world.
https://crown.tech/about/

10. We are currently listed on 4 quality exchanges, we have not paid them to list us, that is our philosophy.
https://bittrex.com/Market/Index?MarketName=BTC-CRW
https://upbit.com/exchange?code=CRIX.UPBIT.BTC-CRW
https://wallet.crypto-bridge.org/market/BRIDGE.CRW_BRIDGE.BTC
https://www.litebit.eu/en/buy/crown

11. You can see a summary of the Crown blockchain in this presentation
https://medium.com/crownplatform/crown-platform-a3c1ad774bff

12. We were selected as one of the few blockchain and featured on a US based TV show Success Files hosted by Rob Lowe
https://medium.com/crownplatform/crown-platform-featured-on-success-files-presented-by-rob-lowe-4a5be9bd3308

13. You can see what we represent in this short video
https://www.youtube.com/watch?v=fI_zjKxzVaA

[crowncoin_knight]

Recommended CROWN update v0.13.4.0

We are pleased to announce the release of Crown v0.13.4.0. This is a recommended update.


Although you can continue to run v0.13.2, unless you have already taken steps to mitigate the increased RAM and CPU usage, you almost certainly will hit problems further down the line. We recommend everyone update at their earliest convenience.

v0.13.4.0 is a recommended update for all users

What does it include?

It was originally planned to include three fixes but actually includes four and some enhancements:

The long awaited fix to the v0.13 sync problem.
Following the v0.13 update, a number of users experienced very severe performance problems with syncing the blockchain. A number of workarounds were published, which successfully circumvented the problem for most of those users. Others continued to experience unacceptably slow syncing. Ashot and presstab have worked hard to identify and resolve the issue.
With the new update, everyone with a part-way decent internet connection should be able to complete a full sync in less than 4 hours.

Incorrect display of rewards on the wallet summary screen.
Rewards were showing as mature (available to spend and stake) before they actually were.
Fresh masternode and systemnode rewards, and staking rewards now show as “Immature” in the wallet summary screen until they receive the required 100 confirmations.

Address labels.
Ashot has worked his magic in the wallet and old labels display correctly with no intervention from the user.

CPU and memory usage.
It became apparent during development that there was a bigger and more pressing problem than any of the preceding three. Nodes and wallets were using much more RAM and CPU than in v0.12.5.3. Depending on the hardware they were running on, nodes could exhaust the available RAM and crash themselves or even the VPS after a couple of days. Painstaking research showed the increase to be related to code hardening against one of the PoS attack vectors. Presstab reworked the code so that it still provides the same protection but at much lower resource cost.

Installer enhancements.
While waiting for the code fixes in v0.13.4 a number of workarounds for the sync and resource usage were deployed. Although they should no longer be required it was thought beneficial to provide easy access to them through the installation/update script. So the script now includes options to add the watchdog script to a new or existing node, to sync a node or wallet using the bootstrap, and to install a pipeline build.

I’m sold, how do I upgrade?
As always, the new release is a drop-in replacement. Essentially, make a backup of your wallet.dat, shutdown your wallet and node(s), replace the executables and restart. The details vary from platform to platform and environment.

Hosted node
If you use a hosted masternode/systemnode service they should take care of the node update for you. Since this is not a mandatory update you might need to ask them, but given the resource savings to be made by upgrading it’s likely they’ll be way ahead of you! You can update your node(s) before or after your wallet; the order is unimportant.

QT wallet
Restart the wallet and it should prompt you to download the update.

Self hosted node (linux) or a wallet
If you are already using the watchdog script you should disable it before upgrading (otherwise it could restart the node at an inopportune moment). See below.
If you’re not interested in the watchdog and bootstrap simply use the one-liner to update a masternode or systemnode. Log on to your server and run
sudo apt-get install curl -y && curl -s https://raw.githubusercontent.com/Crowndev/crowncoin/master/scripts/crown-server-install.sh | bash -s

All environments
The network protocol version has not changed so it isn’t necessary to issue start-alias commands for masternodes or systemnodes if you have already upgraded to v0.13.2.0

What about the watchdog and bootstrap thingies?
The installation/update script has new options which could still be useful in certain circumstances. If you want to take advantage of them, we recommend you download the latest version of the script and run it directly (doing so gives you the most flexibility, but if that sounds too complicated see below).

Download the installer
You can use curl or wget. The following example uses curl. Put the installer somewhere in your path (/usr/local/bin is recommended) and make sure it is executable.
sudo curl -o /usr/local/bin/crown-server-install.sh https://raw.githubusercontent.com/Crowndev/crowncoin/master/scripts/crown-server-install.sh
sudo chmod +x /usr/local/bin/crown-server-install.sh

watchdog
The watchdog as originally published ran every 15 minutes and did two things:
Check if crownd is running, start if it is isn’t.
Check free memory and restart crownd if it is “too low”.
If you are already using the watchdog it won’t do any harm to continue running it after the upgrade, but you should disable the cron entry for the duration of the upgrade. Use the command
crontab -e and comment out the watchdog entry by putting a hash sign (#) at the start of the line. Uncomment the line (by removing the hash sign) after upgrading.

The watchdog could still be useful after the upgrade. It is very unlikely you would need the memory checking. However, making sure your node is running every 15 minutes isn’t a bad thing (but don’t use the watchdog in conjunction with systemd or any other automatic process starter/monitoring system).

The installer has a new option, -w followed by a number 1 or 2 which corresponds exactly with the two actions described above. If you want to add the watchdog to an existing instance at the same time as upgrading then the command to use is
crown-server-install.sh -w 1
or, if you want to use the free memory checking as well
crown-server-install.sh -w 2

bootstrap
Syncing performance in the v0.13.4 update is vastly improved. Pretty much everyone should be able to sync a new node across the network, from scratch, in less than four hours. With a good internet connection, we saw several such syncs complete in less than two hours during testing.
There may still be times when syncing with the bootstrap is useful so the installer now has the option to use it. Most VPSs have a good internet connection but your local connection may not be as fast or reliable. We anticipate some wallet installations might benefit from syncing with the bootstrap, which can be done using the -b option. For example
crown-server-install.sh -c -b

The -c option indicates this is a new wallet installation (-w is already used for the watchdog). This example will ensure your system is updated, download the release package and the latest bootstrap, create swap space if you don’t have any, write a new crown.conf, update your firewall, install the release package, unzip the bootstrap into the datadir and start the daemon.

wait, there’s more!
Unless told otherwise the installer will fetch the latest release package from our Github mirror. There may be times when you want to use some other version, specifically a test version from a Gitlab pipeline build. A number of community members helped test this version before release and we’re grateful for their assistance. If you’d like to get involved and help with testing in future please get in touch via the #contributor-general channel in Discord.

Use the -j option to specify a pipeline build to install or update to. For example
crown-server-install.sh -j 6114

The installer has a number of other options. They are mostly additive although there are some mutually exclusive combinations (for instance you can’t specify both -m for a masternode and -s for a systemnode in a single invocation). You could combine all the options we’ve seen so far here, like
crown-server-install.sh -j 6114 -c -b -w 1
to install a pipeline build as a wallet, sync with the bootstrap and enable the watchdog (level 1).

We plan to publish another article soon describing the installer in more detail.

Wrapping up
Thank you to everyone who has upgraded to v0.13.2 for your patience while we dealt with the glitches and performance issues. We recommend you update at your earliest convenience.
There are still a number of v0.12.5.x nodes and wallets which have not upgraded. Although the node count is down about 20% the network hasn’t really missed them but they have been missing out on both node rewards and staking rewards. We hope these fixes will encourage their owners to upgrade those nodes and rejoin the network.

If you have any questions or issues with the upgrade or want to know more or even just chat about Crown, please contact us in Discord or Telegram.

https://medium.com/crownplatform/recommended-update-v0-13-4-0-6791cb0599a8

[crowncoin_knight]

The Crown tech lead Artem is nearly finished with his long awaited work on the #NFT (Non-fungible Token) framework.
A technical document will be released in June, followed by the release of the code into testnet. Crown is now one step closer to the Emerald release milestone!

[BOoOBa]

I have analyzed your project, it is realistic and seems to be performing well. Can you confirm when the next division of annual percentages will take place in 2020 or 2021?

[BOoOBa]

I see that the fintech sector is exploding with new and innovative products and services. Since it covers monetary transactions in the fields of credit, payments, insurance and trading, most of which are processed in end-to-end processing (STP) mode, regulatory compliance is a must. Promoting innovation without the overhead costs of over-regulation and consumer protection requires a balanced approach, for which regulators in many countries have adopted a "regulatory sandbox" approach and allows authorised companies to test their innovative products, services, business models and delivery mechanisms in the real market, with real consumers, on a trial basis. It helps reduce time-to-market at low cost, improves access to capital and ensures compliance with compliance requirements. These regulatory sandboxes allow direct communication between fintech developers, companies and regulators, while mitigating the risks of unintended negative consequences, such as security breaches. It is nice to see that CRW meets these criteria.

[Mountain_Crew]

I read this about CRW:

The Crown chain is launched in 2014 and has now evolved into an open source Proof of Stake (PoS) block chain protocol that provides a distributed consensus system.

Crown MNPOS' secure protocol is unique in that it uses a new concept called pile indicators and overcomes known attack vectors in consensus mechanisms.

In its current use Crown is a global financial platform accessible to all connected in a global network from which transactions are managed and carried out through a communication channel (MN nodes) and through its software connected to the network 24 hours a day, 7 days a week.

MN Masternodes provide a unique cold picketing solution that allows you to receive the "network reward" to generate regular revenue per intelligent staking system currently supported. Its protocol operation makes it possible to drastically reduce the costs associated with the power consumption problems currently encountered with existing public and private blockchain protocols. Crown requires much less electricity to operate.

Crown supports an innovative communicative community approach through its CDGP (Crown Decentralized Governance Proposal) system that allows the community to be fully involved through user-generated proposals.

In addition, the legal compliance and transparency of its decentralized governance model. Crown is auditable and operates in a secure execution environment with very low transaction costs.

Ultimately, the Crown platform is moving in the right direction and will have the scalable objective of operating as a one-way solution to provide a useful set of programmable infrastructure components for management, deployment, planning for developers, individuals and businesses and for designing simple or complex applications independently, directly within Crown's secure network.

More IT solutions and unique innovations on Crown are coming soon.

That's exactly what it is! I couldn't have described it better

[crowncoin_knight]

Development update June 2019

Onwards and upwards


Our developers, Artem and Ashot have been hard at work since the last development update.

Version 0.13.4.0 was released a week later than we had hoped but was worth the wait. Everyone who has updated is experiencing improved stability, lower resource consumption and fast syncing. The network node count has recovered from its dip and there are currently around 1000 masternodes and 1500 systemnodes online. The systemnode count is still much lower than it traditionally has been because the depressed price makes them unprofitable (in fiat terms) on many hosting platforms at present. However, canny community members know the systemnode ROI is higher than the masternode ROI, take a long term view and keep running those nodes.

Trezor

The final pre-reqs for Trezor integration have been completed:
Bitcore-Crown and the associated Crownsight explorer
the pull-requests to Trezor-firmware for the prefix change and explorer links
We now have to wait for Trezor to push a new firmware release. These happen roughly every 3 months and the last was in March so we’re hoping it will happen this month.

NFT framework

Artem is still concentrating on development of the non-fungible token (NFT) framework. He has completed coding of most of the APIs (get, getbytxid, totalsupply, balanceof, ownerof) and has a couple more still in progress. He’ll be working on the documentation soon and we’re hopeful for a testnet release on 20 June 2019.

Codebase refresh

Ashot evaluated the best Bitcoin codebase to migrate to and has settled on v0.17. This is going to be a complex and time-consuming process. He basically has to take all the changes over the last four years which made Crown Crown, and re-apply them to a clean Bitcoin base. A very rough guestimate for how long this might take is 3–6 months.

Astute readers might wonder why we chose Bitcoin v0.17 rather than v0.18 since the amount of effort is about the same. The reason is account support. Accounts are the flaky wallet code for partitioning wallet funds into separate chunks. Some centralised exchanges are known to rely on this functionality. In Bitcoin v0.17 the functionality is deprecated but still present. In Bitcoin v0.18 it is removed completely. Switching to the v0.18 codebase without prior agreement from exchanges could cause us problems.

The new codebase will bring security, speed and stability enhancements. It will also make it easier to keep up to date with critical Bitcoin changes and ease maintenance into the future.

https://medium.com/crownplatform/development-update-june-2019-a1086c5d3aa0

[crowncoin_knight]

Attention masternode owners

It’s time to vote!

Being a masternode owner isn’t just about earning a passive income. With great rewards comes great responsibility. Masternode owners are responsible for enacting the Crown Decentralised Governance Proposal system which decides the future direction of the Crown project, and allocates funds from the superblock to the current proposals.

If you need a reminder of what the CDGP system is about please take a look at the governance section of the Crown website, and familiarise yourself with the superblock calendar and the voting system.

TL;DR
It is crucially important that you exercise your duty to vote in the monthly superblock “election”.
The next superblock is at block 2,419,200 which is estimated to occur at about 07:20 UTC on 17 June 2019. However, voting closes 2880 blocks (about 2 days) before that but your masternode must remain online until the actual superblock for your vote(s) to count.
Please go and vote now!

Why?
Last month, in superblock 2,376,000 the submitted proposals asked for a combined total amount of Crown which exceeded the available funds. The proposal with the largest ask received the smallest number of votes and consequently, although it passed, it did not get funded. This put continued platform development in jeopardy. Also, fewer than 20% of the enabled masternodes actually voted.
That’s right, the majority of masternode owners abdicated their responsibility and left it up to a minority of a subset of the Crown community to decide how the project should progress and which proposals to fund.

This month, for superblock 2,419,200 the submitted proposals again ask for a combined total amount of Crown which exceeds the superblock maximum of 54,000 CRW. It is possible that there will be some additional proposals submitted for this superblock which will further increase the competition for the limited funds available. Almost inevitably that means some proposals will fail to be funded, even if they pass (a proposal passes when the number of Yes votes exceeds the number of No votes by at least 10% of the number of enabled masternodes).
At the time of writing, only about 30% of masternodes have voted in this superblock.
We need all masternode owners to carefully review the submitted proposals and vote according to their interpretation of the best interests of the project.

Each proposal contains a link to a detailed description of what it entails, how much funding is sought, who is asking for it and doing the work, and the benefits it will bring. Please take the time to review all the proposals and to consider (among other things)

- the total available budget
- the individual amounts requested
- the other proposals amounts requested
- the priorities of the project
- the impact of each proposal on those priorities if it is funded and if it isn’t funded
- just passing may not be sufficient for a proposal to be funded

Hint: it would be a really good thing if the development and infrastructure proposals passed!

Where to find the proposals?
You can see a pretty colour overview of the active proposals at crowncentral.net:

An enhanced proposal view but you can’t vote directly here
You can also see the submitted proposals directly in your QT wallet in the Voting tab of the Masternodes page:

The voting tab in the QT wallet
Most importantly, you can also vote for them here. But before voting, please take time to click on the URL for each proposal to read the details. Some of the descriptions can be found in the Crown forum:

Proposal descriptions in the Crown forum
but proposal owners can put the description anywhere (Google docs is another popular location).
The description should include essentials like who is making the proposal, how much they’re asking and what the community gets in return. There should also be contact details so if you have any questions about the proposal you can contact the proposer and seek clarification or offer comments and feedback.

Questions and comments are positively encouraged because they increase participation and help build the community. If you vote No on a proposal it would be really helpful to the proposer if you let them know why you voted that way. You can ask questions and leave comments in the #proposals channel in Discord.

How to vote

Each proposal includes instructions on how to cast your vote. There are two cryptic looking lines of the form

How To Vote YES: mnbudget vote-many 3c67369ab31786ab1bff83c3634a71eb3b9b8983260d1f97c0e664bc741cdb4f yes
How To Vote NO: mnbudget vote-many 3c67369ab31786ab1bff83c3634a71eb3b9b8983260d1f97c0e664bc741cdb4f no

which are what you need to know if you’re going to vote using the command line interface or the debug console of the QT wallet. You can also vote directly from the Voting tab in the QT GUI. Whichever method you’re going to use, your wallet must be unlocked before you can vote.
To vote using the QT GUI, click on a proposal to highlight it and then click the appropriate vote-many button. The wallet will respond with a confirmation request window:

After voting you should get a result window similar to:

Due to a bug in the QT wallet, votes don’t always register on the first attempt. If you don’t get a result window like this, you need to vote again.
Important. You can vote more than once for any proposal but only your last vote before the voting window closes counts. So you can change your mind on a proposal if you want to.

Remember: this superblock is over-full. It is probable that not every proposal which passes will get funded. If passing proposals don’t get funded there is a possibility that some superblock funds will remain unallocated and be wasted (as happened last month). One of your responsibilities as a masternode owner is to ensure funds are allocated in the best interests of the project. You may want to change one or more of your votes to make that happen.

Please vote as soon as possible.
Please also check again before the voting window closes (around 07:20 UTC on 15 June) because circumstances could have changed and you may want to vote again.

So far only about 30% of masternodes have voted. Let’s see if we can double that number over this coming weekend.

https://medium.com/crownplatform/attention-masternode-owners-4c15040f285