How to remove BitCoin Clipper - virus removal instructions

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

[PSA] Dogecoin Wallet version 1.4 released. You must update.

WARNING: DO NOT send your wallet.dat file or dogecoin folder to anyone. There have been reports of people offering to help others by asking them to send their files to them so they can help. DO NOT do this. Scam attempt picture
Always encrypt your wallet! I can't express this enough. You should use a strong password longer than 15 characters. This password should contain numbers, symbols, and some capitalization! There is no need to have your wallet open 24 hours a day. Open it only when you need it. See - 'Getting Started' on the side bar.
This entire post has been written to be as close to ELI5 (Explain it like I'm 5) as possible - By request! If anyone wants to add/fix/correct anything in this message, please send a message to the mods <<-- Click blue text.
All blue text in this post can be clicked on. The blue text is a link to a picture, site or download file.
A very important message/reminder below.
25 Jan 1.5 pre-releases have started.
http://www.reddit.com/dogecoin/comments/1uhpwf/dogecoin_for_mac_14_topic_thread/
OLD VERSIONS The 1.4 update for the dogecoin wallet has been released. This update addresses the block chain error that occurred. This update is mandatory meaning you have to do this update. Also further down the page you can read up about the block chain. You MUST make sure you're on the correct block chain and the old block chain has been removed.
For a Windows computer the version must be 1.4. - 1.4.1 just released! See below
For a Apple Mac Computer the version must be 1.4
Download links:
[Windows Download Link](https://github.com/dogecoin/dogecoin/releases/download/1.4/dogecoin-qt-v14-Win.zip) <<--Click to start download
Windows Download Link 1.4.1 UPDATED 19JAN
Mac Download Link <<--Click to start download
Mac users can join this thread if there are any problems
Android (phone): Please see This post
To update, simply download the new version from the download link above. Open the downloaded file and extract the contents of the downloaded file into any new folder or location on your computer. If you put the files into a folder you can name the folder anything you want but make sure you remember that this is the latest version of the software.
You don't have to remove your folder containing the old version of the wallet. You can place it in a folder called 'Old versions of dogecoin wallet' if you like.
Now you can click on the Dogecoin icon contained in the new folder to open your version 1.4 wallet.
What happens if I get an error when I open the new wallet?
An error was reported called "11DbException"
If this happens Download this file and place it in the same folder as your updated wallet. Open the file you just downloaded called "Dogecoin OPEN' and wait. This might take 2 or 3 minutes.
Also jtlarousse has found a solution that worked on Windows. Please follow carefully and make backups before starting.
Reebzy might have found a solution for Apple Mac
Blockchain fork 101: The block chain is a ledger or document created containing every transaction that has ever happened. This file can be quite large. Bitcoins ledger is over 15GB. At some point this document/ledger split into two separate documents known as a fork.
How do I know if I am on the right block chain?
Go to your newly updated dogecoin wallet and open it. Click on Help>>Debug next Observe the current block number
*Note the example numbers in the pictures might be out of date by the time you read them
Now go over to http://dogechain.info/chain/Dogecoin . This website is the official Dogecoin blockchain website. Check the block number they're reporting
The number you found in your wallet and the number reported on the website should close. There might be a difference of 100 blocks depending on when you last refreshed your wallet or how long it took for you to get from one step to the next step in this guide and if the dogechain website is lagging.
I'M NOT ON THE CORRECT BLOCK CHAIN
My numbers are very different. How do I get back onto the right block chain?
IMPORTANT
For windows:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: C:\Users[your windows log-in name]\AppData\Roaming\DogeCoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
For Apple Mac:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: ~/Libarary/Application Support/Dogecoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
Next visit this post by Netcodepool for instructions on how to manually download the correct block chain and install it.
Much Thanks. 
Edit: Some posts were removed from this thread. To limit confusion.
Check this post for details about mining pools that were/are using the wrong fork.
Did you send coins only to find out you're on the wrong chain? See this post to get them back
An Apple Mac support thread has been made by voidref (The mac developer). If you're having troubles please see this thread
Some shibes have reported their wallets wont sync. Please check to make sure your firewall, antivirus, malware scanner or similar programs are not blocking it the wallet. You can add rules to these programs to allow the wallet to make contact with the internet. It's not advised but possible to also disable the software for a short amount of time. Don't forget to enable the software again afterwards.
Is your wallet crashing? Try this helpful tip from gandhikahn or if you're using windows try the 1.4.1 update above.
submitted by 42points to dogecoin [link] [comments]

Run a 0.14 Full-Node on RaspberryPi3 Pruned(less than 16GB SD needed)

Hi!
Happy if this guide helps you.
Tip if you want: 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v
UPDATE 04/06/17
Add 'uacomment=UASF-SegWit-BIP148' into your bitcoin.conf if you want to signal UASF.
UPDATE 03/13/17
ADDED a tl;dr; Version at the end of this Post.
UPDATE 03/12/17:
Just to test it - I reinstalled all on 8GB SD and it works as well. But maybe you should use at least 16GB for the beginning.
Using a 128GB card for the first version was a little bit stupid - so I reinstalled everything on a 8GB SD card. Including Linux and a pruned blockchain - and it works.
I used prune=550 and Jessie Lite (headless / command line) - without wallet and gui.
The SD is almost full, but it works so far
I also updated the whole manual a bit to make things more clear. Thank you for all your feedback!
Just started my Bitcoin Node today and wanted to share the way I did it with people who are interested in running their own full node. It took some time to write everything down - hopefully correct so far.
I am sure, many people around bitcoin are way more informed and educated as I am - I am the noob. So I wrote this manual to help users like me - noobs, to get started with a cheap, simple bitcoin node on raspberry pi.
Have fun!
I wanted to get my Raspberry Pi 3 working as a node to support the network. Actually the process of installing and running the node was more or less easy - but for Noobs (like I am) it might be a bit tricky to start the whole thing, because there are different ways.
Did you - like me - think you would need +120GB on the raspi, external USB HDD to be a full node? You won't!
If you have a Raspberry and you know what Bitcoin is, I guess, you are a little bit aware of linux, networks and of course bitcoin - so I won't go into detail too much.
This guide is just a little helper to get a full node running on your raspberry pi. Thanks to the help of the nice people in this sub and of course the documentation by the developers, I got it working - and of course also special thanks to raspnode.com - as I followed their tutorial to start - I went some other ways here and there - so please read carefully.
For the Part 2 I would suggest to have http://raspnode.com/diyBitcoin.html open and read through my manual.
I split the tutorial in 2 Parts - PART ONE is about installing the client on your PC and downloading the Blockchain.
PART TWO is about the setup of the raspberryPi and transferring the pruned blockchain to the pi and run it as a full node!
The first thing to be aware of is: You actually need to download the whole blockchain to get this working - if you already have your bitcoin client synced on the PC / MAC great you can reuse it!
Now you might think "but you said less than 16GB in the title!"
Yes, but the good thing is you won't need to download it on your Raspberry, neither you need to sync it completely on your raspberry which took ages (weeks!) before. When you finished this Guide, you will just have a max. 4GB Blockchain on your Raspberry Pi - but it still is a full node! The magic word is Pruning.
Maybe even a 8GB SD Card works just fine including Linux (jessie lite)!
So, if you already have a full node on your PC - Great you can almost skip PART ONE - BUT have at how to Prune in PART ONE if you don't know about it.
For PART TWO you'll need a Raspberry Pi 2 or 3 (I used 3) min. 8GB (works also) or better 16GB SD Card. (I used a 128GB for the first version of this manual - which is way too big)

PART ONE

This is the manual how to get started on you PC / MAC / Linux (I did it on Win7)
Go to: https://bitcoin.org/en/download and download the core Client for your Machine (I used win64).
Install it and configure it to save the Blockchaindata to the directory of your choice - so instead getting 120GB on your C drive, I would suggest to download it to another place like a USB drive.
You can set this up during the install. Standard folder for the blockchain folder is "%APPDATA%\Bitcoin" on Windows.
or you can do it after the install by creating a bitcoin.conf file inside your installation folder / or %APPDATA%\Bitcoin and add
datadir=l:\yourfolder
to the file. Line by line.
By the way here you could also just add dbcache - to use more memory to speed up the process a bit:
dbcache=4096
if you don't want to use the settings inside the program. (you can also set this inside the program under settings! If you have this inside the bitcoin.conf you will see the amount you set there from inside the program - it overrides the values)
You can check inside the windows client under settings, if you can see a manual dbcache is set by having a look at the left footer area. When your dbcache value shows up, everything is fine.
So the Blockchain download process will take time - maybe a few days! Depending on your machine, internet connection and HDD.
The Blockchain is huge as it contains every single transaction of the past until today. You won't need to keep your PC running all the time, you can turn it off and on and it will resync automatically when you start bitcoin-qt.exe!
Make sure to close the client always via "quit" - ctrl+q.
After you have your bitcoin core installed, the blockchain downloaded and synced - you are ready to PRUNE!
First - close the Client and let it close smoothly. After it is really closed you can follow these steps:
By pruning, your blockchain will dramatically shrink. From 120GB to just a few GB.
Be aware, that you will lose your Downloaded Blockchain as pruning will erase a big chunk of it! If you have enough space, you could of course keep the full blockchain saved somewhere on another HDD.
You can prune by editing your bitcoin.conf file by adding:
prune=550
I used prune=1024 - not sure where the differences are right now (min. prune=550). (for my 8GB version I used 550! I suggest to use this.)
Save the bitcoind.conf file and restart your windows client.
It will now clean up the Blockchain. So just the latest blocks are saved. The client should start without any problems. Maybe it takes some time to prune the blockchain data.
Check if everything works normally (the client opens as usual, you can see an empty wallet) than close the client.
Inside the Bitcoin Folder, you'll find two folders called:
blocks chainstate
those are the interesting folders containing the important data (now pruned) - and we will transfer those two to the raspberry later!
Now you are good to start the raspi transfer explained in the next part.

PART 2

Here is what I did:
1) I installed Raspian Pixel (https://www.raspberrypi.org/downloads/raspbian/) using a 128 GB SD - which is not needed because of "Pruning" - I think a 16GB card might work, too! (You can also install Raspian Jessie Lite - which saves you even more space, as it runs headless - only command line) (Updated: It is better to use Jessie Lite to save a lot of space - when you are fine with only command line)
2) I followed partly this tutorial to get everything running and setup:
http://raspnode.com/diyBitcoin.html
Please have a look at it - I have copied the Headlines in capitals to let you know what I did, and what I skipped.
On Tutorial Page: Start with RASPBIAN (OPTIONAL) CONFIG OPTIONS.
Set You RasPi up including "EDITING FILES" to save your Layout at the tutorial page and come back here.
I skipped the CONFIGURE USB AND SET AUTOMOUNT process, as we are going to use PRUNING to reduce the 120GB to a tiny filesize - so USB Devices are not needed here!
It was necessary to ENLARGE SWAP FILE to install bitcoin core - otherwise it didn't went through which ended in a frozen raspi.
So have a close look by following the raspnode tutorial at: ENLARGE SWAP FILE.
I have my raspi running via cable to router - but you can also WiFi setup everything described under NETWORKING ON THE RASPBERRY PI.
Now comes the interesting part: Follow the steps at DOWNLOADING BITCOIN CORE DEPENDENCIES - they work fine for 0.14.0 too. Git should be on Board already when you installed Pixel - otherwise you would need to install it.
sudo apt-get install git -y (only jessy lite)
I skipped the next command lines - as I don't use bitcoin-qt wallet. If you want to use it as wallet - do the step.
mkdir ~/bin cd ~bin
Now you are in the folder you want your bitcoin core data be downloaded to via git. I didn't Downloaded the Berkeley Database source code - so I also skipped the whole next command lines
[email protected]~/bin$ wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz [email protected]~/bin$ tar -xzvf db-4.8.30.NC.tar.gz [email protected]~/bin$ cd db-4.8.30.NC/build_unix/ [email protected]~/bin/db-4.8.30.NC/build_unix$ ../dist/configure --enable-cxx [email protected]~/bin/db-4.8.30.NC/build_unix$ make -j4
and went on with "INSTALLING BITCOIN"!
I followed the first part but instead downloading 0.13 I took of course the latest version:0.14
git clone -b 0.14 https://github.com/bitcoin/bitcoin.git cd bitcoin ./autogen.sh
this might take some time to start.
If you have trouble with hanging RESOLVING DELTAS - just restart the Raspberry Pi and remove the bitcoin folder inside /~bin using
rm -rf bitcoin
this command will delete the folder and you can reuse
git clone -b 0.14 https://github.com/bitcoin/bitcoin.git

For some reason RESOLVING DELTAS is a common problem with different downloads - so just retry it and at least after 3 times it should work!

as I didn't use the GUI/ Wallet, I ran
./configure --enable-upnp-default --disable-wallet
as I don't need the wallet functionality.
I didn't need to use "MAKE" which saves you maybe up to 2.5 hours.
instead you can just go ahead with:
sudo make install
(If I am wrong in doing so - please let me know)
The install takes some time - and just a heads up: when it gets stuck somewhere - just redo the installation process - it took three times to went through - stuck at some processing.
After the installation took place you can finally get your Raspberry Pi Node running in no time!
To test if the the installation went through - you can just start bitcoind using:
bitcoind &
than check if everything is working so far:
bitcoin-cli getinfo
after a few seconds you should see version: etc...
if not, something went wrong. Try to redo the steps in the raspnode tutorial.
(don't give up if it failed - retry! Ask your questions here)
IMPORTANT: you need to stop bitcoin on your raspberry now!
bitcoin-cli stop
If you don't need an external USB Drive - what I hope - as we are going to use pruning just go ahead and skip the USB part and create a file inside (or follow the raspnode tutorial on how to setup the USB drive):
cd .bitcoin
sudo nano bitcoin.conf
and enter the exact same pruning size you have used on your Desktop Machine to prune. I used 1024 but the minimum is 550. (used 550 for the 8GB SD card on PC and Raspberry)
prune=550
That's it for the raspi.
update: To signal UASF enter in a new line:
uacomment=UASF-SegWit-BIP148

TRANSFER

Now you have to transfer the two folders CHAINSTATE and BLOCKS from your PC bitcoind directory to your raspberry.
I am using a program called "WINSCP" - it is free and easy to use: https://winscp.net/eng/download.php
We need this to transfer the files to the Raspberry pi. Pretty sure you can also do it via SSH - but I am the noob. So let's keep it simple.
Open Winscp and put in the IP Address of your Raspberry Pi, User and Password (same as in SSH)
You should now see the directories on your Raspberry Pi. There is a folder called
.bitcoin
enter it and you will see the two folders
blocks & chainstate
you can delete them on the raspberry as they have some data from your previous test inside.
Make sure you can also see the bitcoin.conf file in that directory, which needs to contain the exact same prune line, like the one on your desktop machine. If not, make sure to edit it via SSH. The line "datadir=l:\yourfolder" is obviously not needed in the Raspberry bitcoin.conf file.
Now grab the two folders CHAINSTATE and BLOCKS from your PC and copy them to your .bitcoind folder.
I also copied banlist.dat, fee_estimation.dat, mempool.dat and peers.dat to the folder - not really knowing if needed! Not needed.
The whole copy process might take some minutes (against some weeks in the old way).
After copying is finished, you can now start bitcoind on the Raspberry.
bitcoind &
the & symbol let you still use the command line while the process is running btw.
The process - if succesfull - will take some time to finish.
bitcoin-cli getinfo
Will give you some informations what is going on right now. When you can see, that it is checking the blocks, this is good!
If you get an error - double check - if you have the correct prune size (same as on desktop machine) - in bitcoin.conf and that this file is inside .bitcoin on RaspberryPi. It took me some time, to find my mistakes.
Congrats! You are almost a part of the network!
To make your node now a fullnode, you will need to go to your router (often 192.168.1.1) and enable portforwarding for your raspberry pi - and open ports 8333 - that's it!
You can now go to: https://bitnodes.21.co/nodes/
scroll down to "JOIN THE NETWORK" and check check if your node IP is connected!
It will show up as soon as the blocks are checked and the raspi is running.
Well done!
Now you are running a full node, with a small Blockchain and got it working in Minutes, not weeks!
I really hope, my little tutorial worked for you and your are part of the Node network now.
If you have problems or I made a mistake in this helper tut, just let me know and I will try to make it better.
Have fun and NODL!
the noob
tl;dr; (if you are a real noob start with the non-tl;dr version!)
tl;dr; PART ONE
1) Download & install / setup bitcoincore @ https://bitcoin.org/de/download
2) change dbcache to something smaller than your memory and download the whole Blockchain (120GB).
3) create a file called bitcoin.conf put the line prune=550 (or higher) in to activate pruning on win inside %appData%/bitcoin
4) Open ports 8333 on your Router to make this a full node with a smaller Blockchain.
You are running a full node on your PC.
tl;dr; PART TWO
1) Install jessie lite and the needed dependencies on your SDCard - Raspberry
( >git clone -b 0.14 https://github.com/bitcoin/bitcoin.git )
  • see tutorial for more info.
2) create a file called bitcoin.conf inside .bitcoin and add the same prune=Number you had on your PC.
3) transfer the pruned folders BLOCKS and CHAINSTATE to the Raspberry Folder .bitcoin
4)Start "bitcoind &"
5) let everything sync
6) Make sure you have port 8333 opened on your router.
You are running a full node on your Raspberry with a super small Blockchain (I put all on a 8GB SDcard)
Tip if you want : 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v
updated 03/12 - will update more, soon.
updated 03/12.2 - I updated the whole process a bit and also added some improvements.
updated 03/14/ Added a tl;dr version at the end.
submitted by I-am-the-noob to Bitcoin [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]

[Social X] Architecture of A Decentralised System for Social Payment and Services

Dear fellow Reddheads:
It's been a month since the successful launch of PoSV, which marked the end of stage one of Reddcoin project. There were three main goals for stage one:
  1. fair distribution of Reddcoin to common users (tipping), miners (mining) and investors (IPCO).
  2. an innovative algorithm to secure the network and encourage ownership, participation and decentralisation (PoSV).
  3. to build out a team of super talented and trustworthy developers.
The three goals have all been achieved so it's time for us to enter stage two: the buildout of services to make Reddcoin actually useful. This is what Social X is meant for. I'm still polishing the whitepaper to make it live up to my own self-imposed high standard, but I think the time is right for me to unveil it in broad strokes. There are three main problems Social X aims to solve.

Social X: why are wallets so difficult to use?

To achieve wide adoption of Reddcoin (or any cryptocurrency) by the non-tech-savvy general public, wallets must solve the following issues:
Ever increasing blockchain size discourages users from running full-blown wallets. It takes too much time and efforts to install or repair. A common user tends to find the process frustrating or even impenetrable and is forced to either give up adoption or rely on 3rd-party service providers (e.g. exchanges, wallets using ReddAPI) to take full control of her fund. Blockchain size grows everyday and grows faster with wider adoption.
Current wallets generate private keys randomly. As a user engages in staking or normal transactions, she has to back up wallet.dat file periodically to make sure all newly generated private keys are backed up. If wallet.dat file is corrupted or lost, there is no way to recover lost fund.
Again, due to the fact that private keys are randomly generated, it's impossible for a user to share the same wallet.dat file across multiple devices (e.g. desktop, iOS, Android) and multiple platforms (e.g. Windows, Linux, Mac). Different copies of wallet.dat will get out-of-sync. A user has to manage each wallet independently, which leads to significant operational burden and risk.
It would be extremely valuable for a service provider, such as an exchange or e-commerce site, to be able to generate unique public keys to receive fund while putting the corresponding private keys in cold storage. The impact on security is significant.

Social X: why is it so hard for me to tip someone?

One essential feature of Bitcoin is pseudo-anonymity. To pay someone, you need to get hold of her impenetrable public hash key, somehow. And the hash key, i.e. the wallet address, may not be valid a moment later because the owner might have lost the corresponding private key. Ironically, this awkwardness, even backwardness, is not perceived as a disadvantage by almost all the cryptocurrencies. In fact, on the contrary, the single biggest, hottest, most wanted feature is full decentralised anonymity, which has seen the rise and fall of many cryptocurrencies and their copycats. While all the other cryptocurrencies compete with each other on this front, Reddcoin, aiming to the social currency of the digital age, moves in the opposite direction. Social lives are not possible without social identities.

Social X: why can't I use a service without giving up control?

The vast majority of 3rd-party service providers which hold fund on a user's behalf has exclusive full control of her private keys. If a service is indeed worthy, a user has no choice but to trust the 3rd party with security and integrity. It's ironic, to say the least, that cryptocurrencies which are created to remove exactly this need for blind trust in middlemen end up in a much worse position than fiat currencies due to the fact that many cryptocurrency companies are unregulated and incompetent. Then the question is: is there a way to create an ecosystem where anyone can write and provide valuable social applications in a fully decentralised fashion?

Social X: Architecture for a Decentralised System for Social Payment and Services

Social X has many components which are already being actively developed. Below I give a brief description of some of them.
  1. In the future, there will be two types of official Reddcoin wallets. QT wallet and reddcoind are full wallets required to run a full node. A second type of wallets, called thin wallets or SPV wallets will use the technology of Electrum modified and enhanced to support PoSV and staking. These wallets include mobile wallets on iOS, Android, next-generation Social Wallet on desktop and wallets inside browsers (Chrome/Firefox/Safari). I've already finished writing and started testing the reference implementation of Reddcoin Electrum server and client. Each client only needs to download 25M of data vs the current full blockchain at 660M. This is how we solve the blockchain size problem.
  2. All our official wallets, whether full or thin, will be deterministic. All private keys are generated deterministically from a long passphrase. This passphrase is all you need to remember and backup and with it you can fully recover your wallet and funds anytime anywhere. You will also be able to support multiple wallets on multiple platforms and devices and they will all be in sync. This is how we solve the portability problem.
  3. All our official wallets, whether full or thin, will be hierarchical. They will allow users to generate public keys on demand while keeping private keys in cold storage. This is how we solve the cold storage problem.
  4. I'm writing code (~30% finished) for sth we call Reddcoin Social ID (Redd-ID):
    • It's a new service provided at the blockchain level.
    • It allow users to associate a username with one private key.
    • The user can choose to bundle extra information such as email, address and avatar.
    • The information is public and embedded in the blockchain. As a result, any user can send Reddcoin to another by simply specifying the recipient's Redd-ID.
    • Redd-ID registration costs Reddcoins. The costs vary depending on many factors such as the length of the username. For example, we expect popular names like tom to cost at least 7 figure.
    • Redd-ID registration is verified in PoSV blocks. Therefore all active Reddcoin stakers will be the provider of Redd-ID service.
    • Redd-ID registration fee goes to the Reddhead who successfully mints the PoSV block that verifies and confirms the registration. In a sense, it will feel like a lottery. And this is why this service doesn't make sense for any PoW coin where each block is pool-mined.
    • Redd-IDs can be transferred to new addresses and by default auto-expire annually and can be renewed.
    • Small Reddcoin holders, as long as they keep staking, may double, triple or 10x their existing holdings just by receiving registration fees.
    • Businesses and organisations can register usernames for purposes like receiving donation.
  5. There will be several services available to provide more ways for Redd-ID to be used on Internet. I don't want to disclose all our cards here. Please wait for my whitepaper and see what we have for you as surprises. Meanwhile, do share with us how you imagine Redd-ID can be used.
  6. Different components of Social X will allow decentralised tipping across all social networks. In our next-generation social tipping platform, there will be no tipbots! When you tip someone on Reddit, Twitter, Twitch, Youtube or Facebook, the tipping goes straight from local wallet, whether on your mobile or desktop to the recipient.
  7. There will be APIs to allow 3rd parties to write and offer decentralised social applications.

Social X: where are we now?

  1. I'm finishing the whitepaper in coming weeks (while writing a lot of code). The whitepaper will contains much more information than this post.
  2. Reddcoin Electrum wallets for iOS and Android are being actively developed.
  3. Reddcoin full wallets (QT/reddcoind) are already hierarchical deterministic in the development branch and are being internally tested.
  4. The Social Tipping Platform is being actively developed.
  5. I need volunteers to host and test Reddcoin Electrum server and clients. I'll make a separate post next week.

Epilogue

Below I'll only answer questions selectively. Much more details will be available in the whitepaper and there is no reason to jump the gun and repeat it here. Stage one took us 6 months. We expect stage two to take 6 months also. It may be the most exciting period in the history of Reddcoin project.
Regards
laudney
submitted by laudney to reddCoin [link] [comments]

Dogecoin 1.5.1 Released - Upgrade Now!

We’re happy to announce the release of Dogecoin version 1.5.1!
This release incorporates a range of updates from community contributors, some much needed bug fixes, plus some cool treats brought down-stream from the recent Bitcoin 0.9 release candidate.
Thanks to everyone who helped make this release possible, the entire community appreciates it. We recommend all users update to the latest version and please report any issues you may encounter. As always, backup your wallet.dat file before updating (just to be safe).
Downloads: Windows Installer Windows Archive Mac OS X App
Release highlights: - Switched to Boost 1.55 to fix network connectivity issues on Windows - Removal of reliance on IRC for discovering nodes - Support for URL protocol, eg. dogecoin:addr?amount=xxx&(see Bitcoin’s implementation) - Ability to automatically look up transactions on Dogechain from your client - Working Windows setup script and installer - Opt-in debug logging via -debuglog (to save disk space and stop constant writing) - Fixed Mac Splashscreen’s greedy desktop behavior - Reimplemented testnet, fixing RPC crash due to no genesis block being present - Allow user to load any wallet from data directory specified using -wallet=mywallet.dat - Updated to LevelDB 1.15 to address blockchain database corruption issues - Allow user to send change only to specified address(es) using -change= (one -change parameter per address) - Fixed RPC difficulty look up
Troubleshooting
If anyone experiences issues, delete all 1.4 data (apart from your backed up wallet.dat file) and do a fresh 1.5.1 install.
Enjoy!
submitted by Laika1954 to dogecoin [link] [comments]

PIVX Core v3.0.6 released (November 30th) - Optional Upgrade

Github release info and binaries
Forum Post
Important information about the automint and zPIV backup requirements

How to Upgrade

This release is optional but recommended. The latest mandatory upgrade is v3.0.5.1, but if you have any problems with earlier versions the latest version is recommended.
If you are running an older version, gracefully shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/PIVX-Qt (on Mac) or pivxd/pivx-qt (on Linux).
There are no special steps needed like config file changes but a backup is always a good idea.
A note from presstab in case it gets buried in the comments
Command line install and upgrade guide

Notable Changes

(but you should still read the release notes on Github)

Automated Database Corruption Repair

There have been cases of blockchain database corruption that can occur when PIVX client is not closed gracefully. The most common cases of corruption have been identified and the wallet will now automatically fix most of these corruptions. Certain corruption states are still unable to be fixed, but now provide more detailed error messages to the user as well as prompting the user to reindex their database.

More Accurate Error Messages

Some error messages in the wallet have been too vague and done little to help developers and the support team properly identify issues. Error messages have been refined and are now more specific.

Reduction of Debug Log Spam

Many 3rd party services have reported that their debug logs have been overloaded with messages about unknown transaction types. This log spam has been fixed.

Removal of Heavy Running Transaction Search Code

Many areas of the block validation code use a "slow" transaction search, which searches redundantly for transactions. This "slow" search has been removed upstream in Bitcoin and is now removed in PIVX. This provides a more efficient syncing process and generally better performing wallet.

Sync Fix for Block 908000

Many wallets were having trouble getting past block 908000. This block recalculates certain aspects of the money supply and zPIV transactions, and is known to take longer to sync. Code has been added to allow block 908000 to be validated without the user needing to enter any special commands into the debug console.

Working Testnet

Testnet is now accessible with this release of the wallet. Testnet can be accessed using the -testnet startup flag.

zPIV Spending Fix

zPIV that were minted between block 891730 and 895400 were experiencing an error initializing the accumulator witness data correctly, causing an inability to spend those mints. This has been fixed.

Credits

Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex.
submitted by turtleflax to pivx [link] [comments]

IRC Log from Ravencoin Open Developer Meeting - Aug 24, 2018

