Solana Accounts Common Modules v0.0.1

New foundational module with account and owner indexes for new solana-accounts substreams endpoint

Vara Foundational Common Modules v0.1.6

Update vara foundational common modules with new metadata version 1620

Starknet-foundational-v0.1.4

• Add padding (64 chars) into addresses, on index keys

Release v0.1.5

Update vara foundational modules with new metadata versions 1421, 1501, 1500

Release v0.1.4

• Fix filtered_extrinsics module importing wrong module
• Update to naming for proto folder to be in line with what is defined inside of the proto types file definition

Solana-common-v0.3.0

• Kept the module hashes identical for blocks_without_votes and program_ids_without_votes index
• Renamed the protobuf output for the 'transaction' modules to proto:sf.substreams.solana.v1.Transactions instead of sol.transactions...
• Renamed the filtered_transactions_without_votes module to transactions_by_programid_without_votes. This index is way bigger than the one with only program IDs, but cover more cases.
• Added program_ids_and_accounts_without_votes index and transactions_by_programid_and_account_without_votes associated mapper

Solana-common-v0.2.0

Solana Common Modules

The Solana Common Modules Substreams contains a set of modules that allow you to easily retrieve basic information from the Solana blockchain, such as transactions or instructions.

The substreams.yaml file defines all the different modules available, and also provides you with documentation about the usage of every module.

Basic Modules

• blocks_without_votes: consume a full Solana Block without Vote transactions (i.e. transactions containg Vote111111111111111111111111111111111111111 instructions). You will have access to the data of a Solana block but the transactions array will not contain Vote transactions.

Filtered Modules

Usually, you want to only listen for specific transactions or instruction types. The following module allow you to specify a filter based on the program ID of the instruction to efficiently retrive filtered transactions.

• filtered_transactions_without_votes: allows you to consume transactions containing instructions from specific program_id based on a filter string.
  Supported operators are: logical or ||, logical and && and parenthesis: ().
  Example: to only consume TRANSACTIONS containing Token or ComputeBudget instructions: program:TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA || program:ComputeBudget111111111111111111111111111111.
  Transactions containing Vote111111111111111111111111111111111111111 are always excluded.

injective-v0.2.3

remove all transactions and filtered transaction

vara-foundational-v0.1.3

Refactor metadata registry to include call and event registries

Refactored the metadata registry to store `regItem` structs containing metadata, call registries, and event registries. Updated the `MapDecodedBlock` function to use the new structure, simplifying the retrieval of registries and reducing redundancy. Additionally, bumped the package version in `substreams.yaml` from v0.1.2 to v0.1.3.

vara-foundational-v0.1.2

Fix seq and array inside a variant