(feature) Can different chain nodes connect to a single instance of slinky?

[shupcode]

Assuming there are 2 different chains (A, B) with 2 different required sets of marketmap assets (set-A, set-B), is it possible to configure slinky to generate set-C that contains set-A and set-B, and allow a single instance of slinky to provide prices to chain A and chain B?

Assuming more chains onboard with Slinky, and validators decide to run them from a single high-spec hardware machine with a single IP, multiple slinky instances from the same ip can potentially cause rate-limiting issues from exchanges or other endpoints.

Furthermore assuming set-A contains all of set-B marketmap assets, there is some redundancy in running more than 1 instance of slinky when both chain-A and chain-B could potentially grab prices from the same slinky instance.

[davidterpay]

We're scoping out the design to have a single sidecar be utilized across multiple chains. Should be a feature we add over the next few months!