Support Chained Transactions

[h0ngcha0]

The chained transaction might be signed by multiple signers, so the interface currently looks like this. Please let me know if we can improve it:

// Transfer fund from group 1 to group 2
const transferTxParams: SignTransferChainedTxParams = {
      signerAddress: signer1.address,
      destinations: [{ address: signer2.address, attoAlphAmount: 10n * ONE_ALPH }],
      type: 'Transfer',
      publicKey: signer1.publicKey
}

// Interact with dApp in group 2
const depositTxParams = await Deposit.script.txParamsForExecution(signer2, {
      initialFields: { c: transactInstance.contractId },
      attoAlphAmount: ONE_ALPH
})

// Build chained txs
const [transferResult, depositResult] = await TransactionBuilder.from(nodeProvider).buildChainedTx([transferTxParams, depositTxParams])

// Sign and submit both txs
await signer1.signAndSubmitUnsignedTx({ unsignedTx: transferResult.unsignedTx, signerAddress: signer1.address })
await signer2.signAndSubmitUnsignedTx({ unsignedTx: depositResult.unsignedTx, signerAddress: signer2.address })

[pragmaxim]

I cannot make sense of it as a newcomer, we sign the transfer with rootWallet and return PrivateKeyWallet.Random(group) which does not seem to hold any important information 🤔 How can we later use it to sign transactions? As we do signer1.publicKey / signer1.address

SOLVED: Sorry I understand now, it is a generator

[pragmaxim]

Please print the error cause it reveals the reason of failure :

  } catch (error) {
    throw new Error(`Failed to get signer, please restart the devnet due to : ${error}`)
  }

[polarker]

@Lbqds Please give a final review on this new feature, thanks!

[Lbqds]

LGTM 👍