Open estebanabaroa opened 1 year ago
1 and 2 are implemented with commit #7b833a65f6470ab2fdc4f0f945c173434a67223e, although a resolve result is considered stale only after 24 hours. I do think that's too much, but also 5m is too low. Maybe 1 hour is good?
I updated ethers.js to 6.3.0 but it requires tsconfig to upgrade to ES2015, which changes a few things in our setup. Maybe not worth the effort for now
1 and 2 are implemented with commit #7b833a65f6470ab2fdc4f0f945c173434a67223e, although a resolve result is considered stale only after 24 hours. I do think that's too much, but also 5m is too low. Maybe 1 hour is good?
I updated ethers.js to 6.3.0 but it requires tsconfig to upgrade to ES2015, which changes a few things in our setup. Maybe not worth the effort for now
I dont think 1 hour is good, the user won't be able to set up his own sub ENS and see it working for 1 hour. assuming the user has 100 subscriptions, that means he makes 100 eth calls every 5 minutes, that seems fine to me. especially since at some point we should use multicall to bulk them up.
Ideas to improving ENS resolving: