bitcoin-qt - Debug Window Console - Herong Yang

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your Private Keys

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your Private Keys

https://preview.redd.it/u4x1o4p37zc41.png?width=700&format=png&auto=webp&s=01d1ff52c0b7fc1c9ae5bb4f161979ad1f4bb559
I’m a longtime blockchain enthusiast and developer and one of my biggest gripes about this space is how quickly every new project is widely dismissed as a “scam” or “shitcoin” by so many people before it even gets off the ground. Sure, there is a lot of uncharted territory with pirates lurking to steal your bags left and right but with a small amount of personal education you can exist safely in the world of crypto I promise! With this article I aim to help lift your knowledge a little higher while helping keep your funds a little safer!

So What Is Happening?

On Tuesday February 18, 2020 a new coin named Ring (RNG) will be minted. This coin aims to bring two unique and fresh methods of proofing to the crypto game, quite literally: Agent-Based Hive Mining (borrowed from LCC) and Proof-of-Play Mining, where literal gameplay is used to hash and reward miners! To celebrate and help spread the word, the team is giving away claims of free RNG to all holders of the following coins:
  • Litecoin Cash (LCC)
  • Bitcoin (BTC)
  • Dash (DASH)
  • Dogecoin (DOGE)
It's being touted as the world's first crypto "4-way fork" but I'd really call it more of a "4-way claim" since its a brand new chain and not based on the code of any of the rewarded coins. It's simply a clever method of allowing a wider range of coin holders a chance to participate in the launch of these exciting new features!

How Will This Process Work?

On the 18th of February, a balance snapshot will be taken of the four chains listed above. Anyone holding a balance with any of these coins at the time of the snapshot will be forever eligible to claim their RNG at any time. Because the only way to prove ownership of a crypto address is to supply the private keys, and pretty much EVERYONE will tell you to guard those things with your life, below I will outline exactly what to do so there is absolutely 0% risk of losing a single satoshi! This method will apply to ANY claim rewards of any coin in the future as well. Always practice #SafeForking!

How Do I Safely Claim My RNG?

STEP 1 -- BEFORE THE SNAPSHOT -- VERIFY ACCESS TO YOUR PRIVATE KEYS
All core wallets will allow you to export a private key of any address in your wallet but many third party services like exchanges and hot wallets do not allow access to them. In these cases you will need to send your funds out of the third party service and into some kind of personal wallet where you can reach the private keys yourself. Then just wait for the snapshot to happen…
To make things easier on yourself, you can optionally collect your original coins into as few addresses as possible BEFORE the snapshot. Doing so reduces the number of keys you will need to empty and import later. It’s just less work!
\** SNAPSHOT HAPPENS HERE... ****
STEP 2 -- ATER THE SNAPSHOT -- EMPTY ALL ADDRESSES YOU WISH TO CLAIM
After the snapshot is confirmed, withdraw all coins OUT of each of your origin coin addresses into brand new addresses leaving the original ones quite empty. This way when you import later there is NO risk of losing anything! Also know that after you import these private keys you should never use them again for safety’s sake! It’s kind of the whole reason you’re even reading this article in the first place.
STEP 3 -- EXPORT PRIVATE KEYS FOR ALL ADDRESS YOU WISH TO CLAIM
This is the most difficult part, are you ready? Once each claim address is confirmed to be EMPTY, you must obtain each one’s private keys. This will entirely depend on the wallet you use (QT example below) but for all core wallets there is generally an option for exporting private keys somewhere in there. Collect them all!
How to Export QT Wallet Private Keys:⛔️ — DISABLE INTERNET FOR SAFETY — ⛔️- Open the QT wallet client- Click on HELP in the menu bar- Click on DEBUG WINDOW- Click on the CONSOLE tab- Click inside the input box at the bottom(if your wallet is locked…)- Type: walletpassphrase [Password] 600(this unlocks your wallet for 10 minutes)- Type: dumpprivkey [Address]- Copy the output hash, paste it into a list somewhere.(repeat as needed, clear your clipboard history after)- Type: walletlock (if applicable)⚡ — RE-ENABLE YOUR INTERNET —
STEP 4 -- IMPORT ALL PRIVATE KEYS INTO RNG CORE WALLET
\** PLEASE VERIFY THAT EVERY CLAIM ADDRESS IS EMPTY BEFORE CONTINUING... ****
The final step is to simply import each of these private keys into the new Ring Core Wallet to claim your free RNG rewards. The wallet handles this part automatically and you will see your new RNG balance right away. You can find this option under the File > Import Private Keys menu.
Importing a private key is the only way to prove ownership of a crypto address so this is unavoidable if you want to claim new coins from it. The steps above will allow you to prove ownership of your snapshotted address balance plus use its empty key to then claim your new coins thus keeping your original coins completely protected in the brand new address with a new private key (which you should now also keep VERY private!)
By emptying the address before you import it’s private key you eliminate the risk of theft entirely. One cannot take from an already empty jar. It should also be noted to NEVER use the imported address again as an added safety precaution*!*
👏👏👏 DONE! ENJOY YOUR FREE MONEY! 👏👏👏

How Much RNG Will I Receive?

Litecoin Cash holders will receive the highest claim ratio (5000 LCC = 1 RNG) as the LCC team are the ones responsible for creating Ring and wanted to extend a heart-felt thank you to the LCC community for their years of support. All other coins will be based on a 1:1 ratio with the value of Bitcoin at the time of the fork. This of course means 1 BTC = 1 RNG. For DASH and DOGE, however, their BTC market prices will determine their reward ratios. (For example if DASH is trading at 0.015 BTC each, then each DASH coin will net you a reward of 0.015 RNG to match.) Of course you don't need whole coins to claim, partial decimals work just fine!

What Value Will RNG Have?

That, my friends, is entirely up to the markets. No one in the history of crypto has had a perfect track record of price predictions so I'm not even going to try here. I will say, though, having gotten to play with their Testnet a bit so far that I am very impressed with the new Proof-of-Play method and how they have initially implemented it. It bodes very good things for the future of their project and this coin so I personally would expect its value to hold and most likely rise steadily as more people become aware of this groundbreaking new tech and it's potential to expand outward!

Is Litecoin Cash Still Going To Exist?

Absolutely! At least, from what I can gather. LCC has it's own purposes and will continue to be developed on. Ring is not meant to be a replacement or upgrade of any kind to Litecoin Cash. It is an entirely different proofing algorithm and a different mission statement altogether. It's more so meant to help expose the amazing new technologies developed on the LCC blockchain to a wider audience beyond simply its own fan base. If anything it'll act a sister chain that can help expose more folks to LCC in the future!

Disclaimer

While I am a moderator for the Litecoin Cash Discord server, I am writing this from an independent point of view as an educated crypto enthusiast with a passion for helping others navigate these waters. Having been an initial forker and third party developer on top of LCC myself, I feel I have some valuable insight into the direction the team is taking and I wanted to offer some sound advice for the upcoming Ring fork before the FUD gets caked on too thick.
I know a lot of people get scared easily in crypto because of the rampant scamming that goes on but I've watched this team work their asses off for two years to get out from under the stain of Charlie Lee's very biased, uneducated "its a scam" tweet which was endlessly parroted throughout the Litecoin community with nothing but blind party loyalty and no due diligence. The LCC folks are kind, wonderful hard-working people with big hearts and ambition and they have actually developed a unique proofing methodology that is likely going to impress a lot of people!
So before you go jumping on the "it's just another shitcoin" bandwagon please stop and take a real hard look at both Litecoin Cash (LCC) and Ring (RNG): two viable projects with something to bring to the table! If nothing else, hey, just claim your new coins and dump them off for some free money. You literally cannot lose if you PRACTICE SAFE FORKING!!!
Good luck, cryptonauts!
=A=
submitted by auscoine to RingCoin [link] [comments]

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your LCC Private Keys

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your LCC Private Keys

https://preview.redd.it/9csw52aw30d41.png?width=700&format=png&auto=webp&s=53ceb329c9772d7f0abbcc56b44ba405e34dd8a8
I’m a longtime blockchain enthusiast and developer and one of my biggest gripes about this space is how quickly every new project is widely dismissed as a “scam” or “shitcoin” by so many people before it even gets off the ground. Sure, there is a lot of uncharted territory with pirates lurking to steal your bags left and right but with a small amount of personal education you can exist safely in the world of crypto I promise! With this article I aim to help lift your knowledge a little higher while helping keep your funds a little safer!

So What Is Happening?

On Tuesday February 18, 2020 a new coin named Ring (RNG) will be minted. This coin aims to bring two unique and fresh methods of proofing to the crypto game, quite literally: Agent-Based Hive Mining (borrowed from LCC) and Proof-of-Play Mining, where literal gameplay is used to hash and reward miners! To celebrate and help spread the word, the team is giving away claims of free RNG to all holders of the following coins:
  • Litecoin Cash (LCC)
  • Bitcoin (BTC)
  • Dash (DASH)
  • Dogecoin (DOGE)
It's being touted as the world's first crypto "4-way fork" but I'd really call it more of a "4-way claim" since its a brand new chain and not based on the code of any of the rewarded coins. It's simply a clever method of allowing a wider range of coin holders a chance to participate in the launch of these exciting new features!

How Will This Process Work?

On the 18th of February, a balance snapshot will be taken of the four chains listed above. Anyone holding a balance with any of these coins at the time of the snapshot will be forever eligible to claim their RNG at any time. Because the only way to prove ownership of a crypto address is to supply the private keys, and pretty much EVERYONE will tell you to guard those things with your life, below I will outline exactly what to do so there is absolutely 0% risk of losing a single satoshi! This method will apply to ANY claim rewards of any coin in the future as well. Always practice #SafeForking!

How Do I Safely Claim My RNG?

STEP 1 -- BEFORE THE SNAPSHOT -- VERIFY ACCESS TO YOUR PRIVATE KEYS
All core wallets will allow you to export a private key of any address in your wallet but many third party services like exchanges and hot wallets do not allow access to them. In these cases you will need to send your funds out of the third party service and into some kind of personal wallet where you can reach the private keys yourself. Then just wait for the snapshot to happen…
To make things easier on yourself, you can optionally collect your original coins into as few addresses as possible BEFORE the snapshot. Doing so reduces the number of keys you will need to empty and import later. It’s just less work!
\** SNAPSHOT HAPPENS HERE... ****
STEP 2 -- ATER THE SNAPSHOT -- EMPTY ALL ADDRESSES YOU WISH TO CLAIM
After the snapshot is confirmed, withdraw all coins OUT of each of your origin coin addresses into brand new addresses leaving the original ones quite empty. This way when you import later there is NO risk of losing anything! Also know that after you import these private keys you should never use them again for safety’s sake! It’s kind of the whole reason you’re even reading this article in the first place.
STEP 3 -- EXPORT PRIVATE KEYS FOR ALL ADDRESS YOU WISH TO CLAIM
This is the most difficult part, are you ready? Once each claim address is confirmed to be EMPTY, you must obtain each one’s private keys. This will entirely depend on the wallet you use (QT example below) but for all core wallets there is generally an option for exporting private keys somewhere in there. Collect them all!
How to Export QT Wallet Private Keys:
⛔️ — DISABLE INTERNET FOR SAFETY — ⛔️
- Open the QT wallet client
- Click on HELP in the menu bar
- Click on DEBUG WINDOW
- Click on the CONSOLE tab
- Click inside the input box at the bottom
(if your wallet is locked…)
Type: walletpassphrase [Password] 600
(this unlocks your wallet for 10 minutes)
- Type: dumpprivkey [Address]
- Copy the output hash, paste it into a list somewhere.
(repeat as needed, clear your clipboard history after)
- Type: walletlock (if applicable)
⚡ — RE-ENABLE YOUR INTERNET — ⚡
DONE!
STEP 4 -- IMPORT ALL PRIVATE KEYS INTO RNG CORE WALLET
\** PLEASE VERIFY THAT EVERY CLAIM ADDRESS IS EMPTY BEFORE CONTINUING... ****
The final step is to simply import each of these private keys into the new Ring Core Wallet to claim your free RNG rewards. The wallet handles this part automatically and you will see your new RNG balance right away. You can find this option under the File > Import Private Keys menu.
Importing a private key is the only way to prove ownership of a crypto address so this is unavoidable if you want to claim new coins from it. The steps above will allow you to prove ownership of your snapshotted address balance plus use its empty key to then claim your new coins thus keeping your original coins completely protected in the brand new address with a new private key (which you should now also keep VERY private!)
By emptying the address before you import it’s private key you eliminate the risk of theft entirely. One cannot take from an already empty jar. It should also be noted to NEVER use the imported address again as an added safety precaution*!*
👏👏👏 DONE! ENJOY YOUR FREE MONEY! 👏👏👏

How Much RNG Will I Receive?

Litecoin Cash holders will receive the highest claim ratio (5000 LCC = 1 RNG) as the LCC team are the ones responsible for creating Ring and wanted to extend a heart-felt thank you to the LCC community for their years of support. All other coins will be based on a 1:1 ratio with the value of Bitcoin at the time of the fork. This of course means 1 BTC = 1 RNG. For DASH and DOGE, however, their BTC market prices will determine their reward ratios. (For example if DASH is trading at 0.015 BTC each, then each DASH coin will net you a reward of 0.015 RNG to match.) Of course you don't need whole coins to claim, partial decimals work just fine!

What Value Will RNG Have?

That, my friends, is entirely up to the markets. No one in the history of crypto has had a perfect track record of price predictions so I'm not even going to try here. I will say, though, having gotten to play with their Testnet a bit so far that I am very impressed with the new Proof-of-Play method and how they have initially implemented it. It bodes very good things for the future of their project and this coin so I personally would expect its value to hold and most likely rise steadily as more people become aware of this groundbreaking new tech and it's potential to expand outward!

Is Litecoin Cash Still Going To Exist?

Absolutely! At least, from what I can gather. LCC has it's own purposes and will continue to be developed on. Ring is not meant to be a replacement or upgrade of any kind to Litecoin Cash. It is an entirely different proofing algorithm and a different mission statement altogether. It's more so meant to help expose the amazing new technologies developed on the LCC blockchain to a wider audience beyond simply its own fan base. If anything it'll act a sister chain that can help expose more folks to LCC in the future!

Disclaimer

While I am a moderator for the Litecoin Cash Discord server, I am writing this from an independent point of view as an educated crypto enthusiast with a passion for helping others navigate these waters. Having been an initial forker and third party developer on top of LCC myself, I feel I have some valuable insight into the direction the team is taking and I wanted to offer some sound advice for the upcoming Ring fork before the FUD gets caked on too thick.
I know a lot of people get scared easily in crypto because of the rampant scamming that goes on but I've watched this team work their asses off for two years to get out from under the stain of Charlie Lee's very biased, uneducated "its a scam" tweet which was endlessly parroted throughout the Litecoin community with nothing but blind party loyalty and no due diligence. The LCC folks are kind, wonderful hard-working people with big hearts and ambition and they have actually developed a unique proofing methodology that is likely going to impress a lot of people!
So before you go jumping on the "it's just another shitcoin" bandwagon please stop and take a real hard look at both Litecoin Cash (LCC) and Ring (RNG): two viable projects with something to bring to the table! If nothing else, hey, just claim your new coins and dump them off for some free money. You literally cannot lose if you PRACTICE SAFE FORKING!!!
Good luck, cryptonauts!
=A=
submitted by auscoine to LCCofficial [link] [comments]

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

Intro

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

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

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

Extra

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

Credits:

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

Walk through of how to claim BCD Bitcoin Diamond

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

How to Mine BiblePay on Windows

This guide is outdated, please refer to:
https://wiki.biblepay.org/POBH_Setup
https://wiki.biblepay.org/PODC_Setup
 
 
 
 
 
 
 
 
IMPORTANT - Evolution Upgrade:
Quick Start https://wiki.biblepay.org/Quick_Start
Evolution Upgrade Information https://wiki.biblepay.org/Evolution_Upgrade
Getting Started with Evolution https://wiki.biblepay.org/Getting_Started_with_Evolution
Generic Smart Contracts https://wiki.biblepay.org/Generic_Smart_Contracts
What is BiblePay Evolution? https://www.reddit.com/BiblePay/comments/bifvpk/biblepay_evolution_what_is_it/
Windows Guide: 1. Download 32 or 64 bit .exe from https://www.biblepay.org/wallet/ 2. Double Click / Run .exe file and step through Install process 3. Run BiblePay 4. Click Tools >> One Click Mining, (Or set up mining manually with steps a through d below)
     a. Open File Explorer, in address bar type: %appdata%      b. Press Enter      c. Go to BiblepayEvolution folder      d. Open biblepay.conf file for editing, add lines and Save
addnode=node.biblepay.org gen=1 genproclimit=1 
NOTE: addnode is used to give the wallet a starting node to connect to and sync with gen=1 turns on mining by default when the wallet is opened genproclimit=1 sets number of mining threads to 1 by default

5. Close BiblePay and Run it again 6. In BiblePay, go to Tools menu, Click Debug Console 7. Type these commands into the debug console:
getinfo getmininginfo help 
NOTE: getinfo will show you what block number your wallet is currently on and the version number getmininginfo will show you how many threads are running and how much mining hash you have help will show you all the other commands you can use

Threads: 8. To change number of threads to use up for mining
a. Edit %appdata%/BiblepayEvolution/biblepay.conf file: Find with File Explorer or inside the wallet go to Menu >> Tools >> Open Wallet Configuration File
genproclimit=X 
and restart BiblePay -or- b. Menu >> Tools >> Debug Console >> Type command:
setgenerate true X 
(Replace X with the number of threads you want to use Open Task Manager to view CPU usage)

Using the Pool:
NOTE: To use the pool you must now use the external miner, not the wallet miner https://whitewalr.us/2019/biblepay-nomp-pool-mining.html
  1. Set up an account on pool website: https://pool.biblepay.org/
  2. Create Worker Username(s) - Workers tab >>> Add (NOTE: Your Worker Username needs to be unique)
  3. Enable pool and add Worker Username in %appdata%/BiblepayEvolution/biblepay.conf file, add these lines:
    pool=https://pool.biblepay.org workerid=insertWorkerUsernameHere
4. Restart BiblePay
How to Withdraw Coins From Pool? The pool holds onto your coins, go to "Account" >> "Withdraw" to withdraw your coins In your BiblePay Wallet go to "File" >> "Receiving Address" and you can right click and copy the address and paste it into the Pool's Withdraw screen as the "Destination Address", then click the "Withdraw" button and the coins will be sent from the Pool to your Wallet
Setup Auto-Withdraw Navigate to Account >>> Account Settings >>> Verify your BBP Receiving Address >>> Click Authorize-Auto-Withdraws
Why use a Pool? As the network hash rises (as more miners are mining), it can take longer and longer to solve a block, by using the pool, everyone works together with all of their hash power to solve blocks, and the reward gets split between everyone who contributed based on how much they contributed in hash.
With solo mining (not using the pool) it may take 1 month to finally solve a block and get large BBP reward, with pool you can get small frequent BBP rewards every ~30 minutes. (BBP meaning BiblePay coins)

How to Update: Download exe from biblepay.org and install again, your wallet will stay intact

Backup:
Your wallet.dat stores your private keys that contain the access to your coins, this file is backed up every 24 hours in the backups folder, We also recommend that you save a copy of this file in other places, like a flash drive
Learn More about Backing Up your Wallet.dat https://www.reddit.com/BiblePay/comments/7lksp4/backup_walletdat/

FAQ
QUESTION: How long does it take for coins to mature? If you're solo mining, the coins become mature after ~100 blocks. If you're using the pool, they become mature after 24 hours
QUESTION: How do I know if I am currently mining? In your wallet >> In Top left Menu select "Tools" >> Click "Debug Console" Type in the command: getgenerate If it returns true, mining is turned on command: getmininginfo Will show how much "hashps" (hashing) your pc is doing, "genproclimit" will show how many mining threads you are using "poolmining" will be show value of true if you are successfully mining on the pool

How to Buy or Sell BBP coins?
You can buy and sell BBP coins for Bitcoin on the Exchanges we are listed on: SouthXChange: https://www.southxchange.com/Market/Book/BBP/BTC CoinExchange.io: https://www.coinexchange.io/market/BBP/BTC

Misc: Building headless Bitcoin and Bitcoin-qt on Windows https://bitcointalk.org/index.php?topic=149479.0 https://msdn.microsoft.com/en-us/commandline/wsl/install_guide https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux https://bitcointalk.org/index.php?topic=2388064.msg27133702#msg27133702 https://github.com/OleEichhorn/bitcoin-msvc

OUTDATED
Windows Mining Video Tutorial by copper101great https://www.youtube.com/watch?v=K1yKx8KsH60
submitted by togoshige to BiblePay [link] [comments]

How to Mine BiblePay on Linux

This guide is outdated, please refer to:
https://wiki.biblepay.org/POBH_Setup
https://wiki.biblepay.org/PODC_Setup
 
 
 
 
 
 
 
 
IMPORTANT - Evolution Upgrade:
Quick Start https://wiki.biblepay.org/Quick_Start
Evolution Upgrade Information https://wiki.biblepay.org/Evolution_Upgrade
Getting Started with Evolution https://wiki.biblepay.org/Getting_Started_with_Evolution
Generic Smart Contracts https://wiki.biblepay.org/Generic_Smart_Contracts
What is BiblePay Evolution? https://www.reddit.com/BiblePay/comments/bifvpk/biblepay_evolution_what_is_it/
Recommend 2GB RAM or can get stuck compiling (if 1GB RAM can use Swap File) Use Ubuntu 16.04
INFO
https://github.com/biblepay/biblepay-evolution/blob/masteBuildBiblePay.txt
INSTALL COMMANDS
apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler apt-get install git apt-get install curl build-essential libtool autotools-dev automake pkg-config python3 bsdmainutils cmake sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev git clone http://github.com/biblepay/biblepay-evolution prefix=x86_64-pc-linux-gnu cd biblepay-evolution/depends make -j4 # Choose a good -j value, depending on the number of CPU cores available cd .. ./autogen.sh #Note: if echo `pwd` does not return your working directory, replace it with your working directory such as /biblepay-evolution/ ./configure --prefix `pwd`/depends/x86_64-pc-linux-gnu make # See more here: #https://github.com/biblepay/biblepay-evolution/blob/mastedoc/build-unix.md 

SWAP FILE
NOTE: if server is 1GB RAM, before running last command "sudo make", set up a swap file
free #check if swap is 0 dd if=/dev/zero of=/vaswap.img bs=1024k count=1000 mkswap /vaswap.img swapon /vaswap.img free #check if swap is 1024 sudo make 

RUN COMMAND LINE
cd src ./biblepayd -daemon 
OR
RUN GUI
Your GUI program will be located in: /biblepay-evolution/src/qt
./biblepay-qt 
You can also run it in the background (to free up your terminal) if you call it with:
./biblepay-qt & 
To start mining, instructions are the same as for Windows: Go to Tools -> Debug Console
Execute this command (to start mining with 8 threads)
setgenerate true 8 
From there you can use all other commands such as getmininginfo, getwalletinfo, etc. Execute help command to get the list of all available commands.
Note: GUI will be built automatically only if you meet the requirements for qt library, i.e. make sure you ran this line before compiling:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler 
BIBLEPAY is now Running!

SETUP CONFIG
Stop BiblePay and set up the config file to get starting nodes to sync with and enable mining:
./biblepay-cli stop cd ~/.biblepayevolution/ vi biblepay.conf addnode=node.biblepay.org gen=1 genproclimit=1 
Escape Key + : (Colon Key) + w + q + Enter (saves file and quits)

addnode --- adds a node to the list of nodes to connect to gen=1 --- turns on mining genproclimit --- sets number of threads to use when mining

Run BiblePay again and fully sync with network
cd ../biblepay-evolution/src ./biblepayd -daemon ./biblepay-cli getinfo 

USEFUL COMMANDS
./biblepay-cli help ./biblepay-cli getaccountaddress "" ./biblepay-cli getinfo ./biblepay-cli getmininginfo ./biblepay-cli setgenerate true 8 ./biblepay-cli sendtoaddress "insertAddressHere" 777 "" "" true ./biblepay-cli stop ./biblepayd -daemon top #CPU usage q to quit 

MINING THREADS: To change number of threads to use up for mining
a. Edit home/yourusername/.biblepayevolution/biblepay.conf file:
genproclimit=X 
and restart BiblePay -or- b. Menu >> Tools >> Debug Console >> Type command:
setgenerate true X 
(Replace X with number of threads Use top command to view CPU usage)

POOL
NOTE: To use the pool you must now use the external miner, not the wallet miner https://whitewalr.us/2019/biblepay-nomp-pool-mining.html
  1. Set up an account on pool website: https://pool.biblepay.org/
  2. Create Worker Username(s) - Workers tab >>> Add
  3. Enable pool and add Worker Username in ~/.biblepayevolution/biblepay.conf file, add these lines and save:
    pool=https://pool.biblepay.org workerid=insertWorkerUsernameHere
4. Restart BiblePay
./biblepay-cli stop ./biblepayd -daemon 
Setup Auto-Withdraw Navigate to Account >>> Account Settings >>> Verify your BBP Receiving Address >>> Click Authorize-Auto-Withdraws

UPDATE:

### Turn off/stop BiblePay
cd /home/yourname/biblepay-evolution/src ./biblepay-cli stop 

### Pull down latest Biblepay code and build it
cd /home/yourname/biblepay-evolution git pull origin master sudo make 

### Turn BiblePay back on and check version number
cd src ./biblepayd -daemon ./biblepay-cli getinfo ./biblepay-cli setgenerate true 8 

UPDATE IN ONE COMMAND:
./biblepay-evolution/src/biblepay-cli stop ; cd && cd biblepay-evolution/ && git pull origin master && sudo make && cd src && ./biblepayd -daemon && sleep 90 && ./biblepay-cli getmininginfo 
Note: the ";" says do this after, regardless of the outcome Note: && says do this after only if previous command finished with no errors

SPEED UP COMPILE:
To speed up the compile time, add -j4 or -j8 after make. This way it compiles using 4 or 8 threads instead of just 1.
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" sudo make -j8 
Reference: http://www.linux-databook.info/?page_id=2319

RSYNC stop biblepay from your nodes compile on your fastest machine then rsync with your machines only src folder is required
rsync -avuz /root/biblepay-evolution/src/ [email protected]:/root/biblepay-evolution/src/ 
https://stackoverflow.com/questions/3299951/how-to-pass-password-for-rsync-ssh-command https://www.thegeekstuff.com/2008/11/3-steps-to-perform-ssh-login-without-password-using-ssh-keygen-ssh-copy-id/
people make cron jobs and rsync automatically

OUTDATED

Unofficial Bash Script
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b

Official Ubuntu Package
https://launchpad.net/~biblepay-official

Unofficial Ubuntu Package
https://www.reddit.com/BiblePay/comments/7rwqqs/unofficial_ubuntu_packages_available/

Unofficial Mine in One Line
https://www.reddit.com/BiblePay/comments/7ryuk1/mine_in_one_line/
NOTE: DONT RUN ON A COMPUTER WITH COINS -- THIS IS A CLEAN INSTALL SCRIPT

COMPILE WITHOUT GUI: https://bitcointalk.org/index.php?topic=2042657.msg21878317#msg21878317 https://bitcointalk.org/index.php?topic=2042657.msg21878389#msg21878389
ADVANCED:

DOCKER IMAGES (NOTE: I havent tested these, use at your own risk) https://hub.docker.com/gagaha/biblepay/ https://hub.docker.com/cryptozero/biblepay-opt/
submitted by togoshige to BiblePay [link] [comments]

Groestlcoin Release September 2018

Introduction

As always, the past 3 months since 22nd June have been crazy busy. The bears might still be around, but the show must go on and of course has not slowed the Groestlcoin development team in the slightest. Here’s a quick overview of what has already happened since the last release: - Integrated into the bitbns exchange, with the ability to buy Groestlcoin directly with the Indian Rupee. - Groestlcoin Rebrand Vote – Whilst there was much talk and push for a rebrand vote, the overall result was almost unanimously in favour of keeping our unique and conversation-starting name. With just 83 votes to Rebrand, and 2577 votes to No Rebrand. Thank you for all who voted, the funds raised are being used to fund ongoing hosting and development costs. - Integrated into the Cryptobridge exchange. Cryptobridge is a popular decentralised exchange where you always hold the private keys to your funds, only YOU have access to them. - Groestlcoin has been added to SimpleSwap – Groestlcoin can now be swapped with over 100 other cryptocurrencies, without signing up! - Groestlcoin has been added to UnoDax, one of the leading cryptocurrency exchanges in India, with TUSD, BTC and INR trading pairs. - Groestlcoin has been added to SwapLab.cc, where you can buy Groestlcoin using Bitcoin and over 50 other altcoins. Purchasing with VISA/Mastercard is coming VERY SOON. Discussed later: - Groestlcoin has been listed on #3 largest exchange in the world on volume, Huobi Global! More on this to come further on in the announcements. - Groestlcoin has been added to the Guarda Multi-Currency Wallet. - Groestlcoin has been added to Melis Multi-Device, Multi-Account, Multi-Platform, Multi-Signature advanced wallet! Already this list is far more than most other cryptocurrencies have achieved in the past 3 months. But this is just the tip of the iceberg of what has been developed.

What's been Happening?

GRSPay Released

We are so excited for this, that it has it's own separate reddit thread. Head over there now at https://www.reddit.com/groestlcoin/comments/9ikr5m/groestlcoin_releases_grspay/? to see more on this!
https://www.melis.io/assets/logo-navbar-4b6f0d372f15b2446d3fa4c68f346e4fb08ee113941186cee58fd6135f3f8b7d.svg

Melis Wallet

The the most advanced wallet for Bitcoin, Bitcoin Cash, Litecoin and now Groestlcoin.
With Melis you have the complete control of your bitcoins and private keys, you can define spending limits policies and make use of two or more factors authentication. Melis is open source, published on GitHub.

How Melis Works?

You can create as many accounts as you want. An account is a part of your wallet that can be customised to your requirements. You can choose how many co-signers are required to spend funds. The accounts are completely independent and act like separate wallets from each other but can be accessed via the same details. A core feature of Melis is the ability to set a ‘primary’ device. With this you can set an account as ‘Secure’ so it is only viewable (and accessible at all) from the Primary device. You can have a savings account hidden from the outside world whilst also having your ‘spending’ funds available on the go. With Melis you can create a multi-signature account between N people, where up to N signatures are required to sign a transaction, choosing if any of those should be mandatory.
Core Features:
https://guarda.co/assets/images/1PGo4ID.svg?1537791124643

Guarda Wallet

Safer than ever! Desktop Light Wallet - Anonymous and fast!
With Guarda Multi-currency Desktop Light Wallet you don’t need to register. Guarda has no access to your private keys or funds. You can receive, send, store, buy and exchange cryptocurrencies in complete anonymity and safety. All these features are available on Linux, Windows or MacOS. Choose the one that suits you!
More info about Guarda wallet on www.guarda.co
https://holytransaction.com/images/logo.png

Integrated into HolyTransaction

What is HolyTransaction?

HolyTransaction gives users access to the crypto world with a universal cryptocurrency wallet and instant exchange.

Features

For more information, visit Holy Transaction here.
https://www.groestlcoin.org/wp-content/uploads/2018/09/next-grs-groestlcoin.jpg

Integrated into NEXT Wallet

What is NEXT?

NEXT is a modern, next-generation stylish open-source Desktop wallet.

Features

For more information, visit NextWallet here.
https://blockchainfinancial.com/mediaserve2018/09/admin-06143647-bcf_logo_vec_256x256.png

Integrated into Blockchain Financial

What is Blockchain Financial?

Blockchain Financial is a set of web based services for individuals and companies that want to make things happen with the Cryptocurrencies Ecosystem. - For those that don't know anything about cryptocurrencies, we offer tools that will let them receive, send and operate with an assortment of coins. - For those that are already riding the wave, we offer tools that will let them do all those things that they weren't able to do.

Blockchain Financials mission

We're not here to reinvent the wheel. We're here to make it run smoother for you, and we provide some of the most useful services you'll find on the internet, made in a way that is easy to understand and use on a daily basis. In short, we're a bunch of people that claim to be Crypto Evangelists. We strongly believe in cryptocurrencies, and our main promise is to push them up so more people get involved and take all the advantages they offer.

More information from Blockchain Financial

Back in 2014, the world was taken by storm when Facebook approved the first cryptocurrencies tipping apps. The first was for Dogecoin, and the second was for multiple coins.
The project was hosted on whitepuma.net, and persisted for almost two years, built up a massive user community and gave a home to Bitcoin, Litecoin, Dogecoin and dozens of other bitcoin-based altcoins.
After very active months, the tipping hype started to fade away. Then, the developers decided to jump into the next stage: bringing not only tipping, but also mining and a widget that could be embedded on websites to allow everyone to accept payments. Sadly, the work was never completed because the project started to require an unsustainable amount of resources. Then, in a painful decision, a shutdown was announced by December 2015.
A couple of months after whitepuma.net was closed, the source code was released by its creator as Open Source on GitHub. But it wasn't maintained.
Now, some of the original members of the dev and admin teams gathered up with a handful of the WhitePuma's elite users, and decided to make something good with the best pieces of the old source code. That, with fresh new ideas and the power of the BardCanvas engine, synthesized the core of Blockchain Financial.
More info about Blockchain Financial wallet on .
For more information, visit [Blockchain Financial](www.blockchainfinancial.com)
https://www.huobi.com/image/logo.aeb4723.svg

Groestlcoin Listed on Huobi

Who are Huobi?

Huobi was founded in China and is now based in Singapore, with offices in Hong Kong, South Korea, Japan and the North America, currently sitting #3 in volume on Coinmarketcap. Huobi is a great leap forward for our growing presence in Asia and we are very excited to be listed here!
You can find the official Huobi announcement here.

Groestlcoin Core v2.16.3 - Please Update ASAP

A new major Groestlcoin Core version 2.16.3 is now available for download which includes both a Denial of Service component and a critical inflation vulnerability, so it is recommended to upgrade to it if you are running a full Groestlcoin node or a local Groestlcoin Core wallet.
v2.16.3 is now the official release version of Groestlcoin Core. This is a new major version release with a very important security updates. It is recommended to upgrade to this version as soon as possible. Please stop running versions of Groestlcoin Core affected by CVE-2018-17144 ASAP: These are 2.13.3 and 2.16.0.
As a result in this, all exchanges and services have been asked to upgrade to this version, so please be patient if wallets go in to maintenance mode on these services.

What's new in version v2.16.3?

This is a major release of Groestlcoin Core fixing a Denial of Service component and a critical inflation vulnerability (https://nvd.nist.gov/vuln/detail/CVE-2018-17144) exploitable by miners that has been discovered in Groestlcoin Core version 2.13.3 and 2.16.0. It is recommended to upgrade to 2.16.3 as soon as possible. If you only occasionally run Groestlcoin Core, then it's not necessary to run out and upgrade it right this second. However, you should upgrade it before you next run it. If you know anyone who is running an older version, tell them to upgrade it ASAP. Stored funds are not at risk, and never were at risk. At this time we believe over half of the Groestlcoin hashrate has upgraded to patched nodes. We are unaware of any attempts to exploit this vulnerability. However, it still remains critical that affected users upgrade and apply the latest patches to ensure no possibility of large reorganizations, mining of invalid blocks, or acceptance of invalid transactions occurs.

The Technicals

In Groestlcoin Core 2.13.3, an optimization was added (Bitcoin Core PR #9049) which avoided a costly check during initial pre-relay block validation that multiple inputs within a single transaction did not spend the same input twice which was added in 2012 (Bitcoin Core PR #443). While the UTXO-updating logic has sufficient knowledge to check that such a condition is not violated in 2.13.3 it only did so in a sanity check assertion and not with full error handling (it did, however, fully handle this case twice in prior to 2.1.0.6). Thus, in Groestlcoin Core 2.13.3, any attempts to double-spend a transaction output within a single transaction inside of a block will result in an assertion failure and a crash, as was originally reported. In Groestlcoin Core 2.16.0, as a part of a larger redesign to simplify unspent transaction output tracking and correct a resource exhaustion attack the assertion was changed subtly. Instead of asserting that the output being marked spent was previously unspent, it only asserts that it exists. Thus, in Groestlcoin Core 2.16.0, any attempts to double-spend a transaction output within a single transaction inside of a block where the output being spent was created in the same block, the same assertion failure will occur. However, if the output being double-spent was created in a previous block, an entry will still remain in the CCoin map with the DIRTY flag set and having been marked as spent, resulting in no such assertion. This could allow a miner to inflate the supply of Groestlcoin as they would be then able to claim the value being spent twice.
Groestlcoin would like to publicly thank Reddit user u/Awemany for finding CVE-2018-17144 and reporting it (https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2018-Septembe000064.html). You deserve gratitude and appreciation from cryptoworld, and you have ours. If you want to support him for his work, please consider donating to him on his bitcoin cash address: bitcoincash:qr5yuq3q40u7mxwqz6xvamkfj8tg45wyus7fhqzug5
http://i.imgur.com/3YhyNZK.png

Groestlcoin Electrum-GRS 3.2.2 - Ledger & Trezor Edition

What is Electrum-GRS?
Electrum-GRS is a lightweight "thin client" groestlcoin wallet Windows, MacOS and Linux based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.

Changes:

http://i.imgur.com/3YhyNZK.png

Electrum-GRS Mobile Android

What is Electrum-GRS Mobile?

Electrum-grs is a lightweight "thin client" groestlcoin wallet Android based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.

Changes

Groestlcoin EasyVanity Released

Groestlcoin EasyVanity is a Windows app is built from the ground-up in C# and makes it easier than ever before to create your very own bespoke Groestlcoin address(es), even whilst not connected to the internet! You can even generate multiple keys with the same prefix and leave it on overnight whilst your CPU or GPU collects and stores these addresses locally.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then Groestlcoin EasyVanity is the right choice for you to create a more personalized address.

Features

• Ability to continue finding keys after first one is found • Includes warning on startup if connected to the internet • Ability to output keys to a text file (And shows button to open that directory) • Ability to make your match case sensitive (Where possible) • Show and hide the private key with a simple toggle switch, and copy the private key straight to your clipboard • Show full output of commands • Includes statistics whilst the application is running • Ability to choose between Processor (CPU) and Graphics Card (GPU) • Automatically detects 32 or 64 bit systems • Features both a Light and Dark Material Design inspired Themes • EasyVanity's search is probabilistic, and the amount of time required to find a given pattern depends on how complex the pattern is, the speed of your computer, and whether you get lucky. • EasyVanity includes components to perform address searching on your CPU (vanitygen) and your OpenCL-compatible GPU (oclvanitygen). Both can be built from source, and both are included in the Windows binary package. • Prefixes are exact strings that must appear at the beginning of the address. When searching for prefixes, Easyvanity will ensure that the prefix is possible, and will provide a difficulty estimate. • The percentage displayed just shows how probable it is that a match would be found in the session so far. If it finds your address with 5% on the display, you are extremely lucky. If it finds your address with 92% on the display, you are unlucky. If you stop EasyVanity with 90% on the display, restart it, and it finds your address with 2% on the display, your first session was unlucky, but your second session was lucky. • EasyVanity uses the OpenSSL random number generator. This is the same RNG used by groestlcoin and a good number of HTTPS servers. It is regarded as well-scrutinized. Guessing the private key of an address found by EasyVanity will be no easier than guessing a private key created by groestlcoin itself. • To speed up address generation, EasyVanity uses the RNG to choose a private key, and literally increments the private key in a loop searching for a match. As long as the starting point is not disclosed, if a match is found, the private key will not be any easier to guess than if every private key tested were taken from the RNG. EasyVanity will also reload the private key from the RNG after 10,000,000 unsuccessful searches (100M for oclvanitygen), or when a match is found and multiple patterns are being searched for. • Free software - MIT. Anyone can audit the code. • Written in C# - The code is short, and easy to review.

Groestlcoin Sentinel (Android & Blackberry) – Mainnet + Testnet

What is Sentinel?

Groestlcoin Sentinel is the easiest and fastest way to track/receive/watch payments in your offline Groestlcoin Wallets. Groestlcoin Sentinel is compatible with any standard Groestlcoin address, BIP44 XPUB (Extended Public Key) BIP49 YPUB and BIP84 ZPUB
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 particular wallet.

What's New?

The P2SH paperwallet supports creating P2SH paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
Changes
Features
The BECH32 paperwallet supports creating BECH32 paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
Features
![WebWallet](https://i.imgur.com/Z2oj7bj.png)

Groestlcoin Web Wallet Update 1.4

What is Groestlcoin Web Wallet?
Groestlcoin Webwallet is an open source, multisignature, HD Wallet and more! Webwallet is a a open source browser based Groestlcoin webwallet.
Webwallet is a playground for Groestlcoin in javascript to experiment with. It supports multisig, OP_HODL, RBF and many more. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
Changes:
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

How To Use Coin Control & Stake More With 'PoS' DEAL Coins

How To Use Coin Control & Stake More With 'PoS' DEAL Coins
When you are using Proof of Stake (PoS) coins, active coin control is essential to ensuring that you maximize your PoS rewards. If you do not use coin control you may benefit less from the compounding of your rewards, and you may lose more rewards than necessary when you make a payment from your wallet.
Exactly how much difference this makes will depend on the specifications of the coin itself, and what transactions you make. It is particularly important for coins such as IdealCash, in which small and medium-sized holders must wait a long time between each time they stake and get a reward.
This presents a manual method of coin control for users of Qt wallets!
Why You Need to Use Coin Control
As I already stated, small and medium-sized IdealCash holders must wait a long time before they stake. When you do finally get to stake some coins, you do not get the interest due on your whole balance; instead, one of the payments you have received is selected and you earn the rewards due on that amount. The rest of your interest is not lost, it keeps building up and you get it later. But what this means is that if you receive a single payment for 10,000 coins, for example, you will earn more compound interest than if you receive 10 payments for 1,000 coins, even though your balance is the same. This is because in both cases you will wait the same amount of time before getting your first reward, but in the first instance you will receive all of your interest at once, whereas in the second example you will receive only 10% as much on your first stake. Because you can earn PoS rewards on your PoS rewards (compounding) that mean you will eventually end up with more money in the first example when you got a single payment than you would in the second example where you got 10 payments that added up to the same amount.
In the example above you could easily fix this without getting into any advanced techniques simply by using your wallet in the ordinary way to send yourself 10,000 coins. By doing this you would combine all of the outputs – all 10 of the 1,000 IdealCash payments – into a single output. But sometimes things can be a little more complicated. For example, let's say you receive a single payment of 10,000 coins, and leave it in your wallet to stake. After 8 weeks you still haven’t earned your first reward, but have built up a nice bit of ‘interest owed’ on these coins. You now receive those 10 payments for 1,000 each we looked at before. When you spend any coins in your wallet, you lose the unpaid rewards owed to you for staking them. So in this example, you would want to send a 10,000 IdealCash payment to yourself using these 10 new payments. But if you simply use the wallet as normal to send a payment to yourself it will probably not do this – it will use the 10,000 you got in your first deposit, destroying your earned rewards and doing nothing to consolidate the smaller payments. To do this, you need to be able to specify which outputs (which payments received) you want to use to create your transaction; that is what I am going to show you how to accomplish in this guide.
Coin control can also be useful when sending payments from your wallet. By specifying which outputs to use in order to make a payment you can ensure that you are not losing rewards unnecessarily. Please be aware, however, that when sending payments to somebody else you will probably need to send yourself change because each output is used entirely in each transaction. I will explain this properly later on in the guide, but for now just be aware that if you don’t do this you may lose some of your coins.
Manual Coin Control Using the Qt Wallet Console
Manual coin control requires you to use the console rather than the GUI. That means instead of just selecting options from menus, you have to manually type commands. These commands must be precise and use the correct grammar or they won’t work, so please read the instructions carefully and check that you have typed each command correctly before hitting enter.
To open a console window you just need to click ‘Help’ from the navigation menu of your wallet, then select ‘Debug Window’. This will open up a new window with two tabs: click ‘console’ to get to the tab that we are going to use here.
Step One: List Unspent Outputs In your console window type “listunspent” (without the quotation marks) and hit enter. This will give you a list of all the outputs of previous transactions which belong to you, or in more plain language, all of the payments that you have received.
Each one will appear between curly brackets and should look something like this:
{
"txid" : "a long list of random looking characters should be here",
"vout" : "this should be a number",
"address" : "this is the IdealCash address belonging to you that these coins where sent to",
"account" : "",
"scriptPubKey" : "another long list of random looking characters",
"amount" : "the number of coins you received",
"confirmations" : "the number of confirmations for this transaction"
}
You can use this list to select the outputs you want to use to make a payment. For example, IdealCash owners may want to select smaller and newer outputs (newer outputs will have fewer confirmations) and leave any older and larger ones.
When you have chosen which ones you want to use, make a note of the exact “amount” for each one. If you have received coins with more than one address then you will also need a list of each address that appears in one of the outputs you are going to use.
Once you have made a note of these things separately, we only need the “txid”, “vout” and “scriptPubKey” to put into the next step. You may like to copy and paste each one into a text editor and then delete every line apart from those three, to leave something like this:
{
"txid" : "a long list of random looking characters should be here",
"vout" : "this should be a number",
"scriptPubKey" : "another long list of random looking characters"
}
Notice that I have removed the comma from the end of the “scriptPubKey” line. Commas must always be included at the end of each line, apart from the last one. This is one of those annoying grammar things that you have to get right (and which I personally mess up more often than not). Don’t worry too much, if you get this kind of thing wrong you won’t lose any coins, it just won’t accept the command. Also please note that if you are not a programmer then you officially will be after you’ve done this, so feel free to be a bit proud of yourself.
Creating a Raw Transaction
The next step is to use the outputs we have selected to build the code for a complete transaction.
You should have a list of edited outputs from the last section. Put them, complete with brackets, into the command below:
createrawtransaction '[output1, output2]' '{"address you want to send coins to" : number of coins to send}' The number of coins you are sending must be exactly equal to total of all the outputs you have used minus the transaction fee (0.01). It is very important that you get this right as you could lose coins if you make a mistake here. For example, if you have one output with an amount of 1,000 and another with an amount of 2,000 then you must send 2999.99 coins (1000+2000-0.01). If you were to make a mistake and send just 2,000 coins, then you would end up paying a fee of 1,000 coins that you would never see again.
To give you an idea of what this should look you can see an example of a raw bitcoin transaction taken from this Reddit thread below:
createrawtransaction '[{"txid":"c7e5e03d2ab5458819eedec46d0ba38ca7a6525e38b493073277cf4a1550a348","vout":1,"scriptPubKey":"76a9144a06df74729aef1dce5e4641960da3a439d2460b88ac"},
{"txid":"c7e5e03d2ab5458819eedec46d0ba38ca7a6525e38b493073277cf4a1550a348","vout":0,"scriptPubKey":"76a914f88262828f5e64b454249e4c45ddb6071a2ab0a988ac"}]'
'{"Dty3qVvYyggQJnYfaXupbHRAPVhUxr1vso":0.17543376,"DwzkF4gP1xRoFKA4YvJpNFR9qvYzaWrFaE":0.17543375}'
IdealCash and most other altcoins will use the exact same format. In this example you can hopefully see that two addresses are listed to send coins to, with an amount for each one and a comma between them. If you are manually creating a transaction to send coins to somebody else then you will probably need to do this, because you will probably need to select outputs which add up to more than the amount you want to send, and then send the change to yourself. For example, you may have outputs of 10 and 15, but you want to send 20 coins – so you need to send the remaining 5 to your own address, otherwise they will be added to the transaction fee and lost.
When you have pasted this command into the console and hit enter, if you have managed to get all the grammar right, then you will get a long list of random looking characters as a response. This is your ‘raw transaction hex code’. Copy this for use in the next step.
Signing Your Transaction
You now need to sign your transaction with the private keys of all addresses used in the outputs you chose earlier. You can find your private key for any address using the following console command:
dumpprivkey
Obviously, you should replace
with the public address you want to get the private key for. If you have encrypted your wallet then you will need to unlock it before doing this.
You can now sign your raw transaction using the following command:
signrawtransaction 'your hex code generated in the last step' '[output1, output2]' '["privatekeyone", "privatekeytwoifneeded"]'
The middle section with output1 and output2 should be exactly the same as you used in the last step when you created the raw transaction.
When you hit the enter button on that command you will get a new, signed hex code. Copy and paste that into the final command:
Sending Your Transaction
The last bit is easy:
sendrawtransaction 'your signed hex code' When you hit enter on that final command your transaction will be broadcast to the network and your console will reply with a transaction id. If you have used this to send coins to yourself in order to consolidate smaller payments for staking, then your wallet GUI should now show ‘payment to yourself -0.01’.
submitted by Tyler__Z to IdealCash [link] [comments]

Inadvisably small full node config

Disclaimer: As the subject implies, this is about an inadvisable config. The following is of zero practical use, but like cross-stitch, may be appealing to the random few people interested in such things. Opinions on the futility of this exercise can be considered already noted. Any suggestions to make this more ridiculously small are very welcome. Obviously I'm not running my primary wallet off of this config. It's just for fun.
TLDR: Wow look, my full node fit on a 0.5 CPU with 0.6 GB memory and 25 GB drive... yeah for me!

Background

I used to run a full node a good ways back, but stopped when the old 3rd string laptop I was using to run it was having drive issues. Still the early interest paid dividends as the price has gone exponential. Missing the good ol' days, I wanted to run another node, but really didn't want to do it on any of my work or lab units. My company took a hard stand years ago to prevent interns from mining on spare HW, so running even a full node on my corporate gear is kinda a capitol punishment. Round about this time, I got some spam for some free VPS service for a year. The promotion were really (I mean really wimpy VPSs). Crappy VPS + bitcoind performance tuning = my kind of waste of time.

Goal

My goal (perverse though it may be), is to get bitcoin or other forks running in very small VPSs. Maybe some of the tuning parameters could be used for a docker container or some whipy SOC. The system I was targeting has 0.5 CPU, 0.6 GB of memory and 25 GB of disk.

Observations

I found some interesting things out along the way that may be of interest to people tweeking bitcoind.

dbcache limits

Since I don't have the requisite memory required to run the node, I've limited memory using the dbcache parameter. Settings range from 100 to 150 depending on what other settings I have in place.

0.15.1 mallocs

I don't know what changed in 0.15.1 but it seems much more memory hungry than previous releases. Throughout the tuning process, I continually had either bitcoind quit due to memory allocation failures (logged in debug.log), or the kernel oom_killer take maters into its own hands (logged in /valog/syslog). This looks very similar to an issue that was logged against 0.14.0 that was patched in 0.14.1. My ultimate solution was to downgrade to 0.14.2 which seems to work great.

prune compromise

My initial thoughts were to use prune=550 to use the least amount of disk space possible. I found out that even on 0.14.2 this causes memory to fill up quick. I found making the pruning less aggressive with a setting of prune=10240 seems to be a good compromise for what I need done. This could possibly be an observation error, but the results seemed very reproducable.

blocksonly avoidance

I had thought to save some memory by using blocksonly. For some reason, on 0.14.2, this causes more problems than it solves. I had a hard time finding any config where blocksonly would work. Surprisingly, maxmempool=5 does effectively the same thing for the miserly cost of 5MiB of memory.

serial consoles

Seems ridiculous, but on my VPS, if bitcoind was running full speed, I would have a hard time connecting through SSH. There were other SSH clients and connection methods that seemed to work better. By far the quickest connections when under heavy utilization was to connect directly to serial ports. I wrote a small snippet to enable extended serial console on my systemd install.

canary log

Since logging into my system gobbles up memory, I wanted this config to be as low-touch as possible once in motion. After tooling up the serial ports, I found all the system log messages where peekable without logging into my VPS through my VPS provider. I wrote a small canary script to simply chirp to the serial port every 5 minutes to confirm that bitcoind was indeed alive and kicking.

Scripts

I made a few scripts during the process as the needs arose. They are very utilitarian, and could do with some major overhauls, but they did what I needed done at the time I needed it.
Scripts:

Final config

Here is my final config, that is still syncing, but seems to be stable on 0.14.2
/usbin/nice -n 15 bitcoind \ -dbcache=115 \ -prune=10240 \ -maxmempool=5 \ -daemon /usbin/nohup $HOME/canary.sh $1 300 $USER >/dev/null 2>/dev/null & cPid=$! sudo /usbin/renice -n -5 -p $cPid echo "Canary @ $cPid" 
Memory utilization while syncing seems to be at about 400MiB. Once I'm synced, I expect to retune for dbcache=60 and maxmempool=60.
Projected full blockchain sync completion in (gulp) 30 days. CPU utilization is currently reported between 30-60% but my provider offers boost periods where they unmeeter the VMs. I've gotten it up to 110% on their dashboard, for what its worth.
I'm well beyond the word limit so I'll drop off here, but I'll eventually put the snipits in a github repo in the near future.
PS If anyone knows of some free VPS or Docker hosting services, please chime in.
EDIT: s/VSP/VPS/g - lysdexia
submitted by brianddk to BitcoinDiscussion [link] [comments]

Inadvisably small full node config

Disclaimer: As the subject implies, this is about an inadvisable config. The following is of zero practical use, but like cross-stitch, may be appealing to the random few people interested in such things. Opinions on the futility of this exercise can be considered already noted. Any suggestions to make this more ridiculously small are very welcome. Obviously I'm not running my primary wallet off of this config. It's just for fun.
TLDR: Wow look, my full node fit on a 0.5 CPU with 0.6 GB memory and 25 GB drive... yeah for me!

Background

I used to run a full node a good ways back, but stopped when the old 3rd string laptop I was using to run it was having drive issues. Still the early interest paid dividends as the price has gone exponential. Missing the good ol' days, I wanted to run another node, but really didn't want to do it on any of my work or lab units. My company took a hard stand years ago to prevent interns from mining on spare HW, so running even a full node on my corporate gear is kinda a capitol punishment. Round about this time, I got some spam for some free VPS service for a year. The promotion were really (I mean really wimpy VPSs). Crappy VPS + bitcoind performance tuning = my kind of waste of time.

Goal

My goal (perverse though it may be), is to get bitcoin or other forks running in very small VPSs. Maybe some of the tuning parameters could be used for a docker container or some whipy SOC. The system I was targeting has 0.5 CPU, 0.6 GB of memory and 25 GB of disk.

Observations

I found some interesting things out along the way that may be of interest to people tweeking bitcoind.

dbcache limits

Since I don't have the requisite memory required to run the node, I've limited memory using the dbcache parameter. Settings range from 100 to 150 depending on what other settings I have in place.

0.15.1 mallocs

I don't know what changed in 0.15.1 but it seems much more memory hungry than previous releases. Throughout the tuning process, I continually had either bitcoind quit due to memory allocation failures (logged in debug.log), or the kernel oom_killer take maters into its own hands (logged in /valog/syslog). This looks very similar to an issue that was logged against 0.14.0 that was patched in 0.14.1. My ultimate solution was to downgrade to 0.14.2 which seems to work great.

prune compromise

My initial thoughts were to use prune=550 to use the least amount of disk space possible. I found out that even on 0.14.2 this causes memory to fill up quick. I found making the pruning less aggressive with a setting of prune=10240 seems to be a good compromise for what I need done. This could possibly be an observation error, but the results seemed very reproducable.

blocksonly avoidance

I had thought to save some memory by using blocksonly. For some reason, on 0.14.2, this causes more problems than it solves. I had a hard time finding any config where blocksonly would work. Surprisingly, maxmempool=5 does effectively the same thing for the miserly cost of 5MiB of memory.

serial consoles

Seems ridiculous, but on my VPS, if bitcoind was running full speed, I would have a hard time connecting through SSH. There were other SSH clients and connection methods that seemed to work better. By far the quickest connections when under heavy utilization was to connect directly to serial ports. I wrote a small snippet to enable extended serial console on my systemd install.

canary log

Since logging into my system gobbles up memory, I wanted this config to be as low-touch as possible once in motion. After tooling up the serial ports, I found all the system log messages where peekable without logging into my VPS through my VPS provider. I wrote a small canary script to simply chirp to the serial port every 5 minutes to confirm that bitcoind was indeed alive and kicking.

Scripts

I made a few scripts during the process as the needs arose. They are very utilitarian, and could do with some major overhauls, but they did what I needed done at the time I needed it.
Scripts:

Final config

Here is my final config, that is still syncing, but seems to be stable on 0.14.2
/usbin/nice -n 15 bitcoind \ -dbcache=115 \ -prune=10240 \ -maxmempool=5 \ -daemon /usbin/nohup $HOME/canary.sh $1 300 $USER >/dev/null 2>/dev/null & cPid=$! sudo /usbin/renice -n -5 -p $cPid echo "Canary @ $cPid" 
Memory utilization while syncing seems to be at about 400MiB. Once I'm synced, I expect to retune for dbcache=60 and maxmempool=60.
Projected full blockchain sync completion in (gulp) 30 days. CPU utilization is currently reported between 30-60% but my provider offers boost periods where they unmeeter the VMs. I've gotten it up to 110% on their dashboard, for what its worth.
I'm well beyond the word limit so I'll drop off here, but I'll eventually put the snipits in a github repo in the near future.
PS If anyone knows of some free VPS or Docker hosting services, please chime in.
EDIT: s/VSP/VPS/g - lysdexia
submitted by brianddk to Bitcoin [link] [comments]

[HIRING] Help me get my bitcoin from my 2013 wallet and I'll send you 0.1 bitcoin

Hey guys, so I was into bitcoin about 3-4 years ago but then I put my wallet on a flashdrive and stored it away. Totally forgot about it until now. I downloaded Bitcoin-qt (which is called Bitcoin core now?) and replaced the wallet.dat with my old wallet.dat file.
Now it's up to date, but on the Overview tab I have 0 BTC available and 0 BTC pending, but under Recent Transactions, it shows that I received some bitcoins in 2013. I also see it under the Transactions tab with a question mark in the left cell and "Received with" under "Type" However, its status is: "Status: 0/unconfirmed, not in memory pool". What does this mean? Am I able to get my old bitcoins? If you can help me get the bitcoins from this transaction then I'll send you 0.1 BTC. Thanks!
Edit: I'm on a Mac btw! If you'd like to help, could you post here instead of sending me a PM?
Edit 2: Here's what I get when I type listtransactions in the console of the debug window:
[ { "account": "", "address": "1EQF3dDFp1txt8EYKfVu1vJH3d9BWTAGi1", "category": "receive", "amount": 14.42514751, "vout": 2, "confirmations": 0, "trusted": false, "txid": "bf180dce241d32609220db4808ab8c7920f6ff3b2deca60c2a23dcda9f4eaf95", "walletconflicts": [ ], "time": 1386416832, "timereceived": 1386416832, "bip125-replaceable": "unknown" } ] 
Edit 3: Increasing reward to 0.2 BTC
Edit 4: Here's what I get when I right click on the transaction and select "Show transaction details"
Status: 0/unconfirmed, not in memory pool Date: 12/7/13 03:47 Credit: 14.42514751 BTC Net amount: +14.42514751 BTC Transaction ID: bf180dce241d32609220db4808ab8c7920f6ff3b2deca60c2a23dcda9f4eaf95 Output index: 0 
Also increasing reward to .42514751 BTC
submitted by TameImpalement to Jobs4Bitcoins [link] [comments]

need help recovering my wallet.

So i bought some coins thru coinpal in 2011. I have the email which contains the bitcoin address that the coins were sent to, at some point in 2012 or something, i lost interest in bitcoin. reformatted and repurposed the drives, etc. but i did backup my wallet files, and after searching i found a wallet.dat file that is compatible with the old bitcoin qt client
under the recieve tab, it shows 3 addresses, one of which has no label, The second has the address contained in the email from coinbase, and the third has another address that i believe i had sent coins to at some point.
The two "labels" i can search on blockchain.info and they both have a balance. HOWEVER.. when you right click copy address, it copes an entirely different address.
this address has a zero balance. in all 3 spots.
So ive tried importing the wallet into bitcoin core, it does not show anything, so i know this is an older file created by the older bitcoin qt client.
ive run several commands in the debug console, trying to dump the private keys, but for some reason the wallet file i have does not contain the private keys for the two addresses that have coins.
I had someone trying to help me but he says the wallet is encrypted.
so i opened the debug console and tried to unlock the wallet using the passphrase i think i would have used, and it tells me that the wallet is not encrypted
which makes sense because i remember specifically not encrypting the wallet because i always forget passwords.
Whats weird is, how did these addresses get put into the label section of the recieveing tab? i know for a fact that one of them which contains 2btc i could have manually entered myself, because i do have a record of the address on my email from coinpal.
the second one tho, i have no idea where i would have found the address. They both have one transaction right around the same time, and they both have a balance. one of 2btc, one of .4 btc. the transaction dates line up to when i bought the coins.
im having data recovery done on my hard drives at this point to look for more bitcoin wallets, because im pretty sure i had more bitcoins in there as well. at least 6 or 8 more that i can remember.
So is it possible that the wallet file is corrupt? if so is it repairable?
or is it more liekely that ADDRESSES listed in the recieve tab are the actual addresses contained in the wallet file, and the labels are something else? im ripping my hair out trying to figure this out.. I have a wallet file. it has 2 addresses listed which i can verify both have a balance, but i cannot gain access.
i remember in 2011 buying some coins, and like the next day my computer crashed and got stuck in a boot loop so i had to reformat. and i remember backing up my wallet on a flash drive, and trying to restore it and the coins not showing up even after the blockchain loaded.
i have not yet finished loading the blockchain on my bitcoin qt app, so maybe that has somethign to do with it, but i find it odd that these addresses do not have the correct private keys.
any ideas?
submitted by cttigwelder to Bitcoin [link] [comments]

DNotes 2.0 Frequently Asked Questions:

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

Lore v2 QT on Raspberry Pi

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

How to Repair a Qt Wallet that won't Sync. Bitcoin Cash: Step By Step Guide To Claim Your Free BCC / BCH Console Logging C++ Qt 118 - Debugging with Qt Creator Qt Creator Kit Setup

Implies all other -debug* options-debugnet Output extra network debugging information-logtimestamps Prepend debug output with timestamp-shrinkdebugfile Shrink debug.log file on client startup (default: 1 when no -debug)-printtoconsole Send trace/debug info to console instead of debug.log file Again in bitcoin-qt console call sendrawtransaction command with your raw will need to open the debug console. Bitcoin virus is a type of malware which is capable of abusing bitcoin qt debug console victims' resources If it detects a malware, purchase its full live forex market hours monitor version to remove it. Entering the getblocktemplate or getwork RPC commands into the Bitcoin-Qt debug console will cause Bitcoin-Qt to crash. Run Bitcoin-Qt with the -server command-line option to workaround. Thanks to everybody who contributed to the 0.8.2 and 0.8.3 releases! APerson241; Andrew Poelstra; Calvin Owens; Chuck LeDuc Díaz; Colin Dean; David Griffith There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called bitcoind).They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. Private keys can be exported on all QT based wallets and it can be exported using the console tab on debug window. Here is a step by step instructions on exporting the private keys of your wallet address. Step 1: In your wallet go to Tools >> and open Debug Window. Step 2: Now in Debug window go to console tab.

[index] [24541] [13994] [24842] [10160] [9407] [11591] [30023] [31166] [30385] [750]

How to Repair a Qt Wallet that won't Sync.

How To Pay Off Your Mortgage Fast Using Velocity Banking How To Pay Off Your Mortgage In 5-7 Years - Duration: 41:34. Think Wealthy with Mike Adams 740,679 views This video shows how to create and set up a kit in Qt creator for deploying qt applications onto your beaglebone. Website: https://deeplyembedded.org/qt-lcd-... C++ Qt 118 - Debugging with Qt Creator VoidRealms. Loading... Unsubscribe from VoidRealms? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 69.5K. Loading... How to solo mining bitcoin with your Bitcoin wallet CPU mining on PC Run your wallet - Help - Debug Window - Console for start mining writte: setgenerate true -1 for controle mining: getmininginfo ... UPDATE: a few specifics have changed, see below for up-to-date commands In this video we create a local bitcoin testnet within a docker container. Then we'll connect to our testnet from Bitcoin-Qt ...

Flag Counter