remark_with_event
Call v101 → current #7Post data on-chain and emit a Remarked event .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with remark_with_event, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: Remarked, and finally post-dispatch where ExtrinsicSuccess is emitted and fees are settled.
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Click items to navigate. Pan and zoom to explore.
Used by: developersanalytics
The Big Picture
Like remark, but emits an event with the data hash, making it indexable and searchable.
Use Cases
- Timestamping with easy indexing
- Application-level messaging
- Searchable audit logs
From Chain Metadata
Make some on-chain remark and emit event.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | remark | Vec<u8> Vec | remark (Vec<u8>) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Signed by any account
- Sufficient balance for transaction fee
Effects
Events Emitted
Postconditions
- Data hash included in Remarked event
- Event recorded in System.Events
Side Effects
- Data permanently anchored to blockchain
- Event can be indexed
Code Examples
import { ApiPromise, WsProvider } from "@polkadot/api";
import { stringCamelCase } from "@polkadot/util";
const provider = new WsProvider("wss://entrypoint-finney.opentensor.ai:443");
const api = await ApiPromise.create({ provider });
// Build remark_with_event call
const remark = 0;
const call = api.tx[stringCamelCase("System")][stringCamelCase("remark_with_event")](
remark
);Runtime Info
- Pallet Index
- 0
- Call Index
- 7
- First Version
- v101
- Current Version
- v393