You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4d82cea
Browse filesBrowse the repository at this point in the historyBrowse files
Fix Chainhooks cross-reference to point to local migrated content
Updates contract-monitoring README to link to build/chainhooks/overview.md
instead of external docs.hiro.so URL, since Chainhooks docs are now
migrated locally.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/build/hiro-platform/contract-monitoring/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,12 @@ Contract monitoring lets you track smart contract events in real-time and receiv
14
14
|**Contract Monitoring**| No-code, UI-based alerts for specific contract function calls on mainnet |
15
15
|**Chainhooks**| Advanced, programmable event monitoring with custom predicates and self-hosted infrastructure |
16
16
17
-
Contract monitoring is ideal when you want quick, no-code alerts for contract activity. For more complex event-driven workflows, consider [Chainhooks](https://docs.hiro.so/tools/chainhooks).
17
+
Contract monitoring is ideal when you want quick, no-code alerts for contract activity. For more complex event-driven workflows, consider [Chainhooks](../../chainhooks/overview.md).
18
18
19
19
## Next steps
20
20
21
21
-[Create an alert](create-alert.md): Set up your first alert for function calls.
22
-
-[Chainhooks](https://docs.hiro.so/tools/chainhooks): Learn more about Chainhooks and how they differ from contract monitoring.
22
+
-[Chainhooks](../../chainhooks/overview.md): Learn more about Chainhooks and how they differ from contract monitoring.
0 commit comments