-
Notifications
You must be signed in to change notification settings - Fork 145
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.
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
Update HIP-904 status and HSCS details #1080
Conversation
Signed-off-by: Stanimir Stoyanov <[email protected]>
✅ Deploy Preview for hedera-hips ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Stanimir Stoyanov <[email protected]>
Signed-off-by: Stanimir Stoyanov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 suggestions for completion.
Thanks
HIP/hip-904.md
Outdated
@@ -7,11 +7,12 @@ requested-by: DEXs, Wallets, External Web3 Users. Notably Reality+, Liithos, Dro | |||
type: Standards Track | |||
category: Core | |||
needs-council-approval: Yes | |||
status: Accepted | |||
status: Final | |||
release: v0.54.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be v0.56 as that's when the system contract functions went in.
Agreed it's 0.54 for when HAPI functionality was completed but it might be confusing if users test this using local node or solo 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense. I copied it from the previous PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
address receiver; | ||
|
||
address token; | ||
int64 serial; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems totally obvious that serial
is only for NFTs - but still, maybe a comment that addresses that (and states explicitly that that depends on the token type addressed by the token
field)? (Reason is: It's a little odd that the very next lines introduce NftID
for identifying "the Nft serial to be rejected" but there's nothing similar for fungible types (the address only?) and anyway it's not used here in PendingAirdrop
because that's the way solidity works: No union types.). And must serial == 0
for fungible tokens or is it a don't care?
Another funny thing with NftID
is why isn't it used as the argument for cancelAirdropNFT
or claimAirdropNFT
? But it isn't I guess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a comment for clarification.
For the latter comment, the stated functions are redirect calls that already have the token address so it makes it obsolete to use NftID
there. The address
parameters there are the token airdrop sender/receiver as stated in the naming.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah! my mistake
Signed-off-by: Stanimir Stoyanov <[email protected]>
b5a7d24
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG
Description: