Emit offchain data via oracle.

[LeilaWang]

An app can emit "offchain" data via oracle, whenever it sees fit.

// oracle.nr
fn emit_offchain_data<MAX_LEN>(storage_slot: Field, data: [Field, MAX_LEN]);

The user should be able to find the offchain data in simulation result. They can either share it with relevant parties offline, or call PXE.addNote to store it for use in future transactions.

[benesjan]

@LeilaWang this has most likely been sufficiently addressed with my and Spyros's work on logs. There are now 2 oracles available for emitting encrypted or unencrypted logs.

The only thing which seems to be different is the data delivery because all the logs are pushed onchain as a part of the encoded block. But that is not so important, right?

[iAmMichaelConnor]

Interesting concept!

I suppose as a cost-saving measure there are two ways to emit data more cheaply than L1 (but without data availability guarantees):

• Emit the data via an oracle (I've not thought about this before - it's basically asking your own node to remember some information, so you can share it with people later).
• Emit the data via L2: I.e. emit the data to the L2 tx pool, and add the data to a leaf of the transactions tree (or maybe the receipts tree - I forget which), but don't emit the data on L1.

Cool.