bitcoind - error : incorrect rpcuser or rpcpassword ...

hodlmon.sh: a UTXO monitoring methodology and script for true connoisseurs of security, paranoia and BTC maximalism

EDIT:
Disclaimer: the below script is provided for example purposes only. You're responsible for your own security. Don't trust, verify.
tldr: the script is literally just an example wrapper to call "gettxout" on your own node via cron to check if your own utxo has been spent yet
OK, since there are a few questions on security below, let me clarify: this script is only for people who are 1) already running their own nodes and 2) can understand the bash script below. And obviously, don't trust some random person on the internet, always verify. I provided this as an example for a way to monitor your own UTXOs with your existing node. Those of you who understand what the below script does will see it's painfully simple and obviously harmless. Those of you who don't understand it, just ignore this post, or better yet, research what the below means until you do understand it. What's important is the idea of monitoring your own UTXO, and this script is an example of how to do that with gettxout.
ORIGINAL POST:
Submitting this to help strengthen the community, and for review:
hodlmon.sh: a UTXO monitoring methodology and script for true connoisseurs of security, paranoia and BTC maximalism
Monitor canary UTXOs for early detection of compromised private keys BEFORE funds are lost, using your own full node for maximum privacy and trustlessness. Note that you will need to implement your own notification strategy (email, push, sms, etc). This script is intended to run on your full node, but can be run from any machine with RPC access to your full node.
hodlmon.sh is designed to check if a given UTXO (i.e. a specific output of a specific btc transaction) has been spent or not. This can be used for early and proactive detection if a seed phrase or private key has been compromised, so you have time to move your btc before full compromise happens. In order for this to work, a small amount of btc should be sent to an address controlled only by a given seedphrase, with that seedphrase being part of a multisig wallet or a seedphrase+passphrase wallet, and the majority of your funds controlled in the seedphrase+passphrase or multisig wallet. The idea is to leave the small amount of btc (the canary utxo) in the address, so that it never moves unless the seedphrase that controls it has been compromised and all funds in the wallet swept. In this way, you use those compromised sats to buy information about the current security status of your wallet(s).
Example usage:Set up a cron job to run hodlmon.sh every 30 min to check if transaction output at index "0" for transaction with id "123" has been spent already. Use "my_utxo_nickname" as a friendly name for the UTXO (to differentiate between multiple wallets)
*/30 * * * * /path/to/hodlmon.sh 123 0 my_utxo_nickname > /tmp/hodlmon_log 2> /tmp/hodlmon_err_log
Usage scenario #1: Seedphrase (A) + passphrase (A')Majority of funds are held in a wallet controlled by both the seedphrase and passphrase, A and A'. A token amount of btc is controlled only by seedphrase A.
A + A': majority of funds
A: canary UTXO
hodlmon.sh is used to monitor the canary funds locked by A, so that if it is discovered that A has been compromised, the funds locked by A and A' can be moved to a new wallet before the passphrase A' can be cracked and all your funds exfiltrated.
Usage scenario #2: multisig e.g. 2 of 3, with seed phrases A, B and CMajority of funds held in a multisig wallet controlled by 3 seedphrases A, B, and C. 3 small canary UTXOs are held in wallets each controlled by A, B or C, respectively.
A + B + C: majority of funds
A: canary UTXO 1
B: canary UTXO 2
C: canary UTXO 3
One benefit of multisig (e.g. 2 of 3) is that even if 1 key is compromised, your funds are safe, since at least 2 keys are needed to release funds. But how do you that none of the keys has yet been compromised? If you create separate wallets controlled each by only 1 of the individual keys, and use hodlmon.sh to monitor whether those UTXOs have been exfiltrated, then you can detect partial compromise of your setup before a full exfiltration event takes place, so you can move your funds to a new multisig wallet with freshly generated and uncompromised keys.
Example of 3 cronjobs to monitor all 3 canary UTXOs:
*/30 * * * * /path/to/hodlmon.sh 123 0 key1 > /tmp/hodlmon_log_1 2> /tmp/hodlmon_err_log_1
*/30 * * * * /path/to/hodlmon.sh 456 0 key2 > /tmp/hodlmon_log_2 2> /tmp/hodlmon_err_log_2
*/30 * * * * /path/to/hodlmon.sh 789 0 key3 > /tmp/hodlmon_log_3 2> /tmp/hodlmon_err_log_3

Example hodlmon script:
#########################################################################
#!/bin/bash
touch /tmp/hodlmon_last_run
echo "Transaction ID: $1"
echo "Output #: $2"
echo "Nickname: $3"
NODE_IP=127.0.0.1 #TODO: use actual value
USER=user#TODO: use actual value
PASS=pass #TODO: use actual value
PORT=8332 #TODO: use actual value
CHECK_CMD="/uslocal/bin/bitcoin-cli -rpcconnect=$NODE_IP -rpcuser=$USER -rpcpassword=$PASS -rpcport=$PORT gettxout $1 $2"
RESULT="$($CHECK_CMD)"
echo "${RESULT}"
if [ "$RESULT" == "" ]
then
echo "UTXO HAS BEEN SPENT! RED ALERT!!"
MSG="The UTXO for $3 from tx $1 output $2 has moved!"
#TODO: ADD YOUR FAVORITE NOTIFICATION STRATEGY E.G. EMAIL, PUSH NOTIFICATION, SMS
else
echo "UTXO is still on ice"
fi
############################################

submitted by facepalm5000 to Bitcoin [link] [comments]

Connecting bitcoin-qt to bitcoind on local network

Hello,
I have a bitcoin node running on a headless box (bitcoind) and I would like to connect to it using bitcoin-qt on my desktop. I'm getting a little confused with the process.... does bitcoin-qt need to connect to bitcoind using RPC? Do I store my wallet file on the bitcoind box, or bitcoin-qt box?
The bitcoin node is already setup to work with an electrum server, so I already have rpcbind=0.0.0.0, rpcallowip=$ELECTRUX_IP, and rpcuserpcpassword set. I tried adding my desktop IP to rpcallowip, and setting the appropriate username/password in bitcoin-qt's bitcoin.conf, but no luck. I can see in debug.log for bitcoin-qt that the connection is rejected.

The node runs over TOR and I have onlynet=onion set in bitcoind's bitcoin.conf, but that doesn't seem to stop electrumx connecting via RPC over clearnet, so this shouldn't be an issue right?

Am I missing something here? Help would be much appreciated!
submitted by backfromBTCpast to Bitcoin [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

Windows
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.
OSX
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), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

Download

Windows
Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Is it normal for a new Full Node server to repeatedly show Potential Sale Tip detected messages? What does this even mean. I surprisingly can't find anything with a solution on the internet. Please look at my log dump and give me an idea what to do. Im trying to run a full node in service to the net

Here is my log messages:

2019-11-14T03:05:38Z Bitcoin Core version v0.18.1 (release build)
2019-11-14T03:05:38Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures.
2019-11-14T03:05:38Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471
2019-11-14T03:05:38Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2019-11-14T03:05:38Z Default data directory /home/norman/.bitcoin
2019-11-14T03:05:38Z Using data directory /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z Config file: /media/norman/Seagate Expansion Drive/.bitcoin/bitcoin.conf (not found, skipping)
2019-11-14T03:05:38Z Using at most 125 automatic connections (1024 file descriptors available)
2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-11-14T03:05:38Z Using 8 threads for script verification
2019-11-14T03:05:38Z scheduler thread start
2019-11-14T03:05:38Z HTTP: creating work queue of depth 16
2019-11-14T03:05:38Z No rpcpassword set - using random cookie authentication.
2019-11-14T03:05:38Z Generated RPC authentication cookie /media/norman/Seagate Expansion Drive/.bitcoin/.cookie
2019-11-14T03:05:38Z HTTP: starting 4 worker threads
2019-11-14T03:05:38Z Using wallet directory /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z init message: Verifying wallet(s)...
2019-11-14T03:05:38Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2019-11-14T03:05:38Z Using wallet /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log
2019-11-14T03:05:39Z init message: Loading banlist...
2019-11-14T03:05:39Z Cache configuration:
2019-11-14T03:05:39Z * Using 2.0 MiB for block index database
2019-11-14T03:05:39Z * Using 8.0 MiB for chain state database
2019-11-14T03:05:39Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2019-11-14T03:05:39Z init message: Loading block index...
2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index
2019-11-14T03:05:39Z Opened LevelDB successfully
2019-11-14T03:05:39Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index: 0000000000000000
2019-11-14T03:05:39Z LoadBlockIndexDB: last block file = 0
2019-11-14T03:05:39Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2019-11-14T03:05:39Z Checking all blk files are present...
2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/chainstate
2019-11-14T03:05:40Z Opened LevelDB successfully
2019-11-14T03:05:40Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/chainstate: fb03fb54abfe4745
2019-11-14T03:05:40Z Loaded best chain: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03T18:15:05Z progress=0.000000
2019-11-14T03:05:40Z init message: Rewinding blocks...
2019-11-14T03:05:40Z init message: Verifying blocks...
2019-11-14T03:05:40Z block index 1516ms
2019-11-14T03:05:40Z init message: Loading wallet...
2019-11-14T03:05:40Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log
2019-11-14T03:05:40Z [default wallet] nFileVersion = 180100
2019-11-14T03:05:40Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total. Unknown wallet records: 0
2019-11-14T03:05:41Z [default wallet] Wallet completed loading in 449ms
2019-11-14T03:05:41Z [default wallet] setKeyPool.size() = 2000
2019-11-14T03:05:41Z [default wallet] mapWallet.size() = 0
2019-11-14T03:05:41Z [default wallet] mapAddressBook.size() = 0
2019-11-14T03:05:41Z mapBlockIndex.size() = 1
2019-11-14T03:05:41Z nBestHeight = 0
2019-11-14T03:05:41Z torcontrol thread start
2019-11-14T03:05:41Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there
2019-11-14T03:05:41Z Bound to [::]:8333
2019-11-14T03:05:41Z Bound to 0.0.0.0:8333
2019-11-14T03:05:41Z init message: Loading P2P addresses...
2019-11-14T03:05:41Z Loaded 253 addresses from peers.dat 16ms
2019-11-14T03:05:41Z init message: Starting network threads...
2019-11-14T03:05:41Z net thread start
2019-11-14T03:05:41Z dnsseed thread start
2019-11-14T03:05:41Z opencon thread start
2019-11-14T03:05:41Z init message: Done loading
2019-11-14T03:05:41Z addcon thread start
2019-11-14T03:05:41Z msghand thread start
2019-11-14T03:05:52Z Loading addresses from DNS seeds (could take a while)
2019-11-14T03:05:54Z 187 addresses found from DNS seeds
2019-11-14T03:05:54Z dnsseed thread exit
2019-11-14T03:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago)
2019-11-14T03:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2520 seconds ago)
2019-11-14T03:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3150 seconds ago)
2019-11-14T04:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3780 seconds ago)
2019-11-14T04:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 4410 seconds ago)
2019-11-14T04:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5040 seconds ago)
2019-11-14T04:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5670 seconds ago)
2019-11-14T04:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6300 seconds ago)
2019-11-14T05:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6930 seconds ago)
2019-11-14T05:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 7560 seconds ago)
2019-11-14T05:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8190 seconds ago)
2019-11-14T05:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8820 seconds ago)
2019-11-14T05:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 9450 seconds ago)
2019-11-14T05:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10080 seconds ago)
2019-11-14T06:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10710 seconds ago)
2019-11-14T06:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11340 seconds ago)
2019-11-14T06:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11970 seconds ago)
2019-11-14T06:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12600 seconds ago)
2019-11-14T06:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13230 seconds ago)
2019-11-14T06:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13860 seconds ago)
2019-11-14T07:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14490 seconds ago)
2019-11-14T07:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15120 seconds ago)
2019-11-14T07:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15750 seconds ago)
2019-11-14T07:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 16380 seconds ago)
2019-11-14T07:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17010 seconds ago)
2019-11-14T08:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17640 seconds ago)
2019-11-14T08:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18270 seconds ago)
2019-11-14T08:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18900 seconds ago)
2019-11-14T08:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 19530 seconds ago)
2019-11-14T08:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20160 seconds ago)
2019-11-14T08:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20790 seconds ago)
2019-11-14T09:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 21420 seconds ago)
2019-11-14T09:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22050 seconds ago)
2019-11-14T09:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22680 seconds ago)
2019-11-14T09:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23310 seconds ago)
2019-11-14T09:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23940 seconds ago)
2019-11-14T09:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 24570 seconds ago)
2019-11-14T10:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25200 seconds ago)
2019-11-14T10:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25830 seconds ago)
2019-11-14T10:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 26460 seconds ago)
2019-11-14T10:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27090 seconds ago)
2019-11-14T10:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27720 seconds ago)
2019-11-14T10:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28350 seconds ago)
2019-11-14T11:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28980 seconds ago)
2019-11-14T11:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 29610 seconds ago)
2019-11-14T11:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30240 seconds ago)
2019-11-14T11:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30870 seconds ago)
2019-11-14T11:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 31500 seconds ago)
2019-11-14T12:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32130 seconds ago)
2019-11-14T12:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32760 seconds ago)
2019-11-14T12:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 33390 seconds ago)
2019-11-14T12:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34020 seconds ago)
2019-11-14T12:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34650 seconds ago)
2019-11-14T12:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35280 seconds ago)
2019-11-14T13:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35910 seconds ago)
2019-11-14T13:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 36540 seconds ago)
2019-11-14T13:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37170 seconds ago)
2019-11-14T13:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37800 seconds ago)
2019-11-14T13:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 38430 seconds ago)
2019-11-14T13:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39060 seconds ago)
2019-11-14T14:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39690 seconds ago)
2019-11-14T14:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40320 seconds ago)
2019-11-14T14:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40950 seconds ago)
2019-11-14T14:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 41580 seconds ago)
2019-11-14T14:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42210 seconds ago)
2019-11-14T15:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42840 seconds ago)
2019-11-14T15:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 43470 seconds ago)
2019-11-14T15:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44100 seconds ago)
2019-11-14T15:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44730 seconds ago)
2019-11-14T15:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45360 seconds ago)
2019-11-14T15:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45990 seconds ago)
2019-11-14T16:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 46620 seconds ago)
2019-11-14T16:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47250 seconds ago)
2019-11-14T16:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47880 seconds ago)
2019-11-14T16:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 48510 seconds ago)
2019-11-14T16:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49140 seconds ago)
2019-11-14T16:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49770 seconds ago)
2019-11-14T17:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 50400 seconds ago)
2019-11-14T17:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51030 seconds ago)
2019-11-14T17:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51660 seconds ago)
2019-11-14T17:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52290 seconds ago)
2019-11-14T17:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52920 seconds ago)
2019-11-14T17:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 53550 seconds ago)
2019-11-14T18:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54180 seconds ago)
2019-11-14T18:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54810 seconds ago)
2019-11-14T18:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 55440 seconds ago)
2019-11-14T18:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56070 seconds ago)
2019-11-14T18:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56700 seconds ago)
2019-11-14T19:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 57330 seconds ago)


this goes on until I decided just to shut down server after 24 hours and the .dat blockchain file was stuck at 16MB in size. Seemed like going nowhere.
submitted by Alchemy333 to Bitcoin [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]

Bitcoind stuck in startup loading block index

Hi,
I have had bitcoin core running on a raspberry pi for about 4 month now (followed the raspibolt instructions from stadicus) and it worked fine until 3 days ago it suddenly stopped working. With bitcoin-cli blockchaininfo i got
error code: -28 Loading block index... 
or something similar. When a looked in the debug log file i saw this:
2019-08-29T16:48:08Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin/.bitcoin/database ErrorFile=/home/bitcoin/.bitcoin/db.log 2019-08-29T16:48:11Z init message: Loading banlist... 2019-08-29T16:48:11Z Cache configuration: 2019-08-29T16:48:11Z * Using 2.0 MiB for block index database 2019-08-29T16:48:11Z * Using 8.0 MiB for chain state database 2019-08-29T16:48:11Z * Using 90.0 MiB for in-memory UTXO set (plus up to 47.7 MiB of unused mempool space) 2019-08-29T16:48:11Z init message: Loading block index... 2019-08-29T16:48:11Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index 2019-08-29T16:48:11Z Opened LevelDB successfully 2019-08-29T16:48:11Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000 2019-08-29T16:54:14Z 2019-08-29T16:54:14Z Bitcoin Core version v0.18.1 (release build) 2019-08-29T16:54:14Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures. 2019-08-29T16:54:14Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471 2019-08-29T16:54:14Z Using the 'standard' SHA256 implementation 2019-08-29T16:54:15Z Default data directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z Using data directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z Config file: /home/bitcoin/.bitcoin/bitcoin.conf 2019-08-29T16:54:15Z Using at most 20 automatic connections (1024 file descriptors available) 2019-08-29T16:54:15Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-08-29T16:54:15Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-08-29T16:54:15Z Using 4 threads for script verification 2019-08-29T16:54:15Z scheduler thread start 2019-08-29T16:54:15Z HTTP: creating work queue of depth 16 2019-08-29T16:54:15Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-08-29T16:54:15Z HTTP: starting 4 worker threads 2019-08-29T16:54:15Z Using wallet directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z init message: Verifying wallet(s)... 2019-08-29T16:54:15Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-08-29T16:54:15Z Using wallet /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin/.bitcoin/database ErrorFile=/home/bitcoin/.bitcoin/db.log 2019-08-29T16:54:16Z init message: Loading banlist... 2019-08-29T16:54:16Z Cache configuration: 2019-08-29T16:54:16Z * Using 2.0 MiB for block index database 2019-08-29T16:54:16Z * Using 8.0 MiB for chain state database 2019-08-29T16:54:16Z * Using 90.0 MiB for in-memory UTXO set (plus up to 47.7 MiB of unused mempool space) 2019-08-29T16:54:16Z init message: Loading block index... 2019-08-29T16:54:16Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index 2019-08-29T16:54:16Z Opened LevelDB successfully 2019-08-29T16:54:16Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000 
After that there should follow a line about Loading the block index but it never appears.
It seems to be restarting without shutting down correctly, maybe it cannot find the block index? I tried reinstalling core, recreating the symlink to the hdd and resetting the service but nothing happened. Everytime it starts it gets stuck at the same point. It also takes an awful long time to stop bitcoind but i don't know if that is normal.
I found several people with similar problems online but noting helped so far. Has anyone had a similar problem in the past and found a solution to this?
submitted by BologneseWithCheese to Bitcoin [link] [comments]

[DEVELOPMENT] Bitcoind IPV4 testnet port (18332) is failing to bind

[SOLVED] Thanks for everyone that have helped!


Hello everyone, this is a development problem that I'm currently having. Since the BTC Development sub is kind of inactive and I couldn't find any rule contraty to posting about BTC Development, I'll try my luck in here as I'm hopeless already. I've posted on BTC Stack Exchange but no answers also. Please, don't get me wrong, I'm trying to solve this problem for many days now, I've looked up everywhere for this.
I'm new to Bitcoin development and I'm currently having difficulties trying to make RPC calls from a Docker Container to a Bitcoin-Core daemon running in a SSH server. I suppose that the problem may be with Firewall or closed ports, but I also do not know much about Network settings.
I'm using nbobtc/bitcoind-php package to make the RPC calls with HTTP requests, and it is running in a Docker container. I'm sure the container is functional and is not the problem.
So here's what happening: when I run bitcoind in root user (but normal also won't work) in my SSH server, the IPV4 testnet port seems to be not opened. This message goes up when I run bitcoind:
Binding RPC on address 0.0.0.0 port 18332 failed.
Here's what my bitcoin.conf looks like (I want to use testnet in here). I'm using Bitcoin-Core "subversion": "Satoshi:0.17.1".
server=1 debug=net txindex=1 testnet=1 rpcuser=userb rpcpassword=test test.rpcport=18332 # I've already tried allowing the IP these 3 ways: # rpcallowip=192.168.xx.xx # My machine's IP # rpcallowip=172.19.x.x/xx # Docker's NBOBTC container IP # rpcallowip=0.0.0.0/0 # Allowing all IP datadir=/home/bitcoin-dev/.bitcoin debuglogfile=/home/bitcoin-dev/.bitcoin/debug.log 
Here's what appears in debug.log right after I run Bitcoind:
2019-05-06T14:43:10Z Bitcoin Core version v0.17.1 (release build) 2019-05-06T14:43:10Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-05-06T14:43:10Z Assuming ancestors of block 0000000000000037a8cd3e06cd5edbfe9dd1dbcc5dacab279376ef7cfc2b4c75 have valid signatures. 2019-05-06T14:43:10Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000007dbe94253893cbd463 2019-05-06T14:43:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation 2019-05-06T14:43:10Z Default data directory /root/.bitcoin 2019-05-06T14:43:10Z Using data directory /home/bitcoin-dev/.bitcoin/testnet3 2019-05-06T14:43:10Z Using config file /home/bitcoin-dev/.bitcoin/bitcoin.conf 2019-05-06T14:43:10Z Using at most 125 automatic connections (1024 file descriptors available) 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 4 threads for script verification 2019-05-06T14:43:10Z scheduler thread start 2019-05-06T14:43:10Z Binding RPC on address 0.0.0.0 port 18332 failed. 2019-05-06T14:43:10Z HTTP: creating work queue of depth 16 2019-05-06T14:43:10Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-05-06T14:43:10Z HTTP: starting 4 worker threads 2019-05-06T14:43:10Z Using wallet directory /home/bitcoin-dev/.bitcoin/testnet3/wallets 2019-05-06T14:43:10Z init message: Verifying wallet(s)... 2019-05-06T14:43:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-05-06T14:43:10Z Using wallet wallet.dat 2019-05-06T14:43:10Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin-dev/.bitcoin/testnet3/wallets/database ErrorFile=/home/bitcoin-dev/.bitcoin/testnet3/wallets/db.log 2019-05-06T14:43:10Z net: setting try another outbound peer=false 2019-05-06T14:43:10Z Cache configuration: 2019-05-06T14:43:10Z * Using 2.0MiB for block index database 2019-05-06T14:43:10Z * Using 56.0MiB for transaction index database 2019-05-06T14:43:10Z * Using 8.0MiB for chain state database 2019-05-06T14:43:10Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-05-06T14:43:10Z init message: Loading block index... 2019-05-06T14:43:10Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/blocks/index 2019-05-06T14:43:10Z Opened LevelDB successfully 2019-05-06T14:43:10Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/blocks/index: 0000000000000000 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file = 161 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=755, size=30875345, heights=1513309...1514061, time=2019-04-29...2019-05-03) 2019-05-06T14:43:19Z Checking all blk files are present... 2019-05-06T14:43:20Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/chainstate 2019-05-06T14:43:20Z Opened LevelDB successfully 2019-05-06T14:43:20Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/chainstate: 2686d59caeb1917c 2019-05-06T14:43:20Z Loaded best chain: hashBestChain=00000000b3b6a5db140b6058b7abe5cb00d8af61afd2a237ae3468cd36e387fa height=927391 date=2016-09-08T15:04:00Z progress=0.311180 2019-05-06T14:43:20Z init message: Rewinding blocks... 2019-05-06T14:43:29Z init message: Verifying blocks... 2019-05-06T14:43:29Z Verifying last 6 blocks at level 3 2019-05-06T14:43:29Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2019-05-06T14:43:29Z No coin database inconsistencies in last 6 blocks (500 transactions) 2019-05-06T14:43:29Z block index 19450ms 2019-05-06T14:43:29Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex 2019-05-06T14:43:30Z Opened LevelDB successfully 2019-05-06T14:43:30Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex: 0000000000000000 2019-05-06T14:43:30Z init message: Loading wallet... 2019-05-06T14:43:30Z txindex thread start 2019-05-06T14:43:30Z [default wallet] nFileVersion = 170100 2019-05-06T14:43:30Z [default wallet] Keys: 2005 plaintext, 0 encrypted, 2005 w/ metadata, 2005 total. Unknown wallet records: 1 2019-05-06T14:43:30Z Syncing txindex with block chain from height 694205 2019-05-06T14:43:30Z [default wallet] Wallet completed loading in 123ms 2019-05-06T14:43:30Z [default wallet] setKeyPool.size() = 2000 2019-05-06T14:43:30Z [default wallet] mapWallet.size() = 7 2019-05-06T14:43:30Z [default wallet] mapAddressBook.size() = 4 2019-05-06T14:43:30Z mapBlockIndex.size() = 1515581 2019-05-06T14:43:30Z nBestHeight = 927391 2019-05-06T14:43:30Z torcontrol thread start 2019-05-06T14:43:30Z Bound to [::]:18333 2019-05-06T14:43:30Z Bound to 0.0.0.0:18333 2019-05-06T14:43:30Z init message: Loading P2P addresses... 2019-05-06T14:43:30Z Loaded 10420 addresses from peers.dat 36ms 2019-05-06T14:43:30Z init message: Loading banlist... 2019-05-06T14:43:30Z Loaded 0 banned node ips/subnets from banlist.dat 29ms 2019-05-06T14:43:30Z init message: Starting network threads... 2019-05-06T14:43:30Z net thread start 2019-05-06T14:43:30Z dnsseed thread start 2019-05-06T14:43:30Z addcon thread start 2019-05-06T14:43:30Z msghand thread start 2019-05-06T14:43:30Z init message: Done loading 2019-05-06T14:43:30Z opencon thread start 
After all that appears above, there are just "UpdateTip", "Requesting block", "received block" and "getdata" messages. (so the P2P port, 18333, works).

And here is when I netstat:

sudo netstat -nap|grep bitcoin|grep LISTEN
tcp 0 0 0.0.0.0:18333 0.0.0.0:* LISTEN 31185/bitcoind tcp6 0 0 :::18332 :::* LISTEN 31185/bitcoind tcp6 0 0 :::18333 :::* LISTEN 31185/bitcoind 
Thank you in advance!

PS: A few days ago I could make it work when running bitcoind with root user, but now even that won't solve the problem.
submitted by VicPietro to Bitcoin [link] [comments]

Chat_Report.25>2 - XL

[22:12] it's not like I'm going to be offended that someone feels that way [22:12] but it's not healthy to be a dick about it, and that's kind of the only way that I can think to be able to deal with it [22:12] I guess, that's not a bad way to think about it [22:12] if you're having trouble dealing with it [22:12] I guess I just have to accept that I am not an expert on that [22:12] but I do have the most basic understanding of the concept [22:12] and I have always known what a "dissociative" is [22:12] and that they are in fact a distinct psychological state [22:13] I didn't have to google to find out [22:13] and in fact I have been working on a book on dissociative phenomena for a number of years [22:13] you mean you were trying to find out what they were? [22:13] i just finished [22:14] i got the manuscript finished and submitted a copy [22:14] well, the "book" is still on your todo list [22:14] i'm very anxious to publish [22:15] what about the research? are you doing any research on it? [22:15] and yes [22:16] some, but the bulk of my effort is in trying to make sense of it [22:16] what are you doing to help us understand it? [22:16] and i have a blogpost of my own that goes into the background of the phenomenon [22:16] it would be great if you could tell us a little about it [22:16] it sounds as if the phenomenon has something to do with people who have had a life-altering experience [22:17] and that the thing they have experienced is so powerful that it is capable of completely altering a person's personality [22:17] (well, that and the fact that a person who had such an experience could have access to the internet) [22:17] i'm sorry, but why not just tell us about it in full detail, instead of asking me a bunch of question and letting me decide what to ask [22:18] it would be very convenient to you [22:18] if you hadnt decided not to talk about it until after i had. [22:18] if you want to know more, it's quite common for people with this kind of problem to share their stories. [22:18] (i'm not sure if its normal, but i can assure you its not something i wouldn't ever do to any of you) [22:19] so i don't know what you're implying by saying you're uncomfortable with talking about it? [22:19] i'm just saying that i'm not going to force you to talk about it just because you told me it was hard to talk about [22:19] ok. [22:20] so this is it: you must come here with me now [22:20] ok [22:20] and I'll go to the other rooms and meet everyone. [22:20] I want to make this a place for everyone [22:21] ok [22:21] i'll talk to you when i get there [22:21] OK, I need a little more detail [22:22] What's the plan for getting it into the house? [22:22] well i'll let you know when i get there [22:22] Ok, thanks [22:22] i'll be back around 12:30 and ill be there [22:23] I've sent you a PM for the key and I'll be waiting for you to talk to her [22:23] lol [22:23] *key [22:23] ouch [22:24] But that's just me [22:24] You can't just go and do it like that, y'know? [22:24] lol [22:25] but if it's just a matter of asking me nicely, i don't mind [22:25] just send it to me and i'll do it [22:25] if that's what you want [22:25] I've never asked you to do anything but that, and I know you haven't, but, that's my opinion [22:26] I mean, if it helps you out a little bit, maybe I could just... [22:26] Vorpas, that's okay. I mean, I think you're pretty amazing, I do, I do. I just don't know what you want to do with your life. I think I'd like to try and get the people that are in the game to understand the power and the importance of the community. I mean, when you're playing against, when you see a really bad player, you can tell that that player is having fun, that they are having fun playing the game, because they are making a lot of money, and then you can just understand that it would be fun to play, and there would be a lot of money to be made by just playing the game. And I think the players that are playing it, maybe they don't know what's happening, and maybe they have the wrong idea about it. But it's okay, I'm not going to judge them, it's their own opinion and they're free to believe whatever they want to believe. [22:27] But, I'm just gonna leave that part up to you. [22:27] Cool. [22:27] So I'm just gonna be, like, really happy for you, 'cause I know you've been putting a lot of work into this. [22:28] You are doing it so well! [22:28] And I really appreciate that, like, for the last few months, it's been a struggle to stay motivated enough to do this. [22:28] I am a bit concerned about how long this will take. [22:28] I am just going to say this, if I'm going to continue doing this, I want you guys to stay around. [22:29] Well, I would love to keep helping, but I'm not sure what my plans are at the moment. [22:29] If you were to make a donation, that would be fantastic [22:29] You know, the donations are very helpful. I just thought that it might be good to keep track of who donated what. [22:29] Vorpas_Jabwak, I can try to get someone to check if this was indeed you that made the donation? [22:29] Oh, yeah. [22:29] Thanks! [22:29] You've probably never received one before, but if you were, that would be awesome. [22:30] Just wanted to let you know the new version of Mumble is being released and working on the beta channel. [22:31] If you do have the software I'd love to hear some feedback. I have a lot of questions for it. [22:32] I have a lot of questions for it too, but it's a bit complicated so I might not get a chance to do that anytime soon. I'll make sure to get on that when it is ready. [22:33] I'm glad you like it, I know I really do. I love having an easier to use, but powerful, voice chat. [22:34] I'd really like to make some more changes to the system, and try it out as a whole. But right now it's pretty darned good. [22:35] Thanks Jak. :) [22:35] I'll try my best to keep them updated. [22:35] Ok, I'll let you know when I get to them, Jak [22:35] Sorry if I didn't keep up with you guys. [22:36] Haha, sorry. [22:36] I'll see you around, Jak [22:36] *takes off* [22:36] Sup everyone? [22:36] I'm out [22:36] *in [22:37] sup [22:37] Hey! [22:37] So are you guys all there yet? [22:37] :P [22:38] * Turoth sets mode: +b KhaosReigns [22:38] Oh! I thought you all quit on me [22:38] * Turoth sets mode: +b KhaosReigns+ [22:38] So uh, what's my problem? [22:38] I was hoping you'd tell me to stop [22:38] I was so upset [22:38] I'm sorry [22:38] I should have been better [22:39] I didn't mean to startle you [22:39] You've just always made me feel like I could take care of myself [22:39] I guess I didn't realize that it takes a lot of people to keep the lights on [22:40] I'm sorry, I've never been this shy around people [22:40] It's been such a long time [22:41] This whole situation is just a shock [22:41] I'm starting to feel really nervous [22:41] I have to go home now [22:42] Ok [22:42] I'll see you later [22:42] Ohh, bye [22:42] Take care [22:42] Yeah, it's a long way home [22:42] Have a nice night [22:42] Thanks for everything. I had fun. [22:42] night [22:42] I hope you have a good night. [22:42] Have a nice night. [22:42] Thanks. [22:42] Have a good night. [22:42] Good night [22:42] How is everyone? [22:42] I'm fine. [22:42] Tired, but fine. [22:42] Yeah. [22:43] i dont know what happened [22:43] Don't know yet, so I'm trying to get the details. [22:43] I went out to get food [22:43] got a pizza, was eating it when I was interrupted by my girlfriend [22:43] and she was saying she wanted to see me [22:43] i don't even know where i am right now [22:44] so she called me at work this morning and said 'well, i'm sorry i couldn't make it for you today', and i had to tell her 'okay' [22:45] i cant find her or the phone number or anything [22:45] i was just in the car, and she was in the kitchen [22:45] it must of been a while [22:45] i think she was off last night [22:46] that's funny that you would call me like that [22:46] then you should know that she has been off for a while [22:46] she said she was sick, and i think she said she was going to stay home and rest and it wasn't till today that i found out the truth [22:46] yeah it's a real bummer that it was a false alarm [22:46] like i said she could have possibly been sick but wasnt being honest about it [22:46] it is a big bummer that we wasted so much time on it, but it doesn't change that we found her body [22:46] yeah we know how the night went, we just dont know if she was really asleep when the phone rang [22:46] i just wish she would have just told us the truth instead of getting her feelings hurt [22:46] the real question is: why is it a phone? [22:46] that's all i got [22:46] so that's it [22:46] yeah and she's got to go find out if she's pregnant [22:46] and i guess there's no point in trying to hide the pregnancy [22:46] she said it was just a few days ago [22:46] wait what [22:46] maybe her parents are going to find it [22:46] ok [22:46] maybe if her parents find out she's pregnant [22:46] they'll just throw you out [22:46] they will [22:47] why do you think she was crying? [22:47] well, I mean, I know it's weird but [22:47] no, you're right [22:47] I mean, it was pretty strange [22:47] she just seemed, well [22:47] I don't think she could have known the guy or not [22:47] there's been plenty of reports of people getting "paedo" on the site [22:47] so it could have just been that her brain just caught on [22:47] like that one guy who was arrested last year for having a lot of chatroom porn [22:47] which is like a whole different thing [22:48] and it just happened to be in that section that she kept checking [22:48] yeah [22:48] like it's not like she has this huge fucking file of porn on her computer [22:48] so if it happens to be in one place, it's not like she's a big fucking voyeur [22:49] but still, she was watching the entire thing [22:49] yes, and that is probably why the guy stopped her [22:49] I can see your point of view [22:50] and it was also in that section that she just kept checking [22:50] yes, and I can say that she just seemed so interested in the guy that she wouldn't mind if he was watching [22:50] and that's not exactly the case with me either [22:50] but, if she's only interested in other men, then she's obviously gay [22:51] which is just something to remember [22:51] and she's so smart, but I can't see her getting on with me [22:51] she has a crush on me, but I don't even know where to start [22:52] I was at a party in NY, and someone I knew was talking to her, and they had been flirting. I didn't get a chance to respond, but I am a nice guy. She said she didn't want to talk about it any more. I am a nice guy, and I know that flirting is bad, but I also know that I like her and I think that there's a chance that it could go somewhere. I want to have a relationship with her, I don't really know where to start [22:52] you'd have to ask her yourself [22:52] but it seems like you don't have to [22:52] but if that's your only point she can't really say something else... [22:52] i think if you were to say you didn't want to have sex with her, you would lose her... [22:52] i'm not even really interested in that right now [22:53] it just seems like she wants to have sex with you [22:53] and is hoping that you'll say yes [22:53] i guess so... [22:53] but she doesn't seem to be trying to win your votes [22:53] maybe she's just trying to piss you off [22:54] and you don't have the time to argue with her [22:54] the internet is a bitch. [22:54] but i know she's just trying to be funny [22:54] and to make a point [22:54] so why can't i? [22:54] yeah [22:54] what do you mean? [22:54] jalockk: i've never seen a single one of these people [22:54] but i see them every day [22:54] and they say the same shit [22:54] we don't like the idea of them being taken out because they are not the ones we really are against [22:54] well i don't think we need to be very big to do that [22:54] but they are a part of it [22:55] the people that dont like us [22:55] the people that are behind all this [22:55] or just the people [22:55] not the people [22:55] it's the people that don't have an opinion [22:56] we should never let our ignorance define us [22:56] well we're doing it now [22:56] and it's not even funny [22:56] it's just sad [22:56] no it's a serious problem [22:56] it's not funny [22:56] and the truth is sadder [22:56] i don't understand why he hates himself so much [22:56] is it because of the death [22:56] or the lies he told [22:56] that's what im trying to figure out too [22:57] not that there is an obvious answer to why he does what he does [22:57] i think he is a pretty shitty person [22:57] the lies hurt more [22:57] i really really wish i could understand [22:58] that's why i'm here to explain the way out [22:58] if i explain it to you in words [22:58] well i don't know you [22:58] i have to explain it to you in a way that makes sense to you [22:58] in english [22:58] and that's how [22:58] this whole thing starts with a picture of a woman [22:58] holding up a phone with the words "HELLO" on the screen [22:58] it's a picture of me [22:58] It's a pic of me in a hat [22:58] and i'm in the hat [22:58] which isnt me [22:58] i'm the one with the hat [22:59] i wear a hat to hide my face [22:59] and when i say this i don't really say "i'm the hat" [22:59] i say "i'm the hat" [22:59] oh okay [22:59] ok let me get this straight [22:59] if we're talking about the "why" [22:59] what the actual, fucking, fuck [22:59] why did she do it [22:59] the "when" part I'm not clear about [22:59] i'd assume that's the part we're discussing [22:59] ok i'm getting out of this [22:59] but yeah the "what" [22:59] yeah [22:59] and it seems like the "how" [22:59] isnt really a big deal [22:59] i think it is [22:59] the fact that we all agree on what it is [22:59] and are people who say its a big deal really saying it on the op? or is it on the op, and people who say its a big deal are just assholes? [22:59] we're pretty fucking certain it's not a big deal [22:59] if you're not convinced [22:59] please say so in the thread [22:59] i'd love to hear your arguments [22:59] the op is just a big deal, it is a huge deal, we've done the math, and there is no downside [22:59] we've actually spent the last 2 days talking about it [22:59] it doesn't really have any consequences on us, as we won't do anything stupid [22:59] we'd be better off not having it in the first place [22:59] it doesn't really matter [22:59] I know I'm a bit biased but... this whole thing feels like it's been set up to be solved by trolls [22:59] not to mention that we can already see a lot of the stuff they are talking about, they just don't want to talk about it [22:59] it's not like they would go back to it and say "we got this, so why don't you shut up!" [22:59] It's frustrating to see them try and keep this open... but it's a shame to see what happens when they fail. [22:59] I love how it seems like the more they try to keep it secret, the more they are forced to keep it open [22:59] :O [23:00] well we don't know yet what they have planned for the next phase but there's a lot of work to be done [23:00] no one knows what we'll be doing now, so if we do everything right, we could actually end up with some more power [23:00] i'm not saying we'll get that, we'll have to wait and see [23:00] maybe i'm just a bit optimistic [23:00] or maybe i'm just stupid? [23:01] i dunno i don't care anymore [23:01] just wait it out [23:01] no time to waste [23:01] let them make it as easy as possible [23:01] and keep an eye on what they say next [23:01] well that could mean some kind of delay [23:01] like they are going to push it out [23:01] well, that's their prerogative [23:01] what they said a month ago is what they're saying now? [23:01] Ok, I'm gonna leave this here: http://en.wikipedia.org/wiki/Woot\_com [23:01] but I can't find the link right now. :( [23:01] it's been posted to the website of the US government [23:01] so you know it's legit [23:02] oh. Ok. [23:02] so it's legit [23:02] ok. [23:02] So, we're not really at the point of doing the whole, "we have a solution" thing, so much as a "we have a general idea" thing. [23:03] i think that's what we're going for [23:03] the problem, in my experience, is that it's hard for people to really figure out what you're talking about. I would assume that with a lot of the work that's going on there are some people who are really good at solving it. I'm not. [23:04] i mean, it is sort of in the realm of "people" [23:04] that we've been able to make progress on this, so i am assuming you have done a lot of that work? [23:04] i would have to ask someone else how they are doing it [23:05] in terms of the algorithms they use [23:05] or other tools [23:06] http://bitinfocharts.com/blocksize-and-bitcoin-future-chart/ [23:06] but i don't know how you guys did it in a way that is also practical [23:06] no problem. it's been done. [23:06] just don't expect anyone to do it for you [23:07] i'll have to ask you that one [23:07] if you have a better idea please post it here and we'll discuss it [23:07] but if we don't have a better idea then we don't know what you're talking about [23:08] it's not our fault they are doing it [23:08] they do it to us [23:08] we don't have any other solution [23:08] but they have access to your wallet [23:09] you are paying for access to it [23:09] so they are getting access [23:09] you are paying to keep their access to your wallet [23:10] I am paying to keep your access to your wallet [23:10] they are making you do it [23:10] i am paying them to keep access to my wallet [23:10] that is what i have been told to do [23:10] what i was told to do [23:10] i am also paying them for this access [23:10] I am not paying to keep access to my wallet for them [23:11] I am paying them for this access [23:11] to mine in their account for them [23:12] well, that was fun [23:12] oh, that's too bad [23:12] it's all for you [23:12] you are mining it for them [23:12] so much for that [23:12] but then you are the victim of a scam, not me [23:13] oh, ok [23:13] it's a good thing you are aware now, because that is a great way to get scammed [23:13] so what's up? [23:14] ok [23:14] we've been looking for you for a while now and we can't find you. [23:14] ok. so what's up? [23:15] the last time you were on IRC we started doing our own investigation and you didn't know where you were or how long you'd been gone [23:15] so we thought that since you weren't there anymore that it had to be a scam [23:15] which it is [23:15] http://www.youtube.com/watch?v=h0bzvq8Fx7Y [23:15] yeah. but it doesnt tell you that [23:15] you gotta ask [23:15] you got that right [23:16] alright. let me see if I can find something similar [23:16] https://www.youtube.com/watch?v=nUZpwWg1g\_s [23:16] http://www.youtube.com/watch?v=pFwX4jJYqhI [23:16] i have a different one [23:16] http://www.youtube.com/watch?v=h\_h2rK4V7ZM [23:16] it is shorter [23:16] it has less information [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http ://www.youtube.com [23:17] http://www.youtube.com [23:17] http://www.youtube.com [23:17] ok I have been listening [23:18] let me hear your response to the question "why are you talking on the radio?" [23:18] "The answer to that is because I was just trying to communicate with the community" [23:18] why do you think it's a good idea to try to communicate with the community? [23:18] you don't need to ask, we're going to have a drink [23:18] let me get you something to drink [23:18] i will be back later [23:18] in like 2 mins [23:18] can you hear me? [23:18] yes, I can hear you [23:18] are you a bot? [23:18] no, i am human [23:19] oh [23:19] good to know [23:19] you're just very very drunk, i guess [23:19] just go to sleep [23:20] you just have to go to sleep [23:20] and it'll be over by the morning [23:20] i'll wait [23:21] but it was only a few hours ago [23:21] and i said it wouldn't be [23:21] so i'm guessing you can't help it [23:21] so is it over? [23:21] not sure if you can help it or not, but if you have any questions or suggestions, do send them to me [23:22] but yeah, there is no immediate threat at all [23:22] but i dont know what to do at the moment, maybe i should move everything to another server [23:22] but i have the code and the rpc server [23:22] you can do that? [23:22] yeah, just let me know what you want [23:22] okay, how do i run rpc from my localhost? [23:22] just open up a terminal and run "rpcuser -i 127.0.0.1" [23:22] okay [23:22] let's go back to maint [23:22] I'm going to add another option to run the wallet (wallet.conf) as a non root user [23:22] I'm going to add rpcuser as an option, and rpcpassword as a second option [23:22] and then run as root [23:23] okay, so what do i want the output of this command to be [23:23] the output should be something like "1" [23:23] what should i put in the command? [23:23] for now, i'll just type it out [23:23] rpcuser=myuser rpcpassword=mypassword [23:23] run_in_remote.sh --port=21 --listen=127.0.0.1:2222 [23:23] you should be able to type that in [23:23] and it should go through ok. you should see something like this: [23:23] [00:11] [23:21] [00:20] [23:23] what do i do to make the next post more visible? [23:23] can someone send a screenshot of the reddit post to me? [23:23] @emmaw [23:23] i can give you my address in case you want to send something there [23:23] you're welcome [23:23] well im going to have to ask the mod team that question now [23:23] thanks for the offer, we'll think about it [23:23] :) [23:23] i'll give you the link soon, also [23:23] but please don't PM me about that :) [23:24] sure [23:24] i'll leave it with you [23:24] but i'll check it again [23:24] later [23:25] so is this the one with the red pill? [23:25] or redpilled? [23:25] redpilled [23:25] redpilled [23:25] ok [23:25] thanks [23:25] I got the link [23:25] yeah [23:25] this is a very big deal [23:25] I'm in a hurry, so I can't see the link, but what you're doing is a lot more powerful than most of what I've ever heard before [23:26] http://www.youtube.com/watch?v=Hjf7hKQ6uQg [23:26] that's a pretty long video [23:26] yeah [23:26] there's lots of cool stuff in there, too [23:26] it has a nice flow to it, too [23:26] so, you have to remember: don't focus on the structure, focus on the content [23:27] i see [23:27] not sure if thats just me though [23:27] its a good thing to have [23:27] not sure why the devs don't do it, but there are some good reasons [23:27] yeah i got your point [23:27] im happy to make it easy for you [23:27] and for other devs to do it as well [23:27] (at least a few of the devs are here to see this) [23:27] we could even get a group of devs to go talk to the press and try to have the topic in a few of the big gaming sites [23:28] this could be a great way to get the game out and to everyone else [23:28] and then we can move onto the next thing [23:28] if this is successful I think we can even get some of the smaller ones to try it [23:28] also if any of the other big ones do it this will get them in on the process
submitted by ShadowWolf525 to WeirdGeneratedStories [link] [comments]

I need help, somebody can review my setup?

I want to install a node machine to be able to receive payments in BTC mainnet and BTC LN, for a webshop and in store. So after testing different solutions I decided to go in this case for a solution using docker for BTC node and LN node, adding a woocommerce plugin for that LN node. The machine is an Ubuntu 18.04. I tested with docker c-lightning + spark wallet, works fine, the plugin for woocommerce also works fine. The restriction is that for c-lightning there is ONLY this Spark wallet and I would want to use/test also other wallets connected to my node, including RTL for a better management. So that's why I wanted to try LND.
So please, if is somebody here willing to review my docker-compose file? I get error connecting the lnd so maybe I miss something in this setup. I have days and days reading githubs documentation, testing versions, but seems that for lnd is not that simple as it was with c-lightning docker.
Here is my yml setup:
version: '2'
services: bitcoind: image: nicolasdoriedocker-bitcoin:0.17.0 container_name: bitcoind environment: BITCOIN_EXTRA_ARGS: | printtoconsole=1 rpcallowip=::/0 server=1 txindex=1 rpcuser=btcnodeuser rpcpassword=btcnodepwd externalip=myIP zmqpubrawblock=tcp://127.0.0.1:28332 zmqpubrawtx=tcp://127.0.0.1:28333 expose: - "8332" ports: - "0.0.0.0:8333:8333" volumes: - "./bitcoin:/data"
lnd: image: lightninglabs/lnd container_name: lndbtc restart: always command: >- lnd --debuglevel=info --alias="myalias" --color="#990099" --bitcoin.node=bitcoind --bitcoind.dir=./bitcoin --bitcoind.rpchost=127.0.0.1 --bitcoind.rpcuser=mybtcnodeuser --bitcoind.rpcpass=mypwd --bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332 --bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333 --bitcoin.active --bitcoin.mainnet --rpcuser=mybtcnodeuser --rpcpassword=mypwd --rpclisten=0.0.0.0:10009 --restlisten=0.0.0.0:8080 --datadir=./lightningd/data --logdir=./lightningd/logs --externalip=myIP:9735 --tlsextraip=myIP --maxpendingchannels=10 --minchansize=100000 ports: - "9735:9735" - "10009:10009" volumes: - "./lightningd:/data" - "./bitcoin:/data"
submitted by btc_freelance to Bitcoin [link] [comments]

SOLO Mining setup instructions. CCminer Nevermore and QT / CLI wallet.

First, I do not solo mine myself, so I can not confirm if this setup pays. I do not have the hash to even consider trying. I can confirm ccminer gets work from the wallet and cards get hot. Enjoy!
 
EDIT: Setup tested on coin with lower difficulty. I got paid.
 
 
 
rpcuser=user rpcpassword=pass rpcbind=192.168.1.100:8766 rpcallowip=192.168.1.1/24 server=1 
 
Replace user, pass and ips to match your setup. You can make up your own usepass. You need to use the same ones when configuring ccminer. 192.168.1.100 needs to be changed to the IP of the machine running the wallet. This setup allows connections from all ips in the range 192.168.1.X
 
 
:mine ccminer.exe -a x16r -o http://192.168.1.100:8766 -u user -p pass -i 21 --no-longpoll --no-getwork --no-stratum --coinbase-addr=YOUR_RVN_ADDRESS_HERE ping -n 30 127.0.0.1 goto :mine 
 
Replace user, pass and IP to match your setup. The IP is to the machine running the wallet and the usepass are the ones you set in the first config file. And don't forget to add your RVN-address.
 
 
If you found this useful any donation would be welcome RVN: RFmtFb9GdZHvbvBW5hYB3s9VezJxeSfnz3  
   
 
#!/bin/bash until /path/to/ccminer -a x16r -o http://192.168.1.100:8766 -u user -p pass -i 21 --no-longpoll --no-getwork --no-stratum --coinbase-addr=YOUR_RVN_ADDRESS_HERE; do ping -c 30 127.0.0.1 done 
 
Replace user, pass and IP to match your setup. The IP is to the machine running the wallet and the usepass are the ones you set in the first config file. And don't forget to add your RVN-address.
 
 
 
If you found this useful any donation would be welcome RVN: RFmtFb9GdZHvbvBW5hYB3s9VezJxeSfnz3
    
Found errors or got suggestions? - please leave a comment or send me a message.
 
Useful links:   https://github.com/brian112358/nevermore-minereleases https://github.com/brian112358/nevermore-minewiki/Solo-mining https://bitcoin.stackexchange.com/questions/118/how-much-bitcoin-will-i-mine-right-now-with-hardware-x https://rvnstats.info/
submitted by fdoving to Ravencoin [link] [comments]

Lightning node on Windows - testing, get not connected

