Topic: [FEEDBACK REQUEST] Bitcoin cloud services - page 2. (Read 5515 times)
This would interest me providing I could do some sort of split private key arrangement.
Personally, I would never host Bitcoins on a machine I don't own the metal to.
I know trust is a concern many people in this community have, but it's a sliding scale with level of service/amount of trust. Sure, it's feasible to host your own metal somewhere, but you're still trusting the network providers, hosting company, hardware manufacturers, etc.
Would you be more interested if the machines were dedicated versus virtual? Or is "renting" a service completely out of the question for you, personally?
Personally, I would never host Bitcoins on a machine I don't own the metal to.
Bump for formatting update. Looking for all feedback, positive or negative! Lots of views, but no comments?
Trying to figure out if developers would make use of bitcoin cloud services:
The idea being to make it easier for developer to code something new without having to deal with the pain of setting up the client. The services would be designed to complement the model being done by other cloud providers, so you can string together services with some REST calls and Webhooks.
Feedback requested, whether positive, negative, or otherwise.
Thanks!
- pre-configured bitcoind VM
- up-to-date blockchain
- txindex=1 for full querying
- optionally enable an authenticated REST interface to interact with bitcoind, including "spend from address" functionality
- optionally enable Abe for blockchain viewing
- block/transaction notifications delivered via Webhooks
- high-availability, low-latency, geo-distributed REST-queryable blockchain cache
The idea being to make it easier for developer to code something new without having to deal with the pain of setting up the client. The services would be designed to complement the model being done by other cloud providers, so you can string together services with some REST calls and Webhooks.
Feedback requested, whether positive, negative, or otherwise.
Thanks!
Jump to: