Bitcoin Forum
December 12, 2019, 06:17:13 PM *
News: Latest Bitcoin Core release: 0.19.0.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 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 ... 231 »
  Print  
Author Topic: Armory - Discussion Thread  (Read 520955 times)
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 2394
Merit: 1133

Armory Developer


View Profile
January 16, 2014, 08:04:14 AM
 #3141

Can you PLEASE provide the download link? Or maybe update the download page via https://bitcoinarmory.com/download/

You need to address your issue with software update.. it's taking too long.

That's in the 0.91-dev branch on github. Still a few weeks until we release this officially. The team is in the process of fixing the known comon bugs in this branch.

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1576174633
Hero Member
*
Offline Offline

Posts: 1576174633

View Profile Personal Message (Offline)

Ignore
1576174633
Reply with quote  #2

1576174633
Report to moderator
bitpop
Legendary
*
Offline Offline

Activity: 2548
Merit: 1045


https://keybase.io/bitpop


View Profile WWW
January 16, 2014, 08:42:19 AM
 #3142

Every time I tried to send bitcoins, Armory crashes and it's rampant. Seriously, when are you going to fix it?! And every time it crash, it takes 20 minutes for bitcoin to scan transaction history - it's a fuking waste of time.

Are you using an older version of Armory that you create offline transactions from? The rescan on crash is fixed for 0.91

Can you PLEASE provide the download link? Or maybe update the download page via https://bitcoinarmory.com/download/

You need to address your issue with software update.. it's taking too long.

Maybe you should donate

Reputation  |  PGP  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
1FfmbHfnpaZjKFvyi1okTjJJu
Full Member
***
Offline Offline

Activity: 164
Merit: 100


Im not 1FfmbHfnpaZjKFvyi1okTjJJusN455paPH


View Profile
January 16, 2014, 11:10:32 AM
 #3143

Has anyone successful changed Armory's appdata path on windows?

From https://bitcoinarmory.com/about/armory-and-bitcoin-qt/
"If you do this, then you will need to start Armory with the exact same path in “–satoshi-datadir=C:\path\to\new\location“."

"–satoshi-datadir=C:\path\to\new\location" : ignores the path and scans the db to default
"-satoshi-datadir=C:\path\to\new\location" : error: ArmoryQt.exe: error: no such option: -s



bitpop
Legendary
*
Offline Offline

Activity: 2548
Merit: 1045


https://keybase.io/bitpop


View Profile WWW
January 16, 2014, 11:25:48 AM
 #3144

Has anyone successful changed Armory's appdata path on windows?

From https://bitcoinarmory.com/about/armory-and-bitcoin-qt/
"If you do this, then you will need to start Armory with the exact same path in “–satoshi-datadir=C:\path\to\new\location“."

"–satoshi-datadir=C:\path\to\new\location" : ignores the path and scans the db to default
"-satoshi-datadir=C:\path\to\new\location" : error: ArmoryQt.exe: error: no such option: -s





 --satoshi-datadir=F:\Bitcoin --dbdir=F:\Armory

Reputation  |  PGP  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
1FfmbHfnpaZjKFvyi1okTjJJu
Full Member
***
Offline Offline

Activity: 164
Merit: 100


Im not 1FfmbHfnpaZjKFvyi1okTjJJusN455paPH


View Profile
January 16, 2014, 11:49:45 AM
 #3145

Has anyone successful changed Armory's appdata path on windows?

From https://bitcoinarmory.com/about/armory-and-bitcoin-qt/
"If you do this, then you will need to start Armory with the exact same path in “–satoshi-datadir=C:\path\to\new\location“."

"–satoshi-datadir=C:\path\to\new\location" : ignores the path and scans the db to default
"-satoshi-datadir=C:\path\to\new\location" : error: ArmoryQt.exe: error: no such option: -s





 --satoshi-datadir=F:\Bitcoin --dbdir=F:\Armory

This worked.
bitpop
Legendary
*
Offline Offline

Activity: 2548
Merit: 1045


https://keybase.io/bitpop


View Profile WWW
January 16, 2014, 12:46:50 PM
 #3146

Has anyone successful changed Armory's appdata path on windows?

From https://bitcoinarmory.com/about/armory-and-bitcoin-qt/
"If you do this, then you will need to start Armory with the exact same path in “–satoshi-datadir=C:\path\to\new\location“."

"–satoshi-datadir=C:\path\to\new\location" : ignores the path and scans the db to default
"-satoshi-datadir=C:\path\to\new\location" : error: ArmoryQt.exe: error: no such option: -s





 --satoshi-datadir=F:\Bitcoin --dbdir=F:\Armory

This worked.

Thanks, the docs are fucked up. No clue where I even learned that.

Reputation  |  PGP  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 2394
Merit: 1133

Armory Developer


View Profile
January 16, 2014, 06:35:19 PM
 #3147

https://github.com/etotheipi/BitcoinArmory/blob/0.91-dev/armoryengine/ArmoryUtils.py#L45

You can see all the current active (and unactive) command line args here, with their associated help comments.

bitpop
Legendary
*
Offline Offline

Activity: 2548
Merit: 1045


https://keybase.io/bitpop


View Profile WWW
January 17, 2014, 12:27:07 AM
 #3148

https://github.com/etotheipi/BitcoinArmory/blob/0.91-dev/armoryengine/ArmoryUtils.py#L45

You can see all the current active (and unactive) command line args here, with their associated help comments.

Perfect

So there's 3 directories to be aware of.
And 3 connections, files, peer and rpc.

Reputation  |  PGP  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
QuantumQrack
Sr. Member
****
Offline Offline

Activity: 340
Merit: 250


View Profile
January 17, 2014, 02:16:47 PM
 #3149

So, I know the Armory developers are working on Trezor integration, etc.  But I was wondering if stealth addresses and CoinJoin via the Armory client are in any sort of planning stage?  Rather than doing these things manually, which is a hassle, it would be nice if it was EZ button type of implementation.

Appreciate all the hard work on Armory!
bitpop
Legendary
*
Offline Offline

Activity: 2548
Merit: 1045


https://keybase.io/bitpop


View Profile WWW
January 17, 2014, 02:39:35 PM
 #3150

So, I know the Armory developers are working on Trezor integration, etc.  But I was wondering if stealth addresses and CoinJoin via the Armory client are in any sort of planning stage?  Rather than doing these things manually, which is a hassle, it would be nice if it was EZ button type of implementation.

Appreciate all the hard work on Armory!

Coinjoin requires networking code which they avoid.

Reputation  |  PGP  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
Peter Todd
Legendary
*
Offline Offline

Activity: 1106
Merit: 1018


View Profile
January 18, 2014, 12:41:44 AM
 #3151

So, I know the Armory developers are working on Trezor integration, etc.  But I was wondering if stealth addresses and CoinJoin via the Armory client are in any sort of planning stage?  Rather than doing these things manually, which is a hassle, it would be nice if it was EZ button type of implementation.

Appreciate all the hard work on Armory!

I can't speak for the Armory devs, but one nice thing about implementing stealth addresses in Armory is that it already has the machinery to scan the blockchain; you could easily use stealth at the highest privacy level where any stealth tx that's sent could be going to you. (zero-filtering)

It's something to consider about Armory in general: because it can work so easily with a local full-node you always have excellent privacy with regard to the contents of your wallet. All the queries are local, so info on what coins are in your wallet never leaves your machine. That's much better than SPV clients like Android Wallet where every peer you connect to learns statistical info narrowing down your addresses to within about one in 10,000 or so, or Electrum which currently just tells peers what addresses are in your wallet.

Anyway, as something I myself would use, I'll offer a 1BTC bounty to get stealth address support in Armory. Contact me if you're interested in making it happen and we'll work out the specifics between myself and the Armory devs. (they're eligible too of course)

etotheipi
Legendary
*
Offline Offline

Activity: 1428
Merit: 1005


Core Armory Developer


View Profile WWW
January 18, 2014, 01:00:22 AM
 #3152

So, I know the Armory developers are working on Trezor integration, etc.  But I was wondering if stealth addresses and CoinJoin via the Armory client are in any sort of planning stage?  Rather than doing these things manually, which is a hassle, it would be nice if it was EZ button type of implementation.

Appreciate all the hard work on Armory!

I can't speak for the Armory devs, but one nice thing about implementing stealth addresses in Armory is that it already has the machinery to scan the blockchain; you could easily use stealth at the highest privacy level where any stealth tx that's sent could be going to you. (zero-filtering)

It's something to consider about Armory in general: because it can work so easily with a local full-node you always have excellent privacy with regard to the contents of your wallet. All the queries are local, so info on what coins are in your wallet never leaves your machine. That's much better than SPV clients like Android Wallet where every peer you connect to learns statistical info narrowing down your addresses to within about one in 10,000 or so, or Electrum which currently just tells peers what addresses are in your wallet.

