Yes. The name is completely cosmetic; there is no name in the Bitcoin blockchain that identifies it as being Bitcoin. The thing that identifies it as being Bitcoin are the consensus rules. This DOES NOT include the port, but it includes the mining algorithm, the genesis block, the difficulty adjustment algorithm, etc. If you do not change any of the consensus rules, then you are using Bitcoin.

What do you mean by "mining itself"? Mining is not involved in this.

Please post the transaction ids of the transactions in question.

Read the documentation provided in the source code. Specifically this file and this file.

Use a script which requests from Bitcoin Core each block and count the number of transactions in each block. Keep a running sum until you reach the block you want to checkpoint at.

The blockchain's sole purpose is to establish transaction ordering; if we can do that in the mempool (i.e. without the blockchain), then there's no need for the blockchain! This is effectively impossible to do though because Bitcoin is an asynchronous system; my node's mempool will be different from your node's mempool and, because of network latency, I will receive transactions in different orders than you do.

This topic has been moved to Trashcan.

Duplicate

The developers of Bitcoin Core (which Litecoin Core routinely rebases onto and thus instructions for recent versions of Core also apply to Litecoin) use the Linux command line and GDB to debug. Very few developers use an IDE or GUI for any sort of work. It is all mostly done with text editors and GDB from the command line.

The XEM address may correspond to the compressed public key, but your private key corresponds to the uncompressed public key. The compression of a public key is simply set by an additional byte at the end of the public key. To try the compressed public key, add 01 to the end of the hex string that you have for the private key.

No, bitcoin-cli does not access anything. It interacts with bitcoind or bitcoin-qt so it "accesses" whatever the running instance of one of this is using.

It is possible that bitcoind is accessing a different wallet from bitcoin-qt. The first time you ran bitcoin-qt, it should have asked you to choose a data directory. If you have changed it from the default, then your wallet file and all of the blockchain data will not be in the default datadir. However if you start bitcoind without the -datadir option, then it will use the default datadir which means that it will be using a different wallet and downloading the blockchain again. To check your datadir, open bitcoin-qt and go to Help > Debug Console > Information. It will say what the datadir is. If it is not C:\Users\<username>\AppData\Roaming\Bitcoin, then you are using a custom datadir and when you use bitcoind it will not be using that datadir.

If you are using a custom datadir, bitcoin-cli will need to have the -datadiir option set so that it also uses the same datadir to get the information it needs in order to access Bitcoin Core's RPC server.

Yes, you must have Bitcoin Core (bitcoind or bitcoin-qt) running in order for bitcoin-cli to work. It is a tool that interacts with Bitcoin Core through the command line.

Where are checking to see if there are addresses?

You could use the importmulti command instead. That allows you to import multiple things (private keys, addresses, etc.) in one command.

This topic has been moved to Trashcan.

plagiarism

bitcoind is not the program to interact with Bitcoin Core from the command line. You want to use bitcoin-cli instead.

A CPFP transaction is not a conflict and does not result in any additional transactions being listed in your wallet unless you are the one performing the CPFP. It does not affect you.

The safest thing for you to do would be to wait for one confirmation. After one confirmation, it does not matter whether a transaction was RBF'd or not; the conflicting transaction will be unconfirmed and you aren't counting those.

One confirmation means that your transaction has been included in a block. All subsequent confirmations happen with more blocks are found on top of the block your transaction was included in. Once you have one confirmation, more confirmations will come as blocks are mined; there is nothing that you need to do.

You only need to pay a transaction fee (or fee for that service) once in order to get the first confirmation.

This topic has been moved to Trashcan.

Begging

THere is no "main channel". Miners are not involved in lightning except for confirming the on-chain opening and closing transactions. The transactions are faster through lightning because they can be done nearly instantaneously (well as fast as you can send data over a wire) with basically guaranteed security.

A transaction is confirmed when it has at least one confirmation. If you don't see it in your wallet or it says "unconfirmed", that means that your wallet is either working improperly or not synced with the blockchain.

It won't be centralized in the sense of traditional banking centralization. Even if LN is dominated by most people connecting to just a few large hubs, those hubs don't have the level of control that a bank does. You as a user will still be in control of your money, and you can close a payment channel at any time you want. And you don't even have to have a channel with those hubs if you don't want to; LN lets you create payment channels with anyone else.

This topic has been moved to Trashcan.

Duplicate of https://bitcointalk.org/index.php?topic=2621437.msg26677881#msg26677881