Install Bitcoin Core on Mac OS X - Bitcoin-en.com

Feather - free, open-source Monero desktop wallet releasing soon™

For the past year tobtoht and I have been working on the foundations of a new Monero desktop GUI called Feather for Mac OS and Linux platforms (Windows tentative) using Qt5, libwallet, QtWidgets.
The goal of this new wallet is to provide a practical, robust and easy-to-use Monero wallet for every day use. It aims to be beginner friendly, but should also cater to the needs of experienced Monero users with the addition of advanced features like coin control and multisig.
Feather's user interface is inspired by Bitcoin's Electrum wallet, but adapted to fit Monero. Feather is not a fork of Electrum, all of the UI code was written from scratch in C++ / QtWidgets.
Development began in the summer of 2019. We estimate to release a beta version in November or December.

Video preview

https://www.youtube.com/watch?v=tylbteVtwrw (watch fullscreen)

Why

Our primary motivation is to create a wallet that we ourselves would want to use and recommend to friends. There aren't many options when it comes to non-custodial Monero desktop wallets. The CLI is an excellent tool for power-users, but is simply not an option for users that are not familiar with with the terminal. The GUI has a slick user interface, but is demanding on system resources due the use of Qt Quick.
Instead we've taken inspiration from Bitcoin's Electrum and started working on the most basic looking Monero desktop wallet one can imagine. We've gotten rid of a lot of functionality, but also added new functionality. Just focussing on the basics results in a clean, robust, and beginner proof wallet.

Privacy

In an effort to mitigate unintentional off-chain linking, we have made it harder to reuse addresses by automatically hiding used subaddresses. We find that the primary address leads uninformed users to believe that it is somehow functionally incompatible with subaddresses, or that funds sent to subaddresses can not be spent together. To encourage the use of subaddresses the primary address is hidden by default, and only used for change and coinbase outputs.
Our wallet supports advanced coin control features like freeze/thaw and sweeping a single output. In the future we may add manual transaction input selection.
There is no need to manually setup Tor to protect your traffic, Feather comes bundled with Tor. By default all traffic is routed through Tor with the exception of traffic between wallet and daemon. Wallet synchronization over Tor takes substantially longer than over clearnet, but you can optionally enable to connect to remote nodes over Tor. If your machine already has a Tor daemon running Feather can use the system daemon when instructed.
Just like in the official GUI, Feather essentially has 2 modes of connecting to the Monero network. You either host your node somewhere (localhost/LAN/internet) or we'll provide you one from a list of trusted, stable, community hosted remote nodes (like Cake Wallet). If Feather detects that it's running on Tails or Whonix it will automatically connect to a random .onion remote node.

Performance

Feather is built with Qt Widgets, providing native looks and performance. In a recent test™ a wallet with 10k+ transactions only consumed 200 MB ram (before optimizations). In comparison, the official GUI uses 400 MB before a wallet is opened.
GPU power is plenty nowadays so this hardly a problem, however, we are serious about providing an user interface that feels snappy to use. The application itself starts within 1-2 seconds on most machines (Bitcoin's Electrum is more like 4-5 seconds due to their usage of PyQt).

User experience

We have implemented Tevador's 14 word seed scheme with embedded restore height. The same function is used to derive the private view key from the private spendkey, therefore it is possible to convert the 14 word seed into a standard 25 word seed in case you want to restore the wallet using the official wallet software.
Feather connects to a websocket server over Tor to obtain miscellaneous data such as: price information, a list CCS proposals, posts on /Monero, the most recent blockheight, a list of community hosted nodes and the latest version of Feather.
The websocket server itself is open-source and self-hostable. By default Feather will connect to a server hosted by the project maintainers. The websocket connection can be disabled completely, but some functionality will be disabled/broken.
Our target audience are users who want to use Monero without too many issues and we've designed the wallet as such, with lots of convenience features, while routing it all over Tor in the background.
The native look of the application should feel familair to users as it behaves like any other program that runs on their computer. Added benefit for future contributors/developers is that it's very fast to implement/test UI components by borrowing from QtWidget's vast library. This in contrast with the Monero GUI, which uses custom QML components - a tricky and time consuming rendereframework more suited for large teams to create electron-like applications.

Additional information

Proposal

Work started early summer 2019. We still have some features to finish, prepare CI/CD, etc. As such we expect an alpha or beta release in December 2020. For this we would like the community's approval to allow the milestones defined in GUI CCS to be used for the remainder of this project, paid in full - we can use the support. Consequently all code will be licensed under the Monero Project and features/changes to libwallet or wallet2 will be committed to upstream (Monero GUI/core). Future development and releases will be maintained by dsc__ and tobtoht.

Beta testing

Idle in #feather on irc.oftc.net if you want to help beta testing in a month or so. You will need Linux, as this is our primary platform for developing the application.
Please let us know what you think in the comments. We're open to suggestions/feature requests/brainfarts.
submitted by dsc__ to Monero [link] [comments]

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

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:
https://github.com/reddcoin-project/reddcoin/issues
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
Credits
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]

