 Show Posts
|
|
Pages: [1]
|
Next version will run natively on OSX
On vera. J'ai des doubts. I'm feeling cynical these days regarding Armory and MacOs. Will it really work some day? It's Sep 2021, I have Bitcoin Core 0.21.1, and a new MBP (w/ intel processors). I get these sucky log messages: Service exited due to SIGKILL | sent by mds[96] |
|
|
|
That's correct... they are a completely different instruction set. However, the M1 Apples have a "Rosetta Translation" system that can run some x86_64 code: https://developer.apple.com/documentation/apple-silicon/about-the-rosetta-translation-environmentSo, Armory might still work on the M1-based laptops... but given that Armory and MacOSX were already somewhat problematic, you might be better using a virtual machine (running Linux or Windows)... or waiting until an M1 native build is released. Or just purchase one of the current MBP's that still have a bunch of intel chips before they stop offering them? |
|
|
|
I'm not aware of any workarounds. I also can't really do any work on finishing the port until the build system settles. So, short of using a VM, macOS users are SOL at the moment.
I currently have macOS Catalina 15.4, and an old version of Armory 0.96, and this works fine. I am now wondering if the new MBP's with their M1 chip (replacing intel) would somehow break Armory. It should make no difference to running Armory, no? ` |
|
|
|
Your transaction history is probably lagging behind. Post your logs for review.
Does my problem have something to do with running 0.96.3-991? I had to build this from source, and I have problems building 0.96.4 from source because /dupes has been deprecated in Homebrew --- so it would be nice if Doug could update the build instructions. Last I checked a month ago, the build instructions were fine. You may want to try the notes here. In particular, if you're using brew, python may now be equal to Python 3, which we don't want for now (uggh). You'll have to use brew to install python2 and run the build script using python2. In any event, a complete overhaul is still on my radar, and will probably be rolled out once we upgrade to Python 3 & Qt 5. I just have other, more pressing issues to deal with, unfortunately. EDIT: Someone else emailed me and confirmed that the directions for 0.96.4 are no longer valid. I'll update the directions for 0.96.5. For now, using the directions I posted should be fine, but if not, swapping out "Homebrew/dupes/zlib" with "Homebrew/homebrew-core/zlib" should do the trick. (Actually, I should probably just switch to "xz" for 0.97, since it doesn't require this silliness. Harumph harumph.) As I mentioned to you earlier, I did swap out Homebrew/dupes/zlib with Homebrew/homebrew-core/zlib. Things compiled fine until it hit issues with qt, saying it was unable to open a file. Anyway, I took goatpig's advice, wiped out the Armory database, and let it rebuild, and this solved the issue -- still in 0.96.3991. Yay! I don't think I want to risk updating to 0.96.4 until some of these issues seem resovled. I see that a lot of people are having trouble with it, and the version I'm using is working. I'm on a 2017 MacBook Pro, using Core 0.16.2, in case anyone else is having trouble with a Mac. Armory 0.96.3991 is syncing with the blockchain now, and all my coins are considered confirmed. Thank you so much, goatpig and droark! |
|
|
|
Your transaction history is probably lagging behind. Post your logs for review.
Does my problem have something to do with running 0.96.3-991? I had to build this from source, and I have problems building 0.96.4 from source because /dupes has been deprecated in Homebrew --- so it would be nice if Doug could update the build instructions. |
|
|
|
Core is running at the same time as Armory, correct? Is Core fully up-to-date?
Yes, I updated to Core 0.16.2, and it is fully up-to-date and running. I also just noticed that the block height, according to Core, is 536633 (currently), whereas my Armory wallet says at the bottom right that it is connected to 526111 blocks. Blockexplorer.com says it was included in Block 532676. This is past block 526111, so that explains that part. Underneath the information about what block it was included in, it says "LockTime 526111." Although it now has 3958 confirmations. What  is "LockTime"? And why is it at the same block height where my Armory Wallet stopped? OK -- I know what LockTime is now. So the question is why did my Armory wallet stop at this block height? |
|
|
|
Core is running at the same time as Armory, correct? Is Core fully up-to-date?
Yes, I updated to Core 0.16.2, and it is fully up-to-date and running. I also just noticed that the block height, according to Core, is 536633 (currently), whereas my Armory wallet says at the bottom right that it is connected to 526111 blocks. Blockexplorer.com says it was included in Block 532676. This is past block 526111, so that explains that part. Underneath the information about what block it was included in, it says "LockTime 526111." Although it now has 3958 confirmations. What is "LockTime"? And why is it at the same block height where my Armory Wallet stopped? |
|
|
|
Core is running at the same time as Armory, correct? Is Core fully up-to-date?
Yes, I updated to Core 0.16.2, and it is fully up-to-date and running. |
|
|
|
|
Hi All:
I am running Armory 0.96.3.991 on a 2017 MacBook Pro. The change from a relatively recent (weeks ago) transaction is listed as "unconfirmed", (and hence, not spendable), on my Armory startup page, down at the bottom, where "Maximum Funds," "Spendable Funds," and "Unconfirmed" are listed.
However, just checking this out with a block explorer -- I used blockexplorer.com, if it matters -- shows that the transaction has 3867 confirmations. I'm pretty sure that is enough confirmations to guarantee that the funds are mine, and that I can spend them if I wish, in principle. But I take it my Armory wallet will not allow me to spend the funds until it considers them "confirmed" (?)
Any ideas as to why this transactoin is not seen by my Armory wallet as confirmed, even after 3867 confirmations?
I'm running Bitcoin Core 0.16.0, if that matters.
|
|
|
|
When you go under /Applications/Armory.app/Contents/MacOS and run Armory ("./Armory"), what's the output?
In this case I get a pop-up with a yellow triangle holding an exclamation mark, and the message "The DB has returned the following error: DB version mismatch. Use another dbdir! Armory will now shutdown. ]Here's what I get in the terminal:/Users/julianthurston -->cd Aplicativos -bash: cd: Aplicativos: No such file or directory -->cd Applications -->ls Armory.app Chrome Canary Apps.localized Chrome Apps.localized -->cd Armory.app -->ls Contents -->cd Contents -->ls Dependencies Frameworks Info.plist MacOS Resources -->cd MacOS -->./Armory /Users/julianthurston/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py:2760: SyntaxWarning: import * only allowed at module level def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals): (WARNING) ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 2f68UeoBm (WARNING) ArmoryQt.py:2575 - Second wallet is more useful than the first one... (WARNING) ArmoryQt.py:2576 - Wallet 1 (skipped): /Users/julianthurston/Library/Application Support/Armory/armory_2f68UeoBm_.watchonly.wallet (WARNING) ArmoryQt.py:2577 - Wallet 2 (loaded): /Users/julianthurston/Library/Application Support/Armory/armory_2f68UeoBm_.wallet (WARNING) ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 36vn4TDvo (WARNING) ArmoryQt.py:2575 - Second wallet is more useful than the first one... (WARNING) ArmoryQt.py:2576 - Wallet 1 (skipped): /Users/julianthurston/Library/Application Support/Armory/armory_36vn4TDvo_.watchonly.wallet (WARNING) ArmoryQt.py:2577 - Wallet 2 (loaded): /Users/julianthurston/Library/Application Support/Armory/armory_36vn4TDvo_.wallet (WARNING) ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, YXdMHf2o (WARNING) ArmoryQt.py:2575 - Second wallet is more useful than the first one... (WARNING) ArmoryQt.py:2576 - Wallet 1 (skipped): /Users/julianthurston/Library/Application Support/Armory/armory_YXdMHf2o_.watchonly.wallet (WARNING) ArmoryQt.py:2577 - Wallet 2 (loaded): /Users/julianthurston/Library/Application Support/Armory/armory_YXdMHf2o_.wallet (ERROR) BDM.py:184 - DB error: DB version mismatch. Use another dbdir! --> |
|
|
|
I have been following this thread, and doing the various terminal gymnastics requested by goatpig and DRoark, and I too get hte BDM error!, after everything has loaded and scanned, apparently correctly....except, I get this BDM error! pop-up that won't let me DO anything with my wallets. I cannot access my wallets, even though all info is present on the screen, wallet name, amount of bitcoin held in wallet, and so on. Maybe I should BLOCK POP-UPS? I am quite frustrated. What happened? This is occurring with multiple users, so there must be something that changed on your end! I love you goatpig, don't be angry with me. Also, Hi goatpig and DRoark... long time no talk. |
|
|
|
Hi, I recently withdrew about 5btc into my offline Armory wallet about a week ago. Transaction was completed and I could see funds sitting there. I recently restarted Armory and the funds are now missing with the transaction history missing?
Is the blockchain fully loaded? |
|
|
|
I was making some transactions using offline Armory, and all of a sudden when I try to click the "Create Unsigned Transaction" button, nothing happens. It won't open the window letting me save the unsigned transaction. Is it because some of my coins were moved to change addresses? What am I doing wrong?
It sounds like you want to create a transaction with an offline full wallet that is "watching-only" on your online version of Armroy. When you are offline, you cannot create a transaction. The transaction should be created with Armory online, with your watching-only wallet. Then you take this to your offline Armory where the full wallet resides, and sign the transaction there. After the transaction is signed, you take the signed transaction back to your online Armory and the tx can then be completed. So when Armory is offline, you will not be able to create any transactions -- you can only sign them offline. |
|
|
|
I'm running 0.91.2 on Mac OSX and whenever I try to send coins it forces me to keep clicking coin control (in advanced mode) or donate to armory developers (in beginners mode).
My coins are basically stuck in my wallet cause every time i try to send, i can't get past the "wallet management" screen due to this bug. Any help?
Are you sure you can't fill in an address, the amount you want to send, and then click send? (And just ignore the "highlighted" buttons you mention above?) |
|
|
|
|
I submitted a "ticket" to them:
[i]I find it almost offensive that you require "paper" proof of residency. What is the purpose of this? I do ALL of my accounting and taxes in a digital format, and seriously doubt that I own a piece of paper for this purpose. Of course, I can just print one out. But I don't want to.
Bitcoin is a digital currency. Right? If you require me to print out a paper copy of some kind of "proof of residency," then I believe you do not quite understand digital currencies, and have simply set up this exchange in the hopes of making money from those who (largely) do understand and appreciate them. That's all fine, so long as you are secure, reliable, and have good customer support. But you should remove the (emphasized-in-bold-font) word "paper" from your requirement for proof of residency so as not to appear uneducated.
Regarding customer support, instead of simply offering "tickets," like a gaming server run by a teenager, you need live chat support backed by the ability to write a ticket.
Best wishes for you success![/i]
|
|
|
|
|
