Bitcoin Forum
May 21, 2024, 10:27:12 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 [461] 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 ... 514 »
9201  Bitcoin / Mycelium / Re: Help an ignorant newb with MyCelium on: June 21, 2017, 04:46:52 AM
So, every time I send from mycelium wallet....  it sends ALL my funds
example  I enter $120 to send... i hit priority fee... it shows $2.25     then i click send....and boom... it zaps my account for $126 and adds the extra to the sending fee.
I know i am missing something obvious,  please help
Firstly, don't use Fiat amounts when referencing bitcoin transactions... It is confusing and can be largely irrelevant. The currency is so volatile that it could simply be that the reason you are seeing different amounts is that the exchange rate is changing...

I would suggest working in BTC amounts... that way it is easier to tell if the system is sending or less than you expect it to.

9202  Bitcoin / Bitcoin Technical Support / Re: Can I delete bitcoin core and the blockchain if Im moving from armory-multibitHD on: June 20, 2017, 10:48:41 AM
Before you commit to MultiBit HD, you might want to browse through this subforum: https://bitcointalk.org/index.php?board=99.0

Pay particular attention to all the "Password did not unlock the wallet" threads... You may also find this issue thread on the MultiBit HD Github interesting: https://github.com/keepkey/multibit-hd/issues/982

The issue has been known for weeks... not sign of a fix from the MultiBit HD devs


TLDR; MultiBit HD is probably not a reliable wallet at this point in time
9203  Other / MultiBit / Re: PLEASE help a newbie? (Multibit...) on: June 20, 2017, 10:34:23 AM
No, addresses are not one time only... although it is not advised for privacy reasons, you can re-use addresses multiple times.

On your "Payments" screen, you should see the address that was generated when you did the "Request".

1. Is this definitely the address that your cloudmining service has?
2. Have you checked that address on a blockexplorer like www.blockchain.info? Does it show the payments being made by your cloud mining service and a non zero balance?
9204  Other / MultiBit / Re: MultiBit on: June 20, 2017, 10:26:41 AM
Multibit classic isn't really functioning "normally" now to be honest... it isn't supported, it isn't maintained... there are instances of people having wallets that won't unlock...  I think the hard fork is the least of your worries Undecided

Having your private keys exported and backed up somewhere is a step in the right direction. You'll be able to import them to whatever client you want to, whenever you want or need to.
9205  Bitcoin / Electrum / Re: Quick newb question, want to verify before accepting large payment. on: June 20, 2017, 10:12:30 AM
... My question is, that receiving address that I gave out two days ago is still unused, and even though the current one showing is different, the unused address I gave out the other day is still ok to receive the payment to, correct? ...
Assuming that the "unused address" you gave out the other day is actually contained within your wallet, then yes... it should be OK.

You should either:
1. Look at the address tab (You may need to goto "Wallet -> Address" to get it to show)... is the address you gave out listed there?
or
2. Goto the console... and type the following command:
Code:
ismine("PUT_THE_ADDRESS_YOU_GAVE_OUT_HERE")

If it says "true" then yes, the address is yours, it'll be fine... if it says "false" then DON'T get coins sent there until you figure out where that address is from!

9206  Bitcoin / Mycelium / Re: compiling github mycelium wallet issues on: June 20, 2017, 10:02:25 AM
Did you see my response here: https://bitcointalk.org/index.php?topic=293472.msg19627824#msg19627824

Do you not get the build options in Android Studio?
9207  Bitcoin / Mycelium / Re: Question about bitcoin wallet address on: June 20, 2017, 09:52:49 AM
Mycelium autogenerates new addresses when the previous address is "used" (ie. it receives funds). This is to prevent "address re-use" as it is generally considered to be a "Bad Thing"™... generating new address for each transaction "helps" with privacy for yourself and others sending/receiving coins to/from you.

Anyway, this is why you see "contains 2 private keys"... you have the private key for the address in the "Output" section (this was the 1st private key in your Mycelium wallet). When that address received your initial deposit, Mycelium automatically generated the next private key and matching address.

