Get desktop application:
View/edit binary Protocol Buffers messages
Represents a committed note. A committed note is a note that has been included in a block.
Used in:
Either private, public, or network note.
The data needed to prove that the note is present in the chain.
Represents the result of getting committed notes.
Used as response type in: rpc.Api.GetNotesById
List of committed notes.
Represents a network note. Network notes are a subtype of public notes, and as such, their details are always publicly known.
The note's metadata.
Serialized note details (i.e., assets and recipient).
Serialized `miden_protocol::note::NoteAttachments`. Empty bytes encode an empty collection.
Represents a note. The note is composed of the note metadata, its serialized details, and serialized attachments.
Used in:
The note's metadata.
Serialized note details (empty for private notes).
Serialized `miden_protocol::note::NoteAttachments`. Empty bytes encode an empty collection.
Represents a note header. A note header consists of a commitment to the note's details and its metadata.
Used in: ,
Commitment to the note's details (recipient + assets), excluding metadata.
The note's metadata.
Represents a note's ID.
Used as request type in: ntx_builder.Api.GetNetworkNoteStatus, rpc.Api.GetNetworkNoteStatus
Used as field type in: ,
A unique identifier of the note which is a 32-byte commitment to the underlying note data.
List of note IDs.
Used as request type in: rpc.Api.GetNotesById
List of note IDs to be queried from the database.
Represents a proof of note's inclusion in a block. Does not include proof of the block's inclusion in the chain.
Used in: , ,
A unique identifier of the note which is a 32-byte commitment to the underlying note data.
The block number in which the note was created.
The index of the note in the block.
The note's inclusion proof in the block.
Represents a note's metadata. Mirrors the protocol-level `miden_protocol::note::NoteMetadata`: it carries the partial metadata (sender, note type, tag), the per-slot attachment schemes, and the commitment over the note's attachments. The full attachment contents (when present) are carried separately on `Note` / `NetworkNote`.
Used in: , , ,
The account which sent the note.
The type of the note.
A value which can be used by the recipient(s) to identify notes intended for them. See `miden_protocol::note::note_tag` for more info.
The attachment scheme of each attachment slot. The protocol allows up to `NoteAttachments::MAX_COUNT` attachments per note. Each slot carries either a scheme value in `1..=65534` or `0` to indicate that the slot is absent. Trailing absent slots may be omitted, so a note with no attachments has an empty list. See `miden_protocol::note::NoteAttachmentHeader` for more info.
Commitment over the note's attachments. See `miden_protocol::note::NoteAttachments::to_commitment` for more info.
Represents a note script.
Used in:
Entrypoint of the script.
MAST of the script.
Represents a commitment to a note script.
Used as request type in: rpc.Api.GetNoteScriptByRoot
Root of the note script.
Represents a note's metadata together with proof of inclusion in a block. To get the full note (including attachment contents), use `GetNotesById`.
Used in:
The metadata of the note.
Proof of the note's inclusion in a block.
The type of a note.
Used in:
Unspecified note type (default value, should not be used).
Public note - details are visible on-chain.
Private note - details are not visible on-chain.