Wallet-Specific Capabilities

This page defines wallet-specific capabilities that are not part of the common adapter baseline.

Use this page when you need to document:

• wallet-specific properties
• wallet-specific methods
• wallet-specific events

Purpose

The goal is to keep integration behavior explicit and predictable when different wallets expose different extensions.

Wallet capabilities documented on this page are not part of the common Adapter interface. They should be treated as wallet-specific extensions.

Binance Wallet (TRON)

signAndSendTransaction()

Sign a transaction and broadcast it using the Binance Wallet selected network in a single call.

signAndSendTransaction(
    transaction: Transaction
): Promise<{
    signature: string;
    txHash: string;
    transaction: SignedTransaction;
}>

Parameters

• transaction: The unsigned TRON transaction to be signed and sent.

Returned Value

{
    signature: string;
    txHash: string;
    transaction: SignedTransaction;
}

• signature: The transaction signature returned by Binance Wallet.
• txHash: The transaction hash returned after broadcasting.
• transaction: The signed transaction payload.

Example

const unSignedTransaction = await tronWeb.transactionBuilder.sendTrx(
    targetAddress,
    100,
    adapter.address
);

const { signature, txHash, transaction } = await adapter.signAndSendTransaction(unSignedTransaction);

console.log('txHash:', txHash);

Notes

• This method is wallet-specific and is not part of the common adapter baseline.
• It is useful when the wallet supports signing and broadcasting as one atomic interaction.
• If you need portable behavior across wallets, use the common signTransaction() flow instead.
• Fee behavior may vary across Binance Wallet clients and versions. Based on our tests with Binance Wallet iOS version 3.12, Android version 3.12.8, and extension version 1.11.1, this method could result in lower costs on some clients when the account did not have enough energy for contract-triggering transactions and similar operations, while no lower fee was observed on the extension.
• If your account already has sufficient energy, Economy mode may result in higher fees. In that case, Fast mode is recommended.
• For dApp integrations, we recommend checking the pre-deducted energy fee shown by the wallet before calling this method and confirming the cost in advance.