feat: send transfer

[fbwoolf]

This PR begins to add support for signing a transaction to transfer btc.

Questions:

1. Should the name be more specific to token transfer?
2. The proposed PR in Connect use a BtcRecipient so an app could send an array of recipient, is that also preferred here? Ref PR: feat: add open btc transfer hirosystems/connect#285

[kyranjamie]

Thanks for the PR @fbwoolf.

I wonder if we should call this something more generic, like send btc, as it includes the broadcast as well? cc/ @janniks

[fbwoolf]

Changing to sendTransfer from spreadsheet ...w/ params as an array of recipient objects. starting singular as discussed.

[fbwoolf]

@kyranjamie ran into this locally until I added a name and version to the package.json: wclr/yalc#101

Just a heads up for testing local dev changes.

EDIT: This didn't seem to totally work either. 🤔 ...just experimenting so not important. I ended up just using the console to trigger it rather than finishing the button in the test-app right now.

[janniks]

Looks good, but yeah I think a recipients array would probably be best and work for both cases

[fbwoolf]

@kyranjamie I think we decided starting singular in our tech mtg was best, did I not understand that correctly? Should I change here?

[janniks]

We can start off singular as well, with the potential problem of maybe a wallet needing to support a changed standard once there is something more official / agreed upon. 🤷🏼‍♂️

[fbwoolf]

We can start off singular as well, with the potential problem of maybe a wallet needing to support a changed standard once there is something more official / agreed upon. 🤷🏼‍♂️

Yeah, prob best just to do the array if we know that is ultimately what we want... @kyranjamie, anything I am missing/not remembering correctly about why we can't/shouldn't?

[kyranjamie]

LGTM