[WAL-1471] Add support for sponsored transactions

[Ivan-Mahda]

Purpose

_Describe the purpose of the pull request, link to issue describing the problem, etc.

Changes

All changes I have at the moment

Checklist

• My code follows the style of this project.
• The code compiles without warnings.
• I have performed a self-review of the changes.
• I have documented my code, in particular the intent of the
  hard-to-understand areas.
• (If necessary) I have updated the CHANGELOG.

CLA acceptance

_Remove if not applicable.

By submitting the contribution I accept the terms and conditions of the
Contributor License Agreement v1.0

• link: https://developers.concordium.com/CLAs/Contributor-License-Agreement-v1.0.pdf

• I accept the above linked CLA.

[soerenbf]

I would suggest applying the changes suggested here, but otherwise it looks good to me and works with the example.

Great job! 🥇

[soerenbf]

Is there a good reason to have the type as an argument as well? It's used in sendTransaction to give better type information with regards to which payload is supported for a transaction type. In the case of the SignableTransaction the transaction type is already available in the payload of the transaction.

Suggested change

	type: LaxNumberEnumValue<AccountTransactionType.Transfer>,
	payload: SignableTransaction
	payload: SignableTransaction

See

• Signable.payload
• Payload.type

[soerenbf]

Would change to

Suggested change

	type: AccountTransactionType,
	payload: SignableTransaction
	): Promise<string> {
	const response = await this.messageHandler.sendMessage<MessageStatusWrapper<string>>(
	MessageType.SendSponsoredTransaction,
	{
	type,
	accountAddress,
	payload: stringify(payload),
	}
	);
	transaction: SignableTransaction
	): Promise<string> {
	const response = await this.messageHandler.sendMessage<MessageStatusWrapper<string>>(
	MessageType.SendSponsoredTransaction,
	{
	accountAddress,
	transaction: stringify(Transaction.toJSON(transaction)),
	}
	);

[soerenbf]

And consequently

Suggested change

	const sponsorResponse = await submitPayloadToSponsor(
	AccountAddress.fromBase58(currentAccountAddress),
	Transaction.toJSON(transaction)
	);
	console.log('sponsorResponse', sponsorResponse);
	return provider
	.sendSponsoredTransaction(currentAccountAddress, 3, sponsorResponse)
	.then((sig) => alert(JSON.stringify(sig)))
	.catch(alert);
	const sponsorResponse = await submitPayloadToSponsor(
	AccountAddress.fromBase58(currentAccountAddress),
	Transaction.toJSON(transaction)
	);
	const sponsoredParsed = Transaction.signableFromJSON(sponsorResponse);
	console.log('sponsorResponse', sponsorResponse);
	return provider
	.sendSponsoredTransaction(currentAccountAddress, sponsoredParsed)
	.then((sig) => alert(JSON.stringify(sig)))
	.catch(alert);

[soerenbf]

And here

Suggested change

	const sponsorResponse = await submitPayloadToSponsor(
	AccountAddress.fromBase58(currentAccountAddress),
	Transaction.toJSON(transaction)
	);
	console.log('sponsorResponse', sponsorResponse);
	return provider
	.sendSponsoredTransaction(currentAccountAddress, 27, sponsorResponse)
	.then((sig) => alert(JSON.stringify(sig)))
	.catch(alert);
	const sponsorResponse = await submitPayloadToSponsor(
	AccountAddress.fromBase58(currentAccountAddress),
	Transaction.toJSON(transaction)
	);
	console.log('sponsorResponse', sponsorResponse);
	const sponsoredParsed = Transaction.signableFromJSON(sponsorResponse);
	return provider
	.sendSponsoredTransaction(currentAccountAddress, sponsoredParsed)
	.then((sig) => alert(JSON.stringify(sig)))
	.catch(alert);

[soerenbf]

Suggested change

	- Added support for Sponsored Transactions handling. With new method `sendSponsoredTransaction` in wallet-api.
	## 2.7.1
	- Added support for Sponsored Transactions handling. With new method `sendSponsoredTransaction` in wallet-api.