Topic: [RELEASE] Portable Bitcoin Client (for USB use!) (Read 9138 times)

Understandable, but I don't consider over a year of membership being "new," granted I haven't been on in a while.. But when I basically already showed the code and method I was using, its hard to understand why people will fuss about it. I'm not using an actual compiler so I can't just github it. I'm using a program to convert batch into a binary, however I recently started a C++ class in college so I'm very much considering making a binary.. It won't be as invisible as this one, but I'll do the job.. In fact, I think I'll start right now just to time myself on it.

People here are wary of programs, especially ones that come from untrusted/new people. Normally any code is posted in a github.

Back into Bitcoin again and decided to post my most recent change to the Bitcoin Portable Client for USB.
Though honestly, I don't use this one much anymore because I just created myself a Web App to access my wallet at Blockchain.info haha..  

Edit: Lmao, why would I pay for winrar? I got the portable version for free, just because I can.. Though I prefer 7-zip really..

First person I know that paid for winrar. Lol

Awesome

There is also this portable wrapper which I made: https://bitcointalksearch.org/topic/bitcoinportable-portable-bitcoin-wrapper-944

I was offended at your post opposing me again, but I saw the end and it was too primitively basic.
You see, to use the wallet manager, it helps to run it on your computer and keep a backup on the USB drive... Like a wallet!
I will, however, put a slight disclaimer in there though. thank you.
As for the quote above? That made me laugh... You are so naive that you entirely missed this:
(Side Note: _{And yeah, I bolded the part that you so easily missed. It was specifically to shut you up, and the fact that actual wallet management and movement should easily be open source because even I wouldn't trust a closed-source wallet manager. The reason the client is, is because it's easier to tell the icon apart from a simple batch file. If I could give a batch file an icon without needing another file, I would.})
And basically meaning that the wallet manager is "Wallet Manager.bat", a batch! But you wouldn't know shit about my program as you haven't even loaded the download site and looked at the posted list of the zip file. Before you accuse, open a damn sandbox and test this thing like any respective forum member, even try VMware or something like it. And yeah, THAT is how you properly test a suspicious file. I've taken my time studying how to actually test possible infected items, so I can know what I talk about before I bash something. But you just point the finger and are no better than the people at /b/.

I just don't see the need to roll bitcoin into an obfuscated exe to run a command line option, there aren't too many people using bitcoin that can't do that, and I am apprehensive that you think this is novel.

If you are going to be copying wallets around for people (which might actually be of utility if done right, but again, you haven't spelled out that you understand why you are doing it), it is very important you understand the 100 key problem. I'll just cut and paste here for reference:

The wallet contains a pool of queued keys. By default there are 100 keys in the key pool. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.

To summarize, as long as less than 100 addresses are ever used per wallet (and you know this wasn't overridden at the command line because your program can actually understand the berkley db format used in wallet.dat), you can have multiple copies of the wallet on several client instances, and all of them can send and receive bitcoins. However you are opening a pandora's box, because even with deep inspection of wallet contents, you can not avoid the potential for monetary loss by users when arbitrarily copying around wallets.

I will spell out the chronology of how you directly can cause and enable losses (by the way, this somewhat applies to wallet backups too):

1: I have a wallet with 200 unique addresses and corresponding private keys for re-sending those addresses' funds,
2: I let your utility copy my wallet to a USB stick,
3: I run the local computer version of bitcoin, press "generate new address", and receive bitcoins at it,
4: I run the portable usb version of bitcoin, press "generate new address", and receive bitcoins at it,
5: Now the seperate wallets are the only ones that can send their respective bitcoins,
6: Your program copies one of these wallets over the other one, and I lose the ability to send all the bitcoins that were at that address.

I hope your idea for a "wallet manager" isn't a copy command in a batch file that you ran through your BAT2EXE... I doubt it can understand the -datadir option I'm already using to frustrate trojans that are just as naïve.

Okay, now for the main attraction... I'm releasing PBC version 1.3!
I've created a Wallet Manager is open batch cause the guy above me is a *****, and yes I censored myself but you can count the stars and make a good guess! 
The Wallet Manager is made to copy your bitcoin client between your PC and Portable Bitcoin Client, in case I'm not the only one that has multiple clients with the same wallet...
So enjoy, and I'll think about actually taking his advice and re-coding the original bitcoin client to save in a local data folder, but I'm much better playing with my batch for now.. xP

Lol, it almost looked like you accused me... I was about to find me a moderator, record what I do to make this, then rub it in some faces.. 
Either way, I'm slowly working on increasing the usability with each version and I doubt everyone wants to code the batch each time. My little kit really "babies" it so an idiot could use it, hehe. And pst.. I used the same instructions to base the binary, bro.. Silly little wisecrack xD
Ah, okay, I'm done trolling you...  But seriously, I don't screw with your threads and people have already been scanning it, so what more do you want other than to make flame posts to merely raise your "post count"? 

This would be a more helpful and trustworthy thread if it was just instructions and no binary, i.e.:

How to make a portable bitcoin:
1. Copy bitcoin.exe to USB drive \bitcoin
2. copy bitcoin user directory contents to USB drive \bitcoin\data
3. run bitcoin.exe -datadir=.\data, or save this command as a bat file
4. don't lose USB drive

A real "creator of the portable bitcoin client" would just release a diff against the source code that changes the default directory. A binary would only be trustworthy if several people compile and get MD5 identical code, and the binary is hosted at a versioning URL unchangeable by the author.

Of course, there are already instructions, which should make you question the binary more: http://forum.bitcoin.org/?topic=809.0

Thanks for sharing the info, I was about to just delete the topic cause no one cared much for it lol.. 

I ran a virus/malware scan and its all clear for me.Hope this helps.If in doubt,either don't run it or run in a virtual machine or sandbox app.

Lol, there's your PM... I don't understand how a group of people can see two source codes and still think it's fake?
Simple, the above source code + batch compiler = program. 

Either post the source or PM it to me or this is getting locked.

what happens if you lose your USB drive? I am sure most people have lost one or two..

Regardless, post the source so that people are able to inspect and compile (and if they feel like it, improve/customize) it themselves. Not posting source code, however small, is a massive alarm bell.

Is it a rule of the forum that alternative clients must have source attached? If not then perhaps it should be.


BB.

Yeah, the code for the bitcoin launcher is batch, so it's very simplistic...

As stated above, I just convert the batch to exe and try to find ways to make it easier to execute.
I use a program that runs the batch file through UPX and a few other programs to make it what it is now, it makes the creation of it as easy as Pi. (Cause I hate Pie)
I mean, if it would make people happier, I could record myself showing the source code, compiling and all, but then what's the point? lol

sounds like a good idea, just need more safe checking into the code and reps from people.

Thanks!   
And yeah, I just updated it to 1.2 cause I got tired of the slow startup speeds... I made it more than twice as fast.. *happy face*
And hmm, win-rar? Sounds like it's worth looking into... And glad to see great minds think alike haha ^^