PIP-16: Adding events in Pactus transactions

[ja7ad]

PIP-16: Adding events in Pactus transactions

[b00f]

We don't have smart contract now.
I am not sure I understood it correctly, but can't we use nanomsg for future events for smart contracts?

[ja7ad]

This model is in Ethereum to find event easy

[b00f]

Pactus uses NanoMsg for emitting events. Each event has a key and a corresponding value.
Keys are hardcoded and defined here.

If we add smart contracts, we can include more events.
NanoMsg fires events and then forgets them.
It doesn't have any memory to keep them; it just sends events to anyone who is interested.

However, we can have an extension or service that stores NanoMsg events and then replays them.
For example, a user may ask the event service to get all events related to smart contract_A after block number N.

[b00f]

@ja7ad category is missed for this PIP.

[kehiy]

@b00f After checking more protocols and more research, I found that this fire-and-forget model in Pactus is good and it's enough even for contracts. I can't see a reason to keep events.

Our nano message can be improved and provide subscribing for specific event also. but keeping events on the chain is not necessary and an off-chain fire-and-forget model is good enough.

If you guys agree, I think we can change the status to withdrawn.

Note: if someone searches for an on-chain event in the past, we have APIs and it's possible without events at all I think. But there are more complex situations for dApps to be considered that we can disscuess.

[b00f]

Yes, this model is good and we can implement more complicated events on top of that

[b00f]

@kehiy Thanks for drafting this PIP
This PIP is replaced by PIP-35. Status can be changed to rejected.