Bitcoin / [bitcoin-list] Bitcoin-Qt and bitcoind version 0 ...

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]

PSA: Enable Tor as a simple way to make your node reachable.

Become one of the 10% of node operators that receive incoming connections.
Installing bitcoin core is easy, and with pruning it really isn't the space sink it is characterized as. Even a modest computer can complete the initial block download (IBD) and become a full node. But what some users (90%) find a bit more challenging, is how to become a listening node. Listening nodes are an important part of the network, and are simple enough to enable. I can think of 4 ways to do it:
  1. Operate on an OS and Network that support uPnP, allowing bitcoin to open the ports for you.
  2. Subscribe to a VPN that allows you to open ports through their service.
  3. Manually configure your OS and network to forward port 8333 and 18333.
  4. Run Tor and direct bitcoin to listen through it.
I'll discuss #4. Obviously #1 or #2 are easier, but require a VPN subscription or uPnP enabled HW. And if you live in a dorm or don't control the network, Tor may be the only free option available.
As a bit of background, bitcoin supports three networks that your node can listen on:
Obviously, the more you enable, the better, but here are the basic steps for Tor in broad strokes. If you have any questions post them here and I'll see if we can't help you out:
  1. Download, verify1 and install Gpg4win
  2. Download, verify2, install, and launch Tor Browser
  3. Download, verify3, install, and launch Bitcoin Core
  4. Launch and Admin command console in the directory containing tor.exe
  5. Install the Tor service: tor.exe --service install
  6. CD to service dir: cd %windir%\ServiceProfiles\LocalService\AppData\Roaming\tor
  7. Create and edit a file called torrc with the contents suggested below
  8. Restart tor: tor.exe --service stop && tor.exe --service start
  9. Record the hostname: type .\HiddenService\hostname as
  10. Add the bitcoin.conf options suggested below
  11. Restart the bitcoin-qt program
  12. (Optional) Activate the bitnodes crawler at https://bitnodes.io/nodes/-8333/
It may take a while for your node to show up on bitnodes. I've found the check button sometimes has trouble with onions. Of course you don't need to do it, but it can provide a simple way to check status once your on the list.

torrc file: (replace c:\windows with the proper path as needed)

```

Change to C:\Windows\ServiceProfiles\LocalService\AppData\Roaming

Log notice file \tor\service.log

Bridges may be needed if the Gov't shuts down Tor exit nodes. Get Bridges by

emailing [email protected] from Gmail (only) and uncomment as follows:

Bridge obfs4 : cert= iat-mode=

HiddenServiceDir \tor\HiddenService HiddenServiceVersion 2 HiddenServicePort 8333 127.0.0.1:8333 HiddenServicePort 18333 127.0.0.1:18333 ```

bitcoin.conf file: (entries to be ADDED)

```

Change to what you recorded earlier

onion=127.0.0.1:9050 listen=1 externalip= discover=1 ```
Footnotes:
  • 1 Cert: {Subject: Intevation GmbH; SHA1: c13a65963ad53e78694dd223d518007791a05fe4}
  • 2 PGP Signing Key: 0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290
  • 3 PGP Signing Key: 0x01EA5486DE18A882D4C2684590C8019E36C2E964
submitted by brianddk to Bitcoin [link] [comments]

Windows / Linux Guide to using Trezor with Bitcoin Core (HWI)

This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest Linux TLDR is here
Unfortunately, I don't have access to a Coldcard or Ledger. I'm not sure how the setpin or -stdinpass parameters are handled on that HW.

( A ) Install TrezorCTL, HWI, and build GUI

You only need to set the wallet up once, but may repeat to upgrade

( A.I ) Download extract and install HWI

  1. Download and isntall Python
  2. Download https://github.com/bitcoin-core/HWI/archive/1.1.2.zip
  3. Extract it to a working folder (assumes C:\User\Reddit\src\HWI)
  4. Change Directory (cd) to working folder cd "C:\User\Reddit\src\HWI"
  5. Setup venv python -m venv .venv
  6. Enter venv .venv\Scripts\activate.bat 1
  7. Install dependencies python -m pip install -U setuptools pip wheel
  8. Install TrezorCTL python -m pip install trezor[hidapi]
  9. Install HWI python -m pip install hwi pyside2
  10. Download github.com/libusb/libusb/releases/download/v1.0.23/libusb-1.0.23.7z
  11. Extract MS64\dll\libusb-1.0.dll from the archive
  12. Copy to pywin copy libusb-1.0.dll .venv\Lib\site-packages\pywin32_system32\

( A.II ) Build the QT UI files

  1. Download and install MSYS2
  2. Launch a mingw64.exe shell
  3. CD to working folder cd "C:\User\Reddit\src\HWI"
  4. Enter venv source .venv/Scripts/activate 1
  5. Run UI build bash contrib/generate-ui.sh

( B ) Create a Trezor wallet in Bitcoin Core (testnet)

You only need to set the wallet up once, no private key data is stored, only xpub data

( B.I ) Retrieve keypool from HWI-QT

  1. Launch hwi-qt.exe --testnet (assuming testnet)
  2. Click Set passphrase (if needed) to cache your passphrase then click Refresh
  3. Select you trezor from the list then click Set Pin (if needed)
  4. Ensure your Trezor in the dropdown has a fingerprint
  5. Select Change keypool options and choose P2WPKH
  6. Copy all the text from the Keypool textbox

( B.II ) Create the wallet in Bitcoin QT

  1. Launch Bitcoin Core (testnet) (non-pruned) 2
  2. Select Console from the Window menu
  3. Create a wallet createwallet "hwi" true
  4. Ensure that hwi is selected in the console wallet dropdown
  5. Verify walletname using the getwalletinfo command
  6. Import keypool importmulti '' (note ' caging)
  7. Rescan if TXNs are missing rescanblockchain 3

( C.I ) Grab Tesnet coins

  1. Select the Receive tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Select Create new receiving address and copy address
  4. Google "bitcoin testnet faucet" and visit a few sites
  5. Answer captcha and input your addressed copied from C.I.3

( D ) Spending funds with HWI

This is how you can spend funds in your Trezor using Bitcoin Core (testnet)

( D.I ) Create an unsigned PSBT

  1. Select the Send tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Verify your balance in Watch-only balance
  4. Rescan if balance is wrong (see B.II.7) 3
  5. Craft your TXN as usual, then click Create Unsigned
  6. Copy the PSBT to your clipboard when prompted

( D.II ) Sign your PSBT

  1. In HWI-QT click Sign PSBT
  2. Paste what you copied in D.I.6 in PSBT to Sign field
  3. Click Sign PSBT
  4. Copy the text for PSBT Result

( D.III ) Broadcast your TXN

  1. Select the Console window in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Finalize PSBT: finalizepsbt
  4. Copy the signed TXN hex from the hex field returned
  5. Broadcast TXN: sendrawtransaction

Final Thoughts

I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks.
There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out.
Footnotes:
  • 1. - Later version of python put the activate script under 'bin' instead of 'Script'
  • 2. - You can run pruned, but you need to have a fresh wallet
  • 3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
submitted by brianddk to Bitcoin [link] [comments]

Windows Guide to using Trezor with Bitcoin Core (HWI)

This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest TLDR is here

( A ) Install TrezorCTL, HWI, and build GUI

You only need to set the wallet up once, but may repeat to upgrade

( A.I ) Download extract and install HWI

  1. Download and isntall Python
  2. Download https://github.com/bitcoin-core/HWI/archive/1.1.2.zip
  3. Extract it to a working folder (assumes C:\User\Reddit\src\HWI)
  4. Change Directory (cd) to working folder cd "C:\User\Reddit\src\HWI"
  5. Setup venv python -m venv .venv
  6. Enter venv .venv\Scripts\activate.bat 1
  7. Install dependencies python -m pip install -U setuptools pip wheel
  8. Install TrezorCTL python -m pip install trezor[hidapi]
  9. Install HWI python -m pip install hwi pyside2
  10. Download github.com/libusb/libusb/releases/download/v1.0.23/libusb-1.0.23.7z
  11. Extract MS64\dll\libusb-1.0.dll from the archive
  12. Copy to pywin copy libusb-1.0.dll .venv\Lib\site-packages\pywin32_system32\

( A.II ) Build the QT UI files

  1. Download and install MSYS2
  2. Launch a mingw64.exe
  3. CD to working folder cd "C:\User\Reddit\src\HWI"
  4. Enter venv source .venv/Scripts/activate 1
  5. Run UI build bash contrib/generate-ui.sh

( B ) Create a Trezor wallet in Bitcoin Core (testnet)

You only need to set the wallet up once, no private key data is stored, only xpub data

( B.I ) Retrieve keypool from HWI-QT

  1. Launch hwi-qt.exe --testnet (assuming testnet)
  2. Click Set passphrase (if needed) to cache your passphrase then click Refresh
  3. Select you trezor from the list then click Set Pin (if needed)
  4. Ensure your Trezor in the dropdown has a fingerprint
  5. Select Change keypool options and choose P2WPKH
  6. Copy all the text from the Keypool textbox

( B.II ) Create the wallet in Bitcoin QT

  1. Launch Bitcoin Core (testnet) (non-pruned) 2
  2. Select Console from the Window menu
  3. Create a wallet createwallet "hwi" true
  4. Ensure that hwi is selected in the console wallet dropdown
  5. Verify walletname using the getwalletinfo command
  6. Import keypool importmulti '' (note ' caging)
  7. Rescan if TXNs are missing rescanblockchain 3

( C.I ) Grab Tesnet coins

  1. Select the Receive tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Select Create new receiving address and copy address
  4. Google "bitcoin testnet faucet" and visit a few sites
  5. Answer captcha and input your addressed copied from C.I.3

( D ) Spending funds with HWI

This is how you can spend funds in your Trezor using Bitcoin Core (testnet)

( D.I ) Create an unsigned PSBT

  1. Select the Send tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Verify your balance in Watch-only balance
  4. Rescan if balance is wrong (see B.II.7) 3
  5. Craft your TXN as usual, then click Create Unsigned
  6. Copy the PSBT to your clipboard when prompted

( D.II ) Sign your PSBT

  1. In HWI-QT click Sign PSBT
  2. Paste what you copied in D.I.6 in PSBT to Sign field
  3. Click Sign PSBT
  4. Copy the text for PSBT Result

( D.III ) Broadcast your TXN

  1. Select the Console window in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Finalize PSBT: finalizepsbt
  4. Copy the signed TXN hex from the hex field returned
  5. Broadcast TXN: sendrawtransaction

Final Thoughts

I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks.
There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out.
Footnotes:
  • 1. - Later version of python put the activate script under 'bin' instead of 'Script'
  • 2. - You can run pruned, but you need to have a fresh wallet
  • 3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
submitted by brianddk to TREZOR [link] [comments]

Bitcoin Tor

Subject: PSA: Make your node reachable by using Tor
There is usually a post every few months with someone asking for tips on how to make their node reachable. It's always a hard question to answer since its impossible to know what type of routers and firewalls they are going to have to punch through. This is especially difficult in college dorms. One cheap (and easy) way around it is to to just jump through a few extra steps to make your bitcoin node a bitcoin onion node. Tor is great about traversing routers and firewalls like a hot knife through butter.
  1. Download, verify1, install and initialize Gpg4win
  2. Download, verify2, install, and launch Tor Browser
  3. Download, verify3, install, and launch Bitcoin Core
  4. Launch an Admin command console in the directory with tor.exe
  5. Install the Tor service: tor.exe --service install
  6. CD to service dir: cd %windir%\ServiceProfiles\LocalService\AppData\Roaming\tor
  7. Create and edit a file called torrc with the contents suggested below
  8. Restart tor: tor --service stop && tor --service start
  9. Record your onion hostname: type .\HiddenService\hostname as
  10. Add the bitcoin.conf options suggested below
  11. Restart the bitcoin-qt program
  12. Verify node connectivity at https://bitnodes.io/nodes/-8333/

torrc file: (replace c:\windows with the proper path as needed)

```

Change to C:\Windows\ServiceProfiles\LocalService\AppData\Roaming

Log notice file \tor\service.log HiddenServiceDir \tor\HiddenService HiddenServiceVersion 2 HiddenServicePort 8333 127.0.0.1:8333 HiddenServicePort 18333 127.0.0.1:18333 ```

bitcoin.conf file: (entries to be ADDED)

```

Change to what you recorded earlier

onion=127.0.0.1:9050 listen=1 externalip= discover=1 ```
Footnotes:
  • 1 - Cert-Subject: "Intevation GmbH"  ;  Cert-SHA1: c13a65963ad53e78694dd223d518007791a05fe4
  • 2 - PGP Signing Key: 0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290
  • 3 - PGP Signing Key: 0x01EA5486DE18A882D4C2684590C8019E36C2E964
submitted by brianddk to brianddk [link] [comments]

How I synced on a 2013 ultrabook in a few days

Note: I don't know exactly how long it took because I didn't do it in one go. I guess it was like 4,5 days doing it only at night. At some points(2015Q3, 2018Q2) it slows down and ETA goes up to 16 weeks or something.
The main bottleneck is IO. My 2013 mobile i3 has enough processing power to sync, I only used 3 threads and most of the time only one was close to 100%. The two directories that need to be written and read from intensively are chainstate and blocks/index. I pruned to 2GB and chainstate didn't go much over 3GB during the entire process. blocks/index is like 100MB.
The best solution is to move chainstate and blocks/index to a ramdisk. If you don't have enough ram the linux kernel has a thing called zram. Zram creates a compressed swap(cache) file in ram, this effectively increases your ram size at the cost of a bit of processing power and access speed(of the compressed part). On my machine I can net a bit more than 1GB of extra ram. That's right, with linux you can download more ram! The second best solution is to leave chainstate and block/index on a sdd. From what I've tested it should take up between 5 whole days and 2 weeks.
With regards to config, I didn't see much benefit in increasing the db cache over the default 450MB in bitcoin-qt. If I recall correctly, smaller prune sizes make chainstate larger.
After the initial sync keeping up to date is very easy on resources. You can catch up a week in a few minutes. At the moment bitcoind is using 400MB but I'm still working on bringing that number down.
Remember: If you want safety or if you want to help the network you need o run a full node. A full node is a node that verifies all transactions. A pruned node is a full node.
Edit: bitocoind really likes to hover around 400MB, sometimes it gets higher than that, some times it get's lower. A lot of that is data, not code, so if you start running out of ram your OS should drop those pages and get down to 250~300MiB. If you really want the memory to be this low all the time, on linux, you can either: Use cgroups to set the swappiness of the process to 99 so all data gets swapped but not code does; Use systemd and set MemoryLimit=300MiB(for example) so almost all data gets swapped but no code. I don't think any of those options are worth the small setup hassle.
submitted by nothing_works4me to Bitcoin [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]

My wallet has been trying to synchronize for 40 minutes now, halp?

submitted by throwawayasdf1234asd to Bitcoin [link] [comments]

Why there isn't a zip file of the blockchain for the first 3 years for quick download?

So if the blockchain is a pain in the ass to download for the first time, why can not be in a zipfile for the first X years, and only the last few weeks or months need to be downloaded/upgraded? Is that really that hard to implement?
If bitcoin will really take off, there will be more and more transactions, so the blockchain is getting bigger and longer faster, so it would make sense that past months would be in an easily handable zip file. Even if this zipfile updated just bimonthly, that means that new users need to download only the last 2 months transactions, the previous years should be a quick download....
submitted by VirtualMoneyLover to Bitcoin [link] [comments]

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

Intro

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

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:
     

Extra

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

Credits:

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

[ELI5] How to send coins using Coinb.in

How to send coins from ANY wallet using https://coinb.in/#settings

Why?

Because cold wallets, such as those stored offline in a text file as I keep recommending in my standard advice below:
All you need is a text file to put your wallets in, like this example from https://walletgenerator.net/?currency=Dogecoin
1,"D7WBUpdgLRtG6WyPsqjhaKiJR65X8ZGnkZ","6KieLMW1poAzNVnmLuQZqA262gxEQ51eLGdDK8e2GL2B4LHCKKb" 2,"DM8LT16d49zHr8ByXbUwZb9UBXDGMaZRdc","6Ktgxdv6vN9v2bDHwcJBBb3oMRAgXJumESzBnxaXUSGFZoq6pWQ" 3,"D5UCa51AfxjtVHQ46oYXe2YfkctTeLXPhx","6L2WSPWadRYCwt2L1CxH6zC7PoTYY3KyjxdiUoCqi5eyq6hQKvj"
Use https://coinb.in/#settings to move coins. Download both sites and run them offline. Use https://bitinfocharts.com/dogecoin/ to check balances and transactions. See http://www.mocacinno.com/blog/create-sign-broadcast-transactions-using-coinb/ for coinb.in tutorial. And read the ELI5s (and my history) for more info.
Are without doubt THE SAFEST way to store your coins. Plus, they consume no resources. No bandwidth, no network stress for every node we have, no storage of 20Gb+ blockchains, no weeks of waiting for things to sync, no tearing your hair out and posting desperate pleas for help, and most importantly, no coins irretrievably lost because you or your client screwed up.

What?

Wallets, ALL WALLETS are nothing but numbers. Very large numbers, but fundamentally no different from “7”, “42”, “911” or a phone number. They cannot be created nor destroyed, and you either know them or you don’t. Anyone who knows a key can use it to spend any coins it controls. Anyone who doesn’t know it, can’t. Don’t be the guy who doesn’t know his own keys. Keep them safe. Make copies. Keep those safe. Don’t let your friends, kid brother or random burglar find them, but don’t lose them either.
The only other thing you need for a fully functional wallet is a way to spend coins. Coinb.in is such a way. There are others, such as DogeCoinMultiSig.org which tomcarbon built.
Oh, and you can and should download it and run it locally.

Where?

The default entry point for coinb.in is https://coinb.in/#settings because this settings page is very well hidden. Its in the tiny gear wheel on the Broadcast page.
Looking across the top of the page, you can see
  • + New
  • Verify
  • Sign
  • Broadcast
  • Wallet
  • About
We’re only going to use three of these. New, Sign, Broadcast.
Now, keep in mind that coinb.in is an old Bitcoin tool which tomcarbon added Dogecoin to. Sometimes it thinks its dealing with Bitcoin still, so if you see anything odd, go and make sure you’ve selected Dogecoin in the Settings page.

When?

This tool should be the only place you spend coins. Sure, some clients may look more convenient, but they all suffer from a very big coin-losing flaw. Whenever you split a UTXO, they create a new wallet to send the change to. And they DON’T TELL YOU! This means unless you back up after every transaction, you run a high risk of finding all your coins have ‘disappeared’ from your wallet, and you don’t recognise where they went.
So if you use a client for the convenience as well as a text list of your wallets, you won’t know to add a new wallet to your masterfile. Its best to ditch the clients entirely.

How?

Now we come to the nitty-gritty. Lets use those three wallets above and assume that #1 is the source, #2 the destination and #3 the change wallet. Note that these won’t actually work, as none of them have ever been used, but they will do as examples.
New Transaction
Located at the bottom of the New menu, this will give you a page to enter your wallets and amounts.
In the top field, you enter your source address or Key. If you use the key, it will calculate the address when you click the Load button, which should match what you expected. Note that Load only brings in the first 100 UTXOs. This is so that you can retrieve coins from high-volume wallets which would kill any client. Coinb.in is in fact the ONLY WAY to do this, as even QT falls over around 600 UTXOs.
You will see the total balance that was loaded in the Transaction Fee field. And also in the Inputs tab, where you can go to adjust which UTXOs to spend.
Now you need to add the wallet(s) and amounts to send to them. Lets suppose the source contained a single UTXO for 1,000 Doge. You want to send 500 of them. So you would enter the #2 address in the Address field, and 500 in the Amount field. The Fee now changes to 500, which is not what you want.
So you click the + button to bring up a new line, enter the change address and the other 500, making the fee zero.
And you’re done. Check that the Fee is indeed zero. Check that the amounts shown in the Outputs and Inputs tabs match exactly.

THIS IS CRITICAL!

There is a bug which will send all the coins to the miners if the Outputs exceed the Inputs. I would have expected the Fee to show as negative in such a situation, but it doesn’t. BE WARNED!
Once everything looks right, hit the Submit button.
This will give you a block of hex code. Copy it.
Sign
Go to the Sign tab and paste it. Add your private key for the source wallet and click Submit. Note this can be done offline for safety.
This will give you another block of hex, the SIGNED transaction.
Broadcast
Copy this and paste it in the Broadcast tab and click Submit.
That’s it. Your coins are on their way. Make a cuppa and settle in while they arrive in a minute or three.
Note: All fields retain their values unless you refresh the page! This can be a boon when doing multiple transactions, such as when emptying a huge wallet. But it can also be a trap for the unsuspecting. Refresh or close the window when you’re done.

Who?

Who should use this?
Absolutely EVERYONE!
Even if you’re wedded to your client in some satanic blood-contract, you should still know how this works, because sooner or later you’re going to have a problem you can’t fix without it.
Definitely download the site and store it on every device you have. On every USB backup of your wallets. On your phone (well, except iOS which doesn’t do local HTML), etc, etc, etc.
Oh, and if you’re a programmer SmartyShibe, do consider improving the code over on GitHub.
EDIT: https://github.com/OutCast3k/coinbin added courtesy of AtomHearth
submitted by Fulvio55 to dogecoin [link] [comments]

Beginners guide to Syscoin (SYS) and why you should be investing in this cryptocurrency in 2018

What is Syscoin?

Some have described Syscoin (SYS) as the Shopify, Amazon and Ebay of the blockchain world. Syscoin is a revolutionary cryptocurrency that offers near zero cost financial transactions, incredible speed and provides businesses the infrastructure to trade goods, assets, digital certificates and data securely. Syscoin isn’t just about money and trading, it has the ability to attract various business types thanks to its native set of features geared towards business on the blockchain. From eBay traders and High Street shops to Medical applications, Insurance and Gaming, Syscoin’s decentralized network benefits everyone!
Syscoin is developed by Blockchain Foundry (BF). BF provides blockchain technology based services, projects and products for a wide variety of use cases with the stated aim of disrupting markets by leveraging the potential of blockchain technology. Syscoin is mainly known to be the first cryptocurrency to offer a fully decentralized marketplace based on blockchain. What is lesser known is that this is only a part of what Syscoin offers.
With the introduction of Masternodes in February or March 2018 SYS will be transformed from just a ’marketplace coin’ to a completely ‘utilitarian coin’. The Masternode infrastructure allows the addition of decentralized databases and file storage, increased transaction speed to surpass POS/Visa/Mastercard capabilities, true Turing complete smart contract capabilities for unlimited business logic, sidechains, application layers and an identity layer. This will all be accessible through an API, rather than a new language, enabling nearly any developer to create any blockchain application they can conceive. This will usher in the next generation of blockchain applications - made for new or existing businesses - by conveniently offering everything available from the blockchain space today.

SYS Origin

The blockchain as conceptualized by Satoshi Nakamoto back in 2008 envisioned a peer-to-peer electronic cash network that would prevent double-spending. A year later, the blockchain became an integral part of bitcoin, serving as the latter's public ledger of transactions. Although Nakamoto's reference client mentioned a decentralized marketplace service, the subsequent implementation did not incorporate this due to a lack of resources.
Syscoin was initially described in a 2014 draft whitepaper that envisioned Decentralized Marketplace Creation, Decentralized Smart Contracts and Documents, Decentralized Certificate Issuance and Transfer, and Decentralized Data Storage and Retrieval, as among the services that it would offer upon its release.
Syscoin aimed to bring Nakamoto's vision of a decentralized marketplace back into the blockchain, among the other commercial-grade services it aims to deliver to clients. Other services that Syscoin plans to provide include secure data storage and transfer, and unique user aliases that link their owners to the services controlled by the alias.
The early Syscoin wallet was superseded by the release of Blockmarket Desktop 1.0 on September 12, 2017, marking the culmination of Syscoin's vision of a fully decentralized marketplace with a desktop GUI based on the blockchain.
The planned release of Blockmarket Web, a fully web-based version, and Blockmarket Professional in 2018 takes that vision one step further, as more advanced seller stores become a reality.

The Team

The Team that NEVER quits! Before the launch of Syscoin (Q3 2014), there was a presale ICO by Moolah (as a partner), which turned out to be detrimental for Syscoin. The project raised around 1,000BTC for development but the Syscoin Team only managed to access 250BTC which were used for price support. Moolah (Ryan Kennedy) absconded with the bulk of the ICO funds and the Syscoin team were left with ~30million Syscoin at a price around 400 satoshi. Even after this tragic event, the devs didn’t quit and continued to work on the project without stopping. The case against Moolah is still on-going. See the article from CoinDesk here: http://www.coindesk.com/uk-court-syscoin-injunction-moolah-750-btc/.
What is this detail telling us about the dev team? While some crypto projects are just scams and bring little to no innovation, they’ve proven that they are in it for the long term - ably demonstrated by the fact that they continued to work despite their funds being stolen. And now that hard work is beginning to pay off with the entire team going full-time for the first time in January 2018 and new developers being hired following VC funding for BF.

Team Page: https://syscoin.org/team/

Blockchain Foundry Products

https://www.blockchainfoundry.co/products

What is Blockmarket Desktop?

Building on the World's First Decentralized Marketplace, Blockmarket is the newest generation of Syscoin's Desktop wallet with a complete, state-of-the-art marketplace built-in where you can securely and reliably buy and sell any items you wish. Entire stores can be created directly through the marketplace where you can sell your own products or re-sell others’ products for commission. Use of blockchain technology eliminates middlemen, credit card fees, maintenance fees, downtime and political interference. Persons are literally able to buy or sell anything to anyone, anytime, anywhere on Earth! Blockmarket Desktop was launched on September 12, 2017.

Key Blockmarket Features

• Price Pegging to currencies such as USD, EUR, GBP, CAD, CNY and BTC
• Bitcoin and Zcash as payment options
• Arbitrated Escrow
• Encrypted Messaging
• KYC/AML Compliance
• Images
• Unlimited Inventory Items

Name Aliases

Wallet addresses for cryptocurrencies generally consist of a unique string of between 27-34 alphanumeric characters. Such an address isn’t easy to memorize. Although the addresses can be added to an address book within the wallet, Syscoin has taken the user's convenience one step further, allowing you to create a unique Alias for your wallet address, such as a name, title, or characters specific to a username. These can be used to send SYS from home, to a mobile wallet, to work, to friends, to common suppliers or to repeat customers easily, without requiring any memorizing, writing it down, copy & pasting or emailing yourself the address.

Digital Certificates

Using the cryptography of the blockchain persons can issue, authorize, and exchange digital certificates of any kind. With Syscoin anyone can issue provably-unique certificates with text or ASCII content to one or multiple parties on the Syscoin blockchain. These certificates can be authenticated by anyone via Syscoin’s cryptographic proof of work. This allows for the creation and free exchange of any kind of digital asset such as ownership certificates, warranties, receipts, tickets, certifications, diplomas, software licenses and more.

Integrated Exchanges

Integrated Crypto exchanges - Flypme and Changelly will facilitate exchanging 30+ cryptos for SYS, directly within the Blockmarket wallet.

Security Audit Verified

Blockmarket was successfully and independently security audited by Digital Boundary Group and was deemed low risk. Audit Results: [https://medium.com/@BlockchainFoundry/blockmarket-security-audit-results-and-next-steps-f69f94f149bf]

Blockmarket Web – (The Key to Mass Adoption)

BM web will bring SYS’s existing decentralized marketplace and all its features into a web-based version, enabling ease of use with a simple email and password login (grandma friendly) without any need for downloading a wallet or waiting for sync. Blockmarket web will be launched in February 2018.

Key Syscoin Developments

Masternodes

Ability for world-class transactions-per-second performance to scale-out with added nodes (theoretically 100k TPS per 1000 Masternodes, 300k TPS/3k masternodes, etc). In later releases, masternodes will also process smart contracts and facilitate sharded+encrypted offchain file-storage (with onchain anchors), among other touted functionality. They should also result in steadying the price movements - less volatility as holding will be incentivized

Smart Contracts

Scalable Ethereum Virtual Machine: Allows Turing complete smart contracts to be executed following the ethereum protocol at a much faster speed and at a fraction of the ethereum gas price.

Assets & Token Issuance

With its token issuance service, Syscoin allows anyone to create a custom asset token which can then be sent directly to anyone else on the network. This facilitates a variety of use cases including ICO token issuance, supply chain management, reward points, and loyalty programs.

Anonymous Transactions

Anonymous transactions: via mixing/shuffling at user-specified denomination. Afterwards, additional tech will be added in the near future which will further compound the degree of anonymity provided -Add ValueShuffle running on top of the masternode layer and you have the world's most advanced privacy tech in any coin. This brings true money fungibility to Syscoin and the missing link for true economic sovereignty. https://twitter.com/realSidhuJag/status/948588279540035584

Instant Send

Transactions can be sent and received instantly. This represents a similar sending capability as Dash, but is a step beyond- A type of backend node locking will allow an instantly received sum to be sent immediately, without delay, and without network risk of double-spend.

Why Invest in Syscoin?

https://medium.com/@StevenVoros88/the-most-undervalued-project-in-the-crypto-world-not-for-long-96814ac66b08 https://medium.com/@danieljasonwestby/syscoin-the-hidden-gem-of-2018-96f973b81b9 https://twitter.com/Asbsvc/status/939959284246380545 https://twitter.com/CryptoBulld0g/status/935915911776784384 https://medium.com/@BlockchainFoundry/syscoin-to-disrupt-ebay-and-real-estate-industries-96aa55ef709a https://medium.com/@thecryptojournal.com/top-crypto-investment-for-2017-b99656491c6f https://www.youtube.com/watch?v=VNDprLJhGys

Merchants

https://medium.com/@BlockchainFoundry/merchant-pilot-program-update-7479fe451639

Partnerships

(Microsoft Azure)[https://azure.microsoft.com/en-us/blog/syscoin-joins-azure/]

Decentralized Identity Foundation

https://medium.com/@BlockchainFoundry/consensus-decentralized-identity-foundation-blockmarket-beta-3-beyond-6f830419ea55

White Paper

http://syscoin.org/whitepaper.pdf
Note: It is anticipated that the whitepaper will be updated by the team in the near future due to recent developments

Roadmap

http://syscoin.org/images/roadmap_2018__1024.png

Blockchain Application Development Architecture

https://cdn-images-1.medium.com/max/1200/1*bUO6_nRI7q805edG59e0DQ.png

Feature List 2017 & 2018

https://pbs.twimg.com/media/DUJwbI_X4AI3QL_.jpg

Where to Buy

• Bittrex • Poloniex • Upbit • Tux Exchange • Livecoin • Yobit • AEX • Bittylicious • Changelly • Flyp.me

Wallets

• Block Market Wallet 1.2 – Windows and Mac. Download from https://syscoin.org/
• QT Wallet for Developers: Download from https://github.com/syscoin/syscoin2/releases/tag/2.1.6
• Coinomi – Syscoin MultiCoin Wallet (only supports send/receive)
• HolyTransaction – Syscoin Multicoin Web Wallet (desktop & android)

Other Sources

https://syscoin.org/ https://twitter.com/syscoin https://www.blockchainfoundry.co/ https://en.wikipedia.org/wiki/Syscoin
Disclaimer This post was created particularly to aid those who are new to Syscoin. Please note that the content provided within this post is for information purposes only and is not to be construed as investment advice.
submitted by one22manytimes to CryptoCurrency [link] [comments]

Anti-FUD: The BIP148 enforcing client - a walkthrough.

There seems to be a lot of FUD going around surrounding https://github.com/uasf/bitcoin/tree/0.14 <--that little guy. I'm a programmer, so let me walk you through what, exactly, is changed, and how you can verify what changes for yourself.
So, to get started, click on the 'Compare' button just below the green button that says 'clone or download'. link
This shows you every single change that has been merged between bitcoin core, in the 0.14 branch (the branch that was used to create the 0.14 Core client many of us use) and this repository's version of the 0.14 client, which requires any blocks after August 1, 2017 to support Segwit.
So, let's go through the page, top to bottom, and explain what it is telling you.
19 commits 4 files changed 3 commit comments 3 contributors 
That tells you that 19 times someone has changed something in the code base, in total, 4 files were changed by those 19 commits, 3 commit comments were made (think of these as replies to a thread on reddit), and 3 people total have made contributions to the code differences represented below.
Below that is a list of what commits were made on what day. You can click on the second column (BIP148 / Update client name to Satoshi BIP148 / etc) to see what changes were made in that version (compared to the version before it) specifically.
Scroll down until you hit
Showing with 19 additions and 5 deletions. 
This is where the 'fun' (programming) begins.

src/clientversion.cpp

-std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments) +std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments, const bool fBaseNameOnly) 
Red lines, which always start with a minus sign, means that line was removed from the file. Green lines, which always start with a + sign, mean that line was added. "But the line wasn't removed, just some stuff was added to the end!" Correct! This is a 'diff-ism'. Diff being the name of the program used to show differences between a file. Diff doesn't highlight just the part of the line that changed, it highlights the entire line, and leaves it to you to spot the changes in the line.
From the above, we can see a parameter was added to the end of the line. "But what does the line do!" Well, what you're looking at is a function declaration. What is a function? Well, imagine you wanted to build a robot to make sandwiches for you. You could make the sandwich yourself, but it's easier if an automated system does it for you. The function is like the robot; you put a specific set of tasks into the robot's programming, give it a specific set of inputs (bread, knife, meat/cheese/spreads/etc) and it returns the resultant sandwich. The way to read the declaration is this:
std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments, const bool fBaseNameOnly) 
  1. std::string The first argument is the return type of the function. In this case, a C++ string.
  2. FormatSubVersion This is the name of the function
  3. (const std::string& name, the first parameter of the function, since it is unchanged from Core, and unmodified by other changes in the file, I will not bother explaining what it does.
  4. int nClientVersion, Second parameter to the function. Same thing, original, unmodified, skipping.
  5. const std::vector& comments, Parameter 3, unchanged, skipping.
  6. , const bool fBaseNameOnly) Parameter 4, 'const bool' means two things: 1) we cannot change the value of this variable in the code. 2) it's a 'bool' type, which is short for boolean. It an either be true or false, those are the only values it can ever have. What does it do? Let's keep reading.

std::ostringstream ss; 
That's important for later, make note of it.
if (!fBaseNameOnly) ss << "UASF-Segwit:0.2(BIP148)/"; 
The above is the change uses the newly minted parameter 4 to add a bit of text into the output stream. Specifically, the string "UASF-Segwit:0.2(BIP148)/" is tacked on to whatever is ahead of it in the output stream. The net result of this change is that clients using this code will report their client version as '/Santoshi:0.14.0/UASF-Segwit:0.2(BIP148)/' instead of the standard value of '/Santoshi:0.14.0/'.
File complete! Next file.

src/clientversion.h

Within C or C++ programming, you have the concept of 'code files' (ending in .c or .cpp) and 'header files' (ending in .h). Strictly speaking, any code can be in either file and the compiler will figure it out (assuming you give it enough information to do so). However, programming conventions exist. Since I assume the readers of this post are (largely) not programmers, I won't bore you. It's a convention used for sanity only, and it is a convention followed by the bitcoin source code. In general, program code that 'does stuff' goes in .c and .cpp files, and the code needed to tell the compiler (compiler = the thing that converts these text files into a program) where to 'find stuff' goes into .h files.
-std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments); +std::string FormatSubVersion(const std::string& name, int nClientVersion, const std::vector& comments, bool fBaseNameOnly = false); 
Well, because this is the exact same function call we just talked about in the previous section, I'll skip going through the parameters one by one, and instead focus only on the change: , bool fBaseNameOnly = false).
"WAIT! It has 'const' before bool in the .cpp file! That's bad right!?" No. The compiler will see const in the .cpp file and mandate the variable be const.
"WAIT! Here it says '= false' and in the .cpp file it doesn't!" Again, not a problem. Remember how I said some code goes in .c/.cpp files, and some in .h files? Well, this is a case where which file contains what code actually does matter. Basically, you can't set a default value for a parameter inside a .c/.cpp file. You can only do that in a .h file. So...that's 100% correct. Here is the souce code for a quick little program to see this behavior:
--test.cpp--
#include "test.h" #include  #include  int main() { function(); } int function(const bool tmp) { tmp = !tmp; } 
---test.h---
int function(bool test = false); 
--If you tried to compile this, you'd get--
g++ test.cpp test.cpp: In function ‘int function(bool)’: test.cpp:12:6: error: assignment of read-only parameter ‘tmp’ tmp = !tmp; 
In this case, 'read only' means 'was declared const'.
Remember how a 4th parameter was added in the code above? Well, you have to tell the compiler to expect that parameter, which you do here, in the header file. That line of code tells the compiler to expect the 4th parameter. It also sets the default value of the parameter, should the caller not specify it, to be false.
Thus, you can call this function two ways:
  1. FormatSubVersion("Test", 99900, std::vector())
  2. FormatSubVersion("Test", 99900, std::vector(), true)
Using method 1 would result in a User Agent string of '/Test:99900/UASF-Segwit:0.2(BIP148)/', because the program uses the default value of 'false' and so it sticks in the bit about BIP148 support. Using method 2 would result in '/Test:99900/' "Wait, wait, how did you figure that out?" Look here, scroll to the bottom (line 88) and that is the FormatSubVersion function we went over above. All you do is built the string in steps as you read the code:
  1. Line 90: ""
  2. Line 91: "/"
  3. Line 92: "/Test:99900" {the 'Test' comes from the 'name' parameter, parameter 1. The : is statically coded (<< ":" <<) and the 99900 comes from nClientVersion, parameter 2}
  4. Line 93: From the function call, we see that parameter 3 is initialized 'std::vector()', this is an empty vector. If the vector had anything in it, it would look like this: std::vector('a')
  5. (because the if statement in line 93 fails, we go to: ) Line 101: "/Test:99900/"
  6. Line 102: (are we doing a version with or without the 4th parameter set to true?)
  7. Line 103: (if parameter 4 is false, line becomes "/Test:99900/UASF-Segwit:0.2(BIP148)/"
  8. Line 104: Convert the 'ss' variable to a standard C++ string and return the that string to whatever asked this function to be run.
SO, in total, this function literally just creates a string. Much like the robot-sandwich example, you give the function a client name, version, and list of comments and it builds you a string containing those things.

src/test/util_tests.cpp

This file is part of the automated testing for bitcoind/bitcoin-qt. When you compile the software, you'd typically run 'make check' before installing the software, to ensure that your changes didn't break anything and that your compile didn't go wrong. With the effort I've put into explaining the change to FormatSubVersion in the past two section, I believe you can now see that the only change made to this test is to ensure that the newly added code performs as expected.
That said, there is a 'defect' in this code. He should not have removed the 3 existing tests. He should have added 3 new tests. That way he'd have both 'positive' and 'negative' test case coverage. That said, it isn't something to fret about.

src/validation.cpp

All right, finally, the big file where all the cool shit happens!
+ // BIP148 mandatory segwit signalling. + if (pindex->GetMedianTimePast() >= 1501545600 && // Tue 1 Aug 2017 00:00:00 UTC + pindex->GetMedianTimePast() <= 1510704000 && // Wed 15 Nov 2017 00:00:00 UTC + !IsWitnessEnabled(pindex->pprev, chainparams.GetConsensus())) + { + // versionbits topbit and segwit flag must be set. + if ((pindex->nVersion & VERSIONBITS_TOP_MASK) != VERSIONBITS_TOP_BITS || + (pindex->nVersion & VersionBitsMask(chainparams.GetConsensus(), Consensus::DEPLOYMENT_SEGWIT)) == 0) { + return state.DoS(0, error("ConnectBlock(): relayed block must signal for segwit, please upgrade"), REJECT_INVALID, "bad-no-segwit"); + } + } + 
The entire section is newly added. Anything it does will be 'in addition to' whatever is already done. Let's go through the change line by line:
"Ok, but what about 1501545600? How do we know that?" It's an epoch timestamp. Google 'epoch converter', copy-paste that number in, convert to UTC, and you'll see it is correct for what the comment says it is.
The '&&' at the end of the line means 'and'. So in this case, 'if the mean age of the past few blocks is greater than or equal to and ...'
You can see proof of this claim in the tests written in src/test/versionbits_tests.cpp lines 277-281. line 277 creates an 'old format' block, then (line 279) checks that the ComputeBlockVersion function works, then verifies that the bitwise-and function returns TOP_BITS, as expected.
If you are concerned that more might be needed to reject a block, simply view src/validation.cpp on line 1892 and see that standard bitcoin Core code rejects blocks in the same way as the SEGWIT patch does.
"So wait, what is the total requirement to reject a block again?"
  1. If the mean age of the past few blocks is greater than or equal to AND the mean age of the past few blocks is less than or equal to AND the previous block did not show that Segwit was in 'active' state:
  2. If all of the conditions in step 1 are met AND the block either does not support BIP9 messaging, or does not signal support for SEGWIT
  3. Then it will be rejected.
"So wait, what happens after the first segregated witness block pops across the network? Hasn't that already happened?" No. Blocks that support segwit have come across the network, but in order for IsWitnessEnabled to return 'true', the SEGWIT state would need to switch to 'active' (see BIP9 spec), which is the final state of any proposal, and the point at which the setting is considered an accepted part of the blockchain.

Conclusions

So, you see, no muss, no fuss. The day-1 bug where the logic was backwards has been fixed. There is nothing to fear. Feel free to ask questions and I'll explain them over the next few hours/days as I am able. I'll try to talk to your level if I can. I like teaching in general and abhor ignorance in all its forms. Understand: ignorance strictly means 'not knowing', rather than the typical 'negative' connotation it gets in English speaking society. I would like everyone to realize just how simple this UASF patch is and that the FUD surrounding it not being 'verified' is absolutely a bad joke.
edit: Logic fix thanks to Phil. Like shaolinfry, I had my negated logic backwards. Oops.
submitted by Kingdud to Bitcoin [link] [comments]

How to Download and Verify the Armory Bitcoin Wallet how to mine for bitcoin core Download Blockchain hack, Bitcoin Hack Free version 2020 ... How To Use Bitcoin Testnet - Getting Free Testcoins - YouTube Downloading the Core - Qt Wallet (Litecoin)

0.8.1 Release notes. The 0.8.1 release has just two changes from the 0.8.0 release: A new block-acceptance rule that will be enforced from 21 March 2013 until 15 May 2013 to prevent accepting blocks that fail to validate on pre-0.8 peers. Download Bitcoin Core Latest version: 0.20.1 Download Bitcoin Core Bitcoin Core 0.20.1 ... Verify release signatures Download torrent Source code Show version history. Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ Or choose your operating system. Windows exe - zip. Mac OS X dmg - tar.gz. Linux (tgz) 64 bit. ARM Linux 64 bit - 32 bit. Linux (Snap Store) Support ... This site is nearly identical to electrum.org except the download links give different files. All three of the files that can be download are much smaller than the real electrum and are most likely malware. The three files are: electrum.exe - 91136 bytes electrum.out - 60316 bytes electrum.zip - 32478 bytes. EDIT: Some Advice: When installing software, especially something as import as wallet ... Recently there has been much debate in the Bitcoin community regarding Segregated Witness, hard forks and soft forks, and the usage of alternative node and mining software. The Armory developers (goatpig, droark, and achow101) support Segregated Witness as is in its current form, and also support Bitcoin Core. The Armory developers also oppose hard forks that may attack the original chain ... 1. Install Bitcoin-Qt Since version 0.9, Bitcoin-Qt was renamed to Bitcoin Core t o reduce confusion between Bitcoin-the-network and Bitcoin-the-software. Bitcoin Core is a full Bitcoin client. It is a thick client, meaning it requires the full blockchain (explained below) on local disk to operate and expose blockchain back to the network to help relay and verify transactions.

[index] [31123] [44352] [47191] [24011] [30468] [18659] [51174] [23391] [24784] [2028]

How to Download and Verify the Armory Bitcoin Wallet

💾 DOWNLOAD LINK: https://bit.ly/32sxvlS 🔐 PASSWORD: 1234 =====Don't forget===== LIKE COMMENT SHARE SUBSCRIBE Basic explanation of how to sign and verify a Bitcoin Adress from your Softwarewallet, example client was Bitcoin-qt. Feel free to donate to keep more Tutorials coming: In this video I show you how to download the Litecoin Core Wallet, also sometimes called the Litecoin Qt wallet. I make a mistake early on in the video when I say I "install" the wallet from terminal. But the Bitcoin plan calls for the creation of only 21 million bitcoins. In this way, Bitcoin will try to avoid the pitfalls of modern fiat currencies such as inflation, deflation, market ... How to Download & Verify the Bitcoin Core Wallet - Duration: 15:29. Rex Kneisley 18,412 views. 15:29. 6. bitcoin-qt - Duration: 6:50. 402 Payment Required 943 views. 6:50. How to start Bitcoin ...

#