Best Bitcoin Wallets for Ubuntu – Linux Hint

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]

All Usernames

Popularity Number Tried Usernames
1 root
2 admin
3 guest
4 supervisor
5 Administrator
6 user
7 tech
8 ubnt
9 default
10 support
11 service
12 888888
13 admin1
14 mother
15 666666
16 test
17 oracle
18 ftpuser
19 usuario
20 test1
21 test2
22 123456
23 test123
24 123
25 321
26 password
27 [email protected]
28 postgres
29 dev
30 testuser
31 tomcat
32 git
33 dspace
34 nexus
35 zabbix
36 teamspeak
37 ftpuser1
38 ubuntu
39 ts3
40 www-data
41 ldapuser1
42 minecraft
43 ghost
44 butter
45 redis
46 ts
47 teamspeak3
48 hadoop
49 tonyeadmin
50 pi
51 odoo
52 mysql
53 contador
54 cron
55 wp
56 ftp
57 weblogic
58 backup
59 ftp_user
60 ts3bot
61 1234
62 bin
63 student
64 user1
65 tom
66 ts3server
67 nagios
68 duni
69 test321
70 e8ehome
71 telecomadmin
72 db2fenc1
73 bitcoin
74 a
75 deploy
76 nginx
77 db2inst1
78 hdfs
79 abc123
80 jenkins
81 web1
82 dasusr1
83 operator
84 anonymous
85 csgo
86 camera
87 passw0rd
88 baikal
89 tplink
90 cssserver
91 tt
92 admins
93 tst
94 osmc
95 prueba
96 fulgercsmode123
97 y
98 odoo9
99 zookeeper
100 mahdi
101 wordpress
102 www
103 billing
104 111111
105 ftp_test
106 flw
107 b
108 redhat
109 steam
110 ohh
111 ops
112 abc123456
113 user8
114 ScryptingTh3cod3r~F
115 ts3user
116 centos
117 svn
118 user9
119 postgres123
120 vagrant
121 gituser
122 enable
123 elastic
124 user2
125 daemon
126 user3
127 walter
128 VM
129 havanaloca
130 csgoserver
131 demo
132 CUAdmin
133 servercsgo
134 css
135 spark
136 ftptest
137 data
138 localadmin
139 wangjc
140 ispadmin
141 1
142 adam
143 Accept-Language: zh-CN,zh;q=0.8
144 web
145 client
146 xuelp123
147 workpress
148 openssh-portable-com
149 cacti
150 zs
151 cubie
152 informix
153 Contact:
154 conf
155 hbase
156 ranger
157 msn
158 bot
159 spark1
160 radio
161 xc3511
162 pass
163 dev123
164 maven-assest
165 noah
166 linktechs
167 query
168 bot1
169 informix123
170 gzw
171 tss
172 NETBASE
173 es
174 oracle123
175 user123
176 mcserver
177 ftpadmin
178 linuxshell
179 app
180 optiproerp
181 wangshaojie
182 knox
183 org
184 nmstest
185 elasearch
186 Xinjiang
187 aticara
188 555
189 [email protected]
190 wwwdata
191 sh
192 jenkins123
193 henry
194 licongcong
195 crontab
196 oldbody
197 tez
198 122.152.213.96
199 zhang
200 Shaanxi
201 nobody
202 cf46e3bdb4b929f1
203 ethereum
204 aa
205 Jay123
206 ionhasbeenidle13hr
207 mysql-data
208 system
209 localhost
210 [email protected]
211 dzldblog
212 linuxprobe
213 bdos
214 raid
215 jira
216 zhouh
217 amx
218 wanjm
219 MPE
220 aaa
221 NISECTC5002
222 ec2-user
223 sandiego
224 iptv
225 shell
226 confluence
227 matthew
228 bizf
229 backupdb
230 hive
231 dell
232 tornado
233 zhou
234 blender
235 user0
236 c
237 @Huawei123
238 net
239 cat1
240 watch 'sh'
241 haohuoyanxuan
242 administrador
243 text
244 dell123
245 wybiftp
246 share
247 yanss
248 squid
249 kafka
250 db2as
251 PRODDTA
252 bitcoinj
253 user01
254 cc
255 [email protected]
256 12345
257 azureadmin
258 duanhw
259
260 zhangfei
261 easton
262 geoeast
263 lwx
264 ldd
265 aws
266 gv1
267 140.115.53.10
268 useradmin
269 tlah
270 walletjs
271 ccc
272 user4
273 solr
274 chef
275 python
276 GET / HTTP/1.0
277 12345678
278 customer
279 sss
280 geminiblue
281 ausftp
282 Chongqing
283 nologin
284 username
285 mining
286 user11
287 news
288 2
289 muiehack9999
290 user5
291 ubuntu123
292 docker
293 nexxadmin
294 wq
295 OPTIONS / HTTP/1.0
296 gpadmin
297 test5
298 kuangwh
299 nagios123
300 ams
301 gfs1
302 vsb_pgsql
303 140.238.189.155
304 carl
305 CONNECT ip.ws.126.net:443 HTTP/1.1
306 nvidia
307 wallet
308 [email protected]
309 3
310 db2fenc1123
311 user6
312 www1
313 andy
314 assest
315 OPTIONS / RTSP/1.0
316 azure
317 webftp
318 tab3
319 aliyun
320 smartworldmss
321 hcat
322 walle
323 zhangfeng
324 openlgtv
325 User-Agent: Go-http-client/1.1
326 wangw
327 kelly
328 usuario1
329 [email protected]#
330 x
331 Huawei1234
332 user7
333 sysadmin
334 video
335 tmp
336 GET /nice%20ports%2C/Tri%6Eity.txt%2ebak HTTP/1.0
337 dianzhong
338 clfs
339 wangk123
340 rsync
341 livy
342 xuezw
343 hduser
344 testing
345 HEAD http://123.125.114.144/ HTTP/1.1
346 bitcoind
347 matrix
348 cassandra
349 xx
350 F
351 backups
352 ktuser
353 barbara
354 sunxinming
355 OPTIONS sip:nm SIP/2.0
356 ftpuser123
357 michael
358 jiang
359 wangh
360 wolf
361 ikan
362 122.88.49.75
363 monitor
364 Proxy-Authorization: Basic Og==
365 pentaho
366 rootadmin123
367 wildfly
368 xxx
369 nobodymuiefazan123456
370
371 www2
372 serial#
373 From: ;tag=root
374 cat2
375 alice
376 robot
377 wowza
378 visitor
379 tab2
380 elasticsearch
381 gbase
382 motorola
383 superuser
384 User-Agent: Mozilla/5.01688858 Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36
385 sara
386 Jaydell123
387 linuxacademy
388 vps
389 xbmc
390 software
391 Call-ID: 50000
392 felix
393 portal
394 backupdb140
395 bdos123
396 greenplum
397 sshd
398 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8
399 daemond
400 qwe123
401 webmaster
402 [email protected]#
403 web13
404 bpadmin
405 ligh
406 leo
407 Max-Forwards: 70
408 password123
409 vivacom
410 dbvisa
411 tab
412 mongo
413 ggg
submitted by Admir4l88 to Admir4l88Data [link] [comments]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B

Intro

This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
 
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
 
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
 
The updates
 
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
     

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:
     

Extra

Backup
Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
 
 
   
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
   
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
   
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
   
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
   
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
 
   
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
   
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  
     

Credits:

   
Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

We need to figure out how to help newbies store and use their bitcoin safely

This is how I do it:
BACKUP:
master private seed words on paper , saved securely.
REGULAR USE:
Preparation: Created a USB bootable linux , install electrum on it , disabled its internet/networking (IMPORTANT!), put private keys in electrum wallet, copy public keys from electrum wallet to usb drive. Boot to regular OS (windows/mac) , open electrum, create watching only wallet with public keys saved on USB.
Using: Create transaction in electrum on regular OS -> save transaction to file on USB . Boot into usb linux -> load transaction from USB in electrum -> sign it, save to USB -> boot to regular OS -> load singed transaction from USB in electrum -> Broadcast!

Add encryption and passwords to the above, and I think its a fairly bullet proof method of storing bitcoins. The private keys are never exposed to any network. I struggled at the part of disabling internet, but it worked out in the end.
Obviously, this process is hard for the average joe. He will just keep his coins on some web wallet, defeating the point of bitcoin, and set themselves up to lose their btc down the road.
There really need to be a method to make this easier. Maybe a modified version of ubuntu, with no networking, encryption and electrum preinstalled ? There is trezor , but I don't have knowledge there. Comments?
submitted by Automataton to Bitcoin [link] [comments]

Reward - Help recovering corrupt wallet.dat /r/Bitcoin

Reward - Help recovering corrupt wallet.dat /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

[Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B

This tutorial has been updated: https://www.reddit.com/reddCoin/comments/a0wn1v/updated_staking_reddcoin_core_client_gui_wallet/.
   

Intro

I want to stake Reddcoins on my Raspberry Pi, but there is no easy to install package for the Reddcoin Core client. I found some tutorials (mentioned at the bottom, under 'credits'), but I still struggled to get the result I wanted. It took some small adjustments, but I got the GUI Wallet of Reddcoin Core working on my Raspberry Pi Model 3B. See the steps below. :).
 
If you have any questions or comments, please post a comment in this thread, so others can also benefit from it.
 
If you would like to tip me: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
   
Even though Raspbian is the primary OS for the Raspberry Pi, it seems that it's not possible to build and compile the Reddcoin wallet software for Raspbian Stretch. However, I got the wallet compiled using Ubuntu MATE.
     

Overview

     

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Extra

 
 
 
 
     

Credits:

 
Thank you all for sharing your knowledge!
submitted by Yavuz_Selim to reddCoin [link] [comments]

Backup solution for LN node?

Is there a good backup option for LN nodes yet? I want to be able to protect myself from total loss of hardware. Think fire, theft, unrecoverable drive error, and so forth. I'm able to accomplish this for a bitcoin wallet fairly easily with cloud and USB storage. Any similar solutions for LN nodes? I would be using a desktop with Ubuntu. I've wanted to run a LN node for a while and this is the one thing the really prevents me from committing any funds towards it.
Update: LND appears to have addressed this issues and created a way to keep dynamic backups. Information can be found here https://github.com/lightningnetwork/lnd/releases/tag/v0.6-beta under "Backup + Recovery Methods."
submitted by walkinglucky1 to lightningnetwork [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]

BTCPay Server + EPS + RTL - how?

I am trying to build a box with: - Linux Ubuntu 18.04 - BTCPay Server, using docker - EPS (Electrum Personal Server) - RTL (Ride the lightning)
I have the full bitcoin data synced in a folder already, from a previous bitcoin-qt/bitcoind instance.
  1. Can I install BTCPay Server with docker and then run beside another docker with EPS?
  2. I understand that RTL is already integrated into BTCPay, so I just have to update the server and activate it?
  3. Is possible to integrate also EPS into the BTCPay docker file, after the installation? Or is it in "works" to be integrated in the same docker installation/update server by BTCPay ?
  4. Is possible to run EPS without docker, but using the bitcoind from BTCPay docker instance?
  5. Is possible to connect a mobile wallet (ex. Samourai) to that bitcoind instance from BTCPay Server ?
  6. One last question: is there a procedure to backup all the BTCPay server settings, for in case of disaster recovery moment? So to restore all data at once after reinstall OS ?
This is very important thing, if I start to put a BTCPay server at work in production and the machine gets fucked, how easy is to restore it?
Please somebody can respond to these questions, not in a super technical manner so many others can understand it?
Maybe u/belcher_ and u/CardCollector1 or u/NicolasDorier can help with some answers here, please?
EDIT: I hope I don't have to add a meme to this post to bring more attention... seems that lately only memes are "important" here, subjects like this are ignored. EDIT2: 21 hours and still not any answer... fuck, nobody uses BTCPay ?
submitted by Mr--Robot to Bitcoin [link] [comments]

Introducing Litecoin as base currency - Huge Bisq/Bitsquare update - Check out v0.5.1

This release comes with tons of changes and improvements.
Please download at: https://github.com/bitsquare/bitsquare/releases/tag/v0.5.1
Most relevant changes are:
Please see the full release notes below.
As that release has very profound changes it is NOT backward compatible to the earlier versions. It uses a new network which is separated from the current trade network. So your offers from the current application will not be visible for users who are using the new version.
If you want to migrate to the new version you need to close your offers and withdraw your funds to the new application. You can run both applications in parallel as they are using a different data directory. You cannot move over the wallet or application data because the wallet format has changed (BIP44) and we use a different data structure for the data base files. So you need to transfer the Bitcoin with a BTC transaction and set up your payment account(s) manually.
Please double check with cmd+e in the old application if no funds are left over (some bugs might have caused that the balance displayed in the UI is not correct).
Please use small amounts when starting trading in the new application as with so many changes there are some risks for bugs (though it is thoroughly tested).
Release notes:
submitted by heavyuser1337 to litecoin [link] [comments]

Huge Bisq/Bitsquare update - Check out v0.5.1

This release comes with tons of changes and improvements.
Please download at: https://github.com/bitsquare/bitsquare/releases/tag/v0.5.1
Most relevant changes are:
Please see the full release notes below.
As that release has very profound changes it is NOT backward compatible to the earlier versions. It uses a new network which is separated from the current trade network. So your offers from the current application will not be visible for users who are using the new version.
If you want to migrate to the new version you need to close your offers and withdraw your funds to the new application. You can run both applications in parallel as they are using a different data directory. You cannot move over the wallet or application data because the wallet format has changed (BIP44) and we use a different data structure for the data base files. So you need to transfer the Bitcoin with a BTC transaction and set up your payment account(s) manually.
Please double check with cmd+e in the old application if no funds are left over (some bugs might have caused that the balance displayed in the UI is not correct).
Please use small amounts when starting trading in the new application as with so many changes there are some risks for bugs (though it is thoroughly tested).
Release notes:
submitted by heavyuser1337 to BitcoinMarkets [link] [comments]

Lost most of my Doge late 2013. There may be one last solution to getting some back. Does anyone have a copy of "DogeCoin version v0.6.4.0-unk-beta" or know which release it is directly linked to?

My keys corrupted and i didn't have a recent backup, after the upgrade lost all the doges.

I think there might be one more hope of finding some, and would appreciate if anyone knows which version " v0.6.4.0-unk-beta" which is on the debug.log output.

Noticed after all this time after digging through Bitcoin release notes that before bip32/hd wallets came in or as a matter of fact As they came in too (thanks devs). Most if not everyone i asked thought backing up the wallet.dat file is good enough, or the old --salvagewallet nor -zapwalletxes. They either aggressively scrambled the wallet making it more likely destroy even more keys, sure saved a few coins but most of the addresses in the keypool which has a size of 100 didn't have a corresponding private key anywhere in the wallet AFAIKT,
Sorry before i rant, i just need some info on if this wallet if linked to a specific Dogecoin version and just happens to say v0.6.4.0 in the debug log file.

I can't update directly to any other version without the wallet breaking up. Apparently i need the exact version that was last used, and turn it off extra safely so the log files which hold some parts of the keys go back to the Wallet.dat or something.

I tried all solutions, this might just work. from the "Bitcoin version 0.7.1 Readme file."
How to Upgrade
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).
If you were running on Linux with a version that might have been compiled with a different version of Berkeley DB (for example, if you were using an Ubuntu PPA version), then run the old version again with the -detachdb argument and shut it down; if you do not, then the new version will not be able to read the database files and will exit with an error.
Explanation of -detachdb (and the new “stop true” RPC command): The Berkeley DB database library stores data in both “.dat” and “log” files, so the database is always in a consistent state, even in case of power failure or other sudden shutdown. The format of the “.dat” files is portable between different versions of Berkeley DB, but the “log” files are not– even minor version differences may have incompatible “log” files. The -detachdb option moves any pending changes from the “log” files to the “blkindex.dat” file for maximum compatibility, but makes shutdown much slower. Note that the “wallet.dat” file is always detached, and versions prior to 0.6.0 detached all databases at shutdown.
or on shut down the coin client using the -detatchdb comas coins use both log and dat files with berkeley.

Thanks,

D_M


submitted by doge_messiah to dogecoin [link] [comments]

Dogecoin Stack Exchange Day 26 : Sabotage

On Saturday we had 20 questions with a score of ten or more.
Today we have 10 questions with a score of ten or more.
https://area51.stackexchange.com/proposals/110056
None of the dogecoin stack followers have downvoted any questions. Maybe an external moderator downvoted questions in the proposal? Or a group of people decided to wihdraw their votes? Why? Such scare! Very conspir.. plz up.!
Status 69 Followers 10 questions with a score of 10 or more
*Required to start comittment phase
20 more questions with a score of 10 or more
A lot of followers haven't voted, if you haven't voted, plz vote. If you haven't signed up, plz sign.
Current Question List
Question Votes
How can I setup a Dogecoin wallet? 14
What are the best ways to back up my wallet? 12
What is "cold storage"? Why is it better for long-term holding? 11
How can I buy Dogecoin? 11
I am trying to install dogecoin core on ubuntu how do i install the dependancies? 10
How can Dogecoin be used outside of Internet transactions? 10
How can I "bootstrap" to speed up the process of syncing up with the Dogecoin blockchain? 10
How can I sell my stuff for dogecoins? 10
Can an old, unencrypted core wallet backup be used to move dogecoins out of that same wallets currently encrypted core wallet? 10
How does merged mining work with litecoin? 10
How do I backup my wallet, and how do I restore form the backup? 9
How to setup a dogecoin public node? 9
How do I get dogecoins? 9
What is a public node? 9
How do i import a existing wallet.dat file from a previous dogecoin installation 9
Why are online wallets considered bad? 9
What would happen to the dogecoin hash rate if litecoin became unpopular? 9
How long does it take for the dogecoin wallet to sync with the dogecoin blockchain? 9
Where can I buy things with doge? 9
How do Dogecoin transaction fees work? 8
What is Dogecoin mining, and how do I begin? 7
Is there a way to tip videos on youtube with dogecoin? 4
Is there a limit on how many Dogecoins can ever be mined/exist? 3
What price would dogecoin need to be in order for the mining rewards to cover the cost of electricity? 3
What is "sweeping" from one wallet to another and why is it important? 1
How can Dogecoin avoid the long transaction wait times and high fees that Bitcoin is currently experiencing? 1
What is the best (most efficient) way to mine Doge? 1
How do I set up Dogecoinfold? 1
What are three reasons to use Dogecoin that the average, non-technical user would find compelling? 1
Is it possible to have two Dogecoin core wallets running on the same computer at the same time? 1
Is there a roadmap for Dogecoin's future? 0
Who are the devs? 1
What exactly is a shibe? 1
How can we help to boost DogeCoin as an accepted Currency? 1
Can I recover my dogecoins if I accidentally have deleted my wallet? 1
What is it about the Dogecoin community that makes it so wow? 1
What happened to the dogecoin foundation? 0
Who owns and runs the dogecoin.com website? 0
Does segregated witness implementation reduce traceability on the blockchain? 0
What is the purpose of cryptocurrency? 0
Can I mine dogecoin on my laptop? 0
What programming language is used for the dogecoin core? 0
Let's go
... to the moooon!
edit This back from Stack Exchange
User does not have to follow the proposal in order to vote on the sample questions. As the faq says, any user with 150 rep on Area 51 can downvote any example question.
So we're being sabotaged and we don't even know who is doing it... At least three people and none are followers. Such sad, very disappoint.
FWIW: https://meta.stackexchange.com/questions/297329/proposal-questions-downvoted-by-anonymous
submitted by mcsen2163 to dogecoin [link] [comments]

Just lost 4BCH backing up my wallet.dat file!

I ran up my first bitcoin (cash) full node a few days ago for a project. It had all gone well. Fully synced, my code was working and talking via RPC. So today I decided to send some BCH to the wallet. First sent 0.01 BCH to check everything was fine. It arrived so then sent 3.99 BCH.
At that point I thought oh! better get a backup of the wallet. So from my home folder (Ubuntu 16.04) I ran the command: bitcoin-cli backupwallet ./ to backup the wallet to the current folder I was in (I thought) it didn't seem to do anything no error and there wasn't a backup in my home folder so I ran bitcoin-cli backupwallet ~/ all good I could see the file.
Then I went to do some testing and realized bitcoind had stopped running. Tried to restart but it wouldn't, checked the logs and it said the wallet was corrupt. Ahhhh! No prob I have a backup. But no. Running the first command with ./ for the backup path had left my wallet.bat file empty i.e. Zero bytes. The backup was also zero bytes. 4BCH gone. :(
I replicated the entire process and it happened again. Not sure if this has happened to anyone else but it sucks. Such a simple bug. Can't believe it hasn't been picked up and fixed before. Just glad it was only 4 it could have been way worse. On my phone excuse grammar.
Edit: Does anyone know how I can pay a bounty to get this fixed? Rather than bitch about my loss i'd like to contribute to fixing it so it doesn't happen to anyone else.
submitted by GenXau4217 to btc [link] [comments]

HD address generation seems to work in bitcoin 0.13.0rc1 :-)

"The only people who should be running fully synchronizing nodes are miners and businesses and uber-geeks like theymos who enjoy fiddling with technology."
Gavin Andresen
Compiled bitcoin-0.13.0rc1 from source on Ubuntu.
Like in older versions, there was no menu visible in bitcoin-qt (it was in the binaries) but I finally solved it through:
sudo apt-get remove appmenu-qt5
I then added the following code:
https://github.com/bitcoin/bitcoin/pull/8206/files
so I could dump the extended private master key (xprv....)
and recompiled.
To dump the wallet (that here includes the master key):
In bitcoin-qt: click help, then choose console
walletpassphrase passphrasehere 60
dumpwallet filename
I then checked some of the addresses generated in bitcoin-qt here:
https://github.com/bip32JP/bip32.github.io
Substituting the BIP32 Extended Key and using:
Custom Path: m/0'/0'/0' (for the first address, etc.)
THEY AGREED!
(edit: and also the private keys)
Thanks, core developers and especially:
Jonas Schnelli
It's nice not having to worry anymore if the backup of your (encrypted) wallet.dat file has become outdated.
submitted by sumBTC to Bitcoin [link] [comments]

Introducing DOGE as base currency - Huge Bisq/Bitsquare update - Check out v0.5.1

This release comes with tons of changes and improvements.
Please download at: https://github.com/bitsquare/bitsquare/releases/tag/v0.5.1
Most relevant changes are:
Please see the full release notes below.
As that release has very profound changes it is NOT backward compatible to the earlier versions. It uses a new network which is separated from the current trade network. So your offers from the current application will not be visible for users who are using the new version.
If you want to migrate to the new version you need to close your offers and withdraw your funds to the new application. You can run both applications in parallel as they are using a different data directory. You cannot move over the wallet or application data because the wallet format has changed (BIP44) and we use a different data structure for the data base files. So you need to transfer the Bitcoin with a BTC transaction and set up your payment account(s) manually.
Please double check with cmd+e in the old application if no funds are left over (some bugs might have caused that the balance displayed in the UI is not correct).
Please use small amounts when starting trading in the new application as with so many changes there are some risks for bugs (though it is thoroughly tested).
Release notes:
submitted by heavyuser1337 to dogecoin [link] [comments]

Bitcoin using Linux boot USB and secondary for a cold storage wallet Ubuntu Coin Wallet How to backup your Litecoin Wallet Cryptocoin Wallet Backup/Restore Ubuntu(Linux) How to install Bitcoin Core wallet in any Linux distribution

So my node and wallet are working on Ubuntu 16.04.3. Bitcoinz installed from 1.0.11... When trying to get backup of wallet or to export keys: ./src/zcash-cli z_exportwallet &quot;filename=backup&qu... Follow these instructions to backup all the bitcoin data (wallet and block chains) to an encrypted disk image. Open Disk Utility; Click New Image and choose a big enough size, 128-bit or 256-bit (faster or more secure) encryption and single partition. Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever) Choose a safe and strong password; Move everything from ... Bitcoin Core runs as a full network node and maintains a local copy of the block chain. This data independence improves wallet privacy and security. Unlike some SPV wallets that leak addresses to peers, Bitcoin Core stores all transactions locally.With local access to the complete set of headers and transactions, Bitcoin Core can use full verification to tell when peers lie about payments. Users should ensure their Bitcoin wallet supports important features like backup to prevent loss of Bitcoins, user privacy and security, etc. before selecting a Bitcoin wallet. To make this process easier for you today we will have a look at the best 5 Bitcoin wallets which are available for the Ubuntu platform. 1. Armory. Armory is a open-source Bitcoin client with cold storage and Multi ... They must be synced with the Bitcoin network. Bitcoin Core is this type of wallet. Installing Bitcoin Core. Enough with the introduction, now I am going to show you how to install Bitcoin Core wallet on your Ubuntu 17.10 Desktop. Go to https://bitcoin.org and click on “Participate” -> “Running a full node”

[index] [27512] [21275] [1579] [46070] [22995] [20780] [21127] [45327] [40356] [45218]

Bitcoin using Linux boot USB and secondary for a cold storage wallet

Bitcoin 101 - Getting Your BTCs out of Your Paper Wallets & Cold Storage - Fun with Sloppy Wallets - Duration: 10:54. CRI 82,619 views Install, Backup And Restore A Bitcoin Wallet. Or, Almost Any CryptoCoin Wallet (Windows) ... How to install Bitcoin Core wallet in any Linux distribution - Duration: 4:28. teklordz 29,851 views. 4 ... You love bitcoin, but what would happen if you lose your phone? As many of us have to come to realize, managing backups in a non-custodial wallet can be over... Bitcoin How to import your old wallet into new one tutorial works 100% Recovered 1.7 BTC - Duration: 8:26. XOOMdotWS 9,189 views Here I explain how to Backup your Digibyte wallet for safe keeping and also how to restore your wallet if you ever need to update your wallet or reinstall it. Keep in mind the same process works ...

#