From 793d25e0d437dda9d6c48ce9dce0a4ff4216f51f Mon Sep 17 00:00:00 2001 From: James Zaki Date: Tue, 23 Apr 2024 22:00:10 +0100 Subject: [PATCH] Update emit_event.md --- .../developers/contracts/writing_contracts/events/emit_event.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/docs/developers/contracts/writing_contracts/events/emit_event.md b/docs/docs/developers/contracts/writing_contracts/events/emit_event.md index 0c461c6317d..5ff18cce72e 100644 --- a/docs/docs/developers/contracts/writing_contracts/events/emit_event.md +++ b/docs/docs/developers/contracts/writing_contracts/events/emit_event.md @@ -93,6 +93,7 @@ They can be emitted by both public and private functions. :::danger - Emitting unencrypted events from private function is a significant privacy leak and it should be considered by the developer whether it is acceptable. - Unencrypted events are currently **NOT** linked to the contract emitting them, so it is practically a [`debug_log`](../oracles/main.md#a-few-useful-inbuilt-oracles). + ::: ### Call emit_unencrypted_log