From 42004137f7d660ba90feee06bc5e6028b9a20dc5 Mon Sep 17 00:00:00 2001 From: Brian Seong Date: Tue, 5 May 2026 20:35:47 +0900 Subject: [PATCH] docs(node): clarify v0.14 network note diagnostics --- .../core-concepts/node/operator/architecture.md | 5 +++++ versioned_docs/version-0.14/core-concepts/node/rpc.md | 7 ++++++- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/versioned_docs/version-0.14/core-concepts/node/operator/architecture.md b/versioned_docs/version-0.14/core-concepts/node/operator/architecture.md index 93a02fe5..a43bf582 100644 --- a/versioned_docs/version-0.14/core-concepts/node/operator/architecture.md +++ b/versioned_docs/version-0.14/core-concepts/node/operator/architecture.md @@ -66,3 +66,8 @@ number of failures, preventing resource exhaustion. The threshold can be set wit The builder also exposes an internal gRPC server that the RPC component uses to proxy debugging endpoints such as `GetNoteError`. In bundled mode this is wired automatically; in distributed mode operators must set `--ntx-builder.url` (or `MIDEN_NODE_NTX_BUILDER_URL`) on the RPC component. + +Network transactions can read public foreign account state through foreign procedure invocation (FPI) while consuming a +network note. The foreign account must be public and retrievable from the store at the transaction's reference block. If +the foreign account is missing, private, or otherwise unavailable, the note execution can fail and the latest failure is +reported through [`GetNoteError`](../rpc#getnoteerror). diff --git a/versioned_docs/version-0.14/core-concepts/node/rpc.md b/versioned_docs/version-0.14/core-concepts/node/rpc.md index 9cc736a5..0e82f713 100644 --- a/versioned_docs/version-0.14/core-concepts/node/rpc.md +++ b/versioned_docs/version-0.14/core-concepts/node/rpc.md @@ -234,10 +234,15 @@ Request the status of the node components. The response contains the current ver ### GetNoteError -Returns the latest execution error for a network note, if any. This is useful for debugging notes that are failing to be consumed by the network transaction builder. +Returns the latest execution error for a network note, if any. This is the v0.14 endpoint for debugging notes that are +failing to be consumed by the network transaction builder. This endpoint is only available when the network transaction builder is enabled and connected. If it is not configured, the endpoint returns `UNAVAILABLE`. +Use this endpoint when a network note appears stuck or is repeatedly failing. For example, if a network account consumes +a note whose script performs FPI into another account, missing or unavailable foreign account data can surface here as +the latest execution error. + #### Request ```protobuf