Latest posts of: goatpig

Show Posts
Pages: « 1 ... 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 [185] 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 »

3681

Bitcoin / Armory / Re: Armory in Fedora 18

on: July 14, 2014, 10:41:54 PM

Quote from: Carlton Banks on July 14, 2014, 10:07:40 PM Did we ever get an rpm package for Armory? I'm not seeing anything on bitcoinarmory.com Oh boy... not quite there yet, wait till we get a Debian package out first o.o

3682

Bitcoin / Armory / Re: Some questions!

on: July 14, 2014, 07:38:57 PM

Quote from: TimS on July 14, 2014, 07:13:18 PM 3. The primary concern would be that it's not part of your paper backup, only in digital backups created after you imported the private keys. You can add imported private keys to a paper backup, but you'll end with extra pages. Also you cannot be under the assumption than an already existing paper backup will cover newly imported private keys, which implies you'll have to print new ones every time.

3683

Bitcoin / Armory / Re: Armory and laptop sleep mode?

on: July 14, 2014, 07:08:36 PM

Long story short: don't use sleep mode.

3684

Bitcoin / Armory / Re: Armory - Discussion Thread

on: July 13, 2014, 11:50:34 PM

Quote from: teste on July 13, 2014, 11:25:31 PM Hi, some noob questions: 1- Is it possible to know if a standard btc address (that start with 1) is part of a multisignature transaction? by looking bitcoin network. 2- Why Armory only generate one multisign address (that start with 3)? Is it possible create a new address for each transation? (privacy) Thanks 1) Yes. Armory supports that in 0.92. Keep in mind that for P2SH transactions, only the TxIn carries the full script, so you cannot see the relation to the given address until the multisig output is spent 2) You use N addresses to build one multisig script. You would need another N addresses to create a different one. The current version of lockboxes only support the single logic. With the new wallets and BIP32 support, we'll add an option to use wallets instead of addresses, so that each lockbox is created from address X out generated from each of the N wallets. This will allow lockboxes to behave like deterministic wallets, all backed by a single root key, if you wish it so.

3685

Bitcoin / Armory / Re: Armory closing at 99% scanning transaction history

on: July 08, 2014, 01:55:59 PM

We ignore the bad data. The issue occurs when the header is present, but the block data is missing or damaged. By this I mean there is a single instance of the incomplete block data, or that it is outright missing. There are a few instances of damaged blocks that have a second, proper copy available further down the blk file, but there are also cases where the only instance of a given block data is damaged. I dont think Bitcoin Core verifies more than the headers.

3686

Bitcoin / Armory / Re: Armory Crash After updating to version 0.91

on: July 08, 2014, 01:51:54 PM

Quote from: Flow on July 08, 2014, 01:06:53 PM Same crash with 0.91.2 (and the latest git version) here, 0.88 seems to work just fine. Was there any feedback from your ticket? Which version are you updating from? 0.90 DB is not compatible with 0.91.2

3687

Bitcoin / Armory / Re: Error Import Multibit Private Key

on: July 07, 2014, 09:02:20 PM

Ill get someone to look into it.

3688

Bitcoin / Armory / Re: Error Import Multibit Private Key

on: July 07, 2014, 06:04:59 PM

Did you copy in the time stamp as well?

3689

Bitcoin / Armory / Re: Armory closing at 99% scanning transaction history

on: July 04, 2014, 07:59:58 PM

Our priority at Armory is security. We do understand the need for better user experience but not at the cost of our utmost priority. If you reread my post you'll see we have a long term solution, but it will come in due time, because other features have to get there first to allow this solution to implemented. It isn't stand alone solution that we could implement over night or we would have done so obviously. You're talking about using paper wallets, but they too are inconvenient, until the point when BIP32 is widely implemented. There are also a lot more clients out there that choose user experience over security. We have a role to fulfill before we can get the user experience up to acceptable levels. By far Armory is not considered the easiest nor the most welcoming wallet, but some people think this is an acceptable trade off for the added features, and here we are today. What you are trully experiencing is a software niche that hasn't just matured yet. Obviously we would like to get rid of all these quirks. As a matter of fact my work for the past 4 months has been towards implementing long term scalability and stability fixes. The problem you describe cannot be dubbed as a "leveldb" error. This is a symptom of your local copy of the blockchain. Simply put, while the you appear to be running a full node, you actually aren't, as you are missing block data. Let's put aside the consequence that has on the network, and focus on Armory. Armory requires a full node to function. Implementing a long term solution to this issue would require a shift in paradigm. That can't be addressed lightly nor quickly. Also consider that most of the codebase is still etotheipi's work: about 100k lines of code over 2 years. He had to make some choices to ensure Armory functions overall. You can't just spend 6 month to fix scanning issues that can be effectively decentralized. Consider that the earlier versions of Armory didn't even have a DB: you had to fully scan the blockchain at every load. Now that 5 developers work full time on Armory, we have the resources and talent required to implement long lasting solutions to all the bugs and quirks, while adding new features. Quote Have you thought of maybe packaging offline transaction feature as a separate product? It does look like the only unique and useful feature that the other apps don't do better than armory You can copy the signed Tx and broadcast it with another service, sure.

