[cleanup][indexer] Clean up unused protos and add new proto for grpc

[larry-aptos]

Description

• Cleaning up the streamingfast unused protos.
• Adding/building a new proto for our upcoming work on indexer.

Test Plan

[github-actions]

✅ Forge suite land_blocking success on 09697d0ab6f4e2aa23d0da23b3d6497cdf0b57fd

performance benchmark with full nodes : 6613 TPS, 5996 ms latency, 13200 ms p99 latency,(!) expired 160 out of 2824220 txns
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite compat success on testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> 09697d0ab6f4e2aa23d0da23b3d6497cdf0b57fd

Compatibility test results for testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> 09697d0ab6f4e2aa23d0da23b3d6497cdf0b57fd (PR)
1. Check liveness of validators at old version: testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b
compatibility::simple-validator-upgrade::liveness-check : 7252 TPS, 5288 ms latency, 8200 ms p99 latency,no expired txns
2. Upgrading first Validator to new version: 09697d0ab6f4e2aa23d0da23b3d6497cdf0b57fd
compatibility::simple-validator-upgrade::single-validator-upgrade : 4281 TPS, 9544 ms latency, 12700 ms p99 latency,no expired txns
3. Upgrading rest of first batch to new version: 09697d0ab6f4e2aa23d0da23b3d6497cdf0b57fd
compatibility::simple-validator-upgrade::half-validator-upgrade : 4919 TPS, 8449 ms latency, 11100 ms p99 latency,no expired txns
4. upgrading second batch to new version: 09697d0ab6f4e2aa23d0da23b3d6497cdf0b57fd
compatibility::simple-validator-upgrade::rest-validator-upgrade : 6979 TPS, 5486 ms latency, 10300 ms p99 latency,no expired txns
5. check swarm health
Compatibility test for testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> 09697d0ab6f4e2aa23d0da23b3d6497cdf0b57fd passed
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[ppoliani]

I can see this PR removes the extractor.proto. However, this is what we currently use in our Streaming fast indexer which utilises Firehose. Is there a documentation explaining the reasons behind this so we can determine what future holds for our indexer?

[larry-aptos]

I can see this PR removes the extractor.proto. However, this is what we currently use in our Streaming fast indexer which utilises Firehose. Is there a documentation explaining the reasons behind this so we can determine what future holds for our indexer?

We'll add extractor.proto back soon. @bowenyang007 is working on this.

[bowenyang007]

@ppoliani We removed that piece of code b/c it's unmaintained (both firehose-stream and extractor.proto). We are building a grpc endpoint so I'm sort of adding it back, but we make no guarantee that the schema will be the same b/c we are not integrated with StreamingFast's Firehose service.

If you want to maintain the integration the best way is to create your own fork.

[ppoliani]

@bowenyang007 thank you for the clarification. Does it mean that this config will also become obsolete?

I'm currently running this firehose-enabled node . Should I expect that future versions of the Aptos node will not work with that code?

[YaroShkvorets]

So is extractor.proto coming back?

[bowenyang007]

So is extractor.proto coming back?

Unfortunately it's not.