Is it insecure to use 'localhost' as a callback URL in ...

Please recommend me a Seedbox

Hello. I'm seeking seedbox recommendations to help bootstrap the swarm on BioTorrents.de, a torrent tracker for biological sequence and medical imaging data. Thanks for any advice you can provide.
Are you OK with direct message offers from vendors?
Yes, but only to discuss tax-deductible donations of server time on behalf of BosLab, the 501c3 community biology lab where BioTorrents.de originated.
What are your main reasons for getting a seedbox?
I'm in the process of launching a semi-private science tracker for genomic and medical data, and would like to seed as much content on as fast connection as I can afford. I'm currently seeding from two residential locations.
Do you have any specific requirements?
I'm seeking a 1 Gbps uplink with as much storage and monthly transfer capacity as can be had for about $20 per month. The storage cap is the limiting factor right now, not the transfer cap.
Are you looking for a shared or dedicated solution?
Dedicated is preferred, but shared is okay if it helps meet the requirements above.
Are you looking for managed or unmanaged solution?
Unmanaged
Please describe your Seedbox experience:
My current setup is a Transmission instance seeding about 5,000 torrents from a home server on a residential connection, that I access and manage remotely behind a SOCKSv5 proxy. I would set up an rTorrent/ruTorrent instance on the seedbox in a similar way (Nginx reverse proxy to daemon listening on localhost).
Currently with a provider or used one before?
No
What is your Linux experience?
Professional development and systems administration for a sizeable public-sector organization.
What is your monthly budget?
$20
Payment preferences or requirements?
PayPal or debit preferred, Bitcoin not preferred.
Do you need support for public trackers?
The BioTorrents.de content distribution model is novel as far as I know: an authenticated private swarm on Tier 1, with three public backups on Tier 2 and forthcoming support for FTP/HTTP seeds.
Routing: Tell us your continent:
I'm currently seeding about 1–2 Mbps from North America and would prefer a European location.
What kind of connection speeds do you need?
At least 150 Mbps guaranteed with 1 Gbps burst available.
How much monthly bandwidth is needed?
2 TB is a reasonable limit because the data is rather niche.
How much disk space do you need?
4 TB is a good minimum, as I've allocated that much space on my home server.
List some features you are looking for:
The ability to install custom ISO images would be nice, for example to use OpenBSD-current, but it's not a strict requirement. I'll make do with whatever Linux images the service offers, preferring Debian.
Anything else you think we should know?
Thanks for helping me out!
submitted by biotorrents to seedboxes [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]

/r/Monero - Newcomers Please Read. Everything You Need To Know.

What is Monero (XMR)?
Monero is a secure, private, untraceable (crypto-)currency. It is open-source and freely available to all. Don't believe us? Click here.
Monero is a tool that people can actually use. It makes receiving payments hassle-free, since merchants and individuals no longer need to fear the source of funds they are accepting. With transparent systems like Bitcoin, Ethereum, Verge, or Dash, these people need to hope (or spend substantial resources verifying) the sender did not use the funds illicitly. Furthermore, merchants do not want all their vendors known, and individually do not want everyone to know how much they are spending. If I spend more than I should at Newegg (store), that's my own business.
Monero is different because every transaction is always private. There is no way for pools and exchanges to opt out of sending private transactions. Thus, Monero's anonymity set far exceeds any other coin's anonymity set. Over 86,000 transactions in the past month of August, 2017 hid the sender and receiver, and about 99.95% of them also hid the amount (will increase to 100% of all new transactions in September)! There is no suspicion in using a private transaction, since all transactions are private. A single transaction does not stick out.*
This privacy is afforded with the best technology. I implore you to take a few minutes to learn about the four main technologies that Monero uses to provide privacy:
There are several other things that make Monero great! It has a smooth tail emission, dynamic blocks and fees, and an accessible Proof of Work (mining) algorithm.
*You can optionally choose a very large, unusual ringsize to make the transaction stick out. This is not recommended, and normal users who leave the ringsize at the default setting will not experience any issues. Also, it's possible for a user to manually add identifying information to the tx_extra field, which is something that a user must seriously go out of their way to do.
Now you know Monero (XMR) has the best technology. What else makes Monero (XMR) different than other cryptocurrencies?
P.S. Want a quick-start, simple your-grandma-could-do-it guide? Here's a great one!
Am I a bad person to consider using this?
No, Monero is freedom money. You can do whatever you want with it, whenever you want, where ever you want. We make it clear that you should own your wealth 100%. What you do with it, is none of our concern.
Where does the word Monero come from?
The word Monero comes from the language Esperanto. Monero means coin oand currency. The plural way of saying Monero in Esperanto and in our cryptocurrency is Moneroj.
How do I store Monero?
Monero Core
Monero Core GUI (If you don't know how to use it, click here for instructions and tutorial)
Monero Web-Wallet
Offline Wallet Generator
Is there a lightweight wallet for Monero?
Not yet, but you can use the official GUI with a remote node.
Are there any other ways to store Monero (XMR)?
Yes, there are many mobile wallets out there that allow you to store Monero (XMR). We do not recommend them, because they are not official releases of Monero. If you do decide to use other wallets, please make sure to do your research first before storing any Moneroj in the wallet. Anything used for Monero outside of official releases, will be used at your own risk. Some may be used for scamming purposes. If you still decide to take the risk; do not use them for large amounts. Also keep in mind that there is a high chance that Monero support will not be able to help you if you bump into any problems from applications outside of official releases. Why should you not use non-official wallets? Well would you buy a house and give your only key you have to the buildemanagement and wait for him/her to open the door to the house you supposedly own? No. Same goes with cryptocurrencies. You should always have possession of your private keys, and your Moneroj. Most non-official releases own your private keys, therefore you do not own the Moneroj.
How do I buy Monero (XMR) with fiat?
Kraken
Bitfinex
Monero For Cash
Local Monero
Other Options
Which exchanges support Monero (XMR)?
Poloniex
Bithumb
Kraken
Bitfinex
Bittrex
Bitsquare
ShapeShift
Livecoin
BTER
How do I setup a offline cold paper wallet?
Step-by-step guide for cold storage and offline transaction signing with optimal security
Guide For Securely Generating An Offline Cold Paper Wallet
USB Monero Cold Wallet Guide
Is there a Chinese translation so I can understand Monero? 是否有中文翻译,以便我能理解Monero?
Monero (XMR) Chinese Translation
Can I buy Monero (XMR) with CNY? 我可以用人民币买Monero吗?
BTER
*Can I buy Monero (XMR) with KRW?
Bithumb
Where can I find a good mining pool?
Monero Pools
What miner should I use?
CPU:
XMR-Stak (Windows-Linux)
CpuMiner by tpruvot (Windows, Linux)
CpuMiner By Wolf
xmr-stak (MacOS)
cpuminer(MacOS) By correcthorse
GPU:
XMR-stak (AMD)
Ccminer (nVidia) by KlausT, psychocrypt, and fireice-uk
Claymore's CryptoNote GPU Miner (AMD)
If you are a Windows user, click here.
Can I use a proxy for mining?
You can use XMR Proxy. If you want to monitor your rigs you can use Monero Mining Monitor.
How can I setup a local wallet while running node with little bandwidth?
You can use GUI, as a remote node as it uses very little bandwidth. Go to settings tab and change: "localhost:18089" to "node.moneroworld.com:18089". If you are still having problems, then just use our Monero Web-Wallet.
Can I run Monero through Tor or I2P?
Guide to use Monero with Tor correctly
Monero Safety Through Tor
Monero I2P
My vendor only accepts bitcoin but I only have Monero, and I know bitcoin is not private/anonymous. What should I do?
Use XMR.TO, but you should also educate them about bitcoins lack of privacy. Tell them to visit this post.
How long does it take to sync to the blockchain?
It can take from a few hours (using SSD drive) or even 24 hours, depending on hard drive and connection speed.
How do I generate a QR-code for a Monero address?
How to generate a QR code for a Monero address
Moneroqrcode.com for a personalized code
Guide to check balance
List of scams: (Always do a background check / research for anything outside of official releases.)
Did you know over 50 high profile artists accept Monero on their online stores? Check out Project Coral Reef
Are there any other sub-reddits that specialize in certain parts of Monero or just related to Monero?
Yes, there are a few. However, please keep in mind that this sub-reddit (/Monero) is the official Monero sub-reddit.
/xmrtrader - Trading, and investing related discussions & inquires.
/MoneroMining - Mining related discussions & inquires.
/MoneroCommunity for those who want to help grow the community.
/moonero for shitposts and memes.
/MoneroMarket for buying and selling wares for Monero.
/MoneroSupport for, you guessed it, Monero support.
Want to get involved? Click here for a list of sources.
How can I participate in the Monero community?
We welcome everyone to join us and help out. Check the "Community Info" section on our subreddit for our website, forum, stack exchange, github, twitter, and facebook. Anyway, we hope you stick around beyond the hype. Monero has a lot going for it, and we hope you agree! We really need your help, since this project is entirely driven by the community!
Nun vi spertis liberecon.
submitted by cryptonaire- to Monero [link] [comments]

Creating a Headless Staking Node on Ubuntu 18.04

Creating a Headless Staking Node on Ubuntu 18.04
##UPDATE## Step 8 - Option 2, has some bugs in the final build process. i haven't had time to work them out yet!

This guide will take you through building and running a headless x42 Full Node! The OS I am using here is Ubuntu 18.04, this guide picks up from a complete/fresh ubuntu install.
This is meant to setup a staking node and so this guide will run you through building, configuring and setting up staking. It will not cover sending transactions or anything else.
The things we are going to do:
  • Step 1 - Install .net core
  • Step 2 - Download The x42 Node Source & Compile It
  • Step 3 - Setting The x42 Node Up To Run On Boot
  • Step 4 - Setup A New Wallet
  • Step 5 - Configure The x42 Daemon
  • Step 6 - Get Address
  • Step 7 - Check Balance
  • Step 8 - Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node # BROKEN#

Step 1 - Install .net Core

Here is the reference link:
https://dotnet.microsoft.com/download/linux-package-manageubuntu18-04/sdk-current
Register Microsoft Key’s & Install Their repos:
cd /tmp wget -q https://packages.microsoft.com/config/ubuntu/18.04/packages-microsoft-prod.deb sudo dpkg -i packages-microsoft-prod.deb sudo add-apt-repository universe sudo apt -y install apt-transport-https sudo apt update sudo apt -y install dotnet-sdk-2.2 
Microsoft collect telemetry data by default, if you are part of the “tin foil hat brigade” you can set the following environment variable to turn it off:
echo "DOTNET_CLI_TELEMETRY_OPTOUT=1" >> /etc/environment 
now you should be at a point where .net core is installed on your system… that wasn’t so hard was it! You can check by running the following command:
dotnet--list-sdks 
The output should look like this:
$ dotnet --list-sdks 2.2.103 [/usshare/dotnet/sdk] 

Step 2 - Download & Compile The x42 Node

This part assumes you have GIT installed, if not:
apt -y install git 
Now to pull down the source and compile it!
cd ~/ git clone https://github.com/x42protocol/X42-FullNode.git # “cd” into the source folder cd X42-FullNode/src/ 
Now .net core uses NuGet for package management, before we compile, we need to pull down all of the required packages.. its as simple as running (this will take a couple of minutes) inside of “X42-FullNode/src/”:
dotnet restore 
now we are ready to compile the source, execute (inside of “X42-FullNode/src/”):
dotnet build --configuration Release 
ignore the yellow warnings, this is just the rosyln compiler having a grumble.. if you get red ones then something went wrong! The “--configuration Release” will strip out all debug symbols and slim things down.. only a little, this optional parameter is not mandatory.
Once this is done everything is built/compiled, you can run the daemon directly from the repository, this can be done by going to:
cd ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1 dotnet x42.x42D.dll 
this will kick off the node, however if you exit SSH at this time it will kill the process! however I always recommend copying out the binaries to a separate folder. This can be done with the following:
mkdir ~/x42node mv ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1/*.* ~/x42node/ 
now we have everything we need to run the node outside the git repository! What we need to do now is run the node and have it create the default x42.conf file.. so
cd ~/x42node dotnet x42.x42D.dll 
feel free to hit “CTRL + C” to exit the application after a couple of seconds, by then the folders/files would have been created at the following path:
~/.x42node/x42/x42Main/ 

Step 3 - Setting The x42 Node Up To Run on Boot

Now we are going to create a service file so our x42 node automatically starts when the system is rebooted.
THINGS TO NOTE ABOUT BELOW.. CHANGE THE ##USER## to the username your currently using as these files are within your home directory!
We need to drop to root for this..
sudo -i cat < /etc/systemd/system/x42node.service [Unit] Description=x42 Node [Service] WorkingDirectory=/home/##USER##/x42node ExecStart=/usbin/dotnet /home/##USER##/x42node/x42.x42D.dll Restart=always # Restart service after 10 seconds if the dotnet service crashes: RestartSec=10 SyslogIdentifier=x42node User=##USER## Environment=ASPNETCORE_ENVIRONMENT=Development [Install] WantedBy=multi-user.target EOF 
To enable the service, run the following (as the root user):
systemctl enable x42node.service 
BOOM.. the node isn’t running yet.. but next time the system restarts it will automatically run!
now lets exit out of root!
exit 
We can now start the node up and begin downloading blocks, by running the following command:
sudo systemctl start x42node.service 
if you want to check its loaded and see some of the output, you can run:
sudo systemctl status x42node.service 
an example of the output:
$ sudo systemctl status x42node.service ● x42node.service - x42 Node Loaded: loaded (/etc/systemd/system/x42node.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-01-24 15:47:55 UTC; 14s ago Main PID: 5456 (dotnet) Tasks: 23 (limit: 1112) CGroup: /system.slice/x42node.service └─5456 /usbin/dotnet /home/darthnoodle/x42node/x42.x42D.dll Jan 24 15:48:09 x42staking x42node[5456]: Batch Size: 0 Mb (0 headers) Jan 24 15:48:09 x42staking x42node[5456]: Cache Size: 0/50 MB Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: =======Mempool======= Jan 24 15:48:09 x42staking x42node[5456]: MempoolSize: 0 DynamicSize: 0 kb OrphanSize: 0 Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:86.184.76.255]:52342' connected (outbound), agent 'x42:1.2.13 (70012)', height 213920 Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:86.184.76.255]:52342' offline, reason: 'Receiving cancelled.'. All node screen output can be found in the /valog/syslog file. 

Step 4 - Setup a New Wallet

With the Node running, we now need to setup and/or restore a wallet!
Everything will be performed through the API’s, however by default these API’s are listening on localhost (127.0.0.1), if you are connecting in remotely then this would be a problem since you cant hit that IP. The solution, SSH TUNNEL!
Execute the following command on your local system:
ssh -L 42220:localhost:42220 @ 
This binds the local port (on your system) with 127.0.0.1:42220 on the remote system, once you have executed the command you can type the following address in your laptop/desktop’s web browser and be able to access the API’s:
http://127.0.0.1:42220/swaggeindex.html 
It should look something like this:
https://preview.redd.it/9lzeg3vob8d21.jpg?width=482&format=pjpg&auto=webp&s=b5d574998816056140d5d6de7b03c56772a892fe
To Create a new wallet, first we have to generate some mnemonic works (e.g. the seed), you can do that by going to the following API:
/api/Wallet/mnemonic 
Hit the “Try it out” button which then prompts you for 2 fields:
https://preview.redd.it/dvbdllfrb8d21.jpg?width=722&format=pjpg&auto=webp&s=766d14bafba6facbcd56d31c63c0012748e682e5
Enter “English” and I would recommend 24 words as this greatly increases the seed strength! Once that is done you hit execute and then scroll down to see the “Response Body”, this should contain the mnemonic which you are going to use to create the wallet! This looks something like below:
https://preview.redd.it/6p4q0rsub8d21.jpg?width=603&format=pjpg&auto=webp&s=44b9265626467a43ca670b134c4d28187f475c2e
THIS IS VERY IMPORTANT, BACKUP THIS MNEMONIC TO A SAFE SECURE LOCATION THAT IS ENCRYPTED!!!
So now we have our mnemonic, its time to generate the wallet, for this we need to use the API:
/api/Wallet/create
There are a number of parameters which are required in order to create a wallet:
WalletCreationRequest{ mnemonic string password* string passphrase* string name* string } 
It should be noted that the password and mnemonic are is the most important parts of this request where the “password” will encrypt the wallet and Is required to unlock it.
  • Hit the “Try it out” button
  • input the necessary data
  • Insert the mnemonic
  • Put a password & passphrase
  • “Name” is what your wallet will be called
It should look something like the following:
https://preview.redd.it/958ttfbxb8d21.jpg?width=603&format=pjpg&auto=webp&s=ce48336436ea4b469b5e87513da802de0bf444ee
Hit “Execute”, the “Loading” sign may spin for a few minutes while the wallet is created… once the wallet has been created the “Response Body” will return the mnemonic you have just used.. we now have a wallet!!
HOWEVER IT IS NOT LOADED INTO THE NODE JUST YET!
This is where we will now jump back out and to configure the node to automatically load the wallet and automatically start staking when it first loads.
AGAIN BACKUP YOUR MNEMONIC AND PASSWORD, MAKE SURE THEY ARE ENCRYPTED AND STORED SOMEWHERE SAFE!

Step 5 - Configure The x42 Daemon

Now we are going to modify the x42.conf file in order to automatically load our wallet and start staking 😊
First things first, lets stop our node by running the following command:
sudo systemctl stop x42node.service 
CD to the following folder and view its contents:
~/.x42node/x42/x42Main ls -lah 
within that folder there should be 2 files you are interested in:
-rw-r--r-- 1 darthnoodle darthnoodle 18K Jan 28 16:01 TestWallet.wallet.json -rw-rw-r-- 1 darthnoodle darthnoodle 3.1K Jan 24 15:25 x42.conf 
So TestWallet.wallet.json is our physical wallet that will be loaded, but for right now we want to modify the x42.conf file.. fire up your favourite text editor (if you use VI you’re a masochist)..
nano x42.conf 
The area we are interested in is the following:
####Miner Settings#### #Enable POW mining. #mine=0 #Enable POS. #stake=0 #The address to use for mining (empty string to select an address from the wallet). #mineaddress= #The wallet name to use when staking. #walletname= #Password to unlock the wallet. #walletpassword= #Maximum block size (in bytes) for the miner to generate. #blockmaxsize=1000000 #Maximum block weight (in weight units) for the miner to generate. #blockmaxweight=1000000 #Enable splitting coins when staking. #enablecoinstakesplitting=1 #Minimum size of the coins considered for staking, in satoshis. #minimumstakingcoinvalue=10000000 #Targeted minimum value of staking coins after splitting, in satoshis. #minimumsplitcoinvalue=10000000000 
Uncomment (remove the #) of the following lines and change their value:
stake=1 (changed to 1) walletname=TestWallet (changed to our Wallet Name) walletpassword=password123 (changed to the wallet password) 
save the file and exit back to the command prompt, now we shall restart the node with the following command:
sudo systemctl status x42node.service 
now the wallet is automatically loaded and ready for action!
YES I KNOW YOU HAVE PUT YOUR PASSWORD IN CLEARTEXT, THIS IS WHERE YOU SHOULD HARDEN YOUR BOX. IF THEY CAN GET TO THE POINT WHERE THEY CAN READ YOUR CONF FILE THEY CAN JUST GRAB YOUR WALLET AND BRUTEFORCE THE PASSWORD.
You can check its loaded by going back to the API and executing the following command:
/Dashboard 
Or execute the following command on the NODE:
curl -X GET "http://127.0.0.1:42220/Dashboard" -H "accept: application/json" 
both will produce the same output, if you scroll to the bottom you should see something like this:
======Wallets====== TestWallet/account 0, Confirmed balance: 0.00000000 Unconfirmed balance: 0.00000000 
This means the wallet is loaded and ready for action!!

Step 6 - Get Addresses

Next thing you are probably going to want is a receive address and to check the balance and TX history.. so lets start with getting an address!
Go to the following API:
/api/Wallet/unusedaddress 
Fill in the Wallet name which is “TestWallet” (in this example) and “account 0” (which is the first/default account):
https://preview.redd.it/ayri5jk0c8d21.jpg?width=602&format=pjpg&auto=webp&s=2d16bbb78da49c0125d24d0834c9454d702cb7a1
Hit execute and you should have an x42 address within the “Response Body”:

https://preview.redd.it/tmc495j3c8d21.jpg?width=349&format=pjpg&auto=webp&s=b00177f66a9e24c980d3c6d4e532a33cbf3fb0bc
BOOM… ok now we can receive funds! 😊

Step 7 - Check TX History

Go to the API and the following call:
/api/Wallet/history 
The 2 fields we are most concerned about are:
https://preview.redd.it/lw194af6c8d21.jpg?width=602&format=pjpg&auto=webp&s=27e264bc008879355ff5b9c50a0a5cb06f16e960
Input the name of the wallet and account you want to view the history of, then hit execute. The other fields can be black. This will return a list of TX’s that the wallet has received:
This should look like the following:
https://preview.redd.it/x1hgargac8d21.jpg?width=585&format=pjpg&auto=webp&s=4fd25f22772f4bcec523a6e82b321ae8146a2c75
There is an easier way of doing this, that doesn’t require you to be connected to your node.. especially if your only interested in viewing your staking rewards… THE EXPLORER!
Access the following URL:
https://explorer.x42.tech/address/ 
this will allow you to easily see all TX’s associated with this address, it should look something like below:
https://preview.redd.it/e480grscc8d21.jpg?width=601&format=pjpg&auto=webp&s=0f8a9ebc7944dfcc73f7df659bd839bb983ba90c
… and your done! By this point your node should be running, staking and you have an easy way to view transactions/rewards 😊


Step 8 - Connect The UI Wallet To A Headless Node

The UI utilises a combination of technologies, however the important part is the code attempts to access the x42 Node API on 127.0.0.1:42220.
So you have 2 options here:
  1. Download the Wallet Installers
  2. Compile The UI Yourselves
Pick the option that best suits you given the pros/cons below:
Option 1 - Pro's/Cons
Pro's
  • If you use the installer, its quick and easy.
Cons
  • This also installs an x42 node on your system which runs when the UI loads.
  • If you dont setup an SSH tunnel before running the wallet the local node will bind to the port and the tunnel wont work.. you will be connecting to the local wallet!!
Option 2 - Pro's/Cons
Pro's
  • You only run the UI, the x42 node is not installed
  • you dont have a superfluous node running, downloading blocks on your local system
Cons
  • Time Consuming
  • Have to download dependencies and manually compile the code

Pre-Requirement - Needed For Both Options!!
As previously mentioned, the UI attempts to access the API's on 127.0.0.1:42220, however our node isnt running on our local system. IN ORDER TO GET IT WORKING YOU NEED TO HAVE AN SSH TUNNEL, THIS TUNNEL NEEDS TO REMAIN ACTIVE WHENEVER YOU WANT TO ACCESS THE WALLET.
this can be done by executing the following command:
ssh -L 42220:localhost:42220 @ 


Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node

Download and install the UI/Wallet & Node from:
https://github.com/x42protocol/X42-FullNode-UI/releases

DO NOT RUN THE WALLET YET!
Those of us who dont want to run a local node and just want the UI, execute the following commands (as an administrator):
cd C:\Program Files\x42 Core\resources\daemon\ ren x42.x42D.exe x42.x42D.exe.bak 
The above is with Windows, if your are in *NIX then locate the daemon and rename it (i will update how to do that/where to find it shortly)
Setup the SSH tunnel as outlined above, Execute the wallet and it will load, however you will see an exception:

https://preview.redd.it/9os5h8q7scd21.jpg?width=550&format=pjpg&auto=webp&s=ac45ed7bc987917142075c61fb486e7d71f820d1
dont worry, this is just the wallet trying to execute/start the x42 node which we dont want, if all works according to plan.. after you click "OK" you should now be presented with the wallet UI and have the option to select what wallet you would like to load:

https://preview.redd.it/hnyt0b4mscd21.jpg?width=958&format=pjpg&auto=webp&s=a47df710a804375d8363ffcd77d1ede2862b9b4d
... DONE!

Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node ###BROKEN

THIS IS STILL A WORK IN PROGRESS, THE ELECTRON BUILD DOESNT WANT TO COMPILE BECAUSE SOME CODE IS MANGLED SOMEWHERE!!

Ok, this is the fun bit! .. we need to install the following dependencies. these instructions are written for a Windows system but it should be easy enough to perform the same on a *NIX system.
Install Dependencies
In order to build the wallet UI, you need to install the following components:
  • git
  • NodeJS
  • Electron Builder
First thing you need to do is install git, so download and install the package:
https://gitforwindows.org/
Next you need to install NodeJS, download and install the package:
https://nodejs.org/en/download/
Next we need to install the node package manager:
npm install npx –verbose 
next we need to make sure we have Visual Studio build tools and Python (2.7) installed, this can be done by executing the following (AS AN ADMINISTRATOR!):
npm install -g --production windows-build-tools 
this will install the necessary tools to build C#/C++ code and python 2.7, this could take some time! When its done you should have something like the following;

https://preview.redd.it/5ekfy5g1kcd21.jpg?width=490&format=pjpg&auto=webp&s=f65196dee6f78f2ececec5ee8b5df1044d68f635

Build & Install - Windows
Create a temp folder to navigate to a folder where you want to download the GIT repository, execute the following command:
git clone https://github.com/x42protocol/X42-FullNode-UI.git 
This will clone the repository into the folder, it will only clone the wallet and not the Node source! now lets CD into the folder and build the UI:
cd X42-FullNode-UI\FullNode.UI npm install 
This will download and install all dependencies (can take a while), at the end you should see something like..

https://preview.redd.it/0zfbfxa8kcd21.jpg?width=601&format=pjpg&auto=webp&s=438d072a6ab2bc7a3d84a8dfe773968acc762bc7
Now the stock UI has a number of third-party libraries which contain some vulnerabilities, being a security conscious person, ive also run:
npm audit fix 
when this is done, we have fixed most of the package vulnerabilities 😊 We also get a complaint about the typescript library being too new for the version of angular in use, so run the following command to install the additional dependency:
npm install [email protected]">=2.4.2 <2.7.0" 
now its time to build the UI, execute the following:
npm run build:prod 
once complete you should see something like the following..

https://preview.redd.it/56vf9zfckcd21.jpg?width=601&format=pjpg&auto=webp&s=31b72daff9ab5001843cba529a7bd38c76fd099d
Next its time to compile the electron binary, it should be noted that the build/package process utilises AppVoyer which is not installed and if you attempt to build right now you will get the following error:
cannot expand pattern "${productName}-v${version}-setup-${os}-${env.arch}.${ext}": env arch is not defined. 
To fix this we need to modify the build file, this is a quick one liner that can do it:
powershell -Command "(gc electron-builder.json) -replace 'env.arch', 'arch' | Out-File electron-builder.json" 
Essentially the offending line for Windows is..
"artifactName": "${productName}-v${version}-setup-${os}-${env.arch}.${ext}" 
The build cannot resolve “env.arch”, so the above one liner replaces “env.arch” with “arch” which works 😊
execute the following command:
npx electron-builder build --windows --x64 
At present i get the following error, no matter what i do.. and ive ran out of time to go hunting about.. if anyone has any ideas on how to fix then please post in here or message me on discord:

https://preview.redd.it/t66rtuqdtcd21.jpg?width=918&format=pjpg&auto=webp&s=a3f1a5ff682586348909c67645ca7ae9454922ff


Happy staking!

If you found this post helpful, then buy me a beer and send a donation to XQXeqrNFad2Uu7k3E9Dx5t4524fBsnEeSw
submitted by D4rthNoodle to x42 [link] [comments]

[How To]Full Node (Beta) + GUI + Staking on Raspberry PI 3

Hello everyone,
With the Full Node Beta recently being released on 3/28 and the Full Node GUI on 4/11, I thought it would be an excellent time to update the RPi tutorial by olcko and demon for the RPi. I've been running it now for about 1 week and it has been working great so far, but I haven't been connected to many peers running the full node. Hopefully this tutorial will help change that!
This tutorial will take over from the previous tutorial's step 4. Steps 1-3 cover installing Raspbian and SSH on the RPi and are excellent.
PREREQUISITES
FULL NODE Setup
mkdir StratisFullNode
cd StratisFullNode
git clone https://github.com/stratisproject/StratisBitcoinFullNode.git
cd StratisBitcoinFullNode
git submodule update --init --recursive
cd src
restore
build
cd Stratis.StratisD
run -apiuri=http://0.0.0.0:32771
The "apiuri" option enables access to the API from another device on your network (Thanks Daan Damhuis!).
That's it! Your node should be running now, but may take a while to sync. You can test the node's API by pointing your browser to http://:37221/swagge
If you don't plan on using RPC, make sure you follow the instructions from the previous tutorial step 3 to block RPC connections.
sudo ufw deny 16174
Full Node GUI Setup
Now that the Core Daemon is running, we can install the GUI frontend. We will be following the instructions from here. The GUI that interacts with the node can be installed on the RPi or another device on your network (with some tweaks to the underlying code, below).
cd ~/StratisFullNode
git clone https://www.github.com/stratisproject/FullNodeUI
cd FullNodeUI/FullNodeUI.UI
npm run mainnet
That's it! Go ahead and set up your new wallet!
Remote GUI Tweaks
I'm adding this section for RPi owners who don't run a GUI on their RPi device, but may want to run the GUI on another device on their network. This can be done because the GUI interacts with the full node through the API; however it will take some tweaks to the code before compiling to make this set-up work. The instructions for "Full Node GUI Setup" above should be run on that device.
There is one place in the code where you need to replace "localhost" with your RPi's local private network IP address.
  • src/app/shared/services/api.service.ts#38
this.stratisApiUrl = 'http://:' + this.apiPort + '/api';
You will also need to comment out a few sections to prevent the GUI from starting up or shutting down the full node when you open/close the GUI.
  • main.ts#86
//startStratisApi();
  • main.ts#96
//closeStratisApi();
Helpful RPi tips for remote management
  • Use Screen + SSH! Screen is a wonderful utility that will leave your session running when you disconnect from ssh. This is available via sudo apt-get install screen on your RPi. You can reconnect when you return at another ssh session with:
screen -x
  • Sometimes the full node on your RPi will hang or unexpectedly crash - stopping staking in the process. Borrowing from here, I have created a script that will monitor for hangs or crashes and restart the node.
  • If the node is restarted, you will still need to re-enable staking. This can be accomplished through the GUI, a browser using swagger, or with an API call through a local script (insecure).
Sample helper scripts, including a .screenrc configuration, for the above can be found in a pastebin here.
Example API calls can be found on the full node's swagger API interface.
  • Note: your wallet passphrase must be sent via POST to re-enable staking.
I hope you found this helpful!
Please feel free to message me with questions/errors/improvements or find me on the discord/telegram as @TjadenFroyda. I'll update this post with feedback.
Donations are welcome as well: SNSwQVvB5FB6KPVT7325tJGWXbxVd4xceR
submitted by gopherdoc to stratisplatform [link] [comments]

gRPC LND Python Problem

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

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

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

Recommendations for node setup

I am torn between two options to set up my node. Some context: my desktop is turn on almost 12 hours everyday, sometimes it is the whole day/week. I also use both electrum and bitcoin core as wallets. At this moment I don't have 100gb in my desktop and I have a pruned node running on [email protected] Have in mind that I don't need HDD space at all and it seems a little over the top to buy one for my desktop just to set up a node. The options:
Additional question: it is possible to run a full node on a different user ([email protected]) with bitcoind and connect to it from another user on the same machine with bitcoin-qt?
submitted by gp2b5go59c to Bitcoin [link] [comments]

Check out my bitcoin-related python project: opensource and easy to use

Hello everyone! Me and my friend have created a project, which aims to simplify usage of bitcoin. We have tried to do the best setup, so you can just clone repository, set your domain if you have it, and run two shell files and boom, it is running(via docker). It uses an easy-to-use api, wrapper around electrum daemon, so you can use it from python as a lib easily too:
from bitcart.coins.btc import BTC btc=BTC("http://localhost:5000",user="youruser", password="password", xpub="xpub") print(btc.get_tx("txhash")) print(btc.add_request(amount=5))
In future, we plan to add support for more coins and simplify setup even more(like gui app where you enter ip address and password of server, it connects to server and installs bitcart). Also there is work in progress on "store", where you can select some web template and add products from admin panel, and changes will be reflected in store. Probably some type of e-commerce thing. We have bitcart running on our server for you to look: https://demo.bitcartcc.tk Github: https://github.com/MrNaif2018/bitcart Docs: https://bitcart.readthedocs.io
submitted by MrNaif2019 to Python [link] [comments]

Mycelium Updates

Hi guys! Just wanted to give you an update on what's happening behind the scenes here at Mycelium.
Mycelium Entropy - We have decided to go with aluminum cases after all, which means Entropy devices will be more durable, actually a bit bigger so they are harder to lose, and will keep the internal stuff protected from any electromagnetic interference or other shenanigans. The cases are actually solid tubes, flattened a bit, with flat edges on the side, so no seams either. The device will slide right in. The minor downside was that these cases were a bit narrower than what we were expecting, and we ended up having to reorganize the chips on the circuit board into a narrower longer shape to get them to fit. But we were continuing negotiations and doing actual manufacturing setup with the manufacturers through that whole time (multitasking!) so we didn't really lose much time on this, and are still on track to ship these some time in October (just closer to the end of October, instead of the beginning). Sorry about that. We also already ordered the t-shirts in various sizes, so if you ordered one and didn't get an e-mail asking for your size, please get back to us on that so we won't send you the wrong size.
Mycelium Wallet 2.0 (HD) - LOTS of changes happening with this one. It won't look very different, but behind the scenes there are a lot of improvements and new features, the most important of which is, obviously, BIP32/39/44 support. So, no more having to back up every bitcoin address or print out PDF's of paper backups. Just write down 12 words, and your wallet is backed up for ever, regardless of what bitcoin addresses you create. At this point we have already gone through the beta stage, and RC1 stage, and will be releasing RC2 some time tomorrow. If everything seems fine with that one, we will probably release the final early next week. In the mean time, if you want to try out what we have now, feel free to sign up for our Beta program (or come see me at Orlando's bitcoin conference this weekend).
Also, with regards to the recent Bloom Filters leak (http://eprint.iacr.org/2014/763), that doesn't really affect us, since our wallets use direct HTTPS connections to our server nodes, and our servers are the only ones that get to hear the address requests. However, we used to log connections for a few days for debugging purposes, but with increased privacy concerns and in preparation for HD wallets (where we don't want to link each new address to the old one), we have now completely disabled logging of addresses. So, even if our servers are compromised, we won't have any information to give out. Eventually we will move completely to Tor, making all connections anonymous, but if you are concerned about that now, we do support Tor (Orbot app) in the current version of the wallet. Just install Orbot, and set up a proxy in Settings to point to localhost:9050.
Bitcoincard - Progress is progressing, right on schedule. Next batch of test units is coming in, UI is even more streamlined, etc. Still expecting end of the year / early next year as the release date. Not much to add besides that, since the hardware is pretty much final. Just tweaking software.
Conferences - I'll be at the http://coinsinthekingdom.com/ conference in Orlando this weekend. Stop by and say hi, see a Mycelium Entropy demo, and I can give you a copy of our RC2 version of our Wallet to try out. I don't think we have any plans for forthcoming conferences, but if there's somewhere where you would like to see us, please let us know!
And finally
A REQUEST - Since we are planning on moving to Tor, we want to make sure that whatever code source we choose will not degrade user experience. So, we need to do some testing on different phones and in different countries. If you are able and willing to help, could you please install Orbot from the play store, and let us know if it works, how long it takes to connect from the Offline to Connected state, and if you can, what country you are testing in? Mainly we want to make sure that users won't be standing around waiting for a minute for their Mycelium Wallet to load and sync, and especially that we don't inadvertently block whole countries from being able to use our wallet.
Thank you!
submitted by Rassah to Bitcoin [link] [comments]

Profit Trailer : A Newbie Guide to Setting up your first Crypto Trading Bot!

Hello Everyone! Unless you’ve been living under a rock, you’ve likely heard all about BitCoin, LiteCoin, Ethereum and a whole host cryptocurrencies. As cryptomining profitability fades underneath increasing difficulties and the rising cost of mining machines, the world is dazzled by the utterly insane profit margins to be made in TRADING cryptocurrencies. This typically leads the average Joe to look into and, likely, invest some money into the cryptocurrency market. And, as time progresses (especially if profits are being made), one inevitably must make a choice to use a trading bot or not.
Now, I’m not trying to sell you one way or the other. My goal here is to take one of the newest and seemingly most profitable of the numerous trading bots out there, Profit Trailer, and break down getting the bot installed and running. There are numerous guides to Profit Trailer Installation and all of them are good. Crypto Gnome has some excellent information at https://github.com/CryptoGnome/Profit-Trailer-Settings/wiki/Setup-Guide. I’m not trying to knock him or anyone else with a guide out there. BUT………….
There are a few things that, in the course of installing this bot for a family member who has gotten on the crypto wagon in a big way, I noticed were lacking in the main set of guides. This being that not one of them had been designed with the true noob in mind. Each assumed a level of knowledge and discourse that can ( and would) leave a newbie cursing the fact they just spent .03 of a Bitcoin on something that refuses to even start.
Anyway, the point is, if you don’t have a tech savvy person handy, you could be left with, at best, the program downloaded but unable to start it or at worst, out a nice chunk of your crypto because of failing to understand EXACTLY what is needed to make the bot operate. Any suggestions on how to make this guide more complete, such as adding specific exchange instructions would be most appreciated.
Have an account at either Bittrex, Poloniex or Binance ACTIVE! I have read horror stories regarding buying this bot and installing it without having your account open and logged into. Just in case there is truth to them, better to be safe than sorry. Open your account of choice ( we used Binance so that is the exchange that this guide refers to. ) Use the account interface to create TWO(2) sets of API keys. One will be public, one will be secret in each set. You will notice that, at least on Binance, that each set of keys will have 2 permissions checked and one, withdrawals, unchecked. This is as it should be. If for some reason the withdrawals permission is checked, delete the key and start over. I would suggest that, for ease of use sake, you label each of the sets of keys. The first should be labeled (yourexchange)Default and the second should be labeled(yourexchange)Trading. This will help you recognize which keys are which later in the setup process. Copy these into a Notepad file, Word file, write them on your bedroom walls in blood, just keep BOTH SETS OF THESE API KEYS SAFE! Anyone with these keys has access to your exchange account. The first key will be initially used when you buy the Profit Trailer bot. The others will be used when you set up Profit Trailer. Ensure that you have JAVA 8 installed and running on your computer. It is extremely important that it be JAVA 8 and not 9. Profit Trailer WILL NOT WORK WITH THE JAVA 9 JRE. This problem was likely the biggest hurdle with Profit Trailer until I realized what was happening. Download and install Notepad++. Very Important. Some guides make it sound like you can do the settings changes on a regular NotePad file. This may be true, but Notepad++ is an actual IDE (software writing program for the uninitiated) that will give you the same view that all the guys in their YouTube Videos have up when they discuss their settings. Just saying guys, you’ve got people who, while they might know how to trade, might not know squat about IDE’s and their function. Buy the bot. This can be accomplished at https://profittrailer.com/pt/CryptoGnome/ At check out, you will be asked for the FIRST of the API keys you created. This will be the, first PUBLIC key you created. Pay for the bot. Wait for BitCoin to go from wallet to Profit Trailer creators. Have a beer….Smoke a cigarette….watch a movie. Seriously, you’re gonna be waiting awhile. One good idea while you spend hours waiting for the license key to be sent to you is to ensure that, if you have a newly created exchange account, you should place some cryptocurrency/money in the account…otherwise you’ve got another wait. Most guides say to next get a VPS(Virtual Private Server or Cloud Server). I was unable to get a VPS enabled at the time of this installation, so I will be posting another article regarding that process as soon as I can get it up and running on this installation. UPDATE We now have a Windows VPS running. You can visit Profit Trailer And You: A Newbie Guide To Setting Up Profit Trailer Part 2: Windows VPS here. Get Profit trailer Up and Running!!!! Here’s what you’ve been waiting for and trust me, all the other “prep stuff” will make this part a whole lot smoother. First, go to https://github.com/taniman/profit-trailereleases download the latest version of Profit Trailer. Next, unzip the files and navigate to the new folder. Open the file named application.properties with Notepad++ and then stare at it. I mean… really stare at it. Scary huh? Looks like you’re about to start coding the next Destiny game doesn’t it? Relax. this is a simple IDE that is giving you a series of settings that have to be adjusted manually instead of using a graphics user interface like the ones we’ve all grown to know and love. What you really need to know is what you are looking at. You’re going to see things like “trading.exchange” and “default_apiKey”. Each of these lines will have an equals sign on the end of them. Concentrate on what’s on the right side of the equals sign, cause that’s where your info is going to go. Remember those API keys you made? Well, here’s where they go.
Update these settings:
trading.exchange = THE EXCHANGE YOU ARE USING e.g. BITTREX (This MUST BE IN ALL CAPS. using lower case letter will give you an error code on startup)
default_apiKey = THE FIRST API KEY YOU CREATED (The key you labeled (yourexchange)Default )
default_apiSecret = THE FIRST SECRET KEY YOU CREATED
trading_apiKey = THE SECOND API KEY YOU CREATED (The key you labeled (yourexchange)Trading )
trading_apiSecret = THE SECOND SECRET KEY YOU CREATED
server.password = PASSWORD HERE (This is a password you create here. it is not tied to any other account)
Click save
You with me so far? Keep in mind that, so far the bot IS NOT RUNNING. we haven’t turned on anything yet, so don’t worry.
Most of the other guides say to start the bot up at this point and I would tend to agree, except you may want to look at the default settings in the pairs and DCA files to ensure that they are set the way you want them. DCA settings are a huge factor in Profit Trailer and I would suggest watching several videos regarding them. I do not claim to be a crypto expert and do not pretend to understand all the terms. The Profit Trailer Wiki at https://wiki.profittrailer.io/doku.php/dca.properties has in depth articles dealing with each of the settings and I suggest getting very familiar with them and understanding exactly what each does before turning the bot on.
Ok, with that being said, if you feel like your settings are just the way you want them, open up the pairs.properties file in Notepad++ and change “ALL_trading_enabled=false” to “ALL_trading_enabled=true” and save the file. Next you will want to click ‘run’ on the ProfitTrailer.cmd file. This will actually start the bot and will open an old style black Windows command line window. Ignore this as it is just the bot starting up, not where you will see what the bot is doing and open your web browser and enter http://localhost:8081/monitoring in the URL field. This will bring up a login page. Use the Password you created in the application.properties file here. This opens the web monitoring dashboard for your bot.
Again, I cannot stress enough the importance of following each step and understanding what each of the settings in Profit Trailer are and what they do. There are several important safety valves in Profit Trailer to keep the bot from chewing through your crypto like cookie monster on a 3 day bender.
One is “ALL_max_cost = x.xxxxx” in pairs.properties. This sets the amount of coin, in BitCoin, that the bot will use for trading. Just because you have have 1.5 BTC in your exchange account doesn’t mean you’ve gotta let the bot play with it all. “ALL_min_buy_balance = x.xx” in the pairs.propertiesfile will accomplish the same thing, just specifying an amount in the account that the bot will not take the account below. There are several important safety triggers in the DCA files as well, one being “min_buy_balance = x.xx” which will keep a specified minimum of BTC in your account, below which NO DCA buys will occur. This is an important distinction from the “ALL_min_buy_balance = x.xx” found in the pairs.properties files; DCA buys will STILL OCCUR even if the account is at or below the minimum specified in the pairs.properties file. Confused yet? It makes sense really, but if you’re like me, DCA really doesn’t mean anything to you. ( It’s Dollar Cost Averaging and it’s a profit mechanism used by Profit Trailer) What it really means is that, if you don’t know or understand what you are doing, it can cause big problems trading. Use your safety triggers and brush up on your trading terms cause soon you’ll be hip deep in EMAGains and Dust Bags…..whatever that means.
Any info on other exchange procedures with reagrds to setting up Profit Trailer would be greatly appreciated. I am not affiliated with or paid by any exchange, developer or site.
Credit & Thanks for this guide by: https://steemit.com/@demonsthenes
submitted by treasuregnome to CryptoCurrency [link] [comments]

Noob in web design, looking for some basic help.

Hello. I work in the IT field, but I dont work in code/web design much unless its just modifying some stuff for my own use. So I can usually get stuff done after playing with it for a bit. Ill be honest, this is for a bitcoin mining monitoring (nothing professional. Im actually stopping all together after I get my last payout.) I just want a better way to monitor my computers. Most of everything is already in place with the software. I just want to add to it for myself.
This isnt a huge deal, just something I would like to have personally and if I cant get any help/info here, no worries. Its just something I was looking to do to learn a bit, and have a more unified interface. But like I said, it wont even be running for long anyways.

Im looking to maybe add a new docker on my unraid server for hosting a local webpage only displaying stats being reported by computers/miners on my network.

The 4 machines already have a viewable webgui displaying all of the stats I want that I can view by pointing that machines browser to localhost:port, but I would like to be able to make it so instead of having to view each one separately on each device, I can have them all point to a web server and that webserver just display all of that info as a group on a single page.

In my mind, all that is is just modifying a few lines/values in some of the .ps1 file or one of the files in the folder "web" that has the page info. I didn't want to link the GitHub page and break one of the rules on the sidebar by mistake (unless its okay?). But the built in webgui for the monitoring seems pretty simple. I just wasnt sure where to start other than getting the docker setup. I know I need to point each machine to the webserver instead of the local host, or maybe have the server look for the port each machine is running its local page on?

Any info would be appreciated.
submitted by Spotopolis to web_design [link] [comments]

looking for ways to keep in touch with lots of machines using Python

I have loads of little machines running all over the place, a Raspberry Pi running a Bitcoin miner on my balcony, a Pi running a security system, my work desktop behind a silly firewall, a few servers... How can I keep in touch with all of them using Python?
Right now, I have the crazy setup of having all of them reverse SSH connect to a public server continuously:
while true; do ssh -R 19999:localhost:22 www.crazyserver.pro sleep 30 done 
They all have their own ports and try to keep the SSH connection going (and I can access them on the server like ssh localhost -p 19999), but this seems bonkers to me.
Slightly less bad might be trying to get all the scripts to listen to me via Signal or Tox or something, and then to run their call_home_using_reverse_SSH functions when they parse a command to do that in a message, but I don't really know how to do this sensibly -- and in a way that is decentralised and not particularly reliant on a public server or private business.
What might be good ways to do this? I need ways that don't require me to think about ports and permissions etc. because I have too many machines in too many situations. The only assumption I can really make is that they all have web access and all can launch SSH connections.
submitted by BlandCorporation to learnpython [link] [comments]

Problems with ElectrumX server

I have setup my ElectrumX server, but I, nor anyone else can connect to it, Im using UFW and the ports are definitely not blocked, looking in netstat I dont even see any process listening on the electrumx server ports. Any assistance will be greatly appreciated.
Also there are no errors in the logs and it is currently 1,002 blocks behind, and chugging along.

EDIT:

I have been told that you cannot connect to your electrumx server until it has finished synchronizing at least once. I have submitted a request to improve the documentation.

Here is my electrumx.conf:

DB_DIRECTORY = /db
DAEMON_URL =
DB_ENGINE=rocksdb
SSL_CERTFILE=/etc/electrumx/server.crt
SSL_KEYFILE=/etc/electrumx/server.key
TCP_PORT=50011
SSL_PORT=50012
HOST=127.0.0.1,xx.xx.xx.xx,0.0.0.0,xx.xx.xx.xx
COIN=BitcoinSegwit
DONATION_ADDRESS=3Nwnujrf2jEghDGiQ2QNmbV2tJSvjwodrt
REPORT_HOST=
REPORT_TCP_PORT=109
REPORT_SSL_PORT=110
BANNER_FILE=/etc/electrum.banner
IRC=yes

Here are the logs:

Dec 4 13:26:49 such electrumx_server.py[17106]: INFO:root:ElectrumX server starting
Dec 4 13:26:49 such electrumx_server.py[17106]: INFO:Controller:event loop policy: None
Dec 4 13:26:49 such electrumx_server.py[17106]: INFO:Daemon:daemon #1 at localhost:8332/ (current)
Dec 4 13:26:49 such electrumx_server.py[17106]: INFO:BlockProcessor:switching current directory to /db
Dec 4 13:26:49 such electrumx_server.py[17106]: INFO:BlockProcessor:using rocksdb for DB backend
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:opened DB for serving
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:software version: ElectrumX 1.2
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:DB version: 6
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:coin: BitcoinSegwit
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:network: mainnet
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:height: 496,598
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:tip: 0000000000000000000e7bba0287a645ad27a20f4cca815f2e3535e954b99e16
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:tx count: 275,887,788
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:flush count: 230
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:BlockProcessor:reorg limit is 200 blocks
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 1/13 btc.smsys.me from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 2/13 E-X.not.fyi from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 3/13 elec.luggs.co from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 4/13 electrum.vom-stausee.de from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 5/13 electrum3.hachre.de from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 6/13 electrum.hsmiths.com from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 7/13 erbium1.sytes.net from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 8/13 helicarrier.bauerj.eu from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 9/13 hsmiths4fyqlw5xw.onion from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 10/13 luggscoqbymhvnkp.onion from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 11/13 ozahtqwp25chjdjd.onion from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 12/13 us11.einfachmalnettsein.de from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:PeerManager:accepted new peer 13/13 ELEX01.blackpole.online from coins.py
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:Controller:RPC server listening on localhost:8000
Dec 4 13:27:49 such electrumx_server.py[17106]: INFO:Prefetcher:catching up to daemon height 497,600 (1,002 blocks behind)
Dec 4 13:36:37 such electrumx_server.py[17106]: INFO:BlockProcessor:our height: 496,608 daemon: 497,600 UTXOs 14MB hist 16MB
Dec 4 13:36:37 such electrumx_server.py[17106]: INFO:BlockProcessor:processed 10 blocks in 521.0s
Dec 4 13:39:22 such electrumx_server.py[17106]: INFO:BlockProcessor:our height: 496,617 daemon: 497,602 UTXOs 24MB hist 29MB
Dec 4 13:39:22 such electrumx_server.py[17106]: INFO:BlockProcessor:processed 9 blocks in 161.3s
submitted by murlidhara to Electrum [link] [comments]

Success with Raspberry Pi 3 and Blockchain API v2

I managed to get my Skyhook running on a Raspberry Pi 3 and it is successfully using the new Blockchain API v2 via the blockchain-wallet-service. The send-bitcoin process via the v2 service on the Pi3 takes only about 5 seconds. Not too bad at all.
Although it may be possible to image a MicroSD card with the contents of the regular Pi1 SD card, I opted to start from a fresh Rasbian Jessie (non-lite) install and start assembling the pieces from there.
After the usual Raspberry Pi setup procedures (expand filesystem, configure to boot to console, apt-get update, apt-get dist-upgrade etc etc)... here is a list the things I needed to address to get everything working. Please note I assembled this list through a lot of trial and error and had to backtrack a few times. I tried to keep track of just what was necessary but it is possible I missed some items from my notes below.
I mounted my original skyhook SD card via USB on my Pi3 so I could copy across files as needed. Whenever copying files, keep the permissions and ownership etc (cp -a) Also, when copying over config files, keep the original if possible. Sometimes handy to reference.
Install needed packages
Compare your old and new /vacache/apt/archives and start filling in the missing pieces. I started with php5, php5-mcrypt, apache2 etc. etc. I didn't try to duplicate those lists... just installed the obviously needed ones.
Main skyhook web directory
Copy your /vawww/btc dir across to the new pi.
Configure PHP
Copy /etc/php5/apache2/php.ini across and comment out (with semicolons) the 5 lines related to 'apc' at the bottom. I tried installing the apc.so library and ran into problems and found elsewhere that apc isn't really necessary anymore (?) with more recent php.
Configure Apache
Copy your /etc/apache2/sites-available/skyhook config file across to the new pi and add a symbolic link from the site-enabled (and remove the link for the default one). Note that you need to name the file with a .conf extension now. So name it "sites-available/skyhook.conf" and symbolically link it with the same name.
The mod-rewrite module needs to be enabled. Create the necessary symbolic link in mods-enabled to the mods-available dir.
Restart apache2.
Setup MySQL
Copy across the database dir to new pi: /valib/mysql/skyhook/
You also need to copy across ibdata1, ib_logfile0 and ib_logfile1 from the /valib/mysql directory.
Change ownership of all those files to mysql:mysql if they aren't already.
Restart mysql.
Add the "skyhook" mysql user with skyhook DB permsissions with empty password. Run "mysql" as root. > GRANT ALL PRIVILEGES ON skyhook.* To 'skyhook'@'localhost' IDENTIFIED BY ''; > FLUSH privileges;
Bill Scanner
The bill-scanner driver gets executed during the purchase stage and is executed as used "www-data". The original setup would modify the ownership of /dev/ttyUSB0 at bootup so that www-data could access it. This doesn't seem to work anymore on Jessie and the device remains with root:dialout ownership. So, instead, I just added www-data to the dialout group.
$ sudo usermod -a -G dialout www-data 
The python script also needs the "pycrypto" library.
$ sudo apt-get install python-crypto 
Temp ramfs directory
When you boot your Skyhook and type your admin password, the decrypted blockchain credentials (etc) are stored in a ramfs mount /tmp_disk
Create the directory as root then add the following to /etc/rc.local to properly setup the ramfs at boot (add it just above the exit 0):
/bin/mount -t ramfs -o size=32m,rw,uid=pi,gid=www-data,discard,user ramfs /tmp_disk /bin/chown pi:www-data -R /tmp_disk /bin/chmod 0770 /tmp_disk 
Blockchain API v2 wallet service
Install the wallet service as per: https://github.com/blockchain/service-my-wallet-v3#installation
I needed a newer version of nodejs and npm than is provided in the Jessie repo. Use this: https://learn.adafruit.com/node-embedded-development/installing-node-dot-js
The addition of the new blockchain v2 api_key needs to be integrated into the php files. I don't have my changes documented so will need to add that in a comment later. Sorry.
To have the wallet service run at bootup I added the following to my /etc/rc.local file (again, somewhere above the "exit 0"):
cd /tmp # needed so nohup can output its nohup.out logfile /sbin/runuser www-data --shell=/bin/sh -c "/usbin/nohup /usbin/blockchain-wallet-service start &" 
I opted to have the service run as "www-data".
Networking
The Pi will have two network interfaces. The ethernet plug (eth0) and the Nexus wifi (usb0). Jessie does networking slightly differently. See: https://www.raspberrypi.org/forums/viewtopic.php?p=798866#p798866
In /etc/network/interfaces I commented out the wlan0 and wlan1 sections, set the eth0 interface to 'manual' and added a new interface line for the Nexus usb0 interface.
iface usb0 inet manual 
With those interfaces set to 'manual' in there, you now need to configure them in /etc/dhcpcd.conf The eth0 will default to dhcp but I added the following lines to the bottom of the file for usb0:
interface usb0 static ip_address=192.168.42.45 static routers=192.168.42.129 static domain_name_servers=8.8.8.8 
Done!
And that was it!
Along the way I found the following logs useful for diagnosing errors:
Not sure how alive Project Skyhook is anymore but I hope this is useful for some people. Please let me know if you have any questions and I'll do my best to answer them.
submitted by TKRSRY to projectskyhook [link] [comments]

I can't set up a full node!! Help!!

I open the port on my router, when check with "bitcoind getnetworkinfo"
I have 8 connections, try to use the IP and port on https://getaddr.bitnodes.io/ and it says not connected.
If I type in terminal: netstat -nptl
As a result I have this:
(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:2628 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:8332 0.0.0.0:* LISTEN 24081/bitcoind tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN 24081/bitcoind tcp 0 0 127.0.0.1:5941 0.0.0.0:* LISTEN - tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN - tcp6 0 0 ::1:631 :::* LISTEN - tcp6 0 0 :::25 :::* LISTEN - tcp6 0 0 :::445 :::* LISTEN - tcp6 0 0 :::139 :::* LISTEN - tcp6 0 0 ::1:8332 :::* LISTEN 24081/bitcoind tcp6 0 0 :::8333 :::* LISTEN 24081/bitcoind
If I try this http://www.lurkmore.com/mining/port8333/ it says that I haven't open the port, but this is untrue!
In port fowarding setup I have:
PORT FORWARDING SETUP
Server Name External Port Start External Port End Protocol Internal Port Start Internal Port End Server IP Address Schedule Rule Remote IP bitcoin 8333 8333 TCP 8333 8333 192.168.1.1 Always bitcoin1 8333 8333 TCP 8333 8333 192.168.1.2 Always bitcoin2 8333 8333 TCP 8333 8333 192.168.1.3 Always bitcoin3 8333 8333 TCP 8333 8333 192.168.1.4 Always folding_at_home 36330 36330 TCP 36330 36330 192.168.1.1 Always 0.0.0.0 
Why it doesn't works?
PS using this "sudo ufw allow 8333" nothing change...
submitted by pietrod21 to BitcoinBeginners [link] [comments]

sx Bitcoin utilities (new installation instructions and information inside)

Hi!
My aim with this project is to provide a set of modular Bitcoin commandline utilities, that admin types can engage with Bitcoin functionality without having to write code.
By chaining all these commands together in different ways, you can do offline transactions, maintain a wallet, work with deterministic keys, ...
It would be cool to see Bitcoin wallets written in bash script using these tools to handle the core functionality. I believe the more we give good tools to the community, the more we can decentralise development and increase access to the core technology for all types.
Use this bash shell script to install sx: http://libbitcoin.dyne.org/install-sx.sh

START HERE:

$ wget http://libbitcoin.dyne.org/install-sx.sh $ sudo bash ./install-sx.sh 
sx should now be installed.
Enjoy!
Installation commencing NOW. ... 

Instructions

Development repository:
https://github.com/genjix/sx/
My Bitcoin address (from http://libbitcoin.dyne.org/):
1Fufjpf9RM2aQsGedhSpbSCGRHrmLMJ7yY
I want your feedback and suggestions! [email protected]
http://i.imgur.com/8R0cfuw.png
Type sx-TAB to see a list of all the sx commands.
Command Description
sx-addr see Bitcoin address of a private key.
sx-broadcast-tx broadcast tx to network.
sx-mktx create an unsigned tx.
sx-newkey create a new private key.
sx-newseed create a new deterministic wallet seed.
sx-mpk extract a master public key from a deterministic wallet seed.
sx-genpriv generate a private key deterministically from a seed.
sx-genpub generate a Bitcoin address deterministically from a master public key.
sx-mnemonic work with Electrum compatible mnemonics (12 words wallet seed).
sx-sendtx send tx to a single node.
sx-showtx show the details of a tx.
sx-sign-input sign a tx input.
sx-genqr generate Bitcoin QR codes offline.
sx-balance show balance of an address.
sx-history get list of output points, values, and their spends for an address. grep can filter for just unspent outputs which can be fed into mktx.
sx-watchtx watch transactions from the network searching for a certain hash.

Simple Bitcoin Client

Try this to make a mini-wallet.
$ cd src/ $ sx-newkey 5KPFsatiYrJcvCSRrDbtx61822vZjeGGGx3wu38pQDHRF8eVJ8H $ sx-newkey > private.key $ cat private.key | sx-addr 134HfD2fdeBTohfx8YANxEpsYXsv5UoWyz 
Now send some funds to your address (0.01 BTC).
In this example we will send the funds to 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe.
100000 Satoshis (0.001 BTC) in total. 90000 Satoshis (0.0009 BTC) to send. 10000 Satoshis (0.0001 BTC) for the fee. 
Use blockchain.info (or the history tool provided here) to lookup the output for this address. Note down the transaction hash and transaction index.
Here is a screenshot of blockchain.info: http://i.imgur.com/dZvqJIV.png
We can see the tx hash is: 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3 And there is a single output at index 1 that we want to spend (the 2nd one for 0.001 BTC).
Construct the transaction:
$ sx-mktx txfile.tx -i 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3:1 -o 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe:90000 
Because there is 100000 Satoshis going in, but only 90000 Satoshis out, the remaining 10000 Satoshis (0.0001 BTC) will be taken by the Bitcoin network as a fee. This is how fees work internally in Bitcoin.
'showtx' allows inspecting of tx files.
$ sx-showtx txfile.tx hash: 4d25b18ed094ad68f75f21692d8540f45ceb90b240a521b8f191e95d8b6b8bb0 version: 1 locktime: 0 Input: previous output: 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3:0 script: sequence: 4294967295 Output: value: 90000 script: dup hash160 [ 18c0bd8d1818f1bf99cb1df2269c645318ef7b73 ] equalverify checksig address: 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe 
Note that the input script is empty.
We will now sign the first input using our private key.
$ cat private.key | sx-sign-input txfile.tx 0 $ sx-showtx txfile.tx hash: 4a8be467fb75f0f757649348dbb05762142236ec236ac9e55e4683d7083ffca2 version: 1 locktime: 0 Input: previous output: 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3:0 script: [ 304602210083f8b5131f6399cdc01ed8368f6137f288f771e40834a94d65cee6b380fec873022100da5ed6d1d283f228752a88c2d6f629587b2a6fbc102202ae7c20f48af7c0533c01 ] [ 04e3af7cdfaab6ba2f14001a7ea0a490f40c6ba43607be92a05111d2e8fc1eecf6fa2c248b3e25ddf7db081684f6f49dc83fd7b9b5a3a88a2e6b83b918f8972351 ] sequence: 4294967295 address: 134HfD2fdeBTohfx8YANxEpsYXsv5UoWyz Output: value: 90000 script: dup hash160 [ 18c0bd8d1818f1bf99cb1df2269c645318ef7b73 ] equalverify checksig address: 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe 
Now the input script is prepared, and the tx is signed.
Broadcast the final tx to the Bitcoin network.
$ sx-broadcast-tx txfile.tx 
Or to send it to one Bitcoin node (like a localhost one), then use:
$ sx-sendtx txfile.tx localhost 4009 

QR Code Generator

$ sudo apt-get install qrencode $ sx-genqr 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe qrcode.png 

Deterministic Wallet

$ sx-newseed > wallet.seed $ cat wallet.seed b220b5bd2909df1d74b71c9e664233bf $ cat wallet.seed | sx-mpk > master_public.key 
Now you can generate your private keys for whatever number:
$ cat wallet.seed | sx-genpriv 0 5Jmb4EYzEqj63rkPwADFY7WyGV2kga3YB1HfDAzg9dHNG57NMPu $ cat wallet.seed | sx-genpriv 1 5KjCYpPyxU2e88S57b1naKUsJ1JNjCudkFSQPxqcYyBYgzzahNe 
You can use either the master_public.key or the wallet.seed for generating Bitcoin receive addresses. But you cannot use the master_public.key for generating the private keys for spending those Bitcoins.
$ cat master_public.key | sx-genpub 0 1a4b47AC4ydSnAAcTNH1qozHq2pwJb644 $ cat wallet.seed | sx-genpub 0 1a4b47AC4ydSnAAcTNH1qozHq2pwJb644 
For Electrum compatible 12 word seeds, use the mnemonic tool.
$ echo 148f0a1d77e20dbaee3ff920ca40240d | sx-mnemonic people blonde admit dart couple different truth common alas stumble time cookie $ echo "people blonde admit dart couple different truth common alas stumble time cookie" | sx-mnemonic 148f0a1d77e20dbaee3ff920ca40240d 

balance/history (Advanced)

The balance/history tools can then use a network connection to make requests against the load balancer.
$ echo 134HfD2fdeBTohfx8YANxEpsYXsv5UoWyz | sx-balance 100000 $ echo 134HfD2fdeBTohfx8YANxEpsYXsv5UoWyz | sx-history Output Hash:Index Output Height Value (Satoshis) Spend Hash:Index Spend Height 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3:1 247683 100000 Unspent 230529504 
It's possible to run as many backend workers as you like. The load balancer (obbalancer) will distribute requests evenly among the backends. Use worker-output.sh to view debug info from the worker. Each worker must have their own unique copy of the blockchain database.
See the Obelisk config files in /uslocal/etc/obelisk/. The sx config file is stored at ~/.sx.cfg (there's an example at /uslocal/share/sx.cfg). You can change this configuration parameter using './configure --sysconfigdir=/etc/'. By configuring different workers and load balancers, you can run multiple setups on the same host. By default it is no pointing at my development server, but I will change this soon and migrate to a new host. Also I make no guarantees about stability or compatibility.
submitted by genjix to Bitcoin [link] [comments]

Are issues sending payments normal?

I'm testing out joinmarket after getting it setup. Have everything running through the tor hidden service. My first payment out seemed to work at first. It ran for about 20 minutes before failing.
Now I continually get "Not enough counterparties" displayed in the terminal and "Not enough transactions" displayed via the GUI itself. Also about 15 seconds before this occurs I get a message that simply says "Transaction has failed" and then it proceeds to tell me about the counterparties a little after.
This is the output in the GUI that shows when the initial "Transaction has failed" appears which occurs almost instantly after syncing the wallet and trying to use the socks5 proxy...
DEBUG:Using socks5 proxy localhost:9150
AttributeError("'IRCMessageChannel' object has no attribute 'fd'",)
DEBUG:CRASHING, DUMPING EVERYTHING
Also I'm pulling the blockchain from bitcoin core and encrypted that wallet file with a separate passphrase. Does that matter as it's not actually using that wallet?
Edit: Same issue with clearnet host although still being routed through tor proxy. It doesn't give me the initial error, just the "not enough counterparties". I assume this is self explanatory but how usual is this occurrence?
submitted by joinmarketonion to joinmarket [link] [comments]

Browsing through Tor + SSH tunnel, have I missed anything?

I am playing around with anonymity on the web and so far the easiest way I have found is to use tor and an SSH tunnel to my VPS by doing:
torify ssh -C -D 8080 myserver.com
and setting firefox to use localhost:8080 as a socks5 proxy.
Obviously I need a VPS that isn't related to me in any way, but that is my second question. First of all does my setup ensure all my traffic is encrypted through tor and out to my VPS? Are there any weaknesses in this method, like rogue exit nodes?
Second question, how can I get a VPS anonymously? I was looking into bitcoin but it seemed a bit of a pain. Any good methods?
submitted by Midasx to antiforensics [link] [comments]

Help with getting things to start mining scrypt currencies (using raspberry pi 2 , gridseed asic miner , & cgminer) . . .

Here's what I have & will be using (I already have the cables & power) :
raspberry pi 2 Gridseed ASIC Miner for Litecoin and Bitcoin Mining --- 4 of these cgminer
[ I followed this example for setting things up : https://www.reddit.com/defcoin/comments/23nvs1/raspberry_pi_asic_defcoin_mining_guide/ it is my understanding that any altcoin you wish to setup mining for , is done in this similar fashion ]
I want to do scrypt cryptocurrency mining , I just want to understand how this is done ....
( I know there's a lot of tutorials out there & great vids , and I've done a lot of reading on all this matter , but I can't seem to get things working right , please help / advise )
Questions:
  1. if I solo mine , what is the correct port # to use here (and is the below command formatted correctly more-or-less) :
sudo ./cgminer -o stratum+tcp:localhost:#### -u Username.Workername -p yourworkerpassword --gridseed-options freq=850
( I understand I need to create my own pool , a pool of 1 , is considered to be solo-mining , correct ? How do I do this ? )
  1. also , before I can solo-mine , I need to have downloaded & install the wallet for the cryptocurrency I am going to mine , correct ? And I understand there is some kind of Config files relevant that I should modify accordingly to set things up with my mining solo , right ? How is it done & where do I find this config files ??
  2. I tried connecting my 4 gridseed(s) to my raspberry pi 2 , via the 4 usb ports it has , but it seems like it can't handle the 4 of them , so I have to deal with only using 2 of the gridseed(s) connected to my raspberry pi 2 at a time .... does this seem right to you ? And so , what work around do I have for this poroblem , I want to use all 4 of these gridseeds connected to my raspberry pi 2 ,,, I'm guess a usb hub is needed for this right ?
THANKS IN ADVANCE FOR YOUR HELP AND GUIDANCE !!!
submitted by justahotmininggirl to scryptmining [link] [comments]

Browsing through Tor + SSH tunnel, have I missed anything?

I am playing around with anonymity on the web and so far the easiest way I have found is to use tor and an SSH tunnel to my VPS by doing:
torify ssh -C -D 8080 myserver.com
and setting firefox to use localhost:8080 as a socks5 proxy.
Obviously I need a VPS that isn't related to me in any way, but that is my second question. First of all does my setup ensure all my traffic is encrypted through tor and out to my VPS? Are there any weaknesses in this method, like rogue exit nodes?
Second question, how can I get a VPS anonymously? I was looking into bitcoin but it seemed a bit of a pain. Any good methods?
submitted by Midasx to onions [link] [comments]

Is it a good idea to put wallet.dat in a hg repo?

Hi, I started with bitcoin. I will soon buy my first coin, 'play money', nothing serious or expensive. Will probably be donated to figure out how stuff works.
I use mercurical for just about everything.
For BTC, I will use two Linux computers. (I'm root on both and no one else has root access.) Each computer has a user account with encrypted home exclusively for BTC. They can communicate with each other via ssh over VPN. I have create a hg repository in ~/.bitcoin and wrote a small script around bitcoin, which commits changes after bitcoin exits. I will start bitcoin using
ssh [email protected] -X 'bitcoin_start_script'
From time to time, I will manually
hg fetch
form the other computer and expect to have a working wallet with all my coins.
Will this setup work. I'm aware that it will take some time to catch up with blocks before I can see transactions.
submitted by jan to Bitcoin [link] [comments]

Mining trouble with another ccurrency

I know this isn't about bitcoin.I am trying my chances at solo mining emerald and is there anyone who knows how to set up cgminer to do that. I've tried doing it before, i've set up my username and password for the .conf and also put cgminer ex: cgminer.exe --scrypt -o localhost:12128 -u yourusername -p password. ~like i said I have the user and password~ but i put that in cgminer as a .bat and it opens but says in cgminer ~wrong url~ ~pool setup failed~.Also in the .conf im using the default in what a previous tutorial told me (rpcallowip=10.1.1.*) am I supposed to put my ip or what? Im so lost
submitted by mg4637 to BitcoinMining [link] [comments]

Create a website on localhost - YouTube How to mine bitcoins (solo mining) with the core client ... How to setup a localhost - YouTube How to Buy Cryptocurrency for Beginners (Ultimate Step-by ... LOCALBITCOINS.COM: How to Open a Wallet, Send, Receive ...

Now you only need to visit your website in your onion-compatible browser to finish setup. Once you’re there, select English as your language and click Continue, then click Let’s go! In the form that follows, keep the database name as wordpress, change the username to admin, and change the password to the one you set earlier when we were configuring mariadb. Keep the database host as ... Bitcoin Node Setup. Learn how to set up your own Bitcoin node, how to work with the various nets the BTC Blockchain supports, and how to set up your first wallet. “We have already gained Bitcoins for development purposes, and we are ready to start programming.” This is the part where the real fun with the Blockchain starts. I will show you how to set up a Bitcoin node, explain what the ... See here for more info - you can setup a local hosts alias, in which case it makes sense to also update the callback url to be the same. 6). localhost gets "special" attention by user agents (incl. web browsers) that can cause unnecessary interference (broad statement, but true). 7). Auth0 now supports Custom Domains. Our setup consists of three services: Single Bitcoin node running in regtest mode, ElectrumX server, BTC RPC Explorer; We chose the regtest mode because it allows us to generate blocks on demand. For the sake of simplicity, I’d like to stick to a single node. While you could have more, this just adds unnecessary complication to the setup ... This bitcoin.conf is the configuration file for Bitcoin Core. Replace X with your username of choice, Q with the password you want it to be. Y is the TCP port number for RPC connections to listen to, which is the number you'll need for your Bitcoin Miner software. server=1 listen=1 daemon=1 rpcuser=X rpcpassword=Q rpcallowip=localhost rpcport=Y. Download and install the ASIC Bitcoin Miner ...

[index] [12918] [46118] [35187] [32902] [45787] [27716] [15896] [36877] [36361] [13870]

Create a website on localhost - YouTube

How to run Bitcoin-qt as a server with a configuration file (3 of 6) ... Creating a Local Bitcoin Testnet / Regtest - Programming Bitcoin - Duration: 23:19. Programming Bitcoin 19,360 views. 23:19 ... Check Out the UPDATED Version of this Ultimate Guide Here: https://youtu.be/sEtj34VMClU This video will teach you how to buy cryptocurrency for beginners ste... Buy or Sell Bitcoin Cash anywhere in the world without an ID or verification. A step by step walkthrough on how to buy or sell BCH on local.bitcoin.com by Ro... In this tutorial I tried to show how to setup a website on localhost. Prerequisites: 1) Have xampp installed 2) A code editor Software I use: 1) Xampp 2) Sub... http://bit.ly/2AObMo5 Pdf with Links, for BUYING BITCOIN http://bit.ly/2ylcR5L

#