Groestlcoin 6th Anniversary Release

Introduction

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?

Windows
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.
OSX
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.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

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

Source

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.

Features

Download

iOS
Android

Source

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.

Features

Download

Main Release (Main Net)
Testnet Release

Source

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.

Features

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

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

Features

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

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

Features

Download

Source

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.

Features

Remastered Improvements

Download

Source

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.

Features

Download

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

Source

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.

Features

Download

Windows
Linux / OSX (Instructions)

Source

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.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

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.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

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

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

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

https://travis-ci.org/vergecurrency/VERGE/builds/323560824
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]

Bitcoin 2 Core v.2.2 Wallets Released!

Now available for download at https://www.bitc2.org/#wallets and https://github.com/BITC2/bitcoin2/releases
Version 2.2 Change log:
Updating your Bitcoin 2 Core wallet to this version is mandatory. That includes upgrading all your Masternodes. After enough nodes have upgraded to this version, a new staking protocol will be activated and the old nodes that fail to upgrade their wallet before that will end up forking to the wrong chain. Estimated time of this protocol upgrade is between August 21 - August 24 2019. As soon as possible.
To update, you just need to download the archive, stop your wallet and let it fully shutdown, and then copy the executable files in the bitcoin2-bin folder to replace the ones you had installed already.
After upgrading your Masternode and your desktop wallet, you should go in the Masternodes tab on your controller wallet and click to Start the upgraded Masternodes.
Binaries for a couple of platforms that are less used are still to be compiled.
submitted by Giradone to bitc2 [link] [comments]

Lore v2 QT on Raspberry Pi

Hello,
 
To follow up to mindphuk's excellent piece on building the headless client on Raspberry Pi (https://www.reddit.com/blackcoin/comments/6gkjrw/wip_blackpi_a_stake_device_based_on_raspberry/), I thought if anyone was interested I'd show you how to get the full QT version running on the Pi on the Jessie with Pixel desktop. This works and has been soak tested for several days now on a standard Raspberry Pi 3. I have since added some coins and it stakes a handful of times a day.
 
Running staking Lore clients paves the way for some of the future use cases of BLK utilising the Bitcoin 0.12 (and newer) core tech, including colored coins. So I'm going to leave this one going indefinitely to kickstart the number of Lore clients staking. It's certainly not mandatory but it will be good in the longer term to have a nice distribution of Lore staking clients.
 
The cross-compile which lets you create binaries for multiple platforms didn't work for the QT version on the Pi, so there is more to do than just running the binary unfortunately, as below. There are folks working on some much cleaner solutions than this for the Pi, with a custom front end, and where you won't have to do any mucking about. That is coming soon. In the meantime, if you enjoy a fiddle with such things, here's how to get this QT client working on your Pi.
 
These instructions assume you are starting from scratch with a completely blank OS.
 
Download Jessie with Pixel from: http://downloads.raspberrypi.org/raspbian/images/raspbian-2017-07-05/2017-07-05-raspbian-jessie.zip
 
Note they have since (August 2017) released a version called 'Stretch' which does not work with this guide. I'll see if I can come up with something new for that at some point and link to it here when I have. In the meantime the guide should work with the Jessie image above.
 
Unzip the file and extract the .img file to burn it onto Fresh SD card to boot from (to be safe, use 16GB or larger), using a tool like win32diskimager or Etcher.
 
Assuming you have keyboard/mouse and monitor plugged into your pi, boot it up and the Jessie Desktop will show.
 
Before we do anything else, you should increase the default swap size on the pi, as compiling certain libraries can exhaust the RAM and get stuck otherwise. To do this, launch a Terminal window and type:
 
sudo nano /etc/dphys-swapfile 
 
and Change the CONF_SWAPSIZE from 100 to:
 
CONF_SWAPSIZE=1024 
 
Exit nano with control + x to write out the file.
 
Then, run the following to restart the swapfile manager:
 
sudo /etc/init.d/dphys-swapfile stop sudo /etc/init.d/dphys-swapfile start 
 
Now, launch the browser and download the Lore 2.12 binaries for ARM here: https://mega.nz/#!k2InxZhb!iaLhUPreA7LZqZ-Az-0StRBUshSJ82XjldPsvhGBBH4 (Version with fee fix from 6 September 2017)
 
(If you prefer to compile it yourself instead, it is possible by following the instructions in the original article by Mindphuk just taking into account this is the newer version of the Lore client than when that was written (https://github.com/janko33bd/bitcoin/releases) and the versions of Boost and the Berkeley DB need to be the same as below.)
 
Double click the zip and extract the Lore binary files. Yes, at the moment they are all called 'bitcoin', not 'blackcoin' or 'Lore' - this is because the code derives from a recent bitcoin core implementation so this has not yet been updated. You can place these wherever you like.
 
In the Terminal window, change directory to where you put the binaries, e.g.:
 
cd Downloads/lore-raspberrypi-armv7-jessie-pixel chmod +x * 
 
That marks the binaries as executable.
 
Now, we need the Boost libraries installed for any of the Lore binaries to work. The project was done with Boost 1.62.0. Unfortunately the Jessie repository only goes up to 1.55, so we need to download and build 1.62 manually on the device.
wget https://sourceforge.net/projects/boost/files/boost/1.62.0/boost_1_62_0.tar.gz/download tar -xvzf download cd boost_1_62_0 sudo ./bootstrap.sh sudo ./b2 install 
 
(This will take almost 2 hours. Have a nice cup of tea and a sit down.)
 
When I came to run the binaries, I found they couldn't find Boost. Running this command fixes that:
sudo ldconfig 
 
Now we are going to install the packages which aren't already included in the default OS installation which the binaries need in order to run:
sudo apt-get install qrencode libprotobuf-dev libevent-pthreads-2.0-5 
 
Now we need to install the Berkeley Database version 6.2.23. This is the version Lore v2 uses. Bitcoin still uses 4.8 which is 10 years old! This doesn't take too long.
wget http://download.oracle.com/berkeley-db/db-6.2.23.tar.gz tar -xvzf db-6.2.23.tar.gz cd db-6.2.23/build_unix ../dist/configure --prefix=/usr --enable-compat185 --enable-dbm --disable-static --enable-cxx 
 
I find this next section of the Berkeley instructions worked better just switching to root, which can be fudged by running sudo su before the rest:
sudo su make make docdir=/usshare/doc/db-6.2.23 install chown -v -R root:root /usbin/db_* /usinclude/db{,_185,_cxx}.h /uslib/libdb*.{so,la} /usshare/doc/db-6.2.23 
 
Now we're going to go up a couple of directories to where the binaries were:
cd ../.. 
 
Then run the client!
./bitcoin-qt 
 
And there you have it. Should hopefully end up looking a bit like this: http://imgur.com/a/eEHGa
 
Using the Bootstrap can save a while syncing. Download it at: https://www.reddit.com/blackcoin/comments/6b3imq/blackcoin_bootstrapdat_up_to_block_1631800
 
Place the bootstrap.dat file into the ~/.lore directory.
 
Run ./bitcoin-qt again, it will say 'Importing Blocks' rather than 'Synchronising with Network'. My pi sync'ed fully in about 5-6 hours.
 
If you want peace of mind that Lore will always start on bootup into the Jessie w/Pixel desktop (i.e. after a power cycle), then you need to create a .desktop file in the following place.
sudo nano ~/.config/autostart/Lore.desktop 
 
And in it, enter the following (tailoring the Exec line below to the whereabouts of your bitcoin-qt file):
[Desktop Entry] Name=Blackcoin Lore Comment=Mining without the waste Exec=/home/pi/Downloads/lore-raspberrypi-armv7-jessie-pixel/bitcoin-qt Type=Application Encoding=UTF-8 Terminal=false Categories=None; 
 
Power usage and payback time
 
After a good while leaving it going by itself, the CPU load averages got down to almost zero, all of the time. Idling, the Pi uses a bit less than 3 watts. This means it would take two weeks to use one 1Kw/h of electricity.
 
If you pay e.g. 12.5 cents a unit, that's what you'd expect this to cost to run in a fortnight. That's around $0.25 a month or $3 a year. Green and cheap and helping to secure the BLK network. I paid for the year's worth of electricity in 2 days staking with 25k BLK. Makes mining look silly, huh? ;)
 
Securing your Pi
 
With staking, your wallet needs to be unlocked and as such, the keys to your wallet are on the device. In a clean and newly installed environment as described above, and if you don't allow others to use your device and there is no other software or nasties running on it, there is no real cause for concern. However, there are some basic security precautions you can take.
 
Firstly, if you have enabled SSH and are playing with your pi across your LAN (or worse, the Internet), you should immediately change the password for the default 'pi' user (which is preconfigured to be 'raspberry'). Simply log in as normal, then type:
 
passwd 
 
You'll be prompted to enter the old and the new passwords.
 
Security by default
 
Your Pi is likely, by default, to not be exposed to incoming connections from the outside world because your router is likely generating a private address range for your LAN (192.168.x.x or 10.0.x.x or 172.x.x.x) which means all incoming connections are effectively blocked at the router anyway unless you set up a 'port forward' record to allow packets arriving on certain ports to be forwarded to a specific internal IP address.
 
As for accessing your Pi across the internet, if you have set up a port forward, this likely has security ramifications. Even basic old fashioned protocols have proven in recent times to have uncaught flaws, so it's always advisable to lock down your device as much as possible, and even if you only plan to access the Pi over your LAN, install a firewall to configure this. I used one called ufw, because it's literally an uncomplicated firewall.
 
sudo apt-get install ufw sudo ufw allow from 192.168.0.0/16 to any port 22 sudo ufw --force enable 
 
This allows just port 22 (SSH) to be open on the Pi to any device on my LAN's subnet (192.168.0.x). You can change the above to a single IP address if paranoid, or add several lines, if you want to lock it down to your LAN and a specific external static IP address (e.g. a VPN service you use). To find out what subnet your router uses, just type:
 
ifconfig 
 
and you'll see on the interface you are using (either hard wired or wifi) the 192.168 or 10. or 172. prefix. Change the above rule so it matches the first two octets correctly (e.g. 10.0.0.0/16 if you're on a 10.0. address).
 
You may already use VNC to access your Pi's desktop across your LAN, this uses port 5900. Add a line like above to lock it down to an internal address. It's not a good idea to expose this port to the wider world because those connections are not encrypted and potentially could be subjected to a MITM attack.
 
You can query the status of the firewall like this:
ufw status 
 
And of course, try connecting remotely once you change the rules to see what works. You should consult the official documentation for further options: https://help.ubuntu.com/community/UFW
 
Back up & Recovery
 
There are again many ways to tackle this so I'll just speak about my basic precautions in this regard. Don't take it as a be-all-and-end-all!
 
The wallet.dat file is the key file (literally) containing all the private/public keys and transactions. This can be found in:
 
~/.lore 
 
You can navigate there using Jessie w/Pixel's own file manager or in a terminal window (cd ~/.lore). You can copy this file or, if you'd rather keep a plain text file of all your public and private keys, use the 'dumpwallet' command in the console. In Lore, go to Help > Debug Window > Console and type 'dumpwallet myfilename' where myfilename is the file you want it to spit out with all your keys in it. This file will end up in the same place you launch bitcoin-qt from.
 
The instructions earlier on, when running Lore for the first time intentionally left out encrypting your wallet.dat file because in order for the wallet to stake upon startup, it needs to have a decrypted key already. This isn't perfect, but after a power cycle, it would never stake unless you left it decrypted. So the best practice here is as soon as the wallet.dat file has left your device, i.e. you copy it to a USB stick for example, put it in an encrypted folder or drive (or both).
 
