Go to file
Linus Kendall 7d7056e043
Update README.md (#66)
2023-02-22 17:44:56 +05:30
.github/workflows Change release name in CI (#50) 2023-02-09 23:29:05 -03:00
ci Updating ci script 2023-02-09 14:19:33 -03:00
golang Updated golang client (#58) 2023-02-22 17:27:48 +05:30
nodejs Fix JS and TS clients compatibility with older Nodejs versions (#60) 2023-02-22 15:06:34 +05:30
proto Added golang client 2023-02-03 10:49:17 +00:00
rust Update README.md (#65) 2023-02-22 17:42:13 +05:30
solana-geyser-grpc chore: mv client.rs into rust dir (#62) 2023-02-22 17:28:41 +05:30
typescript Fix JS and TS clients compatibility with older Nodejs versions (#60) 2023-02-22 15:06:34 +05:30
.gitignore Fix JS and TS clients compatibility with older Nodejs versions (#60) 2023-02-22 15:06:34 +05:30
Cargo.lock chore: mv client.rs into rust dir (#62) 2023-02-22 17:28:41 +05:30
Cargo.toml chore: mv client.rs into rust dir (#62) 2023-02-22 17:28:41 +05:30
README.md Update README.md (#66) 2023-02-22 17:44:56 +05:30
config.json Add filter limits to config (#4) 2022-10-25 14:52:29 -03:00
rust-toolchain.toml Update solana =1.14.10 (#19) 2022-12-16 10:37:32 -03:00

README.md

Solana GRPC interface

This repo contains a fully functional gRPC interface for Solana. It provides the ability to get slots, blocks, transactions, and account update notifications over a standardised path.

For additional documentation, please see: https://docs.triton.one/rpc-pool/grpc-subscriptions

It is built around a Geyser plugin for the Solana interface.

Validator

$ solana-validator --geyser-plugin-config ./config.json

Plugin config check

cargo-fmt && cargo run --bin config-check -- --config config.json

Filters

See proto/geyser.proto.

Slots

Currently all slots are broadcasted.

Account

Accounts can be filtered by:

  • account — acount Pubkey, match to any Pubkey from the array
  • owner — account owner Pubkey, match to any Pubkey from the array

If all fields are empty then all accounts are broadcasted. Otherwise fields works as logical AND and values in arrays as logical OR.

Transactions

  • vote — enable/disable broadcast vote transactions
  • failed — enable/disable broadcast failed transactions
  • account_include — filter transactions which use any account
  • account_exclude — filter transactions which do not use any account

If all fields are empty then all transactions are broadcasted. Otherwise fields works as logical AND and values in arrays as logical OR.

Blocks

Currently all blocks are broadcasted.

Blocks meta

Same as Blocks but without transactions.

Limit filters

It's possible to add limits for filters in config. If filters field is omitted then filters doesn't have any limits.

"grpc": {
   "filters": {
      "accounts": {
         "max": 1,
         "any": false,
         "account_max": 10,
         "account_reject": ["TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"],
         "owner_max": 10,
         "owner_reject": ["11111111111111111111111111111111"]
      },
      "slots": {
         "max": 1
      },
      "transactions": {
         "max": 1,
         "any": false,
         "account_include_max": 10,
         "account_include_reject": ["TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"],
         "account_exclude_max": 10
      },
      "blocks": {
         "max": 1
      }
   }
}