LETS MAKE CROWN GREAT AGAIN

hey what up. love your poem

𝔻𝕚𝕘𝕚𝕥𝕒𝕝 𝕂𝕟𝕚𝕘𝕙𝕥𝕤

Long, long ago, in Europe’s heart,
When anarchy tore lands apart,
The Bohemian Crown yet unformed,
Noble families in conflict swarmed.

Amidst this strife, young Otakar,
A prince, adventurous, like a star.
He rode with knights, his people to save,
From bandits and thieves, he was brave.

Suddenly, his kingly father’s fall,
Turned his life into a fugitive’s call.
The emperor's schemes, a cruel twist,
Yet Otakar’s spirit did persist.

He fought to reclaim his rightful throne,
Through years of struggle, he stood alone.
First Bohemian king, his title earned,
For his children, the Crown confirmed.

Eight centuries passed in Europe’s core,
Digital knights dreamt of yore.
Bitcoin enthusiasts, with history's zeal,
Saw the Crown as a symbol real.

In October 2014, the chain’s first link,
Crowncoin was born, a digital brink.
Launched fairly, in cypherpunk pride,
A project where justice and freedom abide.

From riches risen, to zero’s ground,
Yet the blockchain’s heart beats, unbound.
For ten years straight, it’s journeyed on,
The digital knights’ legacy lives on.

A fair, honest realm they envision still,
A just domain, through metaverse will.
Can a pure dream inspired by history's light,
Become reality in the digital night?

The crypto world, on shaky ground,
Fueled by memecoins and wealth unbound.
First, we must foster values bright,
Only then can blockchain's path be right.

The industry must fall, to rise anew,
With purpose clear, and vision true.
Build your kingdom with justice and grace,
A digital realm for all to embrace.

Not sure if this is active, you can check it out

https://medium.com/crownplatform/incentivised-token-creation-3836ee588694

100%

you could try starting the daemon with -platformreindex
So instead of just

crownd


Do

crownd -platformreindex

best is to join the Crown discord there are dedicated channels for your issue #support-wallet or #support-nodes

there is a lot of information on Crown NFTs here: https://www.crownplatform.com/nft-framework/

https://medium.com/crownplatform/crown-core-0-14-0-2-released-b04197a48859

Crown Core 0.14.0.2 released
Recommended update to stabilize database sync

A new version of Crown Core has been released. It solves inconsistencies between the blocks database and the platform database by levelling out their contents before synchronising to the network.

It is now possible to quickly reindex the NFT database without having to reindex the whole blockchain. To do so you can run platformreindex in the wallet repair GUI. Alternatively, you can run the Crown software with the -platformreindex argument or by adding platformreindex=1 to the crown.conf file.
This update is recommended for users experiencing stuck wallets and for VPS providers that run large amounts of daemons.

Updating Windows and Mac

QT wallets will prompt automatically to download the new version next time they are started. The update procedure is the same as for the previous Emerald update:

    Download the file when prompted.
    Shutdown the wallet.
    Open the downloaded update. This will unzip it into a directory in your downloads folder. Navigate to the Crown-v0.14.0.2-Emerald\bin folder.
    Copy the executables over the old ones.
    Restart the wallet.

Linux

For masternodes, systemnodes and linux wallets the one line script to do all of the above is

sudo curl -s https://gitlab.crownplatform.com/crown/crown-core/raw/master/scripts/crown-server-install.sh | bash -s

You can also download the new version on Github

https://github.com/Crowndev/crown-core/releases/tag/v0.14.0.2-Emerald

https://medium.com/crownplatform/crown-platform-development-flash-21-07-2020-6704b8fd0cb



Dev Flash 21.07.2020
NFT resync functionality coming along. Trezor testers wanted. Crown Bounty program launched. Website drafts evolving.

Ashot
has been working on the nftoken database resync functionality. The release candidate should be ready for public testing by the end of the week. A non-mandatory update will follow shortly. This new version will resync the NFT database to avoid tx-nft db conflicts that led to client instability for some users.

New Crown-Electrum builds
are available for testing. You can get all the information in the Discord channel #bitcore-electrum-testing.

A Crown bounty program
has been launched by several contributors. Read all the details here and engage in open issues to receive rewards!

Bitcore
is progressing slowly, there are no relevant updates on this front.

Website
development for the new community presence has started after intensive feedback rounds on design and structure. You can have a look at the designs and discusssions in Discord.

Stay tuned for more development updates and general news.

https://medium.com/crownplatform/crown-bounty-program-9ad21b853e9c

Crown bounty program

Incentivising community development contributions

We are pleased to announce the launch of the Crown bounty program. Thanks to the community “sweeper” superblock proposals and some donations, we now have some funds to cover bounties for community-delivered projects.

Several months ago we reviewed the Gitlab open issues and identified some ideal candidates https://gitlab.crownplatform.com/crown/crown-core/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Community for tackling by community members or external coders. We tagged them with the “Community” label and published a Medium article inviting community effort to resolve some of those issues. With no bounties available, unsurprisingly, the response was not great!

The original bounty projects list was a Google docs spreadsheet. Technology progresses and the list will soon be tokenised using the Crown NFT framework. The community fund does not currently have sufficient balance to cover all of the bounty program tasks. We plan to add a “Bounty” label to the Gitlab issues which are active at any one time and also tag those issues with the level of bounty allocated. This will make it easy for anyone to see which issues currently have a bounty attached, and the amount. Simply click here and there’s no need to refer to the spreadsheet.

We will continue to sweep unallocated funds from future superblocks and some community members have indicated a willingness to donate to the fund so we expect to be able to cover all of the bounty tasks in time. If you would like to donate to the community fund please send CRW to CRWW8wDhtZjv8rNfzySvsR2HyGZXRUZwJmZj

If you are interested in working on a bounty task please comment directly in the Gitlab issue, or use the Discord Gitlab updater bot to update the issue, or simply comment in the #bounty-program channel in Discord.

New Crown Platform Website designs are being worked on. Coding will start soon

Landing page http://mockupr.com/mu/kkzi9122

Roadmap page http://mockupr.com/mu/eqgr1788

Wallet page http://mockupr.com/mu/fxxx2429

More pages in work in progress

https://medium.com/crownplatform/crown-development-update-07-07-2020-b9a6e2a54f56

Crown Development Update 07.07.2020
New biweekly format to bring you the latest Crown Platform news

In this edition of the Crown development update we bring you the latest news on the NFT Framework, Bitcore, Crown-Electrum and GitLab CI/CD integration tools. Last week we skipped the development meeting and we have moved it to a biweekly rhythm. It adapts better to our current progress and brings more consistent and digested updates.

NFT Framework

Code lead Ashot has continued debugging logs and has located the main issue we have been experiencing lately, which materialises in some nodes freezing on a certain blockheight before new NFT data is written to the chain. This issue is due to inconsistency between blocks / nftoken databases and can be solved levelling out the amount of information contained in each of them before syncing to the network. In order to improve user experience, Ashot is also going to integrate a new -reindex / -resync option starting on the first NFT block instead of at block 0 so that the process will be much faster and easier to complete by affected users. These fixes are estimated to take 1–2 weeks and will be released in a non-mandatory update.

Crown-Electrum

Community developer Ahmedbodi has been working on a new version of the popular lightweight Electrum client. Testing is advanced and Trezor compatibility has been confirmed, although there are still some bugs to iron out when importing previous CRW Trezor key paths. Once everything is working smoothly, the new version will be officially released.

Bitcore / Insight APIs

Developer Zhanzhenzhen has kept up the work on Bitcore and is now integrating the nfproto APIs. Bitcore will be a key piece to develop on the NFT Framework and will be mainly ued to interact with through the Insight APIs. If you are a developer or an entrepreneur looking to use these featuers, feel free to give feedback on the specs you would like them to include.

GitLab Infrastructure and CI / CDs

The infrastructure team is working on the GitLab environment to integrate Electrum to the official Crown Platform repositories and be able to make these processes easier in future. If you want to help out with Docker or have a high level of Python knowledge, feel free to reach out and give a hand.

A Wordpress plugin to create protocols

Recently, contributor Defunctec released a wordpress plugin to create Crown Platform NF-Protocols. It is available on Github:
defunctec/crown-protocol-generator
A simple Wordpress plugin to create NFT protocols on the Crown blockchain. You need a VPS with (recommended) 2GB RAM, 1…
github.com

NFTRegSign methods

Defuncted has also provided a short and understandable explanation of the NFTRegSign modalities available when creating a new NF-Protocol:

1 (SelfSign)
Imagine being the owner of the protocol but anyone can make a token using this protocol. Someone with enough Crown to sign a NFT transaction can use this protocol to create tokens from their wallet, even though they’re not the protocol owner.

2 (SignByCreator)
Owner makes a protocol and only the owners addresses can be used to create tokens. Unlike “SelfSign” only the owner of the protocol can use addresses associated with the protocol wallet, a user for example cannot use their own addresses.

3 (SignPayer)
This allows an outside address to be used to own a NFT but the NFT must be created via the protocol owners wallet. Eg, You own a website, create a protocol with SignPayer. You can then allow users to enter their address as the NFT owner to create and own tokens using your protocol.

Heartbeat Protocol

The heartbeat NF-Protocol has been created by walkjivefly to keep historical data on Masternode and Systemnode coutns. The tokens issued by this protocol every 6 hours can be called upon to visualize historical data on MN/SN counts and can be used by anyone wanting to leverage this information.

That is all for now on the development front. You are invited to join us on Discord if you want to keep track of everything else that is going on.

Thank you for supporting the Crown Platform project!

You have probably hit the "NFT-glitch" we are experiencing and now fixing https://gitlab.crownplatform.com/crown/crown-core/-/issues/362
If you post the debug.log and we can confirm that is the case.

Does your wallet run 24/7 or do you only run it periodically? On which platform? When was the last wallet restart and did you shut it down cleanly before that?

It would be a good idea to take this opportunity to upgrade your wallet to Artem's hotfix code. The NFT-glitch hotfix builds are at OSX(DMG):

https://gitlab.crownplatform.com/crown/crown-core/-/jobs/7405/artifacts/download
and linux64:
https://gitlab.crownplatform.com/crown/crown-core/-/jobs/7406/artifacts/download
and win64:
https://gitlab.crownplatform.com/crown/crown-core/-/jobs/7407/artifacts/download

Download the appropriate artifact, unzip it, replace the crownd and/or crown-qt by the new ones.

Next you need to straighten out your chain. The quickest way will be with a snapshot of the blocks, chainstate and platform folders from one of your MNs. The alternative is to sync from the latest bootstrap but that'll take longer.

https://medium.com/crownplatform/crw-is-now-on-polispay-cfd6da3171a4

CRW is now on PolisPay
Adding more real-world utility to Crown Platform


PolisPay has released a new version for their popular Desktop application and one of the new highlights is added support for CRW. You can now store, send and receive CRW on the non-custodial PolisPay wallet, as well as use them for a battery of services that are provided in-app such as gift cards, vouchers, phone and card top ups. More upcoming functionalities like the long awaited “Shift” function to swap coins will see the light along with the new mobile versions of the app once Google Play and App Store validate it in the next days.

To help the Crown Platform community onboard PolisPay and learn how to use it, the PolisPay team will be holding a Webinar on Tuesday 19 May at 15:00 UTC. The details will be shared through Twitter, Discord and Telegram, so stay tuned!

You can download the latest PolisPay v8.5.0 desktop application here: https://github.com/grupokindynos/polispay-releases/releases/tag/v8.5.0

Thank you for supporting Crown Platform!

https://medium.com/crownplatform/crown-development-meeting-minutes-04-05-2020-58c082db9eb6

Crown development meeting minutes 04/05/2020
Just the facts, ma’am

Present: crowncoin-knight, Crownfan, pjcltd, walkjivefly

Ashot couldn’t make the meeting but afterwards sent a very short report saying he is still working on the NFT integration and expects it to take about another two weeks. He also provided a link to the essential barebones NFT transaction structure which has now been passed on to the Bitcore and Electrum developers.

There is no progress on the NFT trading design specification documentation.

Community developer Zhen is still working on the Bitcore NFT adaptation. He asked for a brief requirements specification. Our minimum requirements are:
    * correctly decodes NFT transactions
    * it can be used to register both NFT protocols and NF tokens.

    crowncoin-knight will check with Farid of Chronovault what else he requires from it.

Our “on loan” MUE engineer is trying to get ElectrumX to sync and is currently stuck at the first block with NFT transactions. There may be as yet undiscovered NFT-related issues in the Electrum-Crown wallet code as well.
   
Crownfan has been testing PolisPay. The integration is not quite complete yet but hopefully will be released this week.

walkjivefly has added dedicated competition and CRWcard pages to the Platform Monitor, and added geolocation, country totals and map display to the masternode and systemnode pages.

