Update FIP-0083 to incorporate changes to the Market Actor events and Sector Activation events as per FIP discussion (#897)

* fip for built-in Actor events

* finish draft

* fix formatting

* changes as per review #1

* link FIPs

* Apply suggestions from code review

Applying editorial changes.

Co-authored-by: Jorge Soares <[email protected]>

* update Market Actor events

* add FIP number

* update fip-0083 to incorporate changes to market actor and sector activation events

* Apply suggestions from code review

Co-authored-by: Alex North <[email protected]>

* change language

---------

Co-authored-by: Jorge Soares <[email protected]>
Co-authored-by: Alex North <[email protected]>

Author: 3 people

FIPS/fip-0083.md

@@ -205,10 +205,15 @@ This event is emitted for each pre-committed sector that is successfully activat
 
 The event payload is defined as:
 
-| flags | key | value                       |
-| --- | --- |-----------------------------|
-| Index Key + Value | “$type" | "sector-activated" (string) |
-| Index Key + Value | “sector” | <SECTOR_NUMER> (int)        |
+| flags             | key            | value                       |
+|-------------------|----------------|-----------------------------|
+| Index Key + Value | “$type"        | "sector-activated" (string) |
+| Index Key + Value | “sector”       | <SECTOR_NUMER> (int)        |
+| Index Key + Value | “unsealed-cid” | <SECTOR_COMMD> (cid)        |
+| Index Key + Value | "piece-cid"    | <PIECE_CID> (cid)           |
+| Index Key + Value | "piece-size"   | <PIECE_SIZE> (bigint)       |
+
+- Note that `piece-cid` and `piece-size` is included for each piece in the sector.
 
 #### Sector Updated
 This event is emitted for each CC sector that is updated to contained actual sealed data.
@@ -248,11 +253,12 @@ Once a deal is published, clients have access to the `dealId` of the deal. All M
 for the “deal published” event have the `dealId` in their payload, which clients can use to filter for events
 they are interested in and then query the chain state for more information.
 
-The `dealId` is not known to the storage client before the deal is actually published as it is generated by 
-the storage provider during the call to `PublishStorageDeals`. Therefore, to make the `deal-published` 
-event useful to subscribers and storage clients, the payload for that event also includes the `client` 
-and `provider` Actors IDs so that listeners can filter this event by specific deal making parties they are
-interested in.
+All Market Actor events have the client and provider Actor IDs in the event payload. This enables users
+to filter these events by the specific deal making parties they are interested in and then query the chain
+state with the corresponding `dealId` to get more information.
+
+However, note that the `dealId` is not known to the storage client before the deal is actually published as it is generated by 
+the storage provider during the call to `PublishStorageDeals`. 
 
 Note that cron jobs do not return message receipts containing the emitted events back to the user. 
 Therefore, the Market Actor  `deal-terminated` event will not be usable as it stands today as the deals 
@@ -286,6 +292,12 @@ that can be processed immediately by the `TerminateSectors` method are rate-limi
 The events emitted for these terminations will not be available to the client because they are 
 emitted from a cron job.
 
+Once [FIP-0076](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0076.md) is implemented,
+sectors can be activated with data that is not associated with a built-in market actor deal. This means that clients may 
+not be able to obtain additional information about this data by querying the Market Actor state.
+Therefore, the sector activation events contains the `unsealed_cid(COMMD)` and the `piece_cid` and
+`piece_size` for each piece in the sector as this information will be useful to aggregators, indexers etc. 
+
 ## Backwards Compatibility
 This proposal does not remove or change any exported APIs, nor change any state schemas. 
 It is backwards compatible for all callers. Since it requires a change to actor code, a network upgrade is 
@@ -321,7 +333,7 @@ emit the events defined in this FIP.
 While this increased gas cost is borne by the users of the methods, the benefit of the emitted events 
 is enjoyed by networking monitoring tools, network accounting tools, block explorer tools and other 
 external agents that provide some value-added services to the Filecoin network.  Improved 
-implementation of these tools should indirectly benefit the network users.
+implementation of these tools will indirectly benefit the network users.
 
 ## Product Considerations
 This FIP will enable tools dedicated to network observability, monitoring, and accounting, as well as