-
Notifications
You must be signed in to change notification settings - Fork 157
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
✨ Prototype DN420 #118
✨ Prototype DN420 #118
Conversation
I just discovered this PR after reading your reply on X. While I believe you may have a more refined implementation of this idea, I would appreciate knowing if you would permit me to add my implementation to the ERC if the PR be merged into the main branch later. Here are the links to the PR of the ERC and the discussion. Of course, feel free to inform me if you and your big brain friends would like to be added as authors as this PR exist for quite awhile compare to the ERC PR with most of the ideas were inspired from DN404 / ERC7631. |
I'll merge this first. |
Description
The aim is to build the "most efficient" single dual-nature contract,
that is also scalable in the long term (no out-of-gas DoS vectors even with millions of trades),
and usable for IPFS token URIs with per-token unique metadata.
This is still extremely hot and experimental.
I haven't got the rest of the avengers to internal audit this yet.
USE AT YOUR OWN RISK
Tbh, I think that ERC721 is a more flexible option in the long term, mainly because of
ownerOf
.Past a certain point, there is only so much gas you can save before eating into UX.
Always take benchmarks (including ours) with a pinch of salt, as they can be cheesed.
Update:
May merge soon once all the fixes are in. But for battle-tested safety and versatility, I'd still recommend DN404.
Checklist
Ensure you completed all of the steps below before submitting your pull request:
forge fmt
?forge snapshot
?forge test
?Pull requests with an incomplete checklist will be thrown out.