Here is an article based on your issue:

Title: Solana: Address Table Lookups Not Added to VestingTransaction Message

Introduction

As a developer working on the Solana blockchain, I am constantly looking for ways to better understand and optimize the various messages used in the Solana protocol. I recently ran into an issue that was hindering my development process.

Problem: Address Table Lookups Not Added to VestingTransaction Message

In order to retrieve the addresses of the accounts in a vesting transaction, I need to look up the address tables (ALTs) associated with the accounts participating in the vesting process. However, when using VestingTransaction, the AddressTableLookup table is not included by default.

Problem:

To resolve this issue, I started by checking the Solana documentation for any messages that mentioned VestingTransaction or related functionality. I couldn’t find any information that suggested adding the AddressTableLookup table to the VestingTransaction message was a necessary action.

Solution: Adding AddressTableLookup

After further research, I discovered that the AddressTableLookup function can be used to look up addresses on the Solana blockchain. To add this function to the VestingTransaction message, we need to use a specific transaction type called VestingTransactionVesting, and then call AddressTableLookup.

Here’s an example of how you could modify the code to add the VestingTransactionVesting transaction:

use solana-program::{account_info::AccountInfo, program_error};
use solana_transaction_builder::TransactionBuilder;
struct VestingTransactionVesting {
account0: &AccountInfo,
account1: &AccountInfo,
}
fn main() -> Result<(), String> {
let mut builder = TransactionBuilder::new();
let vesting = builder
.create_account(
&[
AccountInfo::from_hash(&vesting.account0.key.hash),
AccountInfo::from_hash(&vesting.account1.key.hash),
],
10_000,
);
builder.apply(builder.finish()).unwrap();
// Create the VestingTransactionVesting transaction
let vesting = VestingTransactionVesting {
account0: vesting.account1.clone(),
account1: vesting.account0.clone(),
};
// Define a function to be called when the vesting is complete
fn on_vesting_complete(vesting: &TransactionGesting) -> Result<(), String> {
let address_table_lookup = Address_table_lookup::new();
// Search for addresses on the Solana blockchain
for (index, account_info) in vesting.account0.keys.iter().enumerate() {
if index == 1 {
// Find an address that matches the account info hash
match address_table_lookup.find(&account_info.key.hash) {
Some(address) => println!("Found address {}", address),
None => return Err("Address not found".to()),
}
} else {
println!("Found another account {}", index);
}
}
OK(())
}
// When the vesting is complete, call the on_vesting_complete function
builder.call_function(
&[
"on_vesting_complete",
AccountInfo::from_hash(&vesting.account0.key.hash),
AccountInfo::from_hash(&vesting.account1.key.hash),
],
100,
)
.Unwrap();
}

Conclusion

In summary, adding the AddressTableLookup function to the VestingTransaction message can be a useful optimization for retrieving account addresses.

Ethereum Smart Using