Running A Full Node - Bitcoin

Funds never received. What did I do wrong?

Sorry if this is a boring or redundant topic, but I just can't find an answer. This is my first attempt at a Monero transaction.
I downloaded and installed the Monero Windows GUI app. I handled the antivirus issues, and the network is showing as connected, with both Daemon and Wallet synchronized.
I used Changelly to exchange Bitcoin to XMR from a Coinbase account.
The transaction seemed to work smoothly, and Changelly is telling me the funds have been moved successfully.
My Monero wallet does not show any received funds.
When I compare the wallet's primary address and the address listed in the confirmed transaction, the appear identical.
What could have possibly gone wrong? How do I debug this?
submitted by raftguide to monerosupport [link] [comments]

#Reddcoin ($RDD) Core Wallet Release 3.0.1 - PosV v2 SuperMajority Consensus Upgrade at 45.6% - Required Upgrade

Reddcoin (RDD) Core Wallet v3.0.1 - January 09, 2020
Version 3.0.1 is the official release version of Reddcoin Core. It is available for download at Reddcoin Core's Github repository here:
This release features PoSV v2.supermajority activation and new staking ruleset (and minor misc fixes). v3.0.1 is still not yet MacOS Catalina compatible. We are still working and should have that fix issued very soon. Sincere apologies to our Mac-using ReddHeads.
It is particularly important that all users upgrade, as once PoSV v2 is enforced, version 4 blocks will be rejected from the network entirely.
Therefore v3.0.1 is a "strongly recommended" update for all users. Note: If you have already installed v3.0.0, this upgrade is not required. If you have not yet upgraded from v2.0.x or earlier, this is a REQUIRED upgrade. Please install the newest version v3.0.1 to avoid losing functionality during supermajority activation of PoSV v2.
Reddcoin Core version 3.0.1 is now available from: Release Notes are available here and replicated below in this announcement:
This is a new major version release of Reddcoin.
Previously, the original and subsequent versions of Reddcoin were taken from a fork of the Litecoin code base.
With the release of Reddcoin V2.0.0, the code was based directly from a fork of Bitcoin. This allows for better source control and feature implementation from upstream changes into the future
With the release of Reddcoin V3.0.0, the PoSV stake reward has been improved to allow for a target 5% network growth, in process re-incentivizing individual network stakers and providing for integrated dev support.
Upgrading to this release is strongly recommended and required for continued operation. Once a supermajority of 90% is reached, old wallets will no longer accept the new v5 blocks.
Please report bugs using the issue tracker at github:
How to Upgrade
If you are running an older version of Reddcoin, shut it down. Wait until it has completely shut down (which may take a few minutes for older versions). Run the installer (on Windows) or just copy over /Applications/Reddcoin-Qt (on Mac) or reddcoind/reddcoin-qt (on Linux).
Start wallet. All done!
Reddcoin v3.0.0 introduced an updated PoSV method to better distribute staking rewards and target a overall 5% network growth. Staking and relay policy enhancements 
To implement PoSV v2, Reddcoin Core's block templates are now for version 5 blocks only. When PoSV v2 consensus (Supermajority 9000/10000) is reached, only v5 blocks will be accepted by the network.This equates to approximately 90% of blocks being generated over 1 week period. Status at any time may be viewed in node debug.log
Blockchain Download:
Blockchain data for both testnet and mainnet along with instructions can be downloaded from github.
3.0.1 changelog
*83e212838 - John Nash, 2020-01-09 : really delete these files *3a1458ecd - Oliver Webb, 2020-01-08 : Added missing dependency libminiupnpc-dev for Jessie *d21915431 - Tiago Peralta, 2019-06-21 : Add vout to listtransactions/gettransaction *8d58ea7cf - Oliver Webb, 2020-01-08 : Script for downloading pre compiled binaries for Raspbian Jessie, Stretch or Buster *d4eced1bc - Oliver Webb, 2020-01-08 : Delete *c5e9f91cf - Oliver Webb, 2020-01-08 : Delete *5d5771b00 - Oliver Webb, 2020-01-08 : Delete *75c6ae91b - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *54c501787 - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *acb30a2b6 - Oliver Webb, 2020-01-05 : script files for Raspbian Jessie (also Stakebox) *cfddbe594 - John Nash, 2020-01-05 : Update copyright year and version *e46e5e7de - John Nash, 2020-01-05 : download script for pre compiled wallet *37386790a - John Nash, 2020-01-05 : change libssl deb packages links to github *9dbc772e6 - Oliver Webb, 2020-01-03 : download script for pre compiled wallet *857d697fd - Oliver Webb, 2020-01-03 : change libssl deb packages links to github *2cb74b9a8 - John Nash, 2019-12-31 : update copyright year *c641a1ab3 - Oliver Webb, 2019-12-30 : Raspberry Pi build script files for v3 wallet *a3f21a4a4 - John Nash, 2019-12-30 : add install script for building db4 update instructions for unix, osx, arm building using the db4 install script *5f6299b2a - John Nash, 2019-12-28 : docs: Update build notes for arm processors *465716c01 - John Nash, 2019-12-28 : test for arm devices *3fec3a535 - John Nash, 2018-02-02 : build: update source paths *5f6031ab4 - John Nash, 2019-12-28 : Scrypt n=1024 Pow hash based upon Colin Percival's Tarnsnap (2009) Modified by Artforz, coblee, pooler, wtogami, Nikolay Belikov, reddink *2fd4d91a0 - John Nash, 2019-12-24 : update copyright year *326828b36 - John Nash, 2019-12-24 : set release state true *8ebede0a6 - John Nash, 2019-12-24 : release notes *36df6fdfb - John Nash, 2019-12-23 : add check explictly for v5 blocks or greater *874dc1f0c - John Nash, 2019-12-17 : remove hardcoded global variable rearrange debug log output *763b25db8 - John Nash, 2019-12-17 : move copyright to new line *536baf635 - John Nash, 2019-12-17 : update version and set release state to false *cde9009f3 - John Nash, 2019-12-17 : update copyright year *ae41b7ed3 - John Nash, 2019-12-17 : set isSuperMajority to 90% for mainnet *e43e1c8ed - John Nash, 2019-12-10 : additional logging to verify isSuperMajority in the debug.log output *e31783cac - John Nash, 2019-12-05 : add/update public key for mainnet *405c6f002 - John Nash, 2019-12-05 : add log output for current inflation rate *9cc43c3f7 - John Nash, 2019-12-02 : determine calculated stake based on posv version *7baa3bf75 - John Nash, 2019-11-25 : check the posv transaction for correct pubkey *9ffa7ca38 - John Nash, 2019-11-21 : check for posv v1 or posv v2 blocks when calculating stake reward *39f7aad68 - John Nash, 2019-11-14 : add logging *0e283e6c3 - John Nash, 2019-11-13 : correct maths *74cbdeffd - John Nash, 2019-11-11 : use new posv v2 functions addidtional logging *35d7413b5 - John Nash, 2019-11-11 : add new proofofstakereward *3d917216c - John Nash, 2019-11-11 : get inflation adjustment *f63d17443 - John Nash, 2019-11-08 : add the developer output split fund output *ca263c9c9 - John Nash, 2019-11-05 : add dev key to chainparams *df6996ab0 - John Nash, 2019-11-05 : add block version checking *14b663479 - John Nash, 2019-11-05 : increase block version
Thanks to everyone who contributed to coding, testing and feedback for this release, notably:
@cryptognasher @techadept @chris @cryptobuze @harmonyq @mindredder @paxtech @Tiago Peralta 
Stake on!!
-Reddcoin (RDD) Core Development Team
submitted by TechAdept to reddCoin [link] [comments]

AMA/Tutorial: Run a full node on AWS free tier with local LAN storage

AMA/Tutorial: Run a full node on AWS free tier with local LAN storage
This is a tutorial/AMA on how you can be running a full node, in the AWS cloud, for very low cost or even free.
I used to run a node on my local network but there is a problem with this; your public IP is broadcast, and then it gets associated with Bitcoin. Node owners are likely to own Bitcoin, and this raises your personal threat profile, validated against my IDS/IPS logs.
Run a VPN? Many VPNs are automatically blocked, or sketchy. Tor is also blocked on a large portion of the internet. Neither provide you with a real static IP, and that helps out the network.
There is a easy solution to this; run a node on the AWS free tier, and use an elastic IP so you have a static address. Bandwidth is free in, and low cost out, and you can control how much of that you use easily, and control your spent. The problem is that Amazon charges a LOT for online storage and even with a 1MB blocksize, the blockchain is very large and growing steadily! We mitigate this by using a VPN back to your network, where you can store the blockchain on a SMB share.
It is not complicated to do, but there are very many moving pieces to keep track of and configure. In order to fully trust your node, the best way is to build it from scratch. This is my goal in walking you through the process.
There are lots of ways to accomplish this same task; I only want to present one that works, and you can go from there. Once you have access to the blockchain in the cloud for reasonable prices, you can also look at things like the Lightning Network.
This article makes four major assumptions:

  1. That you have a OpenVPN server on your network and know how to configure it. I use pfSense and OpenVPN; others will work just as well, but you'll need to do a little work to figure out the particulars. If you don't know how, do not fret! There are loads of good tutorials for just about every platform. Or ask below. I also limited the user with access to the share at the firewall specifically to the IP hosting the share to lower the threat envelope.
  2. That you have the blockchain downloaded locally and reasonably up to date. If you don't, head on over to and download it for OSX or Windows or Linux, whatever you use for your workstation. Follow the directions to set up the software and download/synchronize it to the network. This will take awhile! Once you've synchronized, copy the data directory to your SMB share you want the AWS instance to access. You could also synchronize everything directly on AWS too, but it will likely take longer and may cost a bit for the bandwidth.
  3. That you're on windows. OSX and Linux will have slightly different processes to connect to the instance via the terminal and SSH. If you need help, ask, and I am sure we can get you fixed up.
  4. That you've read the excellent full node tutorial here:

With that, on with the show!
First: Head on over to and make yourself an account.
Once you've set up you'll need to start the process of creating a virtual machine on AWS. Look for this graphic and click on it:

Start by launching a new machine

Follow the rabbit hole, and you'll be looking to create a plain jane Amazon AMI Linux instance. It looks like this:

Pick the basic AMI instance
Keep in mind you want to pick the x86 version, which is the default.

Continue clicking, you'll want to select the t2.micro instance that is eligible for the free tier for new accounts.

Pick the free tier. You can also upgrade to the smaller tier for more ram, but the micro works for now.
Now, you're going to need a way to connect to your soon-to-be-created node in the cloud. Amazon uses SSH keys to do this, so the next step means you're going to make some. You need to save this file, as if you lose it, you won't be able to access your node anymore. Much like your wallet private keys!

Beware losing your keys!

If you've made it this far, you're almost launched!
Now we need to convert the key to a format that we can use to connect to the instance from Windows. I recommend using Putty! if you don't have it already; if you're on OSX or Linux, you likely have what you need already.
Follow the guide here to get connected:

Next you'll need to set up a opening in the firewall if you want incoming connections. This is done by adding to the security group in the "Network and Security" section; edit it to look like this:

Change the inbound security rules for the instance to accept incoming connections on 8333.

The hard part is over!
Optional: Configuring a static IP. Amazon calls their implementation "elastic" IPs, but it's really a static IP that you can move around between instances very easily. It will ensure your public address on AWS does not change; it isn't required, but it is better if you intend on allowing outgoing connections.
Go back to the main dashboard display.
In "Network and Security", click on "Elastic IPs".
Select Allocate New Address (blue button on top) and then select it in the table. In actions, you will see "Associate Address". Select this then assign the address to the instance you have previously configured. Done!

Next up: Log into your machine, and immediately update everything. Use the IP provided by Amazon, or the Elastic IP if you assigned one to the instance in the last step.
type: "sudo yum update"

Now, let's get the VPN configured.
First step is to install OpenVPN. We need to install the extended package library to do this.
type: "sudo amazon-linux-extras install epel"
type: "sudo yum-config-manager --enable epel"
Now you can install OpenVPN.
type: "sudo yum install openvpn"
You will need your credential file from OpenVPN; it's a file you generate that will have a .ovpn extension. But you're going to need to upload it to the instance. You can do this through the scp command on OSX or Linux, but if you're on Windows, you'll need another utility. Get WinSCP here:
But we'll have to tell it where your key file is so you can login. Select "New Session", then use the same IP and username as you did to connect before. We'll need to tell it about the key file though! Select the "Advanced" tab then under the SSH section, click on "Authentication" and then select your private key file you generated in the tutorial above.
Connect and upload the .ovpn file that you generated when you added a user for the VPN. This step depends on your OpenVPN configuration - ask below if you have problems.
Next, let's verify we can connect to the VPN!
type: "openvpn --config my-configuration-file-made-by-openvpn.ovpn &"
You will be prompted for a password if you configured one.
Verify operation by pinging your LAN router, e.g.
type: "ping" or the address of the SMB server where you shared the information.

Allllrighty! Next up is getting connected to your blockchain. Create a directory where the data directory will be mounted.
type: "mkdir blockchain"
We need to install samba and some utilities to get things mounted.
type: "sudo yum install samba"
type: "sudo yum install cifs-utils"

Now let's mount the folder:
type: "sudo mount -t cifs // ./blockchain -o user=bitcoin,vers=2.0,uid=ec2-user,gid=ec2 user,file_mode=0777,dir_mode=0777"
Where " //" is the address of the SMB server and share where you put the data directory from your initial sync. If you didn't, and just want to sync everything from AWS, then make sure it's a folder where your user has access. In this case, I'm assuming you've made a SMB user with the name "Bitcoin". The command will prompt you for the password to access the share. The other bits ensure you can have read and write access to the share once it's mounted in AWS.

Now we're ready for some Bitcoin! Props to the tutorial here:
But I'll summarize for you:
Download and then re-upload with WinSCP, or download directly to your instance with wget, the most current Bitcoin core. In this case, it's bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz downloaded from
Let's verify it hasn't been tampered with once you have it uploaded to the terminal:
type: "sha256sum bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz"
Then compare that with the hash value that's listed in the SHA256SUMS.asc file on In this case, "36ce9ffb375f6ee280df5a86e61038e3c475ab9dee34f6f89ea82b65a264183b" all matches up, so we know nobody has done anything evil or nefarious to the file.
Unzip the file:
type: "tar zxvf bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz"
There is a warning about a symbolic link; everything seems to work OK regardless, but if anyone knows what or how to fix, please comment.
We'll need to get some missing libraries before we can run it; these aren't in the basic AMI instance.
type: "sudo yum install glibc.i686"
type: "yum install"

FINALLY! We are ready to launch the program. Go to the "bin" directory inside where you unzipped the Bitcoin Core tarball. (e.g. /home/ec2-useblockchain/bitcoin-0.18.0/bin)
./bitcoind -datadir=/home/ec2-useblockchain/data
You will see the program either start to sync and download, or start to read the existing blockchain file that you put in the share from before.


There are a couple extra steps to have it automatically start on reboot, but let's see if anyone gets this far first. I use the "screen" program to do this, but there's also a daemon mode, and some other functionality that is discussed in the hackernoon tutorial.
The primary cost will be outgoing bandwidth. AWS charges $0.10/GB beyond 15GB; You can limit the outgoing bandwidth easily according to your budget:

Hope this encourages people to try running a free, or very low cost, cloud node, with a substantially reduced threat profile.
submitted by xtal_00 to Bitcoin [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
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
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
252 bitcoinj
253 user01
254 cc
255 [email protected]
256 12345
257 azureadmin
258 duanhw
260 zhangfei
261 easton
262 geoeast
263 lwx
264 ldd
265 aws
266 gv1
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
304 carl
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