Bitcoin Rpc Curl CryptoCoins Info Club

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

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]

How to pass in wallet password over rpc using electrum-cash wallet

Hi, I am trying to send bitcoin using rpc and electrum and I am trying to pass the wallet password flag over rpc.

curl --data-binary '{"id":"curltext","method":"paytomany","params":[["bitcoincash:qrmcdhr4q5qvfq", 0.000006],["bitcoincash:qqcugujm4kfq5cgf3w6ddwz53ntmy5yfuygp9achwl", 0.000006]] }' http://username:[email protected]:7777
Somewhere I have to include the -wp flag that you use when interacting with daemon
submitted by BrandonBryant12 to btc [link] [comments]

bitcoin-cli.com

submitted by danielsocials to Bitcoin [link] [comments]

Trying to recover wallet, getting zero balance

Trying to recover my wallet using the 12 keywords. I get a zero balance. Interestingly Bitcoin core shows a balance but its wrong.
I have tried python wallet-tool.py -g 50 and -m 15 and rescan on bitcoin core repeatedly
Problem seems to be on original wallet internal addresses m/0/0/1 m/0/0/1/089 1CFwCuUpDBqW8Z8qHuJJ4V used 0.00288322 btc m/0/0/1/094 1LaZ9Rvc6DyFFRkKMHvBi8h used 0.00460657 btc for mixdepth=0 balance=0.00748979btc But on recovered wallet internal address m/0/0/1 only goes up to 10?
submitted by number6666 to joinmarket [link] [comments]

DNSBL is currently not blocking anything after recent pfsense update

I do not know if there was any update on the pfblockerng-devel package recently, as I just updated pfsense when I saw that it was available. After this update, DNSBL is not showing anything in the reports tab for blocks. The IP blocklists are working correctly, and when it reloads, it shows that unbound resolver, as well as the blocklists in DNSBL are loaded correctly. I do not know what could have caused this, and if I will have to re-install all of Pfsense to get it to work again. I have already tried to uninstall(while not keeping any previous settings), and then re-installing while re-doing all of the feeds in DNSBL.

TOP1M Final

33 33 1 0 0 32
[ Wally3kpersonal ] Reload [ 05/25/19 16:31:55 ] . completed .. Whitelist: analytics.ff.avast.com|analytics.plex.tv|app.adjust.com|content.tapjoy.com|gfe.nvidia.com|gfwsl.geforce.com|gstaticadssl.l.google.com|ip-info.ff.avast.com|ipm-provider.ff.avast.com|open.oneplus.net|placements.tapjoy.com|reports.crashlytics.com|rpc.tapjoy.com|settings.crashlytics.com|v7event.stats.avast.com|www-googletagmanager.l.google.com|
Orig. Unique # Dups # White # TOP1M Final
740 734 697 16 0 21
[ NewPihole_custom ] Reload [ 05/25/19 16:31:58 ] No Domains Found! Ensure only domain based Feeds are used for DNSBL!
[ Samsungblocks_custom ] Reload.
Orig. Unique # Dups # White # TOP1M Final
31 29 26 0 0 3
Saving DNSBL database... completed
Assembling DNSBL database... completed [ 05/25/19 16:32:07 ] Reloading Unbound Resolver..... completed [ 05/25/19 16:32:27 ]

DNSBL update [ 1654237 | PASSED ]... completed [ 05/25/19 16:32:28 ]

===[ GeoIP Process ]============================================
===[ IPv4 Process ]=================================================
[ Whitelist_custom_v4 ] exists. [ Abuse_DYRE_v4 ] Downloading update .. 404 Not Found
[ pfB_PRI1_v4 - Abuse_DYRE_v4 ] Download FAIL [ 05/25/19 16:32:29 ] Firewall and/or IDS (Legacy mode only) are not blocking download.
The Following List has been REMOVED [ Abuse_DYRE_v4 ]
[ Abuse_Feodo_C2_v4 ] exists. [ Abuse_IPBL_v4 ] exists. [ CINS_army_v4 ] exists. [ ET_Block_v4 ] exists. [ ET_Comp_v4 ] exists. [ Talos_BL_v4 ] Downloading update .. 403 Forbidden
[ pfB_PRI1_v4 - Talos_BL_v4 ] Download FAIL Firewall and/or IDS (Legacy mode only) are not blocking download.
The Following List has been REMOVED [ Talos_BL_v4 ]
[ Abuse_CW_PS_v4 ] exists. [ Abuse_LY_PS_v4 ] exists. [ BotScout_v4 ] exists. [ MDL_v4 ] exists. [ SFS_Toxic_v4 ] exists. [ CoinBlocker_v4 ] Downloading update .. 404 Not Found
[ pfB_PRI4_v4 - CoinBlocker_v4 ] Download FAIL [ 05/25/19 16:32:30 ] Firewall and/or IDS (Legacy mode only) are not blocking download.
The Following List has been REMOVED [ CoinBlocker_v4 ]
[ HoneyPot_IPs_v4 ] exists. [ Malc0de_v4 ] exists. [ Improware_v4 ] exists. [ LB_BL_v4 ] Downloading update . cURL Error: 28 Connection timed out after 15018 milliseconds Retry in 5 seconds... . cURL Error: 28 Connection timed out after 15002 milliseconds Retry in 5 seconds... . cURL Error: 28 Connection timed out after 15003 milliseconds Retry in 5 seconds... .. unknown http status code | 0
[ pfB_MAIL_v4 - LB_BL_v4 ] Download FAIL [ 05/25/19 16:33:30 ] Firewall and/or IDS (Legacy mode only) are not blocking download.
The Following List has been REMOVED [ LB_BL_v4 ]
[ Nix_Spam_v4 ] exists. [ SpamCop_SC_v4 ] exists. [ Toastedspam_v4 ] exists. [ DNSBLIP_v4 ] Downloading update .. completed ..
Reputation (Max=50) - Range(s) 185.244.25.|37.9.55.|146.185.236.|146.185.238.|64.154.80.|
Reputation -Max Stats
Blacklisted Match Ranges IPs Ranges IPs
5 877 0 0
Original Master Final
14168 12832 12832 [ Pass ]
===[ Reputation - pMax ]======================================
Querying for repeat offenders ( pMax=50 ) [ 05/25/19 16:33:31 ] Reputation -pMax ( None )
===[ Reputation - dMax ]======================================
Querying for repeat offenders ( dMax=20 ) [ 05/25/19 16:33:31 ] Classifying repeat offenders by GeoIP Processing [ Block ] IPs Removing [ Block ] IPs
Removed the following IP ranges: 212.27.35.|216.200.199.|207.246.136.|206.65.183.|209.132.193.|209.132.218.|209.132.220.|205.180.85.|61.135.131.|207.68.178.|204.253.104.|200.221.6.|
Reputation - dMax Stats
Blacklisted Match Ranges IPs Ranges IPs
12 359 0 0
===[ Suppression Stats ]===================================

List Pre Suppress Master

Abuse_Feodo_C2_v4 427 427 42824 Abuse_IPBL_v4 333 333 42824 CINS_army_v4 13730 13730 42824 ET_Block_v4 888 888 42824 ET_Comp_v4 498 498 42824 Abuse_CW_PS_v4 1 1 42824 Abuse_LY_PS_v4 1 1 42824 BotScout_v4 55 55 42824 MDL_v4 968 968 42824 SFS_Toxic_v4 83 83 42824 HoneyPot_IPs_v4 24 24 42824 Malc0de_v4 65 65 42824 Improware_v4 973 973 42824 Nix_Spam_v4 10323 10323 42824 SpamCop_SC_v4 195 195 42824 Toastedspam_v4 1775 1775 42824 DNSBLIP_v4 12485 12485 42824
===[ Aliastables / Rules ]==========================================
No changes to Firewall rules, skipping Filter Reload
Updating: pfB_Whitelist_v4 no changes. Updating: pfB_PRI1_v4 no changes. Updating: pfB_Abuse_PS_v4 no changes. Updating: pfB_PRI3_v4 no changes. Updating: pfB_PRI4_v4 no changes. Updating: pfB_MAIL_v4 no changes. Updating: pfB_DNSBLIP_v4 no changes.
===[ FINAL Processing ]=====================================
[ Original IP count ] [ 76449 ]
[ Final IP Count ] [ 42824 ]
===[ Permit List IP Counts ]=========================
 2 /vadb/pfblockerng/permit/Whitelist_custom_v4.txt 
===[ Deny List IP Counts ]===========================
42824 total 13730 /vadb/pfblockerng/deny/CINS_army_v4.txt 12485 /vadb/pfblockerng/deny/DNSBLIP_v4.txt 10323 /vadb/pfblockerng/deny/Nix_Spam_v4.txt 1775 /vadb/pfblockerng/deny/Toastedspam_v4.txt 973 /vadb/pfblockerng/deny/Improware_v4.txt 968 /vadb/pfblockerng/deny/MDL_v4.txt 888 /vadb/pfblockerng/deny/ET_Block_v4.txt 498 /vadb/pfblockerng/deny/ET_Comp_v4.txt 427 /vadb/pfblockerng/deny/Abuse_Feodo_C2_v4.txt 333 /vadb/pfblockerng/deny/Abuse_IPBL_v4.txt 195 /vadb/pfblockerng/deny/SpamCop_SC_v4.txt 83 /vadb/pfblockerng/deny/SFS_Toxic_v4.txt 65 /vadb/pfblockerng/deny/Malc0de_v4.txt 55 /vadb/pfblockerng/deny/BotScout_v4.txt 24 /vadb/pfblockerng/deny/HoneyPot_IPs_v4.txt 1 /vadb/pfblockerng/deny/Abuse_LY_PS_v4.txt 1 /vadb/pfblockerng/deny/Abuse_CW_PS_v4.txt
====================[ Empty Lists w/127.1.7.7 ]==================
Abuse_CW_PS_v4.txt
===[ DNSBL Domain/IP Counts ] ===================================
1668405 total 1083648 /vadb/pfblockerng/dnsbl/New.txt 370231 /vadb/pfblockerng/dnsbl/BBC_DGA.txt 51684 /vadb/pfblockerng/dnsbl/Abuse_urlhaus.txt 35526 /vadb/pfblockerng/dnsbl/Joewein_base.txt 20185 /vadb/pfblockerng/dnsbl/CoinBlocker_All.txt 14305 /vadb/pfblockerng/dnsbl/MDS.txt 11617 /vadb/pfblockerng/dnsbl/adguard.txt 10810 /vadb/pfblockerng/dnsbl/SFS_Toxic_BD.txt 10347 /vadb/pfblockerng/dnsbl/Shallamalware.txt 7616 /vadb/pfblockerng/dnsbl/Abuse_urlhaus_v4.ip 5739 /vadb/pfblockerng/dnsbl/CCT_BD.txt 5431 /vadb/pfblockerng/dnsbl/SWC.txt 5367 /vadb/pfblockerng/dnsbl/adserver.txt 4410 /vadb/pfblockerng/dnsbl/Shallalist_adv_v4.ip 4140 /vadb/pfblockerng/dnsbl/Spam404.txt 4036 /vadb/pfblockerng/dnsbl/Easylist.txt 3300 /vadb/pfblockerng/dnsbl/Shallalist_adv.txt 3130 /vadb/pfblockerng/dnsbl/hpHosts_ATS.txt 2619 /vadb/pfblockerng/dnsbl/Quidsup_Trackers.txt 2503 /vadb/pfblockerng/dnsbl/UT1_malware.txt 2009 /vadb/pfblockerng/dnsbl/Abuse_URLBL.txt 1869 /vadb/pfblockerng/dnsbl/CCT_BD_v4.ip 1515 /vadb/pfblockerng/dnsbl/MDS_Immortal.txt 1293 /vadb/pfblockerng/dnsbl/Cameleon.txt 588 /vadb/pfblockerng/dnsbl/EasyPrivacy.txt 560 /vadb/pfblockerng/dnsbl/UT1_publicite.txt 509 /vadb/pfblockerng/dnsbl/CoinBlocker_Opt.txt 493 /vadb/pfblockerng/dnsbl/UT1_marketingware.txt 456 /vadb/pfblockerng/dnsbl/MVPS.txt 317 /vadb/pfblockerng/dnsbl/ISC_SDL.txt 289 /vadb/pfblockerng/dnsbl/MDL.txt 280 /vadb/pfblockerng/dnsbl/EasyList.txt 267 /vadb/pfblockerng/dnsbl/UT1_ddos.txt 235 /vadb/pfblockerng/dnsbl/D_Me_Malv.txt 205 /vadb/pfblockerng/dnsbl/UT1_bitcoin.txt 205 /vadb/pfblockerng/dnsbl/Adaway.txt 129 /vadb/pfblockerng/dnsbl/Abuse_DOMBL.txt 78 /vadb/pfblockerng/dnsbl/Joewein_base_v4.ip 76 /vadb/pfblockerng/dnsbl/BBC_DC2.txt 74 /vadb/pfblockerng/dnsbl/UT1_publicite_v4.ip 58 /vadb/pfblockerng/dnsbl/Abuse_URLBL_v4.ip 32 /vadb/pfblockerng/dnsbl/Torrentlocker.txt 31 /vadb/pfblockerng/dnsbl/SFS_Toxic_BD_v4.ip 31 /vadb/pfblockerng/dnsbl/Quidsup_Mal.txt 28 /vadb/pfblockerng/dnsbl/Joewein_new.txt 26 /vadb/pfblockerng/dnsbl/SBL_ADs.txt 25 /vadb/pfblockerng/dnsbl/UT1_bitcoin_v4.ip 25 /vadb/pfblockerng/dnsbl/Lockyrw.txt 21 /vadb/pfblockerng/dnsbl/Wally3kpersonal.txt 15 /vadb/pfblockerng/dnsbl/Yoyo.txt 5 /vadb/pfblockerng/dnsbl/EasyList_v4.ip 5 /vadb/pfblockerng/dnsbl/ADs_custom.txt 3 /vadb/pfblockerng/dnsbl/Samsungblocks_custom.txt 2 /vadb/pfblockerng/dnsbl/Abuse_Zeus_BD.txt 2 /vadb/pfblockerng/dnsbl/Abuse_CW_C2.txt 1 /vadb/pfblockerng/dnsbl/UT1_marketingware_v4.ip 1 /vadb/pfblockerng/dnsbl/NoCoin.txt 1 /vadb/pfblockerng/dnsbl/MoneroMiner.txt 1 /vadb/pfblockerng/dnsbl/Malc0de.txt 1 /vadb/pfblockerng/dnsbl/EasyPrivacy_v4.ip 0 /vadb/pfblockerng/dnsbl/simple.txt 0 /vadb/pfblockerng/dnsbl/malvertising1.txt 0 /vadb/pfblockerng/dnsbl/hosts2.txt 0 /vadb/pfblockerng/dnsbl/dgad.txt 0 /vadb/pfblockerng/dnsbl/coinblockernew.txt 0 /vadb/pfblockerng/dnsbl/adhost.txt 0 /vadb/pfblockerng/dnsbl/adaway.txt 0 /vadb/pfblockerng/dnsbl/Windows_hosts_block.fail 0 /vadb/pfblockerng/dnsbl/Teslacrypt.txt 0 /vadb/pfblockerng/dnsbl/Ransomware1.txt 0 /vadb/pfblockerng/dnsbl/NewPihole_custom.txt 0 /vadb/pfblockerng/dnsbl/Malware2.txt 0 /vadb/pfblockerng/dnsbl/Malware1.txt 0 /vadb/pfblockerng/dnsbl/H3X_1h.txt 0 /vadb/pfblockerng/dnsbl/D_Me_Tracking.txt 0 /vadb/pfblockerng/dnsbl/D_Me_Malw.txt 0 /vadb/pfblockerng/dnsbl/D_Me_ADs.txt 0 /vadb/pfblockerng/dnsbl/Cryptowall1.txt 0 /vadb/pfblockerng/dnsbl/Abuse_TC_C2.txt 0 /vadb/pfblockerng/dnsbl/Abuse_C2_custom.txt
====================[ IPv4/6 Last Updated List Summary ]==============
Feb 8 2017 Improware_v4 Feb 21 09:45 MDL_v4 May 23 06:17 Malc0de_v4 May 23 21:29 ET_Comp_v4 May 23 21:37 Whitelist_custom_v4 May 24 23:35 CINS_army_v4 May 24 23:51 BotScout_v4 May 24 23:59 SFS_Toxic_v4 May 25 00:00 Nix_Spam_v4 May 25 00:05 Abuse_LY_PS_v4 May 25 00:05 Abuse_CW_PS_v4 May 25 00:05 Abuse_IPBL_v4 May 25 00:05 Abuse_Feodo_C2_v4 May 25 00:06 Toastedspam_v4 May 25 00:07 ET_Block_v4 May 25 00:07 HoneyPot_IPs_v4 May 25 00:08 SpamCop_SC_v4 May 25 16:33 DNSBLIP_v4
====================[ DNSBL Last Updated List Summary ]==============
Jul 31 2015 D_Me_Tracking Mar 9 2016 simple Mar 9 2016 D_Me_ADs Jan 20 2018 adaway Jan 20 2018 Adaway Mar 18 2018 Cameleon Nov 29 13:50 MDS_Immortal Feb 21 09:45 MDL Apr 15 22:17 Wally3kpersonal May 7 07:51 hpHosts_ATS May 7 07:51 adhost May 8 09:55 MVPS May 14 22:14 SWC May 17 12:21 Malware1 May 17 16:00 Shallamalware May 18 06:31 adguard May 18 06:41 Easylist May 21 06:13 coinblockernew May 21 06:13 CoinBlocker_Opt May 21 06:13 CoinBlocker_All May 22 21:57 Abuse_Zeus_BD May 22 21:58 Spam404 May 22 22:00 Shallalist_adv May 22 22:00 CCT_BD May 22 22:00 H3X_1h May 22 22:00 MoneroMiner May 22 22:00 NoCoin May 22 22:00 Quidsup_Mal May 22 22:00 Quidsup_Trackers May 22 22:01 adserver May 22 22:01 hosts2 May 22 22:01 Malware2 May 23 04:40 Yoyo May 23 06:10 Malc0de May 24 05:07 dgad May 24 05:07 SBL_ADs May 24 13:28 MDS May 24 16:00 New May 24 17:15 BBC_DGA May 24 21:01 Joewein_base May 24 21:04 ISC_SDL May 24 23:12 BBC_DC2 May 24 23:21 malvertising1 May 24 23:21 D_Me_Malw May 24 23:21 D_Me_Malv May 24 23:51 EasyList May 24 23:51 EasyPrivacy May 24 23:59 SFS_Toxic_BD May 25 00:00 Torrentlocker May 25 00:00 Lockyrw May 25 00:00 Cryptowall1 May 25 00:00 Abuse_URLBL May 25 00:00 Abuse_DOMBL May 25 00:00 Abuse_CW_C2 May 25 00:00 Abuse_urlhaus May 25 00:00 Joewein_new May 25 00:05 Teslacrypt May 25 00:05 Abuse_TC_C2 May 25 00:05 Ransomware1 May 25 14:12 UT1_bitcoin May 25 14:12 UT1_ddos May 25 14:12 UT1_malware May 25 14:12 UT1_marketingware May 25 14:12 UT1_publicite May 25 16:30 Abuse_C2_custom May 25 16:30 ADs_custom May 25 16:31 NewPihole_custom

May 25 16:31 Samsungblocks_custom

Database Sanity check [ PASSED ]

Masterfile/Deny folder uniq check Deny foldeMasterfile uniq check

Sync check (Pass=No IPs reported)

Alias table IP Counts

42826 total 15876 /vadb/aliastables/pfB_PRI1_v4.txt 13266 /vadb/aliastables/pfB_MAIL_v4.txt 12485 /vadb/aliastables/pfB_DNSBLIP_v4.txt 1106 /vadb/aliastables/pfB_PRI3_v4.txt 89 /vadb/aliastables/pfB_PRI4_v4.txt 2 /vadb/aliastables/pfB_Whitelist_v4.txt 2 /vadb/aliastables/pfB_Abuse_PS_v4.txt

pfSense Table Stats

table-entries hard limit 400000 Table Usage Count 154505
UPDATE PROCESS ENDED [ 05/25/19 16:33:33 ]
submitted by disguyisheren to pfBlockerNG [link] [comments]

C LIGHTNING rpc user and password?

How can I communicate from php via curl and rpc to work with LN?
can I use easybitcoin-php lib and throw commands as methods like I do with bitcoin?
Furthermore where do i set a user password for LN..
LN is sparse documentation for this :(
Please help
edit.. I HAVE GIVEN UP
just too hard and documented for experts only
i got close bitcoind running lnd running and connected via rpc to bitcond node
but in terms of communicating a simple command via php script i struck out
maybe it's c lightning vs lnd but lightning is just not ready for people as stupid as me i guess.
AMAZING.. wat i might be talented at is making A USE CASE! but the 5 fkn minutes of docs and 5 lines of unkown OS config IS STOPPING EVERYTHING..
This is how we can make bitcoin more valuable by allowing app level guys to get working without taking 50% of our time and messing with OS LEVEL COMMUNICATION..
LN low level DEVS pls take LITERALLY 10 minutes to whip up some curl lines and CONFIG AND SYNTAX Examples .. so we can do our job you divas. Why cant the RPC interface be like bitcoind? it just works!
EDIT: ok looks like they use NODE version outside current xenial repositories so1 upgrade node to ver 8
then it will probably still puke installing charge so to fix that try
2 npm install -g [email protected]
Jesus this is ridiculous version nightmares still errors now with sqlite3 perm issues so try
  1. npm -g install sqlite3 --save --unsafe-perm
OMG
NOW Looks like sqlite doesn't have support for Node 8 yet.!!! fk me this is stupid.
STILL!! Error: Cannot find module '/uslib/node_modules/lightning-charge/node_modules/sqlite3/lib/binding/node-v51-linux-x64/node_sqlite3.node'
EVEN AFTER downgrading node to v7 OMG this is really stupid i have no idea who is able to get this crap to work
FIXED: ===========
went TO /uslib/node_modules/lightning-charge/ and installed sqlite3 from there
.. finally now i can get on to my real job.. making something useful. Hope this helps other people.
submitted by vroomDotClub to lightningnetwork [link] [comments]

How Ulbricht paid ฿100 to learn about `bitcoind -rescan`

I was revisiting Gwern and my research into the Silk Road / Mt. Gox connection, found something very interesting on the '1MR6pXD' address. Oh Ulbricht...
xpost from this post:
Long-time readers may recall that among Ulbricht's problems with developing & running Silk Road, he had problems with theft from his MtGox account: "Silk Goxed: How DPR used Mtgox for hedging & lost big". We identified his accounts and deposits as part of that investigation.
Based on our findings, imposter has found a previously unknown Ross Ulbricht account on the Bitcoin Talk forums, used for tech support with SR1 problems: the user account "kohlanta" (posts), registered 19 August 2012. The name is a reference to a tourist destination in Thailand; Ulbricht was living in Australia around this time and traveled some places, apparently including Ko Lanta. This account must be Ulbricht because (1) who has ฿40,000 in a single address in August 2015? (2) the amount matches up exactly with the big transactions noted in 'Silk Goxed', and kohlanta's address 1MR..Y is the one involved in the Ulbricht withdrawals/deposits. (When he told me about this, I felt dumb - why hadn't I bothered to google 1MR..Y during our 'Silk Goxed' work to see if it had appeared anywhere else online?)
kohlanta's first question concerns the inability to move ฿40,000; this problem was solved by bitcoind -rescan, as pointed out by BT user fcmatt. (You can see he did indeed pay the ฿100 by noting that the amounts shrink by exactly that much.)
We can also see the trial testimony independently confirmed by kohlanta's further questions: questions about using curl, json-rpc, and versioning issues with the wallet.
There's nothing really important here that I can see, but it's interesting to see him panicking over the 1MR..Y, and it's definitely a reminder that Bitcoin addresses are only pseudonymous; once pseudonymity has been broken or damaged, you can continue to follow transactions & addresses to see what you can find.
submitted by impost_r to Bitcoin [link] [comments]

How Ulbricht paid ฿100 to learn about `bitcoind -rescan`

Long-time readers may recall that among Ulbricht's problems with developing & running Silk Road, he had problems with theft from his MtGox account: "Silk Goxed: How DPR used Mtgox for hedging & lost big". We identified his accounts and deposits as part of that investigation.
Based on our findings, impost_imposter has found a previously unknown Ross Ulbricht account on the Bitcoin Talk forums, used for tech support with SR1 problems: the user account "kohlanta" (posts), registered 19 August 2012. The name is a reference to a tourist destination in Thailand; Ulbricht was living in Australia around this time and traveled some places, apparently including Ko Lanta. This account must be Ulbricht because (1) who has ฿40,000 in a single address in August 2012? (2) the amount matches up exactly with the big transactions noted in 'Silk Goxed', and kohlanta's address 1MR..Y is the one involved in the Ulbricht withdrawals/deposits. (When he told me about this, I felt dumb - why hadn't I bothered to google 1MR..Y during our 'Silk Goxed' work to see if it had appeared anywhere else online?)
kohlanta's first question concerns the inability to move ฿40,000; this problem was solved by bitcoind -rescan, as pointed out by BT user fcmatt. (You can see he did indeed pay the ฿100 by noting that the amounts shrink by exactly that much.)
We can also see the trial testimony independently confirmed by kohlanta's further questions: questions about using curl, json-rpc, and versioning issues with the wallet.
There's nothing really important here that I can see, but it's interesting to see him panicking over the 1MR..Y, and it's definitely a reminder that Bitcoin addresses are only pseudonymous; once pseudonymity has been broken or damaged, you can continue to follow transactions & addresses to see what you can find.
submitted by gwern to SilkRoad [link] [comments]

Blackcoin Wallet Passphrase mistyped - Bruteforce

Summary: I executed a (limited!) brute force attack on a wallet where I mistyped the passphrase. Attached is a short tutorial how to make it.
Long story: some months ago I created a wallet. I keyed in my passphrase with 70 characters long (yes it is long), wrote it down, bought Blackcoin. Next day I tried to open it, but it seems to be that I mistyped (two times) the passphrase. So I started to make a long research how to "hack" it. I finally figured that I can make a limited brute force attack by using RPC. So, I got familiar with curl (RPC tool) and created a batch-script with Excel where I just changed one character per try. I ended with 5200 tries.
And boom: It worked! It was try number 2814 which worked. So, I really just mistyped one single character. The wallet has been opened once again. So now I have access to my Blackcoins.
-----TUTORIAL-----
I was using the old blackcoin-qt (on windows) because the wallet was created with this one. I do not know if it is compatible with lore. Situation is that you remember (more or less) the passphrase, but you think that you just mistyped one character. Idea is to make a limited brute force attack on the wallet - so, to test different passphrase which are similar to your remembered one.
we will create a script (batch) which calls the blackcoin-qt (as server) via RPC and try to open the wallet with different passphrases.
What did not work
I found some hints concerning hashcat and bitcoin2john (also for Blackcoin), which enable you to retrieve the seed out of the wallet and to make a bruteforce on the hash of the seed (with hashcat). But it did not work, because the blackcoin wallet seems to be different than the bitcoin wallet.
There is also no direct commandline parameter for opening the wallet with passphrase. So I started to work with RPC.
Using the blackcoin-qt as a server
Switch into C:\Users\myusername\AppData\Roaming\BlackCoin and place a blackcoin.conf file here. This should contain (at least) these entries:

server=1 tells BlackCoin to accept JSON-RPC commands.

server=1

You must set rpcuser and rpcpassword to secure the JSON-RPC api

rpcuser=user
rpcpassword=password

Listen for RPC connections on this TCP port:

rpcport=15715

You can use BlackCoin or blackcoind to send commands to Bitcoin/bitcoindBlackCoin/blackcoind

running on another host using this option:

rpcconnect=127.0.0.1
...Start blackcoin from the commandline with the server parameter like this: blackcoin-qt -server=1
Test RPC Calls with curl
Download curl (an RPC tool for the commandline): https://curl.haxx.se/
For this test you should use a new generated wallet with a password you know.
First test with the getinfo method, which shows you if the connection to the Blackcoin Daemon is established: curl --header "Content-Type: application/json" --data-binary "{\"jsonrpc\":\"1.0\",\"id\":\"curltest\",\"method\":\"getinfo\",\"params\":[]}" http://user:[email protected]:15715/
If you do not get any connection, you can also use netstat -a to see if your machine is listening on the port 15715.
Finally, the method to open the wallet via RPC (uses two parameters) curl --header "Content-Type: application/json" --data-binary "{\"jsonrpc\":\"1.0\",\"id\":\"curltest\",\"method\":\"walletpassphrase\",\"params\":[\"mySecretWalletPassword\",50]}" http://user:[email protected]:15715/
Note the output you get, when you use the correct password: {"result":null,"error":null,"id":"curltest"}
Later we want to search in a logfile for the expression "error":null in order to identify the correct password
Generating the Bruteforce Script
I used an Excel file to create a script. On the basis of the so-far-remembered-passphrase and a selection of possible characters this scripts changes for each row only one character. I ended up with roughly 5000 rows, but I used a very long passphrase (70 characters). Using the Excel output you can create a script out of it.
If you are interested in the Excel file you can contact me on bitcointalk - my username is "Euro1000"
Execution
Start the script (batch) and pipe the output into a log: myScript.bat > log.txt
When the batch finished search for the expression "error":null If you found it, you found the password in the line above the expression.
Limitations
I used the old blackcoin-qt (not Lore), because the wallet has been generated with blackcoin-qt. Lore should use the same RPC implementation, but it is untested if this tutorial also works with Lore.
I used this on Windows I do not know if this will also work on Linux.
Some special characters are a little bit tricky in curl, because some of them like "<" let curl crashes. Perhaps you can escape these special characters somehow.
submitted by coindestroyer to blackcoin [link] [comments]

need some help to start mining on my macbook air

hi guys. i've known of BitCoins for a while, but i've just started to really learn about them this past week. nobody i know knows anything about them, so i'm trying to just teach myself from the internet. i started by reading a ton of start off guides and whatnot. i have the bitcoin-qt wallet to start off with. next, since pool mining is my main interest, i followed this guide after the wallet, i downloaded rpcminer for my mac. next, i set up an account on slush's pool and finished the instructions. i think i did everything right, but when i run rpcminer i get

"Starting RPCminer (CPU)...

Client will start 4 miner threads Work will be refreshed every 4000 ms Could not retrieve work from RPC server. CURL return value = 7 Could not retrieve work from RPC server. CURL return value = 7 Could not retrieve work from RPC server. CURL return value = 7 Could not retrieve work from RPC server. CURL return value = 7 Could not retrieve work from RPC server. CURL return value = 7 Could not retrieve work from RPC server. CURL return value = 7 Could not retrieve work from RPC server. CURL return value = 7 Could not retrieve work from RPC server. CURL return value = 7 No blocks are being hashed right now. This can happen if the application is still starting up, you supplied incorrect parameters, or there is a communications error connecting to the RPC server. Could not retrieve work from RPC server."
any help would be greatly appreciated! how can i fix this error? or are the different mining softwares or mining pools that work better? i've tried really hard to get this working myself but i seem to be stuck. i'd really appreciate any hands-on help i can get from people who know their stuff.
i have a macboook air with a 1.8GHz intel core i5 ivy bridge processor, and the integrated intel HD Graphics 4000 512 MB. if you need any more information i didn't include to help me, please say so i can fill you in. thanks a ton for looking!
Edit- thanks everybody for all the help! Its greatly appreciated. I never thought about overheating it. I'll just consider other options if i do decide to get somewhat serious into mining, like an asic jalepeno or something
edit 2- i've found a computer i can use, with an amd fx-8350 inside of it. i'm trying to figure out how many bitcoins i can mine if i start using it soon. i've googled around a lot, but i can't seem to find the hash rate for this GPU. i'm probably going to start mining on it this weekend, but having some sort of a clue of what i can mine would be nice. i'm not looking for a get rich quick sort of thing, i'm just looking to get into mining as more of a hobby. i'd rather not buy a dedicated miner, and i think i can mine a fair amount of bitcoins with the 8350 before all the new ASICs arrive. thanks if anybody knows the hash rate on the 8350!
submitted by _connor_ to BitcoinMining [link] [comments]

JSON-RPC connection failed when blockchain on USB – Please Help!

Hi,
Please be gentle.
2 weeks ago I had only ever used windows, the tor browser bundle and an electrum bitcoin wallet. Id heard of tails but never used it and knew nothing at all of coinjoin and joinmarket. I read a few things on reddit and thought id give it a try. After a lot more reading I decided on the following set up:
1.Tails with persistant on USB
2.Veracrypt install with hidden partition volume
3.bitcoin core over tor with blockchain stored on USB drive
4.joinmarket using the blockchain on my USB
5.joinmarket using the tor based irc channel
as you can imagine for a complete noob it has been a very steep learngin curve!
I was very pleased with myself today when I thought I had finnally managed to get it all set up without having to ask for help (I enjoy the intelectual challenge of working it ouy for myself) but when I tested it using python wallet-tool.py wallet.json
I get the following error:
2016-03-15 16:08:47,033 [MainThread ] [DEBUG] hello joinmarket
Traceback (most recent call last):
File "wallet-tool.py", line 89, in
load_program_config()
File "/home/amnesia/Persistent/joinmarket/joinmarket/configure.py", line 223, in load_program_config
global_singleton.config)
File "/home/amnesia/Persistent/joinmarket/joinmarket/configure.py", line 242, in get_blockchain_interface_instance
bc_interface = BitcoinCoreInterface(rpc, network)
File "/home/amnesia/Persistent/joinmarket/joinmarket/blockchaininterface.py", line 492, in init
blockchainInfo = self.jsonRpc.call("getblockchaininfo", [])
File "/home/amnesia/Persistent/joinmarket/joinmarket/jsonrpc.py", line 111, in call
response = self.queryHTTP(request)
File "/home/amnesia/Persistent/joinmarket/joinmarket/jsonrpc.py", line 100, in queryHTTP
repr(exc))
joinmarket.jsonrpc.JsonRpcConnectionError: JSON-RPC connection failed. Err:error(111, 'Connection refused')
so close yet still so far!!!!! I havent been able to find an answer to this anywhere and simply have no idea what it means or how to fix it. so am posting here in the hope someone can help or point me in the right direction. my bitcoin and joinmarket settings are as follows:
/home/amnesia/Persistent/bitcoin-0.11.2/bin/bitcoin.conf
rpcuser=bitcoin
rpcpassword=password
daemon=1
proxyrandomize=1
proxy=127.0.0.1:9050
listen=0
server=1
For JoinMarket
walletnotify=curl -sI --connect-timeout 1 http://localhost:62602/walletnotify?%s
alertnotify=curl -sI --connect-timeout 1 http://localhost:62602/alertnotify?%s
User must uncomment and input path to blockchain files
datadir=/media/amnesia/590C-2CF0/bitcoin
/home/amnesia/Persistent/joinmarket/joinmarket.cfg
[BLOCKCHAIN]
blockchain_source = bitcoin-rpc
network = mainnet
rpc_host = localhost
rpc_port = 8332
rpc_user = bitcoin
rpc_password = password
[MESSAGING]
host = 6dvj6v5imhny3anf.onion
channel = joinmarket-pit
port = 6698
usessl = true
socks5 = true
socks5_host = localhost
socks5_port = 9050
maker_timeout_sec = 30
and can anyone confirm I am right in thinking that to run bitcoin core over tor I just choose socks5 and port 9050 in the settings, there's nothing else I need to change? Told you I was a noob!
Thanks in advance for any help and please forgive me if I dont understand your answer at first.
i also have no idea how to sort out the formatting of that post, sorry!!!!
submitted by smokingskills1 to joinmarket [link] [comments]

tailsjoin full node connection failed

I've been trying to get joinmarket running with a full node working forever and I'm almost there but I keep getting this error.
2016-04-18 22:09:43,109 [MainThread ] [DEBUG] hello joinmarket Traceback (most recent call last):
File "wallet-tool.py", line 89, in
load_program_config() 
File "/home/amnesia/Persistent/joinmarket/joinmarket/configure.py", line 222, in \load_program_config
global_singleton.config)
File "/home/amnesia/Persistent/joinmarket/joinmarket/configure.py", line 241, in \get_blockchain_interface_instance
bc_interface = BitcoinCoreInterface(rpc, network) 
File "/home/amnesia/Persistent/joinmarket/joinmarket/blockchaininterface.py", line 492, in
init blockchainInfo = self.jsonRpc.call("getblockchaininfo", [])
File "/home/amnesia/Persistent/joinmarket/joinmarket/jsonrpc.py", line 111, in call
response = self.queryHTTP(request) 
File "/home/amnesia/Persistent/joinmarket/joinmarket/jsonrpc.py", line 100, in queryHTTP
repr(exc))
joinmarket.jsonrpc.JsonRpcConnectionError: JSON-RPC connection failed. Err:error(111, \'Connection refused')

joinmarket.cfg:

[BLOCKCHAIN] blockchain_source = bitcoin-rpc #options: blockr, bitcoin-rpc, json-rpc, regtest # for instructions on bitcoin-rpc read # https://github.com/chris-belchejoinmarket/wiki/Running-JoinMarket-with-Bitcoin-Core-full-node network = mainnet rpc_host = 127.0.0.1 rpc_port = 8332 rpc_user = bitcoin rpc_password = password
[MESSAGING] #host = irc.cyberguerrilla.org channel = joinmarket-pit #port = 6697 #usessl = true #socks5 = false socks5_host = 127.0.0.1 socks5_port = 9050 #for tor host = 6dvj6v5imhny3anf.onion port = 6697 usessl = true socks5 = true maker_timeout_sec = 30

bitcoin.conf:

rpcuser=bitcoin rpcpassword=password daemon=1 proxyrandomize=1 proxy=127.0.0.1:9050 listen=0 server=1
# For JoinMarket
walletnotify=curl -sI --connect-timeout 1 http://127.0.0.1:62602/walletnotify?%s
alertnotify=curl -sI --connect-timeout 1 http://127.0.0.1:62602/alertnotify?%s
# User must uncomment and input path to blockchain files
datadir=/home/amnesia/Persistent/.bitcoin"
Can any please help?
submitted by frustratedtails to joinmarket [link] [comments]

Bitcoin Core 0.12.1 released | Wladimir J. van der Laan | Apr 15 2016

Wladimir J. van der Laan on Apr 15 2016:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.12.1 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.12.1/
Or through bittorrent:
magnet:?xt=urn:btih:25c4df2a822e840e972a50a31095632d87efadab&dn;=bitcoin-core-0.12.1&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 the BIP9, BIP68 and BIP112
softfork, various bugfixes and 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/.
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrade warning

Downgrade to a version < 0.12.0

Because release 0.12.0 and later will obfuscate the chainstate on every
fresh sync or reindex, the chainstate is not backwards-compatible with
pre-0.12 versions of Bitcoin Core or other software.
If you want to downgrade after you have done a reindex with 0.12.0 or later,
you will need to reindex when you first start Bitcoin Core version 0.11 or
earlier.
Notable changes

First version bits BIP9 softfork deployment
This release includes a soft fork deployment to enforce BIP68,
BIP112 and BIP113 using the BIP9 deployment mechanism.
The deployment sets the block version number to 0x20000001 between
midnight 1st May 2016 and midnight 1st May 2017 to signal readiness for
deployment. The version number consists of 0x20000000 to indicate version
bits together with setting bit 0 to indicate support for this combined
deployment, shown as "csv" in the getblockchaininfo RPC call.
For more information about the soft forking change, please see
https://github.com/bitcoin/bitcoin/pull/7648
This specific backport pull-request can be viewed at
https://github.com/bitcoin/bitcoin/pull/7543
BIP68 soft fork to enforce sequence locks for relative locktime
BIP68 introduces relative lock-time consensus-enforced semantics of
the sequence number field to enable a signed transaction input to remain
invalid for a defined period of time after confirmation of its corresponding
outpoint.
For more information about the implementation, see
https://github.com/bitcoin/bitcoin/pull/7184
BIP112 soft fork to enforce OP_CHECKSEQUENCEVERIFY
BIP112 redefines the existing OP_NOP3 as OP_CHECKSEQUENCEVERIFY (CSV)
for a new opcode in the Bitcoin scripting system that in combination with
BIP68 allows execution pathways of a script to be restricted based
on the age of the output being spent.
For more information about the implementation, see
https://github.com/bitcoin/bitcoin/pull/7524
BIP113 locktime enforcement soft fork
Bitcoin Core 0.11.2 previously introduced mempool-only locktime
enforcement using GetMedianTimePast(). This release seeks to
consensus enforce the rule.
Bitcoin transactions currently may specify a locktime indicating when
they may be added to a valid block. Current consensus rules require
that blocks have a block header time greater than the locktime specified
in any transaction in that block.
Miners get to choose what time they use for their header time, with the
consensus rule being that no node will accept a block whose time is more
than two hours in the future. This creates a incentive for miners to
set their header times to future values in order to include locktimed
transactions which weren't supposed to be included for up to two more
hours.
The consensus rules also specify that valid blocks may have a header
time greater than that of the median of the 11 previous blocks. This
GetMedianTimePast() time has a key feature we generally associate with
time: it can't go backwards.
BIP113 specifies a soft fork enforced in this release that
weakens this perverse incentive for individual miners to use a future
time by requiring that valid blocks have a computed GetMedianTimePast()
greater than the locktime specified in any transaction in that block.
Mempool inclusion rules currently require transactions to be valid for
immediate inclusion in a block in order to be accepted into the mempool.
This release begins applying the BIP113 rule to received transactions,
so transaction whose time is greater than the GetMedianTimePast() will
no longer be accepted into the mempool.
Implication for miners: you will begin rejecting transactions that
would not be valid under BIP113, which will prevent you from producing
invalid blocks when BIP113 is enforced on the network. Any
transactions which are valid under the current rules but not yet valid
under the BIP113 rules will either be mined by other miners or delayed
until they are valid under BIP113. Note, however, that time-based
locktime transactions are more or less unseen on the network currently.
Implication for users: GetMedianTimePast() always trails behind the
current time, so a transaction locktime set to the present time will be
rejected by nodes running this release until the median time moves
forward. To compensate, subtract one hour (3,600 seconds) from your
locktimes to allow those transactions to be included in mempools at
approximately the expected time.
For more information about the implementation, see
https://github.com/bitcoin/bitcoin/pull/6566
Miscellaneous
The p2p alert system is off by default. To turn on, use -alert with
startup configuration.
0.12.1 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.

RPC and other APIs

  • - #7739 7ffc2bd Add abandoned status to listtransactions (jonasschnelli)

Block and transaction handling

  • - #7543 834aaef Backport BIP9, BIP68 and BIP112 with softfork (btcdrak)

P2P protocol and network code

    • #7804 90f1d24 Track block download times per individual block (sipa)
    • #7832 4c3a00d Reduce block timeout to 10 minutes (laanwj)

Validation

    • #7821 4226aac init: allow shutdown during 'Activating best chain...' (laanwj)
    • #7835 46898e7 Version 2 transactions remain non-standard until CSV activates (sdaftuar)

Build system

    • #7487 00d57b4 Workaround Travis-side CI issues (luke-jr)
    • #7606 a10da9a No need to set -L and --location for curl (MarcoFalke)
    • #7614 ca8f160 Add curl to packages (now needed for depends) (luke-jr)
    • #7776 a784675 Remove unnecessary executables from gitian release (laanwj)

Wallet

  • - #7715 19866c1 Fix calculation of balances and available coins. (morcos)

Miscellaneous

    • #7617 f04f4fd Fix markdown syntax and line terminate LogPrint (MarcoFalke)
    • #7747 4d035bc added depends cross compile info (accraze)
    • #7741 a0cea89 Mark p2p alert system as deprecated (btcdrak)
    • #7780 c5f94f6 Disable bad-chain alert (btcdrak)
Credits

Thanks to everyone who directly contributed to this release:
    • accraze
    • Alex Morcos
    • BtcDrak
    • Jonas Schnelli
    • Luke Dashjr
    • MarcoFalke
    • Mark Friedenbach
    • NicolasDorier
    • Pieter Wuille
    • Suhas Daftuar
    • Wladimir J. van der Laan
As well as everyone that helped translating on Transifex.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJXELrMAAoJEHSBCwEjRsmm75EH/0iyqFxXuJDbfzMmBbMTkXD2
/CXEeyMvs62F2ZeODE0SSqo9sXo4foiT9WI5Dq7BwAiF6jh/XE4QwBvc91BbPyGZ
1nOGEab+oe37xEOkn8MyGbHfCutsUldyKltVQjA3y685MxlSgTjl/nX6Pbpbxped
vZRog3KHRrpWAMrHdi6p/xgqX0ajxE6K1P16JMOx4W/gE9QgOPyy7+l/4WT6SyBj
k/pOLqJc+yQIOa9szS4pjLUqaSOirhsjXfro9FYjHqiTWQwAdvuK4xXgo1GrGIW1
PWs419uLmGl4bhg9jdY6v+PyPz4iUilRzoixVi8op1Rt9/AoNN1ViJ/LT15Hagw=
=h4Wp
-----END PGP SIGNATURE-----
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-April/012607.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Total noob stuck trying to mine doge. [help]

Hello,
I've gotten up and running with GUIminer which mines bitcoins no problem, but I want to mine Doge, not Bit. I keep getting this error:
CURL return value = 52 "Communications error connecting to the RPC server"
I've triple checked that all my miner information is correct (user_name.miner_name not just miner_name).
I was using the suchcoins.com pool and figured maybe the server was down or something, so I switched to dogepool.net. Still the same error.
I tried running CUDAminer alone without GUIminer, but same results...
I'm stumped on what to do here...
Here's my specs:
------------------ System Information ------------------ Time of this report: 2/11/2014, 21:53:13 Machine name: USER1-PC Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 System Manufacturer: ASUSTeK Computer INC. System Model: CM5571 BIOS: BIOS Date: 08/25/10 11:20:07 Ver: 08.00.14 Processor: Pentium(R) Dual-Core CPU E5400 @ 2.70GHz (2 CPUs), ~2.7GHz Memory: 6144MB RAM Available OS Memory: 6144MB RAM Page File: 2371MB used, 9912MB available Windows Dir: C:\Windows DirectX Version: DirectX 11 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled DxDiag Version: 6.01.7601.17514 32bit Unicode --------------- Display Devices --------------- Card name: NVIDIA GeForce GT 240 Manufacturer: NVIDIA Chip type: GeForce GT 240 DAC type: Integrated RAMDAC Display Memory: 3794 MB Dedicated Memory: 978 MB Shared Memory: 2815 MB 
Also I had a few other questions about mining: 1) I know ASIC's won't work on scrypt coins, but will ASIC's like AntMiner work for other SHA-256 coins? Or just bitcoins?
2) A lot of the tutorials I've seen have very short simple passwords for their workers. Some even just one letter. Why do workers need a password at all?
Thank you!
submitted by dogehelpplz to dogemining [link] [comments]

Bitcoin HACK 2020 BITCOIN GRATIS - YouTube How to give your bitcoin node commands using a web server PGN - Pigeon Coin Mining  GPU Pool  CPU Solo - nvidia 1080ti Bitcoin RPC Remote Code Execution Exploit for BitcoinCore 0.9-0.15.1 CVE-2017-9230 $10 VS $20,000 EBAY MYSTERY BOX! (Bitcoin?!) - YouTube

.NET (C#) The communication with the RPC service can be achieved using the standard http request/response objects. A library for serializing and deserializing Json will make your life a lot easier: How to Do RPC Calls with C++ Bitcoind . bitcoin deamon = core value of the software (bitcoind -printtoconsole -debug=1) Bitcoind provide the RPC "interface" in which user can query with bitcoin-cli (or a library in c++). You must run bitcoind before using bitcoin-cli. The testnet=1 option can be (not) specified in the bitcoin.conf file (thus causing it to be on mainnet by default), and this can be over-ridden in bitcoin-cli with the -testnet command-line option. But, when using the json-rpc interface via curl, I can't figure out how to specify I want testnet in this case. Jgarzik bitcoin rpc curl has forked it algo trading amibroker as Python-BitcoinRPC and optimized it for current versions.Key to this, he says, is continued advancement in the cryptocurrencies themselves; to add applications and transact faster at lower costs. 410334, "version":"hash" (string) The hash of the next block } Result (for verbosity = 2):June 8 2012 Havelock Investments Mining Fund ... Put the correct RPC port (default for the selected chain or set explicitly with -rpcport) into the RPC help text "curl" example. Previously, the port there was always reported as 8332 (default mainnet port). With this change, it will be correct for testnet/regtest or with an explicit -rpcport, so that the example can be used as-is in these situations.

[index] [36199] [47962] [39279] [2901] [14413] [14038] [41526] [16989] [30413] [16052]

Bitcoin HACK 2020 BITCOIN GRATIS - YouTube

Updated 2018 How to mine Bitcoin with GPU Video Card Windows 10 - Duration: 6:14. howtwos101 32,410 views. 6:14. Microsoft Access 2016 Tutorial: A Comprehensive Guide to Access ... Anditto covers basics of Remote Procedure Calls (RPC) that allow developer to use Bitcoin client to interact with Bitcoin network. How to configure and interact with Bitcoin using RPC (create ... Ehi! Sei alla ricerca delle risposte alle domande più importanti di sempre? Sia che ti piacciano le scoperte scientifiche, l'esplorazione dello spazio, gli i... In this video we look at the iOS Kodi Remote app and the underlying JsonRpc API that drives it. https://kodi.wiki/view/JSON-RPC_API/v9. Bitcoin JSON-RPC Tutorial 3 - bitcoin.conf - Duration: 8:10. m1xolyd1an 13,667 views. 8:10. How to build a monero full (remote) node on ubuntu linux server - Duration: 14:32. ...

#