Topic: Armory - Discussion Thread - page 102. (Read 521763 times)

Congrats on the round

Yes, it is redundant, but it the goal is to have Armory become more detached from bitcoin-qt/bitcoind.  There is no way to ultimately connect Armory to a remote Bitcoin-Qt/bitcoind instance unless it maintains its own DB.   Also, these first few versions are maintaining a full database, but the goal to create a lighter-weight version that doesn't duplicate all that data.  But the full implementation is easier, and solves the RAM problem, so it makes a great first step.

It's not out yet, so there's no new version yet.  Yes it is redundant, and it more than doubles the HDD requirements.  But it should considerably speedup startup, no more 15 minute waiting for Armory to load.  Maybe with this investment -1 can make a full bitcoin node replacement.

so the "2nd DB" is somehow different than the Bitcoin-qt DB?  sounds redundant.  does it double the HDD requirements?

i'm also not seeing any download links on the website for the new version.  am currently runnng 0.88.1 on mac os. 

looks like my 0.88.1 is already the latest version?

It is still dependent on bitcoin-qt, but it maintains a second blockchain database on your HDD instead of keeping it in RAM.  So it uses much less memory.  But it doesn't communicate with other bitcoin nodes, so it can't download blocks itself.

someone catch me up on what the new beta version does.

is it still dependent on and open Bitcoin-qt?  or is it standalone with it's own DB.  any significant differences otherwise with 0.88.1 on mac osx?

Congratulations Alan!  Great news.

Thanks everyone, and you too goatpig!  Your help was actually tremendous.  Just because I have full time people helping doesn't mean that we no longer will need help from the community!  We actually have already tried out your solution and it appears to take us much further than we got before!  So I'm glad you helped, and I think you deserve the 2 BTC.  Though, I just realized that your solution uses a very old version of LevelDB ... I haven't tried merging that project with the latest LevelDB, but we will need to do that eventually.



Check out armoryd.py.  After this next update, armoryd.py will be stable, and you can access everything that Armory GUI can do through python.  It's already setup as an RPC server, but of course it currently uses a lot of RAM, and additionally crashes on each blockfile split (about once a week).  For reference, I even have unit tests for blockfile splits, and they pass... but somehow it still crashes when run on the live network  I've already confirmed the new version doesn't suffer from this problem.  While you can use armoryd.py as an RPC server (a very minimal one), I'd actually recommend using it as a template for just creating your own armoryd.py which is fully customized for your use case.  Now that it will be stable with the next release, I'll spend some effort upgrading it with some more functionality, which will make it more useful both as a server, and as example code for modifying it yourself.

There is already programmatic access.  The c++ functions are neatly callable through python.

Thank you Kevin, and of course, Thanks, as always to Alan

Gratz on the investor, I hope armory will grow into an even better wallet software. I personally hope you'll implement a mod/add-on system to allow side devs to bing in their own small contribution.

I ended up helping at the very moment my help wasn't required anymore. Story of my life =P.

Congrats. Make sure Armory stays the best wallet. Oh and start a free T-Shirt promo! 

I love to see that you can seriously earn a living from your hobby now. All the best.

Have a warm welcome, Kevin!
Nice to have you here, looking forward for a lot of exciting stuff coming from you guys in the future! :-)

Ente

Mixed feelings. Both sides of those feelings probably pretty obvious. Disappointed we weren't donating enough to get the benefits of this deal done in a decentralized way. At any rate, can't wait to see what Alan & team can do! Good luck!

Right, you could have a "user" version for the general public and also a version for merchants, who pay for support.

The merchant version could do things like generate new public keys on the fly and track when payments come into those addresses.  That would mean monitoring potentially thousands of addresses.

It could also handle things like refunds.  Does the payment protocol do that?

It could also do the zero confirmation system.  This is where a merchant connects to 20-30 peers (and does things like make sure all the IPs are from different networks).  If a transaction is received on > 75% of peers and no double spend is received, then it is probably not a double spend.  Ofc, that is kind of the opposite of Armory, since it is probability based security, rather than maximum security.

Hello Alan,

Congratulations for your funding round and also for that other thing you are involved in in a few weeks time !
These are exciting times for you !

:-)

Jim

Yep, Alan will now be full time on Armory.  And so will at least two other folks as well.

Btw, I'm Kevin Bombino, one of the investors in the deal.  I just wanted to add my congratulations to Alan.  I'm thrilled to have the opportunity to support the project.

I doubt many people deserve it more, congrats!

What are the ideas for developing Armory as a business btw? Will everything remain open source? What are you guys planning on charging for? (I'm kinda hoping it'll be customer specific customizations ).

Wow.

Does that mean you are switching to full time work on the project (or were you already)?

Congratulations!  This is great news.