Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIP-0083: Changes to VerifReg events and Sector Activation event as per FIP discussion #905

Closed
wants to merge 17 commits into from
Closed

FIP-0083: Changes to VerifReg events and Sector Activation event as per FIP discussion #905

Changes from all commits
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
3974c92
fip for built-in Actor events
aarshkshah1992 Nov 27, 2023
df5bfca
finish draft
aarshkshah1992 Nov 27, 2023
bea0cf0
fix formatting
aarshkshah1992 Nov 27, 2023
edba91f
changes as per review #1
aarshkshah1992 Dec 12, 2023
6ea0be3
link FIPs
aarshkshah1992 Dec 12, 2023
af82b6d
Apply suggestions from code review
aarshkshah1992 Dec 14, 2023
9df8f31
update Market Actor events
aarshkshah1992 Dec 14, 2023
979b035
add FIP number
aarshkshah1992 Dec 15, 2023
7eb8da9
merged
aarshkshah1992 Dec 15, 2023
09ccfd1
update fip-0083 to incorporate changes to market actor and sector act…
aarshkshah1992 Dec 21, 2023
6cd5df5
Apply suggestions from code review
aarshkshah1992 Jan 4, 2024
5c2b201
Merge remote-tracking branch 'origin/master' into aarshkshah1992/FIP-…
aarshkshah1992 Jan 4, 2024
1a959d2
change language
aarshkshah1992 Jan 4, 2024
6e57cf4
changes as per FIP discussion
aarshkshah1992 Jan 4, 2024
871472c
Merge remote-tracking branch 'origin/master' into aarshkshah1992/FIP-…
aarshkshah1992 Jan 4, 2024
4e3815c
merge
aarshkshah1992 Jan 4, 2024
e0332d8
resolve conflict
aarshkshah1992 Jan 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 20 additions & 15 deletions FIPS/fip-0083.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,12 +68,14 @@ This event is emitted when a verified client allocates datacap to a specific dat

The event payload is defined as:

| flags | key | value |
| --- | --- |-------------------------|
| Index Key + Value | “$type” | “allocation” (string) |
| Index Key + Value | “id” | <ALLOCATION_ID> (int) |
| Index Key + Value | “client” | <CLIENT_ACTOR_ID> (int) |
| Index Key + Value | “provider” | <SP_ACTOR_ID> (int) |
| flags | key | value |
| --- |--------------|-------------------------|
| Index Key + Value | “$type” | “allocation” (string) |
| Index Key + Value | “id” | <ALLOCATION_ID> (int) |
| Index Key + Value | “client” | <CLIENT_ACTOR_ID> (int) |
| Index Key + Value | “provider” | <SP_ACTOR_ID> (int) |
| Index Key + Value | "piece-cid" | <PIECE_CID> (cid) |
| Index Key | "piece-size" | <PIECE_SIZE> (bigint) |

#### Datacap Allocation Removed
This event is emitted when a datacap allocation that is past its expiration epoch is removed.
Expand All @@ -100,6 +102,8 @@ The event payload is defined as:
| Index Key + Value | “id” | <CLAIM_ID> (int) |
| Index Key + Value | “client” | <CLIENT_ACTOR_ID> (int) |
| Index Key + Value | “provider” | <SP_ACTOR_ID> (int) |
| Index Key + Value | "piece-cid" | <PIECE_CID> (cid) |
| Index Key | "piece-size" | <PIECE_SIZE> (bigint) |

#### Claim Updated
This event is emitted when the term of an existing allocation is extended by the client.
Expand Down Expand Up @@ -205,13 +209,14 @@ 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) |
| Index Key + Value | “unsealed-cid” | <SECTOR_COMMD> (cid) |
| Index Key + Value | "piece-cid" | <PIECE_CID> (cid) |
| Index Key + Value | "piece-size" | <PIECE_SIZE> (bigint) |
| 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 | "piece-size" | <PIECE_SIZE> (bigint) |
| Index Key + Value | "has-data" | <IS_NOT_A_CC_SECTOR> (bool) (true if NOT CC sector, false if CC sector) |

- Note that `piece-cid` and `piece-size` is included for each piece in the sector.

Expand Down Expand Up @@ -257,8 +262,8 @@ All Market Actor events have the client and provider Actor IDs in the event payl
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`.
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
Expand Down