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.


Messages - EdwardMorra

Pages: 1 2 [3]
31
    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

    32
      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

      33
      Feedback / Re: Introductions
      « on: January 11, 2018, 07:21:24 am »
      Well I have exams next week, after that I'll think about it

      34
      Feedback / Re: Introductions
      « on: January 10, 2018, 02:16:51 pm »
      We should have an introductions segment of the forum for new members

      do you mean a "welcome, this is how the forum works" segment, or a segment where members can introduce themselves?
      The one where people can introduce themselves is active

      35
      Systemnodes / Re: 4 days without a dividend -- normal?
      « on: January 08, 2018, 08:55:44 am »
      Well it seems like you haven't given a Start command that has reset them in the queue, check on your VPS with
      Code: [Select]
      crown-cli systemnode status to see if they are successfully started.

      If they are succesfully started then it's a glitch in the system if not then we can go from there...

      36
      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.

      37
      Wallet / Exchange / Re: error: {"code":-28,"message":"Loading wallet..."}
      « on: January 02, 2018, 10:35:44 am »
      Is it up to speed now?

      38
      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

      39
      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

      40
      Ideas / Re: [Idea] Proposal fee refund / static fiat amount for a proposal
      « on: December 20, 2017, 06:49:42 am »
      Maybe changing the fee every super block?

      Pages: 1 2 [3]