Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Armory with new links #1235

Closed
wants to merge 1 commit into from

Conversation

achow101
Copy link
Contributor

Armory is no longer developed by ATI. Its website, bitcoinarmory.com, is down and is no longer Armory's website. The source code is now maintained by goatpig.

This PR changes the website link to point to the release download location (since a new website has not yet been set up) and the source code link to point to goatpig's repository.

@Cobra-Bitcoin
Copy link
Contributor

I've removed Armory from our wallets page (8f6dfb3).

It will take some time for this new fork maintained by goatpig to establish itself as trustworthy. We'll review the situation in 3 months.

@achow101
Copy link
Contributor Author

Why would it be not trustworthy? Goatpig was one of the primary developers of armory; now he is the maintainer of the project.

@sunnankar
Copy link
Contributor

@Cobra-Bitcoin Bitcoinarmory.com is operational with download links and signed hashes for Version 0.93.3 which was already widely considered trustworthy.

Version 0.94 is still being (1) actively developed by goatpig, who has maintained the public version of the branch for about two years, and (2) semi-actively developed by the original developer etotheipi who has focused most of his attention on the non-public enterprise branch over the last two years. Consequently, all of the removal commits should be reverted.

@achow101 achow101 mentioned this pull request May 19, 2016
@BitPopCoin
Copy link

Armory is the best wallet available

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants