Content
@
0 reply
20 recasts
20 reactions
Haardik
@haardikkk
Syncing Teleport onchain from scratch and came across weirdness In block 114523861, there is a storage Rent event from someone which has fid 38053300632633822045410405651412025795888287900 How is this even possible? This broke Teleport a bit - working on fixing it, but how does this fid even exist? cc @v
9 replies
1 recast
7 reactions
Varun Srinivasan
@v
If it’s a valid fid then you can either : 1. Keep track of it now 2. Reindex the event when the fid is added Cc @sanjay and @horsefacts.eth
2 replies
0 recast
1 reaction
horsefacts
@horsefacts.eth
Yeah, this is not handled at the contract level, it’s up to hubs to validate it. We could do this in future storage contracts if we change our minds. It does avoid a dependency between the storage registry and ID registry contracts.
0 reply
0 recast
1 reaction