In Windows, one way is to use Bitlocker drive encryption for the entire drive. You should follow the instructions here to encrypt your flash drive before your wallet.dat is on there, and don't forget the password!!
http://infosec.nmsu.edu/instructions-guides/how-to-enable-bitlocker-to-go-for-external-hard-drives-and-usb-flash-drives/
 
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself: http://www.belightsoft.com/products/conceale   There are almost certainly free packages with similar functionality, I have just used that one for years.
 
Either way, if you want to just make sure your USB drive is encrypted, you can do so in one-click in Finder before you put the sensitive files on it: http://lifehacker.com/encrypt-a-usb-stick-in-finder-with-a-click-1594798016
 
Note that these disk encryption methods may mean having to access the USB stick on a PC or Mac in order to retrieve the files in the event of a disaster. Be aware this may mean exposing them to more security issues if your computer is in any way compromised or someone nefarious has access to your computer. There are more 'manual' ways of backing up and recovering, such as literally writing down private/public key pairs which this guide doesn't go into, but may suit you better if paranoid about your setup.
 
Recovery
 
The wallet.dat file has everything in it you need to recover your wallet, or if you used 'dumpwallet', the file you saved out has all the keys.
 
Wallet.dat method: Install Lore as normal then replace any auto-generated wallet.dat in ~/.lore directory with your backup. If a lot of time has elapsed and many transactions have occurred since your backup, launch lore with:
./bitcoin-qt -rescan 
 
And if that doesn't do the job, do a full reindex of the blockchain:
 
./bitcoin-qt -reindex 
 
If you used the dumpwallet command, install Lore then place the file containing all the keys that you saved out in the same directory as bitcoin-qt. In Lore, go to Help > Debug Window > Console and type 'importwallet myfilename' where myfilename is that file containing all the keys. The wallet should automatically rescan for transactions at that point and you should be good to go.
 
There are a million ways to do effective security and disaster recovery, but I hope this shows you a couple of basic precautionary ways. There are discussions about better ways to stake without compromising too much security which are happening all the time and developments in this regard will happen in time.
 
In the meantime, feel free to comment with your best practices.
 
submitted by patcrypt to blackcoin [link] [comments]

Mac/OSX Dev needed - get Lore to compile on OSX - receive 6000BLK ($3k) bounty

Dear fellow developer.
 
Good developers know their limits, and ask for help. So do I.
After playing for a week, maybe someone more skilled can play better game.
Lore has to compile on OSX. I have done a lot of patches on top,
to make it easy for you. Nothing is wrong in code, you don't have
to develop.. the issue is Qt and Xcode, everything other compiles, problem is the GUI.
 
It compiles on other OS(win, linux..)
Mac OS X should work too, but am making some blatant mistake
and am still not able to. I hope you stay a while with this super community we have.
 
The one that solves this puzzle will get 6000 BLK.
(pull request, with compilation instruction, we can meet on slack)
 
MacOs Sierra 10.12.5
XCode 8.3.2
 
Here is the codebase:
https://github.com/janko33bd/bitcoin/tree/Blackcoin-Lore
submitted by janko33 to blackcoin [link] [comments]

Trading DOGE: Your full guide to trading Dogecoin for profit

NOTE: YES! This guide is long, but when you get started it's fast and easy.
Hi everyone,
my previous post about PTC's got so much hate. So I decided to make a full guide on how I made $120 last month. If the same interest and numbers remain you'll be making $100/month for two months, and $500/month for another month. On your third month, you'll be able to make over $750 if the market remains. These last couple of days I've just bought low sold high to people. The steps are really simple and anyone can do it, I'll show you all the steps in detail for maximum profits.
Disclaimer: I am not responsible for your money or actions. Any accusations to me (Rynsi) will not be accepted, use it on your own risk!
1. Introduction
2. Get started with Dogecoin
2.1 Install your wallet
3. Choose trading sources
3.1 USD/BTC
3.2 BTC/DOGE
4. Where to sell Dogecoin?
5. Good advise
6. Summary
7. Proof of Screenshots for the naysayers
8. Links
1. Introduction
I started trading Dogecoin (I'll talk about this coin soon) 5th of February, and saw a great potential in making money with it. With this guide, you'll make 15%-30% of your money back with each trade because the current market is limited, therfor YOU can provite this service that many people request. I started with $72 and now have $220, which makes my ROI 205.5%. I will show you how it's made step by step before it blows up and become viral!
2. Get started with Dogecoin
You can use it to buy goods and services, or trade it for other currencies (both other cryptocurrencies or traditional currency like US dollars). By far the most popular use the Dogecoin however is for "tipping" fellow internet-goers who are creating or sharing great content. Think of it as a more meaningful "like" or upvote, with real value that can be used all across the internet.
2.1 Install your wallet
To start using Dogecoin, you'll need a wallet. A wallet is just like your online bank account, only your entire account is stored securely on your local computer or in the cloud. From your wallet you can send and receive Dogecoin, manage your address book and review a history of your transactions.
Desktop wallets can be downloaded and run from your computer's desktop. Desktop wallets are more secure as they don't rely on a third-party server in the cloud:
Windows (click to download)
OS X (click to download)
Source code(if you're using Linux, you'll need to compile the wallet yourself)
For Windows and OS X users, simply extract the .zip file to a secure location on your computer, then double click on "dogecoin-qt" to run. For information on how to use your desktop wallet, check out this great site.
3. Choose trading sources
You know now how to get a Dogecoin wallet, but you will need to get an online wallet to save USD on, one exchange site to trade USD to BTC and one to trade BTC to DOGE. It might sound a lot to do in the startup phase, but it's really easy once you get going!
3.1 USD/BTC Exchange
There are a lot of options when it comes to buying BTC, but for now VirWox is the only one that accepts PayPal and VISA purchases. You can choose many different kinds of sites that accept USD/BTC trades, that is another story that is another story to be told. VirWox has a limit of depositing $780 per month, but after 60 days you can deposit $2800 per month, so trading as much as possible will be the best thing to do if you want money.
USD Storage: PayPal
USD/BTC Exchange: VirWox (ref / non-ref)
To deposit dollars with (VERIFIED) PayPal to VirWox, you need to be a verified user. This is to prevent frautend actions such as chargebacks and instant payments. The deposit will be instantly made after you complete the order and you can start trade. To trade, you first have to buy SLL with the USD on your account [!!!WARNING!!!] USE LIMIT ORDER and NOT market order.
Now do the same, but with the SLL/BTC exchange. I repeat, do NOT use the market order. Use LIMIT ORDER to get as much BTC as possible.
You have now successfully completed a USD/BTC exchange!
3.2 BTC/DOGE Exchange
This step is almost similar to the previous Exchange, but this step is only with Crypto-currency (read Bitcoin and Dogecoin).
BTC/USD Exchange: Cryptsy (ref / non-ref)
To exchange to BTC, you need to withdraw your BTC from VirWox to Cryptsy. This is made in the Cryptsy balance page, where you can generate a BTC deposit adress. Unfortunately, you have to wait 48 hours the first time for VirWox to accept your deposit manually due to security reasons, all the other transactions in this guide will be almost instant.
Now when you have BTC on your Cryptsy account, you have to do the same as you did with USD/SLL and SLL/BTC, really easy! When you have traded to DOGE, your downloaded Desktop Wallet comes in handy. Deposit the DOGE from Cryptsy to your Desktop Wallet and you're ready to go to the next step!
4. Where to sell Dogecoin?
This is a great surprise I have waited to tell you, you use REDDIT to sell Dogecoin! It's really easy to do. Go to /dogemarket/new and see what the current prices are. You can sell for the same price as others, undercut for faster sales or overcut for slower sales (but bigger profits!). You structure the post by [SERVICE] AMOUNT RATE PAYMENT TYPE (SPECIAL OFFER). Here is an example, my last post where I sold Dogecoin. If you follow my conversation in that post you will see how typical trades are being made.
When you have traded the Doge you can make a post on the /dogemarket verification thread where you achieve levels that will be shown for other users through your flare. Notice the orage flares, those indicate level of trades, age and amount you have traded. These are good for noticing legit and fake users, but always be of scammers!
5. Good advise
A. Only accept GIFT (friends and family option) from (VERIFIED) PayPal, DO NOT accept eChecks or transactions that has to be accepted first. eChecks and Instant payments can be chargebacked and gifts will prevent this from being possible.
B. If you have reached VirWox deposit limit, wait a while to see how the BTC/DOGE market is going. You might make some extra 1000's of DOGE if you wait a while.
C. Always be nice and kind to the DOGE community, they are really friendly, patient and polite, be so too!
D. Try to be fast in your transactions on /dogemarket, good service equals good reviews.
E. PEOPLE WILL TRY TO SCAM YOU! Always check for names including "shibe" or "doge" and new accounts.
F. Have fun! If you have fun trading and communicating with other people on Reddit, you will enjoy yourself and have a better time making money.
6. Summary: A step by step guide to make $100+/month
(and $500+/month after 60 days if market remains)
Download your dogecoin wallet.
Sign up to PayPal, VirWox and Cryptsy.
Add money to your (VERIFIED) PayPal account.
Deposit the money to VirWox.
Exchange money to SLL.
Exchange SLL to BTC.
Withdraw BTC to Cryptsy.
Exchange BTC to DOGE.
Withdraw DOGE to Desktop Wallet.
Make a post on /dogemarket.
Recieve PayPal money from buyer.
Send Dogecoin to buyer.
7. Proof of Screenshots for the naysayers
PayPal Proof
VirWox Proof
Cryptsy Proof
Desktop Wallet Proof
As if you haven't seen the whole iceberg, here is my reddit verification post
8. Links
Dogecoin Promotional video(a must watch)
Dogecoin Subreddit
Dogecoin Official website
Bitcoin Subreddit

Bitcoin Official website

This is my first guide: making over $100/month with a $72 investment. When your VirWox account is 60 days you'll make $500/month and when your VirWox account is 90 days you'll make $750/month (if market remains as it is).
I think it's a big effort by me trying to teach you how to make money, so I would really appreciate you using the referral links. If you find any errors in my guide, please don't hesitate to tell. I will be answering any questions regarding my guide as good as possible doesn't matter if you comment or PM.
I'm accepting any donations,
DHKzSsCVpv5QuJvHxWKENH9SKC3S58raBx
Thanks.
TL;DR Wanna be rich? read.
Edit: Formatting
submitted by Rynsi to beermoney [link] [comments]

Cannacoin 0.8.7.1 Updates coming soon! Development/Beta Support needed!

I have been working hard on updating the Cannacoin protocol/client to version 0.8.7.1 (to be called Version 2.0) which will bring us up to date with crypto standards and also patch OpenSSL heartbleed. Following open source standards I want the new updates to be public and available for peer review before implementing. If there is anyone with development backgrounds or with history working with the Bitcoin/Litecoin/Cryptocurrency protocol that wish to help with build support and testing please contact me to join to project. As it stands, the source is completed and builds are compiling without problems, we just need some more eyes and people that have a technical background who can help with build support. Here's a few sneak peeks to get you excited for what's to come:
Edit: Here's some notes from the teams development log as it pertains our Cannacoin 2.0 protocol/wallet updates. (as of 5/24)
Completed:
To Do:
Note: The "Cannacoin 0.8.7.1" github repoistory will be merged alongside the main "Cannacoin" repoistory as a seperate branch (Version 2.0.0.0) after peer review.
submitted by SubCreative to cannacoin [link] [comments]

QuarkCoin Daemon in OS X

QuarkCoin is a crypto-currency, a fork of bitcoin.
I like it because:
*) Must faster block time, ~ 30 seconds
*) CPU mining, ASICs can't do it and it is doubtful they ever will
*) Coin supply is not capped, which discourages hoarding
-=-
Right now you should consider it to be play money, don't go selling your house and dumping it into QuarkCoin. Most derivatives of bitcoin ultimately fail.
But anyway - while there is a GUI qt client for quarkcoin, there is not an official headless daemon release, and me - I like headless, I'm a Linux guy at heart and I like to be able to have it start / stop via the crontab.
Patches to get the daemon to build in OS X are here, written by me:
http://www.domblogger.net/puzzle/q/
make test currently fails, but not because of the daemon - but a bug in the test code (Xcode c++ compiler is very strict and not very forgiving)
There's also a shell script in that directory to aid in controlling the daemon.
What I do is put the daemon and shell script in ~/bin/ and then use the cron daemon to start the daemon every hour on the hour and stop the daemon at 45 after the hour. With iMacs etc. Apple didn't design them for constant CPU use so you don't want the daemon mining 100% of the time or eventually it could damage your hardware.
Watch your CPU temps and adjust how long you let the daemon run accordingly.
To build it - okay you need Xtools with the command line stuff installed. I used MacPorts for other dependencies.
Those other dependencies being:
sudo port install boost [email protected]+no_java openssl miniupnpc
The QuarkCoin source is at https://github.com/MaxGuevara/quark
Get the zip, unpack it, apply the two patches, and then you can build it by going into the src directory and typing
make -f makefile.osx
-=-
Not trying to sell any doubters on QuarkCoin - just providing patches for those who want to play with it on OS X and would like to use the headless daemon instead of (or in addition to) the official qt GUI client.
The quark homepage : http://www.qrk.cc
I'll try to help anyone who is trying to build this and is having trouble, but keep in mind I'm a Linux guy, not an OS X guy. Just happen to currently have access to a Mac running OS X.
submitted by AliceWonderBTC to osx [link] [comments]

Unable to use any Invictus apps. Can someone help?

I posted my original question here: https://bitsharestalk.org/index.php?topic=2735.0 and followed the instructions here: https://bitsharestalk.org/index.php?topic=1936.0 but my ProtoShares-Qt-0.2.0 for Mac OS X app will not connect to any nodes. My firewall is off and I am able use other Qt clients just fine.
What app should I use to get a ProtoShares wallet that works? Is ProtoShares even a thing anymore or is it AngelShares now? Or BitShares? Or BitShares X? What's with this naming scheme? Who is doing the marketing for Invictus? I fix Macs for a living and I can hardly figure out how any of these products relate to each other.
In an attempt to see if I could get any Invictus app to work for me I have visited the Invictus site and GitHub but have been unable to find an installer or .dmg file for any Invictus app that "just works". Are there no Invictus apps that just function out-of-the-box after a simple download and drag and drop into the Applications folder on my Mac? Do all Invictus products require the user to compile the software themselves? If this is the case can a forum moderator or Invictus employee provide with a link to a working version of ANY Invictus app that will function on a Mac?
Perhaps it is just easier to just purchase some ProtoShares with Bitcoin on Cryptsy and forget trying to use any of Invictus' software. Of course that is problematic too because I still need to get my PTS off Cryptsy at some point. As I asked before, is ProtoShares even the right thing? Or should I buy BitShares?
Halp!
submitted by cryptoearly to protoshare [link] [comments]

