TTP as a Service PoC

[sreuland]

What

PoC of using the Token Transfer Processor TTP as a compiled cli tool(micro-service) which emits token transfer events over streaming GRPC protocol.

The sub-directory structure comprises two sample applications which demonstrate the TTP as a service using .protos for IDL and a Node javascript based consumer:

• cli_tool runs a GRPC service by using protobufs/GRPC generated code from the TTP .protos as the IDL for token transfer events.
  • provides GetTTPEvents as a GRPC streaming endpoint.
  • uses RPC serrver on testnet as the source of ledger metadata,
  • runs an instance of TTP internally to derive token transfer events from ledger metadata
• A sample consumer app is provided in Node javascript. It uses client-side code generated from same TTP .protos. The app requests and consumes a stream of token transfer events over GRPC from a running instance of cli_tool.

demo recording of building and running the processor as a GRPC service and then running a Node javascript consumer in command line terminal:

To try this at home, checkout the pr locally and follow the demo steps in exp/tools/ttp_poc/README.md

Why

• Enables applications developed in non-go programming languages to consume Token Transfer events produced by TTP.
• Composing ingestion processors as services with an accompanying IDL(.proto file) defining their service endpoint and output model facilitates distributed streaming topology. Processors interact with other Processors through the IDL only for loosely coupled systems.

Known limitations

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
golang/github.com/stellar/[email protected]	environment, eval, filesystem, network, shell, unsafe	0	17.9 MB
golang/github.com/stellar/[email protected]	environment, eval, filesystem, network, shell, unsafe	0	819 kB
golang/google.golang.org/[email protected]	environment, eval, filesystem, network, shell, unsafe	0	9.03 MB
golang/google.golang.org/[email protected]	environment, eval, filesystem, network, shell, unsafe	0	15.5 MB
npm/@grpc/[email protected]	None	+1	2.37 MB	grpc-packages, murgatroid99, nicolasnoble
npm/@grpc/[email protected]	filesystem Transitive: environment, network	+29	3.8 MB	murgatroid99
npm/@types/[email protected]	None	0	116 kB	types
npm/@types/[email protected]	None	+1	2.4 MB	types
npm/[email protected]	None	0	735 kB	dibenede
npm/[email protected]	None	0	37.5 MB	thesayyn
npm/[email protected]	environment, filesystem, shell	+46	2.01 MB	whitecolor
npm/[email protected]	environment, filesystem, unsafe	+16	2.12 MB	blakeembrey
npm/[email protected]	None	0	22.9 MB	typescript-bot

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Deprecated	npm/[email protected]	Reason: Glob versions prior to v9 are no longer supported	exp/tools/ttp_poc/consumer_app/node/package-lock.json exp/tools/ttp_poc/consumer_app/node/package.json	⚠︎
Deprecated	npm/[email protected]	Reason: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.	exp/tools/ttp_poc/consumer_app/node/package-lock.json exp/tools/ttp_poc/consumer_app/node/package.json	⚠︎
Deprecated	npm/[email protected]	Reason: Rimraf versions prior to v4 are no longer supported	exp/tools/ttp_poc/consumer_app/node/package-lock.json exp/tools/ttp_poc/consumer_app/node/package.json	⚠︎

View full report↗︎

Next steps

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]