If you send coins to the current address that shows in your balance (or receive) tab... you will find that Mycelium will generate a 3rd private key... and the address showing on your balance (and receive) tab will change again.

This will occur whenever the most recently generated address receives coins for the first time. If you send more coins to the 1st address, Mycelium will not generate another address.
9208  Other / MultiBit / Re: Trouble recovering Multibit Classic Keys on: June 20, 2017, 05:18:07 AM
 I've sent you a PM... I'll have a play with some old versions of MultiBit Classic when i get off shift tonight... hopefully i can replicate these different file formats and figure out exactly what these 94 character strings are...
9209  Bitcoin / Development & Technical Discussion / Re: Pywallet 2.2: manage your wallet [Update required] on: June 20, 2017, 01:30:37 AM
Sorry I should have been more clear, I'm running this on a computer that doesn't have any bitcoin software installed, just the wallet.dat file from my old computer, and pywallet.
For the wallet dump the command I ran was:

$ python pywallet.py --datadir=./ --wallet=wallet.dat --dumpwallet --dumpwithbalance > keys.txt
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.


I've tried changing the permissions of the wallet file with chmod, and running the command as sudo to make sure its not a permissions issue, but it still gives the same response...
Have you tried specifying the full path to the wallet file rather than just . ?? It's possible that the script is attempting to parse this as a full path and may not be locating the file correctly? I haven't looked at the actual code to see how the script is handling the --datadir argument, so I'm not 100% sure of the format required here.

When I get home from work tonight I'll have a proper look and and a bit of a play around with it and see if I can replicate and/or figure out some more specific solutions for you.
9210  Other / MultiBit / Re: MultiBit on: June 20, 2017, 01:22:10 AM
The only people likely to suffer "loss" as a result of whatever happens on Aug 1st are those that have their coins stored on exchanges, gambling sites, web wallets etc where their coins exist in an "account" where they do not directly have access to and/or control of the private keys controlling these coins.

As any fork will use the existing blockchain history, if you have your coins in addresses with private keys that you control, you will still have access/control of those coins post fork... regardless of which side of the fork you want to use.
9211  Economy / Web Wallets / Re: Why is coinbase fee much higher? on: June 19, 2017, 10:04:13 AM
Currently, recommended fees (as seen here: https://bitcoinfees.21.co/) are over 300 sats/byte... and have been for a few weeks.

Your fee of 0.00087576 btc... at a rate of around 300 sats/byte would indicate your transaction size was around 300 bytes... it seems about right for the current fee levels. Your options are to use a different wallet that allows you to set fees at a custom rate (but face the possibility of slow or no confirmation times), put up with current high fees and get fast confirmations or wait until the network is a bit less overloaded and send your coins in off peak times... when there is less demand and lower fees are required.
9212  Bitcoin / Development & Technical Discussion / Re: Encrypted NFC tag for paper wallet? on: June 19, 2017, 09:12:55 AM
If you encrypt the private key with a password, then anyone who gets close enough will have access to the encrypted private key. Anyone with the encrypted private key could go to a second location with powerful equipment, and attempt to figure out the password -- being that humans are bad at generating 'random' passwords, it would not be unreasonable to say that the password would eventually be figured out.
Could you not just store a BIP38 encrypted private key on your NFC then, much like you would on a paper wallet? And for an added bonus paranoia put a password on top of that on the NFC chip data?

Also, the OP did actually mention storing the tag in a "blocker sleeve", by which I assume they meant one of those RFID signal blocking sleeves designed to prevent the tag from being read without physical access to remove it from said sleeve.
9213  Other / MultiBit / Re: can some one help me? on: June 19, 2017, 08:37:48 AM
No, you should open it from inside the MultiBit program... then use "File -> Open Wallet". Don't try and open it in wordpad or notepad etc.

Also, you have opened the multibit.info file... you want to open the multibit.wallet file (or the multibit-[YYYYMMDDHHMMSS].wallet file from your wallet-backup folder). The YYYYMMDDHHMMSS is the Year-Month-Day-Hours-Mins-Seconds that the file was created.

Pick the one that has the date before all your coins went away.

You can also check those "receive" addresses on www.blockchain.info (or another block explorer) to make sure they still have coins in them.
9214  Economy / Web Wallets / Re: forgot and lost private key blockchain.info on: June 18, 2017, 08:31:02 AM
Like I said, it would appear that when you imported this address into blockchain.info that only the public key or the public address was used to do so. If you have subsequently lost the private key attached to this address, then you are not going to be able to get the bitcoins.... ever. No one is. Sad

There is no brute forcing (or guessing or reverse engineering) of private keys. It just isn't possible with current computers. You either have it, or you don't. If you don't have it, then you don't have access to the coins in that address. Undecided

I would highly recommend you immediately stop sending any coins to this address until you can locate the private key for it. You should create a new address so that you have the private key, and send your coins there instead.
9215  Bitcoin / Mycelium / Re: Mycelium Bitcoin Wallet on: June 18, 2017, 08:24:20 AM
I still haven't set up an Android dev environment due to laziness and lack of time and resources... but looking at the github code, that gradle build is supposed to be able to create multiple APKs

If you are using Android Studio, it would appear that to pick the "Product Flavor" that you want:

You can change the build variant to whichever one you want to build and run—just go to Build > Select Build Variant and select a one from the drop-down menu. To start customizing each build variant with its own features and resources, however, you'll need to know how to create and manage source sets.

So, theoretically you should be able to pick "prodnet"...

Given that is listed as a product flavour here: https://github.com/mycelium-com/wallet/blob/master/mbw/build.gradle
9216  Bitcoin / Bitcoin Discussion / China "Roundtable" and Segwit2x... on: June 18, 2017, 07:06:44 AM
So, I swept through the top five or six pages here... and didn't see anything related to this... I stumbled across this announcement on BTC.TOP (yay for Google Translate)... The original text is here: http://www.btc.top/resolution.php

I see they mention July 31st... is this an attempt to cut BIP148 off at the pass? All aboard the Segwit2x Train?? What's going on? Huh

Quote
China 's counter - dollar roundtable forum on the decision to implement the special currency New York consensus expansion program resolution

In order to effectively solve the problem of Bitcoin network congestion, we will accelerate the development of Bitcoin expansion and promote the sustained, healthy and stable development of Bitcoin. With the support of various mines, exchanges, miners and miners, The meeting of the participants in the June 15, 2021 held a special currency agreement to upgrade the meeting, the meeting we unanimously decided to fully support the promotion of Bitcoin New York consensus expansion program, and reached the following resolution:

1, we support the New York Consensus SegWit2x program;
2, we will next Monday (June 19) began to vote to support SegWit2x program. In order to avoid using the bit4 vote to influence the official voting results, we will write the "NYA" tag in coinbase and vote on the New York Consortium SegWit2x program.
3, we will start the New York Consensus SegWit2x program btc1 (https://github.com/ Btc1) software test and join testnet5, and after the release of the official version as soon as possible after the release;
4, we eager to activate the July 31 before the New York consensus SegWit2x program.
Participants are as follows:

1,1hash.com
2, Hu Lan (currency net mineral pool)
3, Jiang Thatcher (BTC.TOP, LTC.TOP)
4, Li Ang (Canoepool.com)
5, Pei was (easy to dig)
6, Liu Aihua (see currency )
7, Mao Bank (F2pool pond)
8, PZ (China Bitcoin roundtable Forum convener)
9, Wang Ruixi (BATPOOL.com)
10, Wu Gang (letter of mine currency pool)
11, Wu Ji Han (bits mainland)
12, Xu Zijing (Kosovo Capital Australia Collinstar)
13, Yang Haipo (ViaBTC.com)
14, Zhao Qianjie (Bit Coin China National Pool)
15, Zhu Jiawei (fire coins)
  June 15, 2017
9217  Economy / Web Wallets / Re: Bitcoin has been stuck on pending for 3 days on blockchain. Help me out on: June 18, 2017, 05:57:34 AM
Your transaction used a fee of 70 sats/byte... that wasn't even close to the current recommended fees:

https://bitcoinfees.21.co/
https://btc.com/stats/unconfirmed-tx

Recommended fees are well over 200 sats/byte minimum these days... usually over 300 sats/byte. I suggest you make use of the "Customize Fee" option that blockchain.info has included now. You can see exactly what the "Regular" and "Priority" fees being used are before you send...

Making sure the fees are correct will save you from such problems in the future!
9218  Other / MultiBit / Re: can some one help me? on: June 18, 2017, 05:03:20 AM
If you can't copy the file, you should be able to just open MultiBit program... then select "File -> Open Wallet"

You will get a Window open that allows you to select a wallet file. You should be able to see the "multibit-data" folder... double click that... and then double click the "wallet-backup" folder. You should see your backup files.

Select the one from the date before your bitcoins disappeared and then click open. This should open your wallet backup and you should be able to see your coins (assuming they have not been hacked/stolen).
9219  Bitcoin / Electrum / Re: Electrum keeps synchronising on: June 18, 2017, 04:46:30 AM
Can you provide a bit more information about your setup, such as your OS and Electrum version. Also, are you using a "seed based" (aka HD) wallet with 12 word seed or a traditional keystore (collection of random private keys)?

I vaguely remember that there was an issue around Electrum 2.5 or 2.6 where it would go into an endless synchronising loop... For the record, the current version is 2.8.3
9220  Bitcoin / Wallet software / Re: Is it my understanding or Jaxx being pants? on: June 18, 2017, 04:41:59 AM
When searching for a wallet/s I quickly learned that downloading the full node for each respective currency is a sure way to fill up my 128gb harddrive.
Yeah, just the bitcoin blockchain will eat up around 120gigs on it's own Wink If you are storage space limited, you definitely want to be looking at "SPV" or "light" wallets.

Quote
First quick question... If the private keys are stored locally how come when I installed Jaxx on my android phone did I just have to enter the 12 word pass phrase to get access to my private keys? They must have been downloaded from somewhere which means they are stored at a location other than 'local'. Is this a vulnerability (surely, 'Yes' ?).
No. They are not downloaded from somewhere. Seeds work by using the 12 'random' words out of a defined list of 2048 words to calculate a (very large) random number. This is your 'seed'. All of your private keys/addresses are then calculated from this seed in a deterministic and repeatable way.

Quote
Jaxx was reported to have been insecure earlier this week but I dont know exactly how. Some of what I have read seems to suggest the security issue comes from thieves accessing your harddrive for the 12 word pass phrase. Most of my reading was on forums, and news websites I have never heard of so I concluded I might be contaminating my mind with potentially misinformation and just swallowed that Jaxx could be insecure. I'm assuming the locally stored private keys are kept in C:\Users\%User%\AppData\Roaming\Jaxx. Does my encrypted C: help my security? Couldn't the developers just code Jaxx so that this folder can be kept on a USB stick so that the private keys are offline until you need to use them?
They could just as easily implement a password/passphrase functionality into the Jaxx application that encrypts your wallet file instead of leaving your 12 word seed in plain text for hackers to come and steal... but apparently they were "happy with the way things were"... this may have changed after all the publicity and backlash from their userbase.

Essentially the vulnerability stems from the fact that your 12 word seed is very easy to retrieve from your wallet file if a hacker gains access to your system.

Quote
My frustration with Jaxx started yesterday when I tried to use Shapeshift to exchange some ZEC for ETH. The transaction debited my ZEC wallet and I knew I would have to wait a little while for it to appear in my ETH wallet. So I went to bed only to find this morning that the ZEC had been returned to my ZEC wallet and nothing credited to my ETH wallet. The transaction failed. No real loss to me other than ETH was a relatively good price given my point of entry to the cryptocurrency game. But I cant find any record of the attempted exchange or the return of the ZEC. The transaction history in Jaxx only shows the very first payment from the pool. So I reset the Jaxx cache. Still only one entry in the transaction history only now its the most recent payment from the pool, oh and the value of my ZEC coins now says £0.00. The ZEC balance is there (all of what I have mined) but no figure for £ or $. Long story short... bar a few minor differences, the same happened with the Jaxx android app too. I have typed my public address into the ZCash block explorer and it reports 6 transactions received but nothing sent. I kind of expected to 1 sent (my exchange) and 7 received (my 6 pool payments and the returned exchange).
Sounds like your transaction sending to ShapeShift never confirmed or was rejected by the network... like most blockchain related transactions, if it isn't actually recorded into the blockchain (by being confirmed in a block) then your transaction doesn't exist. This is why there is no record of it in your account... because there is no actual record of it. Why that might be, I couldn't say, you'd need to contact Jaxx and/or ShapeShift Support and see if they can explain why your transaction failed.

Quote
Another thing that has me scratching my head is when I view my private keys. When I first tried mining to my wallet address. It failed, it wouldn't mine. So I clicked on 'view private keys' and there were two private keys, each with a different public key. I just selected one the of the public keys and mined to that. Its been working fine. I have read that its a good idea to change the wallet address for each transaction so expected this to change after each transaction. Sure enough this has changed but its changed to the other public key (the one I didn't use to mine to). I'm confused by this because that new wallet address is an existing public key that is derived from a different private key. I thought that your wallet has/is a private key. From this, you get a public key and from that you get a wallet address. Even if the public key changes too I expected the private key to always be the same. Is this normal?
Your understanding of HD (Hierarchically Deterministic) wallets and private keys is a bit lacking... an HD wallet, as I explained above, uses a "seed". From this starting point... all your private keys (and matching public keys/addresses) are then calculated.

Every address has it's own matching private key... they are often referred to as a "private key/address pair".

Your wallet is really just a collection of private keys. Most of the HD wallets will automatically generate a new address, when the previous address gets "used" to try and minimise address re-use (what you read about it being a good idea to change wallet addresses etc). So what has happened, is that after the one you selected received some coin from your mining, the wallet automatically switched to the next unused address. If you were to send some coins to that address, the wallet would automatically generate a new private key/address pair and give you a 3rd public key.

So, your "seed" will always stay the same... but each public key/address has it's own private key.


Quote
Is Jaxx just buggy and worth steering clear of? Am I just not well enough read. Or both!? I suspect both but Jaxx really isnt helping my understanding.
My personal opinion is that Jaxx is not a great wallet... But that is mostly because it isn't suitable for me and my use cases. I don't really deal much with altcoins and mostly just use BTC... so my needs are different to yours.

Quote
Am I right to expect just one private key with a public that may, or may not, change and a wallet address that does change after each transaction.
No. As explained, private key -> public key/wallet address.

If the public key (aka wallet address) has changed, so has the private key. Your wallet is just a collection of private keys.

Quote
Should I expect to see a complete list of all transactions made to and from my wallet or just the most recent since a cache reset?
Does a failed/returned transaction get logged as a transaction so that the attempt can be traced?
You should expect to see all transactions that are recorded in the blockchain for your private keys/addresses. If the transaction failed and nothing got confirmed into the blockchain, the transaction effectively "never existed".

Quote
(The convenience of only having to remember the passphrase is great (no backing up of files, and backing up the backup etc!) but it seems to me that you can access all my crypto-wealth by forcing the discovery of the 12 word passphrase. Couldn't you just write some code to punch in 12 word combos repeatedly until you hit gold? There are only so many words in English dictionary. EDIT, well 171,476, but as time goes on there will be a lot of wallets created and thus increasing the chances of finding an active combination. EDIT again, actually, there are about 1.348x10^54 combinations! Quite a few!)
It isn't quite that high... it should be more like: 2048 * 2047 * 2046 * 2045 * 2044 * 2043 * 2042 * 2041 * 2040 * 2039 * 2037 * 2038 = 5.27x1039

Most wallets don't repeat words in seeds as far as I know... but there isn't anything stopping that... so Danny's maths here: https://bitcointalk.org/index.php?topic=1623339.msg16320050#msg16320050 would probably be more accurate.
Pages: « 1 ... 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 [461] 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 ... 514 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!