Skip to content

Conversation

@NicoMolinaOZ
Copy link
Contributor

@NicoMolinaOZ NicoMolinaOZ commented Dec 1, 2025

Documentation Pull Request

Summary

  • Adding info about monitor migration to open source monitor.
  • Adding info about relayer migration to open source monitor.
  • Fixing minor issue

DO NOT MERGE - FIRST WE NEED TO DEPLOY DEFENDER LAST CHANGES

Type of Change

  • New documentation
  • Documentation update/revision
  • Fix typos or grammar
  • Restructure/reorganize content
  • Add examples or tutorials
  • Update API documentation
  • Other: ___________

Related Issues

Fixes #
Relates to #

Checklist

Additional Notes

@netlify
Copy link

netlify bot commented Dec 1, 2025

Deploy Preview for openzeppelin-docs-v2 ready!

Name Link
🔨 Latest commit c549642
🔍 Latest deploy log https://app.netlify.com/projects/openzeppelin-docs-v2/deploys/6932f2ff81b6d2000820753f
😎 Deploy Preview https://deploy-preview-91--openzeppelin-docs-v2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@NicoMolinaOZ NicoMolinaOZ requested a review from zeljkoX December 2, 2025 17:51
Testnet relayers are considered inactive if they haven’t sent any transactions in more than 60 days. When a testnet relayer is inactive, we provide a 14-day grace period to mark the relayer as active. If users don’t take any action, the relayer will be automatically deleted once the period is over.
## Migration: Defender Relayer to OpenZeppelin Open Source Relayer
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this placement is not visible enough.

In the Defender Overview page, top part, we should add callouts with links to Relayer and Monitor migration pages.

We can do that for Monitor and Relayer pages as well, add top level callout for migration guide and create new pages in guides directory, OpenSource Relayer migration page and OpenSurce Monitor migration page.

That way we would with callouts increase visibility and we would improve readability by placing migration content into separate page.

In addition to that here are few more recommendations on how to improve migration flow:

  • Add Notes to Defender landing page above overview section with links to migration guides(Monitor, Relayer).
  • Add Pages in OpenZeppelin Relayer and OpenZeppelin Monitor docs so users visiting those pages could check how to migrate to those projects from Defender. Now we only have guide in Defender Docs. Other option is to add callouts to OpenSource Monitor and Relayer docs with callout and link that leads to Defender migration pages.

cc @tirumerla To verify should we add additional steps i pointed out here.

@zeljkoX
Copy link
Contributor

zeljkoX commented Dec 4, 2025

small nits, otherwise looks good. Thanks

Copy link
Collaborator

@tirumerla tirumerla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, added few text changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants