QT cross compile to ARM · Issue #13495 · bitcoin/bitcoin ...

Reddcoin (RDD) 02/20 Progress Report - Core Wallet v3.1 Evolution & PoSV v2 - Commits & More Commits to v3.1! (Bitcoin Core 0.10, MacOS Catalina, QT Enhanced Speed and Security and more!)

Reddcoin (RDD) Core Dev Team Informal Progress Report, Feb 2020 - As any blockchain or software expert will confirm, the hardest part of making successful progress in blockchain and crypto is invisible to most users. As developers, the Reddcoin Core team relies on internal experts like John Nash, contributors offering their own code improvements to our repos (which we would love to see more of!) and especially upstream commits from experts working on open source projects like Bitcoin itself. We'd like tothank each and everyone who's hard work has contributed to this progress.
As part of Reddcoin's evolution, and in order to include required security fixes, speed improvements that are long overdue, the team has up to this point incorporated the following code commits since our last v3.0.1 public release. In attempting to solve the relatively minor font display issue with MacOS Catalina, we uncovered a complicated interweaving of updates between Reddcoin Core, QT software, MacOS SDK, Bitcoin Core and related libraries and dependencies that mandated we take a holistic approach to both solve the Catalina display problem, but in doing so, prepare a more streamlined overall build and test system, allowing the team to roll out more frequent and more secure updates in the future. And also to include some badly needed fixes in the current version of Core, which we have tentatively labeled Reddcoin Core Wallet v3.1.
Note: As indicated below, v3.1 is NOT YET AVAILABLE FOR DOWNLOAD BY PUBLIC. We wil advise when it is.
The new v3.1 version should be ready for internal QA and build testing by the end of this week, with luck, and will be turned over to the public shortly thereafter once testing has proven no unexpected issues have been introduced. We know the delay has been a bit extended for our ReddHead MacOS Catalina stakers, and we hope to have them all aboard soon. We have moved with all possible speed while attempting to incorproate all the required work, testing, and ensuring security and safety for our ReddHeads.
Which leads us to: PoSV v2 activation and the supermajority on Mainnet at the time of this writing has reached 5625/9000 blocks or 62.5%. We have progressed quite well and without any reported user issues since release, but we need all of the community to participate! This activation, much like the funding mechanisms currently being debated by BCH and others, and employed by DASH, will mean not only a catalyst for Reddcoin but ensure it's future by providing funding for the dev team. As a personal plea from the team, please help us support the PoSV v2 activation by staking your RDD, no matter how large or small your amount of stake.
Every block and every RDD counts, and if you don't know how, we'll teach you! Live chat is fun as well as providing tech support you can trust from devs and community ReddHead members. Join us today in staking and online and collect some RDD "rain" from users and devs alike!
If you're holding Reddcoin and not staking, or you haven't upgraded your v2.x wallet to v3.0.1 (current release), we need you to help achieve consensus and activate PoSV v2! For details, see the pinned message here or our website or medium channel. Upgrade is simple and takes moments; if you're nervous or unsure, we're here to help live in Telegram or Discord, as well as other chat programs. See our website for links.
Look for more updates shortly as our long-anticipated Reddcoin Payment Gateway and Merchant Services API come online with point-of-sale support, as we announce the cross-crypto-project Aussie firefighter fundraiser program, as well as a comprehensive update to our development roadmap and more.
Work has restarted on ReddID and multiple initiatives are underway to begin educating and sharing information about ReddID, what it is, and how to use it, as we approach a releasable ReddID product. We enthusiastically encourage anyone interested in working to bring these efforts to life, whether writers, UX/UI experts, big data analysts, graphic artists, coders, front-end, back-end, AI, DevOps, the Reddcoin Core dev team is growing, and there's more opportunity and work than ever!
Bring your talents to a community and dev team that truly appreciates it, and share the Reddcoin Love!
And now, lots of commits. As v3.1 is not yet quite ready for public release, these commits have not been pushed publicly, but in the interests of sharing progress transparently, and including our ReddHead community in the process, see below for mind-numbing technical detail of work accomplished.
e5c143404 - - 2014-08-07 - Ross Nicoll - Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope. *99a7dba2e - - 2014-08-15 - Cory Fields - tests: fix test-runner for osx. Closes ##4708 *8c667f1be - - 2014-08-15 - Cory Fields - build: add funcs.mk to the list of meta-depends *bcc1b2b2f - - 2014-08-15 - Cory Fields - depends: fix shasum on osx < 10.9 *54dac77d1 - - 2014-08-18 - Cory Fields - build: add option for reducing exports (v2) *6fb9611c0 - - 2014-08-16 - randy-waterhouse - build : fix CPPFLAGS for libbitcoin_cli *9958cc923 - - 2014-08-16 - randy-waterhouse - build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix. *342aa98ea - - 2014-08-07 - Cory Fields - build: fix automake warnings about the use of INCLUDES *46db8ad51 - - 2020-02-18 - John Nash - build: add build.h to the correct target *a24de1e4c - - 2014-11-26 - Pavel Janík - Use complete path to include bitcoin-config.h. *fd8f506e5 - - 2014-08-04 - Wladimir J. van der Laan - qt: Demote ReportInvalidCertificate message to qDebug *f12aaf3b1 - - 2020-02-17 - John Nash - build: QT5 compiled with fPIC require fPIC to be enabled, fPIE is not enough *7a991b37e - - 2014-08-12 - Wladimir J. van der Laan - build: check for sys/prctl.h in the proper way *2cfa63a48 - - 2014-08-11 - Wladimir J. van der Laan - build: Add mention of --disable-wallet to bdb48 error messages *9aa580f04 - - 2014-07-23 - Cory Fields - depends: add shared dependency builder *8853d4645 - - 2014-08-08 - Philip Kaufmann - [Qt] move SubstituteFonts() above ToolTipToRichTextFilter *0c98e21db - - 2014-08-02 - Ross Nicoll - URLs containing a / after the address no longer cause parsing errors. *7baa77731 - - 2014-08-07 - ntrgn - Fixes ignored qt 4.8 codecs path on windows when configuring with --with-qt-libdir *2a3df4617 - - 2014-08-06 - Cory Fields - qt: fix unicode character display on osx when building with 10.7 sdk *71a36303d - - 2014-08-04 - Cory Fields - build: fix race in 'make deploy' for windows *077295498 - - 2014-08-04 - Cory Fields - build: Fix 'make deploy' when binaries haven't been built yet *ffdcc4d7d - - 2014-08-04 - Cory Fields - build: hook up qt translations for static osx packaging *25a7e9c90 - - 2014-08-04 - Cory Fields - build: add --with-qt-translationdir to configure for use with static qt *11cfcef37 - - 2014-08-04 - Cory Fields - build: teach macdeploy the -translations-dir argument, for use with static qt *4c4ae35b1 - - 2014-07-23 - Cory Fields - build: Find the proper xcb/pcre dependencies *942e77dd2 - - 2014-08-06 - Cory Fields - build: silence mingw fpic warning spew *e73e2b834 - - 2014-06-27 - Huang Le - Use async name resolving to improve net thread responsiveness *c88e76e8e - - 2014-07-23 - Cory Fields - build: don't let libtool insert rpath into binaries *18e14e11c - - 2014-08-05 - ntrgn - build: Fix windows configure when using --with-qt-libdir *bb92d65c4 - - 2014-07-31 - Cory Fields - test: don't let the port number exceed the legal range *62b95290a - - 2014-06-18 - Cory Fields - test: redirect comparison tool output to stdout *cefe447e9 - - 2014-07-22 - Cory Fields - gitian: remove unneeded option after last commit *9347402ca - - 2014-07-21 - Cory Fields - build: fix broken boost chrono check on some platforms *c9ed039cf - - 2014-06-03 - Cory Fields - build: fix whitespace in pkg-config variable *3bcc5ad37 - - 2014-06-03 - Cory Fields - build: allow linux and osx to build against static qt5 *01a44ba90 - - 2014-07-17 - Cory Fields - build: silence false errors during make clean *d1fbf7ba2 - - 2014-07-08 - Cory Fields - build: fix win32 static linking after libtool merge *005ae2fa4 - - 2014-07-08 - Cory Fields - build: re-add AM_LDFLAGS where it's overridden *37043076d - - 2014-07-02 - Wladimir J. van der Laan - Fix the Qt5 build after d95ba75 *f3b4bbf40 - - 2014-07-01 - Wladimir J. van der Laan - qt: Change serious messages from qDebug to qWarning *f4706f753 - - 2014-07-01 - Wladimir J. van der Laan - qt: Log messages with type>QtDebugMsg as non-debug *98e85fa1f - - 2014-06-06 - Pieter Wuille - libsecp256k1 integration *5f1f2e226 - - 2020-02-17 - John Nash - Merge branch 'switch_verification_code' into Build *1f30416c9 - - 2014-02-07 - Pieter Wuille - Also switch the (unused) verification code to low-s instead of even-s. *1c093d55e - - 2014-06-06 - Cory Fields - secp256k1: Add build-side changes for libsecp256k1 *7f3114484 - - 2014-06-06 - Cory Fields - secp256k1: add libtool as a dependency *2531f9299 - - 2020-02-17 - John Nash - Move network-time related functions to timedata.cpp/h *d003e4c57 - - 2020-02-16 - John Nash - build: fix build weirdness after 54372482. *7035f5034 - - 2020-02-16 - John Nash - Add ::OUTPUT_SIZE *2a864c4d8 - - 2014-06-09 - Cory Fields - crypto: create a separate lib for crypto functions *03a4e4c70 - - 2014-06-09 - Cory Fields - crypto: explicitly check for byte read/write functions *a78462a2a - - 2014-06-09 - Cory Fields - build: move bitcoin-config.h to its own directory *a885721c4 - - 2014-05-31 - Pieter Wuille - Extend and move all crypto tests to crypto_tests.cpp *5f308f528 - - 2014-05-03 - Pieter Wuille - Move {Read,Write}{LE,BE}{32,64} to common.h and use builtins if possible *0161cc426 - - 2014-05-01 - Pieter Wuille - Add built-in RIPEMD-160 implementation *deefc27c0 - - 2014-04-28 - Pieter Wuille - Move crypto implementations to src/crypto/ *d6a12182b - - 2014-04-28 - Pieter Wuille - Add built-in SHA-1 implementation. *c3c4f9f2e - - 2014-04-27 - Pieter Wuille - Switch miner.cpp to use sha2 instead of OpenSSL. *b6ed6def9 - - 2014-04-28 - Pieter Wuille - Remove getwork() RPC call *0a09c1c60 - - 2014-04-26 - Pieter Wuille - Switch script.cpp and hash.cpp to use sha2.cpp instead of OpenSSL. *8ed091692 - - 2014-04-20 - Pieter Wuille - Add a built-in SHA256/SHA512 implementation. *0c4c99b3f - - 2014-06-21 - Philip Kaufmann - small cleanup in src/compat .h and .cpp *ab1369745 - - 2014-06-13 - Cory Fields - sanity: hook up sanity checks *f598c67e0 - - 2014-06-13 - Cory Fields - sanity: add libc/stdlib sanity checks *b241b3e13 - - 2014-06-13 - Cory Fields - sanity: autoconf check for sys/select.h *cad980a4f - - 2019-07-03 - John Nash - build: Add a top-level forwarding target for src/ objects *f4533ee1c - - 2019-07-03 - John Nash - build: qt: split locale resources. Fixes non-deterministic distcheck *4a0e46e76 - - 2019-06-29 - John Nash - build: fix version dependency *2f61699d9 - - 2019-06-29 - John Nash - build: quit abusing AMCPPFLAGS *99b60ba49 - - 2019-06-29 - John Nash - build: avoid the use of top and abs_ dir paths *c8f673d5d - - 2019-06-29 - John Nash - build: Tidy up file generation output *5318bce57 - - 2019-06-29 - John Nash - build: nuke Makefile.include from orbit *672a25349 - - 2019-06-29 - John Nash - build: add stub makefiles for easier subdir builds *562b7c5a6 - - 2020-02-08 - John Nash - build: delete old Makefile.am's *066120079 - - 2020-02-08 - John Nash - build: Switch to non-recursive make
Whew! No wonder it's taken the dev team a while! :)
TL;DR: Trying to fix MacOS Catalina font display led to requiring all kinds of work to migrate and evolve the Reddcoin Core software with Apple, Bitcoin and QT components. Lots of work done, v3.1 public release soon. Also other exciting things and ReddID back under active dev effort.
submitted by TechAdept to reddCoin [link] [comments]

#Reddcoin ($RDD) Core Wallet Release 3.0.1 - PosV v2 SuperMajority Consensus Upgrade at 45.6% - Required Upgrade

Reddcoin (RDD) Core Wallet v3.0.1 - January 09, 2020
Version 3.0.1 is the official release version of Reddcoin Core. It is available for download at Reddcoin Core's Github repository here: https://github.com/reddcoin-project/reddcoin/releases/tag/v3.0.1
This release features PoSV v2.supermajority activation and new staking ruleset (and minor misc fixes). v3.0.1 is still not yet MacOS Catalina compatible. We are still working and should have that fix issued very soon. Sincere apologies to our Mac-using ReddHeads.
It is particularly important that all users upgrade, as once PoSV v2 is enforced, version 4 blocks will be rejected from the network entirely.
Therefore v3.0.1 is a "strongly recommended" update for all users. Note: If you have already installed v3.0.0, this upgrade is not required. If you have not yet upgraded from v2.0.x or earlier, this is a REQUIRED upgrade. Please install the newest version v3.0.1 to avoid losing functionality during supermajority activation of PoSV v2.
Reddcoin Core version 3.0.1 is now available from: https://github.com/reddcoin-project/reddcoin/releases Release Notes are available here and replicated below in this announcement: https://github.com/reddcoin-project/reddcoin/blob/mastedoc/release-notes.md
This is a new major version release of Reddcoin.
Previously, the original and subsequent versions of Reddcoin were taken from a fork of the Litecoin code base.
With the release of Reddcoin V2.0.0, the code was based directly from a fork of Bitcoin. This allows for better source control and feature implementation from upstream changes into the future
With the release of Reddcoin V3.0.0, the PoSV stake reward has been improved to allow for a target 5% network growth, in process re-incentivizing individual network stakers and providing for integrated dev support.
Upgrading to this release is strongly recommended and required for continued operation. Once a supermajority of 90% is reached, old wallets will no longer accept the new v5 blocks.
Please report bugs using the issue tracker at github:
How to Upgrade
If you are running an older version of Reddcoin, shut it down. Wait until it has completely shut down (which may take a few minutes for older versions). Run the installer (on Windows) or just copy over /Applications/Reddcoin-Qt (on Mac) or reddcoind/reddcoin-qt (on Linux).
Start wallet. All done!
Reddcoin v3.0.0 introduced an updated PoSV method to better distribute staking rewards and target a overall 5% network growth. Staking and relay policy enhancements 
To implement PoSV v2, Reddcoin Core's block templates are now for version 5 blocks only. When PoSV v2 consensus (Supermajority 9000/10000) is reached, only v5 blocks will be accepted by the network.This equates to approximately 90% of blocks being generated over 1 week period. Status at any time may be viewed in node debug.log
Blockchain Download:
Blockchain data for both testnet and mainnet along with instructions can be downloaded from github. https://github.com/reddcoin-project/bootstrap_files
3.0.1 changelog
*83e212838 - John Nash, 2020-01-09 : really delete these files *3a1458ecd - Oliver Webb, 2020-01-08 : Added missing dependency libminiupnpc-dev for Jessie *d21915431 - Tiago Peralta, 2019-06-21 : Add vout to listtransactions/gettransaction *8d58ea7cf - Oliver Webb, 2020-01-08 : Script for downloading pre compiled binaries for Raspbian Jessie, Stretch or Buster *d4eced1bc - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_stretch.sh *c5e9f91cf - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_jessie.sh *5d5771b00 - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_buster.sh *75c6ae91b - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *54c501787 - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *acb30a2b6 - Oliver Webb, 2020-01-05 : script files for Raspbian Jessie (also Stakebox) *cfddbe594 - John Nash, 2020-01-05 : Update copyright year and version *e46e5e7de - John Nash, 2020-01-05 : download script for pre compiled wallet *37386790a - John Nash, 2020-01-05 : change libssl deb packages links to github *9dbc772e6 - Oliver Webb, 2020-01-03 : download script for pre compiled wallet *857d697fd - Oliver Webb, 2020-01-03 : change libssl deb packages links to github *2cb74b9a8 - John Nash, 2019-12-31 : update copyright year *c641a1ab3 - Oliver Webb, 2019-12-30 : Raspberry Pi build script files for v3 wallet *a3f21a4a4 - John Nash, 2019-12-30 : add install script for building db4 update instructions for unix, osx, arm building using the db4 install script *5f6299b2a - John Nash, 2019-12-28 : docs: Update build notes for arm processors *465716c01 - John Nash, 2019-12-28 : test for arm devices *3fec3a535 - John Nash, 2018-02-02 : build: update source paths *5f6031ab4 - John Nash, 2019-12-28 : Scrypt n=1024 Pow hash based upon Colin Percival's Tarnsnap (2009) Modified by Artforz, coblee, pooler, wtogami, Nikolay Belikov, reddink *2fd4d91a0 - John Nash, 2019-12-24 : update copyright year *326828b36 - John Nash, 2019-12-24 : set release state true *8ebede0a6 - John Nash, 2019-12-24 : release notes *36df6fdfb - John Nash, 2019-12-23 : add check explictly for v5 blocks or greater *874dc1f0c - John Nash, 2019-12-17 : remove hardcoded global variable rearrange debug log output *763b25db8 - John Nash, 2019-12-17 : move copyright to new line *536baf635 - John Nash, 2019-12-17 : update version and set release state to false *cde9009f3 - John Nash, 2019-12-17 : update copyright year *ae41b7ed3 - John Nash, 2019-12-17 : set isSuperMajority to 90% for mainnet *e43e1c8ed - John Nash, 2019-12-10 : additional logging to verify isSuperMajority in the debug.log output *e31783cac - John Nash, 2019-12-05 : add/update public key for mainnet *405c6f002 - John Nash, 2019-12-05 : add log output for current inflation rate *9cc43c3f7 - John Nash, 2019-12-02 : determine calculated stake based on posv version *7baa3bf75 - John Nash, 2019-11-25 : check the posv transaction for correct pubkey *9ffa7ca38 - John Nash, 2019-11-21 : check for posv v1 or posv v2 blocks when calculating stake reward *39f7aad68 - John Nash, 2019-11-14 : add logging *0e283e6c3 - John Nash, 2019-11-13 : correct maths *74cbdeffd - John Nash, 2019-11-11 : use new posv v2 functions addidtional logging *35d7413b5 - John Nash, 2019-11-11 : add new proofofstakereward *3d917216c - John Nash, 2019-11-11 : get inflation adjustment *f63d17443 - John Nash, 2019-11-08 : add the developer output split fund output *ca263c9c9 - John Nash, 2019-11-05 : add dev key to chainparams *df6996ab0 - John Nash, 2019-11-05 : add block version checking *14b663479 - John Nash, 2019-11-05 : increase block version
Thanks to everyone who contributed to coding, testing and feedback for this release, notably:
@cryptognasher @techadept @chris @cryptobuze @harmonyq @mindredder @paxtech @Tiago Peralta 
Stake on!!
-Reddcoin (RDD) Core Development Team
submitted by TechAdept to reddCoin [link] [comments]

How to get Energi Wallet running on Raspberry Pi 4

How to get Energi Wallet running on Raspberry Pi 4
I'm new to the Raspberry Pi and trying to get the NRG Core Cryptocurrency wallet running on my Raspberry. Finally I was able to compile the files after this commands:
Download and install the newest updates sudo apt-get update && sudo apt-get upgrade
Install the following major dependencies packages sudo apt-get install git build-essential libtool autotools-dev autoconf pkg-config libssl-dev libcrypto++-dev libevent-dev libminiupnpc-dev libgmp-dev libboost-all-dev devscripts libdb++-dev libsodium-dev
Install the following QT dependencies packages sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libcrypto++-dev libminiupnpc-dev qt5-default
Install bitcoin PPA files cd /etc/apt/sources.list.d/
sudo nano bitcoin.list
Add this line to the file: deb-src http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu artful main
Close file
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv C70EF1F0305A1ADB9986DBD8D46F45428842CE5E
sudo apt-get update
Clone Github cd git clone https://github.com/energicryptocurrency/energi.git
Install Libdb4.8 Libdb4.8-dev Libdb++ Libdb4.8++-dev
Compile the wallet cd energi ./autogen.sh ./configure --with-boost-libdir=/uslib/arm-linux-gnueabihf make sudo make install
After compiling I see the files in /uslocal/bin
No I need to know how to use this files? Can someone help me please?
submitted by FCU4ever to energicryptocurrency [link] [comments]

Groestlcoin 6th Anniversary Release


Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.

Other Linux



Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here


ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.





ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.



Main Release (Main Net)
Testnet Release


ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.


Live Version (Not Recommended)





ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).






ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).




Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.


Remastered Improvements



ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.



Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 


ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.



Linux / OSX (Instructions)


UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.



Main Net
Main Net (FDroid)
Test Net


UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.




UPDATED – P2Pool Test Net



Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/


submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

[IDEA] [PROPOSAL] Monero Debian (deb) packages / Debian package repository deb.getmonero.org (I can do)

I have the skills to implement this if wanted.
Possible User Experience
This is a proposal, i.e. not implemented yet. Instructions for users, simplified.
How to install monero using apt-get
Download the repository signing key.
wget https://www.getmonero.org/monero.asc
Add the signing key.
sudo apt-key --keyring /etc/apt/trusted.gpg.d/monero.gpg add ~/monero.asc
Add APT repository.
echo "deb https://deb.getmonero.org buster main" | sudo tee /etc/apt/sources.list.d/monero.list
Update your package lists.
sudo apt-get update
Install monero.
sudo apt-get install monero
A few technical implementation details
I would simply grab the binaries provided by getmonero.org, download them, check software (gpg) signatures, put these into deb packages, add these to a repository, and upload the repository.
What I would not do is creating the binaries during package creation. While this is nice to have, it doesn't help user experience and blocks the progress on reaching this goal. See next chapter.
Why simply put the pre-build Monero binaries into a deb package?
1) After bitcoin existing for more than 10 years, being popular and being in Debian unstable (sid) it still never made its way into Debian testing, let alone stable. Reason being explained that a difference in underlying libraries (even just security fixes) during compilation may result in a network split. Binaries compiled during packaging on different versions of Linux distributions might have different libraries that might cause a network fork / chain split.
(Note: above website saying Tags: fixed-upstream is probably a mistake as discussion at bottom says.)
2) The github issue of packaging monero stalled.
3) By shipping the same binaries as provided by getmonero.org reduces the chances of introducing a backdoor.
Many Options
Doable quickly. The electrum (bitcoin) AppImage was recently added to a Debian package (binaries-freedom) by me and is now easily installable in Whonix. Pre-installed in testers version of Whonix already.
About Me
I am the founder of Whonix, which I am maintaining at present for more than 7 years.
Whonix (formerly TorBOX) is a Debian GNU/Linux–based security-focused Linux distribution. It aims to provide privacy, security and anonymity on the internet.
You can see an overview of packages I am maintaining on my github profile.
To proof that this forum account adrelanos corresponds the same person maintaining whonix.org, it is added here.
What happened to, what is the successor of the forum funding system?
submitted by adrelanos to Monero [link] [comments]

[Lightning] I didn't believe it until I saw it

