how the KPNG API objects connect

 

There are jobs and they implement a Sink and a Run().  These are called out to from the kpng cmd/ package when you start a new backend.

There are two ways a backend can process data coming from the KPNG GRPC api.  Raw (Fullstate) or,  massaged by a decoder. 

To grok this, look at any KPNG backend, and first look at the sink.go or register.go functions, they will show you what localsink/ they import.  That will then tell you how they are receiveing and processing data. 

Ill add this to the docs more formally soon