(RNExt-01) - Event processing framework about rchip-proposals HOT 3 OPEN

events are critical in ethereum apps for synchronizing external processes. RChain needs that capability somehow. STDOUT fails to identify the source of the output and is thus not trustworthy unless a deployId or other identification is provided for the output..

from rchip-proposals.

I just (re?)discovered rho:block:data.

https://github.com/rchain/rchain/blob/2677fcaf57edd2538fdc330400de569bdd1a76cf/casper/src/main/resources/RevVault.rho#L193-L196

It looked like an event mechanism for a minute, but then I realized: it's data going into an event, not a destination for storing events.

For reference, by way of motivation for events:

• Smart Contracts are not Databases | by Alberto Cuesta Cañada | Coinmonks | Medium Apr 7

from rchip-proposals.

@dckc block data should be like a clock on chain. Contract can calculate how many blocks are passed as time.

from rchip-proposals.