Moderately long post, tl;dr at the bottom.
I've seen lightning transaction gifs and videos over and over. Today, I decided to fire up a lightning node on my laptop and give it a shot.
I followed this walk-through for mac (I adapted it to Arch Linux) for setting up Bitcoin TestNet Node with Eclair Lightning (it's practically the same as Mac, except for the installation process). Running on Arch caused the problem of accidentally installing the latest dev version of Bitcoin Core (AUR:bitcoin-git) - also had some compilation issues because upstream moved some files and this hadn't been updated in the PKGBUILD.
The latest dev version of Bitcoin Core included the SegWit address generation by default, which was very nice, didn't have any bugs using it in the brief period I used it.
After a couple of hours of syncing the TestNet blocks on my laptop, I started up Eclair and got Eclair and Bitcoin Core connected (had to use bitcoin-qt --deprecatedrpc=addwitnessaddressbecuase Eclair calls a soon-to-be deprecated function), sent myself some tBTC, and started opening up channels. Once I had about 3 channels open, I went to everyone's favorite online coffee shop and rewarded myself with some imaginary coffee.
My mind was absolutely blown at how fast the transaction went through and how insanely low the fees were (10 sat).
I went to test a transaction with a couple more hops, bought myself an imaginary 100eur Steam voucher, paid 100 sat in fees, near instant transaction (my Eclair client took a couple seconds to find a route to bitrefill)
Lightning truly is an incredible addition to Bitcoin, big things are coming.
tl;dr - Saw a couple lightning transaction videos and gifs, didn't really sink in how amazing this really is, decided to give it a shot on linux, mind=blown
Edit: I've done a little further testing and noticed that Eclair doesn't warn you if you're opening a duplicate channel (open a second channel with the same node)
submitted by Kill3rism to Bitcoin [link] [comments]

Reddcoin on Raspberry Pi

A lot of user asked lately, how to run Reddcoin on the popular Raspberry Pi platform. Raspberry Pi is a cheap ARM computer (using junk leftover chips with 10 year lag in technology) but it has enough RAM and consumes around 5 watts, so its ideal to use it for Reddcoin Staking.
This tutorial is not from me, i take NO RESPONSIBILITY about these binaries or the accuracy. This tutorial is created by cryptoBUZE, a fellow member of the Reddcoin community.
Before attempting to follow this tutorial, do a sudo apt-get update
The following commands must be run to install dependencies:
sudo apt-get install libboost-thread-dev
sudo apt-get install libboost-program-options-dev
sudo apt-get install libboost-filesystem-dev
sudo apt-get install libboost-system-dev
Download and install older libssl version - bitcoin clones are using this glorious and fantastic communist product of openssl so it naturally does not works. Its getting totally incompatible after each relase even with itself. Therefore, you must install this, which is the compatible one with the wallet software (no, you cant even compile the code with the newer one) :
wget http://apt.screenlyapp.com/raspbian/pool/main/o/openssl/libssl1.0.0_1.0.1t-1%2Bdeb8u6_armhf.deb
wget http://apt.screenlyapp.com/raspbian/pool/main/o/openssl/libssl-dev_1.0.1t-1%2Bdeb8u6_armhf.deb
sudo dpkg -i libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb
sudo dpkg -i libssl-dev_1.0.1t-1+deb8u6_armhf.deb
Download the wallet software itself:
wget https://github.com/cryptoBUZE/reddcoin/releases/download/raspberrypi/reddcoind
wget https://github.com/cryptoBUZE/reddcoin/releases/download/raspberrypi/reddcoin-cli
wget https://github.com/cryptoBUZE/reddcoin/releases/download/raspberrypi/reddcoin-qt
chmod +x reddcoin\*
When speaking about compatibility, ARM is similar to x86 if you are running user mode applications. You know that every arm based chip needs a different kernel due to the lack of an unified IO system thankfully for the glorious clueless egoistic communist developers at ARM, who succesfully bankrupted the corporation after 25 or so years, and the company got acquired by the japanese softbank. But in user mode, its sort of backward compatible if you have all the proper libraries installed. This means that this will run on any other newer ARM based machine as well (not just raspberry pi-s, on every other arm stuff, chromebooks, or android phones hacked to work with linux).
submitted by GeriGeriGeri to reddCoin [link] [comments]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B


This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
The updates
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.






This video shows how long it takes to start Reddcoin Core.   TL;DR:


Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  


Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

Build Updates #610 and #611: More UI polishing. Updating action toolbar.

More UI polishing.
The previous ones that returned an error have most likely been fixed and compiled again in LLUV.
Considering the master builds are complete, this UI polishing is just the finishing touches!
EDIT: Another UI update Build #612. What it looks like is that code is being posted on the test net so that some of the lower coders can optimize the UI code. All pretty easy for anyone that is versed in the programming language. The main coder Hoyt is getting the code together and structured so that another coder can come in and optimize.
The code doesn't need to be successful. The master builds are set and they are just finishing the framework for the UI for Wraith.
EDIT 2: The recent UI enhancements are being built into the master builds in Build #612. The core protocol of Wraith was finished in Build #604 of the master build. Now they are just layering the UI on top of their masterpiece. Icing on the cake!
EDIT 3: The results of Build #610 are positive! All of the lines of code that needed to execute, did so successfully. The successful code will be built into Build update #612 which is integrating the new UI code into the Master Build. Excellent progress.
EDIT 4: Build #612 is going smoothly. Over half of the way through compiling and no flags yet. Takes roughly 47 minutes to compile Windows, Linux, and Mac OS X. I have pulled an all nighter and will continue to keep an eye on the code and keep everyone in the loop on what the coders are up to and the progress they are making. I will not sleep until Wraith is complete!
EDIT 5: A couple of things not pointing to the correct toolbar, UI, action. Very minor hiccups. Most likely due to building multiple UI updates into the master all at once. Only one coder is active on Travis, but I guarantee there are many more working on their personal computers and fixing all of the small flags that are being thrown to finish the UI overhaul.
EDIT 6: I will address some of the concerns in this thread regarding code that has errors being uploaded onto Travis. The whole coding team is using Travis to centralize their efforts around. They most likely have a dev that is assigning portions of the UI code to individuals, who will provide their completed assignment once finished. Once the overall UI overhaul is near complete, then it will be compiled again in Travis.
EDIT 7: Build updates #613 and #614. Looks like they will be merging more and more code as it is complete. Keep an eye on Github for some updates. Also, looks like we have at least 4 to 5 coders actively working right now to get Wraith perfect before release. Hang tight.
EDIT 8: Pull request #152 and action #615. Lots of things being pulled into and integrated into the master (essentially the final build). Error flags are flying from not being fully integrated yet. Code looks extremely clean. Not a whole lot to update due to mostly everything happening behind the scenes. Going out for lunch for a bit and then I will come back and do an extensive review of anything that has been uploaded since I left. Things are looking smooth! No telling when Wraith is going to drop, but it will be AMAZING for the New Year and all of 2018!
EDIT 9: Hey everyone! I am back. Sorry that I left for a bit. So it looks like there has been a little bit of positive development since I left. First let me clarify some mild FUD that was being thrown around in some other threads: They DID NOT break the master build that they had running in Build #604 and #607. They can go right back to any previous working builds very easily. One of the most basic fundamentals in coding is saving the previous build overtime you compile a new one. Very easy for them to go back to back to a working build. So I will clarify that all of the focus is being put into getting the UI Pristine.
The issue boils down to the program that generates the Wraith UI that we will all see and use. Qt. There was an initial issue with the Qt version 5.4 that was used in the past. It was no longer available or compatible really. (for a great point of reference, bitcoin also had some issues with QT in the past during an update back in 2012. I can't seem to find the link that was floating around this sub/Github in the last 24 hours (no sleep)) Now the development focus is into Qt 5.5 or 5.10. Some of the devs tested Qt 5.10 yesterday and were unable to get it to work. The safe option at this point is to go with Qt 5.5 or an easily compatible version. Essentially all this means for the community is Wraith is going to look really amazing, or beautiful. The last thing that you do for any project is you develop the UI. Sunerok and the devs are just making sure that the gift they deliver to us looks as beautiful as possible. This is their baby, and when it is delivered they want it to look as shiny as possible. Worst case scenario at this stage in the game is they revert back to an earlier working build with a decent UI overlay that will satisfy this massive crowd. They are taking the time to see if they can end the year on the biggest bang possible. From what I see guys, no need to worry.
submitted by bettencourt76 to vergecurrency [link] [comments]

Discord Log from Ravencoin Open Developer Meeting - Oct 5, 2018

joey at 1:57 PM

What kind of transaction types are possible with RVN assets? Is it possible to create an asset that has a set lifetime or self-destruct time?

Tron at 2:00 PM

Not for assets/sub-assets/unique. We might be able to do that with voting tokens.

RavencoinDev at 2:01 PM

Hello Everybody!📷1

SpyderDev at 2:01 PM

Hi boss📷1

[Dev] Blondfrogs at 2:01 PM


Chatturga at 2:01 PM


BruceFenton at 2:01 PM

Probably lots of ways to do a self destruct on second layer as well if desired

russ at 2:01 PM

suuuuuupso what is todays topic?

RavencoinDev at 2:02 PM

Thanks for joining us today. We would like to discuss the current status of the 2.1 release.As well as doing an open Q&A at the end.First though I want to thank everybody that helped get the word out on upgrading to the release!Without that fix being in place and exchanges and pools upgrading we would be having a different conversation today.This community is amazing.

russ at 2:04 PM

we would have ended up like pigeoncoinnot a good look📷2

watsure at 2:05 PM

Hello Mr. God

RavencoinDev at 2:05 PM


russ at 2:05 PM

i gave pigeoncoin the pullrequest but they ignored meglad we have competent devs

[Dev] Blondfrogs at 2:05 PM

Everyone, So we are planning on getting out build 2.1 as soon as possible. We are still doing bug fixes, and getting the code hardened for release. There is currently one bug is the asset layer that we are fixing right now, and once that is done we should have a couple days of testing. It would be lovely if the community helped with testing, and we appreciate all of the testing that the community has already done. Once, we have a basic build that is tested, we are going to make a public release and notify the miners and pools.

RavencoinDev at 2:06 PM

Once that bug is addressed a release branch will be created.

russ at 2:06 PM

that duplicate ownership asset bug is nasty

RavencoinDev at 2:06 PM

You should all be able to build that and jump on testnet.

[Dev] Blondfrogs at 2:07 PM

@russ Yeah, didn't see that one. BUt I have a fix right now that seems to be working on my local machine

RavencoinDev at 2:07 PM

We need as much testing help from our devs as possible.

[Dev] Blondfrogs at 2:07 PM

so, I will have that pushed up with the day.

russ at 2:07 PM


[Dev] Blondfrogs at 2:08 PM

Just a reminder, that when the new wallet is published, if you don't update your wallet by the time assets are voting in by the blocks you will fork. So, we are going to try and get the wallet out there as soon as we can so users have weeks to upgrade.

Skan at 2:09 PM

Hey everyone

RavencoinDev at 2:10 PM

Any questions comments about the 2.1 release?

Skan at 2:10 PM

Mojave support?

SpyderDev at 2:10 PM

Yes and no

RavencoinDev at 2:10 PM

Good question SkanRight now that's also an issue with Bitcoin.

SpyderDev at 2:12 PM

The short version for Mojave is that the released binaries will work fine.

Skan at 2:12 PM

Interesting, so is it likely going to be a future upgrade that brings stability?

SpyderDev at 2:12 PM

However, developers should hold off.

RavencoinDev at 2:12 PM

We are currently building on High Sierra

Skan at 2:12 PM

Ok good to know for those who ask

SpyderDev at 2:13 PM

There is an incompatibility with Berkeley db version 4 that causes a segfault on init.

RavencoinDev at 2:13 PM

Or using the build scripts that Under created to build on Linux. Thjanks @Under

[Master] Roshii at 2:13 PM

Looks I'm late to the event

[Dev] Blondfrogs at 2:13 PM


RavencoinDev at 2:13 PM

Sorry it's late for you @[Master] Roshii

Skan at 2:14 PM

master roshi is never late, he is simply the turtle hermit

SpyderDev at 2:14 PM

One can upgrade Berkeley-db to the latest version and compile with the --incompatible-bdb and things will run, but there are some unknowns as far as wallet compatibility is concerned.

RavencoinDev at 2:15 PM

Raven will likely follow Bitcoin on Mojave support.

SpyderDev at 2:15 PM

The release binaries are compiled on Linux which we have tested on Mojave, so as long as you aren't compiling binaries go ahead and update to Mojave

RavencoinDev at 2:15 PM

It's a problem they have to solve as well, so...

SpyderDev at 2:15 PM

There is supposed to be a patch to bdb, but so far it isn't working

[Master] Roshii at 2:15 PM

@RavencoinDev it's never late for me.

Skan at 2:15 PM

Ok, and for the devs interested just point them to the berkeley upgrade with some warnings or to Under's scripts?

RavencoinDev at 2:16 PM

Right, the wallet runs just fine on Mojave. It's just a developer issue.

[Master] Roshii at 2:16 PM

If I can say anything it will be : don't update to Mojave

SpyderDev at 2:16 PM

There is a warning note in the docs section for OSX building

RavencoinDev at 2:16 PM

Mojave slowed down @[Master] Roshii and the iOS wallet.

Skan at 2:16 PM

YikesOk good to know, just want to be able to help / point people in the right direction

RavencoinDev at 2:17 PM

Thanks @Skan

SpyderDev at 2:17 PM

There is also an issue with Mojave dark mode and the QT wallet that makes things difficult to read (white on white text). We have a workaround which is to disable dark mode for QT in the plist file.

Skan at 2:17 PM

Ok so this is going to be pretty soon then, right ? Next week, likely?

RavencoinDev at 2:18 PM

Any further Mojave questions?Which @Skan ?

Skan at 2:18 PM

I think that covers it for me2.1 releaseIn order to have weeks to upgrade before main net

RavencoinDev at 2:18 PM

Yes, it is looking like we can work through this last issue with asset re-org very soon.Likely early next week.

Skan at 2:20 PM

Is 2.1 going to have any UI updates ?

RavencoinDev at 2:20 PM

Yes, frogs has more details.

[Dev] Blondfrogs at 2:20 PM

The UI is done. It is currently in the develop2. So if you have built the develop2 branch, you would be looking at the new UI for now.

RavencoinDev at 2:21 PM

There have been other QT designs kicked around and we would love to see more from the community.

[Dev] Blondfrogs at 2:21 PM

Future upgrades to come though. but those won't be mandatory upgrades. Just visual upgrades.

SpyderDev at 2:21 PM

The UI tweaks are subtle, but they make a big difference.

Skan at 2:22 PM

Very cool, I will check out dev2 branch

russ at 2:22 PM

new asset creation UI is awesome

Skan at 2:22 PM

I saw that, I like it. And the longer asset holdings list

RavencoinDev at 2:22 PM

@russ Don't make @[Dev] Blondfrogs head any larger...

russ at 2:23 PM


RavencoinDev at 2:23 PM

Other 2.1 release questions/comments?

Skan at 2:23 PM

Cant think of anything else at the momentThanks!

Hans_Schmidt at 2:23 PM

Is dividend support officially part of 2.1 release? It wasn't intuitive to me how that works.

RavencoinDev at 2:24 PM

No it will be in the next release. However, you could write a script that would provide the same functionality with what will be released in 2.1.

Skan at 2:25 PM

I heard something about Phase 4 being complete already, is that true, and is that in 2.1?

RavencoinDev at 2:25 PM

List all addresses with an asset, loop through sending X raven to each.

Skan at 2:25 PM

Unique assets>

RavencoinDev at 2:25 PM

Yes, Unique assets are complete.(edited)

Tron at 2:25 PM

Dividend support can be done without modifying the protocol. We can add it to a version of the software that can be used by the payer, without requiring others to upgrade.So we did phase 1, 2, 4

Skan at 2:26 PM

Oh wowGreat job everyone!

RavencoinDev at 2:26 PM

Yeah, we're super excited about the use cases that assets and unique assets provide to our develoepers(edited)

Skan at 2:27 PM

Can you tell us anything else about this separate software client? Will it be geared more towards enterprise use in general or will it just be that feature?

RavencoinDev at 2:27 PM

Speaking of, do any of you have a dev project in the works with assets?

russ at 2:27 PM

well its not a separate software client, its a backwards compatible release @Skan(edited)kind of like a softfork if you know what that is

Skan at 2:28 PM

Yeah unique assets will be awesome, actually there's a korean community member planning on issuing them along with silver ravencoinsIf im not mistaken

RavencoinDev at 2:28 PM

That's awesome!

russ at 2:28 PM

@RavencoinDev @Scotty is working on an asset explorerhttp://ravencoin.asset-explorer.net/

RavencoinDev at 2:29 PM

Yes, we've been watching that.

Skan at 2:29 PM

I am working with him on a Korean translation of the whitepaper, x16r whitepaper, and an introduction article so that we can take advantage of our availability in that market📷1

RavencoinDev at 2:29 PM

Super excited to see that mature.

Skan at 2:29 PM

@russ ah ok that makes senseWill there be anything else to that release?

RavencoinDev at 2:30 PM

Thanks @Skan. We want Raven to span the globe.Okay, Open Q&A time.What other questions do you guys have?

Skan at 2:31 PM

This release with rewards capability, will there be anything else added/changed for that version?

Tron at 2:31 PM

It might be released as phase 3, 5, 6.Although it could be released separately, without impacting anything.

Skan at 2:32 PM

Ah ok, so all of these features can be opted-into by someone who wants to take advantage, without cluttering the experience for a basic user

Tron at 2:32 PM

Phase 5 and 6 will be together as it requires a hard-fork.

RavencoinDev at 2:33 PM

Yes, we want to focus on user experience so it's super simple to do what you want to do.

Skan at 2:33 PM


russ at 2:33 PM

so is anyone working on RSK yet

[Dev] Blondfrogs at 2:34 PM

We aren't yet.

russ at 2:34 PM

yea im gonna have a look at the code soon

[Master] Roshii at 2:34 PM

Who said ravencoin needs RSK

RavencoinDev at 2:34 PM

It'd be great to have that done by the community.

russ at 2:34 PM

i think some people would like smart contracts @[Master] Roshii

Skan at 2:35 PM

RSK would be great for token distributions

russ at 2:35 PM

the real trick would be getting RSK to recognize assets

Tron at 2:35 PM

RSK, Segwit, Lightning are all on the table, but lower priority than phases 3, 5, 6.

[Master] Roshii at 2:35 PM

This is just like saying let's do what ravencoin does in the old fassion!

russ at 2:35 PM

well not really, smart contracts can do other things

[Master] Roshii at 2:36 PM

What's the RBF status @Tron

Skan at 2:36 PM

Keep us posted russ I think that would be amazingWhen you write smart contracts in RSK what language is it in?

russ at 2:36 PM

solidity i thinlthink

RavencoinDev at 2:36 PM


russ at 2:36 PM

eth contracts also work on RSKso thats a plus

Skan at 2:37 PM

Ok great so we dont even have to work on templates or anything

RavencoinDev at 2:37 PM

Having solidity contracts that interact with Raven assets would open up a lot of possibilities.

Skan at 2:37 PM

I think so too, especially for stuff like tokens in gaming use case📷1

russ at 2:37 PM

i guess it would also help with cross chain atomic swaps too

Skan at 2:37 PM


RavencoinDev at 2:37 PM


russ at 2:38 PM

BTC directly for an asset

Skan at 2:38 PM

sounds like a good product

russ at 2:38 PM

making ICOs easier

Tron at 2:38 PM

Yes, cross-chain atomic swaps would be amazing with user issued assets.

RavencoinDev at 2:39 PM

Other questions?

Skan at 2:40 PM

Smart contract atomic swap erc20token 1:1 for their new RVN counterpart

Hans_Schmidt at 2:40 PM

I believe that every cross-chain atomic swap implementation I have seen requires a trusted federation. That's even true for RSK.

Tron at 2:40 PM

@Skan I like it!

Skan at 2:42 PM

No more questions from me

RavencoinDev at 2:42 PM

Okay, seems that we're winding down on the Q&A.Thank you all for joining us today. I've really liked how this discussion has worked out on Discord.Did anybody miss IRC today?

russ at 2:43 PM

hell no

Hans_Schmidt at 2:43 PM

Like a toothache

russ at 2:43 PM

this was waaay better

RavencoinDev at 2:44 PM


Hans_Schmidtat 2:44 PM

Missed the mems tho

RavencoinDevToday at 2:44 PM

I agree. I was even able to fix my typos.That's right, we had some epic memes last time.Where are you @Pathfinder

Chatturga at 2:45 PM

@Pathfinder Do you have an epic meme for us today?

Skan at 2:45 PM

Meme please

[Master] Roshii at 2:46 PM

Can somebody give @Pathfinder a Master Memer role and color

Chatturga at 2:46 PM


Pathfinder at 2:46 PM

heyayeah, that was my meme for today 📷 ty Chatturga

BruceFenton at 2:46 PM

Good stuff

RavencoinDev at 2:47 PM

Thanks everybody!

[Dev] Blondfrogs at 2:47 PM

peace out

Skan at 2:47 PM


RavencoinDev at 2:47 PM

Have a great weekend. NH Raven Meetup next week!!!!

Jeroz at 2:47 PM


SpyderDev at 2:47 PM

Thanks guys!

RavencoinDev at 2:47 PM

See you there!

Pathfinder at 2:47 PM

I'll be there! looking forward to seeing folks 📷

Hans_Schmidt at 2:47 PM

See ya in NH

Tron at 2:48 PM

See ya there!

Jeroz at 2:48 PM

Cant make it, but have fun! 📷

RavencoinDev at 2:48 PM

^ did you have a question about tron's Comment?

Jeroz at 2:49 PM

No I was super excited about it

RavencoinDev at 2:49 PM

Ah, me too!

russ at 2:49 PM

mtarget is streaming the meetup, right?

RavencoinDev at 2:50 PM

Not sure, we have really appreciated his work in the past but haven't heard.

Chatturga at 2:52 PM

Yes, he is planning on doing a stream📷1

RavencoinDev at 2:53 PM

Thanks again everybody.
submitted by Chatturga to Ravencoin [link] [comments]

A Guide to Keeping Keys Offline Using Armory +rPi

Hi Redditors.
I am going to post in this thread my experiences in getting my Desktop (Debian) machine running Armory in watch-only mode, and coupling that with an offline Raspberry Pi (which holds my private keys) for signing the transactions previously made in watch-only mode.
I actually compiled Armory from source directly on my Pi. This guide is probably more for the bitcoin 'power user', as to run Armory online, and broadcast the signed transactions, you need to have a bitcoin full node running (bitcoind).
Basic requirements:
Aimed-for Setup:
I'll post the guide in digestible sections...

Section 1

I should begin by saying I installed source code from git, and got Armory to build the DB on my desktop initially, WITHOUT creating a wallet.. (This allowed me to debug what was going on a little!)
Go to Bitcoin.org, select Armory..
It leads to a Download from Git:
Followed the procedure for Linux Debian verify code, compile, install, all straight-forward..
Began by running bitcoind, and telling Armory where to find it. This is the command I used, obviously it was all on one line and didn't include the arrows/explanations!:
python ArmoryQt.py \ --satoshi-datadir=/BlockChain/chain20180414/blocks \ # <-----(where my bitcoind blocks live) --datadir=/ArmoryDataDi \ # <-----(this is instead of ~/.armory) --dbdir=/ArmoryDataDidatabases # <-------(again, non std. place used for Armory's databases.. my choice.) 
So, on the Desktop, after the initial "build databases"
(NB the initial "Build Databases" took about 1.5h and my two CPUs were maxed the whole time, Temps up to 62C. Not ideal; Im not in a rush!)
I then wanted to import a watch-only wallet.
Before I did this, I took a full backup of the Armory data dir:
(or ~/.armory in a default installation).
I'd hate to have to make Armory do another full sync with the bitcoind node!

Section 2

Next step: offline wallet (with Private Keys) is on a Raspberry Pi.
I downloaded the source and managed to compile it on the pi itself! :)
Though there were some gymnastics needed to setup the Pi.
My Pi is running Raspbian based on Wheezy.. quite old!
I did the following on the Pi:
apt-get update apt-get upgrade (<---took about an hour!) apt-get install autotools-dev apt-get install autoconf 
Then I followed the instructions exactly as I had done for my Debian Desktop machine, EXCEPT:
I had to increase the Pi's swap space. I upped it from 100Mb to 400Mb.
The compilation took 7 hours, and my poor SD card got a thrashing.
But after compilation, I put the Swap back to 100Mb and Armory runs ok with about 150Mb of memory (no swap needed).
Swap increase on the Pi:
use your favourite editor, and open the file /etc/dphys-swapfile
add/change the following line:
Then, REBOOT the Pi:
sudo shutdown -h -P now 
Once the compilation was done on the Pi, put the swap back, rebooted and created an Armory wallet.
I added manual entropy and upped the encryption 'time' from 250ms to 2500ms - since the Pi is slow, but I'll be happy to wait for more iterations in the Key Derivation Function.
Once the wallet was created, it obviously prompts you for backup.
I want to add a private key of my own (i.e. import), so don't do the backup until this is over.
I import my Private Key, and Armory checks that this corresponds to a Public Key, which I check is correct.
This is the point now where the Pi storage medium (e.g an SD card) has to be properly destroyed if you ever get rid of it.
I had thought that now would be a good time to decide if your new wallet will generate Segwit receiving addresses, and also addresses used to receive 'change' after a transaction..
But it seems Armory WON'T let you switch to P2SH-P2WPKH unless your Armory is connected to a node offering "WITNESS" service.
Obviously, my Pi is offline and will never connect to a node, so the following will not work on the Pi:
NB: I thought about setting this on the Debian "watch-only" wallet, but that would surely mean doom, as the Pi would not know about those addresses and backups might not keep them.. who knows...
So, end result:- no segwit for me just yet in my offline funds.

--If anyone can offer a solution to this, I'd be very grateful--

Section 3

Ok, now this is a good point to back up your wallet on the Pi. It has your imported keys. I choose a Digital Backup - and put it on a USB key, which will never touch the internet and will be stored off-site. I also chose to encrypt it, because I'm good with passwords..
NB: The Armory paper backup will NOT back up your imported private keys, so keep those somewhere if you're not sweeping them. It would be prudent to have an Armory paper backup anyway, but remember it will likely NOT help you with that imported key.
Now for the watch-only copy of the wallet. I want to get the "watch-only" version onto my Desktop Debian machine.
On the Pi, I created (exported to a USB key) a "watching-only" copy of my wallet.
I would use the RECOMMENDED approach, export the "Entire Wallet File".
As you will see below, I initially exported only the ROOT data, which will NOT capture the watching-only part of the Private Key I entered manually above (i.e. the public Key!).
Now, back on the Debian Desktop machine...
I stopped all my crontab jobs; just give Armory uninterrupted CPU/memory/disk...
I also stopped bitcoind and made a backup prior to any watch-only wallet being imported.
I already made a backup of Armory on my Desktop, before any wallet import.
(this was needed, as I made a mistake.. see below)
So on the Debian Desktop machine, I begin by firing up bitcoind.
my command for this is:
./bitcoind -daemon -datadir=/BlockChain/chain20180414 -dbcache=400 -maxmempool=400 

Section 4

I try running Armory like this:
(I'm actually starting Armory from a script - StartArm.sh)
Inside the script StartArm.sh, it has the line:
python ArmoryQt.py --ram-usage=4 --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
I know from bitter experience that doing a scan over the blockchain for a new wallet takes a looong time and a lot of CPU, and I'd like it to play nicely; not gobble all the memory and swap and run my 2xCPUs both at 100% for four hours...
So... I aim to run with --ram-usage=X and --thread-count=X
(For me in the end, X=1 but I began with X=4)
I began with --ram-usage=4 (<--- = 4x128Mb)
The result is below...
TypeError: cannot concatenate 'str' and 'int' objects 
It didn't recognise the ram-usage and carried on, crippling my Debian desktop PC.
This is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up, and it can take over 30 minutes just to exit nicely from bitcoind and ArmoryDB.
So, I ssh to the machine from another computer, and keep an eye on it with the command
"free -h" 
I'd also be able to do a "sudo reboot now" if needed from here.

Section 5

So, trying to get my --ram-usage command recognised, I tried this line (added quotes):
python ArmoryQt.py --ram-usage="4" --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
But no, same error...
Loading Armory Engine: Armory Version: 0.96.4 Armory Build: None PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('debian', '9.4', '') User home-directory : /home/ Satoshi BTC directory : /BlockChain/chain20180414 Armory home dir : /ArmoryDataDi ArmoryDB directory : /ArmoryDataDidatabases Armory settings file : /ArmoryDataDiArmorySettings.txt Armory log file : /ArmoryDataDiarmorylog.txt Do wallet checking : True (ERROR) ArmoryUtils.py:3723 - Unsupported language specified. Defaulting to English (en) (ERROR) ArmoryQt.py:1833 - Failed to start Armory database: cannot concatenate 'str' and 'int' objects Traceback (most recent call last): File "ArmoryQt.py", line 1808, in startArmoryDBIfNecessary TheSDM.spawnDB(str(ARMORY_HOME_DIR), TheBDM.armoryDBDir) File "/BitcoinArmory/SDM.py", line 387, in spawnDB pargs.append('--ram-usage=' + ARMORY_RAM_USAGE) TypeError: cannot concatenate 'str' and 'int' objects 

Section 6

So, I edit the Armory python file SDM.py:
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=4') #COMMENTED THIS, SO I CAN HARDCODE =4 # ' + ARMORY_RAM_USAGE) 
Running it, I now have acknowledgement of the --ram-usage=4:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=4 
Also, even with ram-usage=4, it used too much memory, so I told it to quit.
It took over 30 minutes to stop semi-nicely. The last thing it reported was:
ERROR - 00:25:21: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version 
But that didn't seem to matter or corrupt the Armory Database, so I think it's ok.
So, I get brave and change SDM.py as below, and I make sure my script has a command line for --ram-usage="ABCDE" and --thread-count="FGHIJ"; the logic being that these strings "ABCDE" will pass the IF criteria below, and my hardcoded values will be used...
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=1') #COMMENTED THIS, SO I CAN HARDCODE =1 # ' + ARMORY_RAM_USAGE) if ARMORY_THREAD_COUNT != -1 pargs.append('--thread-count=1') #COMMENTED THIS, SO I CAN HARDCODE =1 #' + ARMORY_THREAD_COUNT) 
So, as usual, I use my script and start this with: ./StartArm.sh
(which uses command line:)
python ArmoryQt.py --ram-usage="ABCDE" --thread-count="FGHIJ" --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
(this forces it to use my hard-coded values in SDM.py...)
So, this is the command which it reports that it starts with:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=1 --thread-count=1 
Again, this is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up. So I ssh to the machine and keep an eye on it with:
"free -h" 