Ok after testing BTCPay, C-Lightning, LND on Ubuntu I said ok let's try also the Windows implementation, is just few clicks and done (as it is promoted).
So I followed this github guide that actually send you to this one.
OK, started Bitcoin-core client on Windows 7 x64, with an already synced data folder. Empty bitcoin.conf (none of guides says how to configure the conf file). Wait until the client is full synced. And then launched the windows-node-launcher (from a subfolder inside Bitcoin folder). All good, started slowly and a small popup appeared in systray saying Bitcoin node is syncing. Reviewed the config of Bitcoin and LND through that little app in systray and saw that bitcoin.conf was already filled with some settings. Didn't change anything. After 1 day (with the bitcoin blockchain already synced), the systray popup still says that is syncing and have a red dot. In the tutorial says that we have to leave it to sync until is blue and then green.
I said, ok maybe it has more things to do. So I open that LND Output link, to see what is going on... And I see that LND is not well. Says: 2019-04-06 21:11:29.772 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default 2019-04-06 21:11:29.772 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-04-06 21:11:29.774 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8 2019-04-06 21:11:29.808 [INF] RPCS: password RPC server listening on 127.0.0.1:10009 2019-04-06 21:11:29.808 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080 2019-04-06 21:11:29.808 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it. 2019-04-06 21:11:32.673 [INF] LNWL: Opened wallet 2019-04-06 21:11:33.183 [INF] LTND: Primary chain is set to: bitcoin unable to create chain control: unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:36.087 [INF] LTND: Shutdown complete unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:39.229 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
Now the bitcoin.conf have this: printtoconsole=1 rpcallowip=::/0 whitelist=0.0.0.0/0 datadir=C:\Users\Admin\AppData\Roaming\Bitcoin prune=0 txindex=1 server=1 disablewallet=0 timeout=6000 rpcuser=user rpcpassword=defaultxzxxxxx zmqpubrawblock=tcp://127.0.0.1:18502 zmqpubrawtx=tcp://127.0.0.1:18503 dbcache=2408
And LND.conf have this: (#) Auto-Generated Configuration File (#) Node Launcher version 6.0.2 debuglevel=info restlisten=127.0.0.1:8080 rpclisten=127.0.0.1:10009 tlsextraip=127.0.0.1 listen=127.0.0.1:9735 alias=aliasme color=#00aa7f bitcoin.active=1 bitcoin.node=bitcoind bitcoind.rpchost=127.0.0.1:8332 bitcoind.rpcuser=user bitcoind.rpcpass=defaultxxxxx bitcoind.zmqpubrawblock=tcp://127.0.0.1:18502 bitcoind.zmqpubrawtx=tcp://127.0.0.1:18503
So what is going on here? I will have to wait indefinitely? Somebody can give some help or explanation? Is this LND node working on Windows Server 2008 or 2012?
submitted by Mr--Robot to Bitcoin [link] [comments]

How to install any QT-Wallet on the Raspberry Pi / Pi3B+

Hello and welcome to my first tutorial. Today I will show you how to install almost any QT-wallet on the RaspberryPi. I hope this tutorial will help you. I use the BankSocietyCoin in this tutorial, you can change it also to your fav. Coin.

Install Raspbian , *Buster produced a lot of failures on my system while compiling Wallets*
(my version: https://downloads.raspberrypi.org/raspbian/images/raspbian-2018-03-14/ )
Run the following commands:

Change Swap Size of the Rasp:

sudo nano /etc/dphys-swapfile
change to CONF_SWAPSIZE=2048
press: ctrl o Enter and ctrl x
enable the swap file with its new size:
sudo dphys-swapfile setup
sudo dphys-swapfile swapon
----------
Install Required Dependencies:

apt-get update
sudo apt-get install git build-essential libtool autotools-dev autoconf pkg-config libssl-dev libcrypto++-dev libevent-dev libminiupnpc-dev libgmp-dev libboost-all-dev devscripts libdb++-dev libsodium-dev
and
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libcrypto++-dev libminiupnpc-dev qt5-default
----------
Install bitcoin PPA files for the compiling process:

cd /etc/apt/sources.list.d/
sudo nano bitcoin.list
paste to following line:
deb-src http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu artful main
press: ctrl o Enter and ctrl x
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv C70EF1F0305A1ADB9986DBD8D46F45428842CE5E
sudo apt-get update
----------
Install working libssl:

cd && sudo apt-get remove libssl-dev
sudo nano /etc/apt/sources.list
change stretch to jessie
press: ctrl o Enter and ctrl x
sudo apt-get update
sudo apt-get install libssl-dev
sudo apt-mark hold libssl-dev
sudo apt-mark hold libssl1.0.0
sudo nano /etc/apt/sources.list
Change jessie" back to stretch
press: ctrl o Enter and ctrl x
sudo apt-get update
----------

Compile and Install BerkeleyDB 4.8.30 :

wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
sudo tar -xzvf db-4.8.30.NC.tar.gz
cd db-4.8.30.NC/build_unix
sudo ../dist/configure --enable-cxx
sudo make
sudo make install
export CPATH="/uslocal/BerkeleyDB.4.8/include"
export LIBRARY_PATH="/uslocal/BerkeleyDB.4.8/lib"
----------

The wallet:

(my way) mkdir wallets , cd wallets
git clone https://github.com/RGPickles/BankSocietyCoin
cd BankSocietyCoin
chmod 755 src/leveldb/build_detect_platform
chmod 755 src/secp256k1/autogen.sh
cd src/
make -f makefile.unix
./societyd
* for qt wallet*
cd ..
qmake
make
edit society.conf in .society
(rpcuser=SomeCoolRandomUsername
rpcpassword=SOMETHINawesomeYOUdontHaveToRemember
rpcconnect=127.0.0.1
save.
./society-qt
----------

Have fun!
for a Beer - Donations ;)
SOCI - Si6V7EwnJqzmFiNGHSbXrtWUXKH6F4EFm3
BTC - 1HpGF4wMzztpJ4KT4o2ySFvnLJ4gCoYaV5
LTC - LS22MgY9G4KbaKhkR5dFi995MbcQhuyDXW
ETH - 0x6b5EdC3e58Fd84a40aa942964690adA91C398075
TRX - TKBpktt5QQ9WV57QjonQrGr1vmKLCVQBL6

13.07.2019 DennisHilk




**********
if error (makefile.unix:200: obj/rpcclient.o] appears)
[This first step is necessary because you will get linking errors if you don't remove the old Boost library]
sudo apt remove --purge --auto-remove libboost-dev libboost-thread-dev libboost-system-dev libboost-atomic-dev libboost-regex-dev libboost-chrono-dev
mkdir boost
cd boost
wget https://dl.bintray.com/boostorg/release/1.64.0/source/boost_1_64_0.tar.gz
tar xfz boost_1_64_0.tar.gz (can take rly long, dont worry)
cd boost_1_64_0/
./bootstrap.sh
./b2 stage threading=multi link=static --with-thread --with-system
sudo ./b2 install threading=multi link=static --with-thread --with-system
cd ../../
nano .bash_profile
export LIBS="-L/home/YOURS/boost/boost_1_64_0/stage/lib"
export CPPFLAGS="-I/home/YOURS/boost/boost_1_64_0"
cd society root
make clean
cd src
sudo make -f makefile.unix

(if bignum error)
sudo apt-get install libgmp-dev
or delete opensll and reinstall as above.
submitted by dennishilk to u/dennishilk [link] [comments]

Soo after almost 3 months of setting up I have my own LN full node running on RP3

Soo after almost 3 months of setting up I have my own LN full node running on RP3
I have been eager to try LN mainnet since the very beginning of it. I've found out about lnd, eclair, zap and other wallets but every scenario I tried to use it failed because of critical issues:
  • eclair does not really constitute a wallet, it's more like a credit card - you can send money but not receive it
  • lnd is okay, but requires a server and tons of resources for maintaining a full node, can't be used securely, efficiently and mobily at the same time
  • zap offers some cloud wallet (in testnet!) by default, this is a serious misunderstanding of my cryptoanarchy needs
  • web wallets - ah, forget it
So I've decided to use my Raspberry Pi with a very old laptop HDD attached (200GB so the pruning function has to be used) to create a backend wallet service and zap desktop (temporarily!) as my frontend control panel.
https://preview.redd.it/0vcq147887q11.png?width=1024&format=png&auto=webp&s=7bb6eccdd4110a857e5af0400acc2d7e1ee7ee85
Setting up Pi is easy, lots of tutorials over the internet, not gonna discuss it here. Then I had to obtain bitcoind (current rel: bitcoin-0.17.0-arm-linux-gnueabihf.tar.gz) and lnd (lnd-linux-armv7-v0.5-beta.tar.gz), create a bitcoin technical user, deploy the tools, configure and install new systemd services and go through the configs. This is a tricky part, so let's share:
# Generated by https://jlopp.github.io/bitcoin-core-config-generato # This config should be placed in following path: # ~/.bitcoin/bitcoin.conf # [core] # Set database cache size in megabytes; machines sync faster with a larger cache. Recommend setting as high as possible based upon machine's available RAM. dbcache=100 # Keep at most  unconnectable transactions in memory. maxorphantx=10 # Keep the transaction memory pool below  megabytes. maxmempool=50 # Reduce storage requirements by only storing most recent N MiB of block. This mode is incompatible with -txindex and -rescan. WARNING: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, 1 = allow manual pruning via RPC, greater than 550 = automatically prune blocks to stay under target size in MiB). prune=153600 # [network] # Maintain at most N connections to peers. maxconnections=40 # Use UPnP to map the listening port. upnp=1 # Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit. maxuploadtarget=5000 # [debug] # Log IP Addresses in debug output. logips=1 # [rpc] # Accept public REST requests. rest=1 # [wallet] # Do not load the wallet and disable wallet RPC calls. disablewallet=1 # [zeromq] # Enable publishing of raw block hex to 
. zmqpubrawblock=tcp://127.0.0.1:28332 # Enable publishing of raw transaction hex to
. zmqpubrawtx=tcp://127.0.0.1:28333 # [rpc] # Accept command line and JSON-RPC commands. server=1 # Username and hashed password for JSON-RPC connections. The field comes in the format: :$. RPC clients connect using rpcuser=/rpcpassword= arguments. You can generate this value with the ./share/rpcauth/rpcauth.py script in the Bitcoin Core repository. This option can be specified multiple times. rpcauth=xxx:yyy$zzz
Whooaa, this online config generator is really helpful, but I still had to manually correct a few things. The last line is obviously generated by rpcauth.py, I disabled the wallet functionality as lnd is going to take care of my funds. ZMQ is not available to the network so only my LND can use it, RPC usage I still have to think through a little, in general I would like to have my own block explorer some day but also be safe from any hacking attempts (thus I would need at least 2 RPC ports/user accounts - one for lnd, one for block explorer frontend). No ports open on firewall at this time, only UPnP is active and gently opens 8333 for block/tx transfers.
Now, synchronizing the blockchain took me time from mid-July to early September... The hard drive is really slow, also my external HDD drive has some trouble with its A/C adapter so Pi was getting undervoltage alerts all the time. Luckily, it is just downclocking when it happens and slowly but steadily synchronized the whole history. After all, I'm not paying even $5 monthly for a VPS, it is by design the cheapest hardware I could use to set up my LN wallet.
When bitcoind was ready (I've heard some stories about btcd but I don't trust this software yet, sorry), it's time to configure lnd.conf:
[Application Options] debuglevel=trace rpclisten=0.0.0.0:10009 externalip=X.X.X.X:9735 listen=0.0.0.0:9735 alias=X color=#XXXXXX [Bitcoin] bitcoin.active=1 bitcoin.mainnet=1 bitcoin.node=bitcoind [Bitcoind] bitcoind.rpchost=127.0.0.1 bitcoind.rpcuser=X bitcoind.rpcpass=X bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332 bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333 
Here I've had to XXX a little more fields, as not only the bitcoind RPC credentials are stored here, but also my node's public information (it should be illegal to run nodes without specifically selected color and alias!). It is public (and I had to open port 9735 on my firewall), but not necessarily connected to my reddit account for most of the adversaries, so let's keep it this way. In fact, I also see a security vulnerability here: my whole node's stability depends on the IP being static. I could swap it for a .tk domain but who can tell if the bad guys won't actively fight DNS system in order to prevent global economic revolution? As such, I would rather see node identification in LN based on a public key only with possible *hints* of last-known-ip-address but the whole discovery should be performed by the nodes themself in a p2p manner, obviously preventing malicious actors from poisoning the network in some way. For now, I consider the IP stability a weak link and will probably have to pay extra Bitcoin TX fees when something happens to it (not much of a cost luckily!).

https://preview.redd.it/hjd1nooo77q11.png?width=741&format=png&auto=webp&s=14214fc36e3edf139faade930f4069fc31a3e883
Okay then, lnd is up and running, had to create a wallet and give it a night for getting up to speed. I don't know really what took it so long, I'm not using Windows nor 'localhost' in the config so the issues like #1027 are not the case. But there are others like #1545 still open so I'm not going to ponder much on this. I haven't really got any idea how to automatically unlock the wallet after Pi restart (could happen any time!), especially since I only tried to unlock it locally with lncli (why would I enter the password anywhere outside that host?), but let's say that my wallet will only be as stable as my cheap hardware. That's okay for the beta phase.
Finally, zap-desktop required me to copy tls.cert and admin.macaroon files to my desktop. If my understanding of macaroon (it's like an authentication cookie, that can later be revoked) is correct then it's not an issue, however it would be nice to have a "$50 daily limit" macaroon file in the future too, just to avoid any big issues when my client machine gets stolen. Thanks to this, I can ignore the silly cloud-based modes and have fully-secure environment of my home network being the only link from me to my money.
https://preview.redd.it/11bw3dgw47q11.png?width=836&format=png&auto=webp&s=b7fa7c88d14f22441cbbfc0db036cddfd7ea8424
Aaand there it is. The IP took some time to advertise, I use 1ml.com to see if my node is there. The zap interface (ZapDesktop-linux-amd64-v0.2.2-beta.deb) lacks lots of useful information so I keep learning lncli syntax to get more data about my new peers or the routes offered. The transactions indeed run fast and are ridiculously cheap. I would really love to run Eclair with the same settings but it doesn't seem to support custom lnd (why?). In fact, since all I need is really a lncli wrapper, maybe it will be easy to write my own (seen some web gui which weighs 700MB after downloading all dependencies with npm - SICK!). Zap for iOS alpha test registration is DOWN so I couldn't try it (and I'm not sure if it allows custom lnd selection), Zap for Android doesn't even exist yet... I made a few demo transactions and now I will explore all those fancy t-shirt stores as long as the prices are still in "early investor" mode - I remember times when one could get 0.001 BTC from a faucet...
https://preview.redd.it/42sdyoce57q11.png?width=836&format=png&auto=webp&s=7ec8917eaf8f3329d51ce3e30e455254027de0ee
If you find any of the facts presented by me false, I am happy to find out more in the discussion. However what I did I did mostly for fun, without paying much attention to the source code, documentation and endless issue lists on github. By no means I claim this tutorial will work for you but I do think I shared the key points and effort estimations to help others decide if they want a full-node LN client too. I'm also interested in some ideas on what to do with it next (rather unlikely that I will share my lnd admin.macaroon with anyone!) especially if it gives me free money. For example, I can open 1000 channels and start earning money from fees, although I no longer have more Bitcoins than the LN capacity yields... I will probably keep updating the software on my Pi until it leaves beta phases and only then will pour more money inside. I'm also keen on improving the general security of my rig and those comments I will answer more seriously.
submitted by pabou to Bitcoin [link] [comments]

Step by step in staking Redd with Raspberry Pi 3

Before I start, I would like to pay complete credits to these two guys :)
https://www.reddcointalk.org/topic/2679/reddcoin-staking-via-ubuntu-mate-on-raspberry-pi-3-model-b-march-2018 (most of my steps, if not all, are from this link)
https://github.com/joroob/reddcoin/blob/mastedoc/build-arm.md
All the steps I am writing is ABSOLUTELY NECESSARY, please don't try to skip it because I did, and it doesn't work.
step 1: get a Raspberry Pi B https://www.raspberrypi.org/products/#buy-now-modal
step 2: make sure you get proper power supply 5v 2A - the Pi will mine, it will need sufficient power. Regular USB samsung charger will not work.
step 3: get proper micro SD card (SanDisk for example) 32Gb++
step 4: USB + Mouse keyboard
step 5: flash micro SD card with Ubuntu MATE
Download Ubuntu Mate image: https://ubuntu-mate.org/raspberry-pi/
Download Etcher: https://etcher.io
After finishing downloading, use Etcher to write/flash the image on micro SD card
After this, your SD card contains Ubuntu MATE OS.
step 6: Place SD Card into Raspberry Pi 3 and start it up. You should be able to see Ubuntu OS! Congrats!
step 7: Connect to wifi or internet cable (internet is better and faster)
step 8: OPTIONAL - turn off UI OS, so that things will work faster
Open XTerminal:
sudo systemctl disable lightdm.service (to turn UI off) 
in case you want to turn UI on again, run this:
sudo systemctl start lightdm.service (to turn UI on) 
step 9: install all dependencies
sudo apt-get update && sudo apt-get install git build-essential libqt4-dev libprotobuf-dev protobuf-compiler libtool autotools-dev autoconf libssl-dev libboost-all-dev wget pkg-config sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install db4.8 sudo apt-get install libminiupnpc-dev sudo apt-get install libqrencode-dev Reboot 
step 10: add additional RAM (sort of) in case the App need it, this is call "Create Swap file"
sudo fallocate -l 1G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile echo ‘/swapfile none swap sw 0 0’ | sudo tee -a /etc/fstab 
step 11: Build Berkeley Database
wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz tar xfvz db-4.8.30.NC.tar.gz cd db-4.8.30.NC cd build_unix ../dist/configure --enable-cxx make sudo make install 
step 11.5: Set BerkeleyDB path
export CPATH="/uslocal/BerkeleyDB.4.8/include" export LIBRARY_PATH="/uslocal/BerkeleyDB.4.8/lib" export LD_LIBRARY_PATH=/uslocal/BerkeleyDB.4.8/lib/ 
step 12: Build Reddcoin Wallet
---download source code ---- only source from joroob/reddcoin will work because some stweak was needed for ARM CPU
cd ~ git clone https://github.com/joroob/reddcoin.git 
---build reddcoin ----
cd reddcoin ./autogen.sh ./configure --with-gui=no --disable-tests cd src make sudo make install 
If you finish this, you are in a great position!!!
step 13: Create reddcoin configuration file
cd ~ mkdir .reddcoin && cd .reddcoin nano reddcoin.conf rpcuser=YOUR OWN USERNAME, YOU DONT NEED TO REMEMBER THIS, MAKE IT AS LONG AS YOU WANT rpcpassword=YOUR OWN PASS WORD, YOU DONT NEED TO REMEMBER THIS, MAKE IT AS LONG AS YOU WANT 
step 14: Use bootstrap
(At this point, you had a running reddcoin daemon, now you can start staking. But syncing the full chain takes long time.)
cd ~/.reddcoin wget https://github.com/reddcoin-project/reddcoin/releases/download/v2.0.1.2/bootstrap.dat.xz xz -d bootstrap.dat.xz 
step 15: start the reddcoin daemon service cd ~/reddcoin/src ./reddcoind -daemon
After this, you can test if the daemon is working, by perform this command: ./reddcoin-cli getblockcount
step 16: if your app is not able to sync, it is probably the firewall issue with OS, run this to allow port 45444 (used by Reddcoin) and redo step 15
sudo iptables -I INPUT 1 -i eth0 -p tcp --dport 45444 -j ACCEPT sudo iptables -A OUTPUT -p tcp --dport 45444 -j ACCEPT 
step 17: open BEER and enjoy! This is a MUST or the daemon will stop working! I am not kidding!
step 18: Actually, i forgot to mention you need to execute this command for the wallet to stake:
reddcoind walletpassphrase $yourpassword 9999999 true 
ADDITIONAL REMARKS:
From my PC: I am using putty to execute the command, winSCP to monitor the file location on raspberry.
Moving Red Coins out of exchange really a big move, start with normal wallet, don't start with this tutorial :) Ever since I move my coins out of exchange, I am free from all of the ups and downs! Really!
So guys and gals, Redd On!
UPDATE 18 Mar: my first stake has arrived after 6 days staking :)
In case you want to tip me: RaF3TeWqgTzAdnaZQffnsxS74dag13zsAY
Edit 1: Format stuff
Edit 2: Add step 18 to execute staking command.
Edit 3: In case you don't want to compile the source code, you can download my compile version here: https://github.com/hieplenet/reddcoin/releases/tag/v2.0.0.0 (but doing this, you should be aware of the risk of me changing source code for my benefit - I don't change any thing, but you should be cautious, this is the internet :) )
submitted by hieplenet to reddCoin [link] [comments]

