Raphael Scheidler

Core Team
  • Content Count

    18
  • Joined

  • Last visited

  • Days Won

    6

Raphael Scheidler last won the day on November 13

Raphael Scheidler had the most liked content!

Community Reputation

15 Good

4 Followers

About Raphael Scheidler

  • Birthday 01/23/1996

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Raphael Scheidler

    Some critical Questions

    So we may provide a higher level of value to the ALQO community and to streamline the access of critical and relevant information regarding ALQO and Bitfineon and its accompanying planets, all team members will request that new questions/inquiries be posted to the ALQO Community HUB. Answers will be provided on the community hub and similar questions asked by community members will be linked accordingly. Additional questions can be asked on the relevant thread and team members will provide replies to the thread. This will help us maximum team efficiency and serve the community in the best possible way, and to position ourselves to better serve new members and to scale effectively with any sudden explosive growth we may experience.
  2. Raphael Scheidler

    Some critical Questions

    No more than a couple of weeks, we plan to move forward at a quick pace, once the closed beta is out. There‘ll be a public beta, after the closed beta for ALQO holders. From there, we‘ll be moving to full public release within a few weeks, no exact timeframes set yet though, but we‘re on schedule for release this year. Yes, of course! Exact trading fees have yet to be determined. Yes, Liberio should be coming out soon for all major smartphone OS. Bitfineons website will be responsive, so it‘ll look great on mobile devices. App is planned but not top priority, should be coming out at some point in 2019. Yes, credit card deposits will be available. Cool idea! I think we‘ll introduce something like that, this hub can also be used as the go-to platform for Bitfineon related discussions, including trading ideas, market discussions etc. Thank you for your questions!
  3. Raphael Scheidler

    VLOG of the ALQO Bitfineon anniversary gala

    Thanks for sharing, great vlog, as authentic as it gets! It has been an exciting time and I I think I can speak for the whole team to say we had an incredible evening, great talks with the community and it’s been a pleasure to celebrate with everyone who shares the enthusiasm for ALQO and Bitfineon, like we do. Looking forward to the next years to come!
  4. Raphael Scheidler

    Bitfineon Beta Demo Trading Contest

    Great idea, I‘m sure we can work on something in anticipation of the Bitfineon launch and ALQOs key role in the ecosystem!
  5. Raphael Scheidler

    Questions regarding the roadmap

    The answers will be provided as soon as possible, don’t worry. It’s just a very busy week for the team, due to the Bitfineon Beta preparations. Once that is accomplished, we‘ll answer in detail, it just takes time, which is a rare good right now.
  6. The team at Bitfineon GmbH is pleased to announce a special gala evening in Heidelberg, Germany on November 3rd 2018, to commemorate the one-year anniversary of the creation and launch of ALQO. Hosted at the enchanting and acclaimed Alte Weinfabrik venue, in the heart of Heidelberg's historic district, and featuring Michelin Star awarded chefs Martin Scharff & Mario Sauer, the evening will focus on celebrating ALQO's first year and the upcoming launch of the Bitfineon exchange. We'd like you to join with us in celebrating the ongoing journey of ALQO & Bitfineon with this special evening. Tickets can be purchased in advance and capacity is capped at 150 due to venue size. This is an exclusive event and local German media will be attending and reporting on the event. Come and join us in celebrating ALQO and Bitfineon, we hope to see you all there! Find all the details and get your tickets here: Special ALQO Gala Website (pre-order starts 6pm UTC+2, 2nd October)
  7. Raphael Scheidler

    Bitfineon Exchange Development

    Anyway, here’s a first sneak peak of the Dashboard view:
  8. Raphael Scheidler

    OpenAlias easy remembrance of addresses in ALQO

    You already have chosen your Liberio thumbID when you registered. So it’s already available, just not all functionalities that come with it. For more information about thumbID, head over to the official ALQO homepage and check out the Liberio section!
  9. Raphael Scheidler

    Masternode - VPS Setup Guide

    Cronjob to restart your server daemon Thanks to smasherx for providing these steps. We'll create a shell script that restarts the masternode if not running and logs the result in the logfile /var/log/alqod_log.txt Creating the shell script Create the empty file mn-check-run.sh in /root/ALQO/: nano /root/ALQO/mn-check-run.sh Insert following code: #!/bin/sh # Check for ALQO MN running and restart if not case "$(pidof alqod | wc -w)" in 0) echo "Restarting alqod: $(date --utc)" >> /var/log/alqod_log.txt /root/ALQO/alqod & ;; 1) # all ok echo "$(date --utc) alqod already running" >> /var/log/alqod_log.txt ;; *) echo "Attention - multiple instances of ALQO daemon running $(date --utc)" >> /var/log/alqod_log.txt ;; esac Save it and exit. Now make it executable: chmod 777 /root/ALQO/mn-check-run.sh Creating the cronjob Create a cronjob which runs the newly created shell script every 10 Minutes: sudo crontab –e Insert the following line, save it afterwards and exit: */10 * * * * /root/ALQO/mn-check-run.sh And that’s it; now you have a script that checks the state of the alqod every 10 minutes and restarts it if its not running anymore – You can delete the logging of the “running daemon” in the script, once I have confirmed that everything is correct. That’s just for the start. In the end, I have only the logs of the restarts and the highly unlikely case that more than one daemon is running.
  10. Raphael Scheidler

    cronjob

    This seems like an ad to me, that is not really welcomed here, since it’s not an answer to his specific question.
  11. Raphael Scheidler

    cronjob

    1. Shell script that restarts the masternode if not running and logs the result in the logfile /var/log/alqod_log.txt Create the empty file mn-check-run.sh in /root/ALQO/ Insert following code: #!/bin/sh # Check for ALQO MN running and restart if not case "$(pidof alqod | wc -w)" in 0) echo "Restarting alqod: $(date --utc)" >> /var/log/alqod_log.txt /root/ALQO/alqod & ;; 1) # all ok echo "$(date --utc) alqod already running" >> /var/log/alqod_log.txt ;; *) echo "Attention - multiple instances of ALQO daemon running $(date --utc)" >> /var/log/alqod_log.txt ;; esac 2. Make it executable. Type in the command line in the VPS: chmod 777 /root/ALQO/mn-check-run.sh 3. Create a cronjob which runs the newly created shell script every 10 Minutes Type in the command line on the VPS: crontab –e Select the editor of your choice Insert following line in the file and save it afterwards */10 * * * * /root/ALQO/mn-check-run.sh And that’s it now you have a script that checks every 10 minutes the state of the alqod and restarts it if its not running anymore – I delete the logging of the “running daemon” in the script once I have confirmed that everything is correct. That’s just for the start. In the end I have only the logs of the restarts and the highly unlikely case that more than one daemon is running. made by our awesome smasher! I‘ll create a guide out of this soon. EDIT: Available here now (better layout): https://hub.alqo.app/topic/16-masternode-vps-setup-guide/?do=findComment&comment=76
  12. Raphael Scheidler

    Bitfineon Exchange Development

    Well, because we think a Beta is the best way to share the progress. You‘ll be able to see it for yourself very soon! I‘m sure the wait is worth it
  13. Raphael Scheidler

    Masternode - VPS Setup Guide

    Masternode - VPS Setup Guide This guide will help you to setup a masternode on an Ubuntu 16.04 64bit Server. Basic Requirements The following items will be required to setup an ALQO masternode: A Virtual Private Server (VPS) running Ubuntu 16.04 (this is key; many will default to 18.04 now and the software is intended for 16.04) There are many reputable providers that these can be purchased from: Vultr, Hetzner, and Time4VPS are some that members of the community use successfully. If you want to support the team: https://billing.time4vps.eu/?affid=2255 (Official ALQO Ref-Link) It may be possible to use the lowest cost VPS to host your masternode as we will be going through a process that creates what can be best explained as virtual ram. However, if possible 1GB of RAM is a good beginning with most providers Control Wallet: A copy of the most up-to-date ALQO QT wallet for your personal computer, you will use to store your masternode funds and control it. As of writing, that is Atlas version 4.1, it can be downloaded from the ALQO website or ALQO Github: ALQO Website URL: https://alqo.app ALQO Github URL: https://github.com/ALQOCRYPTO/ALQO/releases 10,000.1 ALQO in your Control Wallet A program to login to your VPS For Windows, most use putty : https://www.putty.org/ You will type: root@yourip into the Host Name box If you are a first-time putty user right click is how you paste For Mac OS you can use the Terminal: Terminal is an application in your utilities folder on your Mac In your terminal window you will type: ssh root@yourip Please keep in mind that for security reasons you’re gonna need a single IP for each masternode you’re planning to run. Getting the Ubuntu Server ready Updating your Server and Installing Dependencies After logging into your VPS, we will input a series of commands. This guide will assume you are using the root user. Some of these will update existing repositories, and others will install fresh ones. This list is deliberately large to ensure that regardless of what your VPS provider has when you begin that you should have everything you need to run an ALQO node. apt-get update apt-get install -y git automake build-essential libtool autotools-dev autoconf pkg-config libssl-dev libboost-all-dev software-properties-common nano add-apt-repository ppa:bitcoin/bitcoin apt-get update && apt-get install -y libdb4.8-dev libdb4.8++-dev libminiupnpc-dev libevent-dev Adding a SWAP file (do the commands line by line, each followed by hitting return) fallocate -l 3G /swapfile chmod 600 /swapfile mkswap /swapfile swapon /swapfile echo -e "/swapfile none swap sw 0 0 \n" >> /etc/fstab echo "vm.swappiness=10" | sudo tee -a /etc/sysctl.conf sysctl -p Compiling the Daemon Now it’s time to decide. Do you want to compile the daemon on your own, or do you want to download a precompiled daemon which will save some time? We are going to talk about both. OPTION ONE - Precompiled files (recommended for most users) If you don’t want to compile the source by yourself, this is where you’ll go. mkdir ALQO cd ALQO wget https://builds.alqo.org/linux/alqod &&chmod -f 777 alqod wget https://builds.alqo.org/linux/alqo-cli &&chmod -f 777 alqo-cli You can skip the following step (OPTION TWO - Compiling on your own) OPTION TWO - Compiling on your own git clone https://github.com/ALQOCRYPTO/ALQO cd ALQO ./autogen.sh ./configure make Running the Daemon the first time Running the Daemon the first time will help us to create the basic folder structure and to check for errors. IMPORTANT: The path is different for the ones who compiled on there own and the ones who downloaded the precompiled files! From any directory on your VPS you can enter: /root/ALQO/alqod -daemon & (For the ones who downloaded the precompiled daemon) OR /root/ALQO/src/alqod -daemon & (For the ones who compiled on their own server) Within the ALQO directory you can use the following command: ./alqod -daemon & Editing the configs Once you’ve run the Daemon for the first time - it will show you to setup a rpcuser and rpcpassword and close right after it - it has also created the folder structure where the blockchain and all config files are going to be. We need to modify the alqo.conf file on our VPS to link our VPS wallet to our main wallet holding our collateral. We are using the program nano we installed during our dependencies process to modify this file. To open it input the following command: nano /root/.alqo/alqo.conf What goes inside the config? Your configuration files gets read by the ALQO-Daemon on startup. This is just a basic configuration for a simple masternode setup: rpcuser={Input a random string of characters you don't need to remember them} rpcpassword={Input a random string of characters you don't need to remember them} rpcallowip=127.0.0.1 listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=256 masternode=1 externalip={Your servers IP address} bind={Your servers IP address} masternodeaddr={Your servers IP address} masternodeprivkey={Here is where we copy the output from when we input masternode genkey in our control wallets debug console; you'll get it at a later step} Make sure to replace all the entries surrounded by these brackets: { } Replace them without the brackets, e.g.: externalip=123.456.789 Once this has been copy and pasted into your alqo.conf, you will save it by pressing CTRL + X. Main Wallet Setup In order to get the masternode to run, we need to send 10,000 ALQO to an address we are just going to create. We use a system called “Cold-Wallet”. This system is meant for better security because actually your masternode won’t have any access to your wallet. Masternode Priv-Key As you might’ve saw we need a “masternodeprivkey” - this key indicates a private key that is used by your wallet and the masternode. In your Wallet-App go to: Tools -> Debug Console and type in: masternode genkey This will generate a private key - We need to add that key to the “masternodeprivkey”-field in the alqo.conf on the VPS. Generate a wallet-address Each masternode needs it’s own address. We are going to send 10,000 ALQO to this address later. getaccountaddress MASTERNODE_01 You can change MASTERNODE_01 to whatever you want to name your masternode. Save the address you’ve just generated for the next step. Sending 10,000 ALQO to the address Let’s send exactly 10,000 ALQO to that address. Yes - make sure this is only 10,000 ALQO. No less, no more.) Wait for the transaction to have at least 15 confirmations before continuing. Getting the transaction For our local masternode-config we need to get the transaction id and following number. Open up the wallet debug console once again and enter: masternode outputs It will display a list of valid masternode transactions. If this is your first masternode there will be only one for sure. The list contains a longer number (transaction ID) and a following number. Save both of these somewhere for the next step. Local config masternode.conf Open your local masternode.conf (Find it or use the “Edit config file” in the ALQO-QT client under “Tools”) and fill it out like this: {YOURMASTERNODENAME} {YOURVPSIP:55500} {The private key we generated in the debug and saved to in our VPS alqo.conf} {The output from when we entered masternode outputs in the main wallet debug} {The check digit that follows this; either a 1 or a 0} Which should result in something like that: MASTERNODE_01 123.456.7890:55500 7123456789abshdhdhfkfcdefgh 9876asjdbdfhdhjma54321dcba 0 Save and close the masternode.conf, then restart the wallet. Starting everything up After editing all the files locally, we need to get back to our Ubuntu Server and enter the “masternodeprivkey” and start the daemon again afterwards. As mentioned earlier when we’ve created the privkey, we need to add that to the alqo.conf on our server. Get back to that step if you are not sure how to open the config. Making sure the daemon is not running anymore, to include the new alqo.conf killall alqod Starting the daemon on the Ubuntu server After adding the “masternodeprivkey” in we want to start the daemon and allow it to sync. /root/ALQO/alqod (For the ones who downloaded the precompiled daemon) OR /root/ALQO/src/alqod (For the ones who compiled on their own server) The daemon should start minimzed. You’ll only see a message like this: ALQO server starting Once this is started the only thing left to do on our VPS is let the wallet sync. This can take anywhere from a few minutes to a few hours in rare circumstances. Once it is synced nothing additional has to be done on the VPS. You can check the current blocks by typing in: /root/ALQO/alqo-cli getinfo (For the ones who downloaded the precompiled daemon) OR /root/ALQO/src/alqo-cli getinfo (For the ones who compiled on their own server) Remote-Start the masternode We are now at the final step of our process. Restart your wallet after editing the masternode.conf. If you don't have the masternode tab appearing in your wallet go to: settings > options in your wallet. Switch over to the tab in settings that says wallet. In here, click the radio button next to “Show Masternode Tab”. In our masternode tab we should now see an entry with the name and other information we gave it. It will be showing as missing under status. To start our masternode and finalize our process all we have to do is press the "start missing" button (or highlight the node and press "start alias"). After this, it should say enabled and still have a 00:00 under time. This shouldn't alarm you, as it can take a few hours for this to reflect. If we want to confirm we were successful, the best way is back on our VPS. There, enter the following command: /root/ALQO/alqo-cli masternode status (For the ones who downloaded the precompiled daemon) OR /root/ALQO/src/alqo-cli masternode status (For the ones who compiled on their own server) If that output says “Masternode Successfully Started”, then you've successfully set up your ALQO masternode! At this point you can close your main wallet as it does not need to be running using the cold wallet system. The only other step left is to keep an eye on it to ensure it stays running and to keep an eye on the ALQO Discord or ALQO Community Hub for any news or updates! Congratulations! You’ve successfully setup a masternode on your own.
  14. Raphael Scheidler

    Nice new Alqo world

    Thats the plan! No, I don’t think there are trolls here yet and we try to keep it like that!