bgreni / solanarpcclient Goto Github PK

For some reason the Solana rpc cluster rejects my wss connection on port 443 (which works just fine with Helius rpc's), and I can't for the life of me figure it out.

Creating this ticket to reflect the existence of this problem, and for obvious reasons will need to be fixed for MVP.

I have yet to finalize the api for versioned transactions in TransactionBuilder. I don't necessarily want to mirror the way it's done in web3.js, but I've yet to decide on preferable solution

Threadsafety for websocket subscription callbacks should be the default to avoid footguns, but still offer an alternative to avoid the performance hit for callback handlers that don't have side effects.

Json and JsonParsed response bodies got getTransactions are left in json form because I was being lazy, this obviously needs to be resolved before we can declare MVP

Read throughput performance on websocket connections is sometimes extremely poor.

Using "onLogs" with the "all" option (which produces hundreds of notifications a second usually) sometimes only ~50 messages will be processed within a 5 second period. The nature and inconsistency of the issue points to a threading/resource contention issue most likely.

This will likely require a high amount of effort to resolve, and only affects high throughput subscriptions so I won't fix it immediately, but creating this ticket to reflect its existence, and to remind myself to fix it later if it persists after the feature is further stabilized.

Being able to wait on the result of a transaction is a critical piece of functionality. Based on my inspection of the web3.js code. They implement it roughly as follows.

• Open a websocket connection to listen for changes in the signature status
• Send a request to the rpc method in case the transaction has already reached the desired finality and cancel the subscription if so
• Return the result of the operation

Once again being too lazy to do this immediately, so making a ticket for it.