Topic: Armory - Discussion Thread - page 39. (Read 521749 times)

Yes, that's what I had thought; or, equivalently, someone selling the BTC and donating the funds. If we could find people willing to do the exchange without charging (I'm sure we could find a few, maybe not 20), then the only fees would be external: BTC/fiat conversion (if any), fiat-to-fiat processing fees (probably quite low), etc. Still, better to reward those who accept BTC or begin accepting it for this - a 4 BTC (~$2,480) reward for setting up a free account should be enough for many charities to bite.

(I was just using it as a source/list of some eligible charities, but now that you mention it...) We could give to some of these charities through Humble Bundle. It would depend on what charities are supported by the bundles available at the time (not counting their Store, which has a fixed donation percentage).

E.g. the current list is: Red Cross, Action Against Hunger, First Book, IndieCade, SFWA (Science Fiction and Fantasy Writers of America) emergency medical fund. Giving one bitcoin would almost certainly put us on the top contributors list of whatever bundle is bought, and so can also serve as a bit of advertisement for Armory/Bitcoin (and the matcher(s)?).
We could also give to Humble Bundle (which is what your post suggests, as I'm interpreting it), but I agree with your points on that, and I see them as a business, not a charity - so no.

I assume you mean, setup with a bitcoin-accepting third-party who can donate the equivalent amount of cash, in order to expand the list to accept any donation targets, not just those accepting BTC...?

It's an option, but I like your comment about rewarding those who already accept BTC.  Also, we'd probably pay a fee to whatever third-party, which makes it even less attractive.

Humble Bundle is a good one, but I say that only because I'm personally a fan of Humble Bundle.  They were early entrants into the Bitcoin scene, and ATI has donated to them before.  Not sure if they should be part of the promotion though -- we'd like to support charities that have wide appeal and Humble Bundle only connects with a portion of the Bitcoin space (i.e. only the bitcoiners who play games).  I'm still happy to entertain them depending on how many options we have and how much in donations we ultimately decide to match.

This could be enough incentive to get charities to start accepting bitcoin donations. All of the charities that came to my mind not already on your list don't seem to accept bitcoin, even though they can do it for 0 fees through BitPay. Here are some (AFAIK apolitical) charities that maybe we could add to the list (some already take bitcoin donations in the form of donations through Humble Bundle...although it's probably fiat by then):
American Red Cross https://www.redcross.org/
Linux Foundation https://www.linuxfoundation.org/
charity: water http://www.charitywater.org/
Child's Play http://www.childsplaycharity.org/

What about paying the BTC to a trusted third party, who will donate the equivalent money to the charities?

In anticipation for the 0.92 release with multi-sig and simulfunding, we would like to offer up to 10 BTC worth of donation matching as a demonstration (and advertising) of the utility of Armory's new simulfunding features.  However, we cannot do this without a list of bitcoin-accepting charities or entities that are apolitical (i.e. making donations to something like wikileaks would be considered controversial, and out of the question).  We need ideas for who we can provide donations to.  Open-source projects are an excellent target since we are an open-source company ourself!

The process will probably look like this:

• Armory Technologies, Inc (ATI) will create 20 promissory notes of 0.5 BTC each, four to each of the 5 donation targets
• ATI will post all 20 prom notes (and descriptions) in a public location for people to browse
• Anyone who is willing to donation 0.5 BTC (knowing that it will be matched), will use the multisig menu to "merge promissory notes".  They will import our note, and then add their own for sending 0.5 BTC from one of their wallets.
• The user will sign the resulting 1 BTC transaction and will send it to us. (knowing it's not valid unless we also donate our 0.5 BTC)
• ATI will confirm that our 0.5 BTC is being sent with someone else's 0.5 BTC (or multiple people, if they coordinate).
• ATI will sign and broadcast the simulfund tx.  The donation target will receive 1.0 BTC

If all promissory notes are matched, it will be a combined donation of 20 BTC across some number of charities or projects.  I'd like to collect a list of potential donation targets, and then narrow it down to 5-10.  Don't want to have too many and dilute the effort.  Here's some ideas:

• Bitcoin Foundation
• Electronic Frontier Foundation
• Let's Talk Bitcoin webcast (Adam Levine, et al)
• XKCD Web Comic  (not exactly a charity, but who doesn't love his work? http://xkcd.com/538/)
• Cryptocat
• Freenet
• LibreOffice
• Linux Mint (this is my primary OS, so I'm a bit biased towards them!)
• The Tor project

Great. Knowing that I need to just upgrade is better than suspecting that something was broken.

Maybe I didn't see it because I never clicked on "Offline Transactions" on the latest dev version. I clicked on "Send Bitcoins" and selected an offline wallet. When I do click on
"Offline Transactions", the popup does appear. (FYI: I virtually never click "Offline Transactions" on the online instance of Armory because the workflow doesn't go that way)

Yes, in order to accommodate multisig transactions, the whole format changed.  There should've been a popup that explained that to you when you click on "Offline Transactions" on the latest dev version.  The old format was insufficient for handling multi-sig spends as well as simulfunding transactions.  There is no clean way to convert them.  We have always tried to maintain backwards compatibility, but it was just not possible this time.

Did something change recently in the Armory dev branch that changed the format of unsigned transactions such that an offline 0.86.3 can't recognize them any more?

there is a sshfs port for OSX

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.

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

Configuring networking-related things is not something I have a problem doing

I have run Armory and bitcoind on separate machines before, when both machines were Linux. I'm trying to help someone do it with an OS X Armory, and I was stuck not knowing the OS X filesystem quirks.

I am very much interested in this as well.
I would like to move bitcoind to a (local) server, running 24/7. My plan was to have a second, local bitcoind on my client pc, which syncs with the server from time to time. But Armory directly using the server' bitcoind via nfs and network would be much nicer!

Ente

Theoretically this should work, as Armory uses the bitcoin rpc calls for the part of the communication that is not related to the blockchain-files. The bitcoind by default does not accept external rpc connections, but can be configured this way: https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File. However, I don't know if there is a setting in Armory, that lets you point the rpc calls to another host. So either it would be necessary to setup a local port redirection (with SSH for example) or to change Armory's source.

Nevertheless, I would like to know about your (or from others) experiences with this setup.

I don't know what exactly you plan, but I know that Armory talks to bitcoind directly as well. It doesn't just use its blockchain files, but does all network-related things via bitcoind. So I am somewhat sure you can't run Armory on a machine with no local bitcoind.
Sorry if I understood your plan wrong. And maybe there's a way to connect to bitcoind non-locally as well, at least I remember it used to not be possible earlier.

Ente

Update: Building on Yosemite is possible when using the Xcode 6 hack I mentioned. I was able to start the version of Armory that was built. I wouldn't want it to be my daily driver, though. I've spotted a couple of issues that probably aren't my responsibility to fix. I'll keep an eye out as various packages are updated to support Yosemite.

(I should emphasize that this is separate from running on Yosemite a copy of Armory built on a pre-Yosemite version. That, as best I can tell so far, is totally fine.)

Thank you.

Default location for mainnet: ~/Library/Application Support/Bitcoin/blocks
Default location for testnet: ~/Library/Application Support/Bitcoin/testnet3/blocks

Where would Armory expect to find the blockchain files on OS X (and by "where" I mean the path where I would mount that directory via /etc/fstab)?

Situation is I want to run bitcoind on a separate linux machine and share the appropriate directory via NFS.

Figuring out how to mount NFS shares in OS X is the easy part, but I don't know where OS X puts things in its directory structure.

I solved it by removing and purging the previous bitcoin-qt install.  Then removing plus purging the Armoury install and also deleting the .armoury folder left behind.  Then reinstalling Armoury and letting it choose to download the bitcoin core client.  The problem I had was that I read I needed to install the bitcoin core client and let it fully update before starting Armoury for the very first time.  When I'd have been better off installing Armoury first and letting it choose to download the bitcoin core client.  Anyway after downloading the blockchain now three times it looks to be working.

Hello. I have some good news for the Mac users out there. As some of you know, there have been some random crashes that have plagued the 0.91 releases. As I suspected, it appears that at least some of it was due to a Qt issue. It looks like a proper fix finally came together last month. Once I ported the fix over to Armory, I banged on Armory pretty hard for over an hour. No crashes, unlike before, when I could trigger a crash within 20-30 min. at the most. I can't promise that this is the magic bullet. Tests so far look pretty promising, though.

Anyway, the fix is in the devel tree now. I believe it'll also be in the next 0.92 test build (0.91.99.9, I think). I'd like to request that everybody give it a spin. Again, no promises. I just want to see how users react, and see if some other Armory changes have fixed an unrelated crash that OS X users have reported and I've been unable to reproduce. Note that there will be some very minor GUI glitches. I'll get to them ASAP.

Thanks for your patience! We really are working hard to make sure that all users - Windows, Linux and Mac - have the same experience with Armory. Unfortunately, some things are beyond our control and require a little patience.

P.S. I need to confirm this but, for bonus points, you should be able to build the devel tree Armory on the Yosemite preview builds out there. You may have to apply a hack by downloading an Xcode 6 preview and renaming it to "Xcode" in /Applications first. If it works, cool. If not, well, I'm trying.