|
Yet another example showing why you shouldn’t leave coins with a third party unless you intend to sell then on the exchange or use them.
|
|
|
|
someone send me 120usd in bitcoin and it showed low few for the past 24hrs i haven't have 1 confimation yet and it say 'expected confirmation time is unknown' what should i do?
What is the transaction ID? |
|
|
|
Hello, i am already registered on Coinsecure but whenever i try to do my KYC details, I get stucked at "name of city"
after selecting State, it seems that there is a dropdown box that comes up with your city name but in case of gujrat, there is none and hence i am unable to upload my kyc details. any one got same problem?
As far as your question, have you contacted Coinsecure's customer service to get some assistance? However, since this is about a service and nothing technical about Bitcoin Core and the network, you should probably move it to the Service area instead of " Bitcoin > Development & Technical Discussion". |
|
|
|
So this is my first post so i do anything wrong please correct me. But i recntly out 0.003 bitcoins into my electrum wallet. Today i transfered 0.0015 of those to exodus. This went fine but when i checked the transfer fee it was $17!!! (0.0007 bitcoin) Is this some sort of error? how can i cancel/ get it back. PLease hellp
If it is confirmed, you can get it back or cancel. Make sure you verify that the fee set is what you want. |
|
|
|
I am compiling bitcoin wallet 0.9.4
In the guide it says
Cd /c/bitcoin-0.9.4
./autogen.sh
CPPFLGS=“-|/c/....
Autually how to run this since CPPFLGS is not a command
Where to put this code? Run command it was not recognized
CPPFLGS is a variable/macro used to include directories. make then uses them as part of the build process. Are you using the shell as mentioned in the instructions you are following? (e.g. Install msys shell ). Perhaps you are using the wrong shell? And to reiterate what achow101 said, is there a reason to use 0.9.4 vs 0.15.1? |
|
|
|
And it notes that as of Dec 15, 2017, there were 15 applications for bitcoin ETFs. If any or all are approved, it will be another game-changing moment. |
|
|
|
That is a nonsense, probably OP just wants to scam people.
Not its idea only Dont tell that Then why post your address for people to send bitcoin to? Posting something that is clearly wrong and then asking for donations seems scammy. Besides, if you are going to post in the "Development & Technical Discussion" section, you should at minimum have some idea of why this will not work. Otherwise, it is probably better moved to the Beginners and Help section. |
|
|
|
I have come back to this thread many, many times. And I am so glad that I did!
Thank you, thank you, all of you who convinced me with your analysis and logic.
I (still) wonder how Atlas is doing - hopefully well after all the drama from years ago. I wonder if he held through all the ups and downs or if he went on to something else. Must be in his 20s now. |
|
|
|
There are 2 ways to generate an address from a private key. Compressed and uncompressed.
There is only 1 way to generate an address out of a public key: address = ripemd160(sha256(public_key)))The public key (composed of: prefix, x-coordinate, y-coordinate) can be either compressed or uncompressed. Which doesn't matter in this case because the second multiplier (y) can be derived from the first multiplier and the prefix. The problem is most likely the wrong derivation path used while trying to recover the correct keys. m/44'/0'/0' should be the right path for JAXX wallets to restore. Depending on the client you use to generate your keys m/44H/0H/0H may be another accepted format. OP, what are the first characters of the addresses? |
|
|
|
There are 2 ways to generate an address from a private key. Compressed and uncompressed.
There is only 1 way to generate an address out of a public key: address = ripemd160(sha256(public_key)))The public key (composed of: prefix, x-coordinate, y-coordinate) can be either compressed or uncompressed. Which doesn't matter in this case because the second multiplier (y) can be derived from the first multiplier and the prefix. The problem is most likely the wrong derivation path used while trying to recover the correct keys. m/44'/0'/0' should be the right path for JAXX wallets to restore. Depending on the client you use to generate your keys m/44H/0H/0H may be another accepted format. You are correct in what you said, but that was not what aplistir said. There are two ways to generate an address from a private key, meaning two addresses. Perhaps op’s software is checking the ‘other’ one. Likewise it could be the wrong derivation path as you state. Best to try all possibilities. See, e.g.: https://github.com/OmniLayer/omniwallet/wiki/Converting-between-Compressed-and-Uncompressed-Addresses-and-Private-Keys |
|
|
|
Can you restore from a backup Unfortunately there are no earlier versions of the wallets. Once I encrypted the wallets, I emailed them to myself and those were the only backups I had. Is there still a copy in the email? Trash for example? |
|
|
|
If both wallets had the same password and they've both started to reject the password at the same time Not the same password for both, but the same structure for both. The chances of mistyping both are extremely low considering how careful I was. What is the possibility the .dat file is merely corrupt and no password will be accepted? Can you restore from a backup and try the passwords on both wallets? If both don't work, then it is likely that you have the passwords wrong. If they do work, problem solved. |
|
|
|
|
Just in case someone looks at this later to avoid confusion, the current version of Bitcoin Core is 0.15.1. There is no 5.7.1. He is perhaps talking about the qt version.
|
|
|
|
I was trying to transfer my BTC to an address and when I copied the address I didn't get the last character because it was text wrapped. I copied 36hMqcjP3CrVrGyitqNzteVrjyGjRn3mW instead of 36hMqcjP3CrVrGyitqNzteVrjyGjRn3mWc. The transaction shows that it is still pending. Is there any way to cancel or Did I lose all my BTC?
Do you have the purported transaction id? As others have asked, what wallet is this? It should be rejected and you should lose nothing - unless you hit the 1 in ~4 billion checksum lottery. |
|
|
|
i think the recent events (the 10-15 hard forks of bitcoin) have proven that you can do anything you want with bitcoin. "stealing inactive balances" requires a hard fork and doing that will create another altcoin similar to these 10-15 altcoins that started being created this month.
and it doesn't really matter anymore. it is not going to be "bitcoin". and the reason is simple. the notion of "inactive wallet balance" is ridiculous. it is simply thievery! no matter how pretty they are going to disguise it. it is like me coming into your home and take something out of your house and say since you are not using this item -that you paid for some day- i am going to take it away!
Agreed. And yet someone suggested it (again for the seemingly billionth time) on the dev mail list this week! If indeed this “untied bitcoin” is planning this, they must be getting desperate and I can’t believe many people will fall for it. |
|
|
|
|
Be careful sending your wallet or private keys to anyone. Even if they have a web site, offer to help, or appear legit. If you do so you could lose your coins.
You just need to have the private key or wallet.dat that contains them to access the coins.
|
|
|
|
Simple answered summarized :
1. Some of those bitcoiner don't care/know much about bitcoin development
2. People would see it's as attempt to centralize bitcoin
3. They have no idea how to fund unique/unusual technology such as bitcoin, especially since it's decentralized and people sometimes reject new ideas/upgrade/scaling solution
Also, it's hard to distribute the funds since anyone can contribute, only few knows how much someone contribute or whether the developer need funds (since some contributor already rich thanks to donation in early adoption phase)
Not to mention that like tcp/ip, smtp, ftp, dns, http etc, the protocol doesn't need a lot of changes. With SegWit and its components, much can be done at a higher level like http and dns are built on tcp/ip and web pages are built on http/https which is in turn built on tcp/ip. And those are places where people and companies can easily fund themselves with a good idea. |
|
|
|
What wallet did you use to create these? With 10 or 20 sat/byte, the fees are really low. You could try CPFP or RBF depending on the settings used to send them. You can also try viabtc. |
|
|
|
I'm probably wrong but here's my opinion on the subject. Others please feel free to correct me if I say something false.
So the whole structure of bitcoin is based on a p2p (peer to peer) network. Each wallet (full node) and miner that is has a copy of the blockchain verify the activity. The vulnerability that comes to mind when I think of a crazy super quantum computer's ability to attack bitcoin is this; what if the computer was able to create enough of it's own nodes to control over half of the network? Hopefully someone with more knowledge will elaborate on this. Because I don't think I understand how bitcoin works fully.
No. The fear is that if could do something like get a private key from a public key, but the hash function should mitigate that risk unless you are reusing addresses. You could spin up 10000 nodes right now pretty easily. My main hope is that quantum computers revolutionize search since this has been discussed many times before. 😂 |
|
|
|
|
Show Posts
