Topic: The mining focus is bad - we need better clients ;) - page 2. (Read 2625 times)
OP: If you think we should/need this then get to building it. If you can't do this yourself then put together a solid business plan, recruit people and issue shares. Who knows, I might even throw some BTC your way.
Too much "should", "need", "we", too little "i've contributed", "come test my addition" etc.
Yes. Say that to all people needing something
I try to get "this thing" into my financial infrastructure - which just happens to be a little more complicated than "typical miner in his basement". More complicated like "multiple levels of security and different workstations where you can move moeny at the press of a button".
What about: Willing to pay for a company level solution.
Too much "should", "need", "we", too little "i've contributed", "come test my addition" etc.
Yes, provovative, but here is the problem.
The curent client is not only bad UI Wise, it also is unsafe and not controllable for an enterprise level application, and enterprise level is what you WANT and NEED. As in: you need to provide an infrastructure (or have one provided) that is programmed in a way to handle (a) million usd deposits with safety and (b) enterrise level authorization scenarios.
The following should be possible:
* Isolating a wallet level client and a node that works on transactions. More code = more attack surface, make my wallet smaller.
* separate authentication for outgoing payments.
* Read only access to wallet only after authorization, encrypt it yourself.
* Allow automatic distribution of wallet and keys between authenticated servers (to faciliate a key loss / wallet loss, which both are devastating scenarios).
* Provide an easy to use API to enter payment requests and get incoming funds. API should handle authentication and authorization.
* Provide automatic forwarding of funds to backup / store addresses. Money comes in,gets send to a separate address.
* Provide "accounts", not addresses. Addresses are arbitrary small. The software should be able to form logical accounts from those. Especially as addresses may be "one time use".
* Provide access to an external WORM space to handle keys. For example sending keys (private) over SERIAL CABLE (!) to another box. Point being: Serial cable is not network, so it is quite impossible to use as a standard attack vector, and the backup box would keep a log of all keys. Or... a printer If every private key gets printed out, a computer crash can not harm them. Been there, implemented somehting along these lines for an online payment provider years ago (every transaction goes to an audit computer via serial + is printed for later scanning in case of a total computer attack).
The end problem is: if I have 100.000 BTC somewhere stored and am an enterprise (and large values have to be possible) then right now I run a high risk setup. None of the normal provisions are in place that my bank gives me. Unless you want this totally to be a bank service (and finding a bank doing this is hard - banks are HEAVILY regulated) this means that the BTC handling is very insecure. And burying it in a vault somewhere is not practical if it is your operating capital.
My bank gives me a lot of features, from nice account statements to an API and a 4 eye principle acount (one person enters transfer, other person has to approove them) to make sure money is not "diverted". Money loss is also a high risk and now way too technical - with a lot of manual intervention.
The end idea should be / would be to have a system that can be installed as a small harware applicane (in a cluster of x) that servves are wallet server. This can then be secured highly (physically) and provides an API that is enterprise level, so my secretary handling my transfers does not run with my money
This, a separate node for processing (no ui needed) and at the end a friendly end user installable client are needed to get out of funny geeky space.
Don't count on services to take over - so far I know of not a single "exchange" adhering to minimal financial standards, and no virtual bank at all. And even then, at the end... it sould have t operate with a pretty bad infrastructure.
The curent client is not only bad UI Wise, it also is unsafe and not controllable for an enterprise level application, and enterprise level is what you WANT and NEED. As in: you need to provide an infrastructure (or have one provided) that is programmed in a way to handle (a) million usd deposits with safety and (b) enterrise level authorization scenarios.
The following should be possible:
* Isolating a wallet level client and a node that works on transactions. More code = more attack surface, make my wallet smaller.
* separate authentication for outgoing payments.
* Read only access to wallet only after authorization, encrypt it yourself.
* Allow automatic distribution of wallet and keys between authenticated servers (to faciliate a key loss / wallet loss, which both are devastating scenarios).
* Provide an easy to use API to enter payment requests and get incoming funds. API should handle authentication and authorization.
* Provide automatic forwarding of funds to backup / store addresses. Money comes in,gets send to a separate address.
* Provide "accounts", not addresses. Addresses are arbitrary small. The software should be able to form logical accounts from those. Especially as addresses may be "one time use".
* Provide access to an external WORM space to handle keys. For example sending keys (private) over SERIAL CABLE (!) to another box. Point being: Serial cable is not network, so it is quite impossible to use as a standard attack vector, and the backup box would keep a log of all keys. Or... a printer
If every private key gets printed out, a computer crash can not harm them. Been there, implemented somehting along these lines for an online payment provider years ago (every transaction goes to an audit computer via serial + is printed for later scanning in case of a total computer attack).The end problem is: if I have 100.000 BTC somewhere stored and am an enterprise (and large values have to be possible) then right now I run a high risk setup. None of the normal provisions are in place that my bank gives me. Unless you want this totally to be a bank service (and finding a bank doing this is hard - banks are HEAVILY regulated) this means that the BTC handling is very insecure. And burying it in a vault somewhere is not practical if it is your operating capital.
My bank gives me a lot of features, from nice account statements to an API and a 4 eye principle acount (one person enters transfer, other person has to approove them) to make sure money is not "diverted". Money loss is also a high risk and now way too technical - with a lot of manual intervention.
The end idea should be / would be to have a system that can be installed as a small harware applicane (in a cluster of x) that servves are wallet server. This can then be secured highly (physically) and provides an API that is enterprise level, so my secretary handling my transfers does not run with my money
This, a separate node for processing (no ui needed) and at the end a friendly end user installable client are needed to get out of funny geeky space.
Don't count on services to take over - so far I know of not a single "exchange" adhering to minimal financial standards, and no virtual bank at all. And even then, at the end... it sould have t operate with a pretty bad infrastructure.
Jump to: