ERC-6982: Default Lockable Proposal

[tbergmueller]

Thanks for your comments @sullof and @SamWilsn!

@sullof

expects 4 parameters, instead of 2, which means that if you replace it with the Locked events in IERC6982, you would either lose information or having to rethink the logic .

Were considering to simplify our whole proposal and make the mapping tokenId <> anchor optional. A much simpler way with identical security is when anchor (bytes32) is used directly as a tokenId (uint256 == bytes32).

This would revert our rationale “Why do you use an anchor<>tokenId mapping and not simply use tokenIds directly?”. Consequently, we’ll need to change all ERC-6956 events and omit the anchor from events. Since I do not know of any large adoptions besides ours yet, this breaking change seems acceptable. dApps interested in the mapping anchor <> tokenId will need to call anchorByTokenId().

@SamWilsn

If you’re talking about the required preamble header, think of it more as “required reading” and not “required to implement”.

Yes I was, thanks for the clarification! If it is only “required to read” it’s fine IMHO to list ERC-6982 there.