Help wanted: Network problem with Bitcoin Core Full Node and Samourai Wallet.

Hi all

I have port forwarding set up for TCP 8333 and TCP 8332.
Firewall says:
8332 ALLOW Anywhere
8332 (v6) ALLOW Anywhere (v6)
...
8333 ALLOW Anywhere # bitcoin mainnet
8333 (v6) ALLOW Anywhere (v6) # bitcoin mainnet

I'm able to reach 8333 using https://www.yougetsignal.com/tools/open-ports/ - but 8332 is closed .

here is the RPC config from ~/.bitcoin/bitcoin.conf
# Connection settings
rpcuser=XXX # user replaced
rpcpassword=XXX # password replaced
rpcallowip=192.168.X.X # IP replaced
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333
rpcbind=0.0.0.0
rpcport=3882
rpcallowip=127.0.0.1
rpcallowip=X.X.X.X # public IP replaced

netstat -na |grep 8332
tcp 0 0 127.0.0.1:283320.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:83320.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:28332127.0.0.1:44296ESTABLISHED
tcp 0 0 127.0.0.1:44296127.0.0.1:28332ESTABLISHED
tcp6 0 0 ::1:8332 :::* LISTEN


I try to use my node in combination with the awesome Samourai Wallet. https://samourai.kayako.com/article/40-configure-your-node-for-samourai-wallet

submitted by xavierfiechter to Bitcoin [link] [comments]

solution for error message when setting up lightning network & wallet

I was getting this error when unlocking my newly created lightning wallet:
"Primary chain is set to: bitcoin unable to create chain control: unable to connect to bitcoind: status code: 401, response: "
I double and triple checked everything and couldn't understand why I couldn't connect. It was extremely frustrating. I googled around and finally found this post:
https://github.com/lightningnetwork/lnd/issues/924

It says that some people were getting that error from having a ! or # or @ characters in their rpcpasswords.

My old rpcpassword was:
gnF#cC%7Aen7^Sb

The pound sign, percentage sign and up arrow characters were messing up my lightning wallets ability to connect.
After I changed my rpcpassword to not include any special characters it connected just fine w/o the error on the first try.

I spent like 3 days pissed off and and completely clueless as to why my wallet was having connection issues, so I thought I'd share this for anyone else who might be in the same situation.

Good ,luck ya'll.

submitted by Rmr1981 to Bitcoin [link] [comments]

How can I make test-net?

I've tried to make test-net for mining pool test. There's no information or seed node for testnet. and find reddit and add testnet node to conf, but, testnode ip is very old , not working now. Is there latest information for make testnet? thanks,
(update)
my config also have a testnet=1 addnode=nz.nutty.one:20888 from searched community .
-- here's logs --
2018-03-12 13:38:46 Bitcoin version v0.14.2.5-6ad93ba 2018-03-12 13:38:46 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2018-03-12 13:38:46 Assuming ancestors of block ff983c72147a81ac5b8ebfc68b62b39358cac4b8eb5518242e87f499b71c6a51 have valid signatures. 2018-03-12 13:38:49 Default data directory /home/nomp/.myriadcoin 2018-03-12 13:38:49 Using data directory /home/nomp/nomp_chaindata/myriadcoin-test/testnet 2018-03-12 13:38:49 Using config file /home/nomp/nomp_chaindata/myriadcoin-test/myriadcoin.conf 2018-03-12 13:38:49 Using at most 125 automatic connections (1024 file descriptors available) 2018-03-12 13:38:49 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements 2018-03-12 13:38:49 Using 2 threads for script verification 2018-03-12 13:38:49 scheduler thread start 2018-03-12 13:38:49 HTTP: creating work queue of depth 16 2018-03-12 13:38:49 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation. 2018-03-12 13:38:49 HTTP: starting 4 worker threads 2018-03-12 13:38:49 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2018-03-12 13:38:49 Using wallet wallet.dat 2018-03-12 13:38:49 init message: Verifying wallet... 2018-03-12 13:38:51 CDBEnv::Open: LogDir=/home/nomp/nomp_chaindata/myriadcoin-test/testnet/database ErrorFile=/home/nomp/nomp_chaindata/myriadcoin-test/testnet/db.log 2018-03-12 13:38:51 Bound to [::]:10898 2018-03-12 13:38:51 Bound to 0.0.0.0:10898 2018-03-12 13:38:51 Cache configuration: 2018-03-12 13:38:51 * Using 2.0MiB for block index database 2018-03-12 13:38:51 * Using 8.0MiB for chain state database 2018-03-12 13:38:51 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2018-03-12 13:38:51 init message: Loading block index... 2018-03-12 13:38:51 Opening LevelDB in /home/nomp/nomp_chaindata/myriadcoin-test/testnet/blocks/index 2018-03-12 13:38:59 Opened LevelDB successfully ... 2018-03-12 13:43:39 keypool added key 100, size=100 2018-03-12 13:43:42 keypool added key 101, size=101 2018-03-12 13:43:43 keypool reserve 1 2018-03-12 13:43:44 keypool keep 1 2018-03-12 13:43:50 wallet 282608ms 2018-03-12 13:43:50 setKeyPool.size() = 100 2018-03-12 13:43:50 mapWallet.size() = 0 2018-03-12 13:43:50 mapAddressBook.size() = 1 2018-03-12 13:43:51 UpdateTip: new best=0000017ce2a79c8bddafbbe47c004aa92b20678c354b34085f62b762084b9788 height=0 version=0x00000002 algo=0 (sha256d) log2_work=17.678071 tx=1 date='2014-02-20 06:06:33' progress=0.000003 cache=0.0MiB(0tx) 2018-03-12 13:43:51 mapBlockIndex.size() = 1 2018-03-12 13:43:51 Failed to open mempool file from disk. Continuing anyway. 2018-03-12 13:43:51 nBestHeight = 0 2018-03-12 13:43:51 torcontrol thread start 2018-03-12 13:43:51 AddLocal(x.x.2x.x:10898,1) 2018-03-12 13:43:51 Discover: IPv4 enp3s0: 175.2x.x.x 2018-03-12 13:43:51 init message: Loading addresses... 2018-03-12 13:43:51 ERROR: Read: Failed to open file /home/nomp/nomp_chaindata/myriadcoin-test/testnet/peers.dat 2018-03-12 13:43:51 Invalid or missing peers.dat; recreating 2018-03-12 13:43:52 init message: Loading banlist... ... 2018-03-12 13:55:05 addcon thread start 2018-03-12 13:55:05 opencon thread start 2018-03-12 13:55:05 dnsseed thread start 2018-03-12 13:55:05 net thread start 2018-03-12 13:55:05 connect() to 75.19.27.27:20888 failed after select(): Connection refused (111) 2018-03-12 13:55:06 connect() to 75.19.27.28:20888 failed after select(): Connection refused (111) 2018-03-12 13:55:16 Loading addresses from DNS seeds (could take a while) 2018-03-12 13:55:17 3 addresses found from DNS seeds 2018-03-12 13:55:17 dnsseed thread exit 2018-03-12 13:55:17 connect() to 75.19.27.27:20888 failed after select(): Connection refused (111) 2018-03-12 13:55:18 connect() to 75.19.27.28:20888 failed after select(): Connection refused (111) 2018-03-12 13:55:22 connect() to 75.19.27.27:20888 failed after select(): Connection refused (111) 2018-03-12 13:55:23 connect() to 75.19.27.28:20888 failed after select(): Connection refused (111) 2018-03-12 1 ....
same forever until today. can't encrease test node heights.
submitted by trustfarmhub to myriadcoin [link] [comments]

04-07 09:48 - 'Lightning node on Windows - testing, get not connected' (self.Bitcoin) by /u/Mr--Robot removed from /r/Bitcoin within 845-855min

'''
Ok after testing BTCPay, C-Lightning, LND on Ubuntu I said ok let's try also the Windows implementation, is just few clicks and done (as it is promoted).
So I followed this [github guide]1 that actually send you to [this one]2 .
OK, started Bitcoin-core client on Windows 7 x64, with an already synced data folder. Empty bitcoin.conf (none of guides says how to configure the conf file). Wait until the client is full synced. And then launched the windows-node-launcher (from a subfolder inside Bitcoin folder). All good, started slowly and a small popup appeared in systray saying Bitcoin node is syncing. Reviewed the config of Bitcoin and LND through that little app in systray and saw that bitcoin.conf was already filled with some settings. Didn't change anything. After 1 day (with the bitcoin blockchain already synced), the systray popup still says that is syncing and have a red dot. In the tutorial says that we have to leave it to sync until is blue and then green.
I said, ok maybe it has more things to do. So I open that LND Output link, to see what is going on... And I see that LND is not well. Says: 2019-04-06 21:11:29.772 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default 2019-04-06 21:11:29.772 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-04-06 21:11:29.774 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8 2019-04-06 21:11:29.808 [INF] RPCS: password RPC server listening on 127.0.0.1:10009 2019-04-06 21:11:29.808 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080 2019-04-06 21:11:29.808 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it. 2019-04-06 21:11:32.673 [INF] LNWL: Opened wallet 2019-04-06 21:11:33.183 [INF] LTND: Primary chain is set to: bitcoin unable to create chain control: unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:36.087 [INF] LTND: Shutdown complete unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:39.229 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
Now the bitcoin.conf have this: printtoconsole=1 rpcallowip=::/0 whitelist=0.0.0.0/0 datadir=C:\Users\Admin\AppData\Roaming\Bitcoin prune=0 txindex=1 server=1 disablewallet=0 timeout=6000 rpcuser=user rpcpassword=defaultxzxxxxx zmqpubrawblock=[link]3 zmqpubrawtx=[link]4 dbcache=2408
And LND.conf have this: (#) Auto-Generated Configuration File (#) Node Launcher version 6.0.2 debuglevel=info restlisten=127.0.0.1:8080 rpclisten=127.0.0.1:10009 tlsextraip=127.0.0.1 listen=127.0.0.1:9735 alias=aliasme color=#00aa7f bitcoin.active=1 bitcoin.node=bitcoind bitcoind.rpchost=127.0.0.1:8332 bitcoind.rpcuser=user bitcoind.rpcpass=defaultxxxxx bitcoind.zmqpubrawblock=[link]3 bitcoind.zmqpubrawtx=[link]4
So what is going on here? I will have to wait indefinitely? Somebody can give some help or explanation? Is this LND node working on Windows Server 2008 or 2012?
'''
Lightning node on Windows - testing, get not connected
Go1dfish undelete link
unreddit undelete link
Author: Mr--Robot
1: g*thub.c*m/light**ng**o*e*-users/no**-launc**r 2: me*ium.*o**lig*tn**g-p*wer-users/w*n**ws-m**os-l**ht*i*g-ne*work-2*4bd5034340 3: 127.0.0**:1*5*2 4: 127*0.0**:185*3 5: 1**.0.0*1:185*2 6: 12*.0**.1:*8503
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

Error when running a bitcoin core node: Corruption: not an sstable (bad magic number)

I try to run a bitcoin core node using 180 GB of blockchain data that I have in a hard drive:
bitcoind.exe --datadir=I:\Bitcoin\Bitcoin_core\Bitcoin\blockchain 
But I get the error
Error: Error: A fatal internal error occurred, see debug.log for details 
Debug.log looks like this:
2018-07-18 19:36:03 Bitcoin Core version v0.16.0 (release build) 2018-07-18 19:36:03 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2018-07-18 19:36:03 Warning: Reducing -maxconnections from 9999 to 1015, because of system limitations. 2018-07-18 19:36:03 Assuming ancestors of block 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0 have valid signatures. 2018-07-18 19:36:03 Setting nMinimumChainWork=000000000000000000000000000000000000000000f91c579d57cad4bc5278cc 2018-07-18 19:36:03 Using the 'sse4' SHA256 implementation 2018-07-18 19:36:03 Using RdRand as an additional entropy source 2018-07-18 19:36:05 Default data directory C:\Users\Pedro FR\AppData\Roaming\Bitcoin 2018-07-18 19:36:05 Using data directory G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain 2018-07-18 19:36:05 Using config file G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain\bitcoin.conf 2018-07-18 19:36:05 Using at most 1015 automatic connections (2048 file descriptors available) 2018-07-18 19:36:05 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2018-07-18 19:36:05 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2018-07-18 19:36:05 Using 4 threads for script verification 2018-07-18 19:36:05 scheduler thread start 2018-07-18 19:36:05 libevent: getaddrinfo: nodename nor servname provided, or not known 2018-07-18 19:36:05 Binding RPC on address ::1 port 8332 failed. 2018-07-18 19:36:05 HTTP: creating work queue of depth 16 2018-07-18 19:36:05 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation. 2018-07-18 19:36:05 HTTP: starting 4 worker threads 2018-07-18 19:36:05 Using wallet directory G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain 2018-07-18 19:36:05 init message: Verifying wallet(s)... 2018-07-18 19:36:05 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2018-07-18 19:36:05 Using wallet wallet.dat 2018-07-18 19:36:05 CDBEnv::Open: LogDir=G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain\database ErrorFile=G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain\db.log 2018-07-18 19:36:05 Cache configuration: 2018-07-18 19:36:05 * Using 56.2MiB for block index database 2018-07-18 19:36:05 * Using 8.0MiB for chain state database 2018-07-18 19:36:05 * Using 385.8MiB for in-memory UTXO set (plus up to 2861.0MiB of unused mempool space) 2018-07-18 19:36:05 init message: Loading block index... 2018-07-18 19:36:05 Opening LevelDB in G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain\blocks\index 2018-07-18 19:36:05 Opened LevelDB successfully 2018-07-18 19:36:05 Using obfuscation key for G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain\blocks\index: 0000000000000000 2018-07-18 19:36:29 LoadBlockIndexDB: last block file = 1259 2018-07-18 19:36:29 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=215, size=130126593, heights=522250...522561, time=2018-05-11...2018-05-13) 2018-07-18 19:36:29 Checking all blk files are present... 2018-07-18 19:36:29 LoadBlockIndexDB: transaction index enabled 2018-07-18 19:36:29 Opening LevelDB in G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain\chainstate 2018-07-18 19:36:30 Opened LevelDB successfully 2018-07-18 19:36:30 Using obfuscation key for G:\Bitcoin\Bitcoin_core\Bitcoin\blockchain\chainstate: f686f3dcea7b64ab 2018-07-18 19:36:30 Loaded best chain: hashBestChain=0000000000000000003f9855f4abee6286e4ff677d366db7b0f24c414caf49cc height=518349 date=2018-04-15 17:14:57 progress=0.916016 2018-07-18 19:36:30 init message: Rewinding blocks... 2018-07-18 19:36:36 Corruption: not an sstable (bad magic number) 2018-07-18 19:36:36 *** System error while flushing: Database corrupted 2018-07-18 19:36:36 Error: Error: A fatal internal error occurred, see debug.log for details 2018-07-18 19:36:36 Shutdown requested. Exiting. 2018-07-18 19:36:36 Shutdown: In progress... 2018-07-18 19:36:36 scheduler thread interrupt 2018-07-18 19:36:36 Corruption: not an sstable (bad magic number) 2018-07-18 19:36:36 *** System error while flushing: Database corrupted 2018-07-18 19:36:36 Error: Error: A fatal internal error occurred, see debug.log for details 2018-07-18 19:36:36 Corruption: not an sstable (bad magic number) 2018-07-18 19:36:36 *** System error while flushing: Database corrupted 2018-07-18 19:36:36 Error: Error: A fatal internal error occurred, see debug.log for details 2018-07-18 19:36:36 Shutdown: done 
I don't remeber messing around with the blockchain data. I think the error first occurred when I was trying to run a node on a Linux machine, I get the same error on both devices. Would be great if I didn't have to download the blockchain all over again.
submitted by johnturtle to BitcoinBeginners [link] [comments]

The Crypto Times v 0.01– The Bitcoin Civil War, Proof of Stake, How to stake your PIVX wallet Recover your Bitcoin Core wallet password with btcrecover ... Guide to the Best Bitcoin Wallets of 2019 - YouTube WINDOWS Tutorial - HempCoin KMD Wallet In Linux VIRTUAL BOX (UPDATED) Bitcoin Vault Desktop Wallet Tutorial - English - YouTube

A new bitcoin-wallet tool is now distributed alongside Bitcoin Core’s other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how ... No you can define the rpcuser and rpcpassword in the bitcoin.conf file itself. Usually it is commented , you can uncomment the line rpcuser and rpcpassword and input your username and password which will be used when you will be connecting to your bitcoind through HTTP JSON RPC. ./bin/bitcoind -testnet \ -rpcuser=myrpc01 -rpcpassword=password01. By running above command, Bitcoin Core will run using the default port 18332. All files (block files, wallet database, etc) will be located in the default datadir ~/.bitcoin/testnet3. ls ~/.bitcoin/testnet3 Now, Work With Your Own Wallet Bitcoind – a daemon program that implements the Bitcoin protocol, is controlled through the command line. It is one of the main components of the Bitcoin network node software. Bitcoin software exists in two forms: a GUI application and a background application (daemon on Unix, service on Windows). The private key is not stored in bitcoind's built-in wallet. That is, private / public key pair was created by vanity utility (for example). ... ./bitcoin-cli -rpcpassword=123456 signrawtransaction ...

[index] [2553] [9360] [26849] [20151] [8113] [22149] [34786] [15783] [456] [16921]

The Crypto Times v 0.01– The Bitcoin Civil War, Proof of Stake, How to stake your PIVX wallet

1: FILE - UNLOCK WALLET 2: ENTER PASSWORD 3: TOOLS - DEBUG CONSOLE 4: TYPE COMMAND: dumpprivkey yourwalletaddresshere 5. your Private key will be revealed, please back this up. DO NOT SHARE WITH ... Today I take a look at Electrum – a fully featured desktop Bitcoin wallet for those that want to get the most flexibility and customization out of their tran... Tips: Bitcoin – 1LN7YM2Zfe3NtgnxUcfwDTTstfzhshPHjv Ethereum – 0x070a05dbe7187baca1d3753868481677ce6aac03 PIVX – DHxPJmjA7H6dFHQ2JbJF4TmFj5dTTUJr3G Dash – XnM... Bitcoin Vault is developed to provide an extra level of security based on a three-private-key security structure. It features all the convenience of Bitcoin ... Sending and Receiving Bitcoin on your Blockchain Wallet https://www.blockchain.com

#