[14:05] <@wolfsokta> Hello Everybody, sorry we're a bit late getting started
[14:05] == block_338778 [[email protected]/web/freenode/ip.72.214.222.226] has joined #ravencoin-dev
[14:06] <@wolfsokta> Here are the topics we would like to cover today • 2.0.4 Need to upgrade - What we have done to communicate to the community • Unique Assets • iOS Wallet • General Q&A
[14:06] == Chatturga changed the topic of #ravencoin-dev to: 2.0.4 Need to upgrade - What we have done to communicate to the community • Unique Assets • iOS Wallet • General Q&A
[14:06] <@wolfsokta> Daben, could you mention what we have done to communicate the need for the 2.0.4 upgrade?
[14:07] == hwhwhsushwban [[email protected]/web/freenode/ip.172.58.37.35] has joined #ravencoin-dev
[14:07] <@wolfsokta> Others here are free to chime in where they saw the message first.
[14:07] == hwhwhsushwban [[email protected]/web/freenode/ip.172.58.37.35] has quit [Client Quit]
[14:08] Whats up bois
[14:08] hi everyone
[14:08] hi hi
[14:08] <@wolfsokta> Discussing the 2.0.4 update and the need to upgrade.
[14:08] <@Chatturga> Sure. As most of you are aware, the community has been expressing concerns with the difficulty oscillations, and were asking that something be done to the difficulty retargeting. Many people submitted suggestions, and the devs decided to implement DGW.
[14:09] <@Tron> I wrote up a short description of why we're moving to a new difficulty adjustment. https://medium.com/@tronblack/ravencoin-dark-gravity-wave-1da0a71657f7
[14:09] <@Chatturga> I have made posts on discord, telegram, bitcointalk, reddit, and ravencointalk.org from testnet stages through current.
[14:10] <@Chatturga> If there are any other channels that can reach a large number of community members, I would love to have more.
[14:10] <@wolfsokta> Thanks Tron, that hasn't been shared to the community at large yet, but folks feel free to share it.
[14:10] When was this decision made and by whom and how?
[14:10] <@Chatturga> I have also communicated with the pool operators and exchanges about the update. Of all of the current pools, only 2 have not yet updated versions.
[14:11] <@wolfsokta> The decision was made by the developers through ongoing requests for weeks made by the community.
[14:12] <@wolfsokta> Evidence was provided by the community of the damages that could be caused to projects when the wild swings continue.
[14:12] So was there a meeting or vote? How can people get invited
[14:12] <@Tron> It was also informed by my conversations with some miners that recommended that we make the change before the coin died. They witnessed similar oscillations from which other coins never recovered.
[14:13] only two pools left to upgrade is good, what about the exchanges? Any word on how many of those have/have not upgraded?
[14:13] <@wolfsokta> We talked about here in our last meeting Bruce_. All attendees were asked if they had any questions or concerns.
[14:13] == blondfrogs [[email protected]/web/freenode/ip.185.245.87.219] has joined #ravencoin-dev
[14:13] == roshii [[email protected]/web/freenode/ip.41.251.25.100] has joined #ravencoin-dev
[14:13] sup roshii long time no see
[14:14] <@Chatturga> Bittrex, Cryptopia, and IDCM have all either updated or have announced their intent to update.
[14:14] == wjcgiwgu283ik3cj [[email protected]/web/freenode/ip.172.58.37.35] has joined #ravencoin-dev
[14:15] sup russki
[14:15] what's the status here?
[14:15] I don’t think that was at all clear from the last dev meeting
[14:15] I can’t be the only person who didn’t understand it
[14:15] <@wolfsokta> Are there any suggestions on how to communicate the need to upgrade even further? I am concerned that others might also not understand.
[14:17] I’m not sold on the benefit and don’t understand the need for a hard fork — I think it’s a bad precedent to simply go rally exchanges to support a hard fork with little to no discussion
[14:17] so just to note, the exchanges not listed as being upgraded or have announced their intention to upgrade include: qbtc, upbit, and cryptobridge (all with over $40k usd volume past 24 hours according to coinmarketcap)
[14:18] <@wolfsokta> I don't agree that there was little or no discussion at all.
[14:19] <@wolfsokta> Looking back at our meeting notes from two weeks ago "fork" was specifically asked about by BrianMCT.
[14:19] If individual devs have the power to simple decide to do something as drastic as a hard fork and can get exchanges and miners to do it that’s got a lot of issues with centralization
[14:19] <@wolfsokta> It had been implemented on testnet by then and discussed in the community for several weeks before that.
[14:19] == under [[email protected]/web/freenode/ip.72.200.168.56] has joined #ravencoin-dev
[14:19] howdy
[14:19] Everything I’ve seen has been related to the asset layer
[14:19] I have to agree with Bruce_, though I wasn't able to join the last meeting here. That said I support the fork
[14:20] Which devs made this decision to do a fork and how was it communicated?
[14:20] well mostly the community made the decision
[14:20] Consensus on a change is the heart of bitcoin development and I believe the devs have done a great job building that consensus
[14:20] a lot of miners were in uproar about the situation
[14:20] <@wolfsokta> All of the devs were supporting the changes. It wasn't done in isolation at all.
[14:21] This topic has been a huge discussion point within the RVN mining community for quite some time
[14:21] the community and miners have been having issues with the way diff is adjusted for quite some time now
[14:21] Sure I’m well aware of that -
[14:21] Not sold on the benefits of having difficulty crippled by rented hashpower?
[14:21] The community saw a problem. The devs got together and talked about a solution and implemented a solution
[14:21] I’m active in the community
[14:22] So well aware of the discussions on DGW etc
[14:22] Hard fork as a solution to a problem community had with rented hashpower (nicehash!!) sounds like the perfect decentralized scenario!
[14:23] hard forks are very dangerous
[14:23] mining parties in difficulty drops are too
[14:23] <@wolfsokta> Agreed, we want to keep them to an absolute minimum.
[14:23] But miners motivation it’s the main vote
[14:24] What would it take to convince you that constantly going from 4 Th/s to 500 Gh/s every week is worse for the long term health of the coin than the risk of a hard fork to fix it?
[14:24] == Tron [[email protected]/web/freenode/ip.173.241.144.77] has quit [Ping timeout: 252 seconds]
[14:24] This hardfork does include the asset layer right? if so why is it being delayed in implementation?
[14:24] <@wolfsokta> Come back Tron!
[14:24] coudl it have been implement through bip9 voting?
[14:24] also hard fork is activated by the community! that's a vote thing!
[14:24] @mrsushi to give people time to upgrade their wallet
[14:25] @under, it would be much hard to keep consensus with a bip9 change
[14:25] <@wolfsokta> We investigated that closely Under.
[14:25] == Tron [[email protected]/web/freenode/ip.173.241.144.77] has joined #ravencoin-dev
[14:25] <@wolfsokta> See Tron's post for more details about that.
[14:25] <@spyder_> Hi Tron
[14:25] <@wolfsokta> https://medium.com/@tronblack/ravencoin-dark-gravity-wave-1da0a71657f7
[14:25] Sorry about that. Computer went to sleep.
[14:26] I'm wrong
[14:26] 2 cents. the release deadline of october 31st puts a bit of strain on getting code shipped. (duh). but fixing daa was important to the current health of the coin, and was widely suppported by current mining majority commuity. could it have been implemented in a different manner? yes . if we didnt have deadlines
[14:27] == wjcgiwgu283ik3cj [[email protected]/web/freenode/ip.172.58.37.35] has quit [Quit: Page closed]
[14:27] sushi this fork does not include assets. it's not being delayed though, we're making great progress for an Oct 31 target
[14:28] I don’t see the urgency but my vote doesn’t matter since my hash power is still CPUs
[14:28] <@wolfsokta> We're seeing the community get behind the change as well based on the amount of people jumping back in to mine through this last high difficulty phase.
[14:28] So that will be another hardfork?
[14:28] the fork does include the asset code though set to activate on oct 30th
[14:28] yes
[14:29] <@wolfsokta> Yes, it will based on the upgrade voting through the BIP9 process.
[14:29] I wanted to ask about burn rates from this group: and make a proposal.
[14:29] we're also trying hard to make it the last for awhile
[14:29] Can you clear up the above — there will be this one and another hard fork?
[14:29] <@wolfsokta> Okay, we could discuss that under towards the end of the meeting.
[14:30] If this one has the asset layer is there something different set for October
[14:30] <@wolfsokta> Yes, there will be another hard fork on October 31st once the voting process is successful.
[14:31] <@wolfsokta> The code is in 2.0.4 now and assets are active on testnet
[14:31] Bruce, the assets layer is still being worked on. Assets is active on mainnet. So in Oct 31 voting will start. and if it passes, the chain will fork.
[14:31] this one does NOT include assets for mainnet Bruce -- assets are targeted for Oct 31
[14:31] not***
[14:31] not active****
[14:31] correct me if I'm wrong here, but if everyone upgrades to 2.0.4 for this fork this week, the vote will automatically pass on oct 31st correct? nothing else needs to be done
[14:31] Will if need another download or does this software download cover both forks?
[14:31] <@wolfsokta> Correct Urgo
[14:32] thats how the testnet got activated and this one shows "asset activation status: waiting until 10/30/2018 20:00 (ET)"
[14:32] Will require another upgrade before Oct 31
[14:32] thank you for the clarification wolfsokta
[14:32] <@wolfsokta> It covers both forks, but we might have additional bug fixes in later releases.
[14:32] So users DL one version now and another one around October 30 which activates after that basically?
[14:33] I understand that, but I just wanted to make it clear that if people upgrade to this version for this fork and then don't do anything, they are also voting for the fork on oct 31st
[14:33] Oh okay — one DL?
[14:33] Bruce, Yes.
[14:33] Ty
[14:33] well there is the issue that there maybe some further consensus bugs dealing with the pruneability of asset transactions that needs to be corrected between 2.0.4 and mainnet. so i would imagine that there will be further revisions required to upgrade before now and october 31
[14:33] @under that is correct.
[14:34] I would highly recommend bumping the semver up to 3.0.0 for the final pre 31st release so that the public know to definitely upgrade
[14:34] @under +1
[14:35] out of curiosity, have there been many bugs found with the assets from the version released in july for testnet (2.0.3) until this version? or is it solely a change to DGW?
[14:35] <@wolfsokta> That's not a bad idea under.
[14:35] <@spyder_> @under good idea
[14:35] @urgo. Bugs are being found and fixed daily.
[14:35] Any time the protocol needs to change, there would need to be a hard fork (aka upgrade). It is our hope that we can activate feature forks through the BIP process (as we are doing for assets). Mining pools and exchanges will need to be on the newest software at the point of asset activation - should the mining hash power vote for assets.
[14:35] blondfrogs: gotcha
[14:35] There have been bugs found (and fixed). Testing continues. We appreciate all the bug reports you can give us.
[14:36] <@wolfsokta> Yes! Thank you all for your help in the community.
[14:37] (pull requests with fixes and test coverage would be even better!)
[14:37] asset creation collision is another major issue. current unfair advantage or nodes that fore connect to mining pools will have network topologies that guarantee acceptance. I had discussed the possibility of fee based asset creation selection and i feel that would be a more equal playing ground for all users
[14:38] *of nodes that force
[14:38] <@wolfsokta> What cfox said, we will always welcome development help.
[14:38] So just to make sure everyone know. When assets is ready to go live on oct 31st. Everyone that wants to be on the assets chain without any problems will have to download the new binary.
[14:39] <@wolfsokta> The latest binary.
[14:39] under: already in the works
[14:39] excellent to hear
[14:39] == UserJonPizza [[email protected]/web/freenode/ip.24.218.60.237] has joined #ravencoin-dev
[14:39] <@wolfsokta> Okay, we've spent a bunch of time on that topic and I think it was needed. Does anybody have any other suggestions on how to get the word out even more?
[14:40] maybe preface all 2.0.X releases as pre-releases... minimize the number of releases between now and 3.0 etc
[14:41] <@wolfsokta> Bruce_ let's discuss further offline.
[14:41] wolfsokta: which are the remaining two pools that need to be upgraded? I've identified qbtc, upbit, and cryptobridge as high volume exchanges that haven't said they were going to do it yet
[14:41] so people can help reach out to them
[14:41] f2pool is notoriously hard to contact
[14:41] are they on board?
[14:42] <@wolfsokta> We could use help reaching out to QBTC and Graviex
[14:42] I can try to contact CB if you want?
[14:42] <@Chatturga> The remaining pools are Ravenminer and PickAxePro.
[14:42] <@Chatturga> I have spoken with their operators, the update just hasnt been applied yet.
[14:42] ravenminer is one of the largest ones too. If they don't upgrade that will be a problem
[14:42] okay good news
[14:42] (PickAxePro sounds like a Ruby book)
[14:43] I strongly feel like getting the word out on ravencoin.org would be beneficial
[14:44] that site is sorely in need of active contribution
[14:44] Anyone can volunteer to contribute
[14:44] <@wolfsokta> Okay, cfox can you talk about the status of unique assets?
[14:44] sure
[14:45] <@wolfsokta> I'll add website to the end of our topics.
[14:45] code is in review and will be on the development branch shortly
[14:45] would it make sense to have a page on the wiki (or somewhere else) that lists the wallet versions run by pools & exchanges?
[14:45] will be in next release
[14:45] furthermore, many sites have friendly link to the standard installers for each platform, if the site linked to the primary installers for each platform to reduce github newb confusion that would be good as well
[14:46] likely to a testnetv5 although that isn't settled
[14:46] <@wolfsokta> Thanks cfox.
[14:46] <@wolfsokta> Are there any questions about unique assets, and how they work?
[14:47] after the # are there any charachters you cant use?
[14:47] will unique assets be constrained by the asset alphanumeric set?
[14:47] ^
[14:47] <@Chatturga> @Urgo there is a page that tracks and shows if they have updated, but it currently doesnt show the actual version that they are on.
[14:47] a-z A-Z 0-9
[14:47] <@Chatturga> https://raven.wiki/wiki/Exchange_notifications#Pools
[14:47] There are a few. Mostly ones that mess with command-line
[14:47] you'll be able to use rpc to do "issueunique MATRIX ['Neo','Tank','Tank Brother']" and it will create three assets for you (MATRIX#Neo, etc.)
[14:47] @cfox - No space
[14:48] @under the unique tags have an expanded set of characters allowed
[14:48] Chatturga: thank you
[14:48] @UJP yes there are some you can't use -- I'll try to post gimmie a sec..
[14:49] Ok. Thank you much!
[14:49] 36^36 assets possible and 62^62 uniques available per asset?
[14:49] <@spyder_> std::regex UNIQUE_TAG_CHARACTERS("^[[email protected]$%&*()[\\]{}<>_.;?\\\\:]+$");
[14:50] regex UNIQUE_TAG_CHARACTERS("^[[email protected]$%&*()[\\]{}<>_.;?\\\\:]+$")
[14:50] oh thanks Mark
[14:51] <@wolfsokta> Okay, next up. I want to thank everybody for helping test the iOS wallet release.
[14:51] <@wolfsokta> We are working with Apple to get the final approval to post it to the App Store
[14:51] @under max asset length is 30, including unique tag
[14:51] Does the RVN wallet have any other cryptos or just RVN?
[14:52] == BruceFenton [[email protected]/web/freenode/ip.67.189.233.170] has joined #ravencoin-dev
[14:52] will the android and ios source be migrated to the ravenproject github?
[14:52] I've been adding beta test users. I've added about 80 new users in the last few days.
[14:52] <@wolfsokta> Just RVN, and we want to focus on adding the asset support to the wallet.
[14:53] == Bruce_ [[email protected]/web/freenode/ip.67.189.233.170] has quit [Ping timeout: 252 seconds]
[14:53] <@wolfsokta> Yes, the code will also be freely available on GitHub for both iOS and Android. Thank you Roshii!
[14:53] Would you consider the iOS wallet to be a more secure place for one's holdings than say, a Mac connected to the internet?
[14:53] will there be a chance of a more user freindly wallet with better graphics like the iOS on PC?
[14:53] the android wallet is getting updated for DGW, correct?
[14:53] <@wolfsokta> That has come up in our discussion Pizza.
[14:54] QT framework is pretty well baked in and is cross platform. if we get some qt gurus possibly
[14:54] Phones are pretty good because the wallet we forked uses the TPM from modern phones.
[14:54] Most important is to write down and safely store your 12 word seed.
[14:54] TPM?
[14:54] <@wolfsokta> A user friendly wallet is one of our main goals.
[14:55] TPM == Trusted Platform Module
[14:55] Ahhh thanks
[14:55] just please no electron apps. they are full of security holes
[14:55] <@spyder_> It is whats makes your stuffs secure
[14:55] not fit for crypto
[14:55] under: depends on who makes it
[14:55] The interface screenshots I've seen look like Bread/Loaf wallet ... I assume that's what was forked from
[14:55] ;)
[14:56] <@wolfsokta> @roshii did you see the question about the Android wallet and DGW?
[14:56] Yes, it was a fork of breadwallet. We like their security.
[14:56] chromium 58 is the last bundled electron engine and has every vuln documented online by google. so unless you patch every vuln.... methinks not
[14:56] Agreed, great choice
[14:57] <@wolfsokta> @Under, what was your proposal?
[14:58] All asset creation Transactions have a mandatory OP_CHECKLOCKTIMEVERIFY of 1 year(or some agreed upon time interval), and the 500 RVN goes to a multisig devfund, run by a custodial group. We get: 1) an artificial temporary burn, 2) sustainable community and core development funding for the long term, after OSTK/Medici 3) and the reintroduction of RVN supply at a fixed schedule, enabling the removal of the 42k max cap of total As
[14:58] *im wrong on the 42k figure
[14:58] <@wolfsokta> Interesting...
[14:59] <@wolfsokta> Love to hear others thoughts.
[14:59] Update: I posted a message on the CryptoBridge discord and one of their support members @stepollo#6276 said he believes the coin team is already aware of the fork but he would forward the message about the fork over to them right now anyway
[14:59] Ifs 42 million assets
[14:59] yep.
[15:00] I have a different Idea. If the 500 RVN goes to a dev fund its more centralized. The 500 RVN should go back into the unmined coins so miners can stay for longer.
[15:01] *without a hardfork
[15:01] <@wolfsokta> lol
[15:01] that breaks halving schedule, since utxos cant return to an unmined state.
[15:01] @UJP back into coinbase is interesting. would have to think about how that effects distribution schedule, etc.
[15:01] only way to do that would be to dynamicaly grow max supply
[15:02] and i am concerned already about the max safe integer on various platforms at 21 billion
[15:02] js chokes on ravencoin already
[15:02] <@wolfsokta> Other thoughts on Under's proposal? JS isn't a real language. ;)
[15:02] Well Bitcoin has more than 21 bn Sats
[15:02] Is there somebody who wants to volunteer to fix js.
[15:02] hahaha
[15:03] I honestly would hate for the coins to go to a dev fund. It doesn't seem like Ravencoin to me.
[15:03] Yep, but we're 21 billion x 100,000,000 -- Fits fine in a 64-bit integer, but problematic for some languages.
[15:03] <@wolfsokta> Thanks UJP
[15:04] <@wolfsokta> We're past time but I would like to continue if you folks are up for it.
[15:04] Yeah no coins can go anywhere centrality contorted like a dev fund cause that would mean someone has to run it and the code can’t decide that so it’s destined to break
[15:05] currently and long term with out the financial backing of development then improvements and features will be difficult. we are certainly thankful for our current development model. but if a skunkworks project hits a particular baseline of profitability any reasonable company would terminate it
[15:05] Yes let’s contibue for sure
[15:05] the alternative to a dev fund in my mind would be timelocking those funds back to the issuers change address
[15:06] But we can’t have dev built in to the code — it has to be open source like Bitcoin and monero and Litecoin - it’s got drawbacks but way more advantages- it’s the best model
[15:06] Dev funding
[15:06] i highly reccommend not reducing the utility of raven by removing permanently the supply
[15:07] == BW_ [[email protected]/web/freenode/ip.138.68.243.202] has joined #ravencoin-dev
[15:07] timelocking those funds accompllishes the same sacrifice
[15:07] @under timelocking is interesting too
[15:07] How exactly does timelocking work?
[15:07] <@wolfsokta> ^
[15:07] I mean you could change the price of assets with the Block reward halfing.
[15:07] == Roshiix [[email protected]/web/freenode/ip.105.67.2.212] has joined #ravencoin-dev
[15:08] funds cant be spent from an address until a certain time passes
[15:08] but in a what magical fairy land do people continue to work for free forever. funding development is a real issue... as much as some might philosphically disagree. its a reality
[15:08] You’d still need a centralized party to decide how to distribute the funds
[15:08] even unofficially blockstream supports bitcoin devs
[15:08] on chain is more transparent imho
[15:09] == Tron_ [[email protected]/web/freenode/ip.173.241.144.77] has joined #ravencoin-dev
[15:09] @UJP yes there are unlimited strategies. one factor that I think is v important is giving application developers a way to easily budget for projects which leads to flat fees
[15:09] If the project is a success like many of believe it will be, I believe plenty of people will gladly done to a dev fund. I don't think the 500 should be burned.
[15:09] *donate
[15:09] centralized conservatorship, directed by community voting process
[15:10] == Tron [[email protected]/web/freenode/ip.173.241.144.77] has quit [Ping timeout: 252 seconds]
[15:10] <@wolfsokta> Thanks Under, that's an interesting idea that we should continue to discuss in the community. You also mentioned the existing website.
[15:10] It would need to be something where everyone with a QT has a vote
[15:10] think his computer went to sleep again :-/
[15:10] I agree UJP
[15:10] with the website
[15:10] No that’s ico jargon — any development fund tied to code would have to be centralized and would therefor fail
[15:11] ^
[15:11] ^
[15:11] ^
[15:11] dashes model for funding seems to be pretty decentralized
[15:11] community voting etc
[15:11] Once you have a dev fund tied to code then who gets to run it? Who mediates disputes?
[15:11] oh well another discussion
[15:11] Dash has a CEO
[15:12] <@wolfsokta> Yeah, let's keep discussing in the community spaces.
[15:12] Dash does have a good model. It's in my top ten.
[15:12] having the burn go to a dev fund is absolute garbage
[15:12] These dev chats should be more target than broad general discussions — changing the entire nature of the coin and it’s economics is best discussed in the RIPs or other means
[15:13] <@wolfsokta> Yup, let's move on.
[15:13] just becuase existing implementation are garbage doesnt mean that all possible future governance options are garbage
[15:13] <@wolfsokta> To discussing the website scenario mentioned by under.
[15:13] the website needs work. would be best if it could be migrated to github as well.
[15:13] What about this: Anyone can issue a vote once the voting feature has been added, for a cost. The vote would be what the coins could be used for.
[15:14] features for the site that need work are more user friendly links to binaries
[15:14] <@wolfsokta> We investigated how bitcoin has their website in Github to make it easy for contributors to jump in.
[15:14] that means active maintenance of the site instead of its current static nature
[15:15] <@wolfsokta> I really like how it's static html, which makes it super simple to host/make changes.
[15:15] the static nature isn’t due to interface it’s due to no contributors
[15:15] no contribution mechanism has been offered
[15:15] github hosted would allow that
[15:16] We used to run the Bitcoin website from the foundation & the GitHub integration seemed to cause some issues
[15:16] its doesnt necessarily have to be hosted by github but the page source should be on github and contributions could easily be managed and tracked
[15:17] for example when a new release is dropped, the ability for the downlaods section to have platform specific easy links to the general installers is far better for general adoption than pointing users to github releases
[15:18] <@wolfsokta> How do people currently contribute to the existing website?
[15:18] they dont?
[15:18] We did that and it was a complete pain to host and keep working — if someone wants to volunteer to do that work hey can surely make the website better and continually updated — but they could do that in Wordpress also
[15:19] I’d say keep an eye out for volunteers and maybe we can get a group together who can improve the site
[15:19] == digitalvap0r-xmr [[email protected]/web/cgi-irc/kiwiirc.com/ip.67.255.25.134] has joined #ravencoin-dev
[15:19] And they can decide best method
[15:20] I host the source for the explorer on github and anyone can spin it up instantly on a basic aws node. changes can be made to interface etc, and allow for multilingual translations which have been offered by some community members
[15:20] there are models that work. just saying it should be looked at
[15:20] i gotta run thank you all for your contributions
[15:20] <@wolfsokta> I feel we should explore the source for the website being hosted in GitHub and discuss in our next dev meeting.
[15:21] <@Chatturga> Thanks Under!
[15:21] == under [[email protected]/web/freenode/ip.72.200.168.56] has quit [Quit: Page closed]
[15:21] <@wolfsokta> Thanks, we also need to drop soon.
[15:21] There is no official site so why care. Someone will do better than the next if RVN is worth it anyway. That's already the case.
[15:21] <@wolfsokta> Let's do 10 mins of open Q&A
[15:22] <@wolfsokta> Go...
[15:23] <@Chatturga> Beuller?
[15:24] No questions ... just a comment that the devs and community are great and I'm happy to be a part of it
[15:24] I think everyone moved to discord. I'll throw this out there. How confident is the dev team that things will be ready for oct 31st?
[15:24] <@wolfsokta> Alright! Thanks everybody for joining us today. Let's plan to get back together as a dev group in a couple of weeks.
[15:25] thanks block!
[15:25] <@wolfsokta> Urgo, very confident
[15:25] Please exclude trolls from discord who havent read the whitepaper
[15:25] great :)
[15:25] "things" will be ready..
[15:25] Next time on discord right?
[15:25] woah why discord?
[15:25] some of the suggestions here are horrid
[15:25] this is better less point
[15:25] == blondfrogs [[email protected]/web/freenode/ip.185.245.87.219] has quit [Quit: Page closed]
[15:25] Assets are working well on testnet. Plan is to get as much as we can safely test by Sept 30 -- this includes dev contributions. Oct will be heavy testing and making sure it is safe.
[15:26] people
[15:26] <@wolfsokta> Planning on same time, same IRC channel.
[15:26] == BW_ [[email protected]/web/freenode/ip.138.68.243.202] has quit [Quit: Page closed]
[15:26] @xmr any in particular?
[15:27] (or is "here" discord?)
[15:27] Cheers - Tron
[15:27] "Cheers - Tron" - Tron
submitted by Chatturga to Ravencoin [link] [comments]