I'm very interested in this feature.  It's just that it still sounds very theoretical at the moment.  I'm also concerned about how much computation it will be to track the addresses ... ECDH calculations aren't cheap.  I guess I'm still in a waiting mode, implementing other things while I wait for this to be ironed out (I don't have much to contribute to the discussion, though I have spent a lot of time thinking about how to get the same benefits without all the ECDH calcs).

Peter:  Btw, I'm working on P2SH support right now.  You will be able to test it on 0.91-dev in the next couple days.  In fact, it seems to be working right now, on the p2shout branch -- you can try it right now, though I wouldn't do anything other than testnet. 

As part of the update, I modified the PyTxDistProposal::createFromTxOutSelection() method to take any arbitrary list of script-value pairs, instead of just hash160 values.  Right now, it will error out if you supply it something other than an P2PubKeyHash or P2SH, but that could be modified locally to create a tx with any arbitrary output scripts.  As long as all the inputs are standard UTXOs, you can create such a tx and sign it no problem (have fun getting it mined, though).

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
po0kie
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
January 20, 2014, 11:19:08 AM
 #3153

Hi!

First of all: Amazing work done by Armory Dev's!

I am working with the Daemon (extending it at moment to support Tx Offline Signing, and Broadcasting)

And i got a Little problem at the moment, maybe some of the Devs can point me to the right direction to get it working.

The Broadcast is nearly ready to use in ArmoryD, the problem I got is:
New Transaction Requests  over the same SourceAddress  of the previous Tx  will fail until the BDM gets notified about Confirmations
from BitcoinD.

Its like he want to spent the same TxInputs and then the Tx will fail in Broadcast. I saw  ArmoryQT  maintaining a combinedLedger.
(appending ZeroConf Ledger Entries to the combinedLedger)
But I have not see any relation to the BDM with the combinedLedger (maybe i am missing something, Its the first Project i am touching python.)

Or How ArmoryQT get it working to not fail on next Tx’s when the previous Tx’s isn’t already +1 Confirmation?
It seems to me that ArmoryQt “makes in some way a manual sync” to be able to realize a next TX.

Any point to direct me where I can follow the needs?

Thanks!


bitpop
Legendary
*
Offline Offline

Activity: 2548
Merit: 1045


https://keybase.io/bitpop


View Profile WWW
January 20, 2014, 11:38:49 AM
 #3154

As far as I know armory doesn't use rpc like that, it reads the database natively and has its own parser which you could borrow

Reputation  |  PGP  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
po0kie
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
January 20, 2014, 12:17:16 PM
 #3155

I think all the needed stuff is in the ArmoryQT Heartbeat.
But I am not really aware which functions are necessary to be called to make it "temporarily sync" until new confirmations
arrive.

Or maybe I am totally wrong Smiley
etotheipi
Legendary
*
Offline Offline

Activity: 1428
Merit: 1005


Core Armory Developer


View Profile WWW
January 20, 2014, 05:08:55 PM
 #3156

Hi!

First of all: Amazing work done by Armory Dev's!

I am working with the Daemon (extending it at moment to support Tx Offline Signing, and Broadcasting)

And i got a Little problem at the moment, maybe some of the Devs can point me to the right direction to get it working.

The Broadcast is nearly ready to use in ArmoryD, the problem I got is:
New Transaction Requests  over the same SourceAddress  of the previous Tx  will fail until the BDM gets notified about Confirmations
from BitcoinD.

Its like he want to spent the same TxInputs and then the Tx will fail in Broadcast. I saw  ArmoryQT  maintaining a combinedLedger.
(appending ZeroConf Ledger Entries to the combinedLedger)
But I have not see any relation to the BDM with the combinedLedger (maybe i am missing something, Its the first Project i am touching python.)

Or How ArmoryQT get it working to not fail on next Tx’s when the previous Tx’s isn’t already +1 Confirmation?
It seems to me that ArmoryQt “makes in some way a manual sync” to be able to realize a next TX.

Any point to direct me where I can follow the needs?

Thanks!


poOkie, I'm not sure what exactly the problem.  It sounds like you might be running into the issue of making multiple offline tx and trying to sign them without first broadcasting one of them.  Armory currently can't handle this situation, and you will have to create-sign-broadcast a tx before you can create the next tx (you can create the next tx, though it will probably be invalid).

Btw, there's a script the in extras directory called "cli_sign_txdp.py" which has example code for you.  You may have found that, or may have already reimplemented it.  Just wanted you to see it.

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
po0kie
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
January 20, 2014, 06:38:55 PM
 #3157

Yeah thats exactly what I am doing.
I am creating a queue for pending Tx's

I Get tge first Item (when no other Tx is in Work)
create a unsigned -> pass it to another worker make it Signed -> and get back to the other woker to make the broadcast.
after the broadcast I get the next item in queue and so on.

It works if the queue waits to start with next item (to create unsigned) until it gets at least 1 confirmation then there is no problem
but if I get on to the next item to mak an unsigned (1 minute after previous broadcast) then this happens:



The exact error occurs here:
class PyTxIn(object):
   def __init__(self):
      self.outpoint   = UNINITIALIZED
      self.binScript  = UNINITIALIZED
      self.intSeq     = 2**32-1
      self.isCoinbase = UNKNOWN

   def unserialize(self, toUnpack):
      if isinstance(toUnpack, BinaryUnpacker):
         txInData = toUnpack
      else:
         txInData = BinaryUnpacker( toUnpack )

      self.outpoint  = PyOutPoint().unserialize( txInData.get(BINARY_CHUNK, 36) )
      scriptSize     = txInData.get(VAR_INT)
      if txInData.getRemainingSize() < scriptSize+4: raise UnserializeError

       #values: ? txInData.getRemainingSize() = 45
       # ? scriptSize + 4 = 95

it raises an UnserializeError.

It does not happen if I select another Address of the wallet.

It should be something with the txoutlist (staying out of sync)??


etotheipi
Legendary
*
Offline Offline

Activity: 1428
Merit: 1005


Core Armory Developer


View Profile WWW
January 20, 2014, 06:57:22 PM
 #3158

Yeah thats exactly what I am doing.
I am creating a queue for pending Tx's

I Get tge first Item (when no other Tx is in Work)
create a unsigned -> pass it to another worker make it Signed -> and get back to the other woker to make the broadcast.
after the broadcast I get the next item in queue and so on.

It works if the queue waits to start with next item (to create unsigned) until it gets at least 1 confirmation then there is no problem
but if I get on to the next item to mak an unsigned (1 minute after previous broadcast) then this happens:



The exact error occurs here:
class PyTxIn(object):
   def __init__(self):
      self.outpoint   = UNINITIALIZED
      self.binScript  = UNINITIALIZED
      self.intSeq     = 2**32-1
      self.isCoinbase = UNKNOWN

   def unserialize(self, toUnpack):
      if isinstance(toUnpack, BinaryUnpacker):
         txInData = toUnpack
      else:
         txInData = BinaryUnpacker( toUnpack )

      self.outpoint  = PyOutPoint().unserialize( txInData.get(BINARY_CHUNK, 36) )
      scriptSize     = txInData.get(VAR_INT)
      if txInData.getRemainingSize() < scriptSize+4: raise UnserializeError

       #values: ? txInData.getRemainingSize() = 45
       # ? scriptSize + 4 = 95

it raises an UnserializeError.

It does not happen if I select another Address of the wallet.

It should be something with the txoutlist (staying out of sync)??


Coincidentally, I just ran into a problem with this in another context.  It does seem that the new code sometimes fails to get the tx properly from TheBDM when the tx is not yet in the blockchain.  It should work, and has worked before (before 0.90), but it may have broken during the upgrade and I didn't notice it.  I will have to verify that the zero-confirmation transactions can be properly retrieved from TheBDM before they are mined.

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
po0kie
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
January 20, 2014, 10:32:49 PM
 #3159

Oh ok perfect. good to know, was getting crazy the last 3 days Smiley
Do You go to notify here on this thread when got news about the fix?
Do you think it will get fixed before release of 0.91? Or directly within 0.91?

Thanks!
etotheipi
Legendary
*
Offline Offline

Activity: 1428
Merit: 1005


Core Armory Developer


View Profile WWW
January 20, 2014, 10:40:41 PM
 #3160

Oh ok perfect. good to know, was getting crazy the last 3 days Smiley
Do You go to notify here on this thread when got news about the fix?
Do you think it will get fixed before release of 0.91? Or directly within 0.91?

Thanks!

Probably 0.91.

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Pages: « 1 ... 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 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 ... 231 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!