Parsed output

[CreepyZander]

Hi,

Great project - well done!

I'm running my own RPC node with Yellowstone running stable.

I'm building a small application that monitors our own established token and provides statistics, buy/sell notifications, competitions based on length of holding, wallet tracking etc.

I have two questions.

At the moment, when I subscribe to our address on gRPC, I am getting the raw Blockchain data. It doesn't seem like the output is parsed in the same way as solana-web3.js.

We want to use a Geyser plug in because it fits in with long-term goals and the speed is critical for these future goals.

As an example, what would be the best way to interpret a buy/sell order using Yellowstone? I'm new to RUST.

Currently we are interpreting the output of Yellowstone via a PHP script (which we know isn't ideal) - but we can port it to a language more suitable later down the line.

My feeling is that I would need to tear apart and port some of the Solana web3.js code into my PHP script.

However, it doesn't look like the filters that are available in Yellowstone are able to limit only buy and sell orders and therefore might overrun my PHP script and potentially cause a backlog.

My second question is, are there any open source projects that are compatible with Yellowstone (or their own geyser plugin) that allow me to implement the hooks similar to that Triton One/Helius offer?

Regard

[Himanityagi27]

Hi
what spec for server your using for geyser plugin
I am also running my solana node with yellowstone plugin
but unfortunately my node is not catchup latest slot ,
server spec 512gb ram , 48 core cpu , 3.4tb disk , latitude cloud ,
sometime my node is start gaining the slot after gaining some slots , again its start failing .

[CreepyZander]

I suspect it's to do with your low ram. Run htop and monitor ram usage in a different terminal while looking at it. Catch up and see if it runs out of ram at the same time it falls behind. I'm running 1.5 TB of RAM Are you indexing? Also, have you put your CPU in performance mode?

…

On Wed, 26 Jun 2024, 07:36 Himanityagi27, ***@***.***> wrote: Hi what spec for server your using for geyser plugin I am also running my solana node with yellowstone plugin but unfortunately my node is not catchup latest slot , server spec 512gb ram , 48 core cpu , 3.4tb disk , latitude cloud , sometime my node is start gaining the slot after gaining some slots , again its start failing . — Reply to this email directly, view it on GitHub <#357 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH377OE65OERS6FFPTQLWWDZJJOPJAVCNFSM6AAAAABI4QZWDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJQHEYTONJQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Himanityagi27]

No i am not indexeing , what configuration you are using for plugin ,

[CreepyZander]

I'm not by my Terminal so I can't provide it but it's pretty stock. Our situations are different however as I am indexing all 3. Yours shouldn't be falling behind if you're not indexing. Have you setup a firewall to stop others from using it? I spotted that as soon as my RPC announced that I'd joined the network, I had connections from people running queries on my RPC node. I installed and configured UFW - Uncomplicated Firewall - and this put a stop to that. Install the firewall, block everything but localhost and try and sync it again. Take care to add a rule for SSH though - you don't want to lock yourself out. I assume you aren't also using the latitude server for a web server, database server etc. Have you put the CPU in performance mode?

…

On Wed, 26 Jun 2024, 08:49 Himanityagi27, ***@***.***> wrote: No i am not indexeing , what configuration you are using for plugin , — Reply to this email directly, view it on GitHub <#357 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH377OA3RAHQKDPZNWUCS43ZJJXCJAVCNFSM6AAAAABI4QZWDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJRGA2DKMRVGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>