http://libbitcoin.dyne.org/doc/
I also have Python bindings and a C wrapper in development:
https://github.com/genjix/libbitcoin-c-wrapper/blob/master/examples/fullnode.c
Topic: How to get started developing bitcoin installed apps on Mac (ie unix-based) (Read 1162 times)
June 14, 2013, 05:56:32 AM
June 13, 2013, 08:22:18 PM
A similar way you would build an app on linux...
But your question, is not really OSX specific...... perhaps if you ask it in a non- OSX context you would get more replies.
But your question, is not really OSX specific...... perhaps if you ask it in a non- OSX context you would get more replies.
June 13, 2013, 10:13:56 AM
I'm rather surprised that I've gotten no replies to this message at all, not even to say it's a stupid question, or the wrong topic or "that's been answered many times". If I've erred in posting it, I would like to know why so I don't do it again.
Thanks
Thanks
June 08, 2013, 04:56:09 PM
I am building out a set of programs that together provide the Collateralized ID functionality I wrote up in this blog post a couple months ago: http://joecascio.net/joecblog/2013/03/25/collateralized-identity-using-bitcoin-to-suppress-sockpuppets/
I have a basic idea of how I think it should be built, but I'd like the input of folks here so I might avoid going down any twisty little passages to nowhere.
I would very much appreciate some suggestions on the best way (best = easiest, most secure, uses python) to implement a completely separate wallet file on a Mac (for starters) for which I can write very specific rule code for how spending should choose output addresses. A separate wallet is needed because it's extremely important to have control over what addresses outputs are drawn from. The historical blockchain record of Latch bitcoin address balances is key to the Collateralized ID concept.
So, should I build bitcoind and run it so I can use the JSON-RPC mechanism to talk to it from a django web app or native app? Or should I try to use JSON-RPC on some random miner server out in the network? Should I continue with the django web appr and/or plan to develop a separately installed native app to create and manage these separate bitcoin addresses?
Thanks in advance,
Joe Cascio
I have a basic idea of how I think it should be built, but I'd like the input of folks here so I might avoid going down any twisty little passages to nowhere.
I would very much appreciate some suggestions on the best way (best = easiest, most secure, uses python) to implement a completely separate wallet file on a Mac (for starters) for which I can write very specific rule code for how spending should choose output addresses. A separate wallet is needed because it's extremely important to have control over what addresses outputs are drawn from. The historical blockchain record of Latch bitcoin address balances is key to the Collateralized ID concept.
So, should I build bitcoind and run it so I can use the JSON-RPC mechanism to talk to it from a django web app or native app? Or should I try to use JSON-RPC on some random miner server out in the network? Should I continue with the django web appr and/or plan to develop a separately installed native app to create and manage these separate bitcoin addresses?
Thanks in advance,
Joe Cascio
Jump to: