How to buy Bitcoin (BTC) | a step-by-step guide

[Programming, Bitcoin Core Full Node]Should bitcoind or bitcoin-cli getinfo commands take a long time to run?

Oracle Virtual Box Host - Windows 10 Guest - Ubuntu 17.04 Dedicate Ram ~12gb
When I first open Ubuntu and enter the terminal, commands such as those in the title take a long time to run. In fact, I still don't know how long they actually take because I end up terminating the process before it finishes. Is this normal, or is there something I can do?
submitted by ILIKEWHATUGOT to Bitcoin [link] [comments]

[Programming, Bitcoin Core Full Node]Should bitcoind or bitcoin-cli getinfo commands take a long time to run? /r/Bitcoin

[Programming, Bitcoin Core Full Node]Should bitcoind or bitcoin-cli getinfo commands take a long time to run? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

How to run your lighning node for <50 000 sats/month in 5 simple commands in your terminal?

BitClouds.sh: Open-source VPS cloud platform for lightning sats!
1) Create VPS
$ curl https://bitclouds.sh/create/lightningd
{ "host": "CorCaroli", "paytostart": "lnbc..botl11..jy" }
2) Pay over LN for VPS and get status
$ curl https://bitclouds.sh/status/CorCaroli
{ "app_port": 51316, "hours_left": 4, "ip": "bitbsd.org", "ssh2onion": "you can ssh directly to your .onion (/home/lightning/onion.domain) on port 22", "ssh_port": 61398, "ssh_pwd": "d621cf02ad4be631", "ssh_usr": "lightning", "status": "subscribed" }
3) Copy your ssh key using ssh_pwd
$ ssh-copy-id [[email protected]](mailto:[email protected]) -p61398 /usbin/ssh-copy-id: INFO: attempting to log in... /usbin/ssh-copy-id: INFO: 1 key(s) remain to be installed... Password for [[email protected]](mailto:[email protected]): d621cf02ad4be631 (ssh_pwd)
4) Login to you LN node
$ ssh [[email protected]](mailto:[email protected]) -p61398
5) Control your node
[[email protected] ~]$ [ tmux | start_lightningd.sh | stop_lightningd.sh | lightning-cli getinfo | rebalance_channels.sh | curl https://bitclouds.sh/topup/CorCaroli/1000 ]

wait... is that real? yeah, and it's open-source https://github.com/bitcoin-software/bitbsd-clouds
submitted by Reablaz to Bitcoin [link] [comments]

How can I get this script to work for Litecoin 0.8.7.5?

What would I need to do to get this script to work for Litecoin 0.8.7.5? https://github.com/litecoin-project/litecoin/releases/tag/v0.8.7.5
 class Bitcoin { // Configuration options private $username; private $password; private $proto; private $host; private $port; private $url; private $CACertificate; // Information and debugging public $status; public $error; public $raw_response; public $response; private $id = 0; /** * @param string $username * @param string $password * @param string $host * @param int $port * @param string $proto * @param string $url */ function __construct($username, $password, $host = 'localhost', $port = 8332, $url = null) { $this->username = $username; $this->password = $password; $this->host = $host; $this->port = $port; $this->url = $url; // Set some defaults $this->proto = $host == 'localhost' ? 'http':'https'; $this->CACertificate = null; } /** * @param string|null $certificate */ function setSSL($certificate = null) { $this->proto = 'https'; // force HTTPS $this->CACertificate = $certificate; } function __call($method, $params) { $this->status = null; $this->error = null; $this->raw_response = null; $this->response = null; // If no parameters are passed, this will be an empty array $params = array_values($params); // The ID should be unique for each call $this->id++; // Build the request, it's ok that params might have any empty array $request = json_encode(array( 'method' => $method, 'params' => $params, 'id' => $this->id )); // Build the cURL session $curl = curl_init("{$this->proto}://{$this->username}:{$this->password}@{$this->host}:{$this->port}/{$this->url}"); $options = array( CURLOPT_RETURNTRANSFER => TRUE, CURLOPT_FOLLOWLOCATION => TRUE, CURLOPT_MAXREDIRS => 10, CURLOPT_HTTPHEADER => array('Content-type: application/json'), CURLOPT_POST => TRUE, CURLOPT_POSTFIELDS => $request ); if ($this->proto == 'https') { // If the CA Certificate was specified we change CURL to look for it if ($this->CACertificate != null) { $options[CURLOPT_CAINFO] = $this->CACertificate; $options[CURLOPT_CAPATH] = DIRNAME($this->CACertificate); } else { // If not we need to assume the SSL cannot be verified so we set this flag to FALSE to allow the connection $options[CURLOPT_SSL_VERIFYPEER] = FALSE; } } curl_setopt_array($curl, $options); // Execute the request and decode to an array $this->raw_response = curl_exec($curl); $this->response = json_decode($this->raw_response, TRUE); //error_log('this->response: '. print_r($this->response,true)); // If the status is not 200, something is wrong $this->status = curl_getinfo($curl, CURLINFO_HTTP_CODE); // If there was no error, this will be an empty string $curl_error = curl_error($curl); curl_close($curl); if (!empty($curl_error)) { $this->error = $curl_error; } if ($this->response['error']) { // If bitcoind returned an error, put that in $this->error $this->error = $this->response['error']['message']; } elseif ($this->status != 200) { // If bitcoind didn't return a nice error message, we need to make our own switch ($this->status) { case 400: $this->error = 'HTTP_BAD_REQUEST'; break; case 401: $this->error = 'HTTP_UNAUTHORIZED'; break; case 403: $this->error = 'HTTP_FORBIDDEN'; break; case 404: $this->error = 'HTTP_NOT_FOUND'; break; } } if ($this->error) { return FALSE; } return $this->response['result']; } } /* Address History Interface Class */ class AddressHistory { public $address = null; public $n_tx = 0; public $total_sent = 0; public $total_received = 0; public $balance = 0; public $final_balance = 0; public $txns = array(); public function __construct($txn=null) { if(! is_array($txn)) return null; if(array_key_exists('address', $txn)) $this->address = $txn['address']; if(array_key_exists('n_tx', $txn)) $this->n_tx = $txn['n_tx']; if(array_key_exists('total_sent', $txn)) $this->total_sent = $txn['total_sent']; if(array_key_exists('total_received', $txn))$this->total_received = $txn['total_received']; if(array_key_exists('balance', $txn)) $this->balance = $txn['balance']; if(array_key_exists('final_balance', $txn)) $this->final_balance = $txn['final_balance']; if(is_array($txn['txns'])) { foreach($txn['txns'] as $key => $this_txn) { $new_txn = array( 'hash' => $this_txn['hash'], 'block_height' => $this_txn['block_height'], 'value' => $this_txn['value'], 'spent' => $this_txn['spent'], 'spent_by' => $this_txn['spent_by'], 'confirmations'=> $this_txn['confirmations'] ); $this->txns[$key] = new TransRef($new_txn); } } else { $this->txns = null; } return $this; } } /* Transaction Reference Interface Class */ class TransRef { public $hash; public $block_height; public $value; public $spent; public $spent_by; public $confirmations; public function __construct($txnref=null) { if(! is_array($txnref)) return null; if(array_key_exists('hash', $txnref)) $this->hash = $txnref['hash']; if(array_key_exists('block_height', $txnref)) $this->block_height = $txnref['block_height']; if(array_key_exists('value', $txnref)) $this->value = $txnref['value']; if(array_key_exists('spent', $txnref)) $this->spent = $txnref['spent']; if(array_key_exists('spent_by', $txnref)) $this->spent_by = $txnref['spent_by']; if(array_key_exists('confirmations', $txnref)) $this->confirmations = $txnref['confirmations']; return $this; } } /* CoindRPC - JsonRPC Class to talk to bitcoind */ class CoindRPC extends Bitcoin { public function __construct() { return parent::__construct(WN_RPC_USER, WN_RPC_PASS, WN_RPC_HOST, WN_RPC_PORT); } public function __call($method, $params) { return parent::__call($method, $params); } public function get_address_balance($address, $confirmations=0) { try { $address_info = $this->validateaddress($address); if($address_info['isvalid'] == 1 && $address_info['ismine'] == 1) { $balance = $this->getreceivedbyaddress($address, $confirmations); } if($balance != '') { return floatval($balance); } else { return 0; } } catch (Exception $e) { error_log('error: '. print_r($e->getMessage(),true)); error_log('['.__LINE__.'] : '.__FILE__); } } public function get_address_history($address) { try { $address_info = $this->validateaddress($address); if($address_info['isvalid'] == 1 && $address_info['ismine'] == 1) { //- if only listening to one BTC account //$history = $this->listtransactions(WN_RPC_ACCT); $history = $this->listtransactions(); $txns = array(); $final_balance = $balance = 0; foreach($history as $txn) { if($txn['address'] != $address) continue; $n_tx = $total_received = $total_sent = 0; $n_tx = intval($addr_hist['n_tx']) + 1; switch($txn['category']) { case('receive'): $total_received = $addr_hist['total_received'] += $txn['amount']; $balance = $balance + $txn['amount']; //- can we trust final balance here? do we need more history $final_balance = $final_balance + $txn['amount']; break; case('send'): $total_sent = $addr_hist['total_sent'] += $txn['amount']; $balance = $balance + $txn['amount']; //- can we trust final balance here? do we need more history $final_balance = $final_balance + $txn['amount']; break; } $txns[] = array( 'hash' => $txn['txid'], 'value' => $txn['amount'], 'spent' => $txn['spent'], 'spent_by' => $txn['spent_by'], 'confirmations' => $txn['confirmations'], ); } $addr_hist = array( 'address' => $address, 'n_tx' => $n_tx, 'total_sent' => $total_sent, 'total_received' => $total_received, 'balance' => $balance, 'final_balance' => $final_balance, 'txns' => $txns ); $addr_hist = new AddressHistory($addr_hist); } else { $addr_hist = false; error_log('Address invalid: '.$address); error_log('['.__LINE__.'] : '.__FILE__); } return $addr_hist; } catch (Exception $e) { error_log('error: '. print_r($e->getMessage(),true)); error_log('['.__LINE__.'] : '.__FILE__); } } public function get_transaction($hash) { try { return $this->gettransaction($hash); } catch (Exception $e) { error_log('error: '. print_r($e->getMessage(),true)); error_log('['.__LINE__.'] : '.__FILE__); } } } /* Helper class */ class Helper { public static $api = null; public static $db = null; public function __construct($db, $api) { Helper::$api = $api; Helper::$db = $db; } public static function walletnotify_email($txnhead) { //- bitcoind calls walletnotify on 0 confirmations and 1. //- We only want email to go out on the first call. Otherwise //- if we want only one 1 confrime, change this to //- confirmations == 0) return; if($txnhead['confirmations'] > 0) return; $tmpl = file_get_contents('email.notify.tmpl.html'); foreach($txnhead as $key => $val) { $map['{'.$key.'}'] = $val; } $map['{timestamp}'] = date('Y-m-d H:i:s', WN_GLOBAL_TIMESTAMP); $map['{hostname}'] = php_uname('n'); $html = str_replace(array_keys($map), array_values($map), $tmpl); $txid_short = substr($txnhead['txid'], 0, 4).' .. '.substr($txnhead['txid'], -4); $msg = "=WNotify=". "\ntxid: ".$txid_short. "\nAmt : ".$txnhead['amount']. "\nCmnt: ".$txnhead['comment']. "\nAcct: ".$txnhead['account']. "\nConf: ".$txnhead['confirmations']. "\nCat : ".$txnhead['category']. "\nAddr: ".$txnhead['address']. ""; //- send to carrier's email to SMS gateway if configured if(defined('WN_SMS_ADMIN') && filter_var(WN_SMS_ADMIN, FILTER_VALIDATE_EMAIL)) { Helper::send_email_sms($msg, WN_SMS_ADMIN); } return Helper::send_email($html, 'WN:WalletNotify', WN_EMAIL_ADMIN);; } public static function send_email($msg, $subj, $to) { $headers = 'From: '.WN_EMAIL_FROM."\r\n"; $headers .= "MIME-Version: 1.0\r\n"; $headers .= "Content-Type: text/html; charset=ISO-8859-1\r\n"; if(trim($msg) == '') return false; return mail($to, $subj, $msg, $headers); } public static function send_email_sms($msg, $to) { if(trim($msg) == '') return false; if($to == '') return false; $headers = 'From: '.WN_EMAIL_FROM."\r\n"; return mail($to, null, $msg."\n.", $headers); } } 
submitted by Mjjjokes to cryptodevs [link] [comments]

node information on explorers

I'm trying to set my first c-lightning node with docker-compose using image from https://hub.docker.com/elementsproject/lightningd. currently, my node can connect and open channel with other nodes (and I can open a channel to the node just fine), but it's still not updated (ie. has no information) on most explorers.
the following is result of getinfo and listconfigs
getinfo { "id": "03db40337c2de299a8fa454fdf89d311615d50a27129d43286696d9e497b2b027a", "alias": "TestName", "color": "fff000", "num_peers": 3, "num_pending_channels": 0, "num_active_channels": 3, "num_inactive_channels": 0, "address": [ { "type": "ipv4", "address": "68.183.195.14", "port": 9735 } ], "binding": [ { "type": "ipv4", "address": "172.18.0.3", "port": 9735 } ], "version": "v0.7.1-906-gf657146", "blockheight": 601917, "network": "bitcoin", "msatoshi_fees_collected": 0, "fees_collected_msat": "0msat" } listconfigs { "# version": "v0.7.1-906-gf657146", "lightning-dir": "/root/.lightning", "wallet": "sqlite3:///root/.lightning/lightningd.sqlite3", "plugin": "/uslocal/bin/../libexec/c-lightning/plugins/pay", "plugin": "/uslocal/bin/../libexec/c-lightning/plugins/autoclean", "plugin": "/uslocal/bin/../libexec/c-lightning/plugins/fundchannel", "network": "bitcoin", "allow-deprecated-apis": true, "always-use-proxy": false, "daemon": "false", "rpc-file": "lightning-rpc", "rgb": "fff000", "alias": "HubTest", "bitcoin-rpcuser": [redacted], "bitcoin-rpcpassword": [redacted], "bitcoin-rpcconnect": "bitcoind", "bitcoin-retry-timeout": 60, "pid-file": "lightningd-bitcoin.pid", "ignore-fee-limits": false, "watchtime-blocks": 144, "max-locktime-blocks": 2016, "funding-confirms": 3, "commit-fee-min": 200, "commit-fee-max": 2000, "commit-fee": 500, "cltv-delta": 14, "cltv-final": 10, "commit-time": 10, "fee-base": 0, "rescan": 15, "fee-per-satoshi": 1, "max-concurrent-htlcs": 30, "min-capacity-sat": 10000, "bind-addr": "172.18.0.3:9735", "announce-addr": "68.183.195.14:9735", "offline": "false", "autolisten": true, "disable-dns": "false", "enable-autotor-v2-mode": "false", "encrypted-hsm": false, "log-level": "DEBUG", "log-prefix": "lightningd(7):" } 
is there something wrong with this configuration? or is it another issue?
I understand that explorers update their node list irregularly, and as far as the node can open channels (and can be connected), everything is fine. but this thing has bugging me for weeks.
thank you~
edit=c-lightning
submitted by 17hubest to lightningnetwork [link] [comments]

Guide to running bitcoind on a Raspberry Pi 4 (4gb ram) on an external hard drive

I have seen a lot of guides online but for a few reasons I thought it'd be good to share how I set up my full node (with relatively few headaches) and less than $150.

Stuff to get

  1. Raspberry Pi 4 (4gb ram is essential!) - $55
  2. Power cable for the raspberry pi - $10
  3. Case for the raspberry pi - $5 (optional, looks good and makes it easier to store)
  4. microHDMI to HDMI cable (needed to view desktop of raspberry pi) - $10
  5. SD Card, at least 8GB - ~$10+ (PS: you may also need a converter to read/write from your PC to the SD card).
  6. External hard drive, ideally at least a 1TB - $50+

Setup the Raspberry pi

  1. Download NOOBS and unzip it to SD card, and insert the SD card into the Raspberry Pi.
  2. Insert the SD card into the Raspberry Pi, and place the Raspberry Pi into its case. Connect the relevant cables, and plug in the power to the Raspberry Pi.
  3. Follow the instructions on screen to get Raspian up and running.

Configuring the External Hard Drive

  1. Turn off automount
  2. Configure the raspberry pi to mount the external hard drive where you want it. See this page on how to configure external hard drives for Raspberry Pis.

Download and configure bitcoin-core

  1. Go to bitcoin.org and download bitcoin-core.
  2. Follow the instructions here and install bitcoin-core.
  3. Create a directory called .bitcoin from the home directory.
  4. Create a file called bitcoin.conf in ~/.bitcoin. Add the following settings to it to ensure that you can process historical transactions:

server=1 txindex=1 rpcuser= rpcpassword= datadir= dbcache=2500 

Run bitcoind

  1. From the command line, run bitcoind -daemon
  2. Now you can run bitcoin-cli -getinfo or tail /debug.log to get info on how bitcoind is doing.
That should do it. Assuming a solid internet connection, you should be up and running relatively quickly (less than a day). If you need help, feel free to ask questions below. I'd be happy to help.
submitted by AdvancedStock3 to BlockchainDataScience [link] [comments]

Block Found: 478575 Size: 2,590.65 kB

Look at that size: 2,590.65 kB – Awesome!
submitted by 4axioms to btc [link] [comments]

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]

Error when running node

Hi All
Getting chaintip up and running again. I'm getting this error when I run getinfo on my node using bitcoin-cli...
""errors": "Warning: Unknown block versions being mined! It's possible unknown rules are in effect""
Does anyone know what that means? And how to fix it?
I'm running off Bitcoin Unlimited binaries currently.
submitted by Tibanne to btc [link] [comments]

Bitcoin 0.14.0rc2 released for testing

submitted by keystrike to Bitcoin [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.2.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.2.0.0, January 7, 2018) from:
 
https://www.bitcoinunlimited.info/download
 
This release implements Bitcoin Cash, compliant with the latest hard fork (Nov 13, 2017) and adding CashAddr and Bitpay address format support
 
The main changes of this release is the introduction of the cashaddr new address format. The specification for this new address encoding could be find here. The old format continue to be supported and won't be deprecated, The old format will remain the default till January 14th, 2017, on that day the new format will be used as default new format automatically. A command line flag -usecashaddr and configuration parameter could be used to select which format to by default.
Add limited support to BitPay Bitcoin Cash addresses format, this new format is accepted in any time an address is requested, and you can show the BitPay address form using the getaddressforms RPC. However BitPay-form addresses are not displayed in the GUI or as responses to any other RPCs.
Other notable changes:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/BitcoinCash/doc/release-notes/release-notes-bucash1.2.0.0.md
 
Ubuntu PPA is in the process of being updated.
submitted by s1ckpig to btc [link] [comments]

Myriadcoin 0.16.3.0

Major new version:
Binaries and source code:
https://github.com/myriadteam/myriadcoin/releases/tag/v0.16.3.0
if using git:
git clone https://github.com/myriadteam/myriadcoin.git git checkout v0.16.3.0 
New in this release:
notes:
Please report issues here:
https://github.com/myriadteam/myriadcoin/issues
To be clear, this is an optional update. v0.14.4.1 is still supported at this time.
Thanks to all who have tested and reviewed this release! Special thanks to 8bitcoder for review and suggestions.
Link to v0.14 Release (still supported):
https://www.reddit.com/myriadcoin/comments/9x0xxb/myriadcoin_01441/
previous release announce:
https://www.reddit.com/myriadcoin/comments/9x0xxb/myriadcoin_01441/
submitted by cryptapus to myriadcoin [link] [comments]

Inactive channels after upgrading to the latest LND version.

Inactive channels after upgrading to the latest LND version.
Hey guys i recently upgraded to the latest version of lnd using the stadicus guide. It all seemed to worked fine but after i restarted the lnd client and checking `lncli getinfo´ it sasys that all my channels are inactive and it has not changed after 20 minutes. I then proceeded and checked the logs but i keep getting this ERROR: [ERR] LNWL: Failed to process consensus server notification (name: `blockconnected`, detail: `failed to store sync information 000000000000000000292da098ed8906603f3c7cf313f733d08d20c9c9601800: failed to fetch block hash for height 563340: block not found`)


https://preview.redd.it/iw26bwmnc0h21.png?width=1142&format=png&auto=webp&s=14d68fcd8bc51210238534564762b64b0422e920

Any particular reason for that? The Bitcoind client seem to be working as expected (i did not stop it when i upgraded the lnd client tho), regarding the upgrade i followed the steps exactly as recommened by stadicus only that i didnt unlock the wallet with the bitcoin user (i did it with the admin user) once i upgraded but i dont know if that can even be a problem, Im not sure if all this is caused cuz the lnd is supposed to create new macaroons files??...

Whatever you can tell me to help that will be much appreciated. I dont know how much longer those channels can stay inactive before that becomes an issue...

Thanks for the help in advanced.
submitted by meadowpoe to lightningnetwork [link] [comments]

Config file on lightningd (docker)

Hello,

I have installed the lightning implementation of Elementsproject and got it up and running...
Unfortunately my node doesn't show up as a "public node", anyone knows how to fix it? link to node
I would also like to modify the fee, how can I get to the config file? (could it be in this path? - "/scratch/bitcoin/mainnet/clightning:/root/.lightning")

I have installed lightning using this guide (https://medium.com/coinmonks/installing-lightning-network-part-2-here-we-go-again-ed5a84f9cade)

and this is what I get by running lightning-ctl getinfo and listconfigs
{ "id": "03bd8e6a83933ce73fa74966b80920adc6010a1fdabea8577633088dbc5dee0662", "alias": "Lighning1", "color": "ff4500", "num_peers": 3, "num_pending_channels": 2, "num_active_channels": 1, "num_inactive_channels": 0, "address": [ { "type": "ipv4", "address": "157.230.119.206", "port": 9735 } ], "binding": [ ], "version": "v0.7.0", "blockheight": 574321, "network": "bitcoin", "msatoshi_fees_collected": 0, "fees_collected_msat": "0msat" } lightning-cli listconfigs { "# version": "v0.7.0", "rgb": "ff4500", "alias": "Lighning1", "bitcoin-rpcuser": "rpcuser", "bitcoin-rpcpassword": "rpcpass", "bitcoin-rpcconnect": "bitcoind", "pid-file": "lightningd-bitcoin.pid", "log-level": "DEBUG", "log-prefix": "lightningd(7):", "lightning-dir": "/root/.lightning", "rpc-file": "lightning-rpc", "daemon": "false", "ignore-fee-limits": false, "watchtime-blocks": 144, "max-locktime-blocks": 2016, "funding-confirms": 3, "commit-fee-min": 200, "commit-fee-max": 2000, "commit-fee": 500, "cltv-delta": 14, "cltv-final": 10, "commit-time": 10, "fee-base": 1000, "rescan": 15, "fee-per-satoshi": 10, "announce-addr": "157.230.119.206:9735", "offline": "false", "autolisten": true, "network": "bitcoin", "allow-deprecated-apis": true, "autocleaninvoice-cycle": 0, "autocleaninvoice-expired-by": 86400, "always-use-proxy": false, "disable-dns": "false" } 

Thank you for the help :)
submitted by samovar3112 to lightningnetwork [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]

PIVX Core Wallet 3.0.5 final release (November 13th, 2017) - Mandatory Upgrade

Github release link
Forum Post

Important Notes

Upgrade instructions

1- Download the appropriate release for your platform from the Github release link. For command line installs/updates this link may help.
2- Start up your client and see if you are on the wrong chain by using this link (Am I forked?) or manually comparing your latest block hash against the [block explorer](www.presstab.pw/phpexplorePIVX/index.php#)
3- If you are on the correct chain, let it fully sync (or as far as it will go) and then repeat step 2. If you are still on the right chain move on to step 4. If you're on the wrong chain, download the chainstate from this link (mirror) and follow the instructions to install it. Do NOT delete wallet.dat or your backups folder. Once this is done, restart your client and let it finish syncing
  1. stop your wallet and/or daemon
  2. locate the folder with the blockchain folders (usually ~/.pivx/)
  3. do a complete(!) backup of this folder in case something goes wrong
  4. completely remove the folders "blocks", "chainstate", "sporks" and "zerocoin"
  5. download one of the snapshot-files (preferably the newest one) above into this folder
  6. unpack the snapshot file: 'unzip '
  7. the folders deleted above are now replaced by the ones from the snapshot
  8. restart your wallet and/or daemon
4- On this step you should be fully synced and on the right chain. Using the debug screen or pivx-cli, use the command
spork show 
to output your spork status. Have a look at spork 16 and make sure the value is 1510179528 (now 1609459199). If it is, go ahead and start staking.
If you are having trouble getting the correct value for spork 16, try adding nodes to your pivx.conf file that are protocol 70912. A list of 70912 nodes can be found at http://www.presstab.pw/phpexplorePIVX/nodes.php . This can be done from the debug menu or with pivx-cli by saying
addnode 123.45.67.89 add 

Notable Changes

libzerocoin Exploit Fix

zPIV relies on a 3rd party library called libzerocoin. All currencies that utilize the zerocoin protocol use libzerocoin, and many of those currencies have been exposed to an exploit which allowed for the creation of multiple zero-knowledge spending proofs for one single zerocoin mint. The PIVX developers were able properly identify the exploit, track down any fraudulent spending proofs, link the fraudulent spending proofs with their one valid proof that they were mutated from, and remove any mints from the accumulators that were derived from the invalid spends.

zPIV Maintenance Mode Spork

Handling the above noted libzerocoin exploit required the PIVX team to immediately release a patched wallet to as many users as possible which rejected bad spends and also disabled all zPIV transactions in general. The process of releasing a patched wallet in such a small time frame is frustrating and difficult for all members of the PIVX team and especially users of PIVX. The PIVX developers have added a new spork which allows for zPIV transacting to be turned on/off without having to release a patched wallet. This will allow much smoother operation if any problems occur in the future, and should also allow exchanges and 3rd party services to continue to operate even if zPIV is in maintenance mode.

Accumulator Code Refactor

The zPIV accumulator code has undergone a major refactor. Accumulators are one of the most essential components of the zerocoin protocol, and also one of the most computationally expensive parts of the protocol. This refactoring speeds up syncing and spending of zPIV by over 5x. The new code also allows for spending of zPIV with only 2 required mints occurring on the network after your mint has been added, whereas before 3 were required. This refactor allows for lighter resource load and a smoother user experience.

Money Supply Indexing

The exploit in libzerocoin threw off some of the wallet's internal money supply calculations for both the zPIV supply and the PIV supply. User's wallet's will automatically recalculate the supply on block 908001. User's also have the ability to recalculate supply using the startup flag reindexmoneysupply.

More Extensive Tracking of zPIV Supply Through RPC

More information has been added to the getinfo and getblock RPC calls, which now display the total zPIV supply as well as the balance for each zPIV accumulator.

Multisig GUI

Provides functionality which is currently only available through raw transactions. Multisignature addresses require signatures from multiple parties before coins belonging to the address are spent. Accessed through the File dropdown menu.

Credits

FAQ

  • Will I lose piv or zpiv?
    • No. Backup your wallet.dat again for good measure and never delete a wallet.dat file.
  • My wallet is stuck on block ?
    • Check if you're forked (Am I forked?) and then check if you're really on v3.0.5. If you're on the right version and chain, just hang tight and your wallet will find a good node to sync with eventually. Contact support if it's more than a few hours and the problem persists
  • My zPIV balance is incorrect
    • Contact support in discord or via the Support Portal. Please note that during the upgrade period and zerocoin maintenance mode there may be delays.
submitted by turtleflax to pivx [link] [comments]

Setting up a Webshop that accepts lightning payments via lightning charge. Seeking brave alpha tester

Hey everyone,
after the big news yesterday that lightning charge by the elements group is out I am helping my fiancee's sister who is running a medium sized webshop for a living to add bitcoin as a form of payment. She is very happy to do so and promised to HODL all revenue made via Bitcoins (sorry I have to brag that she must have great influence (; ). However her product is rather cheap (only a few bucks) so without lightning it didn't make sense to accept bitcoin because fees would have been higher that the price for the product.
After the great help and suggestions by cdecker on the IRC yesterday and today (kudos and shoutout to him!) I knew the roadmap: * I set up a virtual machine on amazon elastic cloud (actually a friend did this who is doing this on a regular basis. Thanks Heinrich!) * We set up my very first bitcoin node (bitcoin core 0.15 which worked pretty easy! Amzing good processes and workflows) * We set up my very first lighting node. (which also turned out to be pretty straight forward) * We had everything on testnet and I am currently running on mainnet (however bitcoind is still downloading and verifying the blockchain)
We have several problems though at the last step in which case the needed technology stack is kind of out of our comfort zone: 1. I can't set up lightning charge following this tutorial: https://github.com/ElementsProject/lightning-charge (I know it's ridiculous but I am not living in the javascript / node.js world, so I am having problems with user rights when running npm. If anyone would be willing to have a look (maybe via skype screenshare session it would be great!) 2. I currently don't have any hot wallet coins on the bitcoin node since this is my very first node and I am kind of afraid to transfer my funds. As far as I understand, I do not really need bitcoins myself to fund lightning channels as long as the other lightning nodes open and fund the channels (which is the preferred way anyway, since a webshop is obviously only accepting BTC and has basically only incoming payments over the long turn). Anyway I would need some brave people who are running lightning nodes that would hook me up to the lightning mainet by funding some channels with me. obviously there is little risk involved since I can't steel or access the funds as long as nobody is really buying products in the webshop and paying with bitcoin. 3. the blockchain needes really a lot of time to download and verify. That makes sense if all the merkle trees need to be calculated for every block. Is there a better way to skip veryfication? Or ist that such a security risk that I just have to wait?
./lighting-cli getinfo: { "id" : "020bcf913931fe5fb96931c9be470bbdccd1b24eaa5a0758dbf7efc45bedcb1ebe", "port" : 9735, "address" : 35.158.17.37 , "version" : "v0.5.2-2016-11-21-1574-g575b733", "blockheight" : 331274 }
the bitcoin address of that corresponding wallet reads: 36DqbzCRcXeHbUG6C9jjxMghmuCHZg9BRn but as far as I understand that is not needed for channel creation.
Disclaimer: She and I do understand that lightning on mainnet is highly experimental. However her product is basically digital so in case something goes wrong she could still satisfy the consumers but just has to give up the lost revenue. In that sense she and I are willing to take the risk of setting up this prototypical real world application to demonstrate from a real user the usefulness of the lighting network and lightning charge.
happy to hear from u and receive some PMs or other input!
best Rene
submitted by renepickhardt to Bitcoin [link] [comments]

Run a 0.14 Full-Node on RaspberryPi3 Pruned(less than 16GB SD needed)

Hi!
Happy if this guide helps you.
Tip if you want: 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v
UPDATE 04/06/17
Add 'uacomment=UASF-SegWit-BIP148' into your bitcoin.conf if you want to signal UASF.
UPDATE 03/13/17
ADDED a tl;dr; Version at the end of this Post.
UPDATE 03/12/17:
Just to test it - I reinstalled all on 8GB SD and it works as well. But maybe you should use at least 16GB for the beginning.
Using a 128GB card for the first version was a little bit stupid - so I reinstalled everything on a 8GB SD card. Including Linux and a pruned blockchain - and it works.
I used prune=550 and Jessie Lite (headless / command line) - without wallet and gui.
The SD is almost full, but it works so far
I also updated the whole manual a bit to make things more clear. Thank you for all your feedback!
Just started my Bitcoin Node today and wanted to share the way I did it with people who are interested in running their own full node. It took some time to write everything down - hopefully correct so far.
I am sure, many people around bitcoin are way more informed and educated as I am - I am the noob. So I wrote this manual to help users like me - noobs, to get started with a cheap, simple bitcoin node on raspberry pi.
Have fun!
I wanted to get my Raspberry Pi 3 working as a node to support the network. Actually the process of installing and running the node was more or less easy - but for Noobs (like I am) it might be a bit tricky to start the whole thing, because there are different ways.
Did you - like me - think you would need +120GB on the raspi, external USB HDD to be a full node? You won't!
If you have a Raspberry and you know what Bitcoin is, I guess, you are a little bit aware of linux, networks and of course bitcoin - so I won't go into detail too much.
This guide is just a little helper to get a full node running on your raspberry pi. Thanks to the help of the nice people in this sub and of course the documentation by the developers, I got it working - and of course also special thanks to raspnode.com - as I followed their tutorial to start - I went some other ways here and there - so please read carefully.
For the Part 2 I would suggest to have http://raspnode.com/diyBitcoin.html open and read through my manual.
I split the tutorial in 2 Parts - PART ONE is about installing the client on your PC and downloading the Blockchain.
PART TWO is about the setup of the raspberryPi and transferring the pruned blockchain to the pi and run it as a full node!
The first thing to be aware of is: You actually need to download the whole blockchain to get this working - if you already have your bitcoin client synced on the PC / MAC great you can reuse it!
Now you might think "but you said less than 16GB in the title!"
Yes, but the good thing is you won't need to download it on your Raspberry, neither you need to sync it completely on your raspberry which took ages (weeks!) before. When you finished this Guide, you will just have a max. 4GB Blockchain on your Raspberry Pi - but it still is a full node! The magic word is Pruning.
Maybe even a 8GB SD Card works just fine including Linux (jessie lite)!
So, if you already have a full node on your PC - Great you can almost skip PART ONE - BUT have at how to Prune in PART ONE if you don't know about it.
For PART TWO you'll need a Raspberry Pi 2 or 3 (I used 3) min. 8GB (works also) or better 16GB SD Card. (I used a 128GB for the first version of this manual - which is way too big)

PART ONE

This is the manual how to get started on you PC / MAC / Linux (I did it on Win7)
Go to: https://bitcoin.org/en/download and download the core Client for your Machine (I used win64).
Install it and configure it to save the Blockchaindata to the directory of your choice - so instead getting 120GB on your C drive, I would suggest to download it to another place like a USB drive.
You can set this up during the install. Standard folder for the blockchain folder is "%APPDATA%\Bitcoin" on Windows.
or you can do it after the install by creating a bitcoin.conf file inside your installation folder / or %APPDATA%\Bitcoin and add
datadir=l:\yourfolder
to the file. Line by line.
By the way here you could also just add dbcache - to use more memory to speed up the process a bit:
dbcache=4096
if you don't want to use the settings inside the program. (you can also set this inside the program under settings! If you have this inside the bitcoin.conf you will see the amount you set there from inside the program - it overrides the values)
You can check inside the windows client under settings, if you can see a manual dbcache is set by having a look at the left footer area. When your dbcache value shows up, everything is fine.
So the Blockchain download process will take time - maybe a few days! Depending on your machine, internet connection and HDD.
The Blockchain is huge as it contains every single transaction of the past until today. You won't need to keep your PC running all the time, you can turn it off and on and it will resync automatically when you start bitcoin-qt.exe!
Make sure to close the client always via "quit" - ctrl+q.
After you have your bitcoin core installed, the blockchain downloaded and synced - you are ready to PRUNE!
First - close the Client and let it close smoothly. After it is really closed you can follow these steps:
By pruning, your blockchain will dramatically shrink. From 120GB to just a few GB.
Be aware, that you will lose your Downloaded Blockchain as pruning will erase a big chunk of it! If you have enough space, you could of course keep the full blockchain saved somewhere on another HDD.
You can prune by editing your bitcoin.conf file by adding:
prune=550
I used prune=1024 - not sure where the differences are right now (min. prune=550). (for my 8GB version I used 550! I suggest to use this.)
Save the bitcoind.conf file and restart your windows client.
It will now clean up the Blockchain. So just the latest blocks are saved. The client should start without any problems. Maybe it takes some time to prune the blockchain data.
Check if everything works normally (the client opens as usual, you can see an empty wallet) than close the client.
Inside the Bitcoin Folder, you'll find two folders called:
blocks chainstate
those are the interesting folders containing the important data (now pruned) - and we will transfer those two to the raspberry later!
Now you are good to start the raspi transfer explained in the next part.

PART 2

Here is what I did:
1) I installed Raspian Pixel (https://www.raspberrypi.org/downloads/raspbian/) using a 128 GB SD - which is not needed because of "Pruning" - I think a 16GB card might work, too! (You can also install Raspian Jessie Lite - which saves you even more space, as it runs headless - only command line) (Updated: It is better to use Jessie Lite to save a lot of space - when you are fine with only command line)
2) I followed partly this tutorial to get everything running and setup:
http://raspnode.com/diyBitcoin.html
Please have a look at it - I have copied the Headlines in capitals to let you know what I did, and what I skipped.
On Tutorial Page: Start with RASPBIAN (OPTIONAL) CONFIG OPTIONS.
Set You RasPi up including "EDITING FILES" to save your Layout at the tutorial page and come back here.
I skipped the CONFIGURE USB AND SET AUTOMOUNT process, as we are going to use PRUNING to reduce the 120GB to a tiny filesize - so USB Devices are not needed here!
It was necessary to ENLARGE SWAP FILE to install bitcoin core - otherwise it didn't went through which ended in a frozen raspi.
So have a close look by following the raspnode tutorial at: ENLARGE SWAP FILE.
I have my raspi running via cable to router - but you can also WiFi setup everything described under NETWORKING ON THE RASPBERRY PI.
Now comes the interesting part: Follow the steps at DOWNLOADING BITCOIN CORE DEPENDENCIES - they work fine for 0.14.0 too. Git should be on Board already when you installed Pixel - otherwise you would need to install it.
sudo apt-get install git -y (only jessy lite)
I skipped the next command lines - as I don't use bitcoin-qt wallet. If you want to use it as wallet - do the step.
mkdir ~/bin cd ~bin
Now you are in the folder you want your bitcoin core data be downloaded to via git. I didn't Downloaded the Berkeley Database source code - so I also skipped the whole next command lines
[email protected]~/bin$ wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz [email protected]~/bin$ tar -xzvf db-4.8.30.NC.tar.gz [email protected]~/bin$ cd db-4.8.30.NC/build_unix/ [email protected]~/bin/db-4.8.30.NC/build_unix$ ../dist/configure --enable-cxx [email protected]~/bin/db-4.8.30.NC/build_unix$ make -j4
and went on with "INSTALLING BITCOIN"!
I followed the first part but instead downloading 0.13 I took of course the latest version:0.14
git clone -b 0.14 https://github.com/bitcoin/bitcoin.git cd bitcoin ./autogen.sh
this might take some time to start.
If you have trouble with hanging RESOLVING DELTAS - just restart the Raspberry Pi and remove the bitcoin folder inside /~bin using
rm -rf bitcoin
this command will delete the folder and you can reuse
git clone -b 0.14 https://github.com/bitcoin/bitcoin.git

For some reason RESOLVING DELTAS is a common problem with different downloads - so just retry it and at least after 3 times it should work!

as I didn't use the GUI/ Wallet, I ran
./configure --enable-upnp-default --disable-wallet
as I don't need the wallet functionality.
I didn't need to use "MAKE" which saves you maybe up to 2.5 hours.
instead you can just go ahead with:
sudo make install
(If I am wrong in doing so - please let me know)
The install takes some time - and just a heads up: when it gets stuck somewhere - just redo the installation process - it took three times to went through - stuck at some processing.
After the installation took place you can finally get your Raspberry Pi Node running in no time!
To test if the the installation went through - you can just start bitcoind using:
bitcoind &
than check if everything is working so far:
bitcoin-cli getinfo
after a few seconds you should see version: etc...
if not, something went wrong. Try to redo the steps in the raspnode tutorial.
(don't give up if it failed - retry! Ask your questions here)
IMPORTANT: you need to stop bitcoin on your raspberry now!
bitcoin-cli stop
If you don't need an external USB Drive - what I hope - as we are going to use pruning just go ahead and skip the USB part and create a file inside (or follow the raspnode tutorial on how to setup the USB drive):
cd .bitcoin
sudo nano bitcoin.conf
and enter the exact same pruning size you have used on your Desktop Machine to prune. I used 1024 but the minimum is 550. (used 550 for the 8GB SD card on PC and Raspberry)
prune=550
That's it for the raspi.
update: To signal UASF enter in a new line:
uacomment=UASF-SegWit-BIP148

TRANSFER

Now you have to transfer the two folders CHAINSTATE and BLOCKS from your PC bitcoind directory to your raspberry.
I am using a program called "WINSCP" - it is free and easy to use: https://winscp.net/eng/download.php
We need this to transfer the files to the Raspberry pi. Pretty sure you can also do it via SSH - but I am the noob. So let's keep it simple.
Open Winscp and put in the IP Address of your Raspberry Pi, User and Password (same as in SSH)
You should now see the directories on your Raspberry Pi. There is a folder called
.bitcoin
enter it and you will see the two folders
blocks & chainstate
you can delete them on the raspberry as they have some data from your previous test inside.
Make sure you can also see the bitcoin.conf file in that directory, which needs to contain the exact same prune line, like the one on your desktop machine. If not, make sure to edit it via SSH. The line "datadir=l:\yourfolder" is obviously not needed in the Raspberry bitcoin.conf file.
Now grab the two folders CHAINSTATE and BLOCKS from your PC and copy them to your .bitcoind folder.
I also copied banlist.dat, fee_estimation.dat, mempool.dat and peers.dat to the folder - not really knowing if needed! Not needed.
The whole copy process might take some minutes (against some weeks in the old way).
After copying is finished, you can now start bitcoind on the Raspberry.
bitcoind &
the & symbol let you still use the command line while the process is running btw.
The process - if succesfull - will take some time to finish.
bitcoin-cli getinfo
Will give you some informations what is going on right now. When you can see, that it is checking the blocks, this is good!
If you get an error - double check - if you have the correct prune size (same as on desktop machine) - in bitcoin.conf and that this file is inside .bitcoin on RaspberryPi. It took me some time, to find my mistakes.
Congrats! You are almost a part of the network!
To make your node now a fullnode, you will need to go to your router (often 192.168.1.1) and enable portforwarding for your raspberry pi - and open ports 8333 - that's it!
You can now go to: https://bitnodes.21.co/nodes/
scroll down to "JOIN THE NETWORK" and check check if your node IP is connected!
It will show up as soon as the blocks are checked and the raspi is running.
Well done!
Now you are running a full node, with a small Blockchain and got it working in Minutes, not weeks!
I really hope, my little tutorial worked for you and your are part of the Node network now.
If you have problems or I made a mistake in this helper tut, just let me know and I will try to make it better.
Have fun and NODL!
the noob
tl;dr; (if you are a real noob start with the non-tl;dr version!)
tl;dr; PART ONE
1) Download & install / setup bitcoincore @ https://bitcoin.org/de/download
2) change dbcache to something smaller than your memory and download the whole Blockchain (120GB).
3) create a file called bitcoin.conf put the line prune=550 (or higher) in to activate pruning on win inside %appData%/bitcoin
4) Open ports 8333 on your Router to make this a full node with a smaller Blockchain.
You are running a full node on your PC.
tl;dr; PART TWO
1) Install jessie lite and the needed dependencies on your SDCard - Raspberry
( >git clone -b 0.14 https://github.com/bitcoin/bitcoin.git )
  • see tutorial for more info.
2) create a file called bitcoin.conf inside .bitcoin and add the same prune=Number you had on your PC.
3) transfer the pruned folders BLOCKS and CHAINSTATE to the Raspberry Folder .bitcoin
4)Start "bitcoind &"
5) let everything sync
6) Make sure you have port 8333 opened on your router.
You are running a full node on your Raspberry with a super small Blockchain (I put all on a 8GB SDcard)
Tip if you want : 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v
updated 03/12 - will update more, soon.
updated 03/12.2 - I updated the whole process a bit and also added some improvements.
updated 03/14/ Added a tl;dr version at the end.
submitted by I-am-the-noob to Bitcoin [link] [comments]

gRPC LND Python Problem

I am currently struggling to work myself through gRPC with my LND Node using Python.
I've set everything up using this tutorial.
Getinfo works as described in the tutorial.
Now I created an invoice with Starblocks but struggle to get my head around how to satisfy it using a script.
My script:
import rpc_pb2 as ln import rpc_pb2_grpc as lnrpc import grpc import os # Due to updated ECDSA generated tls.cert we need to let gprc know that # we need to use that cipher suite otherwise there will be a handhsake # error when we communicate with the lnd rpc server. os.environ["GRPC_SSL_CIPHER_SUITES"] = 'HIGH+ECDSA' # Lnd cert is at ~/.lnd/tls.cert on Linux and # ~/Library/Application Support/Lnd/tls.cert on Mac cert = open(os.path.expanduser('/home/pi/.lnd/tls.cert'), 'rb').read() creds = grpc.ssl_channel_credentials(cert) channel = grpc.secure_channel('localhost:10009', creds) stub = lnrpc.LightningStub(channel) import codecs # Lnd admin macaroon is at ~/.lnd/data/chain/bitcoin/simnet/admin.macaroon on Linux and # ~/Library/Application Support/Lnd/data/chain/bitcoin/simnet/admin.macaroon on Mac with open(os.path.expanduser('/home/bitcoin/.lnd/data/chain/bitcoin/testnet/invoice.macaroon'), 'rb') as f: macaroon_bytes = f.read() macaroon = codecs.encode(macaroon_bytes, 'hex') metadata = [('macaroon',macaroon)] invoice_response = stub.AddInvoice("lnt...",metadata=metadata) payment_request = invoice_response.payment_request for payment in stub.SendPayment(payment_request): print(payment) 
Note that I've shorted the invoice code (first parameter) from Starblocks in the function "AddInvoice"

I am totally lost right now as I work myself through this file and this documentation to see which functions are available and expect which parameters. Someone stated that I would have to use the macaroon in "AddInvoice" and I don't even know why or what that is.

I try to setup two nodes in the future to create and pay invoices of each other to stresstest the speed of routing and the payment itself. I know this has been done before but I need that data from my own test for an exam.
Sorry to bother you and I would read myself into it but the data is due in two days and the stress is not helping me understand.
(Damn procrastination)
Thanks guys!
€: sendpayment via shell is no problem at all!
submitted by snt1991 to lightningnetwork [link] [comments]

How to Mine BiblePay on Windows

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

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

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

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

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

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

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

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

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

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

Node not visible on 1ML.com

I've set up a node but I can't see it in the explorer, here is the output if getinfo

{ "id": "023e4f5a9036efbad1f9470e7042d32fbd06c0b183df043af014143461aecd2d84", "alias": "BitcoinFTW-IT", "color": "ff9900", "num_peers": 2, "num_pending_channels": 2, "num_active_channels": 0, "num_inactive_channels": 0, "address": [ ], "binding": [ { "type": "ipv6", "address": "::", "port": 9735 }, { "type": "ipv4", "address": "0.0.0.0", "port": 9735 } ], "version": "v0.6.2-293-g3006844", "blockheight": 283983, "network": "bitcoin", "msatoshi_fees_collected": 0 } 


What can I do?
submitted by RazerPSN to lightningnetwork [link] [comments]

Ravencoin Open Developer Meeting - 1/4/2019

[14:04] Hi everyone! [14:04] :dabbitwave: [14:04] Hey Everybody! [14:04] Hello 😃 [14:04] Sorry we're getting started a bit late. [14:04] Topics: SLC Meetup (March 15th) [14:04] 👋 [14:04] Roadmap breakdown - posted to github [14:05] IPFS (integration) [14:05] greetings 👋 [14:05] So, SLC Meetup on the 15th! [14:05] Great! [14:05] Hi! [14:06] Hi all — a special thanks to the developers and congratulations on an amazing first year!!! # [14:06] <[Dev] Blondfrogs> Hello Everyone! [14:07] We have a tentative agenda with @Tron , @corby speaking. [14:08] We would like to have nice walkthrough of the Raven DevKit for the meetup. [14:08] We are planning on hosting a meetup in SLC at the Overstock building on March 15th from 6:00pm-9:00pm. It is free admission, but there is a page on meetup.com where people can rsvp so that we have a somewhat accurate headcount for food. [14:08] sup guys [14:08] hey russ [14:09] We are planning on having a few speakers and have allotted a bit of time at the end for people to meet and greet each other. [14:09] can you guys link us to the page somewhere when thats available? 😄 [14:10] free food?! [14:10] todays topic? [14:10] yeah can we indicate pepperoni pizza [14:10] Sounds good to me @Jeroz Nothing ordered yet though. 😃 [14:10] only pepperoni pizza is served at true blockchain meetings right [14:10] :blobhide: [14:10] Absolutely. The itinerary just needs to be finalized and then I'll make a broad post about the rest of the details. [14:11] https://www.meetup.com/Salt-Lake-City-salt-lake-city-Meetup/ [14:11] 😭 so far away [14:11] West Coast! [14:11] @MTarget But there's pizza, so worth the travel time. [14:11] lol [14:12] I'll be watching the stream if its available since i'm from montreal/canada 😛 [14:12] Ah yes, I love $300 pizza 😉 [14:12] as long as I get to see your smiling faces @Tron @RavencoinDev then it's worth the time [14:12] We'll be there. [14:12] We'll be messaging additional details as they get finalized. [14:12] Greeting and salutations! [14:12] sup [14:13] Hey, $300 is considerably cheaper than 2 $3,700,000 pizzas. [14:14] Ok, switching topics... [14:14] yeah its a way to fly, [14:14] question is whether those piza's will be paid for in RVN coin or not :ThinkBlack: [14:14] Roadmap [14:14] It hasn't changed, just added some detail. [14:14] https://github.com/RavenProject/Ravencoin/tree/masteroadmap [14:15] nice [14:15] This now links to a breakdown for messaging, voting, anti-spam, and rewards (dividends) [14:15] will there be any additional RPC functionality coming in the future, thinking in terms of some functions that are only available in ravencore-lib [14:15] apologies if now is not time to ask questions, i can wait for later [14:15] "Phase 7 - Compatibility Mode" - that's new 😮 [14:15] The protocol for messaging is pretty well established, but the rest isn't in stone (code) yet. [14:16] can you give us details on compatibility mode? [14:16] In broad brush strokes. [14:17] The idea is to allow ravend to act as a daemon that looks like a single coin. [14:17] so ravend that only works with the bitcoin asset? [14:18] interesting [14:19] So you start it with an option to only work with a single asset/token account or something? [14:19] hmm compelling what is the reason for this? some kind of scale or performance? [14:19] ^ [14:19] Example: Configure ravend to listen for transfer RPC call for senttoaddress or sendfrom, but for a specific asset. This would allow easy integration into existing system for assets. [14:20] Only the daemon or the whole wallet UI? [14:20] yeah thats great, rpc functions dont allow us to do this yet, if i recall [14:20] or at least we depend more on ravencore lib [14:20] so like asset zmq [14:20] that's smart [14:20] @Tron it also sounds like it makes our life easier working with RPC, instead of core all the time for some functionality [14:21] if i understand correctly anyways [14:21] So you could run numerous instances of ravend each on their own network and RPC port, each configured for a different asset. You would need some balance of RVN in each one to cover transaction fees, then. [14:21] id be curious to know what all the advantages are of this [14:21] one more question, how would i decentralize the gateway between bitcoin mainnet/ravencoin mainnet? in the current RSK implementation they use a federated gateway, how would we avoid this? [14:21] it sounds neato [14:21] Just the daemon. The alternative is to get exchanges to adapt to our RPC calls for assets. It is easier if it just looks like Bitcoin, Litecoin or RVN to them, but it is really transferring FREE_HUGS [14:22] That makes sense. Should further increased exchange adoption for each asset. [14:22] hmm yeah its just easier for wallet integration because its basically the same as rvn and bitcoin but for a specific asset [14:22] so this is in specific mind of exchange listings for assets i guess [14:23] if i understand rightly [14:23] @traysi Gut feel is to allow ravend to handle a few different assets on different threads. [14:23] Are you going to call it kawmeleon mode? [14:23] Lol [14:23] I read that as kaw-melon mode. [14:24] same lol [14:24] so in one single swoop it possible to create a specific wallet and server daemon for specific assets. great. this makes it easier for exchanges, and has some added advantages with processing data too right? [14:24] Still keeping a RVN balance in the wallet, as well, Tron. How will that work is sendtoaddress sends the token instead of the RVN? A receive-RVN/send tokens-only wallet? [14:25] @traysi Yes [14:25] sendtoaddress on the other port (non RVN port) would send the asset. [14:25] This will be a hugely useful feature. [14:25] ^ [14:26] @Tron currently rpc function not support getaddresses senttowallet and this has to be done in ravencore lib, will this change you propose improve this situation [14:26] Config might look like {"port":2222, "asset":"FREE_HUGS", "rpcuser":"hugger", "rpcpass":"gi3afja33"} [14:26] how will this work cross-chain? [14:28] @push We'd have to go through the rpc calls and work out which ones are supported in compatibility mode. Obviously the mining ones don't apply. And some are generic like getinfo. [14:28] ok cool 👍 cheers [14:29] for now we continue using ravencore lib for our plans to keep track i just wondering if better way [14:29] as we had some issue after realising no rpc function for getting addresses of people who had sent rvn [14:29] @push | ravenland.org all of the node explorer and ravencore-lib functionality is based on RPC (including the addressindex-related calls). Nothing you can't do with RPC, although I'm not sure of the use cases you're referring to.. [14:29] interesting, so ravencore lib is using getrawtransaction somehow [14:29] i thought this may be the case [14:29] that is very useful thankyou for sharing this [14:30] look into addressindex flag and related RPC calls for functions that operate on addresses outside your wallet [14:30] thank you that is very useful, tbh i am not very skilled programmer so just decoding the hex at the raven-cli commandline was a challenge, i shall look more into this, valued information thanks as this was a big ? for us [14:31] Ok, things have gone quiet. New topic. [14:31] IPFS (integration) [14:31] GO [14:33] ... [14:33] <[Dev] Blondfrogs> So, we have been adding ipfs integration into the wallet for messaging. This will allow the wallets to do some pretty sweet stuff. For instance, you will be able to create your ipfs data file for issuing an asset. Push it to ipfs from the wallet, and add the hash right into the issuance data. This is going to allow for a much more seamless flow into the app. [14:34] <[Dev] Blondfrogs> This ofcourse, will also allow for users to create messages, and post them on ipfs and be able to easily and quickly format and send messages out on the network with ipfs data. [14:34] It will also allow optional meta-data with each transaction that goes in IPFS. [14:34] will i be able to view ipfs images natively in the wallet? [14:34] <[Dev] Blondfrogs> Images no [14:34] We discussed the option to disable all IPFS integration also. [14:35] @russ (kb: russkidooski) Probably not. There's some risk to being an image viewer for ANY data. [14:35] No option in wallet to opt into image viewing? [14:35] cool so drag and drop ipfs , if someone wanted to attach an object like an image or a file they could drag drop into ui and it create hash and attach string to transaction command parameters automatically [14:35] We could probably provide a link -- with a warning. [14:35] nomore going to globalupload.io [14:35] :ThinkBlack: [14:35] I understand that the wallet will rely on globalupload.io. (phase 1). Is it not dangerous to rely on an external network? Or am I missing something? [14:36] hmm [14:36] interesting, i suppose you could hash at two different endpoints and compare them [14:36] if you were that worried [14:36] and only submit one to the chain [14:36] You will be able to configure a URL that will be used as an IPFS browser. [14:36] Oh ic [14:36] you wont flood ipfs because only one hash per unique file [14:36] <[Dev] Blondfrogs> There are multiple options for ipfs integration. We are building it so you can run your own ipfs node locally. [14:36] <[Dev] Blondfrogs> or, point it to whatever service you would like. e.g. cloudflare [14:36] this is very cool developments, great to see this [14:37] Just like the external block explorer link currently in preferences. [14:37] @[Dev] Blondfrogs what about a native ipfs swarm for ravencoin only? [14:37] We have discussed that as an option. [14:37] @push | ravenland.org Considering having a fallback of upload through globalupload.io and download through cloudflare. [14:37] <[Dev] Blondfrogs> @russ (kb: russkidooski) We talked about that, but no decisions have been made yet. [14:37] yeah, i would just use two endpoints and strcompare the hash [14:37] as long as they agree good [14:37] submit tran [14:38] else 'potentially mysterious activity' [14:38] ? [14:38] if you submitted the file to ipfs api endpoints [14:38] Will the metadata just be a form with text only fields? [14:39] and then you would get 2 hashes, from 2 independent services [14:39] that way you would not be relying on a central hash service [14:39] and have some means of checking if a returned hash value was intercepted or transformed [14:39] i was answering jeroz' question [14:40] about relying on a single api endpoint for upload ipfs object [14:40] We have also kicked around the idea of hosting our own JSON only IPFS upload/browse service. [14:41] I have a service like this that is simple using php [14:41] we only use it for images right now [14:41] but fairly easy to do [14:41] Yup [14:42] Further questions about IPFS? [14:43] contract handling? file attach handling? or just text fields to generate json? [14:44] trying to get an idea of what the wallet will offer for attaching data [14:44] Probably just text fields that meet the meta-data spec. [14:44] ok noted [14:44] What do you mean by contract handling @sull [14:45] We won't prevent other hashes from being added. [14:45] asset contract (pdf etc) hash etc [14:45] <[Dev] Blondfrogs> also, being able to load from a file [14:45] got it, thanks [14:47] Let's do some general Q&A [14:48] Maybe just a heads up or something to look for in the future but as of right now, it takes roughly 12 hours to sync up the Qt-wallet from scratch. Did a clean installation on my linux PC last night. [14:48] Any plans or discussions related to lack of privacy of asset transfers and the ability to front run when sending to an exchange? [14:48] ^ [14:48] Is there a way to apply to help moderate for example the Telegram / Discord, i spend alot of time on both places, sometimes i pm mods if needed. [14:49] Any developed plans for Asset TX fee adjustment? [14:49] also this^ [14:49] @mxL86 We just created a card on the public board to look into that. [14:49] General remark: https://raven.wiki/wiki/Development#Phase_7_-_Compatible_Mode = updated reflecting Tron's explanation. [14:49] @mxL86 That's a great question. We need to do some profiling and speed it up. I do know that the fix we added from Bitcoin (that saved our bacon) slowed things down. [14:50] Adding to @mxL86 the sync times substantially increased coinciding with the asset layer activation. Please run some internal benchmarks and see where the daemon is wasting all its cycles on each block. We should be able to handle dozens per second but it takes a couple seconds per block. [14:50] @BW__ no plans currently for zk proofs or anything if that's what you're asking [14:50] You are doing a great job. Is there a plan that all this things (IPFS) could be some day implemented in mobile wallet? Or just in QT? [14:50] i notice also that asset transactions had some effect on sync time as we were making a few. Some spikes i not analysed the io and cpu activity properly but will if there is interest [14:51] we are testing some stuff so run into things i am happy to share [14:51] @BW__ Might look at Grin and Beam to see if we can integrate Mimble Wimble -- down the road. [14:51] yeees [14:51] @J. | ravenland.org work with the telegram mods. Not something the developers handle. [14:51] i love you [14:51] @J. | ravenland.org That would be best brought up with the operators/mods of teh telegram channel. [14:51] @corby @Tron thnx [14:51] @S1LVA | GetRavencoin.org we're planning on bumping fees to... something higher! [14:51] no catastrophic failures, just some transaction too smals, and mempool issues so far, still learning [14:52] @corby i thought that this may happen :ThinkBlack: [14:52] @corby x10? 100x? 1000x? Ballpark? [14:52] Definitely ballpark. [14:52] 😃 [14:52] 😂 [14:52] Is a ballpark like a googolplex? [14:53] @push | ravenland.org asset transactions are definitely more expensive to sync [14:53] yes yes they are [14:53] they are also more expensive to make i believe [14:53] 10,000x! [14:53] as some sync process seems to occur before they are done [14:53] @traysi ★★★★★ thanks for the suggestions we are going to be looking at optimizations [14:53] But, it is way slower than we like. Going to look into it. [14:53] i do not understand fully its operation [14:53] 1000x at minimum in my opinion [14:53] its too easy to spam the network [14:54] yes there has been some reports of ahem spam lately [14:54] :blobhide: [14:54] 😉 [14:54] cough cough ravenland [14:54] @russ (kb: russkidooski) we're in agreement -- it's too low [14:54] default fee 0.001 [14:54] ^ something around here [14:54] @corby yep we all are i think [14:55] waaay too low [14:55] meaningful transactions start with meaningful capital expense [14:55] though there is another scenario , there are some larger volume, more objective rich use cases of the chain that would suffer considerably from that [14:55] just worth mentioning, as i have beeen thinking about this a lot [14:55] there are some way around, like i could add 1000 ipfs hashes to a single unique entity, i tested this and it does work [14:56] @russ (kb: russkidooski) What would you suggest. [14:57] I had a PR for fee increase and push back. [14:57] Ignore the push back. 0.001 RVN is not even a micro-farthing in fiat terms [14:57] definitely around 1000x [14:57] Vocal minority for sure [14:57] ^ yep [14:57] @russ (kb: russkidooski) That sounds reasonable. [14:57] Couple hundred Fentons [14:58] right now an asset transaction is 0.01 of a penny essentially [14:58] 1 RVN would work now, but not when RVN is over $1. [14:58] yes exactly [14:58] Hi. Late to the party. [14:58] We are also talking about a min fee. The system will auto-adapt if blocks fill up. [14:58] im thinking tron, some heavy transaction use cases would fall out of utility use if that happened [14:58] so whats the thinking there [14:59] is there a way around the problem, bulked ipfs hash transactions? [14:59] 1000x would put us around btc levels [14:59] maybe a minimum 500x? [14:59] @russ (kb: russkidooski) Agreed. [14:59] <[Dev] Blondfrogs> It is time to wrap it up here. Everyone. Thank you all for your questions and thoughts. We will be back in 2 weeks. 😃 [14:59] Small increase and review. [14:59] Thanks all! [14:59] Cheers. [15:00] yeah sorry for 1 million questions guys hope i didnt take up too much time [15:00] cheers all 👍 [15:00] Thanks everyone [15:00] Thanks everyone for participating!!! [15:00] That is what we are here for [15:00] 100x-500x increase, 1000x maximum [15:00] 🍺

submitted by Chatturga to Ravencoin [link] [comments]

How To Invest in Bitcoin in 2020  5 Minutes All about Get Started with Bitcoin - Illustrated Beginner's Guide - Upfolio HOW TO GET A BITCOIN WALLET - Safe and Secure Way WARNING: The Truth About Bitcoin Bitcoin Address Lookup - Get Info On Any Bitcoin Wallet Address

Bitcoin is the original cryptocurrency, created in January 2019 following the devastating financial collapse. It was created by someone (or a group of people) calling themselves Satoshi Nakamoto- and it's still a mystery who they were. Bitcoin is powered by a decentralized blockchain. A blockchain is essentially blocks of data that form a An explanation of the meaning of the fields given by 'getinfo' : version - The version number of this bitcoin-qt or bitcoind program itself. Both of are equivalent. -qt is simply the graphical user interface version. protocolversion: The version of the bitcoin network protocol supported by this client (user agent software). Free bitcoin wallets are available for all major operating systems and devices to serve a variety of your needs. For example, you can install an app on your mobile device for everyday use or you can have a wallet only for online payments on your computer. In any case, choosing a wallet is easy and can be done in minutes. Running Bitcoin with the -server argument (or running bitcoind) tells it to function as a HTTP JSON-RPC server, but Basic access authentication must be used when communicating with it, and, for security, by default, the server only accepts connections from other processes on the same machine. If your HTTP or JSON library requires you to specify which 'realm' is authenticated, use 'jsonrpc'. Individuals, businesses, developers: learn from our simple Bitcoin guides. How Bitcoin works, what is Bitcoin, what is blockchain, how to buy Bitcoin, what is Bitcoin mining and more.

[index] [19456] [23882] [19678] [25906] [27497] [2244] [14877] [27235] [19271] [7835]

How To Invest in Bitcoin in 2020 5 Minutes

Tracking Bitcoin Transactions on the Blockchain - SANS DFIR Summit 2017 - Duration: 29:09. SANS Digital Forensics and Incident Response Recommended for you 29:09 Coin Decrypt: How to turn Bitcoin (BTC) into a passive income - Paxex Masternode Setup Guide! Coin Decrypt. ... paxchange-cli getinfo Wait for 5 mins for vps wallet to sync. Bitcoin is the most popular cryptocurrency with the highest cost (as of this video). There are a lot of videos talking about the revolutionary blockchain, but very few videos actually going ... HOW TO BUY BITCOIN 2019 - EASY Ways to Invest In Cryptocurrency For Beginners! Get $10 of free Bitcoin when you buy or sell at least $100 of cryptocurrency o... Fascination About Getting Started with Bitcoin - UsenetReviewz.com Here are three steps to help you get going utilizing Bitcoin Cash right now: A Bitcoin wallet is an app or program that enables ...

Flag Counter