latest pro retina stock. instant open and scanning of blockchain took 3 minutes
guess i need to quit being lazy and get the parts for the offline system build put together
with the latest bitcoin-qt
looks be using 1.8 gb of ram not so bad
Oh, I didn't even realize that this packaging job is offline-bundle-ready! Since it's completely self-contained, you should be able to use it on a freshboot of an offline OSX installation. Cool! 3-minute blockchain scan is good! Are you using an SSD? |
|
|
|
|
Hmm... it takes 4-5 minutes on my OSX VM in VMware, with 4 GB of RAM. I wonder if maybe it's a caching problem? Weird.
Well now that I'm done with this, I'll finally be able to get to the persistent blockchain stuff. So RAM usage will drop, and full scans should only happen on the first sync, and during import/sweep. I have no idea how long it's going to take, but I do know exactly how I'm going to do it.
|
|
|
|
The only issue I had was the time, it start at 3 mintues it took around 30-40mins to load the blockchain.
Great work!
What's the system specs? 30-40 min is excessive.... |
|
|
|
I decided not to add other clients like Armory and Multibit since they require extra components like JRE and I preferred to keep this version as slim as possible.
If you think there are any more tools I should add or links to include I'd be happy to hear about them.
For reference, Armory is trivial to build in Ubuntu. It is five terminal commands: - sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil
- git clone git://github.com/etotheipi/BitcoinArmory.git
- cd BitcoinArmory
- make
- python ArmoryQt.py
It's not terribly large, either. The offline bundle has all dependencies included to run on an offline computer and is 25 MB. |
|
|
|
The latest release is still not working for me, and the log file is pretty much the same. What can I do?
Gah, I forgot about you. There should be more information in there this time. I added a bunch of good debugging output. Can you remind me what is wrong? And send me the log file again, just in case it did catch something new. Thanks for being so patient. I'll figure it out! |
|
|
|
I made a sticky to talk about backups: https://bitcointalk.org/index.php?topic=152151.0This is one of the main reasons people use Armory: you only need to backup one time, ever. Period. All your addresses are generated from the data on that paper backup. Every time you receive coins, it just gets the next address in the mathematical chain of addresses. All addresses are seemingly-unrelated unless they have your wallet. |
|
|
|
|
Yeah, that's more like it. 38 bytes is what I expect for compressed private keys:
0x80 + 32-byte private key + 0x01 + 4-byte checksum
The 0x01 indicates it's a compressed key, and the address is computed differently. In a way that Armory doesn't understand yet. Another thing that will be supported in the new wallet format when it's done.
I actually have a chunk of code in the import dialog that detects you put in a compressed private key, but apparently that is malfunctioning. I just tried it, and it gave the too-big error instead of telling you that it's a format Armory doesn't support yet. I'll spend a couple minutes looking for that.
|
|
|
|
|
I too believe that Mt.Gox failed at their "duty", but they really have nothing to do with the crash. At all. Get over it.
The Bitcoin bubble was driven by speculators. And hype. Media attention. Millions of people wanted to get involved and started pouring their money in. The price goes up and more people want to get in -- but the Bitcoin infrastructure isn't there yet. It doesn't actually support $3 billion in economic activity. The system simply corrected itself to a more-reasonable value, and Mt.Gox only made that correction a little more turbulent. But they didn't cause it.
Bitcoin isn't ready for mainstream. Personally, I'm looking forward to a little more stability in the system as people tune out for a bit and tune back in when it's actually ready. I agree that Gox "failed", but they failed their own business, not the Bitcoin system.
|
|
|
|
Done! I have a testing release, posted here. |
|
|
|
It finally works! Thanks again to higuys who debugged and polished his OSX build script, which makes building on OSX too easy. In fact, it was so easy, I did more than I had to and ended up breaking it. Whoops! But it's all sorted out now, and I've been playing around with it in my OSX VM. I can see that there's a lot of stuff that needs improvement, but it does appear to be very usable. I had to completely disable Bitcoin-Qt/bitcoind management, because there is no reliable way to get bitcoind, and I'm not sure yet if I want to run Bitcoin-Qt. I might have no choice... I used my online GPG to sign this just to have something. My offline system is not setup yet for certificate-signing OSX builds. But I have a feeling this will need some tweaking before v0.88-beta anyway. https://bitcointalk.org/index.php?topic=156250.msg1655941#msg1655941NOTES:- I got the icons working.
- Auto-bitcoind/bitcoin-qt is disabled. I may have to start bitcoin-qt instead and minimize it immediately. Anyone know how to start-and-minimize-immediately an OSX app, from the command line?
- Notifications are disabled completely. Apparently this solution does not play nicely with Growl. 0.5 BTC to anyone who figures out how to fix it!
|
|
|
|
|
I'm glad to see more Bitcoin exposure, but I'm not sure this is the best kind of exposure. Roger is a valuable contributor to the Bitcoin ecosystem, but in this interview he sounds like he drank to koolaid of the Bitcoin Cult. His fanaticism is a little over the top. It appeals to people on the Bitcoin forums, but not those who've never heard of Bitcoin before.
|
|
|
|
|
You have to switch to "Expert" usermode from the main menu, to enable "Coin Control" in the Send-Bitcoins window. It's because this is not a common operation at all and I don't need to confuse standard users with it.
Once you are in expert mode, you can choose addresses to send from. You can't choose individual coins, but if you use each address once, it's identical.
|
|
|
|
|
It's because that's not a standard private key format. In fact, I'm not sure what format it's in, because it's 36 bytes, and unless I did something wrong, it does not look like the last 4 bytes are a checksum. Therefore, Armory interpretted it as a 36-byte integer, which is clearly larger than that 32-byte integer shown there.
I'm not sure what's going on with that key...
|
|
|
|
I am trying to set up and use Armory with a hidden O/S with TrueCrypt for plausible deniability. (Armory offline is in the hidden O/S.) The problem I'm having is that I can't write to any other partitions except for the outer partition when I need to sign a transaction. This breaks the rule of plausible deniability because writing to the outer partition is registered by the unhidden O/S, not to mention you have to read the file and delete it which leaves in on the drive (although encrypted, but on the "less secure" side).
Any thoughts? The TrueCrypt forum guys sent me here wondering if Armory could be set up different to do transaction signs (like maybe through QR codes or something I can write down).
Cheers.
-Andy
I'm not sure I understand the problem. Can't the hidden OS read and write to a USB key? Does the inner O/S run at the same time as the outer OS? Sorry, I have no experience with this, so I need a little better background, first. QR codes will not be able to handle a significant number of transactions. I'd have to use some kind of QR-code movie in order to make it reliable. There's a lot of discussion about alternatives in this thread about offline alternatives. Do you think the inner OS can talk to a serial port without registering with the outer OS? That's a very solid solution, anyway. If not, maybe QR codes are the best solution. But can you access the camera "safely"? P.S -- DISCLAIMER: I do not endorse the use of Bitcoin in any way not consistent with laws in your (or any) jurisdiction! Please pay your taxes, and please don't do illegal stuff with Bitcoin, with Armory, or any of my advice! I claim no responsibility for your crimes or jail time! (but please believe me, I don't follow privacy==must-be-doing-something-illegal, this is for those who have such motives in reading this thread!). |
|
|
|
So I feel a little silly. After talking with higuys, and sending him my .bash_history of my failed attempts, we figured out that Red Emerald's instructions are actually conflicting somehow with his build. I thought I had to follow RedEmerald's instructions first, then do his, not realizing that he made his script pretty much full-service. - (1) Install XCode from the App store
- (2) Open XCode, go to Edit->Preferences->Downloads(Tab)->Command Line Utilities->Install
- (3) Install brew: ruby -e "$(curl -fsSkL raw.github.com/mxcl/homebrew/go)"
- (4) Install pip: sudo easy_install pip
- (5) Clone the repo: git clone git://github.com/etotheipi/BitcoinArmory.git; cd BitcoinArmory
- (6) Make it: make osx
- (6a) You'll have to type in your password, since the "make osx" script installs everything for you
- (7) Run it: ./osxbuild/Armory.app/Contents/MacOS/Armory
That's it! And it appears to work. The only problem I see so far is that the icon doesn't work, and notifications crash it. I am in the process of disabling notifications (and 0.5 BTC to someone who figures out how to run them without causing growl to segfault, or whatever is happening), and then I'm going sign the .app and add it to my testing release notification. Because there is no bitcoind for OSX, it's going to take me quite a bit of work to even get Bitcoin-Qt automated. I think for 0.88, I will be skipping that (disabled the option for auto-bitcoind), and OSX will run just like the previous versions. It's still better than nothing. Perhaps others can experiment with how to best find Bitcoin-Qt, run it, and then hide it. I'll have something posted soon! |
|
|
|
Did you really mean to post that very relevant picture in this thread? And if you think this is a ride, try a real crash! The price "crashed" down to what it was four days ago. How dramatic!  Indeed. I have suspected for a while that the run-up was a bubble, though I expected it to persist a bit longer. All this media attention came in only last week, and thought there was going to be another couple weeks of people pouring into the system. Maybe there still will be. But I'm not afraid of the price "reverting to the mean", only the ensuing media attention which going to cast it into a poor light. And it's partly justified -- people are going mental, and panicking, and our poor little infrastructure can't handle it! For reference... 2 months ago I was at about 2,000 downloads/month. Now I've gotten 2,000 downloads in the last 2-4 days! I'm also getting a lot more emails and postings about it. Obvioulsy no one else can respond to the emails, but I request some help responding to postings in the Armory subforum. I'm going to try to resist the urge to respond to these things immediately, and give others a chance to help me, first. I'm going to focus on coding  I don't think the Armory download volume is/was experiencing a bubble, since mostly only people who have done thorough research about bitcoin would be interested in it(many of the long-time bitcoiners I know still have no idea about the advantages of cold storage), it's a sign of growth of educated bitcoin userbase. I think that was the case before they changed bitcoin.org. Now, it is parallel to Bitcoin-Qt instead of an alternative you have to go hunting for. Granted, the description says "advanced", but I'm sure lots of people want to try it out anyway... There's just no other way to describe a 5x-8x increase in volume (bitcoin.org getting 5x-10x more volume and them featuring Armory next to Bitcoin-Qt). It's pretty awesome, but it makes these usability issues all the more pressing! |
|
|
|
I have a clean OS X 10.7.5 partition in this mac mini I'm using.
If it's OK with you not being 10.8 I can try what you said.
By all means take a shot at it. |
|
|
|
What is the status with respect to testing under MacOS? Should I build from source, and manage bitcoind/bitcoin-qt myself?
I ran into more problems with OSX than expected. I decided to start over from scratch, but decided I should focus on getting the Linux & Windows stuff out the door before then. With about 20k downloads per month for Windows, I decided the usability upgrades I have need to be top priority. I think I'm finally almost there. Probably tonight or tomorrow I'll take another shot at the OSX build. I promise it's coming! |
|
|
|
|
Show Posts
