I am working on sign() now, it will be ready soon (at least for pubkeyhash)


On Sat, Mar 15, 2014 at 7:58 PM, Matt Faus <notifications@github.com> wrote:

> In Transaction.js:
>
> > + *      remainderAddress: null,
> > + *      fee: 0.001,
> > + *      lockTime: null,
> > + *    }
> > + *
> > + *  Amounts are in BTC. instead of fee and amount; feeSat and amountSat can be given,
> > + *  repectively, to provide amounts in satoshis.
> > + *
> > + *  (TODO: should we use uBTC already?)
> > + *
> > + *  If not remainderAddress is given, and there is a remainderAddress
> > + *  first in address will be used. (TODO: is this is reasoable?)
> > + *
> > + *  TODO add exceptions for validations:
> > + *  out address - ins amount > out amount - fees < maxFees
> > + *  + more?
>
> What do you think about adding the ability to pass in a private key so
> that the transaction returned is ready to be transmitted immediately? The
> examples listed in the top-level README.md show how to create a
> transaction and then send it out via peer-to-peer, but it does not show how
> to sign the transaction so that it will actually be accepted.
>
> Although, it might make sense to make sign() a separate API.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/bitpay/bitcore/pull/160/files#r10637090>
> .
>



-- 
Matías Alejo Garcia
Skype/Twitter: @ematiu
Roads? Where we're going, we don't need roads!