Linus Kendall

Any path component should be accepted

1

To follow the behaviour of the solana validator and be as transparent as possible the cache should accept any path "/" component of the URL. I have seen some applications...

Feature/discussion: multiple ip addresses

1

This might be something we'd look to contribute to the repo, but first wanted to check your thoughts about the design/integration of it. Here's the rationale: We have multiple PoPs....

Add gossip notifications / cluster node notifications to geyser

4

#### Problem To avoid having lite clients like (https://github.com/blockworks-foundation/lite-rpc) participate in gossip and causing further # of gossip clients increasing we would like to be able to get notifications via...

JSON RPC API using (u)int64 whereas JS can only handle int53

7

#### Problem The JSON API uses int64 for fields like lamports. However, the maximum safe integer in browsers is 2^53-1 https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER #### Proposed Solution Make lamports a string in the...

(Optionally) Load messenger config from geyser config file

2

Currently messenger config is loaded only from environment variables. It would be helpful if it could optionally load it from the geyser config file, as this allows some more flexibility...

I believe that this: https://github.com/solana-labs/solana-accountsdb-plugin-postgres/pull/23/files Doesn't actually fix the transaction order in the blocks. Requires this: https://github.com/solana-labs/solana/pull/25688

This is related to: https://github.com/lijunwangs/solana-postgres-rpc-server/issues/3 When slots that were on forks end up being skipped, we're storing inconsistent state data in the `accounts` table. Proposed solution: Add a trigger that...

Currently you need to activate historical data storage to be able to run the RPC server (https://github.com/lijunwangs/solana-postgres-rpc-server) as it can otherwise not return the correct commitment level data. If the...

I believe that getAccountInfo can return incorrect/invalid reads when accounts are written to on a fork that later doesn't get confirmed. Suppose account `XXX` is written to on slot `123`....

Since GPA is currently not fully supported by the plugin (not using `account_audit` table) this means it can yield incosistent result - either including accounts that shouldn't be or excluding...