Submitted by sorrynotsorry
https://github.com/code-423n4/2022-11-canto/blob/2733fdd1bee73a6871c6243f92a007a0b80e4c61/CIP-001/src/Turnstile.sol#L86-L101
https://github.com/code-423n4/2022-11-canto/blob/2733fdd1bee73a6871c6243f92a007a0b80e4c61/CIP-001/src/Turnstile.sol#L107-L120
There is no re-register or re-assign option for the smart contracts.
Lets assume a smart contract is registered either through the register() function with a new NFT minted or the assign() function to an existing NFT.
However, if somehow, the NFT is burned by the owner or transferred to another owner either by an approval or compromised tx, there is no option to re-register for these contracts which create gas fees but might not get a fee distribution in return.
And if the NFT is burned or transferred to another owner, the smart contracts will lose the fees generated if not previously withdrawn.
register function;
Permalink
assign function;
Permalink
The team might consider adding an option to validate historical registrations and re-register those contracts accordingly.
tkkwon1998 (Canto) acknowledged and commented:
For this contest, 13 reports were submitted by wardens detailing low risk and non-critical issues. The report highlighted below by 0xSmartContract received the top score from the judge.
The following wardens also submitted reports: Josiah,
Deivitto,
peritoflores,
cryptonue,
keccak123,
RaymondFam,
rotcivegaf,
aphak5010,
gzeon,
martin,
cccz, and
joestakey
.
