Topic: Cant connect to each other nodes (own Altcoin, bitcoin forked) (Read 85 times)

I didn't explain it well enough. 0.18.1 means that I can't build bitcoin-qt on windows using mingw.

From where couldn't you download 18.1's qt version? Bitcoincore.org? It didn't exist in the server? And what does it have to do with the building? The executable from the Bitcoin Core page wouldn't work for your altcoin. You had to just build it using the source code.

Is there anything that I've not understood properly? Judging from your text, that's the problem I've understood you're facing.

Depends solely on what you're trying to achieve. If you just want to test the transaction system, let it be 18.1.

Hi.

What's an original coin? Just say it altcoin. It isn't bad sounded.

In both Windows and Ubuntu there should be an application data directory where all the applications keep things such as configuration files etc. Same applies for Bitcoin Core. You should create the .conf file there and if you've ensured that it's the correct directory, then any included command in that file should be the same if you executed as a parameter.

If you've included the addnode commands, what's the debug.log saying? Is that all it says?

---

---

Note that many things may have gone wrong, so it may take time to even understand why your computers cannot connect. Could you first explain me why you used 0.20.1?

  I am cloning bitcoin to create an original coin.
I have prepared a total of two Ubuntu systems, one local and one on AWS.
I want to set up nodes with these and connect them to each other, but it doesn't work.


#version:
bitcoin 0.20.1
VM1: ubuntu20.04
VM2: AWS/Ubuntu20.04


#Debug.log
2021-10-18T11:52:19Z net thread start
2021-10-18T11:52:30Z Loading addresses from DNS seed 52.40.22.215
2021-10-18T11:52:30Z Loading addresses from DNS seed 49.230.202.66
2021-10-18T11:52:30Z 0 addresses found from DNS seeds
2021-10-18T11:52:30Z dnsseed thread exit


#settings of my bitcoin.conf. I wrote the same settings for both VMs.
rpcuser=user
rpcpassword=password
server=1
listen=1
addnode=52.40.22.215
addnode=49.230.202.66
addnode=udeep.net


I also tried this command on both VMs with each other.
bitcoin-cli addnode 52.40.22.21 onetry
. /bitcoin-cli addnode 49.230.202.6 onetry


1, Please lend me your wisdom on how to connect them.

2, bitcoin.conf settings and the addnode command, and bitcoind,
Is it all for the same purpose?

I mean for example, if I write addnode in the conf file, I don't need to type the same command from cli? If I write addnode in the conf file, do I not need to type the same command from the cli?



3. I have successfully built a Windows wallet, but I cannot send or accept coin.

How do I set it up so that it automatically connects to the node when I start the Win Wallet?
I would like to set it up to automatically connect to a node when I start the Win Wallet so that we can send coin to each other.
How can I do this?