price feed mechanism without Zoe

[turadg]

What is the Problem Being Solved?

The price feed contract, fluxAggregator, receives new prices by PushPrice offers. That incures the overhead of Offer Safety and the entire Zoe layer. (See benchmark) It also goes through smartWallet because that is how the oracle operator account is endowed with permission to push.

Description of the Design

TK @warner has some ideas.

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

Probably after this,

• Plan for replacing priceFeeds, redirecting oracles #8740

[mhofman]

We don't automatically need to avoid the smart wallet, as it's still a good place to hold and translate capabilities for a given message sender. I know that @michaelfig had ideas on how to move the REPL feature to the smart wallet, which would require the ability to send messages to remote objects held there, and handle results. I expect that ability to be very similar to any communication that bypasses Zoe offer safety.

One thing to remember is that only smart wallet messages are currently enabled for high priority status based on the owner. We will need to extend that to whatever new cosmos message type this new interaction would require.