Published on: 2012-06-14T20:00:57+00:00
On June 14th, 2012, Peter Vessenes emailed Gavin Andresen with a request to add a feature that would allow private keys to be provided at the command line with the signature, effectively turning the client into a wallet-less signature machine. Andresen agreed with the idea and suggested adding a third argument to support an array of private keys. This would enable the client to sign using only the given private key(s) and ignore the bitcoind wallet. The private keys would only remain in bitcoind memory for the duration of the RPC call.Peter subsequently submitted a feature request to allow private keys to be provided at the command line with the signature, enabling the client to function as a wallet-less signature machine. Meanwhile, Gavin Andresen has already submitted a pull request for an API implementation of low-level "raw" transactions. He is seeking feedback on the API and assistance in testing it.The key new method introduced in the pull request is the signrawtx method. It takes a raw transaction, signs as many inputs as possible, and returns the modified raw transaction with signatures. This API is primarily intended for people developing services on top of bitcoind rather than for command line usage. It is important to include appropriate transaction fees when using the sendrawtx method; otherwise, it is likely to fail. For more detailed information, the design document, pull request, and test plan can be found at the following links: - Design doc: https://gist.github.com/2839617- Pull request: https://github.com/bitcoin/bitcoin/pull/1456- Test plan: https://secure.bettermeans.com/projects/4180/wiki/Raw_Transaction_RPC_Test_PlanAdditionally, a list of all new RPC calls, along with their help output and example usage, is available.
Updated on: 2023-08-01T03:36:54.750439+00:00