Bitcoin Forum
January 19, 2019, 07:21:46 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 [15] 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 ... 550 »
281  Bitcoin / Development & Technical Discussion / Re: The Beginning of Bitcoin on: May 22, 2018, 09:48:30 PM
1. Was the genesis block mined or just set somehow?
Both. The genesis block needed to be mined as it must have a valid proof of work. However it is not a block that the network mined but rather satoshi mined it and hard coded its value into the Bitcoin source code.

2. How did it all actually start? Did Satoshi share the first bitcoin software to a group of interested individuals?
Satoshi posted the Bitcoin whitepaper to the Cryptography mailing list. He also registered the domain bitcoin.org (bitcoin.com was taken at the time) and hosted the whitepaper there. A few months later, Satoshi announced the first release of Bitcoin on the same cryptography mailing list. The source code and the binaries were hosted on bitcoin.org.

3. Did he announce a particular point in time to start mining? Or perhaps he had to mine by himself for a period of time before other people jumped in?
No. There was no start time to mining. Mining could be done by anyone who had the software, including Satoshi. The first block after the genesis block was mined later the same day, possibly by Satoshi. Satoshi certainly did mine by himself for some time, but other people were also mining. It is difficult to know which blocks were mined by Satoshi and which blocks were mined by someone else.

4. How long did they have to mine empty blocks?
The first transaction was block 170

5. With only a handful of nodes at the beginning, did they have to set a particular type of network communication between them?
The network protocol is largely the same as it is now. The same message types are used and the format is very similar. To find nodes to connect to, the original client would connect to an IRC server and post its IP address there. New nodes would connect to the same IRC server and retrieve IP addresses to connect to. There was no method to tell the software to initiate a connection with a specific IP address.

6. Did it ever happen that (during this initial phase) the network was off line for some time?
Yes. There were periods of time where blocks were not being mined (a few hours usually).
282  Bitcoin / Development & Technical Discussion / Re: Where are functions: Add transaction, Sign transaction, Check transaction ... on: May 22, 2018, 07:50:40 PM
SignSignature is the one that sign a transaction with private key no ?
No, ProduceSignature is. SignSignature is not actually used outside of tests.
283  Bitcoin / Development & Technical Discussion / Re: Where are functions: Add transaction, Sign transaction, Check transaction ... on: May 22, 2018, 07:36:11 PM
By Add Transaction i mean: Create a new transaction.
Follow the code for createrawtransaction. If you are interested in how the wallet works, then follow the code for sendtoaddress

Transaction is checked first and added to Mempool waiting for miners no ?
Yes. However the checking and adding to mempool are done as part of the same function. The AddToMemoryPool function will call the various checking functions for checking a transaction and then add it to the mempool at the end. It also performs its own checks for the additional conditions of adding a transaction to the mempool (e.g. conflicts, replacement, transaction fee, etc.).
284  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core private keys on: May 22, 2018, 07:32:28 PM
Since the "dumpwallet" command is allowed over RPC and will print out all your private keys (which equals complete access to your coins regardless of the wallet password), ...

Using RPC's does NOT allow to directly dump all of the private keys if the wallet is encrypted.
Authenticating RPC's does not equal the decryption of the wallet.

If you want to dump the wallet via RPC, you need to unlock the wallet with the walletpassphrase first.
HCP has mentioned this directly above your post.
Not only that, but dumpwallet does not return the private keys over RPC. It writes them to a file which is local to the machine so attackers cannot use dumpwallet and extract all of your private keys. They could use dumpprivkey but that can only get them private keys for addresses that they know belong to that wallet.
285  Bitcoin / Development & Technical Discussion / Re: Where are functions: Add transaction, Sign transaction, Check transaction ... on: May 22, 2018, 07:22:17 PM
- Add transaction
Add transaction to what?

- Sign the transaction by private key
The code for the RPC command signrawtransactionwithwallet can be found here. Follow the code and it will take you to where transactions are actually signed. Starting with this command shows you the whole process.

- Check the transaction by nodes
- Add to mempool
Checking a transaction is done when it is being added to the mempool (the same functions are used for checking transactions in blocks). Just follow the code for AcceptToMemoryPool
286  Bitcoin / Bitcoin Technical Support / Re: Cross Compile Windows Binaries For Bitcoin v0.10.2 on: May 21, 2018, 09:16:52 PM
The cross compilation process for Bitcoin Core 0.10.x should be largely the same as for recent versions of Bitcoin Core. Try following those instructions but with the 0.10.2 codebase.

You can also use gitian which is used for building the release binaries. Instructions for that are available here: http://github.com/bitcoin/bitcoin/blob/v0.10.2/doc/gitian-building.md and here http://github.com/bitcoin/bitcoin/blob/v0.10.2/doc/release-process.md
287  Bitcoin / Armory / Re: Payment not received in Armory on: May 21, 2018, 09:14:36 PM
Is Bitcoin Core fully synced? If not, wait for it to sync.

Now it looks like my receive address is different
You do not have just one receiving address. Your wallet contains multiple addresses. Armory will give you a new address every time you want to receive Bitcoin. The old addresses are still in your wallet and your Bitcoin will "arrive" once you are fully synced (assuming that the transaction has confirmed).
288  Bitcoin / Electrum / Re: bitcoin is hackable on electrum-2.9.3-portable news may 2018 on: May 21, 2018, 03:41:01 PM
Electrum versions between 2.6 and 3.0.4 are known to be vulnerable and you should upgrade immediately.

Unfortunately there is nothing that can be done to recover your Bitcoin.
289  Bitcoin / Development & Technical Discussion / Re: Atomic Swap - is it a best way to exchange cryptocurrencies? on: May 21, 2018, 03:38:24 PM
Not all coins can have HTLCs (they don't all have OP_CLTV) so this method does not work for some coins.
290  Bitcoin / Development & Technical Discussion / Re: Question about LN routing at 1 Million TPS on: May 21, 2018, 02:49:14 AM
Well if we had an open channel and I transfer all my available funds in the channel to you, I wouldn't be able to transfer more funds to you so that path would be blocked, wouldn't it?

Consequently, when a sender would use our channel as part of his route, it could have been blocked before the sender knows about it.

Is there a solution to that or do I have an error on my part here?
This is certainly possible, but I doubt it would be likely or really that big of an issue.

In the event that this happens, the node which has the problem will send an error back to the origin node and then the HTLCs will fail and be removed from the commitment transactions. Then the node will choose a different route and try the payment again. It's trivial to solve and not really a problem, especially with a large, well connected network.
291  Bitcoin / Development & Technical Discussion / Re: Question about LN routing at 1 Million TPS on: May 20, 2018, 08:39:51 PM
Why would it? Having 1 million tps does not necessarily effect the open channels. Furthermore, calculating a path does not take all that long.
292  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: May 17, 2018, 11:23:46 PM
This is a great news, but am a kind of person that ask a lot of questions. I want to know the principle of working of Bitcoin Core version 0.16.0. Does it entails POW
Of course, Bitcoin uses PoW. Bitcoin Core is the reference implementation for Bitcoin, it is not an altcoin.
293  Bitcoin / Development & Technical Discussion / Re: A thought experiment: PROVE you own a bitcoin on: May 16, 2018, 03:33:51 AM
C does not require trust, does it?

A person verifies a public address, then he sees that one bitcoin has moved to a new address, that was previously specified by you.

There is no way he could know whether you were the sole owner of the old address.

Now, how could a proof be devised that you owned the new address?
Just send back to the same address. No need for a new address and it proves that you have the private key for that address and can move coins associated with it.
294  Bitcoin / Development & Technical Discussion / Re: A thought experiment: PROVE you own a bitcoin on: May 16, 2018, 12:21:37 AM
If you want proof of "I can spend coins associated with this address", you can sign a message with the address (or specifically with the private key whose public key hashes to the hash encoded by an address).
295  Bitcoin / Development & Technical Discussion / Re: 64: too-long-mempool-chain on: May 15, 2018, 05:09:18 AM
No need to do that. This has nothing to do with the databases.
Does this  means that there is no need for adding reindex options ?
  2. Restart bitcoind (← without adding -reindex options)
Correct. Just restart without -reindex
296  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: May 15, 2018, 04:21:12 AM
Is this version available for mobile?
No, Bitcoin Core is not a mobile application.
297  Bitcoin / Development & Technical Discussion / Re: 64: too-long-mempool-chain on: May 15, 2018, 04:20:08 AM
Can I override the default limit of 25 unconfirmed transactions by adding to cofiguration file as below.

  1.  Additionally write to configuration file.
  bitcoin.conf-----------------------
  limitancestorcount=1000 ← e.g. 1000
  limitdescedantcount=1000 ← e.g. 1000
  ----------------------------------
Sure, you can do that, but that does not mean that your transactions will actually be relayed across the network. Just because you have this in your config does not mean that your peers will so they likely won't accept any transactions once you reach the default limit. Your local config only applies to your node. Changing this just means the transactions will sit in your node's mempool (and not be relayed across the network). They won't even be rebroadcast by your node because nodes don't do that.

Instead of trying to get long unconfirmed transaction chains to be relayed, you should be rethinking why you are generating long unconfirmed transaction chains and thinking of ways that you can avoid making long unconfirmed transaction chains instead.

 2. Restart bitcoind with -reindex options.
No need to do that. This has nothing to do with the databases.
298  Bitcoin / Bitcoin Technical Support / Re: Node Privacy on: May 15, 2018, 04:17:19 AM
Privacy in what regard? Do you want people to not know your node's IP address? Or do you want people to not know whether you are behind your transactions? Or something else?
299  Bitcoin / Bitcoin Technical Support / Re: Berkeley db address format on: May 14, 2018, 06:08:04 PM
A follow up question...I understand that if an address has a transaction, then the public key can then be known. Thatís why bitcoin generally uses new addresses every time. How can I find the public key in the event that the address has a transaction?  The address Iím looking for does not, but Iím just asking to learn in this case.
You would have to find the transaction, parse it as a standard Bitcoin transaction, and look at the inputs to see if any of the public keys hash to the hash encoded by your address. Bitcoin Core does not store transactions by association to the address, and addresses nor their data are contained in the inputs of a transaction.

Note that transactions can also be associated by the outputs. In that case, the public key is not known, however the hash provided in the output will be the same hash encoded by the address.
300  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: May 14, 2018, 05:24:52 AM
What happen if send BTC from legacy address to SegWit address?
The typical thing happens, your Bitcoin are transferred from a legacy address to a Segwit address. The address types really don't matter; the network doesn't care and such transactions are possible due to the soft forking nature of Segwit. You can even do it the other way around, segwit address to legacy address. It doesn't matter.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 [15] 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 ... 550 »
Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!