Section 7

So, on the Debian Desktop PC, I inserted the USB stick with the watch-only wallet I exported from the Pi.
Start Armory...
Import "Entire Wallet File" watch-only copy.
Wait 4 hours..
After running Armory for about 30m, the memory usage dropped by 400m... wierd...
It took ~2 hours to get 40% completion.
After 3.5 hours it's almost there...
The memory went up to about 1.7Gb in use and 900Mb of Swap, but the machine remained fairly responsive throughout, apart from a few (10?) periods at the start, where it appeared to freeze for 10-30s at a time.
(That's where my ssh session came in handy - I could check the machine was still ok with a "free -h" command)
Now, I can:
Create an unsigned transaction on my Desktop,
Save the tx to USB stick,
Move to the Pi,
Sign the tx,
Move back to the Desktop,
Broadcast the signed tx.

Section 8

My initial Mistake:
This caused me to have to roll-back my Armory database, using the backup. so you should try to avoid doing this..
On the Pi, I exported only the ROOT data, which will NOT capture the watching-only part of the Private Key
It is RECOMMENDED to use the Digital Export of Entire Wallet File from the Pi when making a watch-only copy. If you just export just the "ROOT data", not the "Entire Wallet File", you'll have problems if you used an imported Private Key in the offline wallet, like I did.
Using the ROOT data text import, after it finished... my balance was zero. So,. I tried a Help->Rescan Balance (Restart Armory, takes 1minute to get back up and running) No Luck. Still zero balance.
So, I try Rescan Databases.. This will take longer. Nah.. no luck.
So, I tried again, thinking it might be to do with the fact that I imported the text "root data" stuff, instead of following the (Recommended) export of watching-wallet file.
So, I used my Armory backup, and wound back the ArmoryDataDi to the point before the install of the (zero balance) wallet. (you should not need to do this, as you will hopefully use the RECOMMENDED approach of exporting the "Entire Wallet File"!)
submitted by fartinator to Bitcoin [link] [comments]

Walk through of how to claim BCD Bitcoin Diamond

I am completely naive when it comes to Linux, coding, compiling, etc., so I found it difficult to follow advice I found for compiling the bitcoin diamond code form git. I followed a few guides for bitcoin core first and could never get it to work. I got some help from someone that knows Linux and here's what finally worked for me with BCD.
Use rufus to make bootable usb with ubuntu iso. (https://rufus.akeo.ie/)
Boot from the usb and install ubuntu.
Follow this guide to compile bitcoin from git: https://www.toshblocks.com/bitcoin/compile-bitcoin-source-code-ubuntu-16-04-lts/
Do the entire guide with bitcoin core to ensure everything is working.
Make sure you replace "theusername" with your own each time it appears, or make "theusername" your user name from the beginning.
There was one small difference, at the end of the guide to run bitcoin-qt it is ./src/qt/bitcoin-qt
At the end when trying to run bitcoin-qt (./src/bitcoin-qt) it said there was no such file, which made me think that I did something wrong but you just have to find where the file is. Hey, I said I was a complete noob, go easy on me.
When you repeat the procedure for BCD there will be a few small changes:
git clone https://github.com/bitcoin/bitcoin.git
git clone https://github.com/eveybcd/BitcoinDiamond.git
mkdir bitcoin/db4/
mkdir BitcoinDiamond/db4/
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=/home/theusername/bitcoin/db4/
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=/home/theusername/BitcoinDiamond/db4/
./configure LDFLAGS="-L/home/theusername/bitcoin/db4/lib/" CPPFLAGS="-I/home/theusername/bitcoin/db4/include/"
./configure LDFLAGS="-L/home/theusername/BitcoinDiamond/db4/lib/" CPPFLAGS="-I/home/theusername/BitcoinDiamond/db4/include/"
when you get to this line: [email protected]eries:~/BitcoinDiamond$ ./autogen.sh
I got the following error:
bash: ./autogen.sh: Permission denied
this command will show some information about autogen.sh
[email protected]:~/BitcoinDiamond$ ls -l autogen.sh
-rw-rw-r-- 1 mmmmm mmmmm 527 Dec 30 21:26 autogen.sh
same command comparing it to the bitcoin core version of autogen.sh
$ ls -l ../bitcoin/autogen.sh
-rwxrwxr-x 1 mmmmm mmmmm 527 Dec 30 21:03 ../bitcoin/autogen.sh
do this to make them the same
[email protected]:~/BitcoinDiamond$ chmod a+x autogen.sh
recheck autogen.sh and it should match the bitcoin core autogen.sh now
[email protected]:~/BitcoinDiamond$ ls -l autogen.sh
-rwxrwxr-x 1 mmmmm mmmmm 527 Dec 30 21:26 autogen.sh
continue on
[email protected]:~/BitcoinDiamond$ ./autogen.sh
[email protected]:~/BitcoinDiamond$ ./configure LDFLAGS="-L/home/mmmmm/BitcoinDiamond/db4/lib/" CPPFLAGS="-I/home/mmmmm/BitcoinDiamond/db4/include/"
[email protected]:~/BitcoinDiamond$ make -s -j5
It will work a while and then you'll get the following error, among others:
/bin/bash: ../share/genbuild.sh: Permission denied
It's the same error as with autogen.sh, so find it and fix it by the following:
[email protected]:~/BitcoinDiamond$ find . -name genbuild.sh ./share/genbuild.sh
[email protected]:~/BitcoinDiamond$ chmod a+x ./share/genbuild.sh
continue on by restarting make
[email protected]:~/BitcoinDiamond$ make -s -j5
It should be good!
go to and run bitcoin-qt to start the gui
[email protected]:~/BitcoinDiamond/src$ cd qt
[email protected]:~/BitcoinDiamond/src/qt$ ./bitcoin-qt
bitcoin-wt will spend some hours syncing the entire blockchain so you have to wait.
When it is finished, import private keys by:
clicking in the "Bitcoin Core - Wallet" window to make it active
hover mouse in top left of the grey bar on the top of the deskto screen, not the "Bitcoin Core - Wallet" until it says "file settings help"
click on "help"
click on "Debug Window"
click on the "Console" tab
enter "importprivkey 5KJvsngHeMpm884wtkJNzQGaCErckhHJBGFsvd3VyK5qMZXj3hS" with your own key
make an account at gate.io where they are allowing deposits
sell!, or don't, maybe you're nuts, who am I to judge
submitted by Ozmodiar to BitcoinAirdrops [link] [comments]

Homelab collective ressources post!

Hey guys!
I'm fairly new to this sub and to having a home lab in general and I found this community to be so kind and helping, I wanted to give back what I've learned. I'm seeing a lot of questions asked around on improvements and on what to do with x extra hardware so I thought it would be nice to have a thread to regroup that.
I'll put here some stuff I gathered and the most common questions I've seen, feel free to contribute and i'll update the post along.
Latest Additions
Homelab Dashboard
Posts about dashboards have been growing lately and here are some of the best that were kind enough to provide us with their sources.
User Screenshot Source
yours truly http://imgur.com/a/GhCNH https://github.com/Gabisonfire/dashboard-q
lastditchefrt http://i.imgur.com/5zQdao4.png https://github.com/d4rk22/Network-Status-Page
_SleepingBag_ http://i.imgur.com/Ql9ZM4W.png https://github.com/jsank/homelabdash
NiknakSi https://niknak.org/extras/sysinfo TBA
DainBramaged http://imgur.com/jYNlUEQ https://github.com/gordonturneBigBoard
michaelh4u https://i.imgur.com/XkZwMKj.png https://github.com/michaelh4u/homelabfrontpage
spigotx http://imgur.com/a/1zMht https://github.com/spigotx/HomeLab2
SirMaster https://nicko88.com/ https://github.com/dashbad/plex-server-status
yourofl10 http://imgur.com/a/AyROa TBA
TheBobWiley http://imgur.com/a/oU6d3 https://github.com/TheBobWiley/ManageThis-LandingPages
0110010001100010 http://i.imgur.com/iwtQcsL.jpg https://github.com/danodemano/monitoring-scripts
mescon & SyNiK4L https://i.imgur.com/gqdVM6p.jpg https://github.com/mescon/Muximux
ak_rex http://i.imgur.com/a/RJkrT https://github.com/ak-rex/homelab-dashboard
Or build yours from scratch: PRTG API, ELK, Grafana, freeboard, JumpSquares
Some other resources: Custom Monitoring Scripts by 0110010001100010
Credits to apt64 for his original post
= Pi specific =
= Download Automation =
= Virtualization =
= Monitoring =
= Media Center =
= Remote access =
= VOIP =
= Networking =
= File Servers/Storage/RAID =
= Cameras =
= Documentation =
= Dynamic DNS =
= Backup =
= Creating network diagrams =
= Guides =
= Misc =
That's all I could come up with on top of my head + some research, passing over to you guys so we can get a nice complete list!
Let's try and stick with free(or mostly) softwares, let me know if you guys feel otherwise.
submitted by Gabisonfire to homelab [link] [comments]

How to Build Qt for Any Board (Embedded Linux) {on-demand ... Compile Bitcoin's source code (0.13) 4. Installing Bitcoin Core on Linux Komodo Qt Wallet: Early Alpha Demo Compiling Bitcoin Core Source Code - 2017 debian/ubuntu/linux with Music

Cross-compile Bitcoin for ARM. 2016-02-23 • bitcoin ARM g++ crosstool-ng. Introduction. So you want to cross-compile Bitcoin (or any C/C++ program in fact) from your x86_64 host machine for an ARM “target” machine. This little howto aims to help you with that. It’s intended for intermediate level, i.e. you should be familiar with the ./configure and make commands but you don’t need ... Compile Bitcoin-Qt from source. qmake-qt4 -makefile -Wall USE_QRCODE=1 make There are a ton of generic instructions spit out when I enter qmake-qt4 command and then upon entering the make command I am told: make: * No targets specified and no makefile found. Stop. FYI, I am using the PKGBUILD file as a guideline for creating the above instructions. bitcoin-core compiling bitcoin-qt-setup ... There are ARM devices out there with HDMI and full desktop linux support. I was able to compile and use QT on an Orange Pi Plus2E running Lubuntu 16.04. Compilation on the device itself takes several hours and QT spends a few minutes loa... Wait a second. .exe files are used on Windows, not Linux (your executable file is simply named bitcoin-qt and is probably in /usr/local/bin). Are you wanting to compile a version for Windows computers (that's called cross-compiling), or a version to run on other Linux computers without installing other dependencies (that's called static linking)? Bitcoin-Qt version 0.8.4 is now available from: ... Linux: clicking on bitcoin: links was broken if you were using a Gnome-based desktop. Fix a hang-at-shutdown bug that only affects users that compile their own version of Bitcoin against Boost versions 1.50-1.52. Other changes. Checkpoint at block 250,000 to speed up initial block downloads and make the progress indicator when downloading ...

[index] [31196] [39939] [134] [7016] [44955] [41877] [20124] [29496] [19511] [7180]

How to Build Qt for Any Board (Embedded Linux) {on-demand ...

This video Shows how to Compile Bitcoin Source Code on Linux operating systems. it covers almost everything on how to compile bitcoin source code. Build Bitc... this video explain how you build the compile environment on windows to create altcoin ~ cryptocoin Windows QT `s Compile Depencies ~ complete deps folder included to download . Depencies : https ... This short video shows how to compile the bitcoin source code on linux (ubunu). an easy task to do but it take some time (around 15 min) please read the instruction in the official github https ... Use the VanityGen tool to generate a Bitcoin address that stands out from the others. Decide for yourself the first part of the address, and have an address ... Discover how to build Qt for Embedded devices running Linux. We’ll cover the following topics: • Adding Qt recipes to your own Yocto build • Building Qt lib...