It seems to me that your security features don't solve the core problem: bad server scripting.
bitcoind, when configured correctly, is a reasonably secure daemon. Using the config, you can block all traffic thats not from localhost or 127.0.0.1, and add basic authentication requirements. The problem, it seems, is in the server script, allowing access to the bitcoin daemon to any random script kiddie that passes by. Even by using time-release transactions and coldstorage wallets, anyone who knows what they're doing (if your scripts are insecure) can just add their transaction to the stack, to be processed later.
bitcoind, when configured correctly, is a reasonably secure daemon. Using the config, you can block all traffic thats not from localhost or 127.0.0.1, and add basic authentication requirements. The problem, it seems, is in the server script, allowing access to the bitcoin daemon to any random script kiddie that passes by. Even by using time-release transactions and coldstorage wallets, anyone who knows what they're doing (if your scripts are insecure) can just add their transaction to the stack, to be processed later.
What are your thoughts on this design?
https://codebounty.hackpad.com/Bitcoin-Transaction-Architecture-ptLNqGP0tnq