running XP SP3 (yeah). installed core in an external HD.
I don't think it's the banlist.dat or write permission issues. sometimes I get past the opening and it crashes when I exit or while it's reindexing the blockchain. I even did a complete uninstall using revo uninstaller but it still doesn't work.
...
The instruction at "0x77c33509" referenced memory at "0x00000000". The memory could not be "read".
Following up from knightdk how much memory do you have on the system? Is this Windows XP Professional or not? A guess is that you are running a 32 bit version of Windows XP and you may just be running out of memory. |
|
|
|
|
Can you connect to the rpcport remotely at all? Eg with telnet or a port scanner? This is to eliminate a firewall issue.
|
|
|
|
I've been waiting on a localbitcoin transaction to confirm for hours now and still zero confirmations. Many of my friends don't know what I mean when I say "waiting on confirmations". Whoever flooded the chain to really show off their 1337 hax0r skills is a fucking moron.
Maybe it wasn't a bad idea to increase the memory pool...
You can increase the memory pool on your node by increasing the RAM - or are you talking about the block size? This is people spending money, probably to spam the network, not "1337 hax0r skills". You should probably read a bit more before posting this in the tech section. |
|
|
|
five days... BTC/USD price GO DOWN. Still 0 confirmations... Yes, bitcoin is "more better then traditional banking"...
The sender paid a super-low fee. You should talk to the sender about why they spent around US$0.0015 to send you the money. Were they just being cheap or didn't they think that paying you was that important? Think about it this way: it sounds like you don't want to work for free, well, the miners say the same thing - to a certain extent. A few days ago the recommended fee was around US$0.07 (iirc), that is still pretty cheap, the sender didn't even pay a penny. |
|
|
|
Move the coins to a new address - one to which only you have the private key. Changing the password of the wallet.dat won't help, you are correct. Hi all quick question. what is the best way to secure your bitcoin if someone else gets hold of your wallet.dat and knows your password? would changing the password in bitcoin core make any difference? i am guessing the old password will still allow the other person to access your keys no matter.
|
|
|
|
What software are you using? Are you using blockchain.info to do the sends or just using them (assuming that is what you meant by blockchain) to check the status? Hi, any help will be greatly appreciated.
I RECEIVED a payment. When it was still an unconfirmed transaction I use part of it, to MAKE a payment. I think it is this connection that is causing the problem. Both payments remained unconfirmed for almost 3 days and Blockchain cancelled them. The monies were returned but within minutes there was an automatic resend of both transactions (which I didn't want). Now the same is happening again....no propagation and no confirmations. I am concerned that after another 3 days Blockchain will cancel the transactions again, and another automatic resend will happen and i'll be stuck in an endless loop. I know the sender and I don't need the received payment. And I would just MAKE a payment. Please help, I don't know what to do.
Many thanks
Lok
|
|
|
|
the internet is a great thing  thank u all! i did the steps as shorena described it and the bitcoins are back in my wallet again. hope this thread will help others who have the same problem. Great. Shorena gave good advice! Just make sure you keep backing up your wallet, and if you are sending from Bitcoin Core, make sure it has been running for a little while so it can get the status of the network and calculate the correct fees to have the transaction go smoothly. |
|
|
|
hi,
thanks for the quick help.
the transaction id is: a4a2f6f82b1fe40732af81f13cc62ea315bfb9eb3d20b0a804cbef9d0e260f45-000
i canīt find anything on blockchain.
i am not sure if itīs safe to post the bitcoin address here.
if i follow the steps shorena posted - should i safe the wallet somewhere before?
@encrypted how long u guess until the blockchain forgets the transaction?
hours? days? weeks?
does it make sense to delete the transaction and wait until blockchain forgets it to send a new transfer?
how long could the transaction without fee take? days? weeks? months?
and also i would like to know if the issue with fees is new!?
i traded some bitcoins 4-5 years ago. i donīt remember fees being an issue back then.
I don't see it on blockr.io either. It NEVER hurts to have a backup copy of your wallet (stored in a secure location of course). If you are asking how long until "blockchain.INFO" forgets about the transaction, it looks like they rejected it anyway. |
|
|
|
I have learned that if anyone else send the push to priority then it may be more chance of getting confirmation, can you help me to push my transaction to priority. so that it can get confirmation soon. Pushing the transaction does not change its priority, it just makes sure the network does not forget about it. In your case I would argue you should wait for the network to forget about the TX and resend with a higher fee. I agree with Shorena here. Depending on which client you used to send the transaction, the methods of doing this vary. |
|
|
|
|
Your account where? For what?
You need to give more information to even know where to suggest you ask the question.
|
|
|
|
can you share us the transaction ID first so we could check it?
Yes, without this information, no one will be able to give you much insight. |
|
|
|
I'm running core 0.11.2 for around 8 hours each day. I've got 8 outbound nodes and no inbound nodes. bandwidth is around 30Kb/s most times. Recently I've noticed that ping rates during synchronisation for about half of the nodes can be in excess of 500,000ms. Once I have synchronised, then all rates seem to drop below 400ms, and are often in double digits. Is this just a coincidence ( it's just an impression, I haven't kept any stats), or do some nodes try to discourage contact from nodes that are synchronising?
Maybe it is just that a high volume of received traffic distorts the ping checking.
Did you really mean 500,000ms? e.g. 500 seconds? If so, that would seem something else is going on. |
|
|
|
hello
my C is a 240GB SSD
I installed the "Bitcoin Core" yesterday
it's been running about 30 hours and has taken up 42GB of space
I don't think I even have enough space for it to finish syncing up
why is it taking so much space ?
and why is it taking so long to sync up ?
gona be 40-50 hours
https://bitcoin.org/en/faq#what-does-synchronizing-mean-and-why-does-it-take-so-longWhat does "synchronizing" mean and why does it take so long?
Long synchronization time is only required with full node clients like Bitcoin Core. Technically speaking, synchronizing is the process of downloading and verifying all previous Bitcoin transactions on the network. For some Bitcoin clients to calculate the spendable balance of your Bitcoin wallet and make new transactions, it needs to be aware of all previous transactions. This step can be resource intensive and requires sufficient bandwidth and storage to accommodate the full size of the block chain. For Bitcoin to remain secure, enough people should keep using full node clients because they perform the task of validating and relaying transactions.
|
|
|
|
It seems that if it was never confirmed, then it should go back in the wallet. Otherwise, it's in limbo forever. Is that even possible? It is either sent or not sent.
This makes a good point. Bitcoin isn't "in limbo." At a low level, bitcoin relies on inputs and outputs, so the bitcoin is either in the original "spot" or the next "spot." Nothing gets 'returned' and nothing 'goes back' because it is either in spot A or in B. ;-) There is a 3rd state though when an input was spend and the TX its used in is well known to the network. In this state is difficult to move it from its original spot to a different next spot. Id call that "in limbo" even though its an abstraction of what really happens. The 3rd state isn't on the block chain though which is what I was speaking about. I do get the point about the tx being well known, but the bitcoin hasn't 'moved' at that point, just that the network is aware of an unconfirmed transaction. :-) |
|
|
|
It seems that if it was never confirmed, then it should go back in the wallet. Otherwise, it's in limbo forever. Is that even possible? It is either sent or not sent.
This makes a good point. Bitcoin isn't "in limbo." At a low level, bitcoin relies on inputs and outputs, so the bitcoin is either in the original "spot" or the next "spot." Nothing gets 'returned' and nothing 'goes back' because it is either in spot A or in B. ;-) |
|
|
|
Thank you for your quick response...If I decide to go with Electrum, can you provide me the link to download?
How do I export the private keys from the bitcoin core to electrum??
My system is old (vista OS). How long would you estimate the download of Electrum??
I hope to hear from you SOON!!!
Electrum is here: https://electrum.org/#home(ONLY download from the official sites for any of the wallets, btw) The Electrum sub-forum is here: https://bitcointalk.org/index.php?board=98.0Electrum itself is small - maybe 30MB depending on the version so it is quick to download electrum itself. As far as exporting, this has some step by step instructions: http://bitcoin.stackexchange.com/questions/4203/how-can-i-export-the-private-key-for-an-address-from-the-satoshi-client/5933#5933 : launch your bitcoin client
click on 'help' in the menu bar (top right)
click on 'debug window'
select the 'console' tab
type: walletpassphrase "your walletpassphrase here" 600
type: dumpprivkey [your Bitcoin address here]
this will return the private key, you can copy it now; ensure you clear your clipboard/history afterwards
|
|
|
|
Thanks cr1776 appreciate the reply......  think i am probably being overly cautious, but have already lost 2 BTC to a scam and dont want to lose any more....lol I don't think you can ever be too cautious. :-) |
|
|
|
-snip-
Ok so a random 12 word password should be strong enough then ?
See the post by cr1776, I dont know. It depends on your way to select random words and the word basis or number of words. It sounds good though. and i prob have no need really to create a .conf file to be honest, but interesting to know. thanks alot for the help
Usually not, no. i used a 12 random password that i had generated from counterparty wallet for some SJCX, could that be an issue? counterwallet.io i doubt very much that the counterparty wallet stored my password....... i think that it is browser based....  In theory a 12 character random password should be good enough. Is it just alpha-numeric characters? Lower case? Upper case mix? Special characters etc? (Don't answer, but that changes the math). Was the random generator that generated it really random? I think the smart advice is: if you don't need to leave the wallet.dat somewhere where someone could copy it and then try to brute force it, don't. But it really depends on the threat that you are worried about. If this is just a computer that your family is using, that is one thing. If this is a USB that you are going to throw away where someone might find it and look at it that is something different. If the wallet.dat is going to be somewhere where you have untrusted people -e.g. people you don't know- who have access to the wallet and computer at random, if you can remove it from the computer/drive etc, you'll be better off. The more bitcoins you have stored in the wallet (or the more that you could potentially have in there at some point in the future) the more concerned you need to be about where it goes. I think the main thing people have to be worried about is a virus on the computer that is stealing their credentials though. |
|
|
|
-snip- Great help, thank you, so thats why it is always best to use a new address for sending and receiving Bitcoin  But its wrong!. Bitcoin core keeps (by default) 100 unused private keys and addresses pre generated for you. This would only work if you would use all 100 (change)addresses. You can change this by adding keypool=103 to your bitcoin.conf file. Ok so then it is dangerous to leave old wallet backups on computers or USB pendrives that others have access to. Shorena could you explain abit more about keypool 103 into bitcoin.conf? where is that file? i have checked %appdata% and cant see it Yes, it is dangerous to do so. Even password protected wallets shouldn't be left where others have access. People often overestimate the security of the passwords that they use and the password that they think is "good" is, in reality, bad. So while the software is good at protecting the wallets reasonably well IF you have a "good" password, if you have any significant number of bitcoins (or alt coins in an alt coin wallet) leaving the wallet.dat exposed anywhere is not recommended if you have the ability to remove it. |
|
|
|
|
Show Posts