3690

Bitcoin / Armory / Re: Using Armory with real world entropy

on: July 04, 2014, 12:10:01 PM

I flip burgers for real life entropy. If the burger falls out of the pan, it counts as a 0, otherwise it's a 1. Each burger can only be flipped once. It maybe long and noisy, but it's delicious!

3691

Bitcoin / Armory / Re: Armory Issue - Won't Broadcast

on: July 03, 2014, 11:13:38 PM

How much fees are you paying and how big is the transaction? You realize this would entirely easier if you created a support ticket and attached your log file. https://bitcoinarmory.com:8443

3692

Bitcoin / Armory / Re: Using Armory with real world entropy

on: July 03, 2014, 09:09:20 PM

You're on the right track so far. There isn't a public seed per say. Address N+1 public and private components are derived from address N and a scalar which is created by hashing address N's public key and the chaincode. The chaincode is an HMAC of the root key: https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L2941 You can read the derivation code here: https://github.com/etotheipi/BitcoinArmory/blob/master/cppForSwig/EncryptionUtils.cpp#L681 https://github.com/etotheipi/BitcoinArmory/blob/master/cppForSwig/EncryptionUtils.cpp#L757

3693

Bitcoin / Armory / Re: Using Armory with real world entropy

on: July 03, 2014, 06:14:39 PM

Original seed is 256bits. If you know some Python it's rather easy: https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L1914 You can use that call to convert 128bits of entropy to an Armory backup string. Do it twice and you have created you own root key that you can then plug in the restore wallet function to create a wallet file out of it.

3694

Bitcoin / Armory / Re: Armory closing at 99% scanning transaction history

on: July 03, 2014, 06:05:43 PM

Quote from: bto4630 on July 01, 2014, 01:08:01 AM Quote from: goatpig on February 15, 2014, 03:27:56 PM Botched block in the DB. Usually rebuilding the Armory DB is enough. Worst case scenario you'll have to delete your copy of the blockchain and redownload it Why doesn't this worst case scenario excite me at all? Thing is like 30 gig. I have to say that this bug has been there from the very beginning and somehow it's still not mitigated in any way. Reference bitcoin client has no issues with it, but somehow armory cannot handle it. Why? I call it bs. It's very sad how otherwise functional client suffers from such usability problems. Bitcoin Core checks for blocks THEN writes them to disk, and doesn't bother to verify they were written correctly, rather relying on its LevelDB database. On some occasions, that results in botched blocks. And yes, Bitcoin Core will fail to read these botched blocks if asked to. Armory depends on the raw files for its blockchain data, this is when those botched blocks get in the way. You also can't access Bitcoin Core's DB since LevelDB is set to lock it at process level. We could hack around that but that's too demanding, will impact stability, and reflects an underlying issues with your copy of the blockchain, which frankly you should fix. The long term solution which to be introduce after supernode and the new wallet format will be blocks over P2P. Quote from: btchris on July 03, 2014, 02:30:11 PM A big thanks to Armory for helping to find this bad RAM! If it weren't for all of the double and triple checking in the Armory code, this could have gone undetected for months, and who knows what I could have lost!! Thanks!!! Well, there are redundancy checks in place for the crypto data, and more on their way with the new wallet format, so while unstable hardware will give you a bad experience, it won't outright lose you coins.

3695

Bitcoin / Armory / Re: Is my armory ready

on: July 02, 2014, 08:10:22 PM

You can check Armory's top reported block against BitcoinQt's top block or an online service like Blockchain.info Then it's a matter of creating your wallet, making a backup and testing it.

3696

Bitcoin / Armory / Re: Bitcoind.exe has stopped working

on: June 29, 2014, 09:28:35 PM

It's --satoshi-datadir It would be entirely easier to figure out your issue if you created a ticket and attached your log file with it.

3697

Bitcoin / Armory / Re: Updating createTxFromAddrList

on: June 27, 2014, 07:55:49 PM

I havent worked with this part of the code, however you're obviously not providing enough data for your intended operation. You can't go from hash160 to pubkey, you have to provide the pubkeys as well, as TxIns need the pubkey to verify the signature. Also, what branch did you pull?

3698

Bitcoin / Armory / Re: Armory - Discussion Thread

on: June 27, 2014, 05:33:02 AM

Quote from: le_Ministre on June 26, 2014, 06:00:28 AM Hi guys, i have a bug in Armory and this is annoying cuz im just waiting for a transaction now. Armory Version : 0.91.2 x64 Windows 7 What i see first is Armory disconnect / Reconnect every 5 second. I check on the web and i found some people with the same issue, but in majority of time they repair it with adding memory or get a faster hard drive. In my case its not the problem, i have 32Go of Ram and two SSD Hard-drive in RAID 1. When i check the log file this is an example of what is see : 2014-06-25 23:02 (INFO) -- ArmoryQt.py:5672 - Dashboard switched to fully-online mode 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull1 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Online" 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull2 2014-06-25 23:02 (INFO) -- ArmoryQt.py:5552 - Dashboard switched to auto-InitSync 2014-06-25 23:02 (WARNING) -- ArmoryQt.py:4919 - Called updateSyncProgress while not sync'ing 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Offline" 2014-06-25 23:02 (INFO) -- ArmoryQt.py:5672 - Dashboard switched to fully-online mode 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull1 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Online" 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull2 2014-06-25 23:02 (INFO) -- ArmoryQt.py:5552 - Dashboard switched to auto-InitSync 2014-06-25 23:02 (WARNING) -- ArmoryQt.py:4919 - Called updateSyncProgress while not sync'ing 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Offline" 2014-06-25 23:02 (INFO) -- ArmoryQt.py:5672 - Dashboard switched to fully-online mode 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull1 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Online" 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull2 2014-06-25 23:02 (INFO) -- ArmoryQt.py:5552 - Dashboard switched to auto-InitSync 2014-06-25 23:02 (WARNING) -- ArmoryQt.py:4919 - Called updateSyncProgress while not sync'ing 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon 2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, Stat So i tried a couple of thing to try to understand the bug, but this just give me more question When i reboot my computer and just run Armory everything working fine. But if i start Google Chrome and go On Gmail, Armory Disconnect I do not understand but i can reproduce the bug like that. <iframe width="560" height="315" src="//www.youtube.com/embed/Q8Vve_VbvL8" frameborder="0" allowfullscreen></iframe> Link: http://youtu.be/Q8Vve_VbvL8 The wallet don't disconnect only on Gmail, this is just an example. When i have a lot of program open the wallet bug to. If i just restart the computer start Armory and do nothing he stay connected for some hour, but when i start app he start disconnecting. After reproduce the bug a couple of time the Wallet connection start spiking. Connect / Disconnect every 5 Sec. Here a Link to my Full log with the Spiking bug : http://pastebin.com/e0X0Ts4w Thanks in advance for your help Sounds like a connectivity issue with BitcoinQt. Add this to your bitcoin.conf, see if that helps Code: addnode=127.0.0.1

3699

Bitcoin / Armory / Re: Armory - Discussion Thread

on: June 25, 2014, 07:50:18 PM

Quote from: Rampion on June 24, 2014, 08:53:50 AM Two questions: a) any plans to make available an offline bundle for Ubuntu 12.04.4? b) are the offline bundles for 10.04 deprecated? Should we update our offline systems to 12.04? Alan is out of town so I'll try to fill in on these a) Yes, we should have this ironed out by the next release, which is soon btw b) I dont remember the exact details but this what happened: We used urllib3 for the overhauled announce system. We then realized most users won't have it so we decided to bundle urllib3 with the installers. Im not sure about how it unfolded from that point onwards since I wasn't involved with this part of the development, but the best solution we had resulted in dropping Python 2.6 support, which is what 10.xx ships with. Of course, that lib is for online Armory, and could be entirely disabled for offline bundles, however that would require modifying the release process some more, which we aren't sure we want to delve in for now. So there's no definitive answer to this question, yet. Ideally, we want to keep supporting older OS for at least offline Armory, such as 10.xx and XP, but only if doesn't come at the cost of ridiculous development efforts. The best way for you to avoid all this uncertainty would be to upgrade, indeed.

3700

Bitcoin / Armory / Re: Armory Issue.

on: June 19, 2014, 05:57:41 PM

Browse to your Armory datadir (C:\Users\myusername\AppData\Roaming\Armory) by default, and delete the databases folder.

Pages: « 1 ... 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 [185] 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 »