litecoin - How to connect to RPCPORT=9332 via LAN ...

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]

I built lightningd, and now am running it, and running into this problem where bcli seems to be returning wrong json (with bitcoind running too)

So I have confirmed that the bitcoin-cli.exe is being invoked, with the arguments shown. But I am not sure why this error is coming up. If I run bitcoin-cli.exe from command line, I can easily get replies for command like getblockchaininfo, which confirms that bitcoind is running.

Here is what I get as output of lightningd command:
2020-08-30T17:35:53.634Z INFO plugin-bcli: bitcoin-cli initialized and connected to bitcoind. /uslocal/bin/../libexec/c-lightning/plugins/bcli error: bad response to getrawblockbyheight (bad 'result' field), response was {"jsonrpc":"2.0","id":8,"error":{"code":400,"message":"bitcoin-cli.exe -datadir=G:\\\\.bitcoin -rpcconnect=127.0.0.1 -rpcport=8332 -rpcuser=... -rpcpassword=... getblockhash 646000: bad JSON: bad blockhash (00000000000000000001ef19be9c9879c6e9aa6241a096f543109e2a34397936\r\n)"} } 
Not sure why I am seeing this problem.
Update: I got it running. Now I see this
2020-08-30T23:45:47.611Z INFO plugin-bcli: bitcoin-cli initialized and connected to bitcoind. 2020-08-30T23:45:48.728Z INFO lightningd: -------------------------------------------------- 2020-08-30T23:45:48.729Z INFO lightningd: Server started with public key 03c7505d1ac56441f234025cd348743cddff147f9356e6296820d5e95d1a56b29d, alias GREENTOLL (color #03c750) and lightningd v0.9.0-197-gdd8cd81-modded 
I've no clue what I am doing, but will continue digging more.
submitted by parakite to lightningnetwork [link] [comments]

Did the BCH Testnet chain split?

I'm seeing explorers report different block heights:
DNS P2P Peers themselves are all over the place:
2020-05-19T20:51:34Z New outbound peer connected: version: 70015, blocks=1378460, peer=0 2020-05-19T20:51:35Z New outbound peer connected: version: 70015, blocks=1364809, peer=1 2020-05-19T20:51:35Z New outbound peer connected: version: 70015, blocks=1379769, peer=2 2020-05-19T20:51:47Z New outbound peer connected: version: 70015, blocks=1378460, peer=4 2020-05-19T20:51:53Z New outbound peer connected: version: 70015, blocks=1327928, peer=6 2020-05-19T20:52:05Z New outbound peer connected: version: 70015, blocks=1364809, peer=7 2020-05-19T20:52:06Z New outbound peer connected: version: 70015, blocks=1327928, peer=8 2020-05-19T20:52:08Z New outbound peer connected: version: 70015, blocks=1379769, peer=9
Seeing some problems with block 1,348,461 being marked invalid:
2020-05-19T21:08:41Z ERROR: invalid header received 2020-05-19T21:08:41Z ERROR: AcceptBlockHeader: block 0000000099f5509b5f36b1926bcf82b21d936ebeadee811030dfbbb7fae915d7 is marked invalid
Block in question: http://testnet.imaginary.cash/block/0000000099f5509b5f36b1926bcf82b21d936ebeadee811030dfbbb7fae915d7
Using Bitcoin ABC Daemon version v0.21.7-unk on 2 separate testnet nodes, hitting the same invalid block
EDIT: Don't know what happened with testnet as the BitcoinABC daemon updates itself nightly, but a block was marked invalid on both nodes. The fix for me: bitcoin-cli -rpcconnect=10.0.0.1 -rpcport=8000 --testnet --rpccookiefile=/my/cookie/is/here/.cookie reconsiderblock 0000000099f5509b5f36b1926bcf82b21d936ebeadee811030dfbbb7fae915d7
submitted by xref to btc [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]

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]

Config file on lightningd (docker)

Hello,

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

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

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

Thank you for the help :)
submitted by samovar3112 to lightningnetwork [link] [comments]

a public bitcoind connects to?

I tried to connect to rpc.blockchain.info. instructions at https://www.blockchain.com/es/api/json_rpc_api
bitcoin-cli --host=rpc.blockchain.info --port=443 --rpcuser= --rpcpassword= getinfo doesn't work
Any working sample? Thanks!
submitted by FarBother to btc [link] [comments]

Creating and address and private key via the command line

I installed the Bitcoin Core a few weeks ago (still haven't managed to fully synchronize) with a view to learning a bit more about the technical side of Bitcoin.
Yesterday I read a post which said that (once you had installed the Core) you could create a Bitcoin address via the command line, so I thought I would try it out.
I found it difficult to find a bare bones explanation of the minimum required to get it working so, having finally gotten it working, I though I would post mine here.
What you will need:
1) A .bat file containing the following:
"C:\Program Files\Bitcoin\daemon\bitcoind.exe" -daemon 
2) A .bat file containing the following:
echo off for /f "delims=" %%i in ('"C:\Program Files\Bitcoin\daemon\bitcoin-cli.exe" getnewaddress') do set outAddress=%%i echo "Address = " %outAddress% for /f "delims=" %%i in ('"C:\Program Files\Bitcoin\daemon\bitcoin-cli.exe" dumpprivkey %outAddress%') do set outKey=%%i echo "Key = " %outKey% pause 
3) A text file called bitcoin.conf with the following contents:
server=1 rpcuser=pick_your_own_user rpcpassword=pick_your_own_password rpctimeout=30 rpcport=8332 rpcconnect=127.0.0.1 noirc=0 minimizetotray=0 
The steps are:
...and that should be it
If bitcoin.conf already exists, you should be able to skip step 2 and just do steps 3 and 4.
Obviously you will need to change the paths to match your own setup (and put your own user and password in the .conf file - they can be anything, but should be unique)
Hope this helps somebody get up and running quickly.
submitted by alarm_test to Bitcoin [link] [comments]

Blackcoin Wallet Passphrase mistyped - Bruteforce

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

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

server=1

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

rpcuser=user
rpcpassword=password

Listen for RPC connections on this TCP port:

rpcport=15715

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

running on another host using this option:

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

Incakoin the future is made on inca gold

Join us on irc #incakoin
https://c-cex.com/?p=nka-btc https://yobit.net/en/trade/NKA/BTC https://www.cryptopia.co.nz/Exchange
https://bter.com/voting#NKA =https://askcoin.net/votes https://www.cryptsy.com/coinvotes
Bootstrap https://mega.nz/#!IgIz3YjY!kRPNG8k8bpU-okErDleJltREwne911DAK404eOMZVCg windows wallet https://mega.nz/#!8gASQCKL!vtZjluErDnoIELf8nf_5jjyTPEQjO6ZUMYnYdCsKuQw mac wallet https://mega.nz/#!NhQFEB4b!26azpMMkwtg5O__1FZteq_5HD0w3l-M7p83PCD8aoFQ linux wallet https://drive.google.com/file/d/0B8Qm4jpV4FrQcTY0bTduRUJQYnc https://github.com/madross/incakoin.git http://www.incakoin.info/paperwallet/index.html
server=1 rpcuser=user rpcpassword=password rpcconnect=127.0.0.1 rpcport=17420 addnode=23.94.38.192 addnode=162.243.222.64 addnode=188.226.155.94 addnode=85.25.214.107 addnode=88.198.12.244 addnode=167.114.156.87 addnode=72.91.220.80 addnode=91.69.20.223 addnode=195.34.100.2 addnode=5.79.169.91 addnode=104.12.86.201 addnode=98.213.71.104 addnode=61.62.44.179 addnode=50.32.122.14
https://cryptocloudhosting.org/order http://www.itopshop.net
Help us build out twitter audience while also being able to earn some extra coins along the way https://twitter.com/Incakoin1/status/647191250144206848 simply follow the tasks provided in the tweet Android wallet 100000 Paper Wallet Design 100000
http://incakoin.info
https://twitter.com/Incakoin1
https://www.cryptopia.co.nz/BlockExplorer?coin=NKA http://23.94.38.192:3001
http://nka.multi-pool.info/
http://23.94.38.192/wheel
http://23.94.38.192/faucet
INCAKOIN. Creating a SAFE and environmentally sound future for the children of the world :D
Many newcomers and some of the early adopters might be asking themselves “Why INCAKOIN? Whats so special about incakoin?”….. Well I’ll tell you.
1.) Early adoption.
INCAKOIN is rounding post beta. INCAKOIN’S dev’s have worked out the bugs. INCA survived a 51% attack which we are very proud of doing. Checkpoint servers have been installed. What this means is even IF incakoin were to experience a 51% attack developers can rewind the blockchain ( The platform in which carries out transactions on the network. ) back to the time of attack and recommence mining right before the time of the attack. A fix for the malleability issue bitcoin has been facing. CRUCIAL due to the rouge nature of data mining. The server acts as a SAFEGUARD so that no one group or entity can control the blockchain or all the coin supply. This is a very good thing and is unique to INCAKOIN.. The Proof of Stake give’s INCA the ability to verify transactions and new coin creation with older mature coins. Another fix for the transaction malleability exploit facing previous forms of CryptoCurrencies. Genius if you ask me. Good work DEV’s. Most SECURE CryptoCurrency. Making us MORE secure than Bitcoin by LIGHT YEARS :D
2.) Fair supply
We came into the game with the question “Why would 21 Million of something be fair for a GLOBAL economy?” Answer: It wouldn’t. Bitcoin is not a fairly distributed currency. 21 million units divisible by how ever many times it can be divided will still NOT be fairly distributed currency. Especially with Bitcoin early adopters holding many of the coins already. Its like saying “I have money because I’m SMARTER than you. I had INVESTED when you didn’t know and I didn’t bother to TELL YOU because it was INSIDE information”…. If this was Wall Street bitcoin would be Enron. Its unforgivable. INCAKOIN however is very transparent about its activities. We feel as though that withholding information about us or how we operate is not something we are willing to do. That’s why we remain transparent. Keeps us honest. 190 million INCA coins are a very reasonable number as far as supply of digital gold. This number better reflects the worlds supply of gold if we choose for it to be the basis of our backing. The network is setup for rapid growth and hashrate. So jump right in and mine with us. You’ll make a FORTUNE :D
3.) Because we CARE :)
We care about the world and people. INCAKOIN is friendly to the environment. With our model of mining we use way less electricity and we do so with pride. Being a Hybrid Proof of Stake and Proof of Work coin enables us to use way less electricity than the BEAST that Bitcoin has become. It is our obligation as responsible adults to create a future that we would want our children and our children’s children to grow up in when we are gone. To do anything else would be SELFISH! We encourage everyone who mines INCAKOIN to be as eco friendly as possible. Solar, Wind, and Water powered energy if you have the means.
On that note that’s what make us special. INCAKOIN is advanced and a hybrid of CryptoCurrency. We have the fix already in place that Bitcoin lacks concerning transaction malleability. We are the future and the future is made of INCA gold.
German https://bitcointalk.org/index.php?topic=953564 Chinese https://bitcointalk.org/index.php?topic=956999.0 Greek https://bitcointalk.org/index.php?topic=1196361.0 Spanish https://bitcointalk.org/index.php?topic=1203497.0
here is the address of the community wallet all coins in this addy are for giveaways bountys over social media and for development costs no coins will leave this wallet unless community has decided that we should move coins each time we require coins out the wallet we will post a poll so community decides if we should make this transaction
these coins are being escrowed by the user blockhunter i do not have access to the wallet at any given time
NhMhvFj3XGfgEurmKiBfgS3FbxjpAsHM9X
submitted by incakoin- to CryptoCurrency [link] [comments]

GUIDE: Coin launches and being prepared.

New CryptoCoin launch preperation guide;
I've created this short guide for new users who want to jump in on the mining of a newly launched coins. Being prepared and getting on the network immediately will lead to you finding the earliest blocks (some coins have block rewards that are higher in the beginning)
Step One - Prepare the Data/Wallet directory
The first step in this guide will be to setup the directory that will hold your wallet data, config file and blockchain store. We want to set this up first so we can immediately start solo mining without screwing around with settings that are common across all CryptoCoin wallets.
Windows 7/8; C:\Users\YOURUSERNAME\Appdata\Roaming\COIN_NAME
Windows XP; C:\Documents and Settings\YOURUSERNAME\Appdata\Roaming\COIN_NAME
Linux; ~/.coinname/
MacOS X - ~/Library/Application Support/
Create a directory in one of the above directories that will match the name of the coin (ie: Bitcoin). In this directory we are going to make the default .conf file;
Default options listed in the COINNAME.conf will be as follows;
server=1
listen=1
daemon=1
rpcuser=YOUR_DESIRED_USER_NAME
rpcpassword=YOUR_DESIRED_PASSWORD
rpcport=NUMERIC_PORT_TO_LISTEN_ON
rpcconnect=127.0.0.1
Change the rpcport parameter to a generic port # if you plan on only having one batch file to start solo mining. WARNING, this method will interfere with mining if multiple wallets are running using the same port number. If the launch forum post lists default rpcport #s, use them instead of one generic port. (cryptocointalk/bitcointalk).
Pay attention to the original launch information forum post, adding nodes with addnode=ipaddress, can help speed up node discovery and wallet sync. You can add these options fairly quickly with a cut and paste.
If you have multiple rigs and plan to throw their hashes at the wallet if it's not on the same machine, use the .conf option rpcallowip=your.network.address.* (eg: rpcallowip=192.168.0.*).
Step Two - Create your .bat file
If you've been mining for awhile, this should be a simple step, otherwise, it is beyond this tutorial on how to fine tune your mining software.
The .bat file should only be a few lines long;
setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o http://127.0.0.1:WALLET_RPCPORT_PARAM -u YOUR_USERNAME -p YOUR_PASSWORD the_rest_of_your_miner_config_here
This is the default for scrypt mining. Always pay attention to the announcement post for specific mining options (CPU only, keccek, scrypt-n, etc).
Change the IP address in -o option to your wallet machines ip address, should be you mining from a different machine. (making sure to set the above rpcallowip= correctly)
note: adding gen=1 to your config file will automatically start the wallets internal block generation routine, by passing the need to start your mining software. Just remember to edit this option later if you run the wallet continually and do no plan to directly mine.
Step Three - Mine!
Download and install/extract wallet, run the wallet. If everything is set correctly, you should be ahead of the game and finding blocks very quickly.
If you've found this post informative, I'm never opposed to receiving gifts of Litecoin :D LXFE81zFSTkzsV1TrRCtdy781F1aiEfYHe
also: If you have any additions to this guide, please PM or comment, so that I may correct any errors I may have included.
edit: formatting.
submitted by agentneuron to CryptoCurrency [link] [comments]

Are there any Bitcoin clients that can RPC connect to a Bitcoind server?

I'm running the original Bitcoin wallet on my server, and I wanted a graphical client that I can run on my desktop that can rpc connect to my server, but I can't seem to find any.
The Bitcoin-qt doesn't support rpcconnect (https://github.com/bitcoin/bitcoin/pull/2513 which is very strange! it should support it :().
Does anyone know of any client that does support it?
submitted by intahnetmonster to BitcoinBeginners [link] [comments]

Unencrypted RPC & Multiparty ECDSA ~ Bitcoin op Tech #18 Connect to Bitcoin & Ethereum networks - Dilum Navanjana- FOSSASIA 2018 How to mine bitcoins (solo mining) with the core client ... Dev++ 01-08-EN  Remote Procedure Calls (RPC) - Anditto Heristyo A breif introduction to the Chain Query Bitcoin RPC API

Bitcoin Core 0.17.0. If the following options are not in a section, they will only apply to mainnet: addnode=, connect=, port=, bind=, rpcport=, rpcbind= and wallet=.The options to choose a network (regtest= and testnet=) must be specified outside of sections.‘label’ and ‘account’ APIs for wallet A client library to connect to Bitcoin Core RPC in JavaScript. - bitpay/bitcoind-rpc There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called bitcoind).They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. Blockdaemon Bitcoin Dedicated nodes expose an RPC interface for connecting and interactions. Connecting: Command Line cURL. The following describes how to run a simple cURL command that prints the current blockchain information from the node. There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called bitcoind).They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files.

[index] [15031] [20742] [50683] [4660] [25423] [36262] [34960] [16946] [51232] [13082]

Unencrypted RPC & Multiparty ECDSA ~ Bitcoin op Tech #18

https://ChainQuery.com/tutorials/a-brief-introduction-to-the-chain-query-bitcoin-rpc-api Take a brief tour of the features and functionality of the Chain Que... The Bitcoin Operations Technology Group (Optech) works to bring the best open source technologies and techniques to Bitcoin-using businesses in order to lower costs and improve customer ... Bitcoin 101 - Calling All APIs - Coding Live Price Data From Bitcoin Exchanges - Duration: 10:53. CRI 27,996 views. 10:53. Slushs pool mining tutorial - cgminer worker setup - Duration: 5:45. ... You can do what ever the blockchain work you want with those APIs. So in my talk I will talk about how to use those APIs to connect to most famous Bitcoin & Ethereum networks. So you can ... Anditto covers basics of Remote Procedure Calls (RPC) that allow developer to use Bitcoin client to interact with Bitcoin network. How to configure and interact with Bitcoin using RPC (create ...

#