Toolchain Setup - Installing Qt on MacOS Rick Astley - Never Gonna Give You Up (Video) - YouTube LagerMaschinen.de - YouTube

Bitcoin is a popular cryptocurrency, which is a form of electronic cash, in which a ledger of all transactions is stored as a blockchain. In this article we will show how to compile your own local copy of the Bitcoin client, run it, and add custom commands in order to inspect various attributes of the underlying blockchain. Bitcoin Core is both a daemon also a Wallet client. A fully functioning node must have the Bitcoin Core (formerly Bitcoin-Qt) daemon running on a machine instance with the complete block chain downloaded.Note that this speed-up is no longer be needed for Bitcoin Core version 0.10 (click here for Bitcoin Core version history) and above because blockchain syncing is paralleled across multiple ... Bitcoin Core is a community-driven free software project, released under the MIT license. Verify release signatures Download torrent Source code Show version history Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ Qt Bitcoin Trader. This software helps you open and cancel orders very fast. Real time data monitoring. Developed on pure Qt, uses OpenSSL, AES 256 key and secret protection. I want to develop this Trader App so that it can be configured for any rule and strategy. Next ToDo: - Add realtime charts - Make rules more advanced. Official website We’re going to run the GUI version first, called bitcoin-qt, then we’ll exit it and run the non-GUI version called bitcoind, and then back to bitcoin-qt, with some steps and configuration in between so you can understand what’s really happening and feel comfortable starting and stopping the software when you need to.

[index] [4665] [20348] [10781] [16070] [2349] [4520] [544] [13065] [5897] [29525]

Toolchain Setup - Installing Qt on MacOS

This video is unavailable. Watch Queue Queue. Watch Queue Queue Rick Astley's official music video for “Never Gonna Give You Up” Listen to Rick Astley: https://RickAstley.lnk.to/_listenYD Subscribe to the official Rick As... Setup PyQt5 Environment with QT Designer on Mac OS X - Duration: 8:33. Ssj6 857 views. 8:33. Qt Install Mac - Duration: ... Compiling OpenGL SuperBible Code - Duration: 13:32. Jens Hannemann 40 views. Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

#