Bitcoin Forum
January 16, 2019, 07:28:45 PM *
News: The copper membership price will increase by about 300% around Friday.
 
  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 66 ... 549 »
301  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core app and the unlocking of the iconů on: May 06, 2018, 06:13:35 AM
While it's obvious that if the scammer saw this thread I'm trying to lay as low as possible in hopes to not cause him suspicion is there a way I could PM the video to you?
Sure
302  Bitcoin / Development & Technical Discussion / Re: Stale files kept under "chainstate"? on: May 06, 2018, 06:06:32 AM
Yes, that's one possibility I thought of. Maybe old TXOs that haven't been used in years.
But considering all the other files change at most every few days, and these haven't changed in months, it does seem odd.

cellard says all his chainstate files are with recent dates. Is it the same for you? And any 0-prefix files?

All of my chainstate files are  fairly recent. No 0 prefix files.

Since the database format has changed in recent versions, it's possible that those are old database files from previous versions.

Are you able to check when those files were last accessed?
303  Bitcoin / Bitcoin Technical Support / Re: How can I get a copy of blk0001 on: May 05, 2018, 04:30:29 PM
This is a quote from Matt. "This needs to go into 0.3.24, so that users who downgrade don't mess up their wallet by adding unencrypted keys to an encrypted wallet, making all versions unable to use the wallet." It is my understanding that when using Cwallet that Matt changed the private key around 0.3.2.1- 0.3.2.3 and it would crash the wallet in 0.3.2.4. it was part of garzik code for encrypted keys that Matt worked on
Email me if you know the format of encrypted keys.
No, you understand completely incorrectly.

As I said earlier, private key encryption was released in 0.4 and no earlier. Wallets prior to that were not encrypted. The problem here is that introducing encrypted keys changes the wallet format by adding things to the wallet that previous versions do not know. Thus the wallet will crash and become corrupted if you encrypted it with 0.4 and then downgraded to 0.3.x. The change for 0.3.24 was so that if someone downgraded from 0.4 to 0.3.24, the act of downgrading would not corrupt their wallet as it would with 0.3.23 and earlier. This has nothing to do with CWallet nor with 0.3.21-0.3.23. Encrypted private keys were not part of any 0.3.x version.
304  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core app and the unlocking of the iconů on: May 05, 2018, 04:07:25 PM
Based on the low resolution (blurry) images, [1] is Bitcoin Core wallet?, [2] I have no idea, can't tell by the looks and I'm positive that [3] is Multibit, which are all made by different developers.
These are all Bitcoin Core wallets. The window that is screenshot is actually the Debug console which is a separate window that Bitcoin Core create when you go to Help > Debug Window > Console.



The icon is indeed supposed to change from closed to open when you unlock. This looks like a bug. Can you provide exact replication steps?
305  Bitcoin / Development & Technical Discussion / Re: Why the wallet.dat file isn't fully encrypted? on: May 05, 2018, 04:01:29 PM
Yup but that's what why I proposed a double lock system:
A double lock system does not get around the fact that it is still a UI/UX issue.

Furthermore, you are asking users to remember yet another password. It seems that it is far more common for people to lose their coins by forgetting their password rather than having someone steal them. Even cases of stolen encrypted wallets seem to be quite low. By adding another password, you introduce yet another way for people to lose their coins. Forget one of two passwords and you are screwed.
306  Bitcoin / Development & Technical Discussion / Re: Stale files kept under "chainstate"? on: May 05, 2018, 01:23:55 AM
Just because the files have not been modified does not necessarily mean they are unused. Those database files are likely still accessed as they contain data that Bitcoin Core needs. However that does not mean that those file need to be modified. The data stored there does not always need to change.
307  Bitcoin / Development & Technical Discussion / Re: Why the wallet.dat file isn't fully encrypted? on: May 05, 2018, 01:21:14 AM
If the wallet.dat file were fully encrypted, you would not be able to see your funds, get addresses, etc. without entering the password. This means that for the wallet to be useful, you have to prompt the user to unlock the wallet at start. Unfortunately this is not really easily done with bitcoind which does not have a GUI. Furthermore, it is not necessary for the entire wallet.dat to be encrypted because all that really matters are the private keys, and not anything else in the wallet file.
308  Bitcoin / Bitcoin Technical Support / Re: Using Createrawtransaction Got no-witness-yet Error on: May 03, 2018, 08:49:13 PM
How can I spend money using createrawtransaction? I am not familiar with Segwit...
createrawtransaction is unrelated to this or to segwit. The problem is that the wallet assumes segwit is enabled by default, but segwit is not enabled according to your network rules. So you either have to enable segwit in the network rules, or change the wallet to assume segwit is disabled. How you do that you will need to figure out yourself.
309  Bitcoin / Bitcoin Technical Support / Re: Using Createrawtransaction Got no-witness-yet Error on: May 03, 2018, 04:22:52 PM
Code:
      "txid": "551ba4bde3460bca6a6cae7da57ffd8b3f1baf18ad7a2e6d50f8d4f5b0a94e14",
      "vout": 1,
      "scriptSig": {
        "asm": "0014620cfaeb631c99d45490cc6560a7258835c260f8",
        "hex": "160014620cfaeb631c99d45490cc6560a7258835c260f8"
      },
      "txinwitness": [
        "3045022100a1e4403c6327fb787ef498cfaf6c54f8372f2792c06a7156cad6cf15c729de2802201eb1b48e2443b04688091897caf0fc9afbfc002227c05441a5f1723be9a532e401",
        "02533dc7b0e2d8f359fb235fd52bcda6135cfb0e39c6d9d93a10704457ff30e6ff"
      ],
      "sequence": 4294967295
    }
This is your problem, the input you are spending is a segwit input. You will need to figure out how to prevent your fork from creating segwit outputs that can be spent as inputs.
310  Bitcoin / Bitcoin Technical Support / Re: Using Createrawtransaction Got no-witness-yet Error on: May 03, 2018, 03:35:16 PM
Can you also post what your final signed transaction looks like?

getrawchangeaddress shows this:

Code:
3PgBJaR5fCw9nBtij7THqfHbbENdCdFEuv
This will be a problem for you later because that is a segwit address and you do not have segwit enabled.
311  Bitcoin / Bitcoin Technical Support / Re: Using Createrawtransaction Got no-witness-yet Error on: May 03, 2018, 03:24:12 PM
I did not include any Segwit in any transaction. why does it show here?
Are you sure? If you forked from the latest Bitcoin Core, it uses segwit by default. Can you post what the changeaddress looks like and what the output of listunspent looks like?
312  Bitcoin / Bitcoin Technical Support / Re: Using Createrawtransaction Got no-witness-yet Error on: May 03, 2018, 03:08:43 PM
This error means that you are trying to spend from or create segwit outputs without segwit being activated yet. Is your node fully synced?
313  Bitcoin / Bitcoin Technical Support / Re: Upgrading to Bitcoin Core 0.16 on: May 03, 2018, 03:08:55 AM
I used to use a old Bitcoin Core and it crash.  I kept the wallet.dat file.  It is only 88 Bytes.  
Your wallet.dat file is most definitely corrupt and does not contain any key data if it is only 88 bytes. An individual key is much longer than 88 bytes. The keys don't even exist in this file so there really isn't anything for you to even attempt to recover.
314  Bitcoin / Development & Technical Discussion / Re: Output in coinbase transaction on: May 03, 2018, 03:04:26 AM
No client checks for coinbase transaction outputs (we've forgotten about segwit, have we?)
Output values are checked to make sure that no more than the correct value is created. The output scripts are not checked.
315  Bitcoin / Bitcoin Technical Support / Re: How can I get a copy of blk0001 on: April 29, 2018, 07:19:56 PM
Like to get a copy of  blk0001 for 2009-2010.
It's the same as a modern blk0001.dat file. Those file formats have not changed.

And maybe you can tell me what format was the private key on a encrypted wallet was. Mid-2010 beta wallet before 3.2.4, before blue Matt changed the format on encrypted private keys.
Wallets were not encrypted prior to Bitcoin 0.4.0 when Matt introduced encrypted wallets. The format of wallets at that time for private keys is the same for unencrypted private keys today.
316  Bitcoin / Bitcoin Technical Support / Re: Setting Up First Wallet -- BitcoinCore 0.16.0 on: April 29, 2018, 02:45:44 AM
I am having trouble getting armory online and in turn, I have downloaded Bitcoin Core 0.16.0 to speed things up. 
Bitcoin Core does not just "speed things up" for Armory. Armory requires Bitcoin Core to be installed and running when Armory runs. Otherwise it will not work.

Is it OK / safe to store the block chain on an external drive? 
You can, however keep in mind that when you do so, Bitcoin Core's databases are more likely to become corrupted.

I have seen products which are 'physical wallets' (a USB drive) which seems like the same concept as I am investigating here. 
No, they are vastly different things.

If this is a viable option, will I have to connect the external drive each time I use my wallet? 
Yes.
317  Bitcoin / Bitcoin Technical Support / Re: Rewinding blocks every time I start bitcoin-qt on: April 27, 2018, 11:32:34 PM
Your node is rewinding hundreds of blocks, that seems like a huge problem.

What version of Bitcoin Core were you running before 0.16? This seems characteristic of upgrading from a non-segwit node to a segwit node. I'm guessing that's the problem (especially since the log is full of lines about non-standard transactions) and, with pruning, it gets into some weird feedback loop.

Your best option is to resync the blockchain entirely. You can do that by deleting everything in the datadir except for your wallet file.

It looks like you need to run the program with the -reindex command line option.
He's pruned so that won't work without resyncing.
318  Bitcoin / Development & Technical Discussion / Re: What IDE used for Bitcoin developement (Ubuntu) ? on: April 27, 2018, 11:09:46 PM
But what about making changes on the source code ?
Use a text editor. A source code file is just a text file. As I said earlier, many people use emacs or vim.

IDE is a good way to debug the code, retreive errors etc.
It's not the only way, and often IDEs require special configuration in order to work with projects that weren't created with them.

For debugging, you can use gdb.
319  Bitcoin / Development & Technical Discussion / Re: What IDE used for Bitcoin developement (Ubuntu) ? on: April 27, 2018, 08:39:36 PM
Most people who work on Bitcoin Core do not use an IDE. Many just use a text editor (such as emacs or vim) and the terminal. All of the build commands are documented and it is not difficult to copy and paste commands into the terminal.
320  Bitcoin / Bitcoin Technical Support / MOVED: ... on: April 26, 2018, 10:07:12 PM
This topic has been moved to Trashcan.

Trashed on request
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 66 ... 549 »
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!