|
If you have an image of the entire USB stick, you are don't need anything like DMA.
What I meant by DMA was "get a map of the entire device and read it like any piece of memory". Basically a raw scan of the underlying bytes. Your file recovery process is still relying on some form of reconstruction of the containers file structure. There could be blind spots that a raw read would not miss.
Since you are looking for a specific byte string, this method would yield better results.
|
|
|
|
I'm getting alot of these with 5a84857: Traceback (most recent call last):
File "/home/user/BitcoinArmory/qtdialogs.py", line 8386, in wltTableClicked
self.setAddrBookTxModel(self.selectedWltID)
File "/home/user/BitcoinArmory/qtdialogs.py", line 8283, in setAddrBookTxModel
self.addrBookTxModel = SentToAddrBookModel(wltID, self.main)
File "/home/user/BitcoinArmory/armorymodels.py", line 1337, in __init__
addressBook = self.wlt.cppWallet.createAddressBook();
File "/home/user/BitcoinArmory/CppBlockUtils.py", line 1949, in createAddressBook
def createAddressBook(self): return _CppBlockUtils.WalletContainer_createAddressBook(self)
RuntimeError: can't connect socket ....when using the Send dialog (triggered by either Coin Control button or Choose Address button). Subsequently, other parts of the GUI throw this error too (not necessarily with the same traceback). Looks like the DB is not running. |
|
|
|
Opened a code review of the PR in Github, please go over it. Just submitted a PR to get the OSX build going again. There are two problems that still need to be addressed.
Merged #170, don't know the status on #151 ------------- Anything else I haven't mentioned is still being reviewed/fixed. |
|
|
|
Would it be possible to pull in my PRs on Github so as to get the Mac build going again and various other small things?  Thanks. Did #143 #148 #161 and #168. Other PRs need longer reviews and testing so that will have to wait till I get back. To all people who submitted PRs, please rebase on top of dev. Thanks. |
|
|
|
This time again. Looking for people willing to build and try the dev branch. Changes can be seen here: https://github.com/goatpig/BitcoinArmory/blob/dev/changelog.txtThis still needs some polish, but it's getting to the point where it's about done. SegWit is currently hardcoded disabled on mainnet, and enabled on testnet. Due to the newly introduced script types, I strongly suggest people test this on testnet first before moving the mainnet.Here is a list of what's missing/known as buggy, so that the testers can focus on what is supposed to be fully functional: - The initialization progress bars are wacky atm. - Still have to add a slider to the auto fee byte feature - no .conf for the client yet - have to redo the path settings GUI to go with the .conf addition - still missing BIP9 rules detection to enable/disable SW - armoryd is fubar I'll be away from Friday to Monday, so don't expect me to reply to bug reports until then. Happy testing! |
|
|
|
|
Start ArmoryDB from the terminal and let it initialize. If it crashes post the terminal output here. If not, start ArmoryQt.py on top of it
|
|
|
|
|
Turn off auto bitcoind in File -> Settings, start BitcoinQt manually, then try start Armory. Report here.
|
|
|
|
Has anyone made a way of simply installing Armory on a Raspberry pi? Unfortunately I can't run it on my 32-bit Windows tablet, as Armory have dropped support for that (64-bit required), so I bought a Raspberry Pi model 2 to use with Armory. However, nothing I try seems to work. I've used Raspbian, and tried installing it via the standard package installer, and for some reason it doesn't install. I tried electrum as well... and it just worked as it should). I've downloaded the files for Raspberry Pi from Armory's web site & unzipped them, and none of them work. I've seen tutorials like this one that make me think I'm mad because I'll need to take a course in heath-robinson computing just to install a flipping bitcoin wallet! I've tried a script that someone helpfully made to automate this and other processes ( https://github.com/aussiehash/Bitcoin-for-SBC), but this doesn't work on the latest Raspbian. Can anyone please explain how it's so hard to install an app on a device when Armory even publish files that are supposed to work on the very device I have? Any help would be greatly appreciated. My RPi setup works just fine. You need to elaborate on the errors you are seeing. |
|
|
|
Hello
I have rebuild and rescan.. but same problem.... I try again...
Same Problem I delete everithing and Install from scratch....
Hello
I have the same problem...
In cmd I see this when I creat the db new
ERROR - 1486617937: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486617937: (..\BlockDataMap.cpp:80) header has: xxx
-ERROR - 1486617937: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-INFO - 1486617937: (..\DatabaseBuilder.cpp:268) parsed block file #278
-DEBUG - 1486617937: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1486617947: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 682.79s
-INFO - 1486617947: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-ERROR - 1486617947: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486617947: (..\BlockDataMap.cpp:80) header has: xxx
-ERROR - 1486617947: (..\BlockDataMap.cpp:81) block yields:xx
-ERROR - 1486617947: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
how I can fix this... or better question how I get my BTC :-(
regards
Create your own thread, post both armorylog.txt and dbLog.txt in full. |
|
|
|
What you need is the hash of your utxos (covered by DB_BARE), and potentially the hashes of the supporting transactions (supported in DB_FULL).
|
|
|
|
Still missing that one tx hash. Any other ideas how to resolve it?
Maybe there is a way of asking DB to process specified hash?
No, it failed to record the filter during the build. You'll have to rebuild & rescan, although at this point I'd recommend you use DB_BARE. |
|
|
|
There is a piece of code called 'resolve missing tx hashes ' - could it be that in case tx hash is missing above function can return unexpected return value? Why resolving missing hashes is needed anyway?
Because keeping an exhaustive list of resolved hashes is too demanding for full nodes. What you need is the hash of your utxos (covered by DB_BARE), and potentially the hashes of the supporting transactions (supported in DB_FULL). That's a narrow dataset that can be processed easily on its own (hence the targeted tx hash resolver). Second thing to consider is transaction size - tx am missing has 26 inputs and thirteen outputs, tx hash is 1cc0cd0ed909dc5f7fa75e34821c7909a6daac7db47687a41c4dfea7d4f17972
any ideas why armorydb could have problems with serializing/unserializing/storing it?
The DB isn't missing the transaction (you wouldn't see its effect on your tx history otherwise). What it is missing if the hash resolution. Transactions are not keyed by their hashes. You need to convert tx hashes in outpoints to actual block height and tx id. This is the piece the DB is missing. Try to run the DB with --rescanSSH and see if that fixes it. If it fails, post dbLog.txt. |
|
|
|
|
Btw, you need to put ArmoryDB behind an http daemon to do this in the first place.
|
|
|
|
|
This is a known bug, I'll fix it for 0.96
|
|
|
|
|
Delete your db, start from scratch.
|
|
|
|
|
Armory devs have typically refrained from commenting on non technical aspects of consensus debates. I do not intend to break that pattern.
Voting with code is more sensible in this space, and my dev branch currently hosts a fully fleshed SegWit feature set.
|
|
|
|
|
The client is the python GUI.
Post dbLog.txt
|
|
|
|
The 'Fake Wallet' is something you created yourself, it's not part of Armory's wallet management process. It is fair to assume it is not related to your actual wallet. You don't need your whole wallet file to get your coins back, only the first 100 bytes or so. You can check out the header format here: https://github.com/goatpig/BitcoinArmory/blob/master/armoryengine/PyBtcWallet.py#L1943What you would need is DMA access to the USB key, that you want to scan for this string: and check the following 100 bytes or so. As for how to do it, you'd have to find software that let's you do that or write the code yourself. If your wallet has enough coins in it, it's worth your time. |
|
|
|
|
Do you see new blocks hitting the DB? What about the client?
|
|
|
|
|
ArmoryDB never gets to connect to your node. Check your firewall, it needs to be able to connect to 127.0.0.1:8333.
|
|
|
|
|
Show Posts
