Change Bitcoin Core Data Directory - BitcoinWiki

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]

Instaling BTC Core - Prune settings help

I am installing BTC Core for the first time on my mac. I am trying to instal the pruned verison.
What I've done is begun the complete installation by default because without there is no directory create on my system. When the installation begun and I had my directory then I accessed it the right way to create the bitcoin.conf file: - Library/Application Support/Bitcoin
Then to the conf file included prune=550 and then restarted the the installation.
Now the estimated time to sync is around the same as when I started without the prune.
Is this the right way to proceed? Is there any way to confirm that now a pruned version is being created?

Thanks for your help and also your understanding that I am a beginner with beginner questions.
submitted by valentinmuller to Bitcoin [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]

(Upvote to the top) > SOLUTION FOR ZCLASSIC Eleos Wallet: "Wallet daemon can not be run. Check if daemon does not already run"

So I noticed a lot of people recently (including myself) are experiencing the error "Wallet daemon can not be run. Check if daemon does not already run" when trying to open up their ZCL Eleos wallet, and people are unable to access their funds or cannot export their private keys as well. A solution to this is now official (thanks to JBrutWhat from the BTCP team for helping me out on this.) Note: Post is being edited as more info becomes available to me.
This solution also works for users who are on the ZClassic Swing wallet experiencing the error "A general unexpected critical error has occurred: error: Couldn't connect to server, see the console output for more detailed error information!."
Eleos Wallet Troubleshooting section
ZClassic Electrum Wallet
  1. Create a new standard wallet and restore the 2FA wallet using your "seed" codes. DO NOT password protect this wallet.
  2. Disable the 2FA feature when presented with the option.
  3. Navigate to C:/Users/YOUR-NAME/AppData/Roaming/Electrum-zcl/wallets. Open the new standard wallet file with Notepad.
  4. You will need to gather the 2 private keys and one public key. To find this easily, press “CTRL+F” and search for “xprv”. Copy the 2 “xprv” values as well as the last “xpub” value. You will need these in a later step.
  5. Create a new “Multi-signature wallet”. Select “From 3 co-signers” on the first slider. Select “Require 2 signatures” on the second slider.
  6. To add the first co-signer, click “Use public or private keys”. Enter the first xprv key in this box.
  7. Add the second co-signer via a private key also.
  8. Add the third co-signer with the public key. Complete the set-up.
  9. Your wallet funds now have the ability to be sent from the multi-signature wallet.
For Users who were already using the Electrum wallet beforehand, you can go to file > new/restore wallet > next > import zclassic private keys and input the private key you obtained from the walletaid tool, and it should import the wallet into the electrum wallet. Then from there, go to file > backup wallet and export a copy of the wallet.dat file onto an offline USB.
Reminder: Backup and delete the private keys file from your desktop pc/hard drive, move it into an offline USB for safekeeping. Do not leave it on an online device.
Donate to me if you found the guide useful! Your donations 100% voluntary but they are greatly appreciated and keep us going!
ZCL: t1fkxCWJs3f2oXznGwZuEgftJ2SCjYZ8VjZ
BTC: 14Xmfm9jf4h1h4RXZBQCFK6i4LWibqWVPu
LTC: LhAERgWcjbbXQbGqjhy4owALGhwfpj1aw2
ETH: 0xe723305337926e1fcb5dd0495e6648569a252c13
BCH: 1JXqLHqjYH8bew38AXwEt9dmKvsdYwLtvr
LINKS
(You can join the discord rooms where there are channels for users looking for help)
submitted by BestServerNA to ZClassic [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]

Groestlcoin September 2019 Development Release/Update!

For a more interactive view of changes, click here
In our current world; bordering on financial chaos, with tariff wars, Brexit and hyperinflation rife, you can count on Groestlcoin to consistently produce innovation that strikes to take the power away from the few and into the many, even after a full five and a half years of solid development.
Here is what the team has already announced in the last 3 months since the last development update:

What's Being Released Today?

Groestl Nodes

What am I?

Groestl Nodes aims to map out and compare the status of the Groestlcoin mainnet and testnet networks. Even though these networks share the same protocol, there is currently no way to directly compare these coins in a single location. These statistics are essential to evaluate the relative health of both networks.

Features

Source - Website

Groestlcoin Transaction Tool

What am I?

This is a tool for creating unsigned raw Groestlcoin transactions and also to verify existing transactions by entering in the transaction hex and converting this to a human-readable format to verify that a transaction is correct before it is signed.

Features

SourceDownload

Groestlcoin AGCore

What am I?

AGCore is an Android app designed to make it easier to run a Groestlcoin Core node on always-on Android appliances such as set-top boxes, Android TVs and repurposed tablets/phones. If you are a non-technical user of Groestlcoin and want an Android app that makes it easy to run a Groestlcoin Core node by acting as a wrapper, then AG Core is the right choice for you.

What's Changed?

Source - Download

Groestlcoin Electrum

What's Changed?

Android Electrum-Specific

OSXWindowsWindows StandaloneWindows PortableLinux - Android
Server SourceServer Installer SourceClient SourceIcon SourceLocale Source

Android Wallet – Including Android Wallet Testnet

What am I?

Android Wallet is a BIP-0032 compatible hierarchial deterministic Groestlcoin Wallet, allowing you to send and receive Groestlcoin via QR codes and URI links.

V7.11.1 Changes

Groestlcoin Java Library SourceSource - DownloadTestnet Download

Groestlwallet

What am I?

Groestlwallet is designed to protect you from malware, browser security holes, even physical theft. With AES hardware encryption, app sandboxing, keychain and code signatures, groestlwallet represents a significant security advance over web and desktop wallets, and other mobile platforms.
Simplicity is groestlwallet's core design principle. Because groestlwallet is "deterministic", your balance and entire transaction history can be restored from just your recovery phrase.

iOS 0.7.3 Changes

Android v89 Changes

iOS SourceAndroid Source - Android DownloadiOS Download

Groestlcoinomi Released

What am I?

Groestlcoinomi is a lightweight thin-client Groestlcoin wallet based on a client-server protocol.

Groestlcoinomi v1.1 Desktop Changes

Groestlcoinomi Android v1.6 Changes

Groestlcoin Java Library SourceAndroid Source
Android DownloadWindows DownloadMac OS DownloadLinux Download

Groestlcoin BIP39 Tool

What's Changed?

Source - Download
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Can i catch a modder with Wireshark? (PC)

April 22nd, 2017 New Working Trick to fight modders*: Reencode their mod menu executables to make it look like a virus on VirusTotal.com, causing their own mods to get deleted by Windows Defender:
https://github.com/tanc7/ModMenuPoisoneraw/masteModMenusRuined.jpg
Isn't that sexy?
It's a really simple trick too! Here is a How-To-Video:
https://raw.githubusercontent.com/tanc7/ModMenuPoisonemasteHowToUseModMenuPoisoner.webm
You need Kali Linux with Metasploit Framework Installed, a VM version for simple users is right here:
https://www.offensive-security.com/kali-linux-vmware-virtualbox-image-download/
Then download VirtualBox:
https://www.virtualbox.org/wiki/Downloads
Then run VirtualBox with Kali Linux as a virtual machine and download my toolkit:
https://github.com/tanc7/ModMenuPoisoner
  1. Copy/paste the unzipped file directory of the mod menu
  2. Take the re-encoded file that now looks like a virus and submit it to VirusTotal: https://virustotal.com/
  3. Wait up to 2 to 3 weeks, eventually a antivirus update is pushed to users on Windows 8 and 10 machines, Windows Defender will auto-flag the menu executable as a virus and "kill it".
Video: Installation my Mod Menu Poisoner in Kali Linux, for total Linux Newbies
https://raw.githubusercontent.com/tanc7/ModMenuPoisonemasteHowToInstallandUseForTotalNewbies.webm
OLD STUFF
I rewrote the post after my discovery of how the network traffic works. The answer in short, unfortunately, is NO. But R* can detect it. I will assure you.
From several tests, there are NO distinguishable traffic from the UDP protocol, in a public lobby that allows you to identify a modder, if you are being harassed by one.
However, I tested two mod menus on my decoy account (I have two Steam accounts, and two Rockstar Social Club Accounts). The one thing that is significant is that there is a suspicious communication to the Rockstar servers. Mod menus generate DTLSv1.0 packets. Sent to Rockstar's servers at "192.81.241.100 prod.ros.rockstargames.com". Playing the game legitimately, no DTLSv1.0 packets are sent. But if you load a mod menu, Rockstar knows.
The problem is, it is traffic going to the dedicated Game Service Servers. You, as a random person in a public lobby, will not be able to see it.
TLDR... Let Rockstar catch and ban modders. You will never find them
They are doing a pretty decent job. According to MPGH chatter, since four days ago a lot of the mod developers are pulling out of implementing money hacks into the game. As they cannot find a way to get past R* Anticheat yet. http://www.mpgh.net/forum/forumdisplay.php?f=414
I tested the one with the "Safe Money Drop". My decoy account got banned for 30 days.
But you could be a real creepster. And tell people with unprotected (no VPN no proxy) internet connections, what city and state they live in. That still works.
How to do that? I tested it on 5 different people already, all my friends.
In-game, you have to be following the player around. The closer you are with the player, the more bytes are generated and sent between your IP and theirs. That helps you distinguish their IP from anyone else's.
Now
Start Wireshark capture Statistics Endpoints Bytes Tab (Sort by highest) Your highest NON-LOCAL IP on ports 6672 (UDP, most players have traffic through this) is the player's IP
Using that IP, you can choose to either click the Name Resolution Checkbox on the bottom left of the Endpoints window. Or, you can just Google it.
The potential of this vulnerability? DO NOT DO THIS
Lets say you wanted to be a douchelord or something, and you don't like another player. Keep GTA V running in Windowed Mode, fire up wireshark, start capture. Locate the player IN-GAME and follow him around for at least one or two minutes.
After you positively identified the player's IP (using the bytes-captured method on port 6672), you can attack it with a subscription DDoS/DoS Botnet provider. Also known as a "stresser" or "booter" for obvious reasons. (Note: they only accept either BitCoin or PayPal, I hate both of them). A few examples...
(1) Defiance Protocol
(2) Thunder Stresser
(3) PolyStress
(4) Stress3d.me
(5) DataBooter
(6) ExoStresser
What does it do if you choose to do this?
Well, first of all, even though they are known as booters or stressers, they initiate a Denial of Service attack on the victim machine. That means even if you left the session (you better), you can initiate the attack. It will shutdown their entire home network for a X amount of ms, just enough to kick someone, including the host of the lobby, out of the session.
All you need to know to launch the attack is...
(a)The IP address of victim machine
(b)The Port you want to attack (port 6672)
(c)The method of attack (chose one that is relevant to the protocol), like TCPStorm, DOMINATE, SYNFLOOD, etc.
Seriously, don't do it. All I figured out is how to stalk my friends on GTA V. I have yet to even learn how to decrypt the captured GVSP data. If you want to catch modders on your own, you need to crack that hash. Seems like there is a new key generated a session. Hopefully R* in GTA VI will patch this vulnerability.
GOOD LUCK,
DON'T DoS people,
and GO sign up for a VPN or Proxy, RIGHT NOW.
Stuff Online on DTLSv1.0 Traffic
https://wiki.wireshark.org/DTLS
DTLS is a SSL Protocol that is compatible through UDP. It can be used to create SSH Tunnels back to R* Servers.
Since the last thing a mod developer wants to do is give R* all of your info willingly, I am assuming that this DTLS traffic is part of the anticheat mechanism implemented by R*.
DTLS traffic, as of yet, cannot be filtered by capture alone. However, you simply just look at the packet, and then filter the UDP traffic and port to display the majority of DTLS traffic.
Example Packet Summary:
Modder Machine To RockstaTake Two Interactive, New York, New York Upon Use of a Mod
Frame 204: 151 bytes on wire (1208 bits), 151 bytes captured (1208 bits) on interface 0 Interface id: 0 Censored TO Avoid MAC Ban Encapsulation type: Ethernet (1) Arrival Time: Jan 19, 2017 18:23:39.836486000 Pacific Standard Time [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1484879019.836486000 seconds [Time delta from previous captured frame: 0.002543000 seconds] [Time delta from previous displayed frame: 0.002543000 seconds] [Time since reference or first frame: 1.598633000 seconds] Frame Number: 204 Frame Length: 151 bytes (1208 bits) Capture Length: 151 bytes (1208 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ethertype:ip:udp:dtls] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Censored TO Avoid MAC Ban Internet Protocol Version 4, Src: 10.0.1.113 (10.0.1.113), Dst: prod.ros.rockstargames.com (192.81.241.100) User Datagram Protocol, Src Port: 58016 (58016), Dst Port: 61457 (61457) Datagram Transport Layer Security
Modder Machine To Victim Machine Upon Giving Him All Weapons from Mod Menu. Victim is from Miami, Florida
Frame 210: 101 bytes on wire (808 bits), 101 bytes captured (808 bits) on interface 0 Interface id: 0 Censored TO Avoid MAC Ban Encapsulation type: Ethernet (1) Arrival Time: Jan 19, 2017 18:23:39.887777000 Pacific Standard Time [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1484879019.887777000 seconds [Time delta from previous captured frame: 0.000169000 seconds] [Time delta from previous displayed frame: 0.000169000 seconds] [Time since reference or first frame: 1.649924000 seconds] Frame Number: 210 Frame Length: 101 bytes (808 bits) Capture Length: 101 bytes (808 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ethertype:ip:udp:gvsp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Censored TO Avoid MAC Ban Internet Protocol Version 4, Src: 10.0.1.113 (10.0.1.113), Dst: c-75-74-37-8.hsd1.fl.comcast.net (75.74.37.8) User Datagram Protocol, Src Port: vision_server (6672), Dst Port: vision_server (6672) Source Port: vision_server (6672) Destination Port: vision_server (6672) Length: 67 Checksum: 0x7c17 [unverified] [Checksum Status: Unverified] [Stream index: 2] GigE Vision Streaming Protocol Undecoded byte number: 50 (0x0030+2) Undecoded byte number: 51 (0x0030+3) Undecoded byte number: 52 (0x0030+4) Undecoded byte number: 53 (0x0030+5) Undecoded byte number: 54 (0x0030+6) Undecoded byte number: 55 (0x0030+7) Undecoded byte number: 56 (0x0030+8) Undecoded byte number: 57 (0x0030+9) Undecoded byte number: 58 (0x0030+10) Undecoded byte number: 59 (0x0030+11) Undecoded byte number: 60 (0x0030+12) Undecoded byte number: 61 (0x0030+13) Undecoded byte number: 62 (0x0030+14) Undecoded byte number: 63 (0x0030+15) Undecoded byte number: 64 (0x0040+0) Undecoded byte number: 65 (0x0040+1) Undecoded byte number: 66 (0x0040+2) Undecoded byte number: 67 (0x0040+3) Undecoded byte number: 68 (0x0040+4) Undecoded byte number: 69 (0x0040+5) Undecoded byte number: 70 (0x0040+6) Undecoded byte number: 71 (0x0040+7) Undecoded byte number: 72 (0x0040+8) Undecoded byte number: 73 (0x0040+9) Undecoded byte number: 74 (0x0040+10) Undecoded byte number: 75 (0x0040+11) Undecoded byte number: 76 (0x0040+12) Undecoded byte number: 77 (0x0040+13) Undecoded byte number: 78 (0x0040+14) Undecoded byte number: 79 (0x0040+15) Undecoded byte number: 80 (0x0050+0) Undecoded byte number: 81 (0x0050+1) Undecoded byte number: 82 (0x0050+2) Undecoded byte number: 83 (0x0050+3) Undecoded byte number: 84 (0x0050+4) Undecoded byte number: 85 (0x0050+5) Undecoded byte number: 86 (0x0050+6) Undecoded byte number: 87 (0x0050+7) Undecoded byte number: 88 (0x0050+8) Undecoded byte number: 89 (0x0050+9) Undecoded byte number: 90 (0x0050+10) Undecoded byte number: 91 (0x0050+11) Undecoded byte number: 92 (0x0050+12) Undecoded byte number: 93 (0x0050+13) Undecoded byte number: 94 (0x0050+14) Undecoded byte number: 95 (0x0050+15) Undecoded byte number: 96 (0x0060+0) Undecoded byte number: 97 (0x0060+1) Undecoded byte number: 98 (0x0060+2) Undecoded byte number: 99 (0x0060+3) Undecoded byte number: 100 (0x0060+4)
Update: The Solo Public Lobby Glitch Works (Somewhat)
https://www.reddit.com/gtaonline/comments/4n8094/tip_if_you_are_on_pc_block_these_ports_using_you?ref=share&ref_source=link
So this was months old, and its a archived post but basically he says you can glitch yourself into a SOLO public lobby by blocking your game ports to R*'s servers.
That is only partially correct by now, January 20th 2017. The game will still attempt to connect to you to a filled public lobby, BUT, it will be much less populated.
Now you need to block both inbound and outbound communications on UDP ports on..
(His Original Post) Select UDP and put in these ports 6672, 61455, 61457, 61456, 61458 These are R* game server ports and select next.
Through the Windows 10 Firewall Settings.
You should have Firewall running at all times anyways. Even though my Airport Extreme already has a smart firewall installed.
Windows Firewall Settings
https://scontent.flas1-1.fna.fbcdn.net/v/t1.0-9/16195900_402016770142664_9185237840131020577_n.jpg?oh=cec83e04c1fa93cd3402702a5b8b867f&oe=591C283E
These are the settings you must have on Windows Firewall, on Windows 10.
Make one rule for INBOUND and one for OUTBOUND. You can do this while playing the game.
Set them to enabled and change session. You should be on a new lobby with MUCH LESS PLAYERS. Keep Lobby-Surfing until you end up alone or the other people leave.
My Wireshark capture tells me that the only other player in the game is connected to me via UDP 35464. He eventually left. Leaving me in a session by myself.
It won't guarantee you a solo lobby anymore, but it makes it much rarer for packed lobbies with modders and jet griefers.
If you are feeling lonely, then disable those firewall rules and switch session again.
I still have a UDP connection via 6672 despite the rules. My wireshark picks up no traffic at all though.
Hmm interesting. If you block your traffic it now generates DTLSv1.0 traffic (like modder traffic) to Rockstar at 192.81.241.100. There is also a lot more TCP traffic through Port 80 (but its still obfuscated). And it is going through my blocked UDP ports in the new firewall rules. It basically SSH tunneled through UDP directly to R*. So it's just me and their gameserver. No one else.
Well the admins know I am not cheating. They prolly think I have a lousy internet connection or a jerk of a admin (they think) who doesn't want me to use UDP gaming ports. I am not worried at all.
If you wanna sell all of your shit without being picked on. Then do this,
enable the firewall rules both inbound and outbound,
sell your shit,
and then disable them and switch sessions again so you won't be lonely anymore.
Here are the packet captures that I am WILLING to share. Basically it shows two things.
R* Will open a SSH tunnel secret in at least TWO conditions
(1) If you are modding. There will be a SSH Tunnel created using the DTLSv1.0 protocol on your UDP ports. Telling R* what you are doing if your game traffic looks suspicious
(2) If you are using the firewall glitch, the game will get around your Windows Software Firewall and start connecting to R* with the SSH tunnel.
https://drive.google.com/file/d/0B5Beow8WOgBFODJJNTN0d3VGYW8/view?usp=sharing
For #2 if you check on my packet capture links, even though I told Windows Firewall to block that UDP port, packets were sent through anyways as DTLS traffic. I have yet to be banned for this.
This ensures that R* can still save my data. And you get to have less populated and/or totally alone sessions so you can play the damn game!
And here is a example of normal traffic. Me and three of my friends in a 4-player Survival Game
https://drive.google.com/file/d/0B5Beow8WOgBFRU1veG52N1VCZkU/view?usp=sharing
Edit: Uploaded a 38 minute video, soloing biker deliveries without interference from other players. Works as long as I end up being the only player in the session, no new players can join because I blocked my ports
https://drive.google.com/file/d/0B5Beow8WOgBFbzBSY3VnWkZyMU0/view?usp=sharing
Other Possible Ramifications (Very Bad If It's True!)
Not to freak everyone out. But it MAY be possible, for someone with actual hacking talent (not me), to drop a Staged Meterpreter Shell into your computer, assuming that he or she knows your IP address through the discovery on Wireshark. They can then...
(1) Have the payload on execution rewrite a critical system file in your computer
(2) Download the remaining stages of the payload
(3) Slowly compromise other system processes on your computer
(4) Gain root-access (Administrator in Windows)
(5) Start executing commands as Root/Admin
(6) Do creepy shit like use your webcam to take a picture of your face. Or steal your saved payment information in your browser cookies for Amazon, etc.
I typically would picture our typical home networks like this in a typical game lobby on GTA Online
Me
Laptop running GTA V My Router and Firewalls My Public IP (UDP Port 6672) My ISP
You
ISP routing path Your ISP Your Public IP (UDP Port 6672 and/or other) Your Home Router and Firewalls Your Computer
The problem with the UDP protocol, is that it has very little verification and checksumming. It just keeps spamming packets, making it viable for low latency applications (gaming).
If I can make a virus or reverse shell look like typical game data, then it SHOULD get through your firewall, and automatically get forwarded by your router to your computer. As long as I am connected to you, all the validation is authentic. As long as I am connected to you, either in a game mode, or through the public lobby!
If those conditions are met. Then it's going to look like regular traffic to your network.
I have yet to even try this. I did managed to reencode a standard reverse shell payload (msfvenom) and infected myself with it (successfully SSH tunneling through my own router from the WWW against my Linux installation). However, my Windows variant failed to execute due to Windows User Account Controls. Windows Defender was futilely, furiously searching for this "virus", and eating up all my hard drive usage (100% while playing GTA) until I finally removed it after running a scan with HitmanPro (a heuristics second-opinion scanner that hunts for files that exhibit virus/malware like activity).
PSA: DO NOT USE WIRESHARK TO MONITOR GTA V TRAFFIC, R* EULA HAS RECENTLY BEEN CHANGED, DEPENDING ON SEVERITY IT MAY BE A INSTANT PERMANENT BAN
At 4:30 AM PST, January 22nd, my account received a permanent ban as I was with my friends on their yacht looking through the scope of a sniper rifle in the middle of a Piracy Prevention Match.
As it turns. Sniffing network traffic via Wireshark may or may not be a ground for a ban. Regardless of whether or not I am doing it right now.
I even double checked the vague Rockstar Games EULA to make sure.
https://www.rockstargames.com/eula
You agree not to:
reverse engineer, decompile, disassemble, display, perform, prepare derivative works based on, or otherwise modify the Software, in whole or in part;
Well I attempted to! And I violated a good half of those.
cheat or utilize any unauthorized robot, spider, or other program in connection with any online features of the Software;
"Spider" (I am guessing they are referring to internet crawlers), but "other program"? Yeah Wireshark fits the bill.
TECHNICAL PROTECTIONS: The Software may include measures to control access to the Software, control access to certain features or content, prevent unauthorized copies, or otherwise attempt to prevent anyone from exceeding the limited rights and licenses granted under this Agreement. Such measures may include incorporating license management, product activation, and other security technology in the Software and monitoring usage, including, but not limited to, time, date, access, or other controls, counters, serial numbers, and/or other security devices designed to prevent the unauthorized access, use, and copying of the Software, or any portions or components thereof, including any violations of this Agreement. Licensor reserves the right to monitor use of the Software at any time. You may not interfere with such access control measures or attempt to disable or circumvent such security features, and if you do, the Software may not function properly. If the Software permits access to Special Features, only one copy of the Software may access those Special Features at one time. Additional terms and registration may be required to access online services and to download Software updates and patches. Only Software subject to a valid license can be used to access online services, including downloading updates and patches. Except as otherwise prohibited by applicable law, Licensor may limit, suspend, or terminate the license granted hereunder and access to the Software, including, but not limited to, any related services and products, at any time without notice for any reason whatsoever.
The Secret UDP SSH Tunnel (DTLSv1.0), got it. R* Anticheat. Check. Don't fuck with it? Naw mang, sorry, totally lost it. Well... if I straight up spilled the beans on how your anticheat works, including what it could possibly do and can't do, and how it might work, I'd guess you'd be pretty mad at me too.
Especially since posting on Reddit is the equivalent of me following you around IRL with a megaphone, screaming in public in earshot "Don't trust him! He is reading your shit! He's looking through your gameplay traffic right now. And he knows everything!!!!"
By installing and using the Software, you consent to the information collection and usage terms set forth in this section and Licensor’s Privacy Policy, including (where applicable) (i) the transfer of any personal information and other information to Licensor, its affiliates, vendors, and business partners, and to certain other third parties, such as governmental authorities, in the U.S. and other countries located outside Europe or your home country, including countries that may have lower standards of privacy protection; (ii) the public display of your data, such as identification of your user-created content or displaying your scores, ranking, achievements, and other gameplay data on websites and other platforms; (iii) the sharing of your gameplay data with hardware manufacturers, platform hosts, and Licensor’s marketing partners; and (iv) other uses and disclosures of your personal information or other information as specified in the above-referenced Privacy Policy, as amended from time to time. If you do not want your information used or shared in this manner, then you should not use the Software.
Remember what I said about DDoSing people that are discovered on Wireshark? If you do this, and the victim knows the right people to call, I wouldn't be surprised if G-Men in suits knock on your door.
At first, I thought, that was it. Then I decided to go Google "GTA V Banwave" and set the time to one week ago. What I saw was a real trip. A huge spike in fake bans and urgent warnings, "PSA's" all over YouTube
It's something related to the latest iteration of Mod Menus that have been popping up. I have not seen so much panic run through the forums of UnknownCheats and MPGH in my life. New versions, updates, and customized variants of Mod Menus have been popping up on a daily basis. And with a detection period from launch, of at most, a week long. That is, the day that the new mod menu gets uploaded, to the point that users start to report they are getting banned for it, can be up from a week from now. R* anticheat went into overdrive. Developers have been scaling back on implementing the money drop feature for fear of triggering instant bans for their users (hence the lack of money drops recently). Then I noticed something...
The prevailing issue of "Persistent Mods" and possible "Memory Corruption" implicating innocent players
I am talking about mod menus that permanently break a lobby's features like free roam missions, like CEO or Bikers, but this time, it can carry over betweens lobby sessions. I saw my first variant earlier this week and shrugged it off. Then I saw my second one today. Some modder was caging me and my friends and trying to flatten us with Bugattis.
Normally I would just join another session and any wacky attachment would fall off. But now the damage, errors, and bugs caused by mod menus can "carry-over" with me. I realized that I couldn't change my Outfits via the "Style Menu" for the second session in a row, I could not eat snacks to regenerate health, nor could I equip body armor. In some cases, I couldn't register as a CEO and start my missions, even though I already SWITCHED to a new lobby.
After fully restarting the game from Steam, the "mod persistence" ceased. I had full control of my character again. Because we are talking about starting over again with fresh untainted memory.
First instance of discussion of innocent bans recently https://www.youtube.com/watch?v=rKYnCDolKSc
This video claims that you should be avoiding public lobbies on the PC like the plague or apocalypse. IDK if you have to be THAT extreme. Just don't interact too much with modders. Or try glitching yourself into a solo public lobby via the firewall glitch.
This is really sad though. This guy is a victim of a modder, and he gets a ban for it, probably from memory corruption caused by the modders that Rockstar's Anticheat picked up https://www.youtube.com/watch?v=_1IEs-Bf7Is
I am certain that if you react quickly enough, you will NOT get flagged by the modder's actions. You just need to do a full restart of the game. Not your PC. Just the game on Steam. So don't enjoy a modder's company for too long, no matter how pleasant they may appear.
Holy fuck dude. The game still costs $60 on Steam. After all these years. I'll just wait until my decoy account gets unbanned. I'll see you guys in 30 days.
Fortunately, it is NOT a MAC Ban. I logged into my decoy account. Decoy account still has a one month suspension.
submitted by ctlister to GTA [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]

Some updates on joinmarket-clientserver

Hi, so here are a few things going on; also at the end some notes about using Joinmarket in today's environment:
I was prompted on this by user Onecoinbob, although there's a very valid discussion about whether wallets should have gone straight to bech32 addresses (instead of p2sh wrap), the reality is that some have (in particular, Electrum) and so I think it's pretty important that people can send coins there. Whether doing direct send (no coinjoin, -N 0), coinjoin, or in joinmarket-Qt you can now use bech32 addresses like "bc1qyzd2qj8tdrvyacvtknj2xav900qkr3a2xjrmg7" as valid destinations. Only master branch for now, will make a new release soon, it's a bit overdue.
Thanks to a couple of other users (including trotski2000), we have instructions how you can install manually in docs/INSTALL.md should there be some problem with the one-step installation. Feel free to ask on github issue or IRC or here (maybe ping me) for more help on this, but note I personally don't run a MacOS machine so I will redirect you.
I recently found that people don't know this exists, indeed I first created it nearly 2 years ago!.
See the PR ; this is backend stuff so little direct relevance to users; devs may be interested, it looks like a really good effort to rationalize and improve this section of the code.
I have started doing work on this, but it's not a small job, Joinmarket being very byte-manipulation heavy means there's quite a lot of changes to get it working on both 2 and 3. However it's really a good idea, a lot of useful libraries are migrating to/only supported on Py3. No real date or goal here.
I think most users already figured this out, but as a Taker the hit on fees from using Joinmarket is far too high in almost all cases (nothing to do with coinjoin fees; just Bitcoin network fees, which the Taker pays basically all of). It is possible in the model to share these fees, by certain sets of configuration, but the system hasn't really been set up like that.
Alternatively, the Taker may lowball a fee to a crazy extent and lock up the Maker coins for a long time.
I'd advise against using Joinmarket in periods of very high fees like we had last week; I'd even advise against Makers running their bots to prevent newbies suffering an unexpectedly high hit on fees. But of course everyone can make their own decision.
(EDIT: Forgot to add the really important thing, which is that whatever kind of transaction you're doing, including direct_send, seriously consider using the feature that setting tx_fees to any value above 144 results in using that figure as a custom fee in satoshis per kB, with a small randomization. So setting tx_fees = 300000 in the config means using a fee of 300 sat/b. Has been mentioned before but bears repeating!)
For myself, I have been actively looking at a number of alternative models (see some of my blog posts at https://joinmarket.me/blog/blog for example, my CoinswapCS repo, also "Snicker"), and of course other people are looking at things too e.g. the ZeroLink project of nopara.
Joinmarket as a model may also continue to be viable if the fee regime changes, and/or when new tech comes online that changes the economics (Schnorr in particular; CT itself would radically change the economics/viability of coinjoin but that is another discussion).
submitted by waxwing to joinmarket [link] [comments]

The Nexus FAQ - part 1

Full formatted version: https://docs.google.com/document/d/16KKjVjQH0ypLe00aoTJ_hZyce7RAtjC5XHom104yn6M/
 

Nexus 101:

  1. What is Nexus?
  2. What benefits does Nexus bring to the blockchain space?
  3. How does Nexus secure the network and reach consensus?
  4. What is quantum resistance and how does Nexus implement this?
  5. What is Nexus’ Unified Time protocol?
  6. Why does Nexus need its own satellite network?
 

The Nexus Currency:

  1. How can I get Nexus?
  2. How much does a transaction cost?
  3. How fast does Nexus transfer?
  4. Did Nexus hold an ICO? How is Nexus funded?
  5. Is there a cap on the number of Nexus in existence?
  6. What is the difference between the Oracle wallet and the LLD wallet?
  7. How do I change from Oracle to the LLD wallet?
  8. How do I install the Nexus Wallet?
 

Types of Mining or Minting:

  1. Can I mine Nexus?
  2. How do I mine Nexus?
  3. How do I stake Nexus?
  4. I am staking with my Nexus balance. What are trust weight, block weight and stake weight?
 

Nexus 101:

1. What is Nexus (NXS)?
Nexus is a digital currency, distributed framework, and peer-to-peer network. Nexus further improves upon the blockchain protocol by focusing on the following core technological principles:
Nexus will combine our in-development quantum-resistant 3D blockchain software with cutting edge communication satellites to deliver a free, distributed, financial and data solution. Through our planned satellite and ground-based mesh networks, Nexus will provide uncensored internet access whilst bringing the benefits of distributed database systems to the world.
For a short video introduction to Nexus Earth, please visit this link
 
2. What benefits does Nexus bring to the blockchain space?
As Nexus has been developed, an incredible amount of time has been put into identifying and solving several key limitations:
Nexus is also developing a framework called the Lower Level Library. This LLL will incorporate the following improvements:
For information about more additions to the Lower Level Library, please visit here
 
3. How does Nexus secure the network and reach consensus?
Nexus is unique amongst blockchain technology in that Nexus uses 3 channels to secure the network against attack. Whereas Bitcoin uses only Proof-of-Work to secure the network, Nexus combines a prime number channel, a hashing channel and a Proof-of-Stake channel. Where Bitcoin has a difficulty adjustment interval measured in weeks, Nexus can respond to increased hashrate in the space of 1 block and each channel scales independently of the other two channels. This stabilizes the block times at ~50 seconds and ensures no single channel can monopolize block production. This means that a 51% attack is much more difficult to launch because an attacker would need to control all 3 channels.
Every 60 minutes, the Nexus protocol automatically creates a checkpoint. This prevents blocks from being created or modified dated prior to this checkpoint, thus protecting the chain from malicious attempts to introduce an alternate blockchain.
 
4. What is quantum resistance and how does Nexus implement it?
To understand what quantum resistance is and why it is important, you need to understand how quantum computing works and why it’s a threat to blockchain technology. Classical computing uses an array of transistors. These transistors form the heart of your computer (the CPU). Each transistor is capable of being either on or off, and these states are used to represent the numerical values 1 and 0.
Binary digits’ (bits) number of states depends on the number of transistors available, according to the formula 2n, where n is the number of transistors. Classical computers can only be in one of these states at any one time, so the speed of your computer is limited to how fast it can change states.
Quantum computers utilize quantum bits, “qubits,” which are represented by the quantum state of electrons or photons. These particles are placed into a state called superposition, which allows the qubit to assume a value of 1 or 0 simultaneously.
Superposition permits a quantum computer to process a higher number of data possibilities than a classical computer. Qubits can also become entangled. Entanglement makes a qubit dependant on the state of another, enabling quantum computing to calculate complex problems, extremely quickly.
One such problem is the Discrete Logarithm Problem which elliptic curve cryptography relies on for security. Quantum computers can use Shor’s algorithm to reverse a key in polynomial time (which is really really really fast). This means that public keys become vulnerable to quantum attack, since quantum computers are capable of being billions of times faster at certain calculations. One way to increase quantum resistance is to require more qubits (and more time) by using larger private keys:
Bitcoin Private Key (256 bit) 5Kb8kLf9zgWQnogidDA76MzPL6TsZZY36hWXMssSzNydYXYB9KF
Nexus Private Key (571 bit) 6Wuiv513R18o5cRpwNSCfT7xs9tniHHN5Lb3AMs58vkVxsQdL4atHTF Vt5TNT9himnCMmnbjbCPxgxhSTDE5iAzCZ3LhJFm7L9rCFroYoqz
Bitcoin addresses are created by hashing the public key, so it is not possible to decrypt the public key from the address; however, once you send funds from that address, the public key is published on the blockchain rendering that address vulnerable to attack. This means that your money has higher chances of being stolen.
Nexus eliminates these vulnerabilities through an innovation called signature chains. Signature chains will enable access to an account using a username, password and PIN. When you create a transaction on the network, you claim ownership of your signature chain by revealing the public key of the NextHash (the hash of your public key) and producing a signature from the one time use private key. Your wallet then creates a new private/public keypair, generates a new NextHash, including the corresponding contract. This contract can be a receive address, a debit, a vote, or any other type of rule that is written in the contract code.
This keeps the public key obscured until the next transaction, and by divorcing the address from the public key, it is unnecessary to change addresses in order to change public keys. Changing your password or PIN code becomes a case of proving ownership of your signature chain and broadcasting a new transaction with a new NextHash for your new password and/or PIN. This provides the ability to login to your account via the signature chain, which becomes your personal chain within the 3D chain, enabling the network to prove and disprove trust, and improving ease of use without sacrificing security.
The next challenge with quantum computers is that Grover’s algorithm reduces the security of one-way hash function by a factor of two. Because of this, Nexus incorporates two new hash functions, Skein and Keccak, which were designed in 2008 as part of a contest to create a new SHA3 standard. Keccak narrowly defeated Skein to win the contest, so to maximize their potential Nexus combines these algorithms. Skein and Keccak utilize permutation to rotate and mix the information in the hash.
To maintain a respective 256/512 bit quantum resistance, Nexus uses up to 1024 bits in its proof-of-work, and 512 bits for transactions.
 
5. What is the Unified Time protocol?
All blockchains use time-stamping mechanisms, so it is important that all nodes operate using the same clock. Bitcoin allows for up to 2 hours’ discrepancy between nodes, which provides a window of opportunity for the blockchain to be manipulated by time-related attack vectors. Nexus eliminates this vulnerability by implementing a time synchronization protocol termed Unified Time. Unified Time also enhances transaction processing and will form an integral part of the 3D chain scaling solution.
The Unified Time protocol facilitates a peer-to-peer timing system that keeps all clocks on the network synchronized to within a second. This is seeded by selected nodes with timestamps derived from the UNIX standard; that is, the number of seconds since January 1st, 1970 00:00 UTC. Every minute, the seed nodes report their current time, and a moving average is used to calculate the base time. Any node which sends back a timestamp outside a given tolerance is rejected.
It is important to note that the Nexus network is fully synchronized even if an individual wallet displays something different from the local time.
 
6. Why does Nexus need its own satellite network?
One of the key limitations of a purely electronic monetary system is that it requires a connection to the rest of the network to verify transactions. Existing network infrastructure only services a fraction of the world’s population.
Nexus, in conjunction with Vector Space Systems, is designing communication satellites, or cubesats, to be launched into Low Earth Orbit in 2019. Primarily, the cubesat mesh network will exist to give Nexus worldwide coverage, but Nexus will also utilize its orbital and ground mesh networks to provide free and uncensored internet access to the world.
 

The Nexus Currency (NXS):

1. How can I get Nexus?
There are two ways you can obtain Nexus. You can either buy Nexus from an exchange, or you can run a miner and be rewarded for finding a block. If you wish to mine Nexus, please follow our guide found below.
Currently, Nexus is available on the following exchanges:
Nexus is actively reaching out to other exchanges to continue to be listed on cutting edge new financial technologies..
 
2. How much does a transaction cost?
Under Nexus, the fee structure for making a transaction depends on the size of your transaction. A default fee of 0.01 NXS will cover most transactions, and users have the option to pay higher fees to ensure their transactions are processed quickly.
When the 3D chain is complete and the initial 10-year distribution period finishes, Nexus will absorb these fees through inflation, enabling free transactions.
 
3. How fast does Nexus transfer?
Nexus reaches consensus approximately every ~ 50 seconds. This is an average time, and will in some circumstances be faster or slower. NXS currency which you receive is available for use after just 6 confirmations. A confirmation is proof from a node that the transaction has been included in a block. The number of confirmations in this transaction is the number that states how many blocks it has been since the transaction is included. The more confirmations a transaction has, the more secure its placement in the blockchain is.
 
4. Did Nexus hold an ICO? How is Nexus funded?
The Nexus Embassy, a 501(C)(3) not-for-profit corporation, develops and maintains the Nexus blockchain software. When Nexus began under the name Coinshield, the early blocks were mined using the Developer and Exchange (Ambassador) addresses, which provides funding for the Nexus Embassy.
The Developer Fund fuels ongoing development and is sourced by a 1.5% commission per block mined, which will slowly increase to 2.5% after 10 years. This brings all the benefits of development funding without the associated risks.
The Ambassador (renamed from Exchange) keys are funded by a 20% commission per block reward. These keys are mainly used to pay for marketing, and producing and launching the Nexus satellites.
When Nexus introduces developer and ambassador contracts, they will be approved, denied, or removed by six voting groups namely: currency, developer, ambassador, prime, hash, and trust.
Please Note: The Nexus Embassy reserves the sole right to trade, sell and or use these funds as required; however, Nexus will endeavor to minimize the impact that the use of these funds has upon the NXS market value.
 
5. Is there a cap on the number of NXS in existence?
After an initial 10-year distribution period ending on September 23rd, 2024, there will be a total of 78 million NXS. Over this period, the reward gradient for mining Nexus follows a decaying logarithmic curve instead of the reward halving inherent in Bitcoin. This avoids creating a situation where older mining equipment is suddenly unprofitable, encouraging miners to continue upgrading their equipment over time and at the same time reducing major market shocks on block halving events.
When the distribution period ends, the currency supply will inflate annually by a maximum of 3% via staking and by 1% via the prime and hashing channels. This inflation is completely unlike traditional inflation, which degrades the value of existing coins. Instead, the cost of providing security to the blockchain is paid by inflation, eliminating transaction fees.
Colin Cantrell - Nexus Inflation Explained
 
6. What is the difference between the LLD wallet and the Oracle wallet?
Due to the scales of efficiency needed by blockchain, Nexus has developed a custom-built database called the Lower Level Database. Since the development of the LLD wallet 0.2.3.1, which is a precursor to the Tritium updates, you should begin using the LLD wallet to take advantage of the faster load times and improved efficiency.
The Oracle wallet is a legacy wallet which is no longer maintained or updated. It utilized the Berkeley DB, which is not designed to meet the needs of a blockchain. Eventually, users will need to migrate to the LLD wallet. Fortunately, the wallet.dat is interchangeable between wallets, so there is no risk of losing access to your NXS.
 
7. How do I change from Oracle to the LLD wallet?
Step 1 - Backup your wallet.dat file. You can do this from within the Oracle wallet Menu, Backup Wallet.
Step 2 - Uninstall the Oracle wallet. Close the wallet and navigate to the wallet data directory. On Windows, this is the Nexus folder located at %APPDATA%\Nexus. On macOS, this is the Nexus folder located at ~/Library/Application Support/Nexus. Move all of the contents to a temporary folder as a backup.
Step 3 - Copy your backup of wallet.dat into the Nexus folder located as per Step 2.
Step 4 - Install the Nexus LLD wallet. Please follow the steps as outlined in the next section. Once your wallet is fully synced, your new wallet will have access to all your addresses.
 
8. How do I install the Nexus Wallet?
You can install your Nexus wallet by following these steps:
Step 1 - Download your wallet from www.nexusearth.com. Click the Downloads menu at the top and select the appropriate wallet for your operating system.
Step 2 - Unzip the wallet program to a folder. Before running the wallet program, please consider space limitations and load times. On the Windows OS, the wallet saves all data to the %APPDATA%\Nexus folder, including the blockchain, which is currently ~3GB.
On macOS, data is saved to the ~/Library/Application Support/Nexus folder. You can create a symbolic link, which will allow you to install this information in another location.
Using Windows, follow these steps:
On macOS, follow these steps:
Step 3 (optional) - Before running the wallet, we recommend downloading the blockchain database manually. Nexus Earth maintains a copy of the blockchain data which can save hours from the wallet synchronization process. Please go to www.nexusearth.com and click the Downloads menu.
Step 4 (optional) - Extract the database file. This is commonly found in the .zip or .rar format, so you may need a program like 7zip to extract the contents. Please extract it to the relevant directory, as outlined in step 2.
Step 5 - You can now start your wallet. After it loads, it should be able to complete synchronization in a short time. This may still take a couple of hours. Once it has completed synchronizing, a green check mark icon will appear in the lower right corner of the wallet.
Step 6 - Encrypt your wallet. This can be done within the wallet, under the Settings menu. Encrypting your wallet will lock it, requiring a password in order to send transactions.
Step 7 - Backup your wallet.dat file. This can be done from the File menu inside the wallet. This file contains the keys to the addresses in your wallet. You may wish to keep a secure copy of your password somewhere, too, in case you forget it or someone else (your spouse, for example) ever needs it.
You should back up your wallet.dat file again any time you create – or a Genesis transaction creates (see “staking” below) – a new address.
 

Types of Mining or Minting:

1.Can I mine Nexus?
Yes, there are 2 channels that you can use to mine Nexus, and 1 channel of minting:
Prime Mining Channel
This mining channel looks for a special prime cluster of a set length. This type of calculation is resistant to ASIC mining, allowing for greater decentralization. This is most often performed using the CPU.
Hashing Channel
This channel utilizes the more traditional method of hashing. This process adds a random nonce, hashes the data, and compares the resultant hash against a predetermined format set by the difficulty. This is most often performed using a GPU.
Proof of Stake (nPoS)
Staking is a form of mining NXS. With this process, you can receive NXS rewards from the network for continuously operating your node (wallet). It is recommended that you only stake with a minimum balance of 1000 NXS. It’s not impossible to stake with less, but it becomes harder to maintain trust. Losing trust resets the interest rate back to 0.5% per annum.
 
2. How do I mine Nexus?
As outlined above, there are two types of mining and 1 proof of stake. Each type of mining uses a different component of your computer to find blocks, the CPU or the GPU. Nexus supports CPU and GPU mining on Windows only. There are also third-party macOS builds available.
Please follow the instructions below for the relevant type of miner.
 
Prime Mining:
Almost every CPU is capable of mining blocks on this channel. The most effective method of mining is to join a mining pool and receive a share of the rewards based on the contribution you make. To create your own mining facility, you need the CPU mining software, and a NXS address. This address cannot be on an exchange. You create an address when you install your Nexus wallet. You can find the related steps under How Do I Install the Nexus Wallet?
Please download the relevant miner from http://nexusearth.com/mining.html. Please note that there are two different miner builds available: the prime solo miner and the prime pool miner. This guide will walk you through installing the pool miner only.
Step 1 - Extract the archive file to a folder.
Step 2 - Open the miner.conf file. You can use the default host and port, but these may be changed to a pool of your choice. You will need to change the value of nxs_address to the address found in your wallet. Sieve_threads is the number of CPU threads you want to use to find primes. Ptest_threads is the number of CPU threads you want to test the primes found by the sieve. As a general rule, the number of threads used for the sieve should be 75% of the threads used for testing.
It is also recommended to add the following line to the options found in the .conf file:
"experimental" : "true"
This option enables the miner to use an improved sieve algorithm which will enable your miner to find primes at a faster rate.
Step 3 - Run the nexus_cpuminer.exe file. For a description of the information shown in this application, please read this guide.
 
Hashing:
The GPU is a dedicated processing unit housed on-board your graphics card. The GPU is able to perform certain tasks extremely well, unlike your CPU, which is designed for parallel processing. Nexus supports both AMD and Nvidia GPU mining, and works best on the newer models. Officially, Nexus does not support GPU pool mining, but there are 3rd party miners with this capability.
The latest software for the Nvidia miner can be found here. The latest software for the AMD miner can be found here. The AMD miner is a third party miner. Information and advice about using the AMD miner can be found on our Slack channel. This guide will walk you through the Nvidia miner.
Step 1 - Close your wallet. Navigate to %appdata%\Nexus (~/Library/Application Support/Nexus on macOS) and open the nexus.conf file. Depending on your wallet, you may or may not have this file. If not, please create a new txt file and save it as nexus.conf
You will need to add the following lines before restarting your wallet:
Step 2 - Extract the files into a new folder.
Step 3 - Run the nexus.bat file. This will run the miner and deposit any rewards for mining a block into the account on your wallet.
For more information on either Prime Mining or Hashing, please join our Slack and visit the #mining channel. Additional information can be found here.
 
3. How do I stake Nexus?
Once you have your wallet installed, fully synchronized and encrypted, you can begin staking by:
After you begin staking, you will receive a Genesis transaction as your first staking reward. This establishes a Trust key in your wallet and stakes your wallet balance on that key. From that point, you will periodically receive additional Trust transactions as further staking rewards for as long as your Trust key remains active.
IMPORTANT - After you receive a Genesis transaction, backup your wallet.dat file immediately. You can select the Backup Wallet option from the File menu, or manually copy the file directly. If you do not do this, then your Nexus balance will be staked on the Trust key that you do not have backed up, and you risk loss if you were to suffer a hard drive failure or other similar problem. In the future, signature chains will make this precaution unnecessary.
 
4. I am staking with my Nexus balance. What are interest rate, trust weight, block weight, and stake weight?
These items affect the size and frequency of staking rewards after you receive your initial Genesis transaction. When staking is active, the wallet displays a clock icon in the bottom right corner. If you hover your mouse pointer over the icon, a tooltip-style display will open up, showing their current values.
Please remember to backup your wallet.dat file (see question 3 above) after you receive a Genesis transaction.
Interest Rate - The minting rate at which you will receive staking rewards, displayed as an annual percentage of your NXS balance. It starts at 0.5%, increasing to 3% after 12 months. The rate increase is not linear but slows over time. It takes several weeks to reach 1% and around 3 months to reach 2%.
With this rate, you can calculate the average amount of NXS you can expect to receive each day for staking.
Trust Weight - An indication of how much the network trusts your node. It starts at 5% and increases much more quickly than the minting (interest) rate, reaching 100% after one month. Your level of trust increases your stake weight (below), thus increasing your chances of receiving staking transactions. It becomes easier to maintain trust as this value increases.
Block Weight - Upon receipt of a Genesis transaction, this value will begin increasing slowly, reaching 100% after 24 hours. Every time you receive a staking transaction, the block weight resets. If your block weight reaches 100%, then your Trust key expires and everything resets (0.5% interest rate, 5% trust weight, waiting for a new Genesis transaction).
This 24-hour requirement will be replaced by a gradual decay in the Tritium release. As long as you receive a transaction before it decays completely, you will hold onto your key. This change addresses the potential of losing your trust key after months of staking simply because of one unlucky day receiving trust transactions.
Stake Weight - The higher your stake weight, the greater your chance of receiving a transaction. The exact value is a derived by a formula using your trust weight and block weight, which roughly equals the average of the two. Thus, each time you receive a transaction, your stake weight will reset to approximately half of your current level of trust.
submitted by scottsimon36 to nexusearth [link] [comments]

Installation of Flutter and setup on MAC - YouTube Easily Install Anaconda Python Distribution On Mac OS X ... How to bind an OS X El Capitan Mac to Active Directory ... How to Mine Bitcoin on Mac with Honeyminer - YouTube How To Mine 1 Bitcoin in 10 Minutes - Blockchain BTC Miner ...

Click Next to start installation. Destination Folder Screen (Optional) Choose preferred directory then click Next. Choose Start Menu Screen. Click Install. Installation Screen. Wait until installation completes then click Next. Finish Screen. Click Finish to start Bitcoin Wallet. Welcome Screen of Bitcoin Core Wallet. On the first load, Bitcoin Qt will ask you to choose directory where your ... 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. Electrum Bitcoin Wallet. Impressum This website is hosted by Electrum Technologies GmbH Electrum Technologies was founded by Thomas Voegtlin in 2013. Its mission is to develop, package and distribute Electrum software, and to provide services to Bitcoin users and businesses. This will create the directory bitcoin-0.20.1 within your current working directory. We will install the contents of its bin subdirectory into the /usr/local/bin directory using the the install command. The install command is part of the GNU coreutils available on nearly every Linux distribution, and the /usr/local/bin directory is a standard location for self-installed executables (you may ... If your data directory already contains a complete block chain and or/wallet, you may want to move it rather than start from scratch. The first step is finding the default data directory. Mac, Windows, and Linux version of Bitcoin Core each store data in a different location. The procedure described here will use a graphical file browser to ...

[index] [11153] [42376] [37077] [19837] [12793] [29974] [6191] [23406] [50936] [2372]

Installation of Flutter and setup on MAC - YouTube

How to setup and install GUI Miner - Duration: 3:59. BitcoinTutorials 5,817 ... KnCMiner Jupiter - Bitcoin Miner 500GH/s+ 28nm ASIC chips - unboxing and setup 1080p - Duration: 4:18. Florian ... SUPPORT THE CHANNEL ON PATREON: http://www.patreon.com/musictechhelpguy DOWNLOAD SPACESHIP DELAY FREE: https://www.kvraudio.com/product/spaceship-delay-by-mu... In this video we will be installing the anaconda package distribution for Python on Mac OS X. This environment is particularly useful for Data Science becaus... In this video tutorial i will show you the step by step guide to install MSSQL Server 2017 on Docker Container on Mac OS Mojave. This is the most latest meth... What it really takes to mine a Bitcoin in 10 Minutes. Firstly I'll show you a special free method to mine Bitcoin and send funds directly to your wallet in 1...

#