Armory 0.93.3 with BIP62 compliance

[twebit]

It won't load with the armory generated bitcoin.conf only with the p2pool config that I have.

I had in the armory generated config
rpcuser=generated_by_armory
rpcpassword=long password

but it won't load with that
but it will load with this...

listen=1
gen=0
server=1
daemon=1
rpcport=8332
rpcconnect=127.0.0.1
rpcallowip=192.168.1.12
rpcuser=bitcoinrpc
rpcpassword=AJacKm5v8MHFBU1vvHjznhAiy3MckM8jPMDiX3grbpc5
maxconnections=30
upnp=0
mintxfee=0.00005
minrelaytxfee=0.00005
disablewallet=1

Something has changed somewhere.

How do I get armory to generate that secure bitcoin.conf like it did originally?

[1715380207]

1715380207

[1715380207]

1715380207

[1715380207]

1715380207

[1715380207]

1715380207

[1715380207]

1715380207

[goatpig]

So that's fixed for me but wonder why it would work in linux and not in windows?

Every issues I have seen on Win10 had something to do with permissions. I guess they tightened the user isolation. I should upgrade to 10 at some point...

How do I get armory to generate that secure bitcoin.conf like it did originally?

That's a feature for auto bitcoind only. Armory only uses the RPC to recover status data from bitcoind when it manages it. It won't bother if you manage Qt yourself.

[trev]

Critical Bug Fix: "bitcoin:" URI handling of Multisig/P2SH addresses:
The code that handles clicking on a "bitcoin:" link outside Armory was improperly handling Multisig/P2SH addresses, and would prefill a valid but incorrect address.

I diff'd the 93.2 v.s. 93.3 source code to find the bug fix for the URI issue.
I can't see any change that is obviously related to it.

There is a change in jsonrpc_listunspent() at armoryd.py:462 where ".getOutPoint()" has been removed.
462c461
<             curUTXODict['txid'] = binary_to_hex(u.getOutPoint().getTxHash(), \
---
>             curUTXODict['txid'] = binary_to_hex(u.getTxHash(), \

Is this the fix for the URI bug?

In jsonrpc_listaddrunspent() the identical code is used at line 556.
Should that line be patched in the same way as line 462 ?

[goatpig]

Is this the fix for the URI bug?

No

In jsonrpc_listaddrunspent() the identical code is used at line 556.
Should that line be patched in the same way as line 462 ?

No

[Roy Badami]

Is 0.93.3 going to be put up on the website?  Currently the downloads link still seems to point to 0.93.2.

roy

[goatpig]

Is 0.93.3 going to be put up on the website?  Currently the downloads link still seems to point to 0.93.2.

roy

Not sure about that, I'll ask around.

[Roy Badami]

Armory 0.93.3 with BIP62 Released

Download links below, but as always, please use the secure downloader within Armory under "Help"-->"Update Software" or on the Announcements tab on the main screen.

More out of curiosity than anything else, but is the secure downloader actually working at the moment?  For me, it complains that it hasn't seen an update in months, and won't show me anything recent.  But I self-built, so maybe something broke.

[Stroto]

Well I have an issue with the new armory.

Sometimes when I make a tx and get change back in the same wallet the change appears as separate tx between the transactions. Not a real problem ofcourse, however the change is also not subtracted from the address so it shows as double. This prevents to make further transactions until the tx are confirmed. In those cases the change address is the same as the output address.

Probably an example makes it clearer:

Wallet A has 0.10 BTC which is bought of 1 transaction

A transaction is made of 0.02

Now the wallet shows two transactions:

tx1 -0.02 BTC
tx2 +0.0799 BTC

total value 0.16998

It shows like that until all tx have confirmed and before confirmation when you try to make a transaction (of the 0.0799 that should be able to spend) it can't broadcast the transaction. When the tx get confirmed the tx (tx2 +0.0799 BTC) disappears from the list.

It does not happen with all the tx just some.

[goatpig]

More out of curiosity than anything else, but is the secure downloader actually working at the moment?  For me, it complains that it hasn't seen an update in months, and won't show me anything recent.  But I self-built, so maybe something broke.

I don't think it is.

Sometimes when I make a tx and get change back in the same wallet the change appears as separate tx between the transactions. Not a real problem ofcourse, however the change is also not subtracted from the address so it shows as double. This prevents to make further transactions until the tx are confirmed. In those cases the change address is the same as the output address.

Armory won't let you spend incoming ZC, only ZC change. I'm aware of the ZC parsing bug (where it sometimes fail to figure out an output is actually change) and I have fixed that in the soon to come release, so you'll have to be patient.

[lemipawa]

For some reason, I cant download the 0.93 version last night, but instead I downloaded 0.92 version, would there be a problem with that in the future?

[achow101]

For some reason, I cant download the 0.93 version last night, but instead I downloaded 0.92 version, would there be a problem with that in the future?

Yes. It would produce high s signatures which would be rejected by the network.

[lemipawa]

For some reason, I cant download the 0.93 version last night, but instead I downloaded 0.92 version, would there be a problem with that in the future?

Yes. It would produce high s signatures which would be rejected by the network.

I'm using a netbook Samsung n150 but I tried to download the 0.93 version, it's not allowing me
Is there any work around on that?

[Newar]

I'm already in contact with support, but I'm wondering if other people experience Armory crashes too, shortly after "Organizing Blockchain" starts?
(Lubuntu 14.04)

[j1pvt]

Im on Core 0.10.0  and Armoury 0.93.2,
Mac OSX 10.10.5
Everything working fine,
Why would I need to update ? ?

[goatpig]

Long story short, you should update Core because you just should, and you should update Armory or you'll have trouble spending coins.

[cypherdoc]

Long story short, you should update Core because you just should, and you should update Armory or you'll have trouble spending coins.

what version of Core should we be on now?

[Holliday]

Long story short, you should update Core because you just should, and you should update Armory or you'll have trouble spending coins.

what version of Core should we be on now?

Err... uhh, don't you run XT or Unlimited?

[goatpig]

Long story short, you should update Core because you just should, and you should update Armory or you'll have trouble spending coins.

what version of Core should we be on now?

CLTV is activated (or should be soon, not sure), so 11.2 at least.

[cypherdoc]

Long story short, you should update Core because you just should, and you should update Armory or you'll have trouble spending coins.

what version of Core should we be on now?

Err... uhh, don't you run XT or Unlimited?

sure, all but one to run Armory.  you have a problem with that?

[Holliday]

Long story short, you should update Core because you just should, and you should update Armory or you'll have trouble spending coins.

what version of Core should we be on now?

Err... uhh, don't you run XT or Unlimited?

sure, all but one to run Armory.  you have a problem with that?

So you run a different client to make a statement but when it comes to actually using Bitcoin, you use Core.

I don't have a problem with that, I just think it's hilarious.

Edit: Oh... and to answer your question, you should use the latest version of Core and Armory.