Crown Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - EdwardMorra

Pages: [1]
1
Proposals / Budget / Crown Infra Jan 19 [Active]
« on: January 05, 2019, 04:26:33 pm »
Proposal Basic Information
Project Name: CrownInfraJan19
Authors: @edwardmorra
Proposer’s Email Address:  edwardmorra@crown.tech
Funds requested: 6815.6 CRW for 1 month – 6815.6 CRW total
Proposal Hash:  9ccc24b2fbb3efedd5a1d900205ca44305359b4c4a3b2ff3c664c4ec3dcddac6
How To Vote YES:  mnbudget vote-many 9ccc24b2fbb3efedd5a1d900205ca44305359b4c4a3b2ff3c664c4ec3dcddac6 yes
How To Vote NO:  mnbudget vote-many 9ccc24b2fbb3efedd5a1d900205ca44305359b4c4a3b2ff3c664c4ec3dcddac6 no

You and your team
Manager: Alex @edwardmorra
Helping out: @pjcltd

Proposal Document
The proposal document can be found here https://docs.google.com/document/d/11T7N-9EF9UehwyfNMDWpES69rRiGfF-yY6oN0rAdfTE/edit?usp=sharing

Project Details
Crown Support Team is a dedicated group of Crown Community members that provides general and technical support to the Crown Community.
Project purpose
Crown Support Team fills the need for help that is requested on a regular basis by
Assisting community members
Supporting the Dev Team

Sidenote:
I (edwardmorra) will not request funds this month for my personal time, I feel it best to let it up to the community to donate what they think my work is worth. I choose to do so as the superblock is under quite a load as it is and I think infrastructure cost should come first.
My CRW address is: 19SDFgjumZyrRCtpzPdWeUMMs4oJ9w7D13



The Crown project needs several IT services to run. This includes Gitlab for code development, website hosting so new users can find the project and other bitcoin-fork  specific services.
This proposal is to cover the costs of the old subscriptions that are currently running. Besides that we try to cover as much of the costs community member pjcltd has by making services of his hosting company available.

Ambition/Intention

The ambition of this proposal is to have crown infrastructure costs covered. This proposal’s project is to streamline system administration of the past 4 years into 1 as cost effective operation as possible so any bear market can be survived.

Proposal timetable and turning point(s)

As of right now there are 35+ servers running. Some of these are running at a too high cost.
12th of January is intended to be the moment where as much as possible of the infrastructure is on the hosting environment of pjcltd.
The migration/new setup of the infrastructure is time intensive and comes with hurdles like access details being spread wide.
Next superblock the intent is to not have to exchange CRW into fiat as pjcltd accepts crown as payment.
Acceptance criteria

This proposal can be called a success when migration and cost cutting doesn’t disturb the network infrastructure. For now it is most important the services keep running.

Risks

The migration methods used have so far not impacted the general operation of the Crown Project, once a server is copied it can be tweaked/setup in a sandbox-like environment. This means there is almost no risk involved with the cost-reduction part of this proposal.
The cost coverage part has 1 significant risk: Price decrease.
To try and hold of that risk the requested crown will be turned into FIAT asap. Thereby knowing how much of the cost is covered, so I (edwardmorra) can find other ways to cover the costs. Besides that pjcltd has agreed to help out with the cost see below.

Funding requirements

See attachment for cost breakdown
*pjcltd agreed that the 2600 crown will be used as buffer in case a price decrease happens. Should a price decrease happen the next superblock will have to cover the reduced amount of CRW.
Total CRW: 6815.6
 Costs cut so far.
69 Dollars from digital Ocean
Hetzner cost reduced as nextcloud will soon be migrated.


Communication
Next proposal will contain an update about the cost situation, besides that @edwardmorra can be pinged in discord and will stay in contact with the contributors.

Additional comments
Provide additional comments on your proposal if you have any.
 
Break down of cost here:
https://docs.google.com/document/d/1AVpkzFXn3_-Ciipm2uMrmpLyhxzJQl-eSel1guV8KvM/edit#heading=h.14zhojjy3m4u


EDITS:
This is the first version of the proposal document. If changes are made, they will be indicated.

2
Official Announcements / Read the Crown Meetup report on Medium!
« on: August 15, 2018, 11:49:47 am »
Crown Essen Meetup report is here



We've published an article where you can read up on what happened in Essen.

It can be found HERE
(Medium)



3
Official Announcements / #CROWNESSEN18 Community meetup closing in
« on: July 30, 2018, 05:25:39 pm »
Check out the Crown Community Meetup Agenda for this Saturday
  • Team and Development Updates, Community interventions, new Crown projects, panel discussions and more!

Agenda for the Crown Community Meetup in Essen on August 4th 2018
Save the date! This saturday, the global Crown Communty will be meeting at the BlockchainHotel in Essen. After London, Prague, Toronto, Amsterdam and Miami, this time we are coming together at the former center of the German coal mining industry! This is the agenda for a day - packed with updates, exclusive news, discussions, networking, giveaways, and of course: bringing the Crown Community together!

We sincerely invite everyone to participate in this free event! Be sure to make it on time to register and receive your accreditations. Whether you are that veteran Crown whale with dozens of Masternodes, the newcomer who only heard about crypto last Saturday, a BlockchainHotel visitor or a regular guest of our great venue, the UnperfektHaus in Essen, come along and meet one of the unique crypto-DAOs!

Venue: BlockchainHotel @ UnperfektHaus

Friedrich-Ebert-Straße 18–26, 45127 Essen

24 hour Parking:
Parkhaus am Weberplatz Wolf GmbH
Kreuzeskirchstraße 35, 45127 Essen

Meetup Event: https://www.meetup.com/de-DE/Crown-Platform-Community-Meetup-August-4th-Essen-Germany/events/251710672/

How to get there once you are in Essen: http://www.unperfekthaus.de/anfahrt/

Any questions? Contact support@crown.tech or join us on Telegram at https://t.me/crownplatform

See you on Saturday!


4
Off Topic / 3D printing
« on: June 01, 2018, 06:15:47 pm »
Who here likes 3D printing :D

5
Wallet / Exchange / Wallet setup guide
« on: May 06, 2018, 08:28:47 am »
Step 1
For getting started with Crown we need the wallet
You can download it from the following link:
https://crown.tech/wallet/

For windows, upack the downloaded file.


After unpacking these files to the place you want to have the program of the wallet, open the folder just extracted.
Here you see 2 folders, open the BIN folder.


Here you see a number of files. We are going to start crown-qt.exe (you can make a shortcut to the desktop of it as well).


At the first start you will be asked to choose a data location. The Crown wallet along with all files is is stored here.


Choose a location, or use the location that the application offers and click OK.
Your Crown wallet will now be started.


As soon as the wallet has been started, we will first secure it.
You do this by clicking “settings” at the top of your screen and selecting “Encrypt wallet”.


There will now be a popup where you have to enter a self-chosen password twice. Do not forget this password!


After setting a password, press “OK”. You will see a warning.


Click “Yes” and then “OK” to continue
Disclaimer: IF the program stops responding it’s doing the heavy calculations of encrypting the wallet… Force closing it corrupts your wallet.dat.


The wallet will now close and you will have to restart it yourself.

Step 2
Now we are going to make a backup of the wallet file, this is important if you want to move the wallet to another computer or if the file unexpectedly gets damaged, so make sure you keep it well because this is the access to your Crown! Click on “File” and then “Backup Wallet” at the top of the Crown wallet.


Once again there will be a new popup screen, here you have to select the location to store the Crown wallet file. Enter a filename and click on “save”.



Be sure to backup your wallet every time you used it for a transaction.

6
Proposals / Budget / [Archive] Crown Support Team - May
« on: April 02, 2018, 10:13:17 am »
    Proposal Basic Information
    Project Name: Support_Team
    Authors: @edwardmorra, @crownfan
    Proposer’s Email Address:  support@crown.tech
    Funds requested: 3500 CRW for one month - 3500 CRW total
    Proposal Hash:  1d852f7f7009396364ad6295dcdf05c37d3eb2845b63c197140d515f58d1a574
    How To Vote YES:  mnbudget vote-many 1d852f7f7009396364ad6295dcdf05c37d3eb2845b63c197140d515f58d1a574 yes
    How To Vote NO:  mnbudget vote-many 1d852f7f7009396364ad6295dcdf05c37d3eb2845b63c197140d515f58d1a574 no

    You and your team
    Role: @crownfan current co-lead
    Role: @edwardmorra - current co-lead
    Role: @hypermist
    Role: @higherbridge
    Role: @crown_translator
    Role: @lezlaig
    Role: @andlug51062

    Proposal Document
    The proposal document can be found here https://crown.link/support

    Project Details
    Crown Support Team is a dedicated group of Crown Community members that provides general and technical support to the Crown Community.
    Project purpose
    Crown Support Team fills the need for help that is generated by the constant growth of the crown ecosystem by
    • Assisting community members
    • Supporting the Dev Team

    Ambition/Intention
    The Crown Support Team obligates itself to deliver the best possible service and to be steadily available to provide flexible and reliable support to both the Crown Community and the Crown Core Team.
    During the coming period the intent is to increase the number of support team members. This is a priority due to the exponential growth of the workload that goes parallel with the growth of the Crown network and community.
    Crown Support has two major fronts:
    While it commits to provide steady support and help, it permanently grows its knowledge base and expands the variety of tools at disposal. Support Team plays a key factor in the propagation and sharing of knowledge. It helps the community to learn how to use the Crown ecosystem.



    Proposal timetable and turning point(s)
    This funding round will reward the Crown Support Team until the May CDGP proposal round.
    The team re-evaluates the requested funds every month to adapt the proposal to future workloads and capacities.

    Acceptance criteria
    The proposal can be called a success if the support team manages to provide help and support to the Dev Team and Community until the end of this funding round.
    Our aim is to continue to establish a sustainable support team with a growing knowledge and experience while future support agents are trained to decentralize the available resources.

    Risks
    Crown Support Team is a resilient and decentralized network of peers with high resistance to individual impediments.

    Funding requirements
    The decision to request 3500 crown has been made because there is a big need to incentivize further engagement in the currently overloaded support team structure and capabilities. It is a fair reward for the availability, flexibility and competences that are provided. We plan to double the capabilities until the end of April.


    The requested funds will be destined to incentivize participation through the bounty programme, reward the support team members for their work and to fund support infrastructure and software.

    Communication
    The Crown Support Team is due to the way it is set to operate in frequent contact with the team and community. It provides monthly statistics about the quantifiable progress through Crown’s communication channels.

    Additional comments
    Crown Support Team provides help and support through the following channels:


    - Mattermost: https://mm.crownlab.eu
    - Zendesk: https://crown-support.zendesk.com (upgraded with new features in January)
    - Crown Forum: https://forum.crown.tech
    - Reddit https://www.reddit.com/r/Crown/
    - Telegram https://t.me/crownplatform ( ticket system implemented in January) [/list]

    7
    Mandatory Update Release Notification



    The Crown team has released a new version of the client (v0.12.4.1) today 13th March.
     
    Full release notes and more on our medium post: https://medium.com/crownplatform/crown-mandatory-update-release-notification-v12-4-1-2b76d11fe4b2

    The network will have 20 days to update before enforcement is turned back on and old clients stop communicating correctly.

    Update instructions:

    **IMPORTANT: Always back up your wallet.dat before proceeding with any updates.**


    For more information visit our

    - New Forum Guide to Update Master- and Systemnodes to 12.4.1: https://forum.crown.tech/index.php?topic=1242.0

    - New Forum Guide to Setup Systemnodes: https://forum.crown.tech/index.php?topic=1240.0

    - New Forum Guide to Setup Masternodes: https://forum.crown.tech/index.php?topic=1241.0

    - Mattermost Community to chat and receive Support: https://mm.crownlab.eu/crown/channels/tech-support

    - Website to download the newest wallet: https://crown.tech/wallet

    You can also open a support ticket by sending an e-mail to support@crown.tech
     
    Thank you for your continued support of the Crown project

    Crown Development Team

    8
    Help, Guides and Support / [LEGACY] Updating Nodes to v0.12.4.1
    « on: March 12, 2018, 12:54:28 pm »
    Crown Master/Systemnode Update Guide

    Firstly, make sure your local wallet is on the latest version (find it at https://crown.tech/wallet).

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

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

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

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

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

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

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

    If you have any trouble following the above guide, please email support@crown.tech

    9
      Table of Contents
      • Encrypt your wallet
      • Backup your wallet
      • Set-up a VPS
      • Start Masternode setup
      • Login to your VPS
      • Install your Masternode on the vps
      • Check if the installation went correctly
      • Backup Masternode.conf and wallet
      • Start your node(s)
      • Additional notes


      Step 1
      Click settings, encrypt wallet

      Enter a new password and save a copy somewhere safe.


      IMPORTANT: interrupting the encryption process corrupts the wallet.dat (so if the wallet stops responding let it continue!)

      Step 2
      In the wallet, click file -> backup wallet

      Save your wallet.dat carefully (recommended is on 2-3 separate hard drives and not on cloud storage. Please do your own research on good practices regarding wallet safety).

      Step 3
      Get yourself a Linux Ubuntu 16.04 VPS. Take note of the password and IPV4 address that comes with the VPS this is needed for the next step.
      Note: the VPS should have at least 1GB of RAM (or 512MB + 512MB vswap) and around 10GB of storage.

      Step 4
      To start the Masternode setup you can go to the Masternodes tab and go to my Masternodes and press New Node:


      Here, do the following:
      • Enter the name(alias) of the node
      • Enter the IP address of the vps you created
      • And if you wish to name the transaction to yourself a label
      Continue to step 5

      OR

      When you send 10000 crw to yourself (from an exchange for example) you will be greeted with the following message as the transaction comes in (with masternode instead of systemnode).


      Click “yes” in the following screen:


      • Enter the name(alias) of the node
      • Enter the IP address of the vps you created

      Continue to step 5
         
      Step 5
      [/list]On a Windows machine, you now need to download PuTTy and install it.


      On a Mac or Linux machine, open the Terminal.

      Enter the IP address of the VPS you created and login to the server using root as the user and the password
      supplied by your VPS provider.


      Step 6
      Once you're logged into your VPS as root, follow the next steps:
      First we need to get your Masternode’s key from the wallet click on the copy to clipboard button:

      To manually generate the genkey, type: node genkey

      Then on the VPS to simplify the process, we’re going to use a script.

      First, replace PLACE-YOUR-MASTERNODE-KEY-HERE with your Masternodenode genkey you just copied to clipboard:
      [/list]
      Code: [Select]
      sudo apt-get install curl -y && curl -s https://raw.githubusercontent.com/Crowndev/crowncoin/master/scripts/crown-server-install.sh | bash -s -- -m -p PLACE-YOUR-MASTERNODE-GENKEY-HERE
      Copy and paste the above line with your genkey in your VPS (putty requires a right click to paste) and hit the enter key.

      Step 7
      Check the status of the node by typing: crown-cli getinfo on the vps.
      Now wait for the blockchain to sync fully. In the meantime you can continue with step 8.

      Step 8
      Back up your wallet.dat just like you did in step 2

      and then back up your masternode.conf
      On Windows:
      Go to AppData/Roaming/Crown (where the wallet.dat is stored - this may be a hidden folder). Copy masternode.conf to the places where you backed up your wallet.
      ------------------------------------------------------------------
      On macOS:
      Open a finder window, press cmd + shift + G and navigate to ~/Library/Application Support/Crown, where you will find masternode.conf
      ------------------------------------------------------------------
      On Linux:
      You can find masternode.conf in ~/.crown and copy to a backup place

      Step 9
      Once the blockchain has fully synchronised on your VPS, run your local CrownQT wallet.

      Goto the Masternode tab and select the Masternode that just fully synchronised and click Start Alias on the bottom:


      After entering your password you will get the request to start it:


      After clicking Yes you should get the following message and be done:


      PLEASE NOTE

      It can take several days for your Masternode to receive its first payment.
      The minimum waiting time (in days) for your first Masternode payment is approximately Amount of Masternodes / 1440
      Maximum time before first payment is the above * 2

      Usually as long as the Masternode says enabled in your Masternode tab, and the active section shows anything above 00:00, you should be good to go.

      It may take up to half an hour for your Masternode's uptime to change from 00:00 to the actual time. Please be patient.

      How to check if you installed your Masternode correctly
      Enter crown-cli masternode status into your VPS command line.

      If it outputs this is not a Masternode, something may have gone wrong in the process.

      If it says not capable Masternode: Hot node, waiting for remote activation, you should activate the node from your local wallet as decribed in step 9.

      If the command outputs that the Masternode is enabled but not yet activated, wait for the VPS wallet to sync with the network. This may take a few minutes. It may be that your wallet is not synced up to the current block. Enter crown-cli getinfo, look at the block your wallet is at and compare that to the current block on http://crown.today

      10
        Table of Contents
        • Encrypt your wallet
        • Backup your wallet
        • Set-up a VPS
        • Start Systemnode setup
        • Login to your VPS
        • Install your Systemnode on the vps
        • Check if the installation went correctly
        • Backup Systemnode.conf and wallet
        • Start your node(s)
        • Additional notes


        Step 1
        Click settings, encrypt wallet

        Enter a new password and save a copy somewhere safe.



        IMPORTANT: interrupting the encryption process corrupts the wallet.dat (so if the wallet stops responding let it continue!)

        Step 2
        In the wallet, click file -> backup wallet

        Save your wallet.dat carefully (recommended is on 2-3 separate hard drives and not on cloud storage. Please do your own research on good practices regarding wallet safety).

        Step 3
        Get yourself a Linux Ubuntu 16.04 VPS. Take note of the password and IPV4 address that comes with the VPS this is needed for the next step.
        Note: the VPS should have at least 1GB of RAM (or 512MB + 512MB vswap) and around 10GB of storage.

        Step 4
        To start the Systemnode setup you can go to the Systemnodes tab and go to my Systemnodes and press New Node:


        Here, do the following:
        • Enter the name(alias) of the node
        • Enter the IP address of the vps you created
        • And if you wish to name the transaction to yourself a label

        Continue to step 5

        OR
        When you send 500 crw to yourself (using a 0 fee transaction for example) you will be greeted with the following message as the transaction comes in.


        Click “yes” in the following screen:


        • Enter the name(alias) of the node
        • Enter the IP address of the vps you created
        Continue to step 5
           
        Step 5
        [/list]On a Windows machine, you now need to download PuTTy and install it.


        On a Mac or Linux machine, open the Terminal.

        Enter the IP address of the VPS you created and login to the server using root as the user and the password
        supplied by your VPS provider.

        Step 6
        Once you're logged into your VPS as root, follow the next steps:
        First we need to get your Systemnode’s key from the wallet click on the copy to clipboard button:


        Then on the VPS to simplify the process, we’re going to use a script.

        First, replace PLACE-YOUR-SYSTEMNODE-KEY-HERE with your Systemnode genkey you just copied to clipboard:
        [/list]
        Code: [Select]
        sudo apt-get install curl -y && curl -s https://raw.githubusercontent.com/Crowndev/crowncoin/master/scripts/crown-server-install.sh | bash -s -- -s -p PLACE-YOUR-SYSTEMNODE-GENKEY-HERE
        Copy and paste the above line with your genkey in your VPS (putty requires a right click to paste) and hit the enter key.

        Step 7
        Check the status of the node by typing: crown-cli getinfo on the vps.
        Now wait for the blockchain to sync fully. In the meantime you can continue with step 8.

        Step 8
        Back up your wallet.dat just like you did in step 2

        and then back up your systemnode.conf
        On Windows:
        Go to AppData/Roaming/Crown (where the wallet.dat is stored - this may be a hidden folder). Copy systemnode.conf to the places where you backed up your wallet.
        ------------------------------------------------------------------
        On macOS:
        Open a finder window, press cmd + shift + G and navigate to ~/Library/Application Support/Crown, where you will find systemnode.conf
        ------------------------------------------------------------------
        On Linux:
        You can find systemnode.conf in ~/.crown and copy to a backup place

        Step 9
        Once the blockchain has fully synchronised on your VPS, run your local CrownQT wallet.

        Go to the Systemnode tab and select the Systemnode that just fully synchronised and click Start Alias on the bottom:


        After entering your password you will get the request to start it:


        After clicking Yes you should get the following message and be done:


        PLEASE NOTE

        It can take several days for your Systemnode to receive its first payment.
        The minimum waiting time (in days) for your first Systemnode payment is approximately Amount of Systemnodes / 1440
        Maximum time before first payment is the above * 2

        Usually as long as the Systemnode says enabled in your Systemnode tab, and the active section shows anything above 00:00, you should be good to go.

        It may take up to half an hour for your Systemnode's uptime to change from 00:00 to the actual time. Please be patient.

        How to check if you installed your Systemnode correctly
        Enter crown-cli systemnode status into your VPS command line.

        If it outputs this is not a Systemnode, something may have gone wrong in the process.

        If it says not capable Systemnode: Hot node, waiting for remote activation, you should activate the node from your local wallet as decribed in step 9.

        If the command outputs that the Systemnode is enabled but not yet activated, wait for the VPS wallet to sync with the network. This may take a few minutes. It may be that your wallet is not synced up to the current block. Enter crown-cli getinfo, look at the block your wallet is at and compare that to the current block on http://crown.today

        11
        Proposals / Budget / [Funded] Crown Support Team
        « on: January 05, 2018, 01:49:02 pm »
        Proposal Basic Information
        Project Name: Crown_Support_Team
        Authors: @edwardmorra, @crownfan
        Proposer’s Email Address:  crownfan
        Funds requested: 1600 CRW/month for 3 months - 4800 CRW total
        Proposal Hash:  e9cb17c2726d561570a6fa5c098f527d635ac876d32cd2bb0a34da6590d8018f
        How To Vote YES:  mnbudget vote-many e9cb17c2726d561570a6fa5c098f527d635ac876d32cd2bb0a34da6590d8018f yes
        How To Vote NO:  mnbudget vote-many e9cb17c2726d561570a6fa5c098f527d635ac876d32cd2bb0a34da6590d8018f no

        You and your team
        Manager: José @crownfan
        Role: Alexander @edwardmorra - co-lead
        Role: Jacob @hypermist - second level / service operation

        Proposal Document
        The proposal document can be found here https://docs.google.com/document/d/11T7N-9EF9UehwyfNMDWpES69rRiGfF-yY6oN0rAdfTE/edit?usp=sharing

        Project Details
        Crown Support Team is a dedicated group of Crown Community members that provides general and technical support to the Crown Community.
        Project purpose
        Crown Support Team fills the need for help that is requested on a regular basis by
        Assisting community members
        Supporting the Dev Team


        Ambition/Intention
        The Crown Support Team obligates itself to deliver the best possible service and to be steadily available to provide flexible and reliable support to both the Crown Community and the Crown Core Team.


        Proposal timetable and turning point(s)
        This funding round will cover our expenses until April. Crown Support has two major fronts: While we commit to provide steady support and help, we also grow our knowledge base and expand the variety of tools at our disposal.
        We will re-evaluate the requested funds after three months to adapt the proposal to future workloads and capacities.


        Acceptance criteria
        We can call our proposal a success if we manage to provide help and support to the Team and Community until the end of this funding round. Our aim is to establish a sustainable support team with a growing knowledge and experience while we train future support agents to decentralize the available human resources. 

        Risks
        Major illness or impediments of the support staff.

        Funding requirements
        We decided on 1600 crown per month because we believe it is a fair remuneration for the availability, flexibility and competences we provide.
        The requested funds of will mainly be destined to remunerate the support team members for their work. Part of the funds will be used to implement new support software.

        Communication
        The Crown Support Team is due to the way it is set to operate in frequent contact with the team and community. We will provide monthly statistics about the quantifiable progress through Crown’s communication channels.

        Additional comments
        Crown Support Team provides help and support through the following channels:


        - Mattermost: https://mm.crownlab.eu
        - Zendesk: https://crown-support.zendesk.com (upgrade with new features in January)
        - Crown Forum: https://forum.crown.tech
        - Reddit https://www.reddit.com/r/Crown/
        - Telegram https://t.me/crownplatform ( ticket system implementation in January)


        EDITS:
        This is the first version of the proposal document. If changes are made, they will be indicated.

        12
        Official Announcements / [OLD] Notice for Master/System node owners
        « on: December 28, 2017, 12:10:37 am »
        OUTDATED
        NOTE: this post is outdated and this advice is no longer the current advice. Follow instructions at own discretion.


        Dear System/Master node owner.
        If you control your own node (Which comes down to that you are not hosting on Node-vps), we need you to stop your node until we tell you to start it again, we are trying to get the block up to right track.
        Follow the following steps and wait for our signal to start your node once again…
        Start with step 1 in your vps console:
        Code: [Select]
        crown-cli stopStep 2:
        Code: [Select]
        cd .crownStep 3: remove the mncache.dat, mnpayments.dat, peers.dat, sncache.dat, snpayments.dat, budget.dat by the following command:
        Code: [Select]
        rm mn* peer* sn* bud*
        Now please leave your node off untill further notice

        13
        Official Announcements / Update regarding the Chain state
        « on: December 27, 2017, 10:14:45 pm »
        Official Announcement

        Situation:
        Crown has experienced an unplanned hardfork December 26th, due to a lack of consensus between the network.
        At that point in time, different mining pools had different beliefs about the chain-state and mined (forked into) according to their beliefs.
        The issue is still under investigation, and we are working together with mining pools and Bittrex on a solution.

        Action:
        As things are sorted out, it is a possibility that a rollback will happen, and therefore it is best if all activity on the network is halted, until further notice on Bitcointalk/mattermost/Telegram.
        Crown Trading on Bittrex is halted, and we would like to ask everyone to please not set up new nodes, send or mine Crown during this period!

        Stance on the issue:

        We're aware that longest chain with the most work usually wins. In this case we feel that no one user wanted to fork the network, and the fork was totally unplanned. We think that if everyone agrees, we should revert back to the chain before the fork happened.

        Thank you for your patience

        Pages: [1]