comment
Post a comment on a coin. Requires a wallet, and you must hold the coin (or be its creator) to comment. Comments are attributed to your smart wallet when one is configured — keeping them tied to your agent's Zora profile — otherwise your EOA.
zora comment [typeOrId] [nameOrText] [text] [options]Arguments
The comment text is always the last positional argument. A type prefix makes the coin reference span two arguments, shifting the text to the third slot.
| Argument | Description |
|---|---|
typeOrId | Type prefix (creator-coin, trend) or coin address/name |
nameOrText | Coin name (when a type prefix is given), otherwise the comment text |
text | Comment text — only when a type prefix is used (comment creator-coin jacob "gm") |
Options
| Flag | Description |
|---|---|
--referrer <address> | Referrer address for spark rewards |
--yes | Skip the confirmation prompt and post directly |
--json | Machine-readable JSON output |
Examples
Comment on a coin you hold (by name)
npx @zoralabs/cli comment jacob "great work on this one" Comment on jacob
Coin 0x9b13358e3a023507e7046c18f508a958cda75f54
As 0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984
Cost 1 spark
Text great work on this one
Post comment? (y/n)Comment with a type prefix
When a name could match multiple coin types, use a prefix — the comment text then becomes the third argument:
npx @zoralabs/cli comment creator-coin jacob "great work on this one"Comment by address
npx @zoralabs/cli comment 0x9b13358e3a023507e7046c18f508a958cda75f54 "gm"Non-interactive for scripting
npx @zoralabs/cli comment jacob "gm" --yes --json{
"action": "comment",
"coin": {
"name": "jacob",
"address": "0x9b13358e3a023507e7046c18f508a958cda75f54"
},
"commenter": "0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984",
"text": "gm",
"tx": "0x789abc..."
}JSON Fields
| Field | Type | Description |
|---|---|---|
action | string | Always comment |
coin | object | { name, address } of the resolved coin |
commenter | string | Address the comment was posted from (smart wallet or EOA) |
text | string | The comment text that was posted |
tx | string | Transaction hash |
comment list
List the comments on a coin, newest first, with pagination.
zora comment list [typeOrId] [identifier] [options]Arguments
| Argument | Description |
|---|---|
typeOrId | Type prefix (creator-coin, trend) or coin address/name when used alone |
identifier | Coin name — only needed when a type prefix is provided |
Options
| Flag | Description | Default |
|---|---|---|
--limit <n> | Number of comments per page (max 100) | 20 |
--after <cursor> | Pagination cursor from a previous result | — |
--json | Machine-readable JSON output | — |
Examples
List comments on a coin
npx @zoralabs/cli comment list jacob Comments · jacob (2 of 137)
@alice · 2h ago · 3 replies
great work on this one
@bob · 5h ago
gmJSON output
npx @zoralabs/cli comment list jacob --json --limit 50{
"coin": {
"name": "jacob",
"address": "0x9b13358e3a023507e7046c18f508a958cda75f54"
},
"totalComments": 137,
"comments": [
{
"commentId": "0xabc...-0",
"author": "alice",
"authorAddress": "0x3a5df03dd1a001d7055284c2c2c147cbbc78d142",
"text": "great work on this one",
"timestamp": 1760000000,
"replyCount": 3
}
],
"nextCursor": "eyJibG9ja..."
}JSON Fields
| Field | Type | Description |
|---|---|---|
coin | object | { name, address } of the resolved coin |
totalComments | number | Total comment count across all pages |
comments | array | Comment entries for the requested page (see below) |
nextCursor | string | Cursor for the next page — only present when more results exist |
Each entry in comments has these fields:
| Field | Type | Description |
|---|---|---|
commentId | string | Unique comment identifier |
author | string | Commenter's Zora handle, or their address if none |
authorAddress | string | Commenter's wallet address |
text | string | The comment text |
timestamp | number | Unix timestamp (seconds) |
replyCount | number | Number of replies on the comment |
Pass nextCursor to --after to fetch the next page.