A number of users are experiencing block validation errors on some blocks containing NFT transactions. Their node or wallet ends up banning all of its peers and/or being banned by all of its peers and is then stuck, unable to do anything. This only happens to a small number of users on a small number of blocks. The symptoms are “well known”, the underlying reason is not. Ideally, we need Artem to investigate since Ashot has not had time to do so. Unfortunately, despite there having been at least seven occurrences we know of, most victims have not been uploading their debug.logs as requested so we have very little documentation for Artem/Ashot to work from. The problem does not reproduce at will which makes debugging it much harder.

https://medium.com/crownplatform/crown-development-meeting-minutes-27-04-2020-b630fb2d0a0e

Crown development meeting minutes 27/04/2020
Just the facts, ma’am

Present: ashot, crowncoin-knight, Crownfan, pjcltd, walkjivefly

1. Ashot pushed another MN/SN commit to the Bitcoin codebase update and has started on the NFT integration. In view of the complexity he has revised downwards the completion estimate to 80%. In addition to the NFT integration there are some new RPCs which are stubbed out at present which will need to be implemented.

2. walkjivefly asked Ashot if he could possibly document what he learns about the NFT framework implementation during integration. We are rather short of documentation (as the Bitcore and Electrum community developers have discovered) and despite the extra workload, this would be a good chance to fill a hole in the NFT framework. It could perhaps avoid similar issues with NBitcoin integration further down the line, as required for BTCPay server integration.

3. An agreement has been reached with PolisPay, and funded by a small group of contributors (led by Crownfan), to integrate Crown into their wallet. The Crown node is synced and we are now discussing launch dates.

4. walkjivefly asked what is our official position regarding running masternodes/systemnodes on Windows. Among the recent sync issues have been some on masternodes running on Windows. Despite asking for precise details of the circumstances leading to whatever the issue was, very few users actually provided any or the accompanying debug.log. One user did and it became apparent that their particular sync problem was caused by inconsistent index files after an incomplete shutdown of the QT wallet. While stopping short of saying that doing so is unsupported, we strongly recommend people do NOT attempt to run a masternode or a systemnode on any Windows platform.

5. Artem has not had time to make any progress on the NFT trading design specification documentation. This is a critical requirement for the wider adoption of the NFT framework. A number of developers have considered deploying NFT applications on the Crown framework but told us they have switched to Ethereum instead because of the ability to trade ERC-721 tokens (on the Ethereum blockchain).


6. The community currently needs to fully focus on building NFT use cases aimed at our registration feature only. We believe there might be a lot of space for such use cases in the education, creativity, environment and other mostly non-profit sectors.

7. Community developer Zhen is still working on the Bitcore NFT adaptation. At first the explorer couldn’t download anything. He updated the DNS seeds to make it work again. But then found that after block 2807349 all hashes were wrong because the explorer had followed a fork. He modified the protocol version so the the explorer could get the correct data and it successfully reached block 2817358 (April 3rd). But it stopped downloading later blocks. He found that the next block contains the first NFT transaction. So now he’s implementing NFT features in Bitcore. This problem could have been avoided if he had NFT documentation.


8. Community developer, Sirak, has withdrawn from the Electrum-Crown project. He is too busy to continue with it. pjcltd has enlisted the help of the MUE team to resolve the Electrum issue. The ElectrumX server has heavy CPU requirements (it builds it’s own indexes over the blockchain) which the current VPS struggles to satisfy. The server will be replaced with a higher spec one but this will raise an issue for the infrastructure team regarding provisioning and costs. Meanwhile a MUE engineer is syncing an Electrum server on loaned hardware and is investigating a code problem, possibly caused by NFT transaction incompatibility. If this is the case then it could have been avoided if Sirak had had access to NFT documentation while creating the Electrum-Crown v1.2 release. There may be as yet undiscovered NFT-related issues in the Electrum-Crown wallet code as well.

9. We received an invitation from Portis.io (part of ShapeShift) to be integrated into their non-custodial multi-platform wallet. It wasn’t clear to Crownfan or walkjivefly (who were both contacted) how this would work and requests for additional information have gone unanswered. If there is a community member interested in following up on this, please let us know.

10. There ensued a lengthy discussion about the problems which have followed the NFT framework rollout. A major factor was the lack of project management surrounding it. A small number of dedicated community members pushed through the Emerald release but there was insufficient planning and coordination because we don’t have an actual project/product manager. Combined with the lack of developer documentation this has caused the current Bitcore and Electrum problems. These problems have a detrimental effect on the Crown Platform and increase the costs associated with the projects.

