Ninjastic
Search content
Sort by
Showing 20 of 90 results by jon_smark
Post
Topic
Board Altcoin Discussion
Re: [GIVEAWAY] @ThisWeeksCoin DOGE coins. Say Hi, get 100 doge!
by
jon_smark
on 24/01/2014, 11:29:28 UTC
Very hello. Such thanks!

D8wBN5agMAgd4xFPD5Ncckqg62jqFo4L7t

Post
Topic
Board Bitcoin Technical Support
Re: Finding out which wallet addresses have a non-zero balance
by
jon_smark
on 27/06/2013, 11:22:22 UTC
By the way, in the meantime I've managed to solve my problem.  Here's how:

  • Used "pywallet --dumpwallet" on my backed-up wallet to get a list of private keys.
  • Deleted the wallet and started Bitcoin-qt.  This created a fresh wallet.
  • Wrote a shell script to iterate through all the old private keys and import them using "bitcoind importprivkey account rescan=false"
  • Restarted Bitcoin-qt with rescan option

Step 3 was key: initially I tried importing also using pywallet.  However, Bitcoin-qt was then unable to read the wallet.  The solution was to use bitcoind itself to import the private keys!
Post
Topic
Board Bitcoin Technical Support
Re: Finding out which wallet addresses have a non-zero balance
by
jon_smark
on 27/06/2013, 10:00:17 UTC
Quote from: PaperClip on June 26, 2013, 09:41:45 PM
You do not need to do all this.
When you have backup of wallet.dat - you can just put it into bitcoin-qt corresponding folder (after you will manage to get it to work again).
Or else, you can create online wallet and import your wallet.dat backup there https://blockchain.info/wallet/import-wallet

I appreciate the reply, but did you read my question carefully?  The problem is that after the upgrade, Bitcoin-qt will crash on start up if I give it my wallet backup!  This is of course because of the differing libdb versions problem which has plagued Bitcoin-qt on Ubuntu for a while now.

However, importing the wallet into an online provider is a good option.  I'll keep that in mind.

Quote from: PaperClip on June 26, 2013, 09:41:45 PM
But, if all you want is just know balance -
1) create new wallet using pywallet
2) import all addresses and private kyes
3) open this wallet using bitcoin-qt
4) goto help-debug window-console (this is on Windows, but I suppose on Linux it is the same)
5) write command getreceivedbyaddress XXXXXXXXXXXXXXXX(insert address here)
If address is not in your wallet - you will not be able to see balance on it

So basically I have to create a small script anyway to automate this process.  Which is what I why trying to avoid...
Post
Topic
Board Bitcoin Technical Support
Re: Finding out which wallet addresses have a non-zero balance
by
jon_smark
on 27/06/2013, 09:53:06 UTC
Quote from: jackjack on June 26, 2013, 09:34:23 PM
1. pywallet does this with the '--dumpwithbalance' flag (takes ~2 min / 100 addresses, of course depending on your connection)

Which version of pywallet does this?  I got mine from Github yesterday, and it does not have this option!

Quote from: jackjack on June 26, 2013, 09:34:23 PM
2. why don't you just import the wallet.dat in another bitcoin-qt installation?

Because frankly, the mess with Bitcoin in Ubuntu is such (because of the differing libdb versions) that a different installation will crash on start up if I give it my wallet backup.  I've tried.
Post
Topic
Board Bitcoin Technical Support
Topic OP
Finding out which wallet addresses have a non-zero balance
by
jon_smark
on 26/06/2013, 20:34:45 UTC
I'm unable to start bitcoind/bitcoin-qt after the latest upgrade of the Ubuntu PPA.  However, I've got a backed-up wallet.dat, and using the pywallet utility I also have a list of addresses and private keys.  I think the best solution right now is to create a new wallet and to import into it the one address which does have an associated balance (I know there is only one).  However, I don't know which address it is!  Is there a way to find out the balance associated with each address without having to manually check them on the Block Explorer?  (And yes, I could write a small programme to automate this process, but it seems I would be reinventing the wheel and abusing the Block Explorer service).
Post
Topic
Board Bitcoin Technical Support
Re: Ubuntu PPA packages broken after latest upgrade
by
jon_smark
on 05/05/2013, 16:46:40 UTC
Quote from: Matt Corallo on May 05, 2013, 03:58:58 PM
Ahh, this is your problem...yes, raring had no packages whatsoever in the PPA, so when you installed bitcoin-qt, you actually installed Ubuntu's version, which depends on libdb5.1, making your wallet incompatible with bitcoin.org's binary releases.  Raring currently has the latest 0.8.1, however Ubuntu is not likely to keep that up to date as new releases come out.  If you have a backup of your wallet prior to the upgrade (I'd hope so) and you haven't done anything with it since, you can just restore that backup and use the PPA versions.  Otherwise you will have to either continue using Ubuntu's version (remove the ppa, remove bitcoin packages, reinstall, and hope you dont fall too far out of date) or build your own bitcoin-qt/d and keep doing so using libdb5.1.

Ah, mystery explained -- thanks!

I've removed the PPA and "downgraded" to Ubuntu's version, and it works fine now.  One problem remains, however: sooner or later I may need to upgrade to the PPA version.  When that happens, I'll need to convert the DBs.

Am I correct in assuming that the blockhain DB is using LevelDB and does not depend on libdb?  And is therefore wallet.dat the only critical file still using libdb?  If so, I can easily migrate simply by exporting+importing the relevant addresses.  Or is there something I'm missing?
Post
Topic
Board Bitcoin Technical Support
Re: Ubuntu PPA packages broken after latest upgrade
by
jon_smark
on 05/05/2013, 15:49:48 UTC
Quote from: Matt Corallo on May 05, 2013, 02:42:03 PM
Which previous version of the packages were you using?
I updated the 13.04 ppa stuff because 13.04 didnt have ppa packages at all, however there should be no issues as long as the new libdb and such were pulled along at the same time.  I'm assuming you were previously on the 12.10 version?

Are you sure 13.04 didn't have packages before?  I did a fresh install of 13.04 last week, added the Ubuntu PPA, and installed the Bitcoin packages.  Today, I got the notification that some packages needed upgrading.  After "apt-get dist-upgrade", the packages bitcoin-qt, bitcoind, and libdb4.8++ were upgraded.  After the upgrade, bitcoin-qt/bitcoind no longer start due the error I mentioned.
Post
Topic
Board Bitcoin Discussion
Re: Ubuntu bitcoin packages
by
jon_smark
on 05/05/2013, 12:54:43 UTC
Yesterday (May 4th, 2013), the packages on the PPA were updated.  After the upgrade, the Bitcoin client no longer starts, due to database incompatibility problems.  Anyone else having the same problem?
Post
Topic
Board Bitcoin Technical Support
Topic OP
Ubuntu PPA packages broken after latest upgrade
by
jon_smark
on 05/05/2013, 12:41:15 UTC
Yesterday (May 4th, 2013), the Bitcoin-qt/Bitcoind packages were updated on the Ubuntu PPA (I'm using Ubuntu 13.04).  After the upgrade, Bitcoin fails to start due to database errors:

Code:
dbenv.open LogDir=/home/smark/.bitcoin/database ErrorFile=/home/smark/.bitcoin/db.log
ERROR: CDB() : error DB_RUNRECOVERY: Fatal error, run database recovery (-30974) opening database environment
Error: Error initializing database environment /home/smark/.bitcoin! To recover, BACKUP THAT DIRECTORY, then remove everything from it except for wallet.dat.

I have no intention of redownloading the whole blockchain again.  Is there any way to fix this, or should the Ubuntu PPA be deprecated?
Post
Topic
Board Altcoin Discussion
Re: Free Terracoins just post your wallet!
by
jon_smark
on 19/03/2013, 15:24:18 UTC
1KDSKCC29CobdBitSei2cUeedA1V9sh4HR
Post
Topic
Board Altcoin Discussion
Re: Ripple Giveaway!
by
jon_smark
on 03/03/2013, 00:01:39 UTC
rNMwBWtFrGKDfPkJcyMqbSBrhBQB4DSSWp
Post
Topic
Board Bitcoin Technical Support
Topic OP
Number of confirmations going down?
by
jon_smark
on 23/10/2012, 14:50:38 UTC
I've witnessed something puzzling on the Testnet: three blocks I mined had their number of confirmations suddenly go down.  One of them jumped from 285 to 263, though it has since monotonically increased again, as one would expect.  I thought that the number of confirmations could only increase, unless the block finds itself in an orphaned fork, in which case the number of confirmations becomes meaningless. So, what may explain this sort of situation?
Post
Topic
Board Bitcoin Technical Support
Re: Determining the account associated with a given txid+vout
by
jon_smark
on 17/10/2012, 20:47:43 UTC
Quote from: kjj on October 17, 2012, 06:33:34 PM
The database is going to be your best bet.

Way too expensive.  I reckon my original plan might be the cheapest option yet, even if convoluted.

Quote from: kjj on October 17, 2012, 06:33:34 PM
Also, you might want to consider using the cold wallet to protect the hot wallet, not to protect individual accounts.

I may be missing what you intended to say, but the cold wallet is used to protect the hot wallet, which happens to have several accounts.  Note that these accounts are not associated with external users; they all belong to me, and are just separate for administrative/accounting purposes.
Post
Topic
Board Bitcoin Technical Support
Re: Determining the account associated with a given txid+vout
by
jon_smark
on 17/10/2012, 13:14:39 UTC
Quote from: kjj on October 16, 2012, 01:04:25 PM
Why do you want to know?

Because I want to forward unspent transactions to a cold-wallet, and knowing the account would let me know immediately which cold-wallet to use.  Though I can derive this information by going through my databases, if Bitcoin were to tell me the associated account that would save me the costly database access...
Post
Topic
Board Bitcoin Technical Support
Topic OP
Determining the account associated with a given txid+vout
by
jon_smark
on 15/10/2012, 17:37:43 UTC
Calling listunspent gives me a list of {txid,vout,spk,amount,conf}.  I also want to determine the account associated with each item in that list.  This can be done in two steps: 1) calling getrawtransaction txid will get me the address associated with a txid+vout combination; 2) calling getaccount addr will finally get me the associated account.

This works, but is awfully convoluted.  Is there a more straightforward way?  I thought about calling gettransaction txid, which does provide account information associated with each "receive" address, but I'm not sure whether I can rely on the array order being exactly the same as the original vout.
Post
Topic
Board Bitcoin Technical Support
Re: More than one address within each vout?
by
jon_smark
on 15/10/2012, 17:26:37 UTC
Thanks guys!

And if someone can find a counterexample, please let me know!
Post
Topic
Board Bitcoin Technical Support
Topic OP
More than one address within each vout?
by
jon_smark
on 15/10/2012, 15:10:16 UTC
If you run bitcoind getrawtransaction abcd1234... 1 you get a fairly complex JSON object with all the information about the given transaction.  My question concerns the "addresses" field deep inside each "vout": if I understand regular Bitcoin transactions correctly, this array should usually contain only one address; on what circumstances would it contain more than one address?  Also, could someone point me towards one transaction (either mainchain or testchain) where more than one address is used?
Post
Topic
Board Bitcoin Technical Support
Topic OP
Questions concerning the official client API
by
jon_smark
on 21/08/2012, 15:14:55 UTC
I have two questions concerning the official Bitcoin client API:

First, getreceivedbyaccount is listed as taking two optional parameters: account and minconf.  However, the source in bitcoinrpc.cpp implies that the account parameter is actually mandatory.  Oversight in the wiki or error in the code?

Second, what exactly is the difference in semantics between the minconf optional parameter that several calls accept and the target-confirmations optional parameter accepted by listsinceblock?  I understand minconf well enough, but doesn't target-confirmations mean exactly the same thing?

Thank you guys!
Post
Topic
Board Bitcoin Technical Support
Re: Is wallet encryption a one way street?
by
jon_smark
on 20/08/2012, 16:58:34 UTC
Quote from: cbeast on August 20, 2012, 01:38:54 PM
You can't unencrypt a wallet, but you could move funds to an unencrypted wallet. Encryption is pretty important. I can't imagine why you would not want encryption for a personal wallet like the Original Bitcoin client.

Thanks for the reply.  However, note that my question did not imply any opinion regarding wallet encryption.  I was merely wondering if there was an API call missing from the wiki...
Post
Topic
Board Bitcoin Technical Support
Topic OP
Is wallet encryption a one way street?
by
jon_smark
on 20/08/2012, 13:33:09 UTC
Looking at the original Bitcoin client API I noticed one thing: once a wallet is encrypted with encryptwallet, there does not seem to be an API call that unencrypts the wallet.  Sure, you can change the passphrase with walletpassphrasechange, but the encryption remains.  Am I missing something, or is encryptwallet really a one-way street as far as the API is concerned?  (One could of course restore an unencrypted wallet from a backup, but that's not in discussion here).