Hey Guys,
i have lost my wallet file but i have been able to recover the private keys. Problem is that they are encrypted with a passphrase. I know the passphrase but how can i now decrypt them to import them into a new wallet?
What program was used to encrypt the private keys? |
|
|
|
|
Can you create the obj directory in src/? (The make file should do so, but...)
eg something like mkdir obj or from the Windows desktop.
(Just adding some detail to Knights' answer)
|
|
|
|
I understood that locktime was disabled to prevent DDOSing the system with millions of delayed dust transactions, now that fees are semi significant, or at least not free, maybe it can be turned on again, because DDOSing the network would now involve some significant cost.
Delayed transactions have great potential for, guaranteed future payments, pensions, investment payouts, all guaranteed because they are in the blockchain.
Take a look at BIP65, perhaps that would be useful. |
|
|
|
Hi,
Ive got a small problem that whenever i make a new receiving address to send to someone to receive payment it doesnt create a clean address, What i mean by this is i can see old transactions from other addresses when i put the new address into block explorer. Is this supposed to happen? I thought the whole point of making new addresses every time was for more anonymity which i dont seem to be getting.
so is this normal? i thought not.
thanks
Which wallet are you using? What version of that wallet are you using? Are you certain you don't have any malware running on your computer? What method or process are you using to "make a new receiving address"? Hi, Its bitcoin core wallet version v0.11.2 (32-bit) I may have malware but dont think so the method im using is i go to file then receiving address, when the new window opens i press new which then creates a new address. I can show you an address if it helps any. thanks It probably would be helpful to see what you are talking about. Are you sure you are just seeing transactions that funded the address that is paying you? |
|
|
|
To be fair:
You shouldn't rely on the randomness of the hash if people are betting on it. Especially not after the hashing.
If you have a miner who stands to make more on the bet than they would on the block subsidy, the economics can favor them getting a hash low enough to make a block, but then withholding it, looking for a hash low enough to make the block *AND* having a final digit that will win them the bet as well. They risk losing the block subsidy if another miner finds a block first, but they can also instantly release the block they found the first instant they get a whiff of the other miner's block, and then they have a nearly-equal chance of getting the block subsidy anyhow. Meanwhile, they go on looking to win the bet.
This. When there is no incentive to mess with the hash, it may be safe to rely on the last digit. But as was said here (and DH above previously) when there is incentive to do so, it is possible to do so. Using the last digit of the hash of a single block as the sole random value for a sufficiently large prize is asking for problems. Even looking at all the values showing it looks random is not sufficient if the lottery drawing (for example) happens every 1000 blocks because you only need to do it once to win a massive sum (eg in the US's Powerball drawing the subsidy is minimal in comparison). In most of the blocks there is no incentive to select a particular hash so even if someone did it successfully 10% of the time (every 10000 blocks in this example) it would be undetectable in the noise. |
|
|
|
and if i didint receive in a hour? i look on my bit coin app and i sent but didnt receive in the game... anyone can explain to me how i cant contacct to anybody "mybitmine" i deposit about 2:00 pm today ... and now is 6:33 pm
The only thing you can do is talk to the people who run mybitmine. No one here can help you. The bitcoin was sent, it is up to the people who run this game to handle crediting your account in their game. I have no experience to know if they are legitimate or not or whether they have good customer service or not. |
|
|
|
ok so what do you suggest please? im not super i.t savvy but kinda know basics. any help or advice would be great, i have bitcoins in there and thought they were safe saved away.
Firstly, back up your wallet. Open the windows file explorer and type into the top bar and hit enter. You should see a file named wallet.dat. Copy that file to a safe location. Next, you should install the latest version of Bitcoin Core, 0.12.1. You can download that here: https://bitcoin.org/en/downloadAlso, your hard drive is probably too small. To run Bitcoin Core, you will need to have a larger hard drive or enable pruning. thankyou matey, i'm about to get some food but will try and resolve this later. i will keep you informed. thanks again for giving me hope lol, and the advice, you are a star. The most important advice was make a backup or two of the wallet before doing anything more. |
|
|
|
Yes, there was a lot of FUD leading up to November 2012. Pretty much like now %-wise, and probably like spring of 2020 will be. Now that we are into the next reward era (as of seconds ago), we'll see what happens. The advantage now is that we're nearing the end of the asic order of magnitude increases like there have been for nearly 4 years and will be back to growth in line with user growth and regular silicon improvements in the next year or so which should help to let more people mine and decrease consolidation. A question to the older members here would be to ask if there was this much worry and fud in the last halving? Surely back then miners where in the same situation that if we never got a price rise then it would become unprofitable to continue to mine and miners would drop out left right and centre. yet we are at another block halving and miners are still doing their thing.
|
|
|
|
But is it better than Pied Piper's compression algorithm?
Best thing I read all day lol I bet Hooli did an under the table deal with Lempel–Ziv on this lossless algo we're seeing here  Our compression algorithm is also a lossless compression, We tested on the bitcoin, compression and decompression about 200,000 blocks without any problem, And Blockchain compression rates may be the highest, And it's not just compression. Like knightdk said, the best way to get it into Bitcoin Core is to do a pull request. A few other suggestions: 1. If you create unit-tests and/or other tests that will also increase the speed at which it is evaluated and potentially merged. 2. If you were to create an option to enable it conditionally for both disk compression and network compression, so that it could be running on some nodes that were testing it vs an all-or-nothing approach to test it, I also think that would increase the likelihood of adoption. 3. Similarly, for the network bandwidth there might need to be a way for nodes running this compression code to identify each other so that it could serve compressed data when possible and uncompressed data (e.g. for non-upgraded nodes) at other times (this may already be implemented, I didn't check the code). Or alternatively be able to send either compressed or uncompressed dynamically through some type of negotiation. 4. You might also consider that some people (e.g. miners) might choose to serve uncompressed blocks when they have found a new block so as to minimize latency. e.g. I would serve compressed blocks for old blocks, but for one I just found, I might just send it uncompressed to avoid the time taken to compress it. It could be a trade off - is it faster to send an uncompressed block or to compress and then send. Much would depend on the network speed of connected nodes and I am not sure if anyone has tested which is faster to do. In short, the more groundwork that is done, the better. In general, on disk and sending old blocks that are compressed is a nice feature. My thoughts. |
|
|
|
|
Yeah, a huge stretch to tie it to Bitcoin. And it is written as if it is an ESL product.
|
|
|
|
Bump.
I don't want my Wily node to fall too far behind, with all the exciting updates coming out!
Your best bet is to compile it yourself, then you don't have to rely on anyone else. However, you can always ask (nicely) on irc if there are plans to build it for the ppa. |
|
|
|
|
Let's hope that they do, but while Putin is in power, I think that it is his decision vs a political party. ;-)
|
|
|
|
|
The article has affiliate links in it, so I would definitely question its objectivity.
|
|
|
|
Hi, This should help: https://en.bitcoin.it/wiki/Data_directoryOrphan blocks are stored too if you are connected to the network when it occurs. I am not sure about the -reindex from a higher number. I suppose it could in theory, but to have complete consistency, it starts from 1. Ok, thanks. That's reassuring. Has anyone described what the various files are in the bitcoin directory? Guessing all the blk files are the container files for the blockchain blocks ( but many blocks are in each file given how few files there are) Is it right to assume the -reindex is merely building the blocks/index files from the blocks/blk0?  .dat files? What happens to orphaned blocks? Are these also stored in these dat files? Sorry for all the questions, last one... would it be sensible to assume -reindex could actually be done from a number much higher than 1 it's simply the last LDB file that was corrupted because the FS was disconnected? |
|
|
|
If you have a fast drive and fast CPU, it shouldn't take days, but if you do have a backup of the entire directory, you should be able to just swap it out so that you don't need the full rescan and might only need to catch up between the date of the last backup and the current date. Thanks, yes I think it's more getting it setup and stable is proving difficult.
I'd like to use bitcore because of the node and HD wallet features... just seems it could be perfect for this project apart from getting the thing running on the new machine.
The reindex feature looks like it's going to take days to rescan.
Any idea why it would be considered insecure for bitcoin to just sync a snapshot, test the hash of the DBs in the snapshot and just test the block headers and merkel tree to ensure it's legitimate (up to the snapshot date)?
|
|
|
|
|
If you are using bitcore, why not just dump bitcore and use Bitcoin Core? Then see if you have the issues using only bitcoin core.
For what it is worth, I had bitcoin running for several years fall 2010-2014 on one machine and never had an issue. And then for 2 years on a different host with similar results. So I think it is one of those ymmv scenarios. If it is in a production environment, UPSs, SSDs, and similar robust measures are pretty much required.
|
|
|
|
|
First, make a backup, or two.
Then, just try renaming it without the .txt and see if that is the issue. There is recovery software to try also IF it gets to that point.
|
|
|
|
Are you sure you are using the correct passphrase?  My BTC wallet was bitcoin core ver. 0.12.1 After sending my BTC to another address, and waiting for two days status was 0 confirmation, maybe be because the transaction fee was not enough, So I found a solution from google, -salvagewallet, then it seemed to work But today I try to send my BTC again, after I insert my pass-phrase, a window show up which says assertion failed program:C:\........bitcore-qt.exe file:wallet/crypter.cpp,line 190 expression: false if click ignore button, it says pass-phrase incorrect. if click retry, it says runtime error. don't know how to solve this problem  |
|
|
|
|
Show Posts
