Add Enclabs to OEV searching candidates #202
Conversation
|
Visit the preview URL for this PR (updated for commit cd9466b): https://oev-docs--pr202-add-enclabs-pkhuq2rd.web.app (expires Tue, 01 Jul 2025 08:55:30 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 6915b094b5ba83fde754632ba50c1ee9406d433f |
| @@ -25,6 +25,7 @@ The following table includes dApps which integrated OEV proxies and are good can | |||
| | dApp | Chain | dApp alias | | |||
| | -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ----------------------------- | | |||
| | [dTRINITY](https://dtrinity.org/) | Fraxtal, Sonic | `dtrinity` | | |||
| | [Enclabs](https://www.enclabs.finance/) | Sonic | `enclabs` | | |||
There was a problem hiding this comment.
Did they switch to their given proxies? We should only merge this once that is done.
There was a problem hiding this comment.
No not yet. I thought it's not much of a searchers' concern, but the PR can wait 👍
There was a problem hiding this comment.
The problem by listing them on this page you're essentially telling the searchers they can derive the dApp ID with the above data and start searching. That is obviously wrong, because they are still using proxies with dApp ID 1.
No description provided.