Search the Community
Showing results for tags 'manjaro'.
Found 4 results
KRONOS Kronos (Originally Denarius Pi - dPi) is a AIO interface/wallet for Denarius. Kronos was originally built with the intention of running it and installing it on Raspberry Pi Ubuntu systems, but now can be used mostly for all Linux distros. It is recommended to have at least 2GB of RAM to install and run Kronos (It also runs a Denarius node). Features: Send and Receive D Denarius Addresses with P2PK and P2PKH scripthashed balances Import and Export Private Keys View Transactions Terminal (Access your terminal for advanced use or restarting your Denarius node manually) Generate Minikeys Convert Minkeys Encrypted Local LevelDB 24 Word Seed Phrases Block Explorer (View Addresses, Transactions, and Blocks) Stake your Denarius Monitor your configured FortunaStakes Verify Denarius Messages Sign Denarius Messages Backup Wallet Send Raw Transactions View Current OS Enviroment Statistics like CPU and Memory Usage Runs on local network by default, so great for running on a local Pi or Linux box and then accessing it from your phone or other computer, can also run it locally if viewing with a monitor on a Pi or Linux box. More Coming Soon How to Install: Run one of these commands depending on your flavor of Linux! wget -qO- https://raw.githubusercontent.com/carsenk/kronos/master/installkronos.sh | bash or curl -o- https://raw.githubusercontent.com/carsenk/kronos/master/installkronos.sh | bash Github: https://github.com/carsenk/kronos Screenshot of Kronos: Screenshots when this all started (dPi): More information and list of features will be coming soon! Stay tuned! It will be a one liner install script to run.
Its very easy to setup the Denarius wallet daemon using SNAP on most Linux distributions, including even a 2GB or more ram Raspberry Pi4. Arch, CentOS, Debian, elementary, Fedora, KDE Neon, Kubuntu, Manjaro, Mint, openSUSE, Red Hat, and Ubuntu are just a few of the supported distros. I will assume you are running a single daemon on a VPS, first create directory as we want to download chaindata and unzip into the proper folder first. If you end up using parallels to install more than 1 snap daemon on your server, the directories would be like this and each need their own chaindata. ~/snap/denarius_1/common/.denarius ~/snap/denarius_2/common/.denarius ~/snap/denarius_3/common/.denarius Start creating the directory so we can grab chaindata for the unzip. If you are using a pi4 or similar ARM server, use the ARM download link. AMD64 - https://denarii.cloud/chaindata.zip ARM - https://denarii.cloud/pichaindata.zip mkdir ~/snap mkdir ~/snap/denarius mkdir ~/snap/denarius/common mkdir ~/snap/denarius/common/.denarius cd ~/snap/denarius/common/.denarius/ wget https://denarii.cloud/chaindata.zip unzip chaindata.zip rm chaindata.zip Pick your OS to install Denarius Daemon from Snap Page https://snapcraft.io/denarius Example Ubuntu sudo apt update sudo apt install snapd sudo snap install denarius Run Snap Daemon denarius.daemon this will auto generate a denarius.conf Stop Snap Daemon after about 60 seconds denarius.daemon stop Edit denarius.conf to add your privkey to denarius.conf and delete these 2 lines fortunastake=0 and fortunastakeaddr= nano denarius.conf fortunastakeprivkey=YOURFORTUNASTAKEGENKEYHERE Example denarius.conf rpcuser=5fWxpSAp rpcpassword=2uArAP0XQvL20a6GuqR5MnP rpcport=32369 port=33369 daemon=1 listen=1 server=1 fortunastakeprivkey=YOURFORTUNASTAKEGENKEYHERE addnode=22.214.171.124 addnode=126.96.36.199 addnode=188.8.131.52 addnode=184.108.40.206 addnode=220.127.116.11 addnode=18.104.22.168 addnode=22.214.171.124:33369 addnode=126.96.36.199:333691 addnode=188.8.131.52:33369 addnode=184.108.40.206:33369 addnode=220.127.116.11:33369 addnode=18.104.22.168:33369 addnode=22.214.171.124:33369 addnode=126.96.36.199:33369 addnode=188.8.131.52:33369 addnode=184.108.40.206:33369 addnode=220.127.116.11:33369 addnode=18.104.22.168 addnode=[2001:bc8:47a8:2519::1] save -> ctrl+x yes Run Snap Daemon denarius.daemon To watch the debug.log as this syncs and to watch the enable happen tail -f debug.log For the 5000 D send please use the original guide for reference.
Mine randomx on Manjaro. I assume same thing to run on Arch btw #compile xmrrig on Manjaro sudo pacman -S base-devel cmake libuv libmicrohttpd openssl hwloc libutil-linux git clone https://github.com/xmrig/xmrig.git cd xmrig mkdir build && cd $_ cmake .. make
I am using a yubikey 5 for this and Manjaro KDE distro. Amazon has same day delivery https://amzn.to/338KYgF slightly different but basically the same as official arch install, except I took out assuming the -m and $MK PIV application's 24-byte management key part as it didn't work for me when generating the self signed certificate. https://wiki.archlinux.org/index.php/YubiKey#Using_a_YubiKey_with_SSH #install yubikey manager sudo pacman -S yubikey-manager yubikey-manager-qt #plug in yubikey and verify it can be seen ykman list #generate key ykman piv generate-key -a RSA2048 9a pubkey.pem #generate self signed certificate ykman piv generate-certificate -d 1826 -s "SSH Key" 9a pubkey.pem #install opensc package sudo pacman -S opensc #configure ssh to use opensc library nano ~/.ssh/config #enter single line below, save and exit PKCS11Provider /usr/lib/opensc-pkcs11.so #convert public-key to standard openssh format ssh-keygen -i -m PKCS8 -f pubkey.pem > pubkey.txt #cat pubkey.txt to see your public key. example can copy and paste the public key into scaleway credentials cat pubkey.txt #or another way to get the public key onto your server cat ~/pubkey.txt | ssh [email protected] 'cat >> .ssh/authorized_keys' now when you ssh into your server, plug in your yubikey and you will be asked for a pin at the login prompt example ssh [email protected] and you will now be prompted for the yubikey pin to access your server