DNotes 2.0 Frequently Asked Questions:

DNotes 2.0 Frequently Asked Questions:
Q: What is new with DNotes 2.0?
A: DNotes 2.0 is a major improvement on the original DNotes blockchain. The new blockchain will allow DNotes and its partner company DNotes Global to achieve its objective to connect DNotes to the modern world of finance and commerce. The new blockchain is faster, more secure, and consumes only a fraction of the electricity. It also allows custom invoices to be created and attached to transactions, and changes the economic incentives of the network to one that encourages savings with the switch to the Proof-Of-Stake algorithm, and paying 0.5% interest on balances that haven’t moved from a wallet address in a 30 day period (~6% per annum).
Specifications
POS 2% Annualized Staking Reward Individual blocks reward will be Total Coins / 525,600 60 Second Block Target 0.005 Transaction Fee Source: https://github.com/DNotesCoin/DNotes2.0 Download Wallet: https://github.com/DNotesCoin/DNotes2.0/releases/tag/v2.0.0.0 Directory DNotes2 (C:\Users\USERNAME\AppData\Roaming\DNotes2 on Windows) CONF dnotes.conf (all lower case)
DNotes 2.0 Features Switch to PoS CRISP Reward - 0.5% interest every 30 days. Awarded by address. Calculated on a 30 day cycle. Automated Invoicing (First Phase) - Integrated blockchain invoice number
There will be a soft deadline where DNotes mined after that block will not be redeemable for 2.0 coins: 4/16/2018 Block# 2180897 133,574,552 Will be the total swappable amount of DNotes we create +20,000,000 Allocated to DNotes Global, Inc for Development & Growth Fund 153,574,552 Total DNotes 2.0 Created
The next update (TBD) will include: Deferred Staking
Q: How do I swap my coins?
A: DNotes stored on the DNotesVault are automatically swapped for you, you don’t need to take any action as the swap process has been done on your behalf.
If you already had a DNotesVault account prior to the swap and still have more coins to swap from exchanges or a PC wallet:
Login to your DNotesVault account. Click “historic” at the top, and send your old DNotes to one of your historical addresses. The DNotes you send will then be converted to the new DNotes 2.0 coins, and will show in your new DNotes wallet under “dashboard” after we have completed the swap process. Note: Please allow some time for this process to complete.
If you do not have a DNotes Vault account, you can perform a manual swap:
Visit the following address: https://goo.gl/forms/MMAKqbqejd1rwf1m2 Provide us with your contact email, and your DNotes 2.0 address. We recommend creating an account at www.dnotesvault.com and sending us your deposit address. Otherwise you can download the DNotes 2.0 QT wallet here: https://github.com/DNotesCoin/DNotes2.0/releases We will contact you with an address for you to send your old DNotes coins to, and send you back the new DNotes 2.0 coins.
Q: I had a DNotes Vault account with DNotes in it before the swap. Have my old DNotes been swapped into the new coins?
A: Yes. We have taken care of swapping all coins held at the DNotes Vault at the time of the upgrade. You don’t need to take any action.
Q: I found some DNotes from the old blockchain, can I still swap them for the new DNotes tokens?
A: Yes, we will continue to run the old blockchain and give a reasonable period of time for people to swap their DNotes to the new DNotes 2.0 tokens. We recommend that users take action to swap their coins as soon as possible, and may treat swaps on a case by case basis.
Q: I have a paper wallet. How do I turn them into the new coins?
A: You will need to download the DNotes v1.2 software, and then use the importprivkey command in the debug console.
https://bitcoin.stackexchange.com/questions/5941/how-do-i-import-a-private-key-into-bitcoin-core
Once your wallet is updated, you will be able to send out your DNotes.
Q: What is the cutoff date for mined DNotes that can be swapped to the new DNotes blockchain?
A: We have set April 16th as the soft deadline. No DNotes mined after this date will be eligible to be swapped to DNotes running on the new blockchain. We will continue swap DNotes after that date, however the process will not be as easy and will take more time.
Q: What is Staking?
A: Staking your coins helps to support the DNotes network, and the network currently pays out roughly 5 DNotes every minute to one address on the network based on a probability that centers on how many coins the user is staking with as a percentage of the total number of coins being staked on the network. The DNotes network pays out ~2% of the total number of coins per annum. If 100% of DNotes were being used to stake on the network, then by probability each user could expect 2% growth in the number of coins they have. If only 50% of coins are used to stake, then those users could expect approximately 4% growth that year.
Q: Can I stake my coins on the DNotesVault?
A: You cannot currently stake your coins that are on the DNotesVault, you will need to withdraw your DNotes 2.0 to a local wallet and stake your coins from your local wallet. We will in a future release incorporate cold staking, which will allow you stake your coins while they are safely tucked away inside the DNotesVault. However, we do not have an ETA, it will be one of our highest priorities for next upgrades.
Q: How do I stake?
Disclaimer: It is recommended that you properly secure your computer and wallet, as well as make proper backups, before attempting to run your own staking wallet. Failure to properly secure your DNotes may result in loss or theft. If you are not familiar with the process, please start off small and familiarize yourself with the process.
You will need to download the DNotes QT wallet here: https://github.com/DNotesCoin/DNotes2.0/releases/tag/v2.0.0.0
Install the wallet (and we recommend creating a backup) Go to settings, and then ‘encrypt wallet’. Enter your password twice (and do NOT forget it, or you will not be able to access the wallet and we can not help you). Go to settings, and then ‘unlock wallet’, enter your password, and select “for staking only”. This will prevent any transfers from being made from your wallet without the password while you stake your coins. Soon the arrow at the bottom will turn green. This means that your coins are now staking.
You can watch a video of these steps here from our alpha release here: https://www.youtube.com/watch?v=2w9r2LoXM6c
Q: How do I earn the interest reward?
A: Our Cryptocurrency Investment Savings Plan (CRISP) payouts occur approximately once per month. All coins that haven’t moved address during that month period will accrue a 0.5% interest, which compounds to roughly 6.17% per annum. If you move your coins during that time, those coins will not receive the interest for that month.
Q: What exchanges are DNotes listed on?
A: Cryptopia, Nova, Yobit, & Trade By Trade
Q: Will DNotes 2.0 be listed on new exchanges?
A: The DNotes team are working to get DNotes listed on new and larger exchanges.
Q: When will Cryptopia relist DNotes 2.0?
A: Cryptopia is starting the delisting process and they have advised they will connect us with their relisting team once the DNotes have been removed from the exchange, in order to prevent confusion.
Q: Are the new DNotes 2.0 coins worth the same as the old coins?
A: Yes, they are worth exactly the same. However we can not predict what price movements will occur at exchanges once DNotes is relisted using the new coins.
Q: I have DNotes on the exchange, do I need to remove them from the exchange?
A: Yes, as soon as possible. Please see “How do I swap my coins?”
Q: I have Mac or Specific Linux OS, will there be wallets for these?
A: Yes, these are among our high priority items to get done as soon as possible.
If you have any other queries, please email [email protected]
submitted by AceRun1 to DNotes [link] [comments]

4. Installing Bitcoin Core on Linux Quick Fix  Bitconnect QT Wallet Out of Sync ️ Mac OSX How to install Electrum Wallet for Bitcoin (BTC) on a Mac syncing Bitconnect qt wallet on a mac for staking Increase slow download and sync of bitcoin blockchain on Mac

af6ac3b doc: Remove mention of Qt4 from build docs (Wladimir J. van der Laan) 462c71f test: Update travis to not test Qt4 anymore (Wladimir J. van der Laan) 907f73b gui: Remove QT_VERSION fallbacks for Qt < 5 (Wladimir J. van der Laan) bad068a build: Build system changes to support only Qt5 (Wladimir J. van der Laan) Pull request description: Implements #8263. #19059 update Qt base translations for macOS release (fanquake) Build system #19152 improve build OS configure output (skmcontrib) #19536 qt, build: Fix QFileDialog for static builds (hebasto) Tests and QA #19444 Remove cached directories and associated script blocks from appveyor config (sipsorcery) #18640 appveyor: Remove clcache (MarcoFalke ... 8c6081a compat: remove bswap_* check on macOS (fanquake) 2cba35a build: skip building OpenSSL lib_ssl (fanquake) 45a2d3c build: remove OpenSSL from Qt build (fanquake) befbc40 build: remove EVP_MD_CTX_new detection (fanquake) fcee10c build: remove SSL lib detection (fanquake) c7f30db gui: Update BIP70 support message (fanquake) a3e8103 build: remove BIP70 entries from macOS Info.plist ... Browse to the location of the Bitcoin Core executable (C:\Program Files\Bitcoin\bitcoin-qt.exe) and click the OK button. Next, add the command line option datadir, using the path to your data directory. Double clicking the newly-created shortcut will direct Bitcoin Core to use the new data directory. #17503 Remove bitness from bitcoin-qt help message and manpage (laanwj) #17539 Update and improve Developer Notes (hebasto) #17561 Changed MiniUPnPc link to https in dependencies.md (sandakersmann) #17596 Change doxygen URL to doxygen.bitcoincore.org (laanwj) #17598 Update release process with latest changes (MarcoFalke)

[index] [20006] [7649] [876] [5398] [23794] [3176] [22672] [33752] [2710] [29754]

4. Installing Bitcoin Core on Linux

When you are experiencing a slow download and synchronisation of the bitcoin blockchain this little tutorial might be of help. We will disable power nap feature for our system to stop macOS from ... Learn how to install your Bitcoin Core wallet on your mac, if you use Bitcoin Core wallet on your machine you need to install the blockchain, right now when this movie is recored its cost around ... Remove all; Disconnect; The next video is starting stop. ... Syncing your Bitconnect QT wallet NEW updated 10/27/2018 - Duration: ... How to Mine Bitcoin on Mac with Honeyminer - Duration: 5:09. Installing Electrum Wallet for Bitcoin (BTC) on a Mac. If you have any further questions, please comment bellow, I will do my best to answer it. If you think my accent is funny, we have something ... In this video I will show you how to quickly fix the syncing issue with Bitconnect QT wallet on a Mac. If this fix does not work please CLICK the Bitconnect link for further options below.

#