https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L819
https://github.com/goatpig/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L88
Topic: Armory client/server? (Read 530 times)
Is there a way to have armory-qt point to armorydb that is on another machine or is armory-qt hardcoded to use localhost? I also notice there isnt a "-help" flag for ArmoryDB. Is there any documents on it to see what it supports or would I have to read the source code to do that?
I am assuming that armorydb does what I ask about in the OP
Yes. No TLS though, I'll be using BIP151 for encryption in a later version.
Quote
Will be looking at 0.95 change log later on because if something like this is already done then I could just have this thread ignored.
https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt#L18
Thanks. I guess I've overlooked it when upgrading. I am assuming that armorydb does what I ask about in the OP or is it something else?
Quote
Will be looking at 0.95 change log later on because if something like this is already done then I could just have this thread ignored.
https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt#L18
Hi,
I been using Armory for a little over a year and something I been wondering is why dont armory have some type of split so one side is the server (armorydb?) and the other is the client (armoryqt) that can connect to the server via tcp/tls (maybe using rpc like bitcoind)? I think it been discussed several times, but having armory as a client that can connect to the server in a way to perform transaction, check balances, create wallets, etc., would, imho, allow more flexibility with how it can be used (if used wisely), and create some portability. I could me missing something with 0.95 release but just a thought/question I had. Will be looking at 0.95 change log later on because if something like this is already done then I could just have this thread ignored.
I been using Armory for a little over a year and something I been wondering is why dont armory have some type of split so one side is the server (armorydb?) and the other is the client (armoryqt) that can connect to the server via tcp/tls (maybe using rpc like bitcoind)? I think it been discussed several times, but having armory as a client that can connect to the server in a way to perform transaction, check balances, create wallets, etc., would, imho, allow more flexibility with how it can be used (if used wisely), and create some portability. I could me missing something with 0.95 release but just a thought/question I had. Will be looking at 0.95 change log later on because if something like this is already done then I could just have this thread ignored.
Jump to: