Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a way for the advanced transaction builder to communicate with WalletConnect for signing #191

Open
rkalis opened this issue May 28, 2024 · 1 comment

Comments

@rkalis
Copy link
Member

rkalis commented May 28, 2024

No description provided.

@mr-zwets
Copy link
Member

mr-zwets commented Oct 2, 2024

this is what the signTransaction interface of BCH WalletConnect looks like

signTransaction: (
  options: {
    transaction: string | TransactionBCH,
    sourceOutputs: (Input | Output | ContractInfo)[],
    broadcast?: boolean,
    userPrompt?: string}
) 
=> Promise<{ signedTransaction: string, signedTransactionHash: string} | undefined>;

( see https://github.com/mainnet-pat/wc2-bch-bcr )

So the main way the transactionbuilder/cashscript could help is by constructing the sourceOutputs object in the required format

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants