Bitcoin Get Account - Getaccountaddress; Parameters:

Megacoin MΣC 1.9.9.x - Release Notes - Short Overview

Megacoin MΣC 1.9.9.x - Release Notes - Short Overview

https://preview.redd.it/3ex64pfi6k251.jpg?width=1452&format=pjpg&auto=webp&s=c029b11966e1215b4bb95be70756923830c150a6

Masternodes
Megacoin MΣC 1.9.9.x brings along a masternode system for Bitcore. The collateral for one masternode is 4,200 MΣC . This allows up to 10,000 masternodes to support the network. The masternodes receive half of all generated bitcores. It is possible to setup a masternode with the minimum version 1.9.9.x or higher. A government system is included in the new core
Datacarriersize

https://preview.redd.it/jyf7ka176k251.jpg?width=1288&format=pjpg&auto=webp&s=cd6f881532ffb0b26f02bc19ca73ecb52882748a
Megacoin MΣC 1.9.9.x increase the default datacarriersize up to 220 bytes. More infos con you find here | here no 2. | here no 3.
Command fork system
Different forks can be activated remotely in the future. This way we can ensure that all critical updates are only activated once all important network participants are ready.
Wallet changes
Megacoin MΣC 1.9.9.x introduces full support for segwit in the wallet and user interfaces. A new `-addresstype` argument has been added, which supports `legacy`, `p2sh-segwit` (default), and `bech32` addresses. It controls what kind of addresses are produced by `getnewaddress`, `getaccountaddress`, and `createmultisigaddress`. A `-changetype` argument has also been added, with the same options, and by default equal to `-addresstype`, to control which kind of change is used.
A new `address_type` parameter has been added to the `getnewaddress` and `addmultisigaddress` RPCs to specify which type of address to generate.
A `change_type` argument has been added to the `fundrawtransaction` RPC to override the `-changetype` argument for specific transactions.
All segwit addresses created through `getnewaddress` or `*multisig` RPCs explicitly get their redeemscripts added to the wallet file. This means that downgrading after creating a segwit address will work, as long as the wallet file is up to date.
All segwit keys in the wallet get an implicit redeemscript added, without it being written to the file. This means recovery of an old backup will work, as long as you use new software.
All keypool keys that are seen used in transactions explicitly get their redeemscripts added to the wallet files. This means that downgrading after recovering from a backup that includes a segwit address will work
Note that some RPCs do not yet support segwit addresses. Notably, `signmessage`/`verifymessage` doesn't support segwit addresses, nor does `importmulti` at this time. Support for segwit in those RPCs will continue to be added in future versions.
P2WPKH change outputs are now used by default if any destination in the transaction is a P2WPKH or P2WSH output. This is done to ensure the change output is as indistinguishable from the other outputs as possible in either case.
BIP173 (Bech32) Address support ("mec.." addresses)

https://preview.redd.it/kzg55cg36k251.jpg?width=1288&format=pjpg&auto=webp&s=288ac36af63f4f5040ca2d20c9d8f07b78d99a5a

Full support for native segwit addresses (BIP173 / Bech32) has now been added.
This includes the ability to send to BIP173 addresses (including non-v0 ones), and generating these addresses (including as default new addresses, see above).
A checkbox has been added to the GUI to select whether a Bech32 address or P2SH-wrapped address should be generated when using segwit addresses. When launched with `-addresstype=bech32` it is checked by default. When launched with `-addresstype=legacy` it is unchecked and disabled.
HD-wallets by default
Due to a backward-incompatible change in the wallet database, wallets created with version 0.15.2 will be rejected by previous versions. Also, version 0.15.2 will only create hierarchical deterministic (HD) wallets. Note that this only applies to new wallets; wallets made with previous versions will not be upgraded to be HD.
Replace-By-Fee by default in GUI
The send screen now uses BIP125 RBF by default, regardless of `-walletrbf`.There is a checkbox to mark the transaction as final.
The RPC default remains unchanged: to use RBF, launch with `-walletrbf=1` oruse the `replaceable` argument for individual transactions.
Wallets directory configuration (`-walletdir`)
Megacoin MΣC 1.9.9.x now has more flexibility in where the wallets directory can belocated. Previously wallet database files were stored at the top level of thebitcoin data directory. The behavior is now:
For new installations (where the data directory doesn't already exist), wallets will now be stored in a new `wallets/` subdirectory inside the data directory by default.
For existing nodes (where the data directory already exists), wallets will be stored in the data directory root by default. If a `wallets/` subdirectory already exists in the data directory root, then wallets will be stored in the `wallets/` subdirectory by default.- The location of the wallets directory can be overridden by specifying a
`-walletdir=` option where `` can be an absolute path to a directory or directory symlink.
Care should be taken when choosing the wallets directory location, as if itbecomes unavailable during operation, funds may be lost.
Support for signalling pruned nodes (BIP159)


Pruned nodes can now signal BIP159's NODE_NETWORK_LIMITED using service bits, in preparation forfull BIP159 support in later versions. This would allow pruned nodes to serve the most recent blocks. However, the current change does not yet include support for connecting to these pruned peers.
GUI changes
We have added a new Walletdesign. The option to reuse a previous address has now been removed. This was justified by the need to "resend" an invoice, but now that we have the request history, that need should be gone.- Support for searching by TXID has been added, rather than just address and label.- A "Use available balance" option has been added to the send coins dialog, to add the remaining available wallet balance to a transaction output.- A toggle for unblinding the password fields on the password dialog has been added
Security
We change the coinbase maturity via command fork from 100 to 576 blocks. Also we have pumb the default the protoversion to 70006. It is possible later to disconnect the old version via command fork.
Hashalgorythm
Megacoin MΣC 1.9.9.x supports a completely new hashalgo "Mega_MEC".
Sources
Bitcoin Core, Dash Core, FXTC Core, LTC Core, PIVX Core, Bitcoin Cash Core, Bitcore BTX Odarhom
submitted by limxdev to megacoinmec [link] [comments]

Odarhom - Release Notes - Short Overview - First Draft

Odarhom - Release Notes - Short Overview - First Draft

Odarhom
Masternodes
Odarhom brings along a masternode system for Bitcore. The collateral for one masternode is 2,100 BTX. This allows up to 10,000 masternodes to support the network. The masternodes receive half of all generated bitcores. It is possible to setup a masternode with the minimum version 0.90.8.x or higher. A government system is included in the new core and can be activated later, if necessary.
Datacarriersize

https://preview.redd.it/csrmknzl58q41.jpg?width=1267&format=pjpg&auto=webp&s=85c59b3e5753009f397505c3000e6d70892188b7
Odarhom increase the default datacarriersize up to 220 bytes. More infos con you find here | here no 2. | here no 3.
Command fork system
Different forks can be activated remotely in the future. This way we can ensure that all critical updates are only activated once all important network participants are ready.
Wallet changes
Odarhom introduces full support for segwit in the wallet and user interfaces. A new `-addresstype` argument has been added, which supports `legacy`, `p2sh-segwit` (default), and `bech32` addresses. It controls what kind of addresses are produced by `getnewaddress`, `getaccountaddress`, and `createmultisigaddress`. A `-changetype` argument has also been added, with the same options, and by default equal to `-addresstype`, to control which kind of change is used.
A new `address_type` parameter has been added to the `getnewaddress` and `addmultisigaddress` RPCs to specify which type of address to generate.
A `change_type` argument has been added to the `fundrawtransaction` RPC to override the `-changetype` argument for specific transactions.
All segwit addresses created through `getnewaddress` or `*multisig` RPCs explicitly get their redeemscripts added to the wallet file. This means that downgrading after creating a segwit address will work, as long as the wallet file is up to date.
All segwit keys in the wallet get an implicit redeemscript added, without it being written to the file. This means recovery of an old backup will work, as long as you use new software.
All keypool keys that are seen used in transactions explicitly get their redeemscripts added to the wallet files. This means that downgrading after recovering from a backup that includes a segwit address will work
Note that some RPCs do not yet support segwit addresses. Notably, `signmessage`/`verifymessage` doesn't support segwit addresses, nor does `importmulti` at this time. Support for segwit in those RPCs will continue to be added in future versions.
P2WPKH change outputs are now used by default if any destination in the transaction is a P2WPKH or P2WSH output. This is done to ensure the change output is as indistinguishable from the other outputs as possible in either case.
BIP173 (Bech32) Address support ("btx..." addresses)

https://preview.redd.it/q0c26p3fx7q41.jpg?width=1278&format=pjpg&auto=webp&s=bd2b8c5d583dca703caae940aa44e01a365f080c
Full support for native segwit addresses (BIP173 / Bech32) has now been added.
This includes the ability to send to BIP173 addresses (including non-v0 ones), and generating these addresses (including as default new addresses, see above).
A checkbox has been added to the GUI to select whether a Bech32 address or P2SH-wrapped address should be generated when using segwit addresses. When launched with `-addresstype=bech32` it is checked by default. When launched with `-addresstype=legacy` it is unchecked and disabled.
HD-wallets by default
Due to a backward-incompatible change in the wallet database, wallets created with version 0.15.2 will be rejected by previous versions. Also, version 0.15.2 will only create hierarchical deterministic (HD) wallets. Note that this only applies to new wallets; wallets made with previous versions will not be upgraded to be HD.
Replace-By-Fee by default in GUI
The send screen now uses BIP125 RBF by default, regardless of `-walletrbf`.There is a checkbox to mark the transaction as final.
The RPC default remains unchanged: to use RBF, launch with `-walletrbf=1` oruse the `replaceable` argument for individual transactions.
Wallets directory configuration (`-walletdir`)
Odarhom now has more flexibility in where the wallets directory can belocated. Previously wallet database files were stored at the top level of thebitcoin data directory. The behavior is now:
For new installations (where the data directory doesn't already exist), wallets will now be stored in a new `wallets/` subdirectory inside the data directory by default.
For existing nodes (where the data directory already exists), wallets will be stored in the data directory root by default. If a `wallets/` subdirectory already exists in the data directory root, then wallets will be stored in the `wallets/` subdirectory by default.- The location of the wallets directory can be overridden by specifying a
`-walletdir=` option where `` can be an absolute path to a directory or directory symlink.
Care should be taken when choosing the wallets directory location, as if itbecomes unavailable during operation, funds may be lost.
Support for signalling pruned nodes (BIP159)

https://preview.redd.it/fctdedmwx7q41.jpg?width=1283&format=pjpg&auto=webp&s=20dafb6385f46a072f68d49fd0e9a294341be684
Pruned nodes can now signal BIP159's NODE_NETWORK_LIMITED using service bits, in preparation forfull BIP159 support in later versions. This would allow pruned nodes to serve the most recent blocks. However, the current change does not yet include support for connecting to these pruned peers.
GUI changes
We have added a new Walletdesign. The option to reuse a previous address has now been removed. This was justified by the need to "resend" an invoice, but now that we have the request history, that need should be gone.- Support for searching by TXID has been added, rather than just address and label.- A "Use available balance" option has been added to the send coins dialog, to add the remaining available wallet balance to a transaction output.- A toggle for unblinding the password fields on the password dialog has been added
Security
We change the coinbase maturity via command fork from 100 to 576 blocks. Also we have pumb the default the protoversion to 80004. It is possible later to disconnect the old version via command fork.
Hashalgorythm
Odarhom supports already lots of Hashalgorythms so can we later with an update new Hashalgorythms for mining. A final decision will be agreed with the community. Odarhom can work with timetravel10, scrypt, nist5, lyra2z, x11, x16r.
Sources
Bitcoin Core, Dash Core, FXTC Core, LTC Core, PIVX Core, Bitcoin Cash Core
submitted by limxdev to bitcore_btx [link] [comments]

Bitcoin JSON RPC API (bitcoin-cli) in your web browser! [new launch for core 0.18.0]

Very excited to announce the all-new https://ChainQuery.com
Entirely up to date with Bitcoin Core 0.18.0 and sporting sexy new navigation, advanced search, category filtering, and a great new UI.
ChainQuery includes full documentation on all 140 Bitcoin RPCs along with the unique ability to run commands in your browser for 27 commands and growing.
Bitcoin core 0.18.0 included a significant RPC update outlined below:
New RPCs added in 0.18.0:
Updated RPC's in 0.18.0:
Deprecated RPCs in 0.18.0:
All depecated RPC's from 0.18.0 onward can be found here: https://chainquery.com/bitcoin-cli#deprecated
Check it out and let me know what you think!
submitted by CoinCadence to Bitcoin [link] [comments]

BiblePay BOINC Cruncher Setup Guide ([email protected] & World Community Grid)

This guide is outdated, please refer to the new guide:
https://wiki.biblepay.org/PODC_Setup
https://wiki.biblepay.org/PODC
NOTE: BiblePay no longer supports [email protected] (RH), Only World Community Grid (WCG)
.
.
.
.
.
.
.
.
.
.
.
.
------
OUTDATED:
BiblePay (BBP), a Charity Christian Cryptocurrency,welcomes all World Community Grid and [email protected] crunchersto start earning BiblePay coins for your volunteered CPU science contributions!
BiblePay recently removed its BOINC Team Requirement,now anyone can be rewarded BBP coins without having to Join "Team BiblePay"!
BiblePay rewards linked BOINC crunchers every 24 hours for their contributed work,To receive rewards you will have to buy and hold some BiblePay coins in your BiblePay Wallet, this is called "staking"
NOTE: This guide assumes that you already a cruncher with RAC (Recent Average Credit)on either BOINC Projects [email protected] (RH) or World Community Grid (WCG)
=== PART A - Download and Install BiblePay Wallet
https://www.biblepay.org/wallet/
=== PART B - Create [email protected] Account
Website: https://boinc.bakerlab.org/rosetta/create_account_form.phporOpen BiblePay Wallet >> Distributed Computing tab >> Enter Email address and Password >> Click "Create and Attach [email protected] Account"
=== PART C - Display Data, Show Computers
[email protected]: "Edit Preferences" >> Enable "Should [email protected] show your computers?" >> Click Update https://boinc.bakerlab.org/rosetta/prefs.php?subset=project
World Community Grid: In "My Profile" select "Display my data", Click Save https://www.worldcommunitygrid.org/ms/viewMyProfile.do
=== PART D - Get 2 BiblePay coins from Pool Faucet
A. Create Pool Account: http://pool.biblepay.org/ >> Register Account
B. On left menu click "Faucet" >> "Non-Biblepay Faucet"
  1. Enter CPID (Cross-project ID) and BiblePay Address
a. Find CPID:
  1. [email protected]: https://boinc.bakerlab.org/rosetta/home.php
  2. World Community Grid: https://www.worldcommunitygrid.org/ms/viewMyProfile.do
b. Generate BiblePay Receiving Address:
  1. Wallet >> File >> Receiving Addresses >> New >> Label: "Staking" >> Ok
  2. Right click "Staking" address >> Click Copy Address
(Command Line: ./biblepay-cli getaccountaddress "Staking")
  1. Click Send button
NOTE: These BiblePay coins will take 2 block confirmations before you can use them,so please wait about 15 minutes before continuing (average BiblePay block time is 7 minutes)
=== PART E - Associate/Link [email protected] Account to Wallet
In Wallet >> Click "Distributed Computing" tab >> Enter Rosetta Username and Password >> Click "Associate"
(Command Line Users: ./biblepay-cli exec associate rosetta_email_address rosetta_password)
NOTE: Cannot link World Community Grid account, has to be [email protected] account, go back to Part B
=== PART F - Calculate Staking and Daily Profit
At a minimum, for 10% of the rewards, you need 1 BBP for every 1 RAC stored in your wallet,
To receive 100% BiblePay Research rewards, you need 20 BBP for every 1 RAC stored in your wallet,
Daily BiblePay Reward = (Your RAC / Total BiblePay RAC) x (Daily PODC Superblock Budget)
For Example (Using numbers/pricing from Oct 20th and assuming you have 30k RAC): Your RAC = 30,000 RAC Total BiblePay RAC = 8,900,000 RAC Daily PODC Superblock Budget = 1,077,000 BBP So a cruncher fully staked with 30,000 RAC would get a daily reward of: (30,000 / 8,900,000) x (1,077,000) = 3,630 BBP = $1.81/day For 10% reward, need 1 BBP per 1 RAC so 30,000 x 1 = 30,000 BBP = $15 would make $0.18/day, earning $5/month, and earn back investment in 3 months, For 100% reward, need 20 BBP per 1 RAC so 30,000 x 20 = 600,000 BBP = $300 would make $1.81/day, earning $50/month, and earn back investment in 6 months, 
View a table of staking reward levels:
In Wallet >> "Tools" menu >> "Debug Console" >> Type command: exec totalrac
(Command Line Users: ./biblepay-cli exec totalrac)
References:- Combined BOINC Stats: https://boincstats.com/en/stats/-1/team/detail/831912762/overview- Budget and Leaderboard: https://www.biblepay-central.org/- Current Market Value: https://coinmarketcap.com/currencies/biblepay/
=== PART G - Buy BiblePay coins for Staking
  1. Buy Bitcoin (BTC)a. Find Bitcoin Exchange: https://bitcoin.org/en/exchanges#international(I recommend Coinbase: https://www.coinbase.com/ Video Tutorial: https://www.youtube.com/watch?v=_NgXWhfVVJU#t=20)b. Create Accountc. Use Credit Card or Bank Account to Buy Bitcoin
  2. Buy BiblePay (BBP)a. Create account on SouthXchange: https://www.southxchange.com/Account/Register(or any exchange that trades BBP: https://coinmarketcap.com/currencies/biblepay/#markets)b. Send Bitcoin to SouthXchange(NOTE: this may take 6 confirmations, so wait about an hour)c. Buy BiblePay (BBP) coins with Bitcoin (BTC) using market or limit orders
Reference:
=== PART H - Wrapping up and Troubleshooting
  1. Send BiblePay coins from the Exchange to your Wallet
  2. Keep Wallet running 24/7 with internet, the coins will be used for stakingand you will get rewarded BiblePay coins every 24 hours!
  3. Useful commands for Troubleshooting:
- exec getboincinfo- exec stakebalance- exec totalrac
References:
NOTE: If stuck or confused, ask for help in the Bitcointalk forums or Discord!Community members will assist you!
More References:
- https://www.biblepay.org/mining/
- https://www.reddit.com/BiblePay/comments/97cx4f/world_community_grid_wcg_mining_guide/
- https://www.biblepay.org/freebbp/#faucetshttps://www.biblepay.org/airdrop/
TODO:
submitted by togoshige to BiblePay [link] [comments]

Paper Wallet support in bitcoin-core | Dan Libby | Sep 29 2017

Dan Libby on Sep 29 2017:
Hi,
I'm writing to suggest and discuss the addition of paper wallet
functionality in bitcoin-core software, starting with a single new RPC
call: genExternalAddress [type].
-- rationale --
bitcoin-core is the most trusted and most secure bitcoin implementation.
Yet today (unless I've missed something) paper wallet generation
requires use of third party software, or even a website such as
bitaddress.org. This requires placing trust in an additional body of
code from a less-trusted and less peer-reviewed source. Ideally, one
would personally audit this code for one's self, but in practice that
rarely happens.
In the case of a website generator, the code must be audited again each
time it is downloaded. I cannot in good faith recommend to anyone to
use such third party tools for wallet generation.
I would recommend for others to trust a paper wallet that uses
address(es) generated by bitcoin-core itself.
At least for me, this requirement to audit (or implicitly trust) a
secondary body of bitcoin code places an additional hurdle or
disincentive on the use of paper wallets, or indeed private keys
generated outside of bitcoin-core for any purpose.
Unfortunately, one cannot simply use getnewaddress, getaccountaddress,
or getrawchangeaddress for this purpose, because the associated private
keys are added to the bitcoin-core wallet and cannot be removed... or in
the case of hd-wallets are deterministically derived.
As such, I'm throwing out the following half-baked proposal as a
starting point for discussion:
genexternaladdress ( "type" ) Returns a new Bitcoin address and private key for receiving payments. This key/address is intended for external usage such as paper wallets and will not be used by internal wallet nor written to disk. Arguments: 1. "type" (string, optional) one of: p2pkh, p2sh-p2wpkh default: p2sh-p2wpkh Result: { "privKey" (string) The private key in wif format. "address" (string) The address in p2pkh or p2sh-p2wpkh format. } Examples: > bitcoin-cli genexternaladdress 
This API is simple to implement and use. It provides enough
functionality for any moderately skilled developer to create their own
paper wallet creation script using any scripting language, or even for
advanced users to perform using bitcoin-cli or debug console.
If consensus here is in favor of including such an API, I will be happy
to take a crack at implementing it and submitting a pull request.
If anyone has reasons why it is a BAD IDEA to include such an RPC call
in bitcoind, I'm curious to hear it.
Also, I welcome suggestions for a better name, or maybe there could be
some improvements to the param(s), such as calling p2sh-p2wpkh "segwit"
instead.
---- further work ----
Further steps could be taken in this direction, but are not necessary
for a useful first-step. In particular:
  1. an RPC call to generate an external HD wallet seed.
  2. an RPC call to generate N key/address pairs from a given seed.
  3. GUI functionality in bitcoin-qt to facilitate easy paper wallet
generation (and printing?) for end-users, complete with nice graphics,
qr codes, etc.
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-Septembe015120.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

WIP: Blackpi - a stake device based on raspberry

Warning: This is a WiP and it's using Blackcoin Lore which is still in beta. Please be aware of that and backup your wallet.dat before you put any real values in this!
UPDATES
29.12.2017
22.06.2017
I am currently trying to set up blackoin on raspberry. Community members asked for a tutorial to compile it, so I will start with this here. Maybe in the future it would even be possible to turn it into a headless (=without screen and keyboard) image to put on an SD card and just boot up the wallet.
I used the latest Blackcoin Lore by janko33 for this process, however it should be quite the same with the "original" core wallet by rat4/johndolittle. Blackcoin Lore is not deemed as stable as it is still in beta, so it's up to you what source tree you take.
Please be also aware, that compiling on a small computer like raspi can take a while. Please also note that Lore is still in beta. The names in the archive are still "bitcoin". There is an update comming where the naming is correct and also maybe a few bugfixes.
** Tutorial: **
You first need to get raspbian. The lite image will work, it's a small version of the operating system without a graphical interface, so you will need ssh to operate it. The image is 294 MB but you will want to have a bigger card. 2GB is certainly too small, better get 16 or even 32GB - you also will need space for the blockchain!
To install it I followed this guide
https://hackernoon.com/raspberry-pi-headless-install-462ccabd75d0
Get the raspdian image file from:
https://www.raspberrypi.org/downloads/raspbian/
Also get Etcher from
https://etcher.io/
Etcher is a tool to write img files to an SD card/USB-stick.
After writing, open the card in your explorer and add a file "ssh". The file sould be empty and just be called "ssh" (not ssh.txt or something). It will tell raspi to activate ssh on boot.
Then boot up your raspi with the card and plug it into your network. Consult your router's LAN-page to find the device, it should register to your router as "raspberry" or so. Open up Putty and login to your raspi using pi as username and raspberry as password.
After login you can configure your raspi, please read the guide linked above for more details.
Note: One important thing that you should configure is your timezone! Use
sudo raspi-config 
Go to 4. Localisation Options and set the time to your timezone. If your time is way off, you would get troubles with staking, so make sure you always have the time set right!
After you got everything set up, get the build environment ready:
sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils #Installs alot and can take a while git clone -b Blackcoin-Lore https://github.com/janko33bd/bitcoin Blackcoin-Lore cd Blackcoin-Lore cd depends make -j 6 HOST=arm-linux-gnueabihf cd .. ./autogen.sh ./configure --prefix=`pwd`/depends/arm-linux-gnueabihf 
# note: ` = is a "backtick" not an apostroph. It causes the outpupt of "pwd" being inserted there
make -j 6 # -j n tells the compiler to use more cores, speeds that up a little (n = 1.5*cores installed) sudo make install 
This should compile so far. Update: Lore does not need Berkeley DB 4.8 to be installed, so just go with the DB provided by the repository works (libdb++-dev). (Thanks patcrypt)
After compile you can run the wallet with
lored 
And after it synced you have bitcoin-cli to control the wallet.
Issue: Synching blocks takes an awfully long time on raspi for some reason, even with Lore (that syncs blocks in a few hours instead of a whole day on a normal computer). If anyone knows how to speed up that process, please let us know!
This thread is a WiP. Please post all issues and errors here, I will then edit the OP to make it into a real, working tutorial.
On a note it was mentioned, that using an USB-stick here instead of a card would make sense since the cards are more prone to failure than USB-sticks. I will include setting it up on USB in a later version of this tutorial.
Some tips and tricks
Since compiling takes a longer time, it is recommented to run it in the console in a screen. Screen is a terminal tool that supports multiple windows in the same shell and, most important, detaches when your ssh connection breaks. Using screen you can simply reconnect and use screen -r to attach to your running shell again. To use screen, you need to install and then start it before you start the whole build process within a screen-shell.
sudo apt-get install screen screen #Start install/build process here #Type [ctrl-a] [d] to detach from the screen and put it in the background #After reconnect type screen -r to jump back into your running shell 
If you want to see your blocks being processed while the wallet syncs to the network, use the following command on a second shell (new Putty instance or screen window which you can open in screen with [ctrl-a] [c] (hit [ctrl-a] [n] to cycle through the windows in screen)
watch -n 5 lore-cli getinfo #This will execute the command "bitcoin-cli getinfo" every 5 seconds and thus display live update of your wallet info 
How to use that thing?
Here are a few helpful CLI commands, call them with lore-cli
help - Returns available commands help  - Returns detailed help to a  getinfo - Returns a descriptive information of your wallet, including balance getwalletinfo - Returns short information about your wallet, including balance, unconfirmed balance, immature balance, number of tx ect getaccountaddress 'raspi' - Returns an address for your wallet. If the account does not need to exist, it will be created with new address sendtoaddress   - Sends  to  sendtoaddress   substractfeefromaccount - Sends  minus tx fee to  getnewaddress  - Returns a new address for  each time you call the command.  is optional 
Further plans for this tutorial/project
Have fun!
Donations: B4nn2Y3SFC6whNGNvcQ2MvV1aQbZp3cZVF
submitted by mindphuk to blackcoin [link] [comments]

UFO Core 0.16 Released!

Bitcoin Core 0.16.0 introduces full support for segwit in the wallet and user interfaces. A new -addresstype argument has been added, which supports legacy, p2sh-segwit (default), and bech32 addresses. It controls what kind of addresses are produced by getnewaddress, getaccountaddress, and createmultisigaddress. A -changetype argument has also been added, with the same options, and by default equal to -addresstype, to control which kind of change is used.
Download at www.ufobject.com
submitted by daimyo-ufo to ufoo [link] [comments]

Finding my BCH in a Bitcoin Core wallet

I decided to dig up my BCH this morning: * created a new bitcoin core wallet and transfered my BTC there. * Downloaded electroncash wallet software and put it in a Docker sandbox * Found instructions on how to ask elecroncash to "sweep" the bitchcoin from a BTC address * Found instruction on how to get my bitcoin core wallet addresses, and private keys for them.
Here is where my confusion starts. Using getaccountaddress "" and getaddressesbyaccount "" I assumed that was the full list of addresses in my wallet.
None of these addresses had any BCH. Yet, I know I had some BTC in this wallet at the time of the fork. So im concerned at this point. I keep digging.
Back in my original bitcoin core wallet, under the transactions tab, I find the transactions that received BTC prior to Aug 1. WTF? There are recv addresses that are not listed in getaddressesbyaccount "", and (yay) they have my BCH.
Im also confused because about half of the addresses printed by getaddressesbyaccount "" fail to give me a private key via dumpprivkey. They just say: Private key for address xxx is not known (code -4)
I did find my BCH, but its all very confusing. If somebody is willing to take the time to explain the bitcoin core wallet address confusion I would appreciate it.
submitted by not420guilty to Bitcoin [link] [comments]

[GUIDE] Create your own Raspberry Pi's Peercoin wallet and Full Active Node with Peerbox!

TL;DR: This guide is about building your personal Raspberry Pi's Peercoin wallet with Peerbox (http://peerbox.me/). The main purpose is to have a secure Peercoin wallet that can be used as a 24/7 running Full Active Node, which contributes to the Peercoin's network security (c.f. CoinDesk's related article: http://www.coindesk.com/bitcoin-nodes-need/). 10 PPC are also rewarded to users running a Full Active Node with their Raspberry Pi!
This guide assumes that you already have some basic knowledges with either Linux or MacOS X (the only operating systems that will be taken into consideration in this guide).
Before we start, what you need is:
1. Locate your SD card
Open a Terminal and type in the following command (choose your corresponding operating system):
(Linux)
fdisk -l # You can also use the mount command 
(MacOS X)
diskutil list 
You should see a list of devices that are plugged to your computer as below (MacOS X):
[...] /dev/disk13 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *7.9 GB disk13 1: DOS_FAT_32 MY_USB_DRIVE 7.9 GB disk13s1 
What matters here is the /dev/deviceID string which corresponds to your plugged in SD card. In the example above with MacOS X it's "/dev/disk13". Do not pick any of the disk13s* for your device name, as they are for identifying the partitions of your device.
For Linux we will choose as an example "/dev/sdb" but you can also face /dev/sda for example. Note that for Linux you should not pick the numbered device names as they are for identifying each partition, i.e. /dev/sdb1, /dev/sdb2, etc. are the partitions of your "/dev/sdb" device.
An easy way to locate your SD card is to look for the SIZE field which should match your SD card's size (in my case I have a 8 GB SD card). You can also plug and unplug your SD card to check which /dev/deviceID string appears/disappears.
2. Download and verify the Peerbox image
If you haven't downloaded the LATEST peerbox image yet, you can download it from this address: http://www.peerbox.me/ (Peerbox 0.24.1 has been downloaded for this guide)
Check that the image is valid. If it is not, STOP NOW and download it again:
shasum -a 256 peerbox-raspi-v0.24.1.img.gz 4165e4b6895c872c9bc7b988d70fb5bb242cb236e45c96ce5accfae9c7b7eff6 peerbox-raspi-v0.24.1.img.gz 
If you have a different checksum than the one expected (c.f. Peerbox download page), STOP NOW!
Unzip the file:
gunzip -d peerbox-raspi-v0.24.1.img.gz 
Check that the file is present in your current directory:
ls -l peerbox-raspi-v0.24.1.img -rw-r----- 1 thireus staff 2002780160 Nov 26 21:07 peerbox-raspi-v0.24.1.img 
3. Copy the image on your SD card
Eject your SD card, which was in my case earlier identified as "/dev/disk13" for MacOS X and "/dev/sdb" for Linux:
(Linux)
sudo umount /dev/sdb? 
(MacOS X)
sudo diskutil unmountDisk /dev/disk13 
Copy this image file on your SD card with the command:
sudo dd bs=8m if=peerbox-raspi-v0.24.1.img of=/dev/disk13 
This last operation will take a while to complete ~10-20min, just be very very patient until it finishes. If you interrupt this process you will have to start all over again.
Once the operation is completed, just eject the disk:
(Linux)
sudo eject /dev/sdb 
(MacOS X)
sudo diskutil eject /dev/disk13 
4. Ready to be used!
Insert the SD card in your Raspberry Pi's SD card slot. Plug your home's Ethernet network cable to your Raspberry Pi and power it on.
Once your Raspberry Pi started, you have two ways of accessing it: SSH or directly.
ssh [email protected]_RASPBERRYPI_IP password: peerbox.me 
If you can't access it via SSH, try to hard reboot your Raspberry Pi. If you still can't, you can always plug a keyboard and a monitor to your Raspberry Pi to access Peerbox directly.
Login: sunny Password: peerbox.me 
/!\ FOR YOUR SECURITY /!\, once logged in change the sunny user's password with the passwd command.
Check your peerbox info using the following command:
peerbox-info -a 
Your Peerbox's wallet is at this location (make sure to save it on an external encrypted storage using SCP or via this guide):
/valib/ppcoind/wallet.dat # /!\ BY DEFAULT THIS WALLET IS NOT ENCRYPTED WITH ANY PASSPHRASE /!\ 
You can also directly interact with ppcoind:
ppcoind getinfo 
To retrieve the list of addresses for your Peerbox wallet use the following command:
ppcoind getaddressesbyaccount "" 
To generate a fresh new Peercoin address (and add it to the list) use the following command:
ppcoind getaccountaddress "" 
Well done, you know have a fully functional Peerbox! Enjoy!
5. Become a Full Active Node
If you want to contribute to the network, you need to be a Full Active Node (your home router's port# 9901 open, that will allow your Peercoin client to have more than 8 connections with the network). A Peercoin client running in Full Active Mode is a client that contributes to securing the Peercoin network.
Learn more about how to become a Full Active Node via this other Guide: http://www.reddit.com/peercoin/comments/2nh911/guide_how_to_become_a_peercoin_full_active_node/
List of useful links:
submitted by Thireus to peercoin [link] [comments]

Second address with the same label in bitcoin-qt?

I noticed that some addresses in my bitcoin-qt got duplicated. That is - in the "Receive" window, I have two lines with the same label, but different addresses.
One of such pairs was generated manually, by doing "new address" (which added one address, and the second one appeared some time later). The other was done by importprivkey.
What's interesting - when I do: "listaccounts" in debug console, I see just one entry for each label. "getaccountaddress "..."" also returns just one address from each pair.
What's going on?
submitted by depesz to Bitcoin [link] [comments]

How to get a Bitcoin Wallet Address - FREE & in under a ... EIN EXTREM, EXTREM SELTENES BITCOIN SIGNAL WURDE HEUTE ... HOW TO GET A BITCOIN WALLET - Safe and Secure Way - YouTube Coinbase - How to Find your Bitcoin wallet address - YouTube How to Get Your Coinbase Bitcoin Wallet Address - YouTube

Digital money that’s instant, private, and free from bank fees. Download our official wallet app and start using Bitcoin today. Read news, start mining, and buy BTC or BCH. Similar to a bank account, a bitcoin address is where you receive and transfer your bitcoins. Without it, there’s no way you would receive or send bitcoins. After all, your senders will need that address to accurately send you bitcoins. All bitcoin traders and investors have one. You should get one too if you want to trade or store bitcoins. A valid Bitcoin address is like a bank account number using which you store your bitcoins and check your balances. For those who are seeing their Bitcoin addresses for the first time, I would say that it won’t look like traditional bank account number but instead, it looks like a long alphanumeric string starting usually with ‘1’ or ‘3”. Welcome bitcoin get account to bitcoin coin machine Bitcoin.SE! Gratis bitcoin wallet , best cryptocurrency to buy in 2018 Bitcoin Checker Apps on Google Play Coinmama: Konto gesperrt bitcoin.de - Bitcoin.de (mit Support) - CoinForum.de Hallo Bitcoin.deIch habe ein großes Problem mit denen bei bitcoin.de vom 11.08.2017.Bitcoin zurück und zahlt dafür 10'900 Franken auf das Bankkonto von ... Get a simple introduction to Bitcoin and why it matters. Learn more. Read Our FAQs. Quickly find the answers to commonly asked questions. Learn more. Meet our company. Discover how we're working towards economic freedom. Learn more. Or start by exploring our Bitcoin products . Wallet. Store your Bitcoin securely. View. Buy. Purchase Bitcoin using your credit card. View. Games. Play Bitcoin ...

[index] [20007] [24359] [36793] [27733] [4084] [51484] [46447] [40720] [27009] [27306]

How to get a Bitcoin Wallet Address - FREE & in under a ...

Bytepay Masternode install guide You need to start by downloading the wallet from https://www.bytepay.org/ Once your wallet is installed you need to go to th... BITCOIN HEUTE: In diesem Video gehe ich über die heutigen Bitcoin News & Ich mache eine Bitcoin Preis Analyse. Die BTC News oder Analysen können eine Inspira... If you want to someone to send you money to your Bitcoin account, Give them this address. you may donate to our network via Bitcoin as well :) Bitcoin addres... SET UP YOUR COINBASE ACCOUNT: https://goo.gl/mWo1aM HOW TO EARN WITH CRYPTOCURRENCY: BEGINNER’S GUIDE https://goo.gl/nTDLgS ----- Today we’re talking about h... Setting up your wallet for MN, debug commands that we are using: getaccountaddress masternode masternode genkey masternode outputs Do save all the outputs fr...

#