Bitcoin Core version 0.20.0 released

Help needed diagnosing another Bitcoin Unlimited Cash orphaned block

We had yet another bitcoin cash orphan this morning, at 7:11:23am EST. I attached the log and the getinfo() results below. I remember that jtoomim has said he was willing to look at logs, so perhaps he or someone else can figure this one out.
In this case, it does not appear as if bandwidth restrictions had any impact. The daemon never hit the bandwidth cap at any time, before or after the block was found by Bitcoin Unlimited Cash. The block was accepted by the daemon as valid, and then our checker later determined that it wasn't present on the main chain.
Does this log contain any information that could assist in determining why the orphan rate is around 5%? I thought that it should be lower than that.
{ "version": 1050100, "protocolversion": 80003, "walletversion": 130000, "balance": 11.99153576, "blocks": 561230, "timeoffset": 0, "connections": 16, "proxy": "", "difficulty": 137513968721.5887, "testnet": false, "keypoololdest": 1542387258, "keypoolsize": 100, "unlocked_until": 0, "paytxfee": 0.00000000, "relayfee": 0.00000000, "status": "ready", "errors": "", "fork": "Bitcoin Cash" } 

2018-12-17 12:02:38 Acceptable block: ver:20c00000 time:1545048143 size: 42558 Tx:106 Sig:179 2018-12-17 12:02:38 UpdateTip: new best=000000000000000003648d35c1bee30a62c93b004d8e5b05df1d0098a8d46aff height=561204 bits=403185772 log2_work=87.75729 tx=268355142 date=2018-12-17 12:02:23 progress=0.999999 cache=0.1MiB(351txo) 2018-12-17 12:02:38 CheckAndAlertUnknownVersionbits: 36 of last 100 blocks have unexpected version. One example: 0x20400000 2018-12-17 12:02:39 CreateNewBlock(): total size 1085 txs: 0 fees: 0 sigops 100 2018-12-17 12:02:39 Acceptable block: ver:20000000 time:1545048159 size: 193 Tx:1 Sig:1 2018-12-17 12:02:39 CreateNewBlock(): total size 1085 txs: 0 fees: 0 sigops 100 2018-12-17 12:02:39 Acceptable block: ver:20000000 time:1545048159 size: 193 Tx:1 Sig:1 2018-12-17 12:05:11 Acceptable block: ver:20000000 time:1545048307 size: 1584 Tx:6 Sig:13 2018-12-17 12:05:11 UpdateTip: new best=000000000000000005ded68295e2f941b4875ba4699e8d6ff5e925bfa7b8573a height=561205 bits=403190346 log2_work=87.757293 tx=268355148 date=2018-12-17 12:05:07 progress=1.000000 cache=0.1MiB(19txo) 2018-12-17 12:05:11 CheckAndAlertUnknownVersionbits: 36 of last 100 blocks have unexpected version. One example: 0x20400000 2018-12-17 12:05:11 CreateNewBlock(): total size 1085 txs: 0 fees: 0 sigops 100 2018-12-17 12:05:11 Acceptable block: ver:20000000 time:1545048311 size: 193 Tx:1 Sig:1 2018-12-17 12:05:11 CreateNewBlock(): total size 1085 txs: 0 fees: 0 sigops 100 2018-12-17 12:05:11 Acceptable block: ver:20000000 time:1545048311 size: 193 Tx:1 Sig:1 2018-12-17 12:11:23 Acceptable block: ver:20c00000 time:1545048311 size: 261 Tx:1 Sig:1 2018-12-17 12:11:23 UpdateTip: new best=000000000000000001d2d4401618fd1c598ab126f407a30df326ccfbf99d2823 height=561206 bits=403197915 log2_work=87.757296 tx=268355149 date=2018-12-17 12:05:11 progress=0.999978 cache=0.1MiB(48txo) 2018-12-17 12:11:23 CheckAndAlertUnknownVersionbits: 36 of last 100 blocks have unexpected version. One example: 0x20800000 2018-12-17 12:11:23 CreateNewBlock(): total size 10511 txs: 24 fees: 33055 sigops 144 2018-12-17 12:11:23 Acceptable block: ver:20000000 time:1545048683 size: 9619 Tx:25 Sig:42 2018-12-17 12:11:23 CreateNewBlock(): total size 10511 txs: 24 fees: 33055 sigops 144 2018-12-17 12:11:23 Acceptable block: ver:20000000 time:1545048683 size: 9619 Tx:25 Sig:42 2018-12-17 12:11:25 Acceptable block: ver:20000000 time:1545048655 size: 2987 Tx:8 Sig:14 2018-12-17 12:14:20 Acceptable block: ver:20000000 time:1545048836 size: 14401 Tx:37 Sig:62 2018-12-17 12:14:20 UpdateTip: new best=000000000000000005ded68295e2f941b4875ba4699e8d6ff5e925bfa7b8573a height=561205 bits=403190346 log2_work=87.757293 tx=268355148 date=2018-12-17 12:05:07 progress=0.999968 cache=0.1MiB(85txo) 2018-12-17 12:14:20 CheckAndAlertUnknownVersionbits: 36 of last 100 blocks have unexpected version. One example: 0x20400000 2018-12-17 12:14:20 UpdateTip: new best=000000000000000002b6dbc218db453dcf75ddce6e8fce27924769429f647c47 height=561206 bits=403197915 log2_work=87.757296 tx=268355156 date=2018-12-17 12:10:55 progress=0.999988 cache=0.1MiB(100txo) 2018-12-17 12:14:20 CheckAndAlertUnknownVersionbits: 35 of last 100 blocks have unexpected version. One example: 0x20800000 2018-12-17 12:14:20 UpdateTip: new best=0000000000000000051ed80cfac2bfcb6736608d13dd4c122365ef5095606dee height=561207 bits=403196363 log2_work=87.7573 tx=268355193 date=2018-12-17 12:13:56 progress=0.999999 cache=0.1MiB(167txo) 2018-12-17 12:14:20 CheckAndAlertUnknownVersionbits: 35 of last 100 blocks have unexpected version. One example: 0x20800000 2018-12-17 12:14:20 CreateNewBlock(): total size 2297 txs: 3 fees: 1223 sigops 114 2018-12-17 12:14:20 Acceptable block: ver:20000000 time:1545048860 size: 1405 Tx:4 Sig:9 2018-12-17 12:14:20 CreateNewBlock(): total size 2297 txs: 3 fees: 1223 sigops 114 2018-12-17 12:14:20 Acceptable block: ver:20000000 time:1545048860 size: 1405 Tx:4 Sig:9 2018-12-17 12:18:18 Acceptable block: ver:20000000 time:1545049076 size: 8023 Tx:21 Sig:41 2018-12-17 12:18:18 UpdateTip: new best=000000000000000003c4d52a41d6c702be827a7048816fdf74e8a3272cdd12eb height=561208 bits=403198104 log2_work=87.757303 tx=268355214 date=2018-12-17 12:17:56 progress=0.999999 cache=0.1MiB(101txo) 2018-12-17 12:18:18 CheckAndAlertUnknownVersionbits: 35 of last 100 blocks have unexpected version. One example: 0x20800000 2018-12-17 12:18:18 CreateNewBlock(): total size 3755 txs: 4 fees: 104676 sigops 108 2018-12-17 12:18:18 Acceptable block: ver:20000000 time:1545049098 size: 2863 Tx:5 Sig:9 2018-12-17 12:18:18 CreateNewBlock(): total size 3755 txs: 4 fees: 104676 sigops 108 2018-12-17 12:18:18 Acceptable block: ver:20000000 time:1545049098 size: 2863 Tx:5 Sig:9 2018-12-17 12:21:50 Acceptable block: ver:20800000 time:1545049250 size: 11480 Tx:26 Sig:41 2018-12-17 12:21:50 UpdateTip: new best=0000000000000000039d58dcb3bcd2e5a8a79b5b47227a97e21d22a1028e3dd4 height=561209 bits=403193955 log2_work=87.757306 tx=268355240 date=2018-12-17 12:20:50 progress=0.999997 cache=0.1MiB(115txo) 2018-12-17 12:21:50 CheckAndAlertUnknownVersionbits: 35 of last 100 blocks have unexpected version. One example: 0x20c00000 2018-12-17 12:21:50 CreateNewBlock(): total size 2463 txs: 4 fees: 2387 sigops 109 2018-12-17 12:21:50 Acceptable block: ver:20000000 time:1545049310 size: 1571 Tx:5 Sig:10 2018-12-17 12:21:50 CreateNewBlock(): total size 2463 txs: 4 fees: 2387 sigops 109 2018-12-17 12:21:50 Acceptable block: ver:20000000 time:1545049310 size: 1571 Tx:5 Sig:10 2018-12-17 12:30:52 connect() to [2607:f2c0:ecae:3d:1262:ebff:fe48:85f3]:8333 failed: Network is unreachable (101) 2018-12-17 12:37:40 Acceptable block: ver:20000000 time:1545050227 size: 69173 Tx:76 Sig:146 2018-12-17 12:37:40 UpdateTip: new best=000000000000000002b2982882663cf01b1db0bcc2876fa55c2a41d3ef354d7b height=561210 bits=403192877 log2_work=87.757309 tx=268355316 date=2018-12-17 12:37:07 progress=0.999998 cache=0.1MiB(548txo) 2018-12-17 12:37:40 CheckAndAlertUnknownVersionbits: 34 of last 100 blocks have unexpected version. One example: 0x20c00000 2018-12-17 12:37:40 CreateNewBlock(): total size 2533 txs: 2 fees: 2316 sigops 103 2018-12-17 12:37:40 Acceptable block: ver:20000000 time:1545050260 size: 1641 Tx:3 Sig:4 2018-12-17 12:37:40 CreateNewBlock(): total size 2533 txs: 2 fees: 2316 sigops 103 2018-12-17 12:37:40 Acceptable block: ver:20000000 time:1545050260 size: 1641 Tx:3 Sig:4 2018-12-17 12:45:19 Acceptable block: ver:20000000 time:1545050688 size: 10306 Tx:14 Sig:29 2018-12-17 12:45:19 UpdateTip: new best=00000000000000000378d55568094cb4aa60155798edd1e4d046c7bfac286a42 height=561211 bits=403185479 log2_work=87.757312 tx=268355330 date=2018-12-17 12:44:48 progress=0.999998 cache=0.1MiB(131txo) 2018-12-17 12:45:19 CheckAndAlertUnknownVersionbits: 34 of last 100 blocks have unexpected version. One example: 0x20c00000 2018-12-17 12:45:19 CreateNewBlock(): total size 13214 txs: 34 fees: 20859 sigops 165 2018-12-17 12:45:19 Acceptable block: ver:20000000 time:1545050719 size: 12322 Tx:35 Sig:55 2018-12-17 12:45:19 CreateNewBlock(): total size 13214 txs: 34 fees: 20859 sigops 165 2018-12-17 12:45:19 Acceptable block: ver:20000000 time:1545050719 size: 12322 Tx:35 Sig:55 2018-12-17 12:51:16 connect() to [2a02:1812:1426:a600:84e:ea09:30b:2772]:8333 failed: Network is unreachable (101) 2018-12-17 12:51:40 connect() to [2001:8003:258d:3200:43:6475:500:8286]:8333 failed: Network is unreachable (101) 

submitted by MattAbrams to btc [link] [comments]

It looks like Bitcoin Cash might be under attack.

TL;DR: The attack is someone mining just enough blocks (12) to not be able to drop 20% difficulty, thus forcing the difficulty to remain very high indefinitely.
 
Explanation:
Per this spreadsheet, we should have started seeing the BCC difficulty start to drop at block #7, but the difficulty has not changed and there have been 12 blocks mined so far (see my section entitled "Proof" below).
A miner with a malicious client and enough processing power (~8% of BTC) can stagger blockrates even if he mines faster than 6 per 12 hours to ensure he only releases them once per 2 hours, which causes the network to not adjust difficulty for 2016 blocks (2 weeks in BTC time, SIX MONTHS in BCC time if he is the only big miner).
If he is also the majority of the network, he can double spend and essentially duplicate his own coins at will to dump the price to zero (if any exchanges are actually accepting deposits).
We'd need to bring online a significant amount of hashpower (at least equal to his) to combat the attack.
It's a 51% attack on steroids because of the difficulty from BTC being active on BCC along with exploitable retargeting rules.
This isn't just something you can idly watch and twiddle your thumbs for. - comment source
 
 
Proof:
(Keep in mind the BCC fork block number was 478559)
 
15:24:58  {
      "version": 140600,
      "protocolversion": 70015,
      "walletversion": 60000,
      "balance": 19.85858560,
      "blocks": 478562,   [this is 4 blocks after the fork block]
      "timeoffset": 1,
      "connections": 5,
      "proxy": "",
      "difficulty": 860221984436.2223,
      "testnet": false,
      "keypoololdest": 1456264638,
      "keypoolsize": 100,
      "paytxfee": 0.00000000,
      "relayfee": 0.00001000,
      "errors": ""
}
 
23:53:52  {
      "version": 140600,
      "protocolversion": 70015,
      "walletversion": 60000,
      "balance": 19.85858560,
      "blocks": 478570,   [this is 12 blocks after the fork block]
      "timeoffset": 1,
      "connections": 15,
      "proxy": "",
      "difficulty": 860221984436.2223,
      "testnet": false,
      "keypoololdest": 1456264638,
      "keypoolsize": 100,
      "paytxfee": 0.00000000,
      "relayfee": 0.00001000,
      "errors": "Warning: Unknown block versions being mined! It's possible unknown rules are in effect"
}
 
Both these blocks have the same difficulty level. It should have dropped, but we mined just enough blocks to not be able to drop 20% difficulty. Coincidence? I don't think so.
 
Now take a look here to see the recently mined BCC blocks:
https://cash.coin.dance/blocks
We all know ViaBTC is mining Bitcoin Cash, so that's fine.
But who is the miner who mined these BCC blocks where it says "Genesis Block 269-273 Hennessy Road Wan Chai Hong Kong"? I believe they are the attacker.
It isn't Bitcoin.com, the only other known pool to mine BCC right now.
 
Summary:
All a big attacker has to do is make sure that X blocks are mined every period, to deny the difficulty adjustment downward.
submitted by BitcoinIsTehFuture to btc [link] [comments]

ShionCoin Console Basics

The following is a brief overview of the commands provided by the "shc" utility console program.
The utility program "shc" communication with the server (shcoind) are restricted to the local host that the service is running. You must use the stratum API in order to access the server from a remote machine.
A sub-set of all the commands are provided here. This guide attempts to concentrate on commonly used commands that are useful. Run "shc help" for a full list of commands. Run "shc help " for details about running that particular command.
You can enter an interactive mode by running "shc --prompt".
Run the daemon with "shcoind --debug" in order to print additional information to the log file (on linux, "/valib/share/shcoind.log") for diagnostic purposes.
ShionCoin "pub-key" coin addresses typically starts with "S" or "R". A "script address" will start with "1" and a seg-wit address will start with "3". Coin addresses are verified when entered on the command-line in order to ensure that the address is prudent in respect to the coin interface.
All fees for extended transactions, such as creating context and aliases, are either stored (for update purposes) in a local extended account and/or are provided as mining fees. You can use the "wallet.donate" command to intentionally create a transaction which includes a specified mining reward value.

Wallet Commands

The wallet commands provides capabilities to transfer funds and manage accounts. Each account can contain several coin addresses and has a counter-part "extended account" that is not visible.
Wallet Info: wallet.info
Display statistical and runtime information on wallet operations.
shc wallet.info { "version": 3010000, "walletversion": 60000, "balance": 658, "keypoololdest": 1517000561, "keypoolsize": 101 }
Create Coin Address: wallet.new
The "wallet.new" command is used to create a normal (non seg-wit) coin address and associate it with an account name. Coin addresses may be automatically generated for accounts, for example in order to return "change" in a fund transfer transaction. All change is directly returned to the associated account.
shc wallet.new test S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci
List Accounts: wallet.list
The "wallet.list" command provides a balance of all accounts in the coin wallet.
shc wallet.list { "": 0, "bank": 658, "system": 0 }
Three accounts are created by default. The "" account receives coinbase rewards which are then distributed to users based on their stratum stats. The "bank" account is a 0.1% cut of the rewards received from the stratum mining pool. The "system" account is currently reserved for a cpu-miner which attempts a single mining operation each time new task work is assigned to miners. The frequency of how often this occurs is based on tracking the "luck" of past attempts.
List Coin Addresses: wallet.listaddr
The "wallet.listaddr" command will list all of the coin addresses associated with an account.
shc wallet.listaddr test ["S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci"]
Create Transaction: wallet.send
The "wallet.send" command is the primary method of sending funds.
All ShionCoin transactions are sent with at least the 0.0001 SHC minimum fee. Providing the minimum fee is provided, any fee can is permitted and affects the priority of the transaction.
shc wallet.send bank S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci 10 307711dace8c0583b744af8acd1df2073e36b0c7a54b8830a15ae146f8c22ddb
Test Create Transaction: wallet.tsend
You can "test send" a transaction in order to determine the aproximate fee and size that would result.
shc wallet.tsend bank SLbnKamvSx8FhaBNpHUwffFDLZ16J8phdX 10 { "amount": 10, "tx-amount": 98.999900, "size": 300, "virt-size": 226, "fee": 0.000100, "inputs": 1, "priority": 1085539000000 }
Create Batch Transaction(s): wallet.bsend
The "wallet.bsend" command allows you to transfer funds that are more complicated than would be permitted in a single transaction. Multiple transactions will be created, as neccessary, in order to send the specified coin value. The total value commited to be sent may be lower than the value requested under certain circumstances.
Create Certified Transaction: wallet.csend
The "wallet.csend" associated a pre-created certificate with the coin transfer. The certificate may be used to associate with the certificate, or provide a method to identity the source of the funds.
shc wallet.csend bank SLbnKamvSx8FhaBNpHUwffFDLZ16J8phdX 10
Create Stamp Transaction: wallet.stamp
The "wallet.stamp" command allows you to create a short message (up to 135 characters), or reference a geodetic location, to associate with a local coin address. The stamp transaction is the exclusive method of claiming spring matix location coins. Creating a stamp in the format "geo:," will result in a single SHC coin, once processed on the network, being rewarded for all locations not yet discovered in the spring matrix. A minimum transaction fee (0.0001) is applied for each stamp transaction created.
Use the "ctx.findloc" command in order to search for locations active in the sprint matrix.
Validate Address: wallet.donate
Donated coins are added to the upcoming block reward. Donations may be optionally associated with a certificate. The maximum donation value in a single transaction is 500 coins. Donations are associated with the coin address that generates them, and may contain a geodetic stamp depending on configuration and availability.
The total cost will include the donation coin value specified plus a minimum transaction fee (0.0001 SHC).
{ "version": 1, "flag": 1025, "txid": "ace04609d0eca593b73a3f1afb1dcfeb10049c4ab4098ff9b17e01da65bf2ec6", .. "ident": { "version": 3, "expire": " ", "geo": "46.770000,113.980000", "addr": "SFrXpo9ykcSeycTdMaFu3xWwJFxN5gkUH4" } }
Validate Address: wallet.validate
The "wallet.validate" command returns general information about the coin address specified, including whether the coin address is contained in the local wallet.
shc wallet.validate SLbnKamvSx8FhaBNpHUwffFDLZ16J8phdX { "isvalid": true, "address": "SLbnKamvSx8FhaBNpHUwffFDLZ16J8phdX", "ismine": true, "account": "system" }
Validate Address: wallet.key
Obtain a code that identifies the private key of a coin address.
Validate Address: wallet.setkey
Create a new coin address, for the specified account, with a private key code.
Validate Address: wallet.keyphrase
Obtain a set of phrases that identify the private key associated with a coin address.
Validate Address: wallet.setkeyphrase
Create a coin address in the wallet given a key phrase.
Export Wallet (json): wallet.export
Creates a JSON formatted backup of all the accounts managed.
Export Wallet (datafile): wallet.exportdat
Creates a binary backup, in the tradition bitcoin wallet format, of all the accounts in the wallet.
Import Wallet (json): wallet.import
Creates a JSON formatted backup of all the accounts managed.
Scan Wallet: wallet.rescan
Cycle through all known wallet transactions and verify their state in the block-chain.

Block Commands

BlockChain Info: block.info
Print summarized information about the block-chain.
shc block.info { "version": 2000000, "blockversion": 2, "walletversion": 60000, "blocks": 77029, "difficulty": 0.000488, "pooledtx": 0, "currentblockhash": "5c4e3a637d857c7df925dda1c017dd3864c0fb95c1421276619810f5b95fc8c5", "errors": "" }
Print Block (hash): block.get
Print detailed information about the specified block hash.
shc block.get bc157eefd48e18152c70ad2937bd44e6bb38d218bf13c262a844a3d0ae9264d6 { "blockhash": "bc157eefd48e18152c70ad2937bd44e6bb38d218bf13c262a844a3d0ae9264d6", "version": 536870912, "merkleroot": "5bda555d945bc36806f1eb4913a47a2ecad4569133cce1d59bd82ad94e7be1c6", "time": 1521898215, "stamp": "03/24/18 07:30:15", "nonce": 4422421, "bits": "1e07ffff", "previousblockhash": "3312abddb29aea55f44a0e3c52d397d3041b9e2deaa160f2ac415cdca05057b9", .. }
Print Block Hash (height): block.hash
Obtain the block hash for a specified block height.
shc block.hash 77022 bc157eefd48e18152c70ad2937bd44e6bb38d218bf13c262a844a3d0ae9264d6
Export BlockChain: block.export
Export an entire block-chain to a binary file. The actual export of data is performed asynchronously (in the background), and the log file should be reviewed to determine when the operation is actually done.
shc block.export /root/.shc/block.bin { "mode": "export-block", "minheight": 0, "maxheight": 0, "path": "/root/.shc/block.bin", "state": "init" }
tail /valog/share/shcoind.log ..
[03/24/18 07:47:14] info: shc: PerformBlockChainOperation: saved 77105 blocks to path "/root/.shc/block.bin".
Import BlockChain: block.import
Import a previously exported block-chain into the live system. The imported file will only over-write block records that do not previously exist.
BlockChain Scan: block.verify
Perform an integrity check against the last X blocks in the block-chain.

Transaction Commands

Print Transaction: tx.get
Print details for a particular transaction from it's transaction hash.
shc tx.get 307711dace8c0583b744af8acd1df2073e36b0c7a54b8830a15ae146f8c22ddb { "version": 1, "flag": 1, "txid": "307711dace8c0583b744af8acd1df2073e36b0c7a54b8830a15ae146f8c22ddb", .. }
Print Transaction: tx.pool
Print details for all transaction currently pending in the active "mempool" queue. These are transactions that are actively being inserted into mined blocks.
Print Transaction: tx.validate
Validate a transaction hash associated with the local wallet. Prints summarized information about all local coin addresses associated with the transaction.
shc tx.validate 307711dace8c0583b744af8acd1df2073e36b0c7a54b8830a15ae146f8c22ddb [{ "spent": "false", "ismine": "true", "address": "S7viXBKwUZKy4aPCby3oXzWFDxhZKjGipA" }, { "spent": "false", "ismine": "true", "address": "S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci" }]

Peer Commands

Import Peers: peer.info
Display a summary of information relating to connected peers.
{ "clientversion": 3010000, "protocolversion": 2000000, "socketport": 24104, "connections": 3, "networkhashps": 11609, "errors": "" }
Import Peers: peer.list
Display information about each node peer currently connected to the coin interface.
Export Peers: peer.export
Export all of the known peers to a JSON file.
shc peer.export /root/.shc/peer.json { "mode": "peer.export", "path": "/root/.shc/peer.json", "state": "finished" }
Import Peers: peer.add
Import a JSON file containing node peer information.
Remove Peer: peer.remove
Disconnect and remove the specified peer from the system.

Context Commands

Context Info: ctx.info
Print the current fee to create a context transaction and the total number of context records in the system.
{ "fee": 25, "total": 1 }
Print String Context: ctx.getstr
Prints the ASCII value associated with a particular context name.
shc ctx.getstr "test name" test value
Print Context: ctx.get
Prints detailed information about a context record given it's context hash.
shc ctx.get ab5b128ce3674f81f0271efbbbb191fed56e9a80 { "version": 3, "label": "ab5b128ce3674f81f0271efbbbb191fed56e9a80 test name (1zgfTHd5BQA)", "expire": "Mar 23 08:28:39 2020", "flags": 10244, "signature": "e0539d3ecb54c5c0a29ccd69f0b03dfdfb58bc24", "hash": "ab5b128ce3674f81f0271efbbbb191fed56e9a80", "valuesize": 10, "valuecrc": "1zgfTHd5BQA", "tx": "0dbf21191091e33ad7be3b1ce1983ffffdbedeb804e3ce934021f0fad038d50e" }
Create String Context: ctx.findloc
Search for a location by it's name or with geodetic cordinates.
The "ctx.findloc" will scan an area and attempt to find a location within it. This area includes a span of about 100 sq. miles. The closest location with the smallest precision found will be returned. In addition, geodetic information provided by the share library is also utilized.
shc ctx.findloc "geo:46.9,114.2" { "name": "missoula, mt", "summary": "Montana", "zone": "America/Denver", "code": "MUNI", "country": "US", "geo": "46.94000,114.04000", "type": "Municipal Zone", "springable": "false" } shc ctx.findloc "Missoula, MT" { "name": "missoula, mt", "summary": "Montana", "zone": "America/Denver", "code": "MUNI", "country": "US", "geo": "46.94000,114.04000", "type": "Municipal Zone", "springable": "false" }
Note: The "springable" value denotes whether the geodetic location can be claimed in the SHC spring matrix (see "wallet.stamp").
Create String Context: ctx.getloc
Print detailed information about a particular location by it's name or geodetic cordinates.
The "ctx.getloc" command requires specific cordinates to be specified when a latitude and longitude is specified.
ctx.getloc "Missoula Creek" ctx.getloc geo:46.9846,114.1213
Note: The "springable" value denotes whether the geodetic location can be claimed in the SHC spring matrix (see "wallet.stamp").
Create String Context: ctx.setstr
Create a text format context value. This establishes a simple name=value relationship.
Context names are stored as hash keys. Therefore, the string name of the context key must be known before-hand in order to perform the lookup. A small label is also provided as part of the context record which includes a snippet (or all of) the context name.
Context records are signed against the coin address that paid to generate the transaction. Context transaction typically cost about 25 SHC or less to create. A context will expire two years after the date at which it is either created or updated. The owner can update a context by creating a new one with the same name as a pre-existing one. The "context hash" that identifies a context is also the key hash of it's label. The context is shown as part of the transaction details.
shc ctx.setstr test "test name" "test value" { "version": 3, "label": "ab5b128ce3674f81f0271efbbbb191fed56e9a80 test name (1zgfTHd5BQA)", "expire": "Mar 23 08:28:39 2020", "flags": 10244, "signature": "e0539d3ecb54c5c0a29ccd69f0b03dfdfb58bc24", "hash": "ab5b128ce3674f81f0271efbbbb191fed56e9a80", "valuesize": 10, "valuecrc": "1zgfTHd5BQA", "tx": "0dbf21191091e33ad7be3b1ce1983ffffdbedeb804e3ce934021f0fad038d50e" }
Create Geodetic Context: ctx.setloc
The "ctx.setloc" command creates contextual information about a specific place.
The command includes information about a location zipcode, name, and description. In addition, an optional place type code, country code, and web-url can be specified.
The place type corrosponds to one of the codes returned from the "ctx.loctypes" command.
This command has two different modes. One corrosponds to giving a name to a particular geodetic latitude and longitude corindate, and the other includes providing details about that particular location. A single location (as specified by latitude and longitude) may have multiple names, but it limited to a single set of details. Although some common places may be reserved from use (such as common city names), the application of detailed information to a geodetic location comes on a first-come-first-serve basis. Note that context information expires after two years.
The size of the area being referenced is dependent on the place type specified. For example, "AREA" spans roughly 30 sq. miles, while "SPOT" only spans 8 sq. feet. This precision is used in relation to geodetic lookups performed.
shc ctx.setloc test geo:46.9846,114.1213 "Bitterroot Creek" STM US shc ctx.setloc test "Missoula Creek" geo:46.9846,114.1213
Create Identity Context: ctx.setid
Create a binary context from the raw command-line argument specified.
Create Binary Context (raw): ctx.setbin
Create a binary context from the raw command-line argument specified.
Create Binary Context (file): ctx.setfile
Create a binary context from the absolute path specified.
Print Location Types: ctx.loctypes
Print out all suported location type codes for use with the "ctx.setloc" command.
[{ "name": "AREA", "desc": "General Area", "prec": 1 }, { "name": "MT", "desc": "Mountain", "prec": 1 }, .. }

Address Alias Commands

Alias Info: alias.info
Print the current fee to create an alias transaction and the total number of alias records in the system.
shc alias.info { "fee": 31.250000, "total": 1 }
Create Address Alias: alias.pubaddr
Create a persistent public association with a name and a coin address. Once confirmed, the coin address can be referenced as "@" in command-line operations.
When a coin address is specified the alias label will be published onto the block chain in reference. If the alias label already exists, then a transfer will occur providing you are the original owner.
A coin address will be automatically created if none is specified. Only "pub-key" coin addresses are currently supported. An alias will expire after 12 years.
An alias cost around 30 SHC to create and will decrease over time.
shc alias.pubaddr test S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci { .. "alias": { "version": 1, "label": "test", "expire": "Mar 21 09:37:40 2030", "type": 30, "addr": "S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci", "type-name": "pubkey" } }
shc wallet.send bank @test 2 d438fea502b7113f155617fc1b400161bb3045645094df5423ce7e484fadf7f2
List Address Alias: alias.list
Print all aliases that match the keyword provided.
shc alias.list { "test": { "block": "79b04f63fe5602f40bc559b1c5b39b730a2d6ea2d6b4ab491904d6054b1add71", "tx": "abb12ed2f4a74c58432afa9e19c08afad1d3dd84052f23be534e96ed53e11d4f", "alias": "77135966b271a06928cdff5548dbbaed61ee7250", "addr": "S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci" } }
Print Address Alias: alias.getaddr
Print details about a particular coin address alias given it's name.
shc alias.getaddr test { "version": 1, "label": "test", "expire": "Mar 21 09:37:40 2030", "type": 30, "addr": "S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci", "type-name": "pubkey" }

Certificate Commands

Certificate Info: cert.info
Prints the current certificate transaction fee and the total number of certificates created on the block-chain.
shc cert.info { "fee": 14.750000, "total": 1 }
Certificate Info: cert.list
Search for a certificate given the provided keyword.
shc cert.list test { "test certificate": "8069f1bbfb435cfa1efdb454684446528343b809" }
Certificate Info: cert.new
The "cert.new" command is used to create a new certificate on the block-chain. The certificate than may be used to derive other certificates or dispense licences. The certificate may have an optional fee specified that will be required to derive or license it.
A certificate can either be designated for issueing other certificates or granting licenses, but not both. Either form of the certificate may be used in order to donate or send a certified coin transfer.
A certificate is signed against a private key that is generated from the associated extended account coin address. You may optionally specify a hexadecimal seed to use for generating the private key. The certificate's private key is not stored in a database or a transaction, and requires the original coin address to be present in the local wallet to be determined. The public key is provided as part of the certificate transaction, and can be used in order to verify the integrity of the associated signature.
The average fee for registering a new certificate is initially about 15 SHC and will decrease over time. The details of the certificate are visible in the underlying transaction that it was generated in.
The frame-work of the certificate is designed to be compatible with the x509 format. See the "shcert" share library utility program for more information on exporting x509 certificate created on the ShionCoin block-chain. Certificates may also be used to provide licensing authentication to run or provide features to programs using the share library "esig" functionality (see the "shesig_verify()" function).
Note that the certificate may contain identifying information such as the originating coin address and, when available, the geodetic location.
shc cert.new test "test certificate" { "version": 1, "flag": 17, "txid": "18d0a73c96af3dd211f27e4ada898e13b4cf25223da2591289edb8a1e86f1129", .. "certificate": { "version": 3, "label": "test certificate", "expire": "Mar 24 04:13:46 2066", "geo": "46.770000,113.980000", "addr": "SC2j6kxbrKzfpxsGqBQSrxeDh2CdPn1TLJ", "certhash": "8069f1bbfb435cfa1efdb454684446528343b809", "issuer": "0000000000000000000000000000000000000000", "serialno": "0c96a132d74df2522f38babf0733224c", "flags": 10244, "signature": "0d5a4e6c7d4975ee443cfc2e057d3d76070bd2f5", "sigpubkey": "0334d9f89253fa0837a1524266414509bdce478368" } }
Certificate Info: cert.get
Print the details of a certificate record given the certificate hash.
{ "version": 3, "label": "test certificate", "expire": "Mar 24 04:13:46 2066", "geo": "46.770000,113.980000", "addr": "SC2j6kxbrKzfpxsGqBQSrxeDh2CdPn1TLJ", "certhash": "8069f1bbfb435cfa1efdb454684446528343b809", "issuer": "0000000000000000000000000000000000000000", "serialno": "0c96a132d74df2522f38babf0733224c", "flags": 10244, "signature": "0d5a4e6c7d4975ee443cfc2e057d3d76070bd2f5", "sigpubkey": "0334d9f89253fa0837a1524266414509bdce478368", "txid": "18d0a73c96af3dd211f27e4ada898e13b4cf25223da2591289edb8a1e86f1129" }
Certificate Info: cert.derive
Derive a certificate from another certificate. You can optionally specify a fee to be associated with the new certificate, and a fee may be required if one is associated with the parent certificate.
Certificate Info: cert.license
Generate a license from a certificate. A license represents authorization to use a particular product and typically requires a fee to be paid. You can optionally specify a hexadecimal seed to be used when creating the certificate's private key.
Certificate Info: cert.export
Exports the private key information from the extended account that is used to claim ownership over a particular certificate.
Ownership and management of a certificate depends on having specific coin address key(s) in the coin wallet. Exporting a certificate provides JSON formatted content which can be used with "wallet.import" command to attain ownership of a certificate.
submitted by shioncoin to u/shioncoin [link] [comments]

Need help trying to figure out why block contains few transactions

I'm trying to troubleshoot bitcoin block 0000000000000000001aaef7bdca12abf93c862b5df4db96ca6130b6445655c1. The Prohashing pool found this block this morning, but it only has 9 transactions. The blocks around it appear to have many more transactions than this one does, some as many as 1300. Yet, getblocktemplate returned just a few transactions. This is the third block where there were about the same number of transactions.
Since all the other coins mined by the pool contain a lot of transactions, it's unlikely that this problem is a bug in the mining server that limits blocks to 9 transactions. For example, litecoin block 9d24ac1c74689309c08f4d2bd4eb47210c8f44f4c788472fd003bf7d8d4ad562 contains 19 transactions. Bitcoin Cash block 000000000000000000c966e7c0f566df540efc2b30604188a7cf511cb8e41730 also contains more than 9 transactions. That's why I think the problem is a configuration error.
Here's the bitcoin.conf file, in case that helps.
server=1 daemon=1 port=4516 rpcuser=daemon rpcpassword=[censored] rpcport=3210 rpctimeout=30 blocknotify=/usshare/blocknotify_new.sh --user=daemon --pass=[censored] #maxconnections=8 txconfirmtarget=6 minrelaytxfee=0.00005 addnode=v4.us-east.fibre.bitcoinrelaynetwork.org 
and here's what getinfo() returns:
{ "version": 1000300, "protocolversion": 80002, "walletversion": 60000, "balance": 15.98119571, "blocks": 534848, "timeoffset": 0, "connections": 27, "proxy": "", "difficulty": 5949437371609.53, "testnet": false, "keypoololdest": 1529134290, "keypoolsize": 100, "unlocked_until": 0, "paytxfee": 0.00000000, "relayfee": 0.00002423, "errors": "Warning: unknown new rules activated (versionbit 1)" } 
While a lot of discussion here is about BCH, all of our employees are banned from all of the Core's discussion forums, so this is the only place we can go. Any help someone can provide would be appreciated, as including more transactions in blocks would also allow the networks to function better for everyone.
submitted by MattAbrams to btc [link] [comments]

How much of an idiot am I?

First up - I have very little idea what I'm doing. Mined a bunch of BTC back in the day, sold most of them years ago, I'm just now having a play with the remainder.
I tried to send some BTC into an exchange just now, and I'm rather confused by what I'm seeing. I've no doubt that I'm an idiot and did something wrong, I'd just like to understand what I did! Here's the output from bitcoin-cli:
$ bitcoin-cli getinfo { "version": 140200, "protocolversion": 70015, "walletversion": 10500, "balance": 1.34880220, "blocks": 502207, "timeoffset": 0, "connections": 8, "proxy": "", "difficulty": 1931136454487.716, "testnet": false, "keypoololdest": 1293896718, "keypoolsize": 100, "paytxfee": 0.00005000, "relayfee": 0.00001000, "errors": "" } $ bitcoin-cli sendtoaddress 1FtRC6jnSPRxDXZ9dQFknkEvHvTNKmFDV6 0.02 b4b2dcd0e76518dee186a24c61ce9d76d9441cf48728e850d9049da5e0b0badf $ bitcoin-cli getinfo { "version": 140200, "protocolversion": 70015, "walletversion": 10500, "balance": 1.19619004, "blocks": 502207, "timeoffset": 0, "connections": 8, "proxy": "", "difficulty": 1931136454487.716, "testnet": false, "keypoololdest": 1293896718, "keypoolsize": 100, "paytxfee": 0.00005000, "relayfee": 0.00001000, "errors": "" } 
"Holy crap", thought I, "the transaction fees must have been ridiculous". But the transaction info is:
{ "account": "", "address": "1FtRC6jnSPRxDXZ9dQFknkEvHvTNKmFDV6", "category": "send", "amount": -0.02000000, "vout": 1, "fee": -0.00001290, "confirmations": 0, "trusted": false, "txid": "b4b2dcd0e76518dee186a24c61ce9d76d9441cf48728e850d9049da5e0b0badf", "walletconflicts": [ ], "time": 1514898128, "timereceived": 1514898128, "bip125-replaceable": "unknown", "abandoned": false } 
My calculations say 1.34880220 - 0.02 - 0.00001290 = 1.3287893. I have no other transactions listed, so why is my balance now showing 1.19619004BTC?! I look forward to face-palming very hard...
submitted by techWARlrus to Bitcoin [link] [comments]

Use the BTCP full Node on a Ubuntu 16.04 LTS from Terminal

In this post I want to show some use of the CLI BTCP wallet from linux terminal.
DISCLAIMER:
First of all, use this tutorial with small amount of BTCP, for example i used 0,01 BTCP, until you feel confortable with commands. An error can happen easily and as result you can loose your money. Be careful! Do it at your risk!
I consider you have already installed the wallet following this instructions:
https://github.com/BTCPrivate/bitcoinprivate
I use Ubuntu 16.04 LTS 64bit, but commands are similar for the windows client.
Open a terminal from your Ubuntu Desktop:
[email protected]:~$ 
type:
[email protected]:~$ ./BitcoinPrivate/src/btcpd --daemon 
you should see the message:
BTCP server starting 
This means the wallet is running in daemon mode.
to stop the node just typing:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli stop 
Answer:
BTCP server stopping 
You can also run the wallet in terminal, is nice to see it, let's try:
 [email protected]:~$ ./BitcoinPrivate/src/btcpd 
You will see the BTCP logo in text mode and the following info:
Thank you for running a Bitcoin Private node! You're strengthening the network and contributing to a social good. To ensure you are fully protecting your privacy when running BTCP, see . Block height | 340079 Connections | 8 Network solution rate | 8359387 Sol/s You are currently not mining. To enable mining, add 'gen=1' to your btcprivate.conf and restart. Since starting this node 1 minutes, 33 seconds ago: - You have validated 695 transactions! [Press Ctrl+C to exit] [Set 'showmetrics=0' to hide] 
See, you can also mine using the wallet! Nice! Just add gen=1 in the file btcprivate.conf. Probably you will never mine a coin, but still you to strenght the net, so, you can try if you want, then disable it when done:
Press CTRL and C to stop the server, then restart the server in daemon mode otherwhise you have to open a new terminal.
Let's find btcprivate.conf and other useful files:
[email protected]:~$ cd .btcprivate [email protected]:~/.btcprivate$ ls 
Answer:
blocks btcprivate.conf chainstate db.log debug.log fee_estimates.dat peers.dat wallet.dat 
You see here: btcprivate.conf and wallet.dat
Edit configuration file:
[email protected]:~/.btcprivate$ pico btcprivate.conf 
add gen=1 if you want to mine, then CTRL X and Y to save.
Restart the wallet....and....
Block height | 340091 Connections | 8 Network solution rate | 8211926 Sol/s Local solution rate | 0.0075 Sol/s Since starting this node 8 minutes, 5 seconds ago: - You have validated 684 transactions! - You have completed 1 Equihash solver runs. You are mining with the default solver on 1 threads. 
Congratulations! You are mining!
Now have a look to the wallet.dat file:
Nb: wallet.dat is your wallet!! If you delete it you will loose all your money!!!
wallet.dat is not encrypted, so, if you want to backup it i do as follows:
[email protected]:~/.btcprivate$ cp wallet.dat home/btcp/Desktop/wallet_btcp_back.dat 
Now you will find the wallet on your desktop. Zip it with an AES256 encryption and a strong password. Test if it works properly: extract it again and copy it in the directory, but before make an other copy of the wallet.dat file. Beware! I almost deleted the file once!
Nb: wallet.dat is your wallet!! If you delete it you will loose all your money!!!
Go back to your home directory, now, we want to play with our wallet:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli help 
if everything is running properly, you will see a list of commands like this:
z_exportwallet "filename" z_getbalance "address" ( minconf ) z_getnewaddress z_getoperationresult (["operationid", ... ]) z_getoperationstatus (["operationid", ... ]) z_gettotalbalance ( minconf ) z_importkey "zkey" ( rescan startHeight ) z_importwallet "filename" z_listaddresses z_listoperationids z_listreceivedbyaddress "address" ( minconf ) z_sendmany "fromaddress" [{"address":... ,"amount":...},...] ( minconf ) ( fee ) z_shieldcoinbase "fromaddress" "tozaddress" ( fee ) zcbenchmark benchmarktype samplecount zcrawjoinsplit rawtx inputs outputs vpub_old vpub_new zcrawkeygen zcrawreceive zcsecretkey encryptednote zcsamplejoinsplit [email protected]:~$ 
Nice! Wallet is running properly. Now try an other command: getinfo
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getinfo 
Answer:
{ "version": 1001251, "protocolversion": 180004, "walletversion": 60000, "balance": 0.00000000, "blocks": 340074, "timeoffset": 0, "connections": 8, "proxy": "", "difficulty": 167290.7158221716, "testnet": false, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000, "relayfee": 0.00000100, "errors": "" } [email protected]:~$ 
You see some useful info about your wallet/node:
blocks is the block heights, in this case is synced with the network. If not the number would be lower.
The wallet is connected to other 8 nodes, the balance is 0.00 BTCP
An other info command can be getblockchaininfo:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getblockchaininfo 
Answer:
{ "chain": "main", "blocks": 340074, "headers": 340074, "bestblockhash": "0000000145c0011d8e914f4ba68d1443c7ae0dd15bdf0bc300994dd5282710aa", "difficulty": 165971.1181999981, "verificationprogress": 0.9999992572690658, "chainwork": "0000000000000000000000000000000000000000000000000002e8314e4484da", "pruned": false, "commitments": 663480, 
we see syncing is almost finished:
"verificationprogress": 0.9999992572690658, (99,99999%)
Now test the wallet with command getwalletinfo
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Answer:
{ "walletversion": 60000, "balance": 0.00000000, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 0, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } [email protected]:~$ 
Now we want to send some btcp to this wallet. First we need an address, get one using getnewaddress:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getnewaddress 
Answer:
b1Cabjwvcce7N8ea9Gxxxxxxxxxxxxxxxx [email protected]:~$ 
Send at this address some BTCP, i sent 0.01 for testing purpose using your ledger, or your wallet, then check if the transaction is done:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Answer:
{ "walletversion": 60000, "balance": 0.00000000, "unconfirmed_balance": 0.01000000, "immature_balance": 0.00000000, "txcount": 1, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } 
Done! Unconfirmed balance is 0.01! Just wait some confirmations.
after a while:
"walletversion": 60000, "balance": 0.01000000, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 1, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 
Now send the coins to a new address. I am using this command:
sendtoaddress "btcpaddress" amount ( "comment" "comment-to" subtractfeefromamount )
subtractfeefromamount parameter can be true or false
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli sendtoaddress "b1Nb42GoK9kmsxxxxxxxxxxxxx" 0.01 "" "" true 
Answer:
2c5d3d1a3b5eec414b721d3817487f53c5eebxxxxxxxxxxxxxxx [email protected]:~$ 
Now check the wallet:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Answer:
{ "walletversion": 60000, "balance": 0.00999808, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 2, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } 
I sent BTCP to the same wallet, so now i have less BTCP because of the fees.
try more commands:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listreceivedbyaddress 
Answer:
[ { "address": "b1Ep2wi2tUnKf433Vaxxxxxxxxxxxx", "account": "", "amount": 0.01000000, "confirmations": 6, "txids": [ "833533440a13c09fda6e90d0c5xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ] }, { "address": "b1Nb42GoK9kmsVZ9KPxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "account": "", "amount": 0.00999808, "confirmations": 1, "txids": [ "2c5d3d1a3b5eec414b721d3817487f53c5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ] } 
This is the list of all used addresses.
Now find the money and the address where they are: use listunspent
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listunspent 
Answer:
[ { "txid": "2c5d3d1a3b5eec414b721d381748xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "vout": 0, "generated": false, "address": "b1Nb42GoK9kxxxxxxxxxxxxxx", "account": "", "scriptPubKey": "76a914c6bdf3bc8aedxxxxxxxxxxxxxxxxxx", "amount": 0.00999808, "confirmations": 6, "spendable": true 
Well done.
Other useful commands can be: dumpprivkey to extract the private key from an address
Be careful! Exposing your private keys will end in loosing your money
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli dumpprivkey b1Ep2wi2tUnxxxxxxxxxxx 
Obtaining the pvt key:
Kz29e62Bmxxxxxxxxxxxxxxxxxxxxxxx 
And now, swipe the private key using the command: importprivkey "btcpprivkey" ( "label" rescan )
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli importprivkey "Kz29e62Bmxxxxxxxxxxxxxxxxxxxxx" "" true 
Let's do a shielded transaction!
first, you must have a z_address:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_getnewaddress 
Answer:
zkEvCiVwgHb3NFi2ee9HGPjno2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 
Check balaces, with also z_addres:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_gettotalbalance 
Answer:
{ "transparent": "0.00999808", "private": "0.00", "total": "0.00999808" } 
Now send some BTCP to the z_address. First, check where BTCP are:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listunspent 
Output:
[ { "txid": "72f568d1ed51524b69f1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "vout": 0, "generated": false, "address": "b1LDhxBJxxxxxxxxxxxxxxxxxxxxxx", "scriptPubKey": "76axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe088xx", "amount": 0.00889808, "confirmations": 556, "spendable": true } ] 
Now, sent a little transparent amount to the shielded address we got before:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_sendmany "b1LDhxBJxxxxxxxxxxxxxxxxxxxxxx" "[{\"amount\":0.001, \"address\":\"zkEvCiVwgHb3xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\"}]" 
Output:
opid-xxxxxxx-36c4-xxxx-beb2-xxxxxxxxxxxx 
Now your PC will work a while, it's CPU consuming...so...check:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_getoperationresult 
until you receive the answer:
[ { "id": "opid-xxxxxx-xxxxx-4a5d-beb2-xxxxxxxxxx", "status": "success", "creation_time": 1529426885, "result": { "txid": "f87e8d5e96a8a0xxxxxxxxxxxxxxx" }, "execution_secs": 216.686332567, "method": "z_sendmany", "params": { "fromaddress": "b1LDhxxxxxxxxxxx", "amounts": [ { "amount": 0.001, "address": "zkEvCiVwgHb3NFxxxxxxxxxxxxxxxxxxR" } ], "minconf": 1, "fee": 0.0001 } } ] 
Done! On my old PC it took 216.68 seconds!
Next will be a reverse operation, from Shielded address to transparent address. See you soon....
Play with your full node wallet and have fun.
Remember: these commands are almost the same in all the bitcoin based coins, so you also learnt how to use many other wallets!
submitted by xivan71 to u/xivan71 [link] [comments]

I'd be happy to spin up Classic nodes on your behalf.

I'd be launching these as separate Amazon AWS EC2 instances ( so separate actual IP's ).
It's looking like I should be able to make $10 = one node for one month. Maybe longer, I'll be looking more into optimization.
In any case, I know a lot of folks want to spin up more nodes right now, and you may not have the technical know-how, or you might not want to have your home IP DDOS'ed.
So feel free to throw some coins at this address:
1BmeNoe1i47X4N6b8zUqaz7ou2TkuKtHsj
https://blockchain.info/address/1BmeNoe1i47X4N6b8zUqaz7ou2TkuKtHsj
I'll put every satoshi towards classic node spawning.
Also I'll work on a way to bring more visibility into the nodes that I have running. For now I don't have a system in place.
But I would venture to say that hellobitcoinworld can vouch for me, and we could probably have a solution for more visibility up on nodecounter.com sometime this week.

Edit 1

I'm still waiting for my first node to catch up on the blockchain, then I'll be able to clone it out into many more. So far I have received ~$55, so after my personal ( and more beefy / expensive ) node is up and running, I'll clone it to 6-8 other less-beefy nodes. As shown below, it's currently at block 348122, so just a little over 50k more blocks to go, but it's slowing down tremendously since each block is ~ 1MB.
For those interested, I am more-or-less using this as my blueprint: https://www.reddit.com/btc/comments/44nzbs/tutorial_running_a_bitcoin_classic_full_node_on_a/
If you're gonna do this yourself, I would suggest combining all of the apt-get install commands into one: https://www.reddit.com/btc/comments/44nzbs/tutorial_running_a_bitcoin_classic_full_node_on_a/d0hdu2s
Also AWS EC2 ports are managed in the web GUI
Here's the current output:
[email protected]##-###:~$ ./bitcoin-0.11.2/bin/bitcoin-cli getinfo { "version" : 110200, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 348122, "timeoffset" : -2, "connections" : 8, "proxy" : "", "difficulty" : 47427554950.64830017, "testnet" : false, "keypoololdest" : 1456701073, "keypoolsize" : 101, "paytxfee" : 0.00000000, "relayfee" : 0.00005000, "errors" : "" } [email protected]##-###:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 996M 12K 996M 1% /dev tmpfs 201M 340K 200M 1% /run /dev/xvda1 126G 38G 84G 31% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 1001M 0 1001M 0% /run/shm none 100M 0 100M 0% /run/user 
I'll update here when I have the other nodes up and running, with some stats.

Edit 2 - 03/05/2016

Well it took for-freakin-ever to get one node to actually catch up on the blockchain. For anyone doing this in the future, use at least a m4.large EC2 instance. The higher network performance and RAM are essential.
Now that this one is caught up, I can clone away, I'm going to create 10 smaller ones now.
Here's stats on the beefy one:
[email protected]##-###:~$ ./bitcoin-0.11.2/bin/bitcoin-cli getinfo { "version" : 110200, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 401298, "timeoffset" : -1, "connections" : 17, "proxy" : "", "difficulty" : 158427203767.39169312, "testnet" : false, "keypoololdest" : 1456701073, "keypoolsize" : 101, "paytxfee" : 0.00000000, "relayfee" : 0.00005000, "errors" : "" } [email protected]##-###:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 3.9G 12K 3.9G 1% /dev tmpfs 799M 344K 799M 1% /run /dev/xvda1 126G 69G 53G 57% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 3.9G 0 3.9G 0% /run/shm none 100M 0 100M 0% /run/user 

Edit 3 - 03/05/2016

I have 10 nodes running Bitcoin Classic 0.12.0. I will run them as long as there are funds to do so.
Here's example output from one of them:
[email protected]##-###:~$ ./bitcoin-0.12.0/bin/bitcoin-cli getinfo { "version": 120000, "protocolversion": 70012, "walletversion": 60000, "balance": 0.00000000, "blocks": 401320, "timeoffset": -2, "connections": 11, "proxy": "", "difficulty": 158427203767.3917, "testnet": false, "keypoololdest": 1456701073, "keypoolsize": 101, "paytxfee": 0.00000000, "relayfee": 0.00001000, "errors": "" } 
submitted by icodeforbitcoin to btc [link] [comments]

Bitcoin daemon troubleshooting

I have an ubuntu server and want to run a full bitcoin node on it. I followed the instructions from bitcoin.org and it seems that everything installed correctly, but i had it running for over 10h and syncing is still at block 0. Here is the output of bitcoin-cli getinfo:
"version": 130000, "protocolversion": 70014, "walletversion": 130000, "balance": 0.00000000, "blocks": 0, "timeoffset": 0, "connections": 3, "proxy": "", "difficulty": 1, "testnet": false, "keypoololdest": 1474289178, "keypoolsize": 100, "paytxfee": 0.00000000, "relayfee": 0.00001000, "errors": ""
What should i do to get it to work?
submitted by Nizagam to Bitcoin [link] [comments]

Another Classic node online and sync'd!

./bitcoin-0.11.2/bin/bitcoin-cli getinfo { "version" : 110200, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 398203, "timeoffset" : -1, "connections" : 17, "proxy" : "", "difficulty" : 144116447847.34866333, "testnet" : false, "keypoololdest" : 1455226900, "keypoolsize" : 101, "paytxfee" : 0.00000000, "relayfee" : 0.00005000, "errors" : "" } 
:D
submitted by obanite to btc [link] [comments]

Problem with BU Core client

[edit] UGH I meant to say "BU Cash" in the title, not Core!
I stopped the BU client and removed. Then I installed BU Cash client. I deleted the .bitcoin/peers.dat file, then started up the new client. That was yesterday. bitcoin-cli getinfo shows me:
{ "version": 1010000, "protocolversion": 80002, "walletversion": 10500, "balance": , "blocks": 479096, "timeoffset": 0, "connections": 69, "proxy": "", "difficulty": 860221984436.2223, "testnet": false, "keypoololdest": 1308596147, "keypoolsize": 101, "paytxfee": 0.00005000, "relayfee": 0.00003000, "errors": "" } 
That sure looks like the original chain? Do I have the right one installed? bitcoind --version shows me:
Bitcoin Unlimited Daemon version v1.1.0.0-unk Copyright (C) 2015-2017 The Bitcoin Unlimited Developers Portions Copyright (C) 2009-2017 The Bitcoin Core Developers Portions Copyright (C) 2014-2017 The Bitcoin XT Developers This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING or . This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit  and cryptographic software written by Eric Young and UPnP software written by Thomas Bernard. 
submitted by mohrt to btc [link] [comments]

Created a full node in ~8 minutes thanks to the contributions of another redditor. Feels great. Please no tips, just sharing information.

Hello /Bitcoin
I just wanted to say that if any of you have been considering starting a bitcoin node, you should do it. I am a programmer, but I've never dabbled into cloud hosting and I've never done anything "advanced" with bitcoin before (I really don't consider this advanced).
I just want to say that this process is super easy:
  1. Get a cloud hosted machine from your provider of choice. I went with Digital Ocean.
  2. Run this script*, or a version of this script (this one was submitted by ymmv2). In my case I made a few modifications to fit my personal needs/choices.
  3. Check the status of the node, both on the node and from an external source.
On the node, run: $bitcoind getinfo
From an external source: https://getaddr.bitnodes.io just plug in the IP of your machine to verify that its accepting incoming connections on port 8333.
Currently my machine has 12 active connections according to bitcoind:
$ bitcoind getinfo
{
"version" : 90300, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 143913, "timeoffset" : -1, "connections" : 12, "proxy" : "", "difficulty" : 1777774.48200146, "testnet" : false, "keypoololdest" : 1416794587, "keypoolsize" : 101, "paytxfee" : 0.00000000, "relayfee" : 0.00001000, "errors" : "" 
}
That is really all you need to get stared!
For me, this was just a trial run on an inexpensive box. I am going to learn bitcoind better and once I get a handle on it, I may do some more advanced stuff (I may also host a litecoin node) on a more powerful box, but for now this was a great way to get my feet wet and give something back to the bitcoin network.
I would also like to use the map on https://getaddr.bitnodes.io to deploy another node in a part of the world that is lacking in nodes, such as Africa or South America, but I would have to find a cloud hosting solution that offers boxes in that region. For now I deployed my node in the Bay Area, SF.
*NOTE: Never sudo a script from the internet unless you know what it does. In my case, I analyzed and understood every command in that script and so I was aware of what I was doing. If you don't know what certain commands do, such as "dd" or how the apt-get system works, I definitely recommend that you google for the manpages and or documentation of each tool and get to know the tool before you just run stuff you saw on github.
Lastly: The IP of the node: 104.236.181.78 (Currently up with more storage and more horsepower)
UPDATE - I took the node down temporarily, it is coming back up in about 20 minutes (currently 11:15PM CST) with a new IP on a faster box with more storage.
Update: Woot, up to 20 connections and rising slowly. I think I will definitely be purchasing a more powerful box in the near future to really serve as many clients as possible, then move this smaller node to Europe until I find cloud hosting in South America and/or Africa. To the moon!
submitted by gunslinger_006 to Bitcoin [link] [comments]

Uso del Full Node Wallet BTCP Bitcoin Private da Terminale Linux

In questo post voglio dimostrare alcuni utilizzi del Full Node Wallet Bitcoin Private da terminale Linux
AVVERTENZA:
Usate questo tutorial con un piccolo quantitativo di BTCP, nell'esempio utilizzo 0,01 BTCP, almeno fino a quando non vi sentite sicuri nell'uso dei comandi. Fate attenzione! I comandi vengono eseguiti senza possibilità di annullarli, salvo in casi eccezionali, quindi fate tutto a vostro rischio.
PREMESSA:
Il wallet è già stato installato sul vostro PC o in un server Cloud usando le seguenti istruzioni:https://github.com/BTCPrivate/bitcoinprivate
Io uso una Ubuntu 16.04 LTS 64bit, ma i comandi sono simili anche per la distribuzione Windows.
Andrebbe anche aperta la porta TCP 7932 per avere un wallet perfettamente funzionante, ma ho fatto le prove senza aprirla.
Come attivare il firewall:
sudo ufw status
Please note: Make sure you enter the code in this order! If you do not, the program will not work! (If need be you can disable your firewall by entering: sudo ufw disable)
sudo ufw default allow outgoing sudo ufw default deny incoming sudo ufw allow ssh/tcp sudo ufw limit ssh/tcp sudo ufw allow http/tcp sudo ufw allow https/tcp sudo ufw allow 7932/tcp sudo ufw logging on sudo ufw enable
Apri un nuovo terminale troverai il prompt dei comandi, il mio è così, ma potrebbe essere differente:
[email protected]:~$ 
Scrivi quello che segue e premi invio:
[email protected]:~$ ./BitcoinPrivate/src/btcpd --daemon 
dovrebbe apparire il seguente messaggio:
BTCP Server Starting 
Questo significa che hai avviato il server (full node wallet) in modalità daemon, silenziosa. Per fermarlo scrivi:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli stop 
Otterrai la risposta:
BTCP server stopping 
Puoi anche avviare il wallet in una finestra del terminale e vederlo lavorare, anzichè usare il comando --daemon
[email protected]:~$ ./BitcoinPrivate/src/btcpd 
Vedreai apparire un logo del BTCP formato da tanti caratteri e la seguente scritta:
Thank you for running a Bitcoin Private node! You're strengthening the network and contributing to a social good. To ensure you are fully protecting your privacy when running BTCP, see . Block height | 340079 Connections | 8 Network solution rate | 8359387 Sol/s You are currently not mining. To enable mining, add 'gen=1' to your btcprivate.conf and restart. Since starting this node 1 minutes, 33 seconds ago: - You have validated 695 transactions! [Press Ctrl+C to exit] [Set 'showmetrics=0' to hide] 
Block height è l'allineamento del wallet con la blockchain, richiede tempo perchè si allinei e scarichi tutta la blockchain, dipende dalla velocità del tuo collegamento e del tuo pc.Connections: 8 sono i nodi a cui è collegato il nostro wallet, che è un vero e proprio nodo.
Network solution rate è la "potenza" di tutta la rete di elaborare i blocchi in Sol/s
Con un full node puoi partecipare anche tu a rafforzare la rete, abilitando il mining. Si tratta di un solo mining, quindi le probabilità di risolvere un blocco sono veramente minime.
Per farlo basta aggiungere la voce gen=1 nel file btcprivate.conf
Proviamo a farlo. Blocchiamo il nodo con il comando CTRL + C e aspettiamo che appaia il prompt di comando.
Appena appare, inseriamo i seguenti comandi:
[email protected]:~$ cd .btcprivate [email protected]:~/.btcprivate$ ls 
ci siamo spostati nella directory nascosta (inizia per .) contenente i file di configurazione di BTCP, ls mostra i file contenuti:
blocks btcprivate.conf chainstate db.log debug.log fee_estimates.dat peers.dat wallet.dat 
puoi vedere il file btcprivate.conf e wallet.dat che è il file del wallet del nodo. Editiamo ora il file di configurazione, io uso PICO, un text editor per linux, ma potete usare anche vi se preferite:
[email protected]:~/.btcprivate$ pico btcprivate.conf 
inserite gen=1 in una riga vuota del file di configurazione e poi chiudete l'editor salvando con i comandi CTRL+X e Y
gen=1 
tornate nella directory home:
[email protected]:~/.btcprivate$ cd 
Fate riavviare il wallet con il comando:
[email protected]:~$ ./BitcoinPrivate/src/btcpd 
Otterrete il seguente output:
Block height | 340091 Connections | 8 Network solution rate | 8211926 Sol/s Local solution rate | 0.0075 Sol/s Since starting this node 8 minutes, 5 seconds ago: - You have validated 684 transactions! - You have completed 1 Equihash solver runs. You are mining with the default solver on 1 threads. 
Congratulazioni! State minando!
Ora diamo un occhiata al file wallet.dat
ATTENZIONE:
wallet.dat è il vostro wallet, se lo cancellate o lo riscrivete perderete tutti i BTCP che contiene. Consiglio di farne una copia ma attenzione: wallet.dat non è crittografato, quindi vi consiglio di crittografarlo prima di spostarlo dal PC: primo faccio una copia.
Bloccate nuovamente il wallet con CTRL+C
Al prompt scrivete:
[email protected]:~$ cd .btcprivate 
Poi copiate il file sul Desktop (scrivania) Sostituite la parola Desktop con Scrivania se avete installato Linux in Italiano
[email protected]:~/.btcprivate$ cp wallet.dat home/btcp/Desktop/wallet_btcp_back.dat 
Ora troverete il file wallet_btcp_back.dat sulla scrivania, crittografatelo AES256 usando il gestore degli archivi GUI e impostando una password resistente. Per verificare che tutto funzioni, vi consiglio di fare una altra copia di wallet.dat, estrarre il file dall'archivio crittato e sostituirlo al wallet.dat. se tutto funziona siete a posto. Se non siete sicuri non fate nulla e non usate questo wallet per mettere i vostri BTCP, ma nolo per scopi didattici con pochi spiccioli. E' facile fare errori e perdere tutto.
Tornate alla directory home e riavviate il server in daemon mode.
proviamo alcuni comandi usando il client: btcp-cli
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli help 
Se tutto funziona correttamente vi risponderà con la lista di tutti i comandi disponibili:
z_exportwallet "filename" z_getbalance "address" ( minconf ) z_getnewaddress z_getoperationresult (["operationid", ... ]) z_getoperationstatus (["operationid", ... ]) z_gettotalbalance ( minconf ) z_importkey "zkey" ( rescan startHeight ) z_importwallet "filename" z_listaddresses z_listoperationids z_listreceivedbyaddress "address" ( minconf ) z_sendmany "fromaddress" [{"address":... ,"amount":...},...] ( minconf ) ( fee ) z_shieldcoinbase "fromaddress" "tozaddress" ( fee ) zcbenchmark benchmarktype samplecount zcrawjoinsplit rawtx inputs outputs vpub_old vpub_new zcrawkeygen zcrawreceive zcsecretkey encryptednote zcsamplejoinsplit [email protected]:~$ 
Benissimo! Ora proviamo ad usare qualche comando, comunciamo con getinfo
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getinfo 
Risposta:
{ "version": 1001251, "protocolversion": 180004, "walletversion": 60000, "balance": 0.00000000, "blocks": 340074, "timeoffset": 0, "connections": 8, "proxy": "", "difficulty": 167290.7158221716, "testnet": false, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000, "relayfee": 0.00000100, "errors": "" } [email protected]:~$ 
Nella risposta troverete alcune informazioni sul wallet, versione, block height, connections, balance = 0 ecc ecc
Proviamo ora getblockchaininfo:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getblockchaininfo 
Risposta:
{ "chain": "main", "blocks": 340074, "headers": 340074, "bestblockhash": "0000000145c0011d8e914f4ba68d1443c7ae0dd15bdf0bc300994dd5282710aa", "difficulty": 165971.1181999981, "verificationprogress": 0.9999992572690658, "chainwork": "0000000000000000000000000000000000000000000000000002e8314e4484da", "pruned": false, "commitments": 663480, 
La sincronizzazione in questo caso è terminata:"verificationprogress": 0.9999992572690658, (99,99999%)
Ora proviamo getwalletinfo
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Risposta:
{ "walletversion": 60000, "balance": 0.00000000, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 0, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } [email protected]:~$ 
Proviamo a ricevere dei BTCP da un wallet esterno, per prima cosa abbiamo bisogno di un transparent address da comunicare a chi ci invia i BTCP. Lo otteniamo con il comando getnewaddress:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getnewaddress 
Risposta: otteniamo un indirizzo (le xxx le ho aggiunte per mascherarlo)
b1Cabjwvcce7N8ea9Gxxxxxxxxxxxxxxxx [email protected]:~$ 
Inviate con un vostro wallet grafico o con electrum pochi BTCP, io ne ho mandati 0.01 per prova, dopo che li avete inviati, verificate se sono arrivati:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Risposta:
{ "walletversion": 60000, "balance": 0.00000000, "unconfirmed_balance": 0.01000000, "immature_balance": 0.00000000, "txcount": 1, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } 
Arrivati ! "Unconfirmed balance" 0.01! non sono ancora confermati, quindi aspettate un po' e ripetete il comando:
"walletversion": 60000, "balance": 0.01000000, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 1, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 
Adesso balance è 0.01 perfetto!
Proviamo adesso ad inviare questi BTCP ad un nuovo T-Address, per semplicità li invierò ad un indirizzo di questo wallet
Generiamo un nuovo indirizzo per riceverli:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getnewaddress 
Otteniamo:
b1Nb42GoK9kmsxxxxxxxxxxxxx 
copiamo l'indirizzo e usiamo il comando sendtoaddress "btcpaddress" amount ( "comment" "comment-to" subtractfeefromamount )
il parametro subtractfeefromamount puo' essere true or false a seconda se vogliamo che le fee vengano detratte dall'ammontare inviato o meno. Io invio tutto quanto al nuovo indirizzo e quindi le fee vanno dedotte da questo:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli sendtoaddress "b1Nb42GoK9kmsxxxxxxxxxxxxx" 0.01 "" "" true 
Risposta:
2c5d3d1a3b5eec414b721d3817487f53c5eebxxxxxxxxxxxxxxx [email protected]:~$ 
Controlliamo cosa è successo:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli getwalletinfo 
Risposta:
{ "walletversion": 60000, "balance": 0.00999808, "unconfirmed_balance": 0.00000000, "immature_balance": 0.00000000, "txcount": 2, "keypoololdest": 1528833903, "keypoolsize": 101, "paytxfee": 0.00000000 } 
Come vedete i BTCP sono diminuiti, perchè sono stati spostati su un nuovo indirizzo dello stesso wallet, pagando le fee. Ora vediamo esattamente dove sono e dove erano:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listreceivedbyaddress 
Risposta:
[ { "address": "b1Ep2wi2tUnKf433Vaxxxxxxxxxxxx", "account": "", "amount": 0.01000000, "confirmations": 6, "txids": [ "833533440a13c09fda6e90d0c5xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ] }, { "address": "b1Nb42GoK9kmsVZ9KPxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "account": "", "amount": 0.00999808, "confirmations": 1, "txids": [ "2c5d3d1a3b5eec414b721d3817487f53c5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ] } 
Questo comando vi da informazione di tutti gli indirizzi usati, vediamo solo gli indirizzi non spesi: listunspent
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listunspent 
Risposta:
[ { "txid": "2c5d3d1a3b5eec414b721d381748xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "vout": 0, "generated": false, "address": "b1Nb42GoK9kxxxxxxxxxxxxxx", "account": "", "scriptPubKey": "76a914c6bdf3bc8aedxxxxxxxxxxxxxxxxxx", "amount": 0.00999808, "confirmations": 6, "spendable": true 
Ottimo!
Ora possiamo provare un comando che ci permette di estrarre la chiave provata da un indirizzo pubblico. Questo puo' essete utile in occasione di Fork o Airdrop per estrarre le monete.
ATTENZIONE: esporre a terzi le chiavi private è rischioso. Potrebbero rubare tutto il contenuto. Fate molta attenzione. Estraete le private keys solo se necessario o per fare delle prove su indirizzi che contengono pochi spicci. In ogni caso, dopo aver usato la private key meglio non riutilizzare quell'indirizzo.
Il comando da utilizzare è dumpprivkey T-ADDRESS
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli dumpprivkey b1Ep2wi2tUnxxxxxxxxxxx 
L'output sarà tipo il seguente, al solito la chiave è mascherata con delle xxxxxx
Kz29e62Bmxxxxxxxxxxxxxxxxxxxxxxx 
Ora proviamo lo swipe della chiave, cioè il wallet andrà a cercare nella blockchain tutti gli importi collegati a quella pvt key, : importprivkey "btcpprivkey" ( "label" rescan )
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli importprivkey "Kz29e62Bmxxxxxxxxxxxxxxxxxxxxx" "" true 
Ora proviamo a fare delle Shielded Transaction, queste transazioni utilizzano la tecnologia zk-Snark per mascherare importi e indirizzi. Per prima cosa dobbiamo ottenere un indirizzo Shielded dal nostro wallet.
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_getnewaddress 
Eccolo generato:
zkEvCiVwgHb3NFi2ee9HGPjno2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 
Vediamo dove sono i nostri BTCP, al momento sono solo su indirizzi Transparent:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_gettotalbalance 
Answer:
{ "transparent": "0.00999808", "private": "0.00", "total": "0.00999808" } 
ora mandiamo qualche BTCP all'indirizzo z_address. Per prima cosa dobbiamo recuperare l'indirizzo t-address dove si trovano:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli listunspent 
Eccoli:
[ { "txid": "72f568d1ed51524b69f1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "vout": 0, "generated": false, "address": "b1LDhxBJxxxxxxxxxxxxxxxxxxxxxx", "scriptPubKey": "76axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe088xx", "amount": 0.00889808, "confirmations": 556, "spendable": true } ] 
Adesso mandiamo un po' di BTCP all'indirizzo Shielded che abbiamo ottenuto sopra. Il comando è abbastanza complicato ma funziona cosi':
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_sendmany "b1LDhxBJxxxxxxxxxxxxxxxxxxxxxx" "[{\"amount\":0.001, \"address\":\"zkEvCiVwgHb3xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\"}]" 
Risultato:
opid-xxxxxxx-36c4-xxxx-beb2-xxxxxxxxxxxx 
Una transazione zk-Snark è piuttosto pesante da elaborare, il mio vecchio PC ci mette un po'. Meglio disattivare processi inutili. Si puo' controllare se l'operazione è andata a buon fine:
[email protected]:~$ ./BitcoinPrivate/src/btcp-cli z_getoperationresult 
al termine dovreste ricevere il seguente output:
[ { "id": "opid-xxxxxx-xxxxx-4a5d-beb2-xxxxxxxxxx", "status": "success", "creation_time": 1529426885, "result": { "txid": "f87e8d5e96a8a0xxxxxxxxxxxxxxx" }, "execution_secs": 216.686332567, "method": "z_sendmany", "params": { "fromaddress": "b1LDhxxxxxxxxxxx", "amounts": [ { "amount": 0.001, "address": "zkEvCiVwgHb3NFxxxxxxxxxxxxxxxxxxR" } ], "minconf": 1, "fee": 0.0001 } } ] 
Fatto! Sul mio vecchio PC ci sono voluti 216,68 secondi!
La prossima prova sarà un invio da indirizzo Shielded a Transparent.
Play with your full node wallet and have fun.Remember: these commands are almost the same in all the bitcoin based coins, so you also learnt how to use many other wallets!
submitted by xivan71 to u/xivan71 [link] [comments]

I can spin up Classic 0.12.0 nodes on your behalf.

Last week, we had a lot of DDoS attacks on classic nodes. This was interfering with people's personal/home networks, and causing some nodes to go offline.
The general consensus of the community was that the best way to respond was to spin up more nodes. If a DDoS results in MORE nodes, then it ceases to be useful.
So last week I offered to spin up nodes on other's behalf, and received some donations. At this time I have 10 Classic 0.12.0 nodes running on AWS EC2 instances. The cost appears to be between $5/mo and $10/mo per node.

How to help

If anyone would like me to spin up more, send coins here: 1BmeNoe1i47X4N6b8zUqaz7ou2TkuKtHsj

Previous Post

Here's the first post from last week with more notes:
https://np.reddit.com/btc/comments/487ai9/id_be_happy_to_spin_up_classic_nodes_on_you

Example Output

And here's some current output from one of the 10 nodes:
[email protected]##-###:~$ ./bitcoin-0.12.0/bin/bitcoin-cli getinfo { "version": 120000, "protocolversion": 70012, "walletversion": 60000, "balance": 0.00000000, "blocks": 401505, "timeoffset": 1, "connections": 17, "proxy": "", "difficulty": 158427203767.3917, "testnet": false, "keypoololdest": 1456701073, "keypoolsize": 101, "paytxfee": 0.00000000, "relayfee": 0.00001000, "errors": "" } 
submitted by icodeforbitcoin to btc [link] [comments]

stopping block sync at 300911

bitcoin-cli getinfo { "version": 1000103, "protocolversion": 80002, "walletversion": 60000, "balance": 0.00000000, "blocks": 300911, "timeoffset": 0, "connections": 18, "proxy": "", "difficulty": 8853416309.1278, "testnet": false, "keypoololdest": 1492390964, "keypoolsize": 101, "paytxfee": 0.00000000, "relayfee": 0.00000000, "errors": "" } How to make sync active ?
submitted by bluejaytodd to btc [link] [comments]

Size of blockchain vs size on disk [bitcoind node question]

Quick check.
At the time of this posting, the blockchain size appears to be 24.32GB.
The current block appears to be: 332,061.
Yet, on the node I'm running, the blocks are taking up substantially more space:
$du -h /root
4.0K /root/.cache
8.0K /root/.ssh
16K /root/.aptitude
244K /root/.bitcoin/database
610M /root/.bitcoin/chainstate
46M /root/.bitcoin/blocks/index
29G /root/.bitcoin/blocks
29G /root/.bitcoin
29G /root
At this rate, it appears my 40GB VPS will run out of space soon, which is disconcerting because I thought I would be good to go for at least another 6 months on a 40GB machine.
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 40G 33G 5.0G 87% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 991M 4.0K 991M 1% /dev
tmpfs 201M 316K 200M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1001M 0 1001M 0% /run/shm
none 100M 0 100M 0% /run/user
More debug info:
bitcoind getinfo
{
"version" : 90300, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 331737, "timeoffset" : 0, "connections" : 29, "proxy" : "", "difficulty" : 40300030327.89140320, "testnet" : false, "keypoololdest" : 1417064498, "keypoolsize" : 101, "paytxfee" : 0.00000000, "relayfee" : 0.00001000, "errors" : "" 
}
Does anyone know:
  1. If there is a way to decrease this size (are there deletable files that can be purged without purging parts of the blockchain itself?).
  2. What the real math is for VPS hosting of a bitcoind node? For example, if the current blockchain size is 24.32GB, but the bitcoind application actually consumes at least 29GB...it would seem there is substantial file size overhead here...what is this overhead in relation to the size of the blockchain?
I'm trying to figure out exactly what my VPS needs truly are for hosting a node in the cheapest way (not mining or storing coins, just helping the network and learning)...and it seems like Digital Ocean (while I LOVE THEM) may not be the best choice since they do not offer ala carte SSD sizing (you have to go up to a much faster machine to get more space).
Thoughts?
I really like Digital Ocean, but it seems like I will have to wait for them to release ala carte SSD sizing (I was told it would happen in 2015) for them to be a truly efficient hosting solution for running a node.
Can anyone else recommend another VPS host solution that does offer ala carte storage/SSD/HDD sizing?
submitted by gunslinger_006 to Bitcoin [link] [comments]

Bitcoin Core 0.13.2 released | Wladimir J. van der Laan | Jan 03 2017

Wladimir J. van der Laan on Jan 03 2017:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.13.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.13.2/
Or by bittorrent:
magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn;=bitcoin-core-0.13.2&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

Microsoft ended support for Windows XP on April 8th, 2014,
an OS initially released in 2001. This means that not even critical security
updates will be released anymore. Without security updates, using a bitcoin
wallet on a XP machine is irresponsible at least.
In addition to that, with 0.12.x there have been varied reports of Bitcoin Core
randomly crashing on Windows XP. It is not clear
what the source of these crashes is, but it is likely that upstream
libraries such as Qt are no longer being tested on XP.
We do not have time nor resources to provide support for an OS that is
end-of-life. From 0.13.0 on, Windows XP is no longer supported. Users are
suggested to upgrade to a newer version of Windows, or install an alternative OS
that is supported.
No attempt is made to prevent installing or running the software on Windows XP,
you can still do so at your own risk, but do not expect it to work: do not
report issues about Windows XP to the issue tracker.
but severe issues with the libc++ version on 10.7.x keep it from running reliably.
0.13.1 now requires 10.8+, and will communicate that to 10.7 users, rather than crashing unexpectedly.
Notable changes

Change to wallet handling of mempool rejection
When a newly created transaction failed to enter the mempool due to
the limits on chains of unconfirmed transactions the sending RPC
calls would return an error. The transaction would still be queued
in the wallet and, once some of the parent transactions were
confirmed, broadcast after the software was restarted.
This behavior has been changed to return success and to reattempt
mempool insertion at the same time transaction rebroadcast is
attempted, avoiding a need for a restart.
Transactions in the wallet which cannot be accepted into the mempool
can be abandoned with the previously existing abandontransaction RPC
(or in the GUI via a context menu on the transaction).
0.13.2 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

Consensus

RPC and other APIs

Block and transaction handling

P2P protocol and network code

Build system

GUI

Wallet

Tests and QA

Miscellaneous

Credits

Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJYa2IbAAoJEHSBCwEjRsmmiQsIALbkHVVwO7nViQKH1Ub2qpD4
TplOuAP0/4vYotizuI12Gqdnu8SjPmhKwAgIXhVinE6TS4OzGNjy+6LtWGzpcpud
B1pcziZ72Mlfxdbdd1UhDMWEjoBumS9RmXMSqzTlMVlHRv4iiISzdaAROu1jHvdF
YTsnmKXB8OvcXOecxRMY9LrnpSzLALM2MYTDmYwlhhExHIA8ZqI2niky6GCfyfDi
KD7bgfIFJzlgFTpAdhQXOXtWoRV5iHqN7T29ot8Y+yIhVCRhHYXS93Z50GKbkqYV
MXsVAkpZF3qqcKYSPFjbif7faMdrMqcEiII6QhXdDTRGI/35IfuTDbWzzQlnVyY=
=ncCY
-----END PGP SIGNATURE-----
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013412.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

[Meta] Re: Bitcoin Core 0.13.2 released | Luke Dashjr | Jan 07 2017

Luke Dashjr on Jan 07 2017:
I don't think release announcements are really appropriate for the bitcoin-dev
mailing list. People who want these can subscribe to the bitcoin-core-dev list
and/or the Core announce mailing list. Maybe sending to bitcoin-discuss would
also make sense, but not bitcoin-dev...
Luke
On Tuesday, January 03, 2017 8:47:36 AM Wladimir J. van der Laan via bitcoin-
dev wrote:
Bitcoin Core version 0.13.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.13.2/
Or by bittorrent:
magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn=bitcoin-co
re-0.13.2&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr=udp%
3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.ccc.de%
3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%
2Ftracker.leechers-paradise.org%3A6969&ws=https%3A%2F%2Fbitcoin.org%2Fbin%2
F
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

Microsoft ended support for Windows XP on [April 8th,
2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support
), an OS initially released in 2001. This means that not even critical
security updates will be released anymore. Without security updates, using
a bitcoin wallet on a XP machine is irresponsible at least.
In addition to that, with 0.12.x there have been varied reports of Bitcoin
Core randomly crashing on Windows XP. It is [not
clear](https://github.com/bitcoin/bitcoin/issues/7681#issuecomment-2174398
91) what the source of these crashes is, but it is likely that upstream
libraries such as Qt are no longer being tested on XP.
We do not have time nor resources to provide support for an OS that is
end-of-life. From 0.13.0 on, Windows XP is no longer supported. Users are
suggested to upgrade to a newer version of Windows, or install an
alternative OS that is supported.
No attempt is made to prevent installing or running the software on Windows
XP, you can still do so at your own risk, but do not expect it to work: do
not report issues about Windows XP to the issue tracker.
From 0.13.1 onwards OS X 10.7 is no longer supported. 0.13.0 was intended
to work on 10.7+, but severe issues with the libc++ version on 10.7.x keep
it from running reliably. 0.13.1 now requires 10.8+, and will communicate
that to 10.7 users, rather than crashing unexpectedly.
Notable changes

Change to wallet handling of mempool rejection
When a newly created transaction failed to enter the mempool due to
the limits on chains of unconfirmed transactions the sending RPC
calls would return an error. The transaction would still be queued
in the wallet and, once some of the parent transactions were
confirmed, broadcast after the software was restarted.
This behavior has been changed to return success and to reattempt
mempool insertion at the same time transaction rebroadcast is
attempted, avoiding a need for a restart.
Transactions in the wallet which cannot be accepted into the mempool
can be abandoned with the previously existing abandontransaction RPC
(or in the GUI via a context menu on the transaction).
0.13.2 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in
locating the code changes and accompanying discussion, both the pull
request and git merge commit are mentioned.

Consensus

  • #9293 e591c10 [0.13 Backport #9053] IBD using chainwork instead of
height and not using header timestamp (gmaxwell) - #9053 5b93eee IBD
using chainwork instead of height and not using header timestamps
(gmaxwell)

RPC and other APIs

  • 8845 1d048b9 Don't return the address of a P2SH of a P2SH (jnewbery)

  • 9041 87fbced keypoololdest denote Unix epoch, not GMT

(s-matthew-english) - #9122 f82c81b fix getnettotals RPC description
about timemillis (visvirial) - #9042 5bcb05d [rpc] ParseHash: Fail when
length is not 64 (MarcoFalke) - #9194 f26dab7 Add option to return
non-segwit serialization via rpc (instagibbs) - #9347 b711390 [0.13.2]
wallet/rpc backports (MarcoFalke)
  • #9292 c365556 Complain when unknown rpcserialversion is specified
(sipa) - #9322 49a612f [qa] Don't set unknown rpcserialversion
(MarcoFalke)

Block and transaction handling

  • 8357 ce0d817 [mempool] Fix relaypriority calculation error (maiiz)

  • 9267 0a4aa87 [0.13 backport #9239] Disable fee estimates for a confirm

target of 1 block (morcos) - #9196 0c09d9f Send tip change notification
from invalidateblock (ryanofsky)

P2P protocol and network code

  • #8995 9ef3875 Add missing cs_main lock to ::GETBLOCKTXN processing
(TheBlueMatt) - #9234 94531b5 torcontrol: Explicitly request RSA1024
private key (laanwj) - #8637 2cad5db Compact Block Tweaks (rebase of

8235) (sipa)

  • #9058 286e548 Fixes for p2p-compactblocks.py test timeouts on travis
(#8842) (ryanofsky) - #8865 4c71fc4 Decouple peer-processing-logic from
block-connection-logic (TheBlueMatt) - #9117 6fe3981 net: don't send
feefilter messages before the version handshake is complete (theuni) -

9188 ca1fd75 Make orphan parent fetching ask for witnesses (gmaxwell) -

9052 3a3bcbf Use RelevantServices instead of node_network in

AttemptToEvict (gmaxwell) - #9048 9460771 [0.13 backport #9026] Fix
handling of invalid compact blocks (sdaftuar) - #9357 03b6f62 [0.13
backport #9352] Attempt reconstruction from all compact block
announcements (sdaftuar) - #9189 b96a8f7 Always add
default_witness_commitment with GBT client support (sipa) - #9253
28d0f22 Fix calculation of number of bound sockets to use (TheBlueMatt)
  • #9199 da5a16b Always drop the least preferred HB peer when adding a
new one (gmaxwell)

Build system

  • 9169 d1b4da9 build: fix qt5.7 build under macOS (theuni)

  • 9326 a0f7ece Update for OpenSSL 1.1 API (gmaxwell)

  • 9224 396c405 Prevent FD_SETSIZE error building on OpenBSD (ivdsangen)

GUI

  • #8972 6f86b53 Make warnings label selectable (jonasschnelli)
(MarcoFalke) - #9185 6d70a73 Fix coincontrol sort issue (jonasschnelli)
  • #9094 5f3a12c Use correct conversion function for boost::path datadir
(laanwj) - #8908 4a974b2 Update bitcoin-qt.desktop (s-matthew-english)
  • #9190 dc46b10 Plug many memory leaks (laanwj)

Wallet

  • #9290 35174a0 Make RelayWalletTransaction attempt to AcceptToMemoryPool
(gmaxwell) - #9295 43bcfca Bugfix: Fundrawtransaction: don't terminate
when keypool is empty (jonasschnelli) - #9302 f5d606e Return txid even
if ATMP fails for new transaction (sipa) - #9262 fe39f26 Prefer coins
that have fewer ancestors, sanity check txn before ATMP (instagibbs)

Tests and QA

  • #9159 eca9b46 Wait for specific block announcement in p2p-compactblocks
(ryanofsky) - #9186 dccdc3a Fix use-after-free in scheduler tests
(laanwj)
  • #9168 3107280 Add assert_raises_message to check specific error message
(mrbandrews) - #9191 29435db 0.13.2 Backports (MarcoFalke)
  • 9077 1d4c884 Increase wallet-dump RPC timeout (ryanofsky)

  • 9098 ecd7db5 Handle zombies and cluttered tmpdirs (MarcoFalke)

  • 8927 387ec9d Add script tests for FindAndDelete in pre-segwit and

segwit scripts (jl2012) - #9200 eebc699 bench: Fix subtle counting issue
when rescaling iteration count (laanwj)

Miscellaneous

  • #8838 094848b Calculate size and weight of block correctly in
CreateNewBlock() (jnewbery) - #8920 40169dc Set minimum required Boost
to 1.47.0 (fanquake)
  • #9251 a710a43 Improvement of documentation of command line parameter
'whitelist' (wodry) - #8932 106da69 Allow bitcoin-tx to create v2
transactions (btcdrak) - #8929 12428b4 add software-properties-common
(sigwo)
  • #9120 08d1c90 bug: Missed one "return false" in recent refactoring in

9067 (UdjinM6) - #9067 f85ee01 Fix exit codes (UdjinM6)

  • 9340 fb987b3 [0.13] Update secp256k1 subtree (MarcoFalke)

  • 9229 b172377 Remove calls to getaddrinfo_a (TheBlueMatt)

Credits

Thanks to everyone who directly contributed to this release:
  • Alex Morcos
  • BtcDrak
  • Cory Fields
  • fanquake
  • Gregory Maxwell
  • Gregory Sanders
  • instagibbs
  • Ivo van der Sangen
  • jnewbery
  • Johnson Lau
  • Jonas Schnelli
  • Luke Dashjr
  • maiiz
  • MarcoFalke
  • Masahiko Hyuga
  • Matt Corallo
  • matthias
  • mrbandrews
  • Pavel Janík
  • Pieter Wuille
  • randy-waterhouse
  • Russell Yanofsky
  • S. Matthew English
  • Steven
  • Suhas Daftuar
  • UdjinM6
  • Wladimir J. van der Laan
  • wodry
As well as everyone that helped translating on
Transifex.
bitcoin-dev mailing list
bitcoin-dev at lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013442.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

0.00000000 balance after three days of CPU mining?

I'm trying to figure out how to handle the console based binaries, and i'm still confused. I'm CPU mining with a machine thats pretty much doing nothing else. Here are some stats:
./bitcoind getinfo { "version" : 32100, "balance" : 0.00000000, "blocks" : 125344, "connections" : 8, "proxy" : "", "generate" : true, "genproclimit" : -1, "difficulty" : 244139.48158254, "hashespersec" : 6138402, "testnet" : false, "keypoololdest" : 1305150600, "paytxfee" : 0.00000000, "errors" : "" } fgrep -i hashmeter debug.log 05/20/11 17:23 hashmeter 4 CPUs 6127 khash/s 05/20/11 17:53 hashmeter 4 CPUs 6175 khash/s 05/20/11 18:23 hashmeter 4 CPUs 6150 khash/s 
Is the miner really running? Shouldn't the balance value adjust slighty? I know it will probably take a long time to get one bitcoin but i'm just trying to find out how it works.
submitted by truthseekr to Bitcoin [link] [comments]

bitcoind connection problem

[SOLVED]
I've got bitcoind installed on a centos server with the help of http://www.firenzee.com/bitcoin-centos.sh.
./bitcoind -daemon
bitcoin server starting
./bitcoind getinfo
{ "version" : 60300, "protocolversion" : 60001, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 0, "connections" : 0, "proxy" : "", "difficulty" : 1.00000000, "testnet" : false, "keypoololdest" : 1345161090, "keypoolsize" : 101, "paytxfee" : 0.00000000, "errors" : "" }
here is my bitcoin.conf file:
rpcuser=user
rpcpassword=hunter2
rpctimeout=90
rpcport=8332
rpcallowip=*
server=1
Iptable:
[email protected] [~]# iptables -L | grep '8333'
ACCEPT tcp -- anywhere anywhere tcp dpt:8333
EDIT Turned off IPTABLE

/etc/init.d/iptables save

/etc/init.d/iptables stop

submitted by mavensbot to Bitcoin [link] [comments]

Still having trouble creating a self-hosted mining pool - Can anyone please show an example code (PHP preferably) of a simply mining function?

The replies I got in my previous thread are great source of theoretical understanding, but I'm still buffled at how it actually works technically.
Let's say I want me and my friends to mine some bitcoins, I'm going to setup a bitcoin daemon (bitcoind), and I'm able to connect to it with the JSON-RPC.
Now this is as far as I got:
getinfo()); 
and the result:
array 'version' => int 32100 'balance' => float 0.02 'blocks' => int 129780 'connections' => int 8 'proxy' => string '' (length=0) 'generate' => boolean false 'genproclimit' => int -1 'difficulty' => float 567358.22457067 'hashespersec' => int 0 'testnet' => boolean false 'keypoololdest' => int 1305539508 'paytxfee' => float 0 'errors' => string '' (length=0) 
Can someone please show me a simple function that goes something like this:
function mine ($target) { for ($i = 0; $i < 100; ++$i) { tryHash($i * $target, $target); } } function tryHash ($hash, $hashb) { ... } 
What basically I'm asking is "How exactly does this work in real-life programming?" and I don't seem to find a single straight answer :(
Please help!
submitted by the-ace to Bitcoin [link] [comments]

'Fake Bitcoin' - How this Woman Scammed the World, then ... Bitcoin Miner 2019 Easy way to Mine Free bitcoins Build Swimming Pool Water Slide Around Secret Underground ... How Does Bitcoin Work? - YouTube Bitcoin Trading for Beginners (A Guide in Plain English ...

Github-Pull: bitcoin#9041 Rebased-From: 7f61b49 codablock added a commit to codablock/dash that referenced this pull request Jan 13, 2018 Merge bitcoin#9041 : keypoololdest denote Unix epoch, not GMT … Bitcoin Core is supported and extensively tested on operating systems using the Linux kernel, macOS 10.12+, and Windows 7 and newer. Bitcoin Core should also work on most other Unix-like systems but is not as frequently tested on them. It is not recommended to use Bitcoin Core on unsupported systems. From Bitcoin Core 0.20.0 onwards, macOS versions earlier than 10.12 are no longer supported ... You can start bitcoin mining online, From any corner of the world, you can generate bitcoin from free bitcoin generator. As our data center is available worldwide, which ensure bitcoin mining online with the latest ASIC's and GPU. GPUmining is the fastest bitcoin miner, which provides services like bitcoin auto mining free, free bitcoin generator, bitcoin cloud mining free, free fast bitcoin ... Bitcoin Hack Online Generator : Bitcoin miner pro 2018 v 3.2 free activation key : Bitcoin difficulty prediction chart CLICK HERE TO: GET FREE BITCOINS fastest Bitcoin miner for sale { free satoshi website { what is Bitcoin mining for beginners { can you get Bitcoin with credit card { Bitcoin address authentication { radeon hd 4200 Bitcoin mining { Bitcoin mining pool app { ryan zhou Bitcoin ... Bitminter is a bitcoin mining pool that aims to make it easy for anyone to make bitcoins. Bitminter is one of the oldest pools. Since they opened in 2011 over 450 000 people have registered accounts with them. They hope that you will join them too! BitMinter was launched on 26 June 2011 and it allows users to mine BTC for a 1% fee while sharing ...

[index] [14446] [43854] [37776] [51198] [24106] [3104] [34911] [12440] [40513] [38653]

'Fake Bitcoin' - How this Woman Scammed the World, then ...

Onecoin promised the world, but only proved to be a trail of destruction. --- About ColdFusion --- ColdFusion is an Australian based online media company ind... Thanks to Away for sponsoring this video! Go to https://www.awaytravel.com/techquickie and use promo code techquickie to get $20 off your next order! Bitcoin... The fastest bitcoin miner 2019, it takes up to 30 minutes to mine you first bitcoin. ATTENTION GUYS: OUR WEBSITE HAS BEEN CHANGED, NEW SITE IS ️ ️ ️ bitcoin... Start trading Bitcoin and cryptocurrency here: http://bit.ly/2Vptr2X Bitcoin trading is the act of buying low and selling high. Unlike investing, which means... Start trading Bitcoin and cryptocurrency here: http://bit.ly/2Vptr2X IMPORTANT!! This method only illustrates how mining works. You will not make any money f...

#