Jump to content


Popular Content

Showing content with the highest reputation since 01/18/2019 in all areas

  1. 4 points
  2. 3 points
    I'm gonna start off with this guide is an adapation of this topic but for Denarius QT. At this time, I haven't been able to compile the QT with NativeTor or UPNP but when I do figure it out, I will update this thread. 0. Preparing Your System As with compiling every project, you need a compiler for the wallet and all the dependencies. Your patience will be tested multiple times duing the build and you have to be ready to spend a good 5 hours or so depending on the speed of your cpu. There are tools you have to install in order to compile. There are a few programs you should have installed to make the process easier here they are: 7-Zip for extracting files, choose the option appropriate for your system Notepad++ for editing certain files duing the building process Lets us start with MinGW, you can download it from here. That will download and install the MinGW. Once installed and open you should see a screen like this one: Click MinGW and Unmark everything, then click MSYS and unmark everything. Then mark the following items under MSYS: msys-autoconf-bin msys-automake-bin msys-base-bin msys-libtool-bin Its okay for other packages to become marked as you make the above, the others are dependencies. Then go to Installation -> Apply Changes -> Apply it will take a minute to download everything Next you are gonna wanna install the MinGW-builds toolchain from here. While compiling, you are gonna have 2 different cli-type interfaces open, more on that later. Unpack that archive to your drive root, for me that is C:\. Next create a folders in your drive root called deps and Qt. This is where we are gonna compile our dependencies. When all steps completed, your file structure should look similar to mine with all the folders outlined in red: Next we are going to make sure that the MinGW is in your PATH environment variable. To to this on windows 10, Search environment variable in the search on the bottom. You will get a window and on the bottom will be a button that says Environment Variables. Click it and go to the second list where its says System variables and scroll down to Path: If you dont see C:\mingw32\bin; at the front, add it in. You may need to reboot your computer to continue this tutorial, one way you can tell is if you open up command prompt and type gcc -v. If it tells you that gcc is an unrecognized program or file, reboot your computer, if not you are good to go and continue. Lastly make sure that the only file in C:\MinGW\bin should be mingw-get.exe. Now to extracting. 1. Downloading and Extracting Dependencies Here are a list of dependencies for you to download. I suggest downloading each one at a time and immediately starting the next as soon as the former has finished: OpenSSL .tar.gz DO NOT UNPACK YET Berkeley DB .tar.gz DO NOT UNPACK YET libboost 1.57.0 .zip Explorer to deps protoc and libprotobuf tar.gz 7Zip to deps libpng 1.6.16 .tar.gz 7Zip to deps qrencode .tar.gz 7Zip to deps QT Base 5.3.2 .7z 7Zip to QT rename to 5.3.2 QT Tools 5.3.2 .7z 7Zip to QT There are newer versions of QT Base and QT Tools but version 5.13 and 5.12 both have strange errors when attempted to compile. Just use 5.3.2. Once every thing is extracted to your deps folder, it should look like this: And your Qt folder should look like this: 2. Compiling Dependencies Finally time to compile, first you are gonna wanna start with OpenSSL. If you remember, I told you not to unpack it with 7ZIP, we are gonna be using tar in the MinGW shell. To open the shell, open C:\MinGW\msys\1.0\msys.bat and do the following: cd /c/deps/ tar xvfz openssl-1.0.1l.tar.gz cd openssl-1.0.1l ./Configure no-zlib no-shared no-dso no-krb5 no-camellia no-capieng no-cast no-cms no-dtls1 no-gost no-gmp no-heartbeats no-idea no-jpake no-md2 no-mdc2 no-rc5 no-rdrand no-rfc3779 no-rsax no-sctp no-seed no-sha0 no-static_engine no-whirlpool no-rc2 no-rc4 no-ssl2 no-ssl3 mingw make This will change directory to your deps folder, extract OpenSSL, configure and compile it. Next comes Berkeley DB which I also told you not to extract. Do the following in MinGW shell: cd /c/deps/ tar xvfz db-4.8.30.NC.tar.gz cd db-4.8.30.NC/build_unix ../dist/configure --enable-mingw --enable-cxx --disable-shared --disable-replication make After Berkeley DB finishes, we will build libboost in Windows Command Prompt: cd C:\deps\boost_1_57_0\ bootstrap.bat mingw b2 --build-type=complete --with-chrono --with-filesystem --with-program_options --with-system --with-thread toolset=gcc variant=release link=static threading=multi runtime-link=static stage While libboost is compiling, compile protoc and libprotobuf in MinGW shell: cd /c/deps/ tar xvfz protobuf-2.6.1.tar.gz cd /c/deps/protobuf-2.6.1 configure --disable-shared make When protoc and libprotobuf are done, compile libpng in MinGW shell: cd /c/deps/libpng-1.6.16 configure --disable-shared make cp .libs/libpng16.a .libs/libpng.a That last line will rename libpng to a name that qrencode can use. Once done compile qrencode cd /c/deps/qrencode-3.4.4 LIBS="../libpng-1.6.16/.libs/libpng.a ../../mingw32/i686-w64-mingw32/lib/libz.a" \ png_CFLAGS="-I../libpng-1.6.16" \ png_LIBS="-L../libpng-1.6.16/.libs" \ configure --enable-static --disable-shared --without-tools make LIBS sets the libraries for qrencode to compile with. After set, go back to Windows Command Prompt. libboost should be done, if not wait until it is. You shold have renamed the folder QT Base extracts from to 5.3.2, the following requires that it is. Run these commands to compile QT Base and QT Tools. Note* if you have a quad core processor, run all mingw32-make commands with -j4 to speed up the compile time: set INCLUDE=C:\deps\libpng-1.6.16;C:\deps\openssl-1.0.1l\include set LIB=C:\deps\libpng-1.6.16\.libs;C:\deps\openssl-1.0.1l cd C:\Qt\5.3.2 configure.bat -release -opensource -confirm-license -static -make libs -no-sql-sqlite -no-opengl -system-zlib -qt-pcre -no-icu -no-gif -system-libpng -no-libjpeg -no-freetype -no-angle -no-vcproj -openssl -no-dbus -no-audio-backend -no-wmf-backend -no-qml-debug mingw32-make set PATH=%PATH%;C:\Qt\5.3.2\bin cd C:\Qt\qttools-opensource-src-5.3.2 qmake qttools.pro mingw32-make *IMPORTATNT* Now that everything is compiled rename the openssl-1.0.1l directory to openssl-1.0.1j. Finally we are ready for the gritty part of the tutorial, compiling Denarius QT 4. Downloading and Compiling Denarius QT Download which ever version of the repo you want. Beta v3.4 is here, and extract it to whichever folder you like, try to put it in a path without any spaces. the deps folder works just fine. Open up Notepad++ we will need it later. There is one last dependency to compile before we can build Denarius QT, and that is leveldb. It comes packaged with Denarius repo and is located in the src folder of your extracted download. The full path for me is C:\deps\denarius-3.4\src\leveldb. Perform the following in MinGW shell to build: cd /c/deps/denarius-3.4/src/leveldb TARGET_OS=NATIVE_WINDOWS make libleveldb.a libmemenv.a Once compiled you should see somewhere at the end both libleveldb.a and libmemenv.a. In Windows Command Prompt, change directory to your downloaded denarius folder, mine is C:\deps\denarius-3.4, set PATH to include QT Tools and use qmake: cd C:\deps\denarius-3.4 set PATH=%PATH%;C:\Qt\5.3.2\bin qmake "USE_QRCODE=1" "USE_UPNP=-" "USE_NATIVETOR=-" denarius-qt.pro This will configure our build to compile on windows with QT, and QR support and without UPNP and Native Tor. Next you wanna open Notepad++ and edit the Makefile.Release file. Press CTRL+F and search for -levent and delete it. To finally compile Denarius QT, run mingw32-make in Windows Command Prompt and wait: *Note be sure to add -j4 on the end to make it compile faster if you are on a quad core machine!!! mingw32-make If the compilation is stuck on a file for a long time, like 50 or so seconds, press CTRL + C very quickly to force the compilation to continue. This may cause an error at the end saying a file with a .o extention is corrupted or missing. Just delete that file and run the above command again. You will know that the compilation succeded when in the release folder of denarius has Denarius.exe in it. My path being C:\deps\denarius-3.4\release. If you have any questions or comments, post them below and I will try to answer them.
  3. 3 points
    @Sheila, join our Discord if you want to learn more - https://discord.gg/BwfAmkE - The community is very helpful and supportive. Don't be afraid to ask any questions you may have.
  4. 3 points
    Now that we have a wallet with address and some Denarius coins, we look at staking your Denarius crypto coins. The way staking works is that D will stake at 6% over the year. 33% of that 6% goes to fortunastake (masternodes). Staking wallets and fortunastakes both help to secure the Denarius blockchain. To get an idea of how much you can receive daily with 100 D. 100 D * 0.06 = 6 D per year 6 D / 365 days = 0.01643835 D per day 0.01643835 D * 0.67 = 0.01101369863 D per day with 33% going to FortunaStakes You can leave your wallet open constantly and help verify transactions and stake frequently, or open your wallet every once in a while to stake. This is up to you. I prefer to leave the wallet open constantly staking, as Denarius is a hybrid cryptocurrency during the Proof of Work and Proof of Stake phase. The safest way to stake your coins is by unlocking the wallet to only stake. Another option if you are planning to transfer Denarius coins to someone else is by fully unlocking the wallet.
  5. 3 points
    Thanks for this.Yeah this is more elegant way to do it.
  6. 3 points
    Wookie bro you did an amazing job, build me a house bro! Lol Buzz killed it on the pi installation!! Absolutely blown away!
  7. 3 points
    I think I know what coin chart you can put on the 2nd TV. 🤑
  8. 2 points
    After a recent windows update I have a wallet installation that stops with an error as attached png. I do have a backup of a few days previously. Anyone got a recommendation on how to get this back up and running?
  9. 2 points
    Guide to installing Qbuntu (Ubuntu 16.04 - Xenial) TemplateVM in Qubes 4.0.2-rc1 fedora-30 as of this writing, I did this on a fresh Qubes install on a Lenovo t450 i7, 8gb ram, 256gb samsung ssd ($280 - ebay) https://www.qubes-os.org/ Basic Idea (but does not work, don't even bother trying to decipher their ubuntu guide as its for someone who somehow knows how to do this already) https://www.qubes-os.org/doc/building-archlinux-template/ Reddit Guide (copying some of the steps from this old guide with some edits to work on Qubes 4.0 as this was written for Qubes 3.2) https://www.reddit.com/r/Qubes/comments/5vzg04/idiots_guide_to_installing_qbuntu_ubuntu_1604/ #gpg stuff from qubes themselves reference: https://wiki.qubes.rocks/Security/VerifyingSignatures Lets Begin Clone your fedora-30 vanilla template into a temporary 'builder' we will use to create Ubuntu templates. [[email protected] ~]$ qvm-clone fedora-30 ubuntu-builder Edit the VM Settings for the newly created template 'ubuntu-builder' (via Qubes Manager GUI), enable 'Allow network access' & increase 'Private storage max size' to 30GB, then start a terminal in ubuntu-builder and initialize GPG [[email protected] ~]$ gpg Break out of "type your message..." with CTRL+C, import Qubes master key [[email protected] ~]$ gpg --recv-keys 0x36879494 Set trust level for qubes master key [[email protected] ~]$ gpg --edit-key 36879494 gpg> trust >Your decision? 5 >Do you really want to set this key to ultimate trust? Y gpg> quit Now retrieve and import Qubes developer keys [[email protected] ~]$ wget http://keys.qubes-os.org/keys/qubes-developers-keys.asc [[email protected] ~]$ gpg --import qubes-developers-keys.asc #install nano [[email protected] ~]$ sudo dnf install nano Install the packages we need to retrieve and run qubes-builder [[email protected] ~]$ sudo dnf install git createrepo rpm-build rpm-sign make python-sh rpmdevtools rpm-sign dialog Retrieve the qubes-builder from GIT repository [[email protected] ~]$ git clone https://github.com/QubesOS/qubes-builder [[email protected] ~]$ cd qubes-builder Edit default config to enable debian_builder only in setup script (example used VI but you can use text editor of your choice, like nano installed above) [[email protected] qubes-builder]$ vi example-configs/qubes-os-r4.0.conf (to check our current version installed, go to Qube Manager -> About -> Qubes OS) Change these lines to look like this DIST_DOM0 ?= fc30 DISTS_VM ?= hint: DOM0 distro being fc30 in this Qubes install, & remove "fc30 buster" from above save and exit (shift-z-z if using vi) Setup qubes-builder and compile the template Run the qubes-builder setup script [[email protected] qubes-builder]$ ./setup Y to add whats missing then yes to add missing keys this failed on me the first time, I ctrl+c and reran ./setup again, did Y again, and it found the keys that were missing after selecting YES, had to even shutdown the qube and try again as it kept glitching out trying to retrieve keys select 4.0 stable dont select current or current-testing (wtf? is this madness) yes (to only build the template) select xenial+desktop with spacebar and push enter select Builder-rpm builder-debian only, nothing else. (I was using the guide to test installing Bionic 18.04 for screenshots) #now you are back at the command prompt and type these in, one by one. The last 2 will take some time so go to Denarius discord and chat with us while waiting. https://discord.gg/7zcwXJN make install-deps make get-sources make qubes-vm make template We have our Ubuntu 16.04 template, now to install it! Qubes-builder should have created an install script, let's make sure it exists: [[email protected] qubes-builder]$ ls -altr qubes-src/linux-template-builder/rpm You should see an 'install-template.sh' file there. Now switch back to your dom0 terminal, and install the template: [[email protected] ~]$ qvm-run --pass-io ubuntu-builder 'cat /home/user/qubes-builder/qubes-src/linux-template-builder/rpm/install-templates.sh' > install-templates.sh Make the copied script executable and run it [[email protected] ~]$ chmod +x install-templates.sh [[email protected] ~]$ ./install-templates.sh #make template (clone) just for denarius, why not in dom0 terminal emulator qvm-clone xenial-desktop denarius-crypto goto qubes-settings for denarius-crypto qube and add your network (I used sys-whonix running tor), run terminal and start to compile the wallet I am choosing color purple background to break out any crypto stuff so I know be careful ignore any errors (pulse audio) #compile denarius QT in template: denarius-crypto sudo apt-get update -y && sudo apt-get upgrade -y sudo apt-get install -y git unzip build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev libminiupnpc-dev libevent-dev autogen automake libtool libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools qt5-default git clone https://github.com/carsenk/denarius cd denarius git checkout master git pull qmake "USE_QRCODE=1" "USE_UPNP=1" denarius-qt.pro make -j2 sudo cp Denarius /usr/local/bin #setup appvm with name reference: https://www.qubes-os.org/doc/managing-appvm-shortcuts/ sudo nano /usr/share/applications/denarius.desktop [Desktop Entry] Version= Type=Application Terminal=false Icon=/home/user/denarius/src/qt/res/icons/denarius-256.png Name=Denarius GenericName=wallet Comment=Denarius Categories=crypto;cryptocurrency; Exec=Denarius in dom0 run qvm-sync-appmenus denarius-crypto now you can add Denarius to your app selection list in the template select denarius from your template: denarius-crypto and start syncing eet
  10. 2 points
    How to install bionic-builder template for Ubuntu 18.04 in Qubes OS 4.0.2-rc1, Qbuntu Clone your fedora-30 vanilla template into a temporary 'builder' we will use to create Ubuntu templates. Top left button -> Terminal Emulator [[email protected] ~]$ qvm-clone fedora-30 ubuntu-builder go into the bionic-builder template and pick your network (sys-firewall), and give yourself 30gb for private storage. Open the terminal for this template and begin. [[email protected] ~]$ gpg I missed the receive keys screenshot [[email protected] ~]$ gpg --recv-keys 0x36879494 [[email protected] ~]$ gpg --edit-key 36879494 gpg> trust >Your decision? 5 >Do you really want to set this key to ultimate trust? Y gpg> quit [[email protected] ~]$ wget http://keys.qubes-os.org/keys/qubes-developers-keys.asc [[email protected] ~]$ gpg --import qubes-developers-keys.asc [[email protected] ~]$ sudo dnf install nano [[email protected] ~]$ sudo dnf install git createrepo rpm-build rpm-sign make python-sh rpmdevtools rpm-sign dialog [[email protected] ~]$ git clone https://github.com/QubesOS/qubes-builder [[email protected] ~]$ cd qubes-builder [[email protected] qubes-builder]$ nano example-configs/qubes-os-r4.0.conf [[email protected] qubes-builder]$ ./setup select Y to anything missing Select Yes to keys that don't exist. Select Yes to add, this one glitches out for me, but worked first try writing this. Just keep rerunning ./setup over and over until this passes through. If this still won't work, change the pgp.mit.edu server to something else in the setup file. nano setup GPG_KEY_SERVER = 'ha.pool.sks-keyservers.net ' Select Qubes Release 4.0 Select Stable Select none of these options Build Template Only? Yes Select your OS template, this example is using Bionic+desktop Select builder-rpm and builder-debian Get Source? Yes Wait while this gets what the source files. This screen gives us what to do next. make install-deps make get-sources make qubes-vm make-template [[email protected] qubes-builder]$ ls -altr qubes-src/linux-template-builder/rpm Go to your dom0 terminal and move the install-templates.sh file over [[email protected] ~]$ qvm-run --pass-io ubuntu-builder 'cat /home/user/qubes-builder/qubes-src/linux-template-builder/rpm/install-templates.sh' > install-templates.sh [[email protected] ~]$ chmod +x install-templates.sh ./install-templates.sh After this was done, I cloned this into a crypto version to play around in. This is a cryptocurrency related site after all. qvm-clone bionic-desktop bionic-crypto After that, I then deleted the bionic-builder templateVM from Qube Manager to save some disk space.
  11. 2 points
    This is a very easy way to track addresses from your android phone. Like watching masternode payments live. Download Coldfolio from https://whopper.io/ which links to the Google Play Store. Add a card Select your Crypto from the List Scan QR Code from the Denarius QT Wallet go to receive tab, click address and then click below Show QR Code Label your Card in Coldfolio and double check you only have the address This example shows the ?label=MN2, delete this part. This can always be modified later by hodling down the card and clicking modify. Keep track of your staking, masternodes, balances.
  12. 2 points
    I'm aware that there is an issue with getting Denarius address' balances. Ive patched the app recently. Expect an update in the next few days 4o be pushed to the play store.
  13. 2 points
  14. 2 points
    Coinexplorer has some useful information that's similar to the QT Wallet staking probability tab. https://www.coinexplorer.net/D Go to one of your addresses by typing in the address into the search bar and lets see some more staking information. What we are looking for on our own address page is the See Address Unspent Outputs page. In the Unspent Output page we can see all of the inputs waiting for staking in our own wallet to this particular address. AVG Days to Stake is what I am looking for. In this example we can see roughly how long it might take for that amount to stake. Typically a 3 D input will stake within a few days of maturing.
  15. 2 points
    I think this is an easier way to setup an electrumx server. It's not that bad once you go through the steps. Trying to be thorough. Install docker My github for this. https://github.com/buzzkillb/docker-electrumx We will end up running denariusd in a container and electrumx in a container. First create a folder on your server or vps to store the denarius blockchain. This can be anywhere, but lets make this easy. cd ~ mkdir .denarius cd .denarius nano denarius.conf Sample denarius.conf, pay attention as we will need the rpcuser and rpcpassword. rpcuser=denariusrpc rpcpassword=MAKEUPSOMEPASSWORD maxconnections=125 rpcport=32369 port=33369 daemon=0 listen=1 server=1 discover=1 txindex=1 bind= We either sync from block 0 or use chaindata. You decide. Now we can run the denariusd docker container. docker run \ --net=host \ --name=denariusd \ -t -d \ -p 33369:33369 \ -p 32369:32369 \ -v ~/.denarius:/data \ -P buzzkillb/denariusd:latest To check the sync docker logs denariusd -f ctrl+c to exit out of that whenever Now to run electrumx server (wait to be fully sync'd). docker run \ --name=electrumx \ --net=host \ --ulimit nofile=5120:5120 \ -t -d \ -v ~/electrumx:/data \ -e DAEMON_URL=http://denariusrpc:[email protected]:32369 \ -e COIN=Denarius \ -p 50001:50001 \ -p 50002:50002 \ buzzkillb/docker-electrumx:latest To watch these logs. docker logs electrumx -f Once running check it can be found. openssl s_client -connect electrumx1.denarius.pro:50002 Working on an easy way to do the compaction. If you stop the container and then run docker run \ --name=electrumx-compact \ --net=host \ --ulimit nofile=5120:5120 \ -t -d \ -v ~/electrumx:/data \ -e DAEMON_URL=http://denariusrpc:[email protected]:32369 \ -e COIN=Denarius \ -p 50002:50002 \ buzzkillb/docker-electrumx:dcompact This will compact the database using Denarius environment variables. With both containers electrumx and electrumx-compact both up, we can now add a cronjob to stop server, start compact, and restart server. crontab -e Run daily, this is overkill. Best to run every 14 days or less. 0 0 * * * docker stop electrumx >/dev/null 2>&1 1 0 * * * docker start electrumx-compact >/dev/null 2>&1 6 0 * * * docker start electrumx >/dev/null 2>&1
  16. 2 points
    To run ElectrumX, use Ubuntu 16.04 and have the denariusd daemon already setup. I tried this first in a VM. #install python 3.7 sudo apt update sudo apt install software-properties-common sudo add-apt-repository ppa:deadsnakes/ppa sudo apt update sudo apt install python3.7 #install pip sudo apt-get install python-pip sudo apt-get install python3-pip #prepare for installing electrumx (this could use some pruning) sudo apt-get install python3.7 python3.7-dev python3-pip libleveldb-dev libssl-dev python3-distutils sudo -H python3.7 -m pip install plyvel pylru aiorpcx aiohttp sudo apt-get install build-essential libsnappy-dev zlib1g-dev libbz2-dev libgflags-dev cmake liblz4-dev sudo python3.7 -m pip install --upgrade pip setuptools wheel sudo apt-get install python3.7-dev sudo python3.7 -m pip install --upgrade aiohttp pylru leveldb plyvel aiorpcx ecdsa tribus_hash #Use electrumx installer script wget https://raw.githubusercontent.com/bauerj/electrumx-installer/master/bootstrap.sh -O - | bash #Use service electrumx start to start electrumx once it's configured #Generating TLS certificates #electrumx has been installed successfully. Edit /etc/electrumx.conf to configure it. Replace denariusrpc and the password with your stuff configured in denarius.conf in ~/.denarius/denarius.conf Don't forget to have txindex=1 in your denarius.conf as well. sudo nano /etc/electrumx.conf #electrumx.conf # default /etc/electrumx.conf for systemd COIN = Denarius # REQUIRED DB_DIRECTORY = /db # Bitcoin Node RPC Credentials DAEMON_URL = http://RPCUSERNAME:[email protected]:32369/ # See http://electrumx.readthedocs.io/en/latest/environment.html for # information about other configuration settings you probably want to consider. DB_ENGINE=leveldb SSL_CERTFILE=/etc/electrumx/server.crt SSL_KEYFILE=/etc/electrumx/server.key TCP_PORT=50001 SSL_PORT=50002 # Listen on all interfaces: HOST= #run electrumx server service electrumx start #check its running journalctl -u electrumx -f #test openssl s_client -connect IPGoesHere:50002
  17. 2 points
    Thanks to @manosv for the nice little kill cronjob to make sure the daemon isnt crashed out. Make sure you know where your denariusd is located for proper path. crontab -e 25 */1 * * * /usr/local/bin/denariusd stop 26 */1 * * * /usr/bin/killall -q -9 denariusd 27 */1 * * * /usr/local/bin/denariusd
  18. 2 points
    Great guide, we need to start building a list of available servers, the more the better.
  19. 2 points
    All I see for votes PRO FPGA are freshly made accounts, sent here to vote because someone from FPGA community asked them to do so. Seems that the twitter vote being askewed by 63-37% wasn't already telling enough. The entire Denarius discord, even those who own FPGA's are against the idea of keeping FPGA's on Tribus. They don't see additional value in keeping them on, for those FPGA guys coming it here telling it's lacking trade volume and they are no threat? I've been in your Discord yesterday, you guys want to achieve 200k Denarius in a matter of months, the total supply will never exceed 10 million coins. Yet us GPU miners know how slow Denerius trickles in when it's mined en masse with even just GPU's only. We weren't waiting for you coinhoggers to claim almost 80% of daily POW rewards. I've seen yesterday dat alot from your community doen't even know what Denarius features are, you were wondering if it was a long term or short term hold now when the debate was openened about changing the algo to GPU only. Some of you still had to look up it's features, I mean? You guys cry about a coin you know jack shit about but the profit you might lose that is your only interest. Yet we as the Denarius community don't want you to mine it, that is the main sentiment from nearly all members in Discord, yet you guys take the lead in votes. Why is that? Cuz you already asked the entire FPGA community to vote on the twitter poll and they are not slowly being sent in here to do the same. Member it's a community vote, the ones who don't want this are more vocal than those who are PRO FPGA, cuz let's face it, those voting here pro FPGA only found out yesterday that Denarius has a masternode stystem (FS) or POS, or POW ending in about 1.25kk blocks? And they didn't even know they were talking to Carsen (the dev) before he popped a vain. So, the people who are less invested in it emotionally or connected to the brand and the coin itself, are the ones who are pulling this vote towards them. Claiming they will dump the coin when we change the algo because they say it becomes worthless if THEY can not mine it. Tell me how does it become worthless when all the suddon it's no longer being mined by a select few but is being mined by the masses, giving a broader audience to reach with GPU only mining and avoiding centralizing our coin supply in the hands of a few who are either willing ot obtain 200k (0.2% of max supply) until they can dump it for profit or those who just dump it immediatly after they mine it. Open up your eyes, pull those dollar signs out of your sight and face it, FPGA people are NOT interested in the wellbeing of Denarius only thing tha matter is their own wallet. But hey, make some more newbie accounts, copy paste some messages from eachother and nothing happened right? We'll see, we'll see!
  20. 1 point
    How to compile QT and daemon on various versions of Ubuntu. Ubuntu 16.04 Daemon sudo apt-get update -y && sudo apt-get upgrade -y sudo apt-get install -y git unzip build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev libminiupnpc-dev libgmp-dev libevent-dev autogen automake libtool libcurl4-openssl-dev git clone https://github.com/carsenk/denarius cd denarius git checkout master git pull cd src make -f makefile.unix sudo mv ~/denarius/src/denariusd /usr/local/bin/denariusd denariusd QT sudo apt-get update -y && sudo apt-get upgrade -y sudo apt-get install -y git unzip build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev libminiupnpc-dev libevent-dev autogen automake libtool libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools qt5-default libcurl4-openssl-dev git clone https://github.com/carsenk/denarius cd denarius || exit git checkout master git pull qmake "USE_QRCODE=1" "USE_UPNP=1" denarius-qt.pro make ./Denarius
  21. 1 point
    Lets make sure to run that python file over and over and over on every new block. Go into denarius.conf and add this line. I have my files in a influx directory. blocknotify=/home/USERNAME/influx/block.sh Lets create block.sh in the influx directory and throw our sample.py in there #!/bin/bash python /home/USERNAME/influx/sample.py make block.sh executable chmod +x block.sh stop and restart daemon to pick this change up denariusd stop denariusd If it all went right your grafana page should start updating the block count.
  22. 1 point
    Login to your localhost grafana. on the left click the gear -> data sources add data source search for influxdb use settings like this save and test Go back to the grafana homepage and click + and add query Your query would look something like this. Remember to select your mydb database, my screenshot is using another name for the DB. Visualization General Click Save at the top right Should see something like this on your homepage.
  23. 1 point
    Download Denarius Wallet Install IPFS (locally or vps) https://docs.ipfs.io/guides/guides/install/ Ubuntu (AMD64) Find latest here - https://dist.ipfs.io/#go-ipfs wget https://dist.ipfs.io/go-ipfs/v0.4.22/go-ipfs_v0.4.22_linux-amd64.tar.gz tar xvfz go-ipfs_v0.4.22_linux-amd64.tar.gz cd go-ipfs sudo ./install.sh ipfs version #start ipfs node and take note of your IPFS node ID ipfs init #example output ``` initializing IPFS node at /home/travanx/.ipfs generating 2048-bit RSA keypair...done peer identity: QmNyud5DGEmkBGYcV4QA69JHiTuWLU6EkStpviddZTgiag to get started, enter: ipfs cat /ipfs/QmS4ustL54uo8FzR9455qaxZwuMiUhyvMcX9Ba8nUH4uVv/readme ``` #try reading the readme ipfs cat /ipfs/QmS4ustL54uo8FzR9455qaxZwuMiUhyvMcX9Ba8nUH4uVv/readme #start IPFS service ipfs daemon denarius.conf jupiterlocal=1 if you want to specify your IPFS server and its not local add jupiterip=yournodeIP:5001 To upload a file #example command to upload using daemon or QT from debug console, other use the Jupiter tab in the QT jupiterupload /home/USERNAME/Downloads/denarius-256.png Carsen uploaded the below image using localhost, then turned off his localhost IPFS server and because Denarius is amazing the file still shows up.
  24. 1 point
    Grab the latest QT wallet with IPFS built in and have 0.1 D or at least something small to pay the PoD fee. IPFS is free and can skip the PoD portion of this if you just want to upload files. Lets pick a good file to Proof of Data against and then upload into IPFS. Current Release: https://github.com/carsenk/denarius/releases/tag/v3.3.9.6 QT Wallet: https://github.com/carsenk/denarius/releases/download/v3.3.9.6/Denarius-v3.3.9.6-Win64.zip Download a file, I am going to use the denarius logo from denarius.io and lets proof of data this and upload to IPFS as a great example of how powerful this is. Here's a link but just right click the image on the homepage and save to your hard drive. https://i2.wp.com/denarius.io/wp-content/uploads/2017/11/denarius-256.png?w=256&ssl=1 Go to the Jupiter Tab Select your file, in this case select the image file we just downloaded. Click Upload to IPFS (The Wallet will freeze while the upload is taking place) After the upload you will get an IPFS Hash along with being able to click the link to see the file in your web browser. Success, and currently there are file limits on uploading through the wallet. I was not able to upload the QT.zip yet. Lets Proof of Data this file for good measure, so the original hash is located on the Denarius blockchain. Go to Proof of Data tab in QT Wallet Select our image, then put a simple narration in and then click Create Timestamp This now gives us a D address where the hash matches the image. Now if we download the image we uploaded to IPFS we can verify the file against the blockchain by checking against PoD again. Here is our set in the blockchain address based on the image file or can Click Check Transaction to get to your PoD transaction. https://www.coinexplorer.net/D/address/DQQxYgD1KPzmoQGeL1JyXZk2JhZPfiaXsY
  25. 1 point
    I have denarius snap already installed so I add denarius_1 as above and this is what snap list shows. snap list Name Version Rev Tracking Publisher Notes core 16-2.41 7713 stable canonical✓ core core18 20191001 1192 stable canonical✓ base denarius 77 stable carsenk - denarius_1 77 stable carsenk - to run the 2nd denarius daemon denarius_1 denarius_1.daemon denarius_1 is now in the ~/snap/denarius_1 folder ~/snap$ ls -l total 28 drwxr-xr-x 5 user user 4096 Oct 5 20:15 denarius drwxr-xr-x 4 user user 4096 Oct 6 10:18 denarius_1 hint: listen=0 and +1 to port and rpcport per additional daemon/QT EZ-MODE
  26. 1 point
    put these options in the denarius.conf file and restart the qt wallet staking=1 fsconflock=1 This will enable two things.Obviously the first enables the staking and the second locks the collateral so it wont stake.So you will be able to unlock and stake the earnings without breaking the collateral.Enjoy and welcome to our Community.
  27. 1 point
    @EnterpointYohan Remove everything in your Denarius data directory (C:/Users/<yourname>/AppData/Roaming/Denarius) EXCEPT for your wallet.dat (back that up), then grab the latest chaindata from here and unzip it into that folder (you should see a blk*.dat and txleveldb folder after extraction in the Roaming/Denarius/ root) You can get the latest chaindata from here: https://gitlab.com/denarius/chain/raw/master/chaindata2290877.zip Also ensure you grab our latest release v3.3.9.3 https://github.com/carsenk/denarius/releases This is an error relating to the txleveldb (your chaindata) being corrupt, Windows can do this possibly after an update if the wallet was open when the computer was turned off/rebooted or possibly Anti-Virus software trying to read/move files.
  28. 1 point
    A guide on how to setup Windows 10 in Qubes 4.0.2-rc1, and then how to login using RDP in a Fedora Qube for clipboard anf file sharing. If you are finding this tutorial, I am going to skip some of the basic how to install Windows 10 shenanigans, as that's a bit redundant. First read through the original guide a few times to get a feel for this. https://groups.google.com/d/msg/qubes-users/dB_OU87dJWA/X2WWa1y-BQAJ What I did was get the Win10 ISO from MS download tool and put that windows.ISO file on a usb drive. https://www.microsoft.com/en-us/software-download/windows10 I then took this file and put it inside a qube's download folder. Once there we use the official Qubes docs. Choose your qube and folder the ISO was placed in for the last step here. https://www.qubes-os.org/doc/windows-vm/ Create a new Qube: Name: Win10, Color: red Standalone Qube not based on a template Networking: sys-firewall (default) Launch settings after creation: check Click “OK”. Settings: Basic: System storage: 30000+ MB Advanced: Include in memory balancing: uncheck Initial memory: 4096+ MB Kernel: None Mode: HVM Click “Apply”. Click “Boot from CDROM”: “from file in qube”: Select the qube that has the ISO. Select ISO by clicking “…”. Click “OK” to boot into the windows installer. Setup Windows 10 as usual, each time the Qube resets the VM will close, keep starting up again until you get to the login screen. Make sure to put some type of password in as we will use this username and password to login through RDP later in the guide. Setup RDP in Windows 10. Enable Remote Desktop in Settings > System Next we need a Fedora qube running freerdp and a firewall qube. I cloned the Fedora 30 template and sys-firewall templates. Because sys-firewall is based off of the Fedora 30 template lets install freerdp in there, I also installed nano since I prefer that to edit files. open up terminal in fedora-30 templateVM. sudo dnf --refresh install freerdp sudo dnf install nano Clone the sys-firewall qube and I called mine sys-firewall-RDP so I knew which one to mess around with. Clone fedora-30 templateVM and use sys-firewall-RDP for your network, call it whatever, fedora-RDP for eaxmple. Lets get the firewall to talk between Win10 qube and our new fedora-RDP qube. We need the IP addresses of both of these qubes for the next step. Open a terminal in sys-firewall-RDP qube. Example Qube A - fedora-RDP ( Qube B - Win10 ( sudo nano /rw/config/qubes-firewall-user-script iptables -I FORWARD 2 -s -d -j ACCEPT iptables -I FORWARD 2 -s -d -j ACCEPT save this and next file to edit sudo nano /rw/config/rc.local iptables -I INPUT -s -j ACCEPT iptables -I INPUT -s -j ACCEPT Restart the sys-firewall-RDP qube. Open fedora-RDP terminal and Win10 qubes. I was able to ping from fedora-RDP and now we are getting close. a sample run of freerdp xfreerdp /u:<USERNAME> /p:<PASSWORD> /v:<WIN10 QUBE IP>:3389 or xfreerdp /u:buzzkillb /p:denariusrocks /v: Some magic should happen and now you RDP'd into Windows 10. Lets add clipboard sharing and file sharing. xfreerdp /u:buzzkillb /p:denariusrocks /v: /drive:software,/home/user/Downloads /clipboard this will create a Windows shared folder called software in the fedora-RDP qube and share with /home/user/Downloads and also allow copy and paste text. lets just show some extra power of this. regedit this to 1 in your Windows 10 Qube. https://getadmx.com/?Category=Windows_10_2016&Policy=Microsoft.Policies.TerminalServer-Server::TS_ALLOW_APPS xfreerdp /u:buzzkillb /p:denariusrocks /v: /drive:software,/home/user/Downloads /clipboard /app:"C:\Windows\explorer.exe" This line will open a windows of just the Windows File Explorer. I ended up creating a start.sh file with these lines like this. start.sh #!/bin/sh xfreerdp /u:buzzkillb /p:denariusrocks /v: /drive:software,/home/user/Downloads /clipboard /app:"C:\Windows\explorer.exe" What would be sweet is putting start.sh into /usr/local/bin and creating a desktop icon in the fedora-RDP qube, to pull these things up like they are in typical Qubes format. I will add more as I play around with this. Next will also be how to run a GPU for games.
  29. 1 point
    Amazing guide @buzzkillb just amazing, I will go through it fully when I have some more time!
  30. 1 point
  31. 1 point
  32. 1 point
    To connect to tor nodes. Look at the IP address of your sys-whonix in Qube Manager. Go into denarius.conf and put tor=10.137.0.x:9050 and now you might be connecting to any onion nodes. Replace that IP obviously with the correct one.
  33. 1 point
  34. 1 point
    Playing with using denariusd and tor in their own docker network. I am bypassing denariusd nativetor for some other reasons right now. denariusd:alpha is the test branch I am creating on docker hub using the latest denariusd wallet daemon. ~/.denarius/denarius.conf should be populated along with /etc/tor/torrc docker-compose.yml version: '3.2' services: tor: image: buzzkillb/tor:alpine container_name: tor networks: - tor_network volumes: - /etc/tor/torrc:/etc/tor/torrc restart: always denariusd: image: buzzkillb/denariusd:alpha container_name: denariusd volumes: - ~/.denarius:/data command: -debug=0 network_mode: service:tor depends_on: - tor restart: always networks: tor_network: external: true docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 48e24fa60efd buzzkillb/denariusd:alpha "denariusd --datadir…" 8 seconds ago Up 7 seconds denariusd 81119081a083 buzzkillb/tor:alpine "/bin/sh -c '/usr/bi…" 19 seconds ago Up 17 seconds 53/udp, 9050/tcp tor Connecting into the TOR nodes I have setup all over the place, something like this should appear in the denariusd logs. docker logs denariusd -f SetBestChain: new best=8499db50db63985aa0ad height=2235381 trust=14348364472433105438 blocktrust=1048577 date=08/03/19 15:48:36 SOCKS5 connected hrzdbqp4vjbohsvg.onion send version message: version 33500, blocks=2235381, us=tyfj5y64rlocawsb.onion:33369, them=hrzdbqp4vjbohsvg.onion:33369, peer=hrzdbqp4vjbohsvg.onion:33369 SetBestChain: new best=000000000019e5f675cb height=2235382 trust=14348373734367204915 blocktrust=9261934099477 date=08/03/19 15:48:44 SOCKS5 connecting 6nw6dekrzc2s5i2w.onion Once I get this working like I want, I will throw in a VPN connection.
  35. 1 point
    Staking Information in Denarius QT Wallet. First turn coin control on in the QT wallet. settings -> options -> Display tab Checkmark the Display coin control features (experts only!) and click OK. We can now see some more information if you go to the Send tab -> Inputs Browsing around that we can see whenever you send or receive Denarius coins, your inputs will change. Each input can be staked. Each input has its own coinage that increases its odds for staking. Go to the Staking tab for some more information for each input. In here we can sort by Transaction, Address, Balance, Age, Coinage, and Stake Probabilty. Now we have a better idea of when we will stake. In this example I left the Display staking probability within to 10minutes. I am always curious what will happen in the short term as I enjoy staking Denarius cryptocurrency.
  36. 1 point
    Not as elegant as I was hoping for, but this appears to work and be somewhat hands off.
  37. 1 point
    How to run a Fortunastake in Windows. At least 700mb of ram per FS and a fast hard drive if you plan to have a lot of these. I wouldnt suggest using Windows, and instead use Ubuntu 16.04 server. But crypto people have reasons. Download latest Windows QT Wallet or compile it yourself. Make a directory to put the wallet in. example: c:\denarius\denarius01.exe Create a .bat file to run the wallet. example c:\denarius\start01.bat Create a directory of your first FS. example c:\denarius\D01 start01.bat c:\denarius\denarius01.exe -datadir=c:\denarius\D01 Fill out the denarius.conf in the c:\denarius\D01 folder like usual. If you have conflicting port issues, easiest thing to do is add to denarius.conf listen=0 For IP address, use whatever you want. Also set externalip=THATADDRESS in this .conf file. They have to be proper IP's, but dont have to be connectable. Examples externalip= externalip=[2006:1] externalip=denarius.onion Wait for the wallet to sync and then start-alias from your hot wallet, hopefully on a separate PC. I hope you can see where this is headed by using a numbering scheme. Also using separate denarius.exe wallets makes this easier to track in task manager. But you can use a single denarius.exe and run a separate .bat calling that same denarius.exe over and over. Will add how to make these TOR onion nodes later.
  38. 1 point
    Denarius v3.3.7 -Fixed QT segfaults across all OSs -Fixed QT compiling across all OSs -Added @buzzkillb Ubuntu 16.04/18.04 Denarius QT installer bash script (denariusqtubuntu.sh) -Fixed Trade D link to https://www.coinexchange.io/market/D/BTC in QT -Updated Refresh button in QT -Fixed macOS compatibility/building Also includes everything from the previous versions, v3.3.6 release notes are below: -Tons of fixes, improvements, and stability updates -New Protocol 33500 -New Peers Tab in QT -New Denarius News in QT -Fortuna Stake Improvements Please update your wallet as soon as possible, as there are significant improvements to take advantage of! We recommend clearing your peers.dat when installing this update to improve your connection experience. Overview of previous version Fixed consensus issues in the FPS payment spread algorithm which were causing network de-syncs for some affected wallets. Due to excessive I/O during sync, stealth transaction scanning is now disabled by default when you have no stealth addresses in your wallet. If you have a stealth address already configured, scanning will occur. If you have stealth addresses, but don't care about them, stealth scanning can be manually disabled with the config option -disablestealth Fixed lag issues when syncing from 0 using wallets with large amounts of existing transactions. Added the peers table in the settings dialog. You may now check out your current peers and their ping-time and other stats in the GUI! Nodes should now also select the closest node by ping-time to sync with. Optimized the FortunaStake FPS blockchain scanning algorithm. Added queuing system to getblocks; the message handling thread will no longer wait in a lock for the message to be pushed to the peer. Users on slow connections should see some significant sync speed improvements. Tweaked wallet payment parameters - wallets will now choose to pay masternodes regardless of seeing their heartbeat. Some situations occured where a wallet did not receive a ping due to unreliable network circumstances, and would time out of people's lists. Improved start-up time, and introduced a loading indicator to the splash screen for long rescans. Fixed a possible segfault in the active FPS wallet which could cause the client to crash on heartbeat and refuse to become active until the txid is changed. Fixed another possible segfault while starting up. Cleaned up debug output Please note, linux binaries require the associated development libraries to be installed from the package manager: libboost-all-dev libminiupnpc-dev libevent-dev libdb++-dev -------------------------------------------------------------------------------------------------------------------------------------- Denarius-v3.3.7-Win64.zip Hashes SHA256 48ba0a1faef06be8782b000e181ed7cc19bd46fa3b0d39a8a826f92dbe64c764 MD5 8ca1c600eaef106a36d2146f8f86bf66 SHA-1 4dd38dd66a7c27b8f6e35e95ab1d6b6b71b2b987 Denarius.exe Hashes SHA256 2d36271560d448283bc39712e2ace64a1b21a2c3538580c101a20f8a2c6a43ba MD5 72c68308f762ed5cfb97663a27c5d1c0 SHA-1 8de3e5a87f58448bc240ca4088a9f73d218b5c12 Authentihash aa29fecf16852ba696fd361c6671d0d9e92ff3d30a74f47002e72592bc7bf638 Imphash 2852de0dcb5e0559e5231e10136fad4b Denarius-v3.3.7-macOS.dmg Hashes SHA256 683ed887479beab00254d53e95ce4d8779d617d2a45532522fffc28c5381f869 MD5 11ae922f86f487ec039215a3b8340096 SHA-1 63066c793718fe392b34fb6df618a34bbe7be644 denariusd-v337-ubuntu1604.tar.gz Hashes SHA256 e1f44f94de8d85c0f5fa5a2138b91b4ad695d925c269900815700625028ffd84 MD5 fc16dc11a21d62a85f499ff2482b85ad SHA-1 f1e84c3d0e712e6ac616480a09854333dc3e3d96 Get the latest release from here: https://github.com/carsenk/denarius/releases/tag/v3.3.7 As always you can git pull our master branch for the latest v3.3.7
  39. 1 point
    Jealous af, room is awesome. Fantastic job.
  40. 1 point
    Please keep it in Tribus - FPGAs aren't enemy as ASICS.
  41. 1 point
    To change fonts I will use Denarius official font selection of Open Sans - Semibold. Go to https://github.com/google/fonts/tree/master/apache/opensans And download https://github.com/google/fonts/blob/master/apache/opensans/OpenSans-SemiBold.ttf I send files to the PI3 using winscp, and made a directory called fonts to store these. Or you could cd ~ mkdir fonts cd fonts wget https://github.com/google/fonts/blob/master/apache/opensans/OpenSans-SemiBold.ttf cd ~ If your original line looks like this font = ImageFont.truetype(FredokaOne, 20) Change to the new font. font = ImageFont.truetype("/home/pi/fonts/OpenSans-SemiBold.ttf", 20)
  42. 1 point
    One last one pulling stats from coinpaprika API. The idea is I have changed a thing or two each go around. This pulls the high, low, volume, and for some reason missing marketcap in $USD terms with one of the D logos from the visual guide, https://github.com/carsenk/denarius/wiki/Denarius-Visual-Guide dprice.py #!/usr/bin/env python # -*- coding: utf-8 -*- import urllib, json from inky import InkyPHAT inky_display = InkyPHAT("yellow") inky_display.set_border(inky_display.YELLOW) from PIL import Image, ImageFont, ImageDraw print("""Inky pHAT: Denarius Price information. """) img = Image.new("P", (inky_display.WIDTH, inky_display.HEIGHT)) draw = ImageDraw.Draw(img) from font_fredoka_one import FredokaOne font = ImageFont.truetype(FredokaOne, 22) url = "https://api.coinpaprika.com/v1/coins/d-denarius/ohlcv/latest" response = urllib.urlopen(url) data = json.loads(response.read()) dhigh = data[0]['high'] dlow = data[0]['low'] dvol = data[0]['volume'] dmc = data[0]['market_cap'] denariusprice = ("$ " + str(dhigh) + '\n' + "$ " + str(dlow) + '\n' + "$ " + str(dvol) + '\n' + "$ " + '\n' + str(dmc)) # Load our backdrop image img = Image.open("/home/pi/d-logo.png") draw = ImageDraw.Draw(img) #img = Image.open("/home/pi/btc_yellow.png") draw.text((10, 0), denariusprice, inky_display.BLACK, font) inky_display.set_image(img) inky_display.show() included png for Denarius logo
  43. 1 point
    How to compile denariusd daemon on Raspberry Pi3 in Raspbian and run TOR. Headless Install (enable wifi and enable ssh) https://desertbot.io/blog/headless-raspberry-pi-3-bplus-ssh-wifi-setup Swap Space (Required for Compiling) https://www.bitpi.co/2015/02/11/how-to-change-raspberry-pis-swapfile-size-on-rasbian/ sudo sed -i 's/CONF_SWAPSIZE=100/CONF_SWAPSIZE=2048/' /etc/dphys-swapfile sudo /etc/init.d/dphys-swapfile stop sudo /etc/init.d/dphys-swapfile start free -m On dependencies read a few posts below if you want to compile and use berkeley database 4.8 to keep backwards compatibility. sudo apt-get update -y && sudo apt-get upgrade -y sudo apt-get --assume-yes install git unzip build-essential libdb++-dev libboost-all-dev libqrencode-dev libminiupnpc-dev libgmp-dev libevent-dev autogen automake libtool Compile and replace openssl to openssl 1.0.1j. (may or may not be required) I need to double check if there was 1 more step to this or not to make sure openssl is right. apt-get install make wget https://www.openssl.org/source/openssl-1.0.1j.tar.gz tar -xzvf openssl-1.0.1j.tar.gz cd openssl-1.0.1j ./config make depend make #make test make install sudo ln -sf /usr/local/ssl/bin/openssl `which openssl cd ~ openssl version -v Git clone v3.4 branch to get v3.3.8. git clone https://github.com/carsenk/denarius cd denarius git checkout v3.4 git pull cd src OPENSSL_INCLUDE_PATH=/usr/local/ssl/include OPENSSL_LIB_PATH=/usr/local/ssl/lib make -f makefile.arm strip denariusd sudo cp denariusd /usr/local/bin/denariusd #Use Chaindata cd ~ mkdir ~/.denarius wget https://github.com/carsenk/denarius/releases/download/v3.3.6/chaindata1612994.zip unzip chaindata1612994.zip #Install TOR service sudo apt-get install tor sudo nano /etc/tor/torrc Find this line and change the 2 #HiddenServiceDir /var/lib/tor/hidden_service/ #HiddenServicePort 80 HiddenServiceDir /var/lib/tor/hidden_service/ HiddenServicePort 33369 sudo service tor restart #To get onion address sudo cat /var/lib/tor/hidden_service/hostname example from above favlp6mro3bh5jnt.onion #sample TOR and clearnet denarius.conf rpcuser=denariusrpc rpcpassword=STRONGPASSWORD rpcallowip= daemon=1 tor= listen=1 externalip=favlp6mro3bh5jnt.onion discover=1
  44. 1 point
    stage 3, qt wallet place hodler #02-denariusqt folder layout #wallpaper pi-gen/stage3/02-denariusqt/files/Lava-PI-2.jpg nano 00-packages libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools qt5-default nano 05-run.sh Throw in custom denarius lava pi by icanhaz and setup the Denarius QT compile. After compile copy Denarius binary to user pi desktop. #!/bin/bash -e install -m 644 files/Lava-PI-2.jpg "{ROOTFS_DIR}/usr/share/rpd-wallpaper/" on_chroot << EOF cd denarius export QT_SELECT=qt5 qmake -v qmake "USE_NATIVETOR=-" "USE_UPNP=1" "USE_QRCODE=1" OPENSSL_INCLUDE_PATH=/usr/local/ssl/include OPENSSL_LIB_PATH=/usr/local/ssl/lib denarius-qt.pro make cp Denarius /home/pi/Desktop/Denarius EOF chmod +x 05-run.sh
  45. 1 point
    adding script I am working on for both daemon and QT https://github.com/buzzkillb/denarius-pi3
  46. 1 point
  47. 1 point
    While mining D with your GPU's, why not spare the wasted cpu and mine Grin? Duplicate your D tribus Flight Sheet. Edit the duplicated D tribus Flight Sheet. This won't be named so its easy to find it. Give this a name. Like Denarius Grin. And then click Add Miner. Select Coin-> Grin. Select Wallet -> Grin Wallet. Select Pool -> grinmint. Select your closest Pool server. Select Miner -> Grin Miner. Then Setup Miner Config. Leave the defaults in and give your grinmint wallet a password. Example don't use this, 1234567890 and copy and paste the below into the Plugin and device configs box. nThreads = 4, is how many CPU cores you have. [[mining.miner_plugin_config]] plugin_name = "cuckaroo_cpu_compat_29" [mining.miner_plugin_config.parameters] nthreads = 4 Apply Changes, and then click update. Click the rocket ship to start the dual mining. Denarius/Tribus will start first on the GPU's. Give it a bit of time for the Grin CPU miner to get going. Check your denarius and grin pools. Grin uses email as your pool address. You will need that strong password from the pass box above, to move the Grin out of their to damp eet. https://mining.cafe https://grinmint.com
  48. 1 point
    Use Hive Shell to Update Nvidia Drivers. Expect this to take 30+ minutes on a USB install. https://forum.hiveos.farm/t/nvidia-drivers-update-guide-and-cuda-10/10921 Select Remote Access -> Hive Shell Start Select Hive Shell and click the Web Link. Type in nvidia-driver-update at the command prompt. nvidia-driver-update Getting the latest Nvidia Drivers from HiveOS. Once this finishes you will get a prompt to reboot. Go back to your other tab, hit the Power button -> Reboot. Say hello to the latest drivers. If you went from Cuda 9.2 to Cuda 10.0, don't forget to redo your miner to correct Cuda version.
  49. 1 point
    3.3.7 is running nice and smooth, finally!! 😍
  50. 1 point
    Hi, have some trouble with buildig qt-wallet. (Ubuntu 16.04 64): After "make" I receive the following Errormessage: .src/tor/address.h: In function ‘tor_addr_to_mapped_ipv4h’: src/tor/torcompat.h:548:37: error: ‘const struct in6_addr’ has no member named ‘s6_addr32’ #define S6_ADDR32(x) ((uint32_t*)(x).s6_addr32) ^ src/tor/address.h:126:35: note: in expansion of macro ‘S6_ADDR32’ #define tor_addr_to_in6_addr32(x) S6_ADDR32(*tor_addr_to_in6_assert(x)) ^ src/tor/address.h:153:14: note: in expansion of macro ‘tor_addr_to_in6_addr32’ addr32 = tor_addr_to_in6_addr32(a); ^ Makefile:8626: die Regel für Ziel „build/hs_cache.o“ scheiterte make: *** [build/hs_cache.o] Fehler 1 Can someone help?
  • Create New...