From a1eaa342b666fe49d03b0760b7baa5911f81f7a9 Mon Sep 17 00:00:00 2001 From: Rahul Kothari Date: Tue, 6 Feb 2024 14:48:07 +0000 Subject: [PATCH] update import --- docs/docs/developers/contracts/portals/main.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/developers/contracts/portals/main.md b/docs/docs/developers/contracts/portals/main.md index 4226ff7460b8..71e5bd40751a 100644 --- a/docs/docs/developers/contracts/portals/main.md +++ b/docs/docs/developers/contracts/portals/main.md @@ -78,7 +78,7 @@ The portal must ensure that the sender is as expected. One way to do this is to To send a message to L1 from your Aztec contract, you must use the `message_portal` function on the `context`. When messaging to L1, only the `content` is required (as a `Field`). -#include_code context_message_portal /yarn-project/aztec-nr/aztec/src/context.nr rust +#include_code context_message_portal /yarn-project/aztec-nr/aztec/src/context/private.nr rust When sending a message from L2 to L1 we don't need to pass recipient, deadline, secret nor fees. Recipient is populated with the attached portal and the remaining values are not needed as the message is inserted into the outbox at the same time as it was included in a block (for the inbox it could be inserted and then only included in rollup block later).