# TxCommentsOptions

#### Blockchain operations

* comment\_options

#### Columns

| Name                     | Description                                                                                                                                            |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| author                   | author of the post/comment (username)                                                                                                                  |
| permlink                 | a unique string identifier for the post, linked to the author of the post                                                                              |
| max\_accepted\_payout    | HBD value of the maximum payout this post will receive                                                                                                 |
| percent\_hbd             | <p>percent of payout paid in HBD, the remaining value will be paid in VESTS. <br>The value must be divided by 100 to get the real float percentage</p> |
| allow\_votes             | allows/disallows a post/comment to receive votes                                                                                                       |
| allow\_curation\_rewards | allows/disallows the voters to receive curation rewards. If set to false, curation rewards are returned to the reward pool.                            |
| extensions               | Reserved for future use                                                                                                                                |

#### Description

Authors of posts may not want all of the benefits that come from creating a post. This operation allows authors to update properties associated with their posts/comments.

Typically, these options will accompany a `comment` operation in the same transaction.

As of HF17, content creators can specify beneficiaries to receive a part of their author rewards. The list of beneficiaries is specified in the extension field of the `comment_options` operation and is a sorted array (by account name) of account and weight pairs. The beneficiaries can only be specified once and must be specified before any votes are cast on the comment. Most apps are adding the`comment_options` operation in the same transaction that creates the comment.

**Notes:**

* The max\_accepted\_payout may be decreased, but never increased.
* The percent\_hbd may be decreased, but never increased.
* `beneficiaries` array
* * Must have at least one item (empty `beneficiaries` is not allowed).
  * Cannot have more than 127 (witness currently only allow up to 8).
  * Cannot allocate more than 100% of rewards to one account.
  * Cannot allocate more than 100% of rewards to a comment.
  * Must be specified in sorted order (account ascending; no duplicates).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hivesql.io/technical-informations/operations/txcommentsoptions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.