Ultimately the root cause is a lack of funding.

We face the possibility of further problems of this nature with the Bitcoin codebase update. To avoid a repeat performance we need someone to take on a project management role. If there is a community member interested in getting involved in this capacity please get in touch via Discord.

https://medium.com/crownplatform/lets-register-the-most-original-nft-on-the-crown-blockchain-e73581272fd5


Let’s register the most original NFT on the Crown blockchain!
Bounties worth 8500 CRW ($425) waiting for the top 3 winners.

In order to drive visibility and use of the recently released Non-fungible tokens (NFT) Framework which enables public and private participants to tokenise assets on the Crown blockchain, the community has launched a bounty contest with the following details and rules:

Goal: Register the most original NFT on Crown.

NFT Form: Picture, crypto art, video, any ORIGINAL visual or text form.

Requirements:

1.Register your NFT (a simple guide of the steps is below)
2. Share your visual output and NFT txid in Twitter via a Tweet tagging @crownplatform

Voting: The Crown community will vote and select top 3 visuals in the CRW Telegram and Discord channel poll. Votes in both channels will be counted together.

Bounties:
Winning prize: 5k CRW (approx 250 USD)
2nd prize: 2.5k CRW (approx 125 USD)
3rd prize 1k CRW (approx 50 USD)

Contest duration:
* NFTs must be registered and tweeted before 22:00 CEST on Sunday May 10th, 2020.
* Votes must be cast by 22:00 CEST on Sunday May 17th, 2020

For those learning how to use the CRW NFT registration tool, we have put together this short guide. For the competition you need to prepare your content, collect the information needed for the NFT and finally create it.

1. Create your original content.
It’s entirely up to you what you create and how.

2. Digitise it if it’s not already in digital format.
For example, a sketch or painting could be digitised with a scanner or a photo on your mobile phone.

3. Create a sha256 checksum of the digital representation.
Blockchains are not good places to store actual content (a single photo could be several MB, a video hundreds of MB) so we use a sha256 checksum as a short form representation.

Linux users
You can easily create a sha256sum from the command line or perhaps from your file manager. If your content is called /home/alice/art/crown1.tiff you could use the command
sha256sum /home/alice/art/crown1.tiff
to generate the checksum

Mac users
If your content is called /users/bob/crownpic.png you could use the command
shasum -a 256 /users/bob/crownpic.png

Windows users
You may already have a command line or GUI tool installed. If not there are lots of possibilities, some suggestions are here. If your content is called C:\Desktop\photos\competition.mp4 you could use the command
certutil -hashfile C:\Desktop\photos\competition.mp4 SHA256

4. Host the digital representation on any publicly accessible URL.
Use any cloud platform, blog or website you have access to. If you’re using Dropbox, Google Drive, Mega etc., please set the sharing options so that the URL is publicly accessible. Use a URL shortener if you want to pay the smallest possible NFT transaction fee.
Please also ensure the content you upload is the exact one you created the checksum from. It’s a good idea to download the content yourself, calculate the checksum again and compare it with the original value. Some sites, for example imgur.com, alter the content slightly. If the checksum we calculate of the object found at your URL (stored in the metadata field of the NFT) doesn’t match the value in the token id your entry may be invalidated.

5. Prepare to create your NFT.

You will need to provide the following information for your token:

* sha256 checksum as created above. This will be your token id, referred to as <token_id> below.
* Crown address to own the token (any address from your wallet), referred to as <token_address> below.
* URL of the digital representation, referred to as <token_meta> below.

6. Create your competition token
We have created an NFT protocol called nftcomp for competition entries.
You can use the crown-cli tool or the debug console in the GUI wallet to actually register the token using the following steps:
unlock your wallet

{crown-cli} walletpassphrase “your password here” 300
generate a new address if required
{crown-cli} getnewaddress “competition”
register the NFT
{crown-cli} nftoken register nftcomp <token_id> <token_addr> 0 <token_meta>

Successful registration will emit the transaction id you need for your tweet. Registration failure will produce an error message. If the message is
error: {“code”:-32603,”message”:”Signing transaction failed”}

then you forgot to unlock your wallet. If you can’t resolve any other problem please contact us in the #support-wallet channel in Discord.

Don’t forget to tweet your competition entry, for example
@CrownPlatform I just registered #CompetitionEntry #NFT 9bd7bd1b35e66120391959fc7af01aaf3b445703d8660629f310470bd42633a8 representing http://bit.ly/3byUfmm on the $CRW Crown blockchain

You can view competition entries in the dedicated page of the Crown Platform Monitor.
You can view all the other registered protocols and tokens in the monitor too. On the NFTs page you could use the competition protocol name (nftcomp) in the search box or use the “Same protocol” option in the dropdown box on any nftcomp token. Then use the “Txn details” option to see the raw transaction including the metadata which contains the entry URL.

Crown development meeting minutes
Just the facts, ma’am

Present: ashot, crowncoin-knight, pjcltd, walkjivefly

Ashot continues to work on the masternode/systemnode syncing aspects of the codebase update. He pushed one commit last week. The NFT integration looks like being a bigger job than he initially thought. He has updated the FlipsideCrypto chainwalker so that NFT transactions get reported and counted in their metrics. He plans to address the testnet issues once the codebase update is otherwise ready for testing.

Community developer, Zhan, estimates the Bitcore NFT update could be ready in about a month. This will make it easier for Javascript developers, including Chronovault, to build use-cases on the NFT framework.

The Electrum Crown problem has been localised to the Electrumx server which interfaces between the Electrum Crowm wallet and the Crown daemons. We suspect the server doesn’t like or understand our NFT transactions and this stops it from syncing and indexing correctly. This then prevents the wallet from connecting. Community developer, Sirak, is working with Artem to identify and fix the problem. There is no ETA for a fix yet.

It has been suggested that after the Bitcoin codebase update is delivered, we concentrate development on smaller projects which can be completed more quickly and which deliver enhanced usability and functionality to the Crown platform. Examples could be BTCPay server integration, in-wallet proposal creation, Crown Masternode Tool, and on-chain governance (this last one perhaps implemented using NFTs). All present thought this would be a good idea. Some of them are already logged in Gitlab.

If you have any ideas for projects which could be candidates for consideration, please let us know through Discord.

https://medium.com/crownplatform/crown-development-meeting-minutes-06-04-2020-e6a28644c45f


Crown development meeting minutes 06/04/2020
Just the facts, ma’am

Present: artem, ashot, crowncoin-knight, pjcltd, walkjivefly

Testing completed successfully for the NFT registration problem and Artem tagged the patch for release. walkjivefly pushed the release on Saturday. A number of NFT protocols and tokens have now been successfully registered including the first CrownCards.

Artem did not submit a proposal last month nor this and doesn’t expect to have any time for Crown issues beyond emergency hot fixes in the foreseeable future. He is still committed to creating an NFT trading design doc but can’t say when this might happen. He thinks there are two likely ways trading could be implemented. The first would involve a two-party multisig transaction and might be the simplest to implement. The second would involve separate request transactions to advertise an NFT for sale and invite bids, and response transactions. These could be fixed price maker-taker kind of operations or auction style with multiple possible competing bids within a defined limited period of time.

crowncoin-knight asked if someone else could (at least temporarily) takeover continuing development. Artem replied it would be possible for someone with the correct mindset and technical skills. However, doing so without the NFT trading design doc would be difficult and it is unlikely there is anyone in the community with the skills, time and inclination to do so.

Artem will monitor the level of NFT framework adoption as an indicator of how important the community sees the implementation of trading.
There have been a number of reports of sync and “hang” problems since the Emerald release. Most are probably due to forks but some could be related to open testnet issues such as 366, 362, 342 or 341. Artem doesn’t have time to look into them but Ashot said he might be able to. In the meantime we ask anyone having sync/hang problems to provide as much information as possible to help classify and resolve them.

Ashot continues to work on the governance syncing aspects of the codebase update. He estimates the project completion at about 85%. Hopefully this week he will also find time for the FlipsideCrypto chainwalker NFT update, and next week will attempt to merge the NFT framework code into the codebase update. He expects to be ready for testnet soon after that.

Ashot will review the open NFT testnet issues 335 and 333 and decide whether to address them or create a new testnet for the codebase update testing.

The bootstrap instructions have been updated to accommodate NFTs. Testing showed there is no need to change the actual creation process and revealed a potential link to a reduction in bootstrap performance. Issue 367 has been opened. Artem will review the log file.
There has been a report of a potential problem with the Electrum Crown servers. These are not managed by the infrastructure team so defunctec has been asked to contact the community developer to get them upgraded if necessary.