Feat/chain upgrade v1.14 #173
Conversation
…d all permissions module documentation to the new module's logic
…d all permissions module documentation to the new module's logic
…veLabs/docs into feat/chain_upgrade_v1_14
WalkthroughThis pull request expands API documentation and client functionality across multiple modules. A new gRPC endpoint, InjBurntEndpoint, is introduced for fetching the total INJ burnt in auctions with corresponding client methods in Python and Go. In addition, new parameters and endpoints are added to binary options, chain exchange, derivatives, spot markets, and the tokenfactory module. Several JSON schema files are added, updated, or removed across exchange, permissions, indexer, and explorer directories to clarify parameter definitions and response structures, without modifying existing logic. Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant AuctionsRPC
Client->>AuctionsRPC: Request: fetch_inj_burnt()
AuctionsRPC->>AuctionsRPC: Process request (retrieve total INJ burnt)
AuctionsRPC-->>Client: Response: { total_inj_burnt: Decimal }
Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🔭 Outside diff range comments (1)
source/includes/_derivativesrpc.md (1)
4685-4688:⚠️ Potential issueFix JSON Formatting in BinaryOptionsMarket Response Example
In the JSON example for the BinaryOptionsMarket response (around line 4685–4688), the object representing the TokenMeta has an error:"decimals":18;uses a semicolon instead of a comma. Please change it to"decimals": 18,to meet valid JSON syntax.
🧹 Nitpick comments (29)
source/json_tables/chain/permissions/queryRoleManagerRequest.json (1)
2-3: Consider Using Boolean for the "Required" FieldCurrently, the "Required" property is provided as the string "Yes". For improved consistency and programmatic clarity, consider using a boolean value (e.g.,
trueinstead of"Yes") if it aligns with other JSON schemas in the project. Verify with the documentation standards before making a change.source/json_tables/chain/permissions/queryActorsByRoleResponse.json (1)
2-2: Consistency of Type DeclarationThe "Type" field is specified as "String Array". Please verify that this format is consistent with other JSON schema files in the repository. If the documentation standards prefer an alternative notation (e.g., "array[string]"), consider updating for consistency.
source/json_tables/chain/permissions/queryVouchersResponse.json (1)
1-3: JSON Structure and Naming ConsistencyThe JSON structure is syntactically correct and clearly documents a response parameter. However, note that:
- The AI summary mentioned a parameter named "voucher" of type "Coin", but the file defines "vouchers" with type "AddressVoucher Array". Please verify that this difference (singular vs. plural and the type definition) is intentional and consistent with the overall API documentation.
- Consider clarifying the type definition. If the intention is to represent an array of AddressVoucher objects, a more conventional type annotation (e.g.,
"AddressVoucher[]"or"Array of AddressVoucher") might improve readability.source/json_tables/chain/exchange/queryFullSpotOrderbookRequest.json (1)
1-3: Clear and Consistent JSON Schema for Request ParameterThe JSON array defines the required
market_idparameter accurately. The key attributes ("Parameter", "Type", "Description", "Required") are straightforward and consistent with similar request schema definitions.Suggestion: Consider using a boolean (e.g.,
"Required": true) if your JSON schema definitions conventionally favor booleans over strings. If this file needs to remain consistent with existing documentation, the current approach is acceptable.source/json_tables/indexer/explorer/getBankTransfersResponse.json (1)
1-4: Well-Documented Bank Transfers Response.
This schema properly conveys the response structure by including "paging" (of type Paging) and "data" (a BankTransfer Array). For absolute clarity, consider if the term "BankTransfer Array" might be better expressed as "Array of BankTransfer"—provided that change does not affect compatibility with existing documentation.source/json_tables/indexer/explorer/getValidatorsResponse.json (1)
1-5: Clean Validator Response Documentation.
The file defines the response with three parameters: "s" for status, "errmsg" for error messages, and "data" for validator details. While the concise key "s" is consistent with similar documents, consider renaming it to "status" if clearer semantics are desired and such a change is acceptable in the broader documentation context.source/json_tables/indexer/explorer/getValidatorResponse.json (1)
1-5: Consistent and Clear Validator Response.
This schema mirrors the structure defined in the previous file by specifying "s", "errmsg", and "data" (of type Validator). For improved clarity, you may want to evaluate whether "s" could be replaced with "status"—especially if future contributors might benefit from more descriptive parameter names.source/json_tables/chain/permissions/role.json (1)
2-4: Correct typographical error in "permissions" description.
The description for the "permissions" parameter currently uses "bitwhise"; this should be corrected to "bitwise" for clarity and professionalism.-{"Parameter": "permissions", "Type": "Integer", "Description": "Integer representing the bitwhise combination of all actions assigned to the role"} +{"Parameter": "permissions", "Type": "Integer", "Description": "Integer representing the bitwise combination of all actions assigned to the role"}source/json_tables/indexer/explorer/signature.json (1)
1-6: Fix typographical error in the "sequence" parameter description.
The description currently reads "Sinature sequence number" which should be corrected to "Signature sequence number."-{"Parameter": "sequence", "Type": "Integer", "Description": "Sinature sequence number"}, +{"Parameter": "sequence", "Type": "Integer", "Description": "Signature sequence number"},source/json_tables/chain/permissions/actions.json (1)
1-12: Action Codes JSON Array: Consider Type Consistency.The array nicely lists action objects with their associated codes and names. One thing to consider is whether the "Code" values should be represented as numeric types instead of strings if these values are to be used in numerical comparisons or computations. If string types are intentional for documentation purposes, this comment can be safely ignored.
source/json_tables/indexer/explorer/validatorDescription.json (1)
1-8: Validator Description JSON: Enhance the "details" Field.The structure is well defined, but the "details" parameter currently has an empty description. It would be beneficial to add a brief description for this field (e.g., "Additional details about the validator") to ensure complete documentation.
source/json_tables/indexer/explorer/paging.json (1)
1-7: Paging Parameters: Clarify Field Naming.The JSON structure accurately reflects the parameters for pagination. Consider using "transactions" instead of the abbreviation "txs" in the "total" description to ensure clarity for all readers. Also, verify that the explanation for "from" and "to" (being either a block height or index number) is sufficiently documented in the broader API documentation.
source/json_tables/indexer/explorer/getContractTxsRequest.json (1)
1-7: Well-Documented Request Structure for Contract TransactionsThe file accurately lists all parameters with clear descriptions. One minor suggestion is to refine the descriptions for "from_number" and "to_number" to explicitly state that they serve as filters for contract numbers (e.g., "Filter contracts to only include those with numbers greater than or equal to from_number").
source/json_tables/indexer/derivative/auctionEndpointRequest.json (2)
6-6: Typographical Correction in Pagination Description
On line 6, "Will skipt the first N items" contains a typo. Please change "skipt" to "skip" for clarity.
11-11: Typographical Correction in Parameter Name
The parameter "subacount_ids" appears to have a typographical error. Consider renaming it to "subaccount_ids" to ensure consistency with naming conventions across the codebase.source/json_tables/indexer/derivative/streamTradesV2Request.json (2)
6-6: Typo in the "skip" parameter description.
The description currently reads "Will skipt the first N items from the result" which contains a typo. Please change "skipt" to "skip" for clarity.- {"Parameter": "skip", "Type": "Integer", "Description": "Will skipt the first N items from the result", "Required": "No"}, + {"Parameter": "skip", "Type": "Integer", "Description": "Will skip the first N items from the result", "Required": "No"},
11-11: Typo in the "subacount_ids" parameter name.
The parameter name "subacount_ids" appears to have a misspelling. We recommend changing it to "subaccount_ids" to maintain consistency with other related fields.- {"Parameter": "subacount_ids", "Type": "String Array", "Description": "Subaccount ids of traders we want to get trades. Use this field for fetching trades from multiple subaccounts", "Required": "No"}, + {"Parameter": "subaccount_ids", "Type": "String Array", "Description": "Subaccount ids of traders we want to get trades. Use this field for fetching trades from multiple subaccounts", "Required": "No"},source/json_tables/indexer/derivative/tradesV2Request.json (2)
6-6: Typo in the "skip" parameter description.
Similar to the previous schema, the description uses "Will skipt" which should be corrected to "Will skip".- {"Parameter": "skip", "Type": "Integer", "Description": "Will skipt the first N items from the result", "Required": "No"}, + {"Parameter": "skip", "Type": "Integer", "Description": "Will skip the first N items from the result", "Required": "No"},
11-11: Typo in the "subacount_ids" parameter name.
Update "subacount_ids" to "subaccount_ids" for consistency and to avoid confusion.- {"Parameter": "subacount_ids", "Type": "String Array", "Description": "Subaccount ids of traders we want to get trades. Use this field for fetching trades from multiple subaccounts", "Required": "No"}, + {"Parameter": "subaccount_ids", "Type": "String Array", "Description": "Subaccount ids of traders we want to get trades. Use this field for fetching trades from multiple subaccounts", "Required": "No"},source/json_tables/indexer/explorer/validator.json (2)
6-6: Typo in the "jailed" parameter description.
The description currently reads "Validator's jain status"; "jain" appears to be a typo. Kindly update it to "Validator's jailed status".- {"Parameter": "jailed", "Type": "Boolean", "Description": "Validator's jain status"}, + {"Parameter": "jailed", "Type": "Boolean", "Description": "Validator's jailed status"},
23-23: Minor wording refinement for uptime percentage description.
The description "Uptime percentage base on latest 10k block" could be refined for clarity. Consider updating it to "Uptime percentage based on the latest 10k blocks".- {"Parameter": "uptime_percentage", "Type": "Float", "Description": "Uptime percentage base on latest 10k block"}, + {"Parameter": "uptime_percentage", "Type": "Float", "Description": "Uptime percentage based on the latest 10k blocks"},source/json_tables/chain/exchange/derivativeMarket.json (1)
20-21: New Parameter Additions – "admin_permissions" and "quote_decimals":
The re-addition of the “admin_permissions” parameter and the addition of “quote_decimals” are clear. Please verify that the description and type details are consistent with those in related JSON schemas (for example, in binary options market).source/includes/_auctionsrpc.md (1)
431-465: Formatting Note on Hard Tabs:
Static analysis has flagged several occurrences of hard tabs (MD010) in this markdown file. Converting these to spaces will improve consistency and help meet markdownlint guidelines.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
431-431: Hard tabs
Column: 1(MD010, no-hard-tabs)
432-432: Hard tabs
Column: 1(MD010, no-hard-tabs)
433-433: Hard tabs
Column: 1(MD010, no-hard-tabs)
434-434: Hard tabs
Column: 1(MD010, no-hard-tabs)
436-436: Hard tabs
Column: 1(MD010, no-hard-tabs)
437-437: Hard tabs
Column: 1(MD010, no-hard-tabs)
441-441: Hard tabs
Column: 1(MD010, no-hard-tabs)
442-442: Hard tabs
Column: 1(MD010, no-hard-tabs)
443-443: Hard tabs
Column: 1(MD010, no-hard-tabs)
444-444: Hard tabs
Column: 1(MD010, no-hard-tabs)
445-445: Hard tabs
Column: 1(MD010, no-hard-tabs)
447-447: Hard tabs
Column: 1(MD010, no-hard-tabs)
448-448: Hard tabs
Column: 1(MD010, no-hard-tabs)
450-450: Hard tabs
Column: 1(MD010, no-hard-tabs)
451-451: Hard tabs
Column: 1(MD010, no-hard-tabs)
452-452: Hard tabs
Column: 1(MD010, no-hard-tabs)
453-453: Hard tabs
Column: 1(MD010, no-hard-tabs)
454-454: Hard tabs
Column: 1(MD010, no-hard-tabs)
455-455: Hard tabs
Column: 1(MD010, no-hard-tabs)
457-457: Hard tabs
Column: 1(MD010, no-hard-tabs)
458-458: Hard tabs
Column: 1(MD010, no-hard-tabs)
459-459: Hard tabs
Column: 1(MD010, no-hard-tabs)
460-460: Hard tabs
Column: 1(MD010, no-hard-tabs)
461-461: Hard tabs
Column: 1(MD010, no-hard-tabs)
462-462: Hard tabs
Column: 1(MD010, no-hard-tabs)
464-464: Hard tabs
Column: 1(MD010, no-hard-tabs)
465-465: Hard tabs
Column: 1(MD010, no-hard-tabs)
source/includes/_derivativesrpc.md (3)
1411-1415: Typo Notice in TradesV2 Description
In the explanatory text for TradesV2 (around line 1414), the phrase “compatible witht the one used for trade events in chain stream” contains a typo. Please correct “witht” to “with”.
1951-1967: Review HTML Table for StreamTradesV2 Request Parameters
The auto-generated HTML table (from line 1951) for the StreamTradesV2 request parameters is generally clear; however, the description for the “skip” parameter contains a typographical error (“Will skipt the first N items from the result”). Please update “skipt” to “skip”. Also, verify that all parameter details (names, types, and requirements) are fully consistent with the updated API.
1-4874: Overall Documentation Consistency and Clarity
This documentation update is extensive and introduces several v2 endpoints (e.g. for positions, orderbooks, and trades) alongside improved response examples and HTML table formats. Please ensure that:
• All updated method names (such aslisten_derivative_positions_v2_updates,fetch_derivative_orderbooks_v2, andfetch_derivative_trades_v2) appear uniformly across all examples in both Python and Go.
• Parameter naming conventions (camelCase vs. snake_case) and response structures are consistent and clearly explained.
• Any cross-references to similar modules (e.g. the permissions or spot modules) are updated so that users have a coherent view of the API changes.
Overall, the changes significantly enhance clarity. A final cross-check with the client libraries might help catch any residual inconsistencies.source/includes/_chainexchange.md (1)
4526-5010: Consider using spaces instead of tabs in code examplesThe Go code examples contain hard tabs which can cause inconsistent formatting across different editors and platforms.
Consider replacing tabs with spaces in the code examples for better consistency:
- "context" - "encoding/json" - "fmt" - "os" + "context" + "encoding/json" + "fmt" + "os"🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
4526-4526: Hard tabs
Column: 1(MD010, no-hard-tabs)
4527-4527: Hard tabs
Column: 1(MD010, no-hard-tabs)
4528-4528: Hard tabs
Column: 1(MD010, no-hard-tabs)
4529-4529: Hard tabs
Column: 1(MD010, no-hard-tabs)
4530-4530: Hard tabs
Column: 1(MD010, no-hard-tabs)
4532-4532: Hard tabs
Column: 1(MD010, no-hard-tabs)
4534-4534: Hard tabs
Column: 1(MD010, no-hard-tabs)
4535-4535: Hard tabs
Column: 1(MD010, no-hard-tabs)
4536-4536: Hard tabs
Column: 1(MD010, no-hard-tabs)
4540-4540: Hard tabs
Column: 1(MD010, no-hard-tabs)
4541-4541: Hard tabs
Column: 1(MD010, no-hard-tabs)
4542-4542: Hard tabs
Column: 1(MD010, no-hard-tabs)
4543-4543: Hard tabs
Column: 1(MD010, no-hard-tabs)
4544-4544: Hard tabs
Column: 1(MD010, no-hard-tabs)
4546-4546: Hard tabs
Column: 1(MD010, no-hard-tabs)
4547-4547: Hard tabs
Column: 1(MD010, no-hard-tabs)
4548-4548: Hard tabs
Column: 1(MD010, no-hard-tabs)
4549-4549: Hard tabs
Column: 1(MD010, no-hard-tabs)
4550-4550: Hard tabs
Column: 1(MD010, no-hard-tabs)
4551-4551: Hard tabs
Column: 1(MD010, no-hard-tabs)
4552-4552: Hard tabs
Column: 1(MD010, no-hard-tabs)
4553-4553: Hard tabs
Column: 1(MD010, no-hard-tabs)
4554-4554: Hard tabs
Column: 1(MD010, no-hard-tabs)
4556-4556: Hard tabs
Column: 1(MD010, no-hard-tabs)
4557-4557: Hard tabs
Column: 1(MD010, no-hard-tabs)
4558-4558: Hard tabs
Column: 1(MD010, no-hard-tabs)
4560-4560: Hard tabs
Column: 1(MD010, no-hard-tabs)
4561-4561: Hard tabs
Column: 1(MD010, no-hard-tabs)
4562-4562: Hard tabs
Column: 1(MD010, no-hard-tabs)
4563-4563: Hard tabs
Column: 1(MD010, no-hard-tabs)
4564-4564: Hard tabs
Column: 1(MD010, no-hard-tabs)
4566-4566: Hard tabs
Column: 1(MD010, no-hard-tabs)
4567-4567: Hard tabs
Column: 1(MD010, no-hard-tabs)
4568-4568: Hard tabs
Column: 1(MD010, no-hard-tabs)
4570-4570: Hard tabs
Column: 1(MD010, no-hard-tabs)
4572-4572: Hard tabs
Column: 1(MD010, no-hard-tabs)
4573-4573: Hard tabs
Column: 1(MD010, no-hard-tabs)
4574-4574: Hard tabs
Column: 1(MD010, no-hard-tabs)
4575-4575: Hard tabs
Column: 1(MD010, no-hard-tabs)
4576-4576: Hard tabs
Column: 1(MD010, no-hard-tabs)
4578-4578: Hard tabs
Column: 1(MD010, no-hard-tabs)
4580-4580: Hard tabs
Column: 1(MD010, no-hard-tabs)
4581-4581: Hard tabs
Column: 1(MD010, no-hard-tabs)
4582-4582: Hard tabs
Column: 1(MD010, no-hard-tabs)
4583-4583: Hard tabs
Column: 1(MD010, no-hard-tabs)
4585-4585: Hard tabs
Column: 1(MD010, no-hard-tabs)
4586-4586: Hard tabs
Column: 1(MD010, no-hard-tabs)
4658-4658: Hard tabs
Column: 1(MD010, no-hard-tabs)
4659-4659: Hard tabs
Column: 1(MD010, no-hard-tabs)
4660-4660: Hard tabs
Column: 1(MD010, no-hard-tabs)
4661-4661: Hard tabs
Column: 1(MD010, no-hard-tabs)
4662-4662: Hard tabs
Column: 1(MD010, no-hard-tabs)
4664-4664: Hard tabs
Column: 1(MD010, no-hard-tabs)
4666-4666: Hard tabs
Column: 1(MD010, no-hard-tabs)
4667-4667: Hard tabs
Column: 1(MD010, no-hard-tabs)
4668-4668: Hard tabs
Column: 1(MD010, no-hard-tabs)
4672-4672: Hard tabs
Column: 1(MD010, no-hard-tabs)
4673-4673: Hard tabs
Column: 1(MD010, no-hard-tabs)
4674-4674: Hard tabs
Column: 1(MD010, no-hard-tabs)
4675-4675: Hard tabs
Column: 1(MD010, no-hard-tabs)
4676-4676: Hard tabs
Column: 1(MD010, no-hard-tabs)
4678-4678: Hard tabs
Column: 1(MD010, no-hard-tabs)
4679-4679: Hard tabs
Column: 1(MD010, no-hard-tabs)
4680-4680: Hard tabs
Column: 1(MD010, no-hard-tabs)
4681-4681: Hard tabs
Column: 1(MD010, no-hard-tabs)
4682-4682: Hard tabs
Column: 1(MD010, no-hard-tabs)
4683-4683: Hard tabs
Column: 1(MD010, no-hard-tabs)
4684-4684: Hard tabs
Column: 1(MD010, no-hard-tabs)
4685-4685: Hard tabs
Column: 1(MD010, no-hard-tabs)
4686-4686: Hard tabs
Column: 1(MD010, no-hard-tabs)
4688-4688: Hard tabs
Column: 1(MD010, no-hard-tabs)
4689-4689: Hard tabs
Column: 1(MD010, no-hard-tabs)
4690-4690: Hard tabs
Column: 1(MD010, no-hard-tabs)
4692-4692: Hard tabs
Column: 1(MD010, no-hard-tabs)
4693-4693: Hard tabs
Column: 1(MD010, no-hard-tabs)
4694-4694: Hard tabs
Column: 1(MD010, no-hard-tabs)
4695-4695: Hard tabs
Column: 1(MD010, no-hard-tabs)
4696-4696: Hard tabs
Column: 1(MD010, no-hard-tabs)
4698-4698: Hard tabs
Column: 1(MD010, no-hard-tabs)
4699-4699: Hard tabs
Column: 1(MD010, no-hard-tabs)
4700-4700: Hard tabs
Column: 1(MD010, no-hard-tabs)
4702-4702: Hard tabs
Column: 1(MD010, no-hard-tabs)
4704-4704: Hard tabs
Column: 1(MD010, no-hard-tabs)
4705-4705: Hard tabs
Column: 1(MD010, no-hard-tabs)
4706-4706: Hard tabs
Column: 1(MD010, no-hard-tabs)
4707-4707: Hard tabs
Column: 1(MD010, no-hard-tabs)
4708-4708: Hard tabs
Column: 1(MD010, no-hard-tabs)
4710-4710: Hard tabs
Column: 1(MD010, no-hard-tabs)
4711-4711: Hard tabs
Column: 1(MD010, no-hard-tabs)
4712-4712: Hard tabs
Column: 1(MD010, no-hard-tabs)
4713-4713: Hard tabs
Column: 1(MD010, no-hard-tabs)
4715-4715: Hard tabs
Column: 1(MD010, no-hard-tabs)
4716-4716: Hard tabs
Column: 1(MD010, no-hard-tabs)
4760-4760: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
4820-4820: Hard tabs
Column: 1(MD010, no-hard-tabs)
4821-4821: Hard tabs
Column: 1(MD010, no-hard-tabs)
4822-4822: Hard tabs
Column: 1(MD010, no-hard-tabs)
4823-4823: Hard tabs
Column: 1(MD010, no-hard-tabs)
4824-4824: Hard tabs
Column: 1(MD010, no-hard-tabs)
4826-4826: Hard tabs
Column: 1(MD010, no-hard-tabs)
4828-4828: Hard tabs
Column: 1(MD010, no-hard-tabs)
4829-4829: Hard tabs
Column: 1(MD010, no-hard-tabs)
4830-4830: Hard tabs
Column: 1(MD010, no-hard-tabs)
4834-4834: Hard tabs
Column: 1(MD010, no-hard-tabs)
4835-4835: Hard tabs
Column: 1(MD010, no-hard-tabs)
4836-4836: Hard tabs
Column: 1(MD010, no-hard-tabs)
4837-4837: Hard tabs
Column: 1(MD010, no-hard-tabs)
4838-4838: Hard tabs
Column: 1(MD010, no-hard-tabs)
4840-4840: Hard tabs
Column: 1(MD010, no-hard-tabs)
4841-4841: Hard tabs
Column: 1(MD010, no-hard-tabs)
4842-4842: Hard tabs
Column: 1(MD010, no-hard-tabs)
4843-4843: Hard tabs
Column: 1(MD010, no-hard-tabs)
4844-4844: Hard tabs
Column: 1(MD010, no-hard-tabs)
4845-4845: Hard tabs
Column: 1(MD010, no-hard-tabs)
4846-4846: Hard tabs
Column: 1(MD010, no-hard-tabs)
4847-4847: Hard tabs
Column: 1(MD010, no-hard-tabs)
4848-4848: Hard tabs
Column: 1(MD010, no-hard-tabs)
4850-4850: Hard tabs
Column: 1(MD010, no-hard-tabs)
4851-4851: Hard tabs
Column: 1(MD010, no-hard-tabs)
4852-4852: Hard tabs
Column: 1(MD010, no-hard-tabs)
4854-4854: Hard tabs
Column: 1(MD010, no-hard-tabs)
4855-4855: Hard tabs
Column: 1(MD010, no-hard-tabs)
4856-4856: Hard tabs
Column: 1(MD010, no-hard-tabs)
4857-4857: Hard tabs
Column: 1(MD010, no-hard-tabs)
4858-4858: Hard tabs
Column: 1(MD010, no-hard-tabs)
4860-4860: Hard tabs
Column: 1(MD010, no-hard-tabs)
4861-4861: Hard tabs
Column: 1(MD010, no-hard-tabs)
4862-4862: Hard tabs
Column: 1(MD010, no-hard-tabs)
4864-4864: Hard tabs
Column: 1(MD010, no-hard-tabs)
4866-4866: Hard tabs
Column: 1(MD010, no-hard-tabs)
4867-4867: Hard tabs
Column: 1(MD010, no-hard-tabs)
4868-4868: Hard tabs
Column: 1(MD010, no-hard-tabs)
4869-4869: Hard tabs
Column: 1(MD010, no-hard-tabs)
4870-4870: Hard tabs
Column: 1(MD010, no-hard-tabs)
4872-4872: Hard tabs
Column: 1(MD010, no-hard-tabs)
4874-4874: Hard tabs
Column: 1(MD010, no-hard-tabs)
4875-4875: Hard tabs
Column: 1(MD010, no-hard-tabs)
4876-4876: Hard tabs
Column: 1(MD010, no-hard-tabs)
4877-4877: Hard tabs
Column: 1(MD010, no-hard-tabs)
4879-4879: Hard tabs
Column: 1(MD010, no-hard-tabs)
4880-4880: Hard tabs
Column: 1(MD010, no-hard-tabs)
4952-4952: Hard tabs
Column: 1(MD010, no-hard-tabs)
4953-4953: Hard tabs
Column: 1(MD010, no-hard-tabs)
4954-4954: Hard tabs
Column: 1(MD010, no-hard-tabs)
4955-4955: Hard tabs
Column: 1(MD010, no-hard-tabs)
4956-4956: Hard tabs
Column: 1(MD010, no-hard-tabs)
4958-4958: Hard tabs
Column: 1(MD010, no-hard-tabs)
4960-4960: Hard tabs
Column: 1(MD010, no-hard-tabs)
4961-4961: Hard tabs
Column: 1(MD010, no-hard-tabs)
4962-4962: Hard tabs
Column: 1(MD010, no-hard-tabs)
4966-4966: Hard tabs
Column: 1(MD010, no-hard-tabs)
4967-4967: Hard tabs
Column: 1(MD010, no-hard-tabs)
4968-4968: Hard tabs
Column: 1(MD010, no-hard-tabs)
4969-4969: Hard tabs
Column: 1(MD010, no-hard-tabs)
4970-4970: Hard tabs
Column: 1(MD010, no-hard-tabs)
4972-4972: Hard tabs
Column: 1(MD010, no-hard-tabs)
4973-4973: Hard tabs
Column: 1(MD010, no-hard-tabs)
4974-4974: Hard tabs
Column: 1(MD010, no-hard-tabs)
4975-4975: Hard tabs
Column: 1(MD010, no-hard-tabs)
4976-4976: Hard tabs
Column: 1(MD010, no-hard-tabs)
4977-4977: Hard tabs
Column: 1(MD010, no-hard-tabs)
4978-4978: Hard tabs
Column: 1(MD010, no-hard-tabs)
4979-4979: Hard tabs
Column: 1(MD010, no-hard-tabs)
4980-4980: Hard tabs
Column: 1(MD010, no-hard-tabs)
4982-4982: Hard tabs
Column: 1(MD010, no-hard-tabs)
4983-4983: Hard tabs
Column: 1(MD010, no-hard-tabs)
4984-4984: Hard tabs
Column: 1(MD010, no-hard-tabs)
4986-4986: Hard tabs
Column: 1(MD010, no-hard-tabs)
4987-4987: Hard tabs
Column: 1(MD010, no-hard-tabs)
4988-4988: Hard tabs
Column: 1(MD010, no-hard-tabs)
4989-4989: Hard tabs
Column: 1(MD010, no-hard-tabs)
4990-4990: Hard tabs
Column: 1(MD010, no-hard-tabs)
4992-4992: Hard tabs
Column: 1(MD010, no-hard-tabs)
4993-4993: Hard tabs
Column: 1(MD010, no-hard-tabs)
4994-4994: Hard tabs
Column: 1(MD010, no-hard-tabs)
4996-4996: Hard tabs
Column: 1(MD010, no-hard-tabs)
4998-4998: Hard tabs
Column: 1(MD010, no-hard-tabs)
4999-4999: Hard tabs
Column: 1(MD010, no-hard-tabs)
5000-5000: Hard tabs
Column: 1(MD010, no-hard-tabs)
5001-5001: Hard tabs
Column: 1(MD010, no-hard-tabs)
5002-5002: Hard tabs
Column: 1(MD010, no-hard-tabs)
5004-5004: Hard tabs
Column: 1(MD010, no-hard-tabs)
5005-5005: Hard tabs
Column: 1(MD010, no-hard-tabs)
5006-5006: Hard tabs
Column: 1(MD010, no-hard-tabs)
5007-5007: Hard tabs
Column: 1(MD010, no-hard-tabs)
5009-5009: Hard tabs
Column: 1(MD010, no-hard-tabs)
5010-5010: Hard tabs
Column: 1(MD010, no-hard-tabs)
source/includes/_derivatives.md (2)
1251-1252: Fix indentation in code blockThe indentation uses tabs instead of spaces which is inconsistent with the rest of the file.
- "minQuantityTickSize":"100000000000000", - "quoteDecimals":6, + "minQuantityTickSize":"100000000000000", + "quoteDecimals":6,🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
1252-1252: Hard tabs
Column: 1(MD010, no-hard-tabs)
1506-1507: Fix indentation in code blockThe indentation uses tabs instead of spaces which is inconsistent with the rest of the file.
- "minQuantityTickSize":"100000000000000" - "quoteDecimals":6, + "minQuantityTickSize":"100000000000000" + "quoteDecimals":6,🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
1507-1507: Hard tabs
Column: 1(MD010, no-hard-tabs)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (97)
source/includes/_auctionsrpc.md(1 hunks)source/includes/_binaryoptions.md(1 hunks)source/includes/_chainexchange.md(2 hunks)source/includes/_derivatives.md(5 hunks)source/includes/_derivativesrpc.md(3 hunks)source/includes/_spot.md(11 hunks)source/includes/_tokenfactory.md(3 hunks)source/json_tables/chain/exchange/binaryOptionsMarket.json(1 hunks)source/json_tables/chain/exchange/denomMinNotional.json(1 hunks)source/json_tables/chain/exchange/derivativeMarket.json(1 hunks)source/json_tables/chain/exchange/marketBalance.json(1 hunks)source/json_tables/chain/exchange/msgInstantSpotMarketLaunch.json(1 hunks)source/json_tables/chain/exchange/queryDenomMinNotionalRequest.json(1 hunks)source/json_tables/chain/exchange/queryDenomMinNotionalResponse.json(1 hunks)source/json_tables/chain/exchange/queryDenomMinNotionalsResponse.json(1 hunks)source/json_tables/chain/exchange/queryFullDerivativeOrderbookRequest.json(1 hunks)source/json_tables/chain/exchange/queryFullDerivativeOrderbookResponse.json(1 hunks)source/json_tables/chain/exchange/queryFullSpotOrderbookRequest.json(1 hunks)source/json_tables/chain/exchange/queryFullSpotOrderbookResponse.json(1 hunks)source/json_tables/chain/exchange/queryMarketBalanceRequest.json(1 hunks)source/json_tables/chain/exchange/queryMarketBalanceResponse.json(1 hunks)source/json_tables/chain/exchange/queryMarketBalancesResponse.json(1 hunks)source/json_tables/chain/exchange/spotMarket.json(1 hunks)source/json_tables/chain/exchange/trimmedLimitOrder.json(1 hunks)source/json_tables/chain/permissions/actions.json(1 hunks)source/json_tables/chain/permissions/actorRoles.json(1 hunks)source/json_tables/chain/permissions/addressRoles.json(0 hunks)source/json_tables/chain/permissions/addressVoucher.json(1 hunks)source/json_tables/chain/permissions/genesisState.json(1 hunks)source/json_tables/chain/permissions/msgDeleteNamespace.json(0 hunks)source/json_tables/chain/permissions/msgRevokeNamespaceRoles.json(0 hunks)source/json_tables/chain/permissions/msgUpdateActorRoles.json(1 hunks)source/json_tables/chain/permissions/msgUpdateNamespace.json(1 hunks)source/json_tables/chain/permissions/msgUpdateNamespaceRoles.json(0 hunks)source/json_tables/chain/permissions/msgUpdateNamespace_SetContractHook.json(1 hunks)source/json_tables/chain/permissions/namespace.json(1 hunks)source/json_tables/chain/permissions/params.json(1 hunks)source/json_tables/chain/permissions/permissionAction.json(0 hunks)source/json_tables/chain/permissions/policyManagerCapability.json(1 hunks)source/json_tables/chain/permissions/policyStatus.json(1 hunks)source/json_tables/chain/permissions/queryActorsByRoleRequest.json(1 hunks)source/json_tables/chain/permissions/queryActorsByRoleResponse.json(1 hunks)source/json_tables/chain/permissions/queryAddressesByRoleResponse.json(0 hunks)source/json_tables/chain/permissions/queryModuleStateResponse.json(1 hunks)source/json_tables/chain/permissions/queryNamespaceByDenomRequest.json(0 hunks)source/json_tables/chain/permissions/queryNamespaceDenomsResponse.json(1 hunks)source/json_tables/chain/permissions/queryNamespaceRequest.json(1 hunks)source/json_tables/chain/permissions/queryNamespaceResponse.json(1 hunks)source/json_tables/chain/permissions/queryPolicyManagerCapabilitiesRequest.json(1 hunks)source/json_tables/chain/permissions/queryPolicyManagerCapabilitiesResponse.json(1 hunks)source/json_tables/chain/permissions/queryPolicyStatusesRequest.json(1 hunks)source/json_tables/chain/permissions/queryPolicyStatusesResponse.json(1 hunks)source/json_tables/chain/permissions/queryRoleManagerRequest.json(1 hunks)source/json_tables/chain/permissions/queryRoleManagerResponse.json(1 hunks)source/json_tables/chain/permissions/queryRoleManagersRequest.json(1 hunks)source/json_tables/chain/permissions/queryRoleManagersResponse.json(1 hunks)source/json_tables/chain/permissions/queryRolesByActorRequest.json(1 hunks)source/json_tables/chain/permissions/queryRolesByActorResponse.json(1 hunks)source/json_tables/chain/permissions/queryVoucherRequest.json(1 hunks)source/json_tables/chain/permissions/queryVoucherResponse.json(1 hunks)source/json_tables/chain/permissions/queryVouchersForAddressRequest.json(0 hunks)source/json_tables/chain/permissions/queryVouchersForAddressResponse.json(0 hunks)source/json_tables/chain/permissions/queryVouchersRequest.json(1 hunks)source/json_tables/chain/permissions/queryVouchersResponse.json(1 hunks)source/json_tables/chain/permissions/role.json(1 hunks)source/json_tables/chain/permissions/roleActors.json(1 hunks)source/json_tables/chain/permissions/roleManager.json(1 hunks)source/json_tables/indexer/auction/injBurntEndpointResponse.json(1 hunks)source/json_tables/indexer/derivative/auctionEndpointRequest.json(1 hunks)source/json_tables/indexer/derivative/streamTradesV2Request.json(1 hunks)source/json_tables/indexer/derivative/tradesV2Request.json(1 hunks)source/json_tables/indexer/explorer/bankTransfer.json(1 hunks)source/json_tables/indexer/explorer/coin.json(1 hunks)source/json_tables/indexer/explorer/cosmosCoin.json(1 hunks)source/json_tables/indexer/explorer/event.json(1 hunks)source/json_tables/indexer/explorer/gasFee.json(1 hunks)source/json_tables/indexer/explorer/getBankTransfersRequest.json(1 hunks)source/json_tables/indexer/explorer/getBankTransfersResponse.json(1 hunks)source/json_tables/indexer/explorer/getContractTxsRequest.json(1 hunks)source/json_tables/indexer/explorer/getContractTxsResponse.json(1 hunks)source/json_tables/indexer/explorer/getContractTxsV2Request.json(1 hunks)source/json_tables/indexer/explorer/getContractTxsV2Response.json(1 hunks)source/json_tables/indexer/explorer/getValidatorRequest.json(1 hunks)source/json_tables/indexer/explorer/getValidatorResponse.json(1 hunks)source/json_tables/indexer/explorer/getValidatorUptimeRequest.json(1 hunks)source/json_tables/indexer/explorer/getValidatorUptimeResponse.json(1 hunks)source/json_tables/indexer/explorer/getValidatorsResponse.json(1 hunks)source/json_tables/indexer/explorer/paging.json(1 hunks)source/json_tables/indexer/explorer/relayer.json(1 hunks)source/json_tables/indexer/explorer/relayerMarkets.json(1 hunks)source/json_tables/indexer/explorer/relayersRequest.json(1 hunks)source/json_tables/indexer/explorer/relayersResponse.json(1 hunks)source/json_tables/indexer/explorer/signature.json(1 hunks)source/json_tables/indexer/explorer/txDetailData.json(1 hunks)source/json_tables/indexer/explorer/validator.json(1 hunks)source/json_tables/indexer/explorer/validatorDescription.json(1 hunks)source/json_tables/indexer/explorer/validatorUptime.json(1 hunks)
💤 Files with no reviewable changes (9)
- source/json_tables/chain/permissions/addressRoles.json
- source/json_tables/chain/permissions/msgRevokeNamespaceRoles.json
- source/json_tables/chain/permissions/msgDeleteNamespace.json
- source/json_tables/chain/permissions/queryVouchersForAddressRequest.json
- source/json_tables/chain/permissions/msgUpdateNamespaceRoles.json
- source/json_tables/chain/permissions/queryVouchersForAddressResponse.json
- source/json_tables/chain/permissions/permissionAction.json
- source/json_tables/chain/permissions/queryAddressesByRoleResponse.json
- source/json_tables/chain/permissions/queryNamespaceByDenomRequest.json
✅ Files skipped from review due to trivial changes (11)
- source/json_tables/chain/permissions/queryVoucherRequest.json
- source/json_tables/chain/permissions/queryPolicyManagerCapabilitiesResponse.json
- source/json_tables/indexer/explorer/relayersResponse.json
- source/json_tables/chain/permissions/queryRolesByActorResponse.json
- source/json_tables/indexer/explorer/validatorUptime.json
- source/json_tables/chain/permissions/queryNamespaceResponse.json
- source/json_tables/chain/permissions/msgUpdateNamespace_SetContractHook.json
- source/json_tables/chain/exchange/denomMinNotional.json
- source/json_tables/chain/permissions/queryActorsByRoleRequest.json
- source/json_tables/indexer/explorer/gasFee.json
- source/json_tables/chain/exchange/queryDenomMinNotionalsResponse.json
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/includes/_derivatives.md
47-47: Hard tabs
Column: 1
(MD010, no-hard-tabs)
48-48: Hard tabs
Column: 1
(MD010, no-hard-tabs)
49-49: Hard tabs
Column: 1
(MD010, no-hard-tabs)
51-51: Hard tabs
Column: 1
(MD010, no-hard-tabs)
53-53: Hard tabs
Column: 1
(MD010, no-hard-tabs)
54-54: Hard tabs
Column: 1
(MD010, no-hard-tabs)
55-55: Hard tabs
Column: 1
(MD010, no-hard-tabs)
56-56: Hard tabs
Column: 1
(MD010, no-hard-tabs)
60-60: Hard tabs
Column: 1
(MD010, no-hard-tabs)
61-61: Hard tabs
Column: 1
(MD010, no-hard-tabs)
62-62: Hard tabs
Column: 1
(MD010, no-hard-tabs)
63-63: Hard tabs
Column: 1
(MD010, no-hard-tabs)
64-64: Hard tabs
Column: 1
(MD010, no-hard-tabs)
66-66: Hard tabs
Column: 1
(MD010, no-hard-tabs)
67-67: Hard tabs
Column: 1
(MD010, no-hard-tabs)
68-68: Hard tabs
Column: 1
(MD010, no-hard-tabs)
69-69: Hard tabs
Column: 1
(MD010, no-hard-tabs)
70-70: Hard tabs
Column: 1
(MD010, no-hard-tabs)
71-71: Hard tabs
Column: 1
(MD010, no-hard-tabs)
72-72: Hard tabs
Column: 1
(MD010, no-hard-tabs)
73-73: Hard tabs
Column: 1
(MD010, no-hard-tabs)
74-74: Hard tabs
Column: 1
(MD010, no-hard-tabs)
76-76: Hard tabs
Column: 1
(MD010, no-hard-tabs)
77-77: Hard tabs
Column: 1
(MD010, no-hard-tabs)
78-78: Hard tabs
Column: 1
(MD010, no-hard-tabs)
80-80: Hard tabs
Column: 1
(MD010, no-hard-tabs)
81-81: Hard tabs
Column: 1
(MD010, no-hard-tabs)
82-82: Hard tabs
Column: 1
(MD010, no-hard-tabs)
83-83: Hard tabs
Column: 1
(MD010, no-hard-tabs)
84-84: Hard tabs
Column: 1
(MD010, no-hard-tabs)
86-86: Hard tabs
Column: 1
(MD010, no-hard-tabs)
87-87: Hard tabs
Column: 1
(MD010, no-hard-tabs)
88-88: Hard tabs
Column: 1
(MD010, no-hard-tabs)
90-90: Hard tabs
Column: 1
(MD010, no-hard-tabs)
92-92: Hard tabs
Column: 1
(MD010, no-hard-tabs)
93-93: Hard tabs
Column: 1
(MD010, no-hard-tabs)
94-94: Hard tabs
Column: 1
(MD010, no-hard-tabs)
95-95: Hard tabs
Column: 1
(MD010, no-hard-tabs)
96-96: Hard tabs
Column: 1
(MD010, no-hard-tabs)
98-98: Hard tabs
Column: 1
(MD010, no-hard-tabs)
99-99: Hard tabs
Column: 1
(MD010, no-hard-tabs)
100-100: Hard tabs
Column: 1
(MD010, no-hard-tabs)
102-102: Hard tabs
Column: 1
(MD010, no-hard-tabs)
104-104: Hard tabs
Column: 1
(MD010, no-hard-tabs)
106-106: Hard tabs
Column: 1
(MD010, no-hard-tabs)
107-107: Hard tabs
Column: 1
(MD010, no-hard-tabs)
108-108: Hard tabs
Column: 1
(MD010, no-hard-tabs)
109-109: Hard tabs
Column: 1
(MD010, no-hard-tabs)
111-111: Hard tabs
Column: 1
(MD010, no-hard-tabs)
112-112: Hard tabs
Column: 1
(MD010, no-hard-tabs)
136-136: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
1252-1252: Hard tabs
Column: 1
(MD010, no-hard-tabs)
1507-1507: Hard tabs
Column: 1
(MD010, no-hard-tabs)
source/includes/_chainexchange.md
4526-4526: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4527-4527: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4528-4528: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4529-4529: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4530-4530: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4532-4532: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4534-4534: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4535-4535: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4536-4536: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4540-4540: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4541-4541: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4542-4542: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4543-4543: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4544-4544: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4546-4546: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4547-4547: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4548-4548: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4549-4549: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4550-4550: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4551-4551: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4552-4552: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4553-4553: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4554-4554: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4556-4556: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4557-4557: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4558-4558: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4560-4560: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4561-4561: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4562-4562: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4563-4563: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4564-4564: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4566-4566: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4567-4567: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4568-4568: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4570-4570: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4572-4572: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4573-4573: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4574-4574: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4575-4575: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4576-4576: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4578-4578: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4580-4580: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4581-4581: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4582-4582: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4583-4583: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4585-4585: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4586-4586: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4658-4658: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4659-4659: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4660-4660: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4661-4661: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4662-4662: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4664-4664: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4666-4666: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4667-4667: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4668-4668: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4672-4672: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4673-4673: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4674-4674: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4675-4675: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4676-4676: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4678-4678: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4679-4679: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4680-4680: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4681-4681: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4682-4682: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4683-4683: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4684-4684: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4685-4685: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4686-4686: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4688-4688: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4689-4689: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4690-4690: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4692-4692: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4693-4693: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4694-4694: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4695-4695: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4696-4696: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4698-4698: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4699-4699: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4700-4700: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4702-4702: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4704-4704: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4705-4705: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4706-4706: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4707-4707: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4708-4708: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4710-4710: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4711-4711: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4712-4712: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4713-4713: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4715-4715: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4716-4716: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4760-4760: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
4820-4820: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4821-4821: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4822-4822: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4823-4823: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4824-4824: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4826-4826: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4828-4828: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4829-4829: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4830-4830: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4834-4834: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4835-4835: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4836-4836: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4837-4837: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4838-4838: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4840-4840: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4841-4841: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4842-4842: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4843-4843: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4844-4844: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4845-4845: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4846-4846: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4847-4847: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4848-4848: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4850-4850: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4851-4851: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4852-4852: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4854-4854: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4855-4855: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4856-4856: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4857-4857: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4858-4858: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4860-4860: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4861-4861: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4862-4862: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4864-4864: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4866-4866: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4867-4867: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4868-4868: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4869-4869: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4870-4870: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4872-4872: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4874-4874: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4875-4875: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4876-4876: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4877-4877: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4879-4879: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4880-4880: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4952-4952: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4953-4953: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4954-4954: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4955-4955: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4956-4956: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4958-4958: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4960-4960: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4961-4961: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4962-4962: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4966-4966: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4967-4967: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4968-4968: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4969-4969: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4970-4970: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4972-4972: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4973-4973: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4974-4974: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4975-4975: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4976-4976: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4977-4977: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4978-4978: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4979-4979: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4980-4980: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4982-4982: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4983-4983: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4984-4984: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4986-4986: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4987-4987: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4988-4988: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4989-4989: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4990-4990: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4992-4992: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4993-4993: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4994-4994: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4996-4996: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4998-4998: Hard tabs
Column: 1
(MD010, no-hard-tabs)
4999-4999: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5000-5000: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5001-5001: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5002-5002: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5004-5004: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5005-5005: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5006-5006: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5007-5007: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5009-5009: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5010-5010: Hard tabs
Column: 1
(MD010, no-hard-tabs)
5054-5054: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
source/includes/_auctionsrpc.md
431-431: Hard tabs
Column: 1
(MD010, no-hard-tabs)
432-432: Hard tabs
Column: 1
(MD010, no-hard-tabs)
433-433: Hard tabs
Column: 1
(MD010, no-hard-tabs)
434-434: Hard tabs
Column: 1
(MD010, no-hard-tabs)
436-436: Hard tabs
Column: 1
(MD010, no-hard-tabs)
437-437: Hard tabs
Column: 1
(MD010, no-hard-tabs)
441-441: Hard tabs
Column: 1
(MD010, no-hard-tabs)
442-442: Hard tabs
Column: 1
(MD010, no-hard-tabs)
443-443: Hard tabs
Column: 1
(MD010, no-hard-tabs)
444-444: Hard tabs
Column: 1
(MD010, no-hard-tabs)
445-445: Hard tabs
Column: 1
(MD010, no-hard-tabs)
447-447: Hard tabs
Column: 1
(MD010, no-hard-tabs)
448-448: Hard tabs
Column: 1
(MD010, no-hard-tabs)
450-450: Hard tabs
Column: 1
(MD010, no-hard-tabs)
451-451: Hard tabs
Column: 1
(MD010, no-hard-tabs)
452-452: Hard tabs
Column: 1
(MD010, no-hard-tabs)
453-453: Hard tabs
Column: 1
(MD010, no-hard-tabs)
454-454: Hard tabs
Column: 1
(MD010, no-hard-tabs)
455-455: Hard tabs
Column: 1
(MD010, no-hard-tabs)
457-457: Hard tabs
Column: 1
(MD010, no-hard-tabs)
458-458: Hard tabs
Column: 1
(MD010, no-hard-tabs)
459-459: Hard tabs
Column: 1
(MD010, no-hard-tabs)
460-460: Hard tabs
Column: 1
(MD010, no-hard-tabs)
461-461: Hard tabs
Column: 1
(MD010, no-hard-tabs)
462-462: Hard tabs
Column: 1
(MD010, no-hard-tabs)
464-464: Hard tabs
Column: 1
(MD010, no-hard-tabs)
465-465: Hard tabs
Column: 1
(MD010, no-hard-tabs)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - injective-docs
- GitHub Check: Header rules - injective-docs
- GitHub Check: Pages changed - injective-docs
🔇 Additional comments (79)
source/json_tables/chain/permissions/queryVouchersRequest.json (1)
1-3: Clear and Concise JSON Structure for Request ParameterThe new JSON file correctly introduces the
"denom"parameter with its type, description, and required flag. The structure is straightforward and aligns well with API documentation practices. Ensure that any downstream dependencies or schema validations consuming this JSON file are updated accordingly.source/json_tables/chain/permissions/queryRoleManagerRequest.json (1)
1-4: Clear and Consistent JSON StructureThe new JSON file is well-structured and clearly defines the parameters expected for a query role manager request. Each object in the array has descriptive keys—"Parameter", "Type", "Description", and "Required"—which makes it easy to understand the intended use.
source/json_tables/chain/permissions/queryActorsByRoleResponse.json (1)
1-3: JSON Structure and Schema ValidityThe JSON is well-formed, representing an array with a single object defining the "actors" parameter. The structure aligns with the expected documentation schema for API responses.
source/json_tables/chain/permissions/queryVoucherResponse.json (1)
1-3: Clear and Consistent Voucher Entry Documentation.
The added JSON entry clearly documents the new "voucher" parameter with type "Coin" and a succinct description. This aligns well with the overall API documentation goals for the permissions module.source/json_tables/chain/permissions/addressVoucher.json (1)
1-4: Well-Structured Address and Voucher Parameters.
The JSON structure effectively documents both the "address" and "voucher" parameters, ensuring consistency with similar entries (e.g., inqueryVoucherResponse.json). This clear documentation will aid users in understanding the expected formats and data types.source/json_tables/chain/exchange/queryFullSpotOrderbookResponse.json (1)
1-4: Well-Defined Response Schema for Full Spot Order BookThis new JSON structure clearly defines the response by listing both the
bidsandasksparameters as arrays ofTrimmedLimitOrder. The descriptions are concise and the arrangement mirrors the overall API design, enhancing clarity for users.source/json_tables/chain/permissions/queryModuleStateResponse.json (1)
1-3: Approved: Clear Definition of Module StateThe JSON structure is simple and clearly defines the "state" parameter with type "GenesisState" and the description "Module state". This structure meets the documentation requirements and aligns with similar schema definitions in the permissions module.
source/json_tables/chain/exchange/queryDenomMinNotionalResponse.json (1)
1-3: Approved: Well-Structured Denom Minimum Notional SchemaThe new JSON entry effectively documents the expected response by specifying the parameter "amount" as "Decimal" with its description. The schema is consistent and clear, facilitating client-side validation.
source/json_tables/chain/exchange/queryMarketBalanceResponse.json (1)
1-3: Approved: Concise Market Balance Response SchemaThis JSON file nicely defines the "balance" parameter with the type "Decimal" and a clear description. The structure is easy to understand and should integrate seamlessly with the related API endpoints.
source/json_tables/chain/permissions/queryRoleManagerResponse.json (1)
1-3: Approved: Clear Role Manager DefinitionThe structure introduces a "role_manager" parameter with type "RoleManager" and an appropriate description. This clear definition will help maintain consistency in API responses related to permissions and role management.
source/json_tables/chain/permissions/queryNamespaceDenomsResponse.json (1)
1-3: Approved: Accurate Namespace Denoms DocumentationThe JSON entry defines the "denoms" parameter as a "String Array" with the description "List of namespaces denoms." The description is sufficiently clear. For further clarity, you might consider specifying if the array contains plain strings or a structured object in future iterations.
source/json_tables/chain/permissions/queryPolicyManagerCapabilitiesRequest.json (1)
1-3: Clear and Consistent JSON Schema for Token Query Parameter.
The JSON array correctly defines the required parameter"denom"with type"String"and an appropriate description. This schema is clear and meets the updated documentation requirements.source/json_tables/chain/permissions/queryPolicyStatusesRequest.json (1)
1-3: Well-Defined Token Denom Parameter.
The JSON structure properly specifies a required"denom"parameter with the correct type and description. Its consistency with similar files ensures clarity and proper request validation across the API.source/json_tables/chain/permissions/queryNamespaceRequest.json (1)
1-3: Accurate Inclusion of the "denom" Parameter.
The JSON schema correctly includes the"denom"parameter with type"String", a clear description, and marks it as required, aligning with the ongoing standardization across the permissions module.source/json_tables/chain/permissions/queryPolicyStatusesResponse.json (1)
1-3: Valid Response Schema Definition with a Minor Suggestion.
The JSON schema defines the"policy_statuses"parameter with type"PolicyStatus"and a description"Role manager details". While the structure is correct, please verify that the description accurately reflects the intended contents of the response. If the response is meant to detail statuses rather than role manager information, consider updating the description for clarity.source/json_tables/chain/permissions/queryRoleManagersResponse.json (1)
1-3: Appropriate Role Managers Response Format.
The JSON structure accurately defines the"role_managers"parameter as a"RoleManager Array"with a descriptive explanation. This clear schema facilitates proper API responses regarding role management.source/json_tables/chain/exchange/queryMarketBalancesResponse.json (1)
1-3: Clear and Consistent Schema for Market Balances
The JSON structure defining thebalancesparameter is well-formed and succinct. It clearly documents that the response will include an array of market balances. Ensure that the type"MarketBalance Array"exactly matches the definition used in the overall API documentation for consistency.source/json_tables/chain/exchange/queryMarketBalanceRequest.json (1)
1-3: Accurate and Concise Request Schema
The new JSON structure for the market balance request is clear. The parametermarket_idis specified as a required string, which aligns well with the documentation needs for fetching a market balance.source/json_tables/chain/exchange/queryFullDerivativeOrderbookRequest.json (1)
1-3: Consistent Order Book Request Schema
The JSON schema is consistent with the other request schemas by defining the requiredmarket_idparameter as a string. This clear specification will help ensure proper integration with the new derivative order book endpoint.source/json_tables/indexer/explorer/getValidatorUptimeRequest.json (1)
1-3: Well-Defined Validator Uptime Request Schema
The schema specifying theaddressparameter is straightforward and correctly marks the parameter as required. This addition will aid in querying validator uptime information effectively.source/json_tables/indexer/explorer/getValidatorRequest.json (1)
1-3: Clear Validator Request Definition
The structure is clear and mirrors the pattern seen in the uptime request schema. Definingaddressas a required string consistently reinforces the API contract for validator data queries.source/json_tables/indexer/auction/injBurntEndpointResponse.json (1)
1-3: Clear and Concise JSON EntryThe new JSON entry for
total_inj_burntis well defined with the type "Decimal" and a clear description. This should help consumers understand that the value represents the total INJ burnt during auctions. Please ensure that the underlying system can appropriately handle the "Decimal" type.source/json_tables/chain/exchange/queryDenomMinNotionalRequest.json (1)
1-3: Proper Schema Definition for Request ParameterThe added parameter for "denom" is clearly documented with its type as "String" and a description that precisely outlines its purpose. Marking it as required via
"Required": "Yes"emphasizes its necessity for the endpoint request.source/json_tables/chain/permissions/params.json (1)
1-3: Well-Defined Permissions ParameterThe new parameter
"wasm_hook_query_max_gas"is clearly specified with type "Integer" alongside a succinct description. This aligns with the enhancements in the permissions module and improves the clarity of parameter documentation.source/json_tables/indexer/explorer/relayersRequest.json (1)
1-3: Consistent and Informative Parameter DefinitionThe JSON entry for
"market_ids"is precise, defining it as a "String Array" with an adequate description and marked as required. This entry ensures that clients know to supply a list of market IDs when querying the relayers. Verify that downstream systems expect the array in the defined format.source/json_tables/indexer/explorer/cosmosCoin.json (1)
1-4: Clear Token Parameter DocumentationThe file introduces token-related parameters
"denom"and"amount", both with type "String" and clear descriptions. These definitions promote consistency with related market and token documentation. Ensure that these parameter types align with other parts of the documentation for uniformity.source/json_tables/chain/permissions/actorRoles.json (1)
1-4: Clear and Concise JSON Schema for Actor RolesThe JSON schema clearly defines two parameters—actor and roles—using descriptive labels. Ensure that the nomenclature (e.g., "String Array") is consistent throughout your documentation, depending on whether you represent arrays as "String Array" or "array of strings" in your style guide.
source/json_tables/indexer/explorer/coin.json (1)
1-4: Clear Documentation for Coin Data SchemaThe schema clearly documents the token parameters with straightforward object definitions. One consideration: while "denom" is appropriately typed as a string, the "amount" being a string might be intentional—for handling very large or precise numbers—but ensure that this aligns with your overall documentation style and data processing requirements.
source/json_tables/chain/permissions/roleManager.json (1)
1-4: Accurate JSON Representation for Role ManagerThis file introduces a well-structured JSON array outlining parameters for role management. The inclusion of both manager and roles is clear and precise. It would be beneficial to cross-check the terminology with other permissions-related files to ensure uniformity—especially regarding array representations.
source/json_tables/chain/permissions/roleActors.json (1)
1-4: Well-Defined Schema for Role ActorsThe JSON schema properly identifies the role and its associated actors. The structure is simple and consistent with typical documentation practices. As a minor note, review the punctuation in the description (the use of the apostrophe in "actors' names") for stylistic consistency with other documentation files.
source/json_tables/chain/exchange/marketBalance.json (1)
1-4: Solid Schema for Market Balance EndpointThe structure documents the market balance parameters with clarity by defining market_id as a string and balance as a decimal. Verify that using "Decimal" as a type is consistent with consumer expectations in your API documentation (some systems use "number" or even a string format for decimal values), and adjust if necessary for uniformity across your documentation.
source/json_tables/indexer/explorer/relayerMarkets.json (1)
1-4: Clear and Well-Structured Schema for Market DataThe new JSON structure clearly defines the
market_idandrelayersfields with explicit types and descriptions. Ensure that the custom type"Relayer Array"is consistently defined and documented across the rest of the application.source/json_tables/indexer/explorer/relayer.json (1)
1-4: Concise and Informative Schema for Relayer MetadataThe file successfully outlines the key parameters –
"name"for the identifier and"cta"for a call-to-action link. The descriptions are precise and provide clear context. Please verify that the terminology aligns with other related documentation.source/json_tables/indexer/explorer/event.json (1)
1-4: Effective Definition for Event ParametersThe introduction of the
"type"and"attributes"fields provides a clear structure for detailing events. The use of"Map"for attributes is appropriate for key-value pairs. This structure aids in consistent event logging across the API.source/json_tables/chain/exchange/queryFullDerivativeOrderbookResponse.json (1)
1-4: Comprehensive Documentation of Orderbook Response FormatThis JSON schema efficiently documents the order book response by separating the bid and ask sides into
"bids"and"asks", each described as arrays of"TrimmedLimitOrder". Verify that the"TrimmedLimitOrder"structure is well documented (e.g., intrimmedLimitOrder.json) and that its usage is consistent with other order-related schemas.source/json_tables/indexer/explorer/getContractTxsResponse.json (1)
1-4: Well-Defined Schema for Contract Transaction ResponsesThe file clearly differentiates pagination details (
"paging") from transaction data ("data"). This separation improves clarity and mirrors patterns seen in similar response schemas. If not already described elsewhere, consider expanding documentation for"TxDetailData"for added clarity.source/json_tables/chain/permissions/queryRolesByActorRequest.json (1)
1-4: Clear and Well-Structured Request Schema.
The new JSON structure properly defines the required parameters "denom" and "actor" as strings with concise descriptions. The design supports documentation clarity for the permissions module.source/json_tables/indexer/explorer/getContractTxsV2Response.json (1)
1-4: Concise Response Format Defined.
The JSON schema clearly specifies two parameters: "next" (a String Array for pagination details) and "data" (of type TxDetailData for transaction details). Ensure that the external definition for "TxDetailData" is maintained elsewhere in the documentation for consistency.source/json_tables/indexer/explorer/getValidatorUptimeResponse.json (1)
1-5: JSON schema is clear and consistent.
The new response structure clearly outlines the required parameters, and the use of "ValidatorUptime Array" suggests that the corresponding schema is defined elsewhere. Ensure that the "ValidatorUptime" type is well documented in its dedicated schema file.source/json_tables/chain/permissions/genesisState.json (1)
1-5: Module configuration schema is well-defined.
The JSON structure cleanly defines the parameters needed for the permissions module configuration with clear types and descriptions.source/json_tables/chain/permissions/policyStatus.json (1)
1-5: Policy status schema is comprehensive.
The JSON structure clearly defines the necessary parameters to describe policy statuses. Just ensure that the "Action" type is defined and documented consistently elsewhere in the API documentation.source/json_tables/chain/exchange/trimmedLimitOrder.json (1)
1-6: JSON Schema Structure: Looks Good!The structure clearly defines the limit order parameters with appropriate types and descriptions. You might consider standardizing the phrasing—for example, using either "Order price" or "Price" consistently—and similarly for other fields.
source/json_tables/chain/permissions/policyManagerCapability.json (1)
1-6: Clear and Concise JSON Structure.This JSON file effectively defines the parameters for policy management capabilities. The descriptions provide clear guidance on expected values. Everything appears consistent and well-organized.
source/json_tables/indexer/explorer/bankTransfer.json (1)
1-7: Well-Structured JSON Schema for Bank TransfersThe schema clearly defines all required parameters for a bank transfer. Each parameter’s type and description are unambiguous, ensuring that users know exactly what information is needed.
source/json_tables/chain/permissions/msgUpdateActorRoles.json (1)
1-6: Clear Definition for Updating Actor RolesThe JSON structure properly distinguishes required fields (such as "sender" and "denom") from optional ones (like "role_actors_to_add" and "role_actors_to_revoke"). The descriptions provide adequate context about their roles in the permissions module.
source/json_tables/indexer/explorer/getContractTxsV2Request.json (1)
1-8: Comprehensive Request Definition for Contract Transactions (V2)The schema includes all necessary parameters with clear type definitions and descriptions. This structured approach helps users understand the expected inputs and supports consistency in API documentation.
source/json_tables/chain/permissions/namespace.json (1)
1-9: Robust Update to Namespace SchemaThe updated JSON schema replaces deprecated parameters (e.g., replacing "wasm_hook" with "contract_hook" and "address_roles" with "actor_roles") and introduces new arrays for enhanced role management and policy functionality. Verify that these updated parameter names are consistently referenced across the documentation and in any related API endpoints.
source/json_tables/chain/permissions/msgUpdateNamespace.json (1)
3-8: Documentation Update for New Namespace Parameters
The added parameters (denom,contract_hook,role_permissions,role_managers,policy_statuses, andpolicy_manager_capabilities) are clearly defined and marked as required. Please ensure that all related documentation and downstream validation logic reflect these new fields consistently.source/json_tables/chain/exchange/msgInstantSpotMarketLaunch.json (1)
9-10: Addition of Decimal Precision Parameters
The new parametersbase_decimalsandquote_decimalsare a valuable addition for specifying token precision in market launches. Confirm that their usage is consistent with similar endpoints and that any related client code is updated accordingly.source/json_tables/indexer/explorer/getBankTransfersRequest.json (1)
1-12: New Bank Transfers Request Schema Implementation
This complete JSON schema adds a comprehensive set of optional parameters for filtering bank transfers (e.g., by senders, recipients, timestamps, and pagination). The descriptions are clear and the required flags are appropriately set. Please ensure that API consumers and validators are updated to accommodate this new structure.source/json_tables/chain/exchange/spotMarket.json (1)
14-16: Spot Market Schema Update with Decimal Parameters
The inclusion ofbase_decimalsandquote_decimals(along with the maintainedadmin_permissions) improves clarity regarding token precision in the market configuration. Verify that the descriptions are aligned with the documentation across related modules (e.g., spot and binary options markets).source/json_tables/indexer/derivative/auctionEndpointRequest.json (1)
1-17: New Auction Endpoint Request Schema Overview
This new JSON schema comprehensively covers a variety of optional parameters for filtering auction trades by market, execution details, timestamps, and trade identifiers. The parameters and their descriptions are well-documented. Please verify that any backend or client-side validators align with these definitions.source/json_tables/indexer/explorer/txDetailData.json (1)
1-23: Schema review for transaction detail data.
The JSON schema is comprehensive and clearly outlines the necessary transaction details. All parameter types and descriptions appear consistent and appropriately detailed.source/json_tables/chain/exchange/binaryOptionsMarket.json (1)
20-21: Validation of new "quote_decimals" parameter.
The addition of the "quote_decimals" parameter with type Integer enhances the schema by specifying the decimal precision for the quote token. The overall structure and integration of parameters appear consistent.source/includes/_auctionsrpc.md (1)
385-388: InjBurntEndpoint Documentation Added:
The new “InjBurntEndpoint” section is clearly introduced, with a concise description and proper grouping under the indexer IP rate limit. Both the Python and Go examples appear to follow the style used in other sections. Please ensure that the response structure here remains fully consistent with the corresponding JSON schema (e.g. in injBurntEndpointResponse.json).source/includes/_tokenfactory.md (3)
644-650: MsgCreateDenom Update – Added "allow_admin_burn":
The updated function call now includes the new parameter “allow_admin_burn” (set to False by default). This additional flag clearly conveys that token burning by admin is disabled unless explicitly enabled. Make sure that related documentation elsewhere reflects this new option.
872-878: MsgMint Update – Added "receiver":
The updated msg_mint documentation now requires a “receiver” parameter to designate where the minted tokens should be sent. This enhances clarity in token distribution. Confirm that the user examples fully reflect this new requirement.
1110-1115: MsgBurn Update – Added "burn_from_address":
The updated msg_burn function now includes a "burn_from_address" parameter, which gives explicit control on which account’s tokens are to be burned. This change aligns well with the improved admin control and should help prevent ambiguity during transactions.source/includes/_binaryoptions.md (2)
158-158: Documentation Update: Repositioning ofadmin_permissionsParameter
The BinaryOptionsMarket table now shows theadmin_permissionsparameter on this line. Its description indicates that the value is computed by summing the individual permissions, which is consistent with the expected logic. Please verify that this change aligns with the corresponding JSON schema and overall documentation ordering.
159-159: Documentation Addition: Introduction ofquote_decimalsParameter
A new parameterquote_decimalshas been added to the BinaryOptionsMarket table. This parameter specifies the number of decimals used for the quote token. Ensure that the parameter’s type (Integer) and its description match the updates in the JSON schema and provide clear guidance for API users.source/includes/_derivativesrpc.md (2)
1501-1511: Review HTML Table for TradesV2 Request Parameters
The auto-generated HTML table (from line 1501) detailing the parameters for the TradesV2 request looks well structured. Please double-check that all parameter names and descriptions accurately match the current API specification.
2161-2194: Verify Derivative Positions V2 Endpoint Example
The Python example for fetching derivative positions (lines 2161–2194) now callsfetch_derivative_positions_v2. Please ensure that this updated endpoint and its parameters are consistently used across documentation and match the underlying API changes. Clarifying any differences from previous versions might also further aid readers.source/includes/_spot.md (6)
5-143: Well-structured documentation for the new L3SpotOrderBook endpoint.The documentation for the new L3SpotOrderBook endpoint is comprehensive and follows good API documentation practices:
- Clear endpoint description and purpose
- IP rate limit group specification
- Request parameters with examples in multiple languages (Python & Go)
- Response parameters with JSON schema tables
- Example responses
282-284: New decimal fields added to spot market response.The response schema has been enhanced with new fields:
baseDecimals: Number of decimals used for the base tokenquoteDecimals: Number of decimals used for the quote tokenThese additions improve precision handling by explicitly specifying decimal places for both base and quote tokens.
311-313: New fields added to SpotMarket schema.The SpotMarket schema has been updated with new fields:
admin_permissions: Integer field for admin permission levelsbase_decimals: Integer field for base token decimalsquote_decimals: Integer field for quote token decimalsThese additions provide better control over market administration and token precision.
1924-1925: New parameters added to MsgInstantSpotMarketLaunch.The message parameters have been extended with:
base_decimals: Specifies decimals for base tokenquote_decimals: Specifies decimals for quote tokenThese additions allow for proper decimal precision configuration during market creation.
2042-2044: Updated MsgInstantSpotMarketLaunch schema documentation.The schema documentation has been updated to include:
min_notional: Required field for minimum notional valuebase_decimals: Required field for base token decimalsquote_decimals: Required field for quote token decimals
4444-4482: Comprehensive documentation for LocalOrderHashComputation.The documentation provides detailed explanations for:
- Purpose and benefits of local hash computation
- Implementation considerations for HFT/API traders
- Gas calculation strategies
- Error handling recommendations
This section greatly helps developers optimize their trading systems.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~4445-~4445: Possible missing comma found.
Context: ...on relies on a nonce based on the state machine which does not change until the transac...(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~4449-~4449: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...emain unique. For strategies employing high frequency trading, order hashes should be calcula...(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~4456-~4456: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...i.e. gas may change if the memo size is very large). The gas can then be increased per ord...(EN_WEAK_ADJECTIVE)
[style] ~4468-~4468: Consider using “incompatible” to avoid wordiness.
Context: ... never fail; however, because v0.46 was not compatible with CosmWasm during the last chain upg...(NOT_ABLE_PREMIUM)
source/includes/_chainexchange.md (7)
4474-4606: LGTM - New MarketBalance endpoint documentation is well structuredThe documentation for the new MarketBalance endpoint is clear and complete, including:
- Accurate endpoint description
- Request parameters with proper examples in both Python and Go
- Response parameters with JSON example and table definitions
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
4526-4526: Hard tabs
Column: 1(MD010, no-hard-tabs)
4527-4527: Hard tabs
Column: 1(MD010, no-hard-tabs)
4528-4528: Hard tabs
Column: 1(MD010, no-hard-tabs)
4529-4529: Hard tabs
Column: 1(MD010, no-hard-tabs)
4530-4530: Hard tabs
Column: 1(MD010, no-hard-tabs)
4532-4532: Hard tabs
Column: 1(MD010, no-hard-tabs)
4534-4534: Hard tabs
Column: 1(MD010, no-hard-tabs)
4535-4535: Hard tabs
Column: 1(MD010, no-hard-tabs)
4536-4536: Hard tabs
Column: 1(MD010, no-hard-tabs)
4540-4540: Hard tabs
Column: 1(MD010, no-hard-tabs)
4541-4541: Hard tabs
Column: 1(MD010, no-hard-tabs)
4542-4542: Hard tabs
Column: 1(MD010, no-hard-tabs)
4543-4543: Hard tabs
Column: 1(MD010, no-hard-tabs)
4544-4544: Hard tabs
Column: 1(MD010, no-hard-tabs)
4546-4546: Hard tabs
Column: 1(MD010, no-hard-tabs)
4547-4547: Hard tabs
Column: 1(MD010, no-hard-tabs)
4548-4548: Hard tabs
Column: 1(MD010, no-hard-tabs)
4549-4549: Hard tabs
Column: 1(MD010, no-hard-tabs)
4550-4550: Hard tabs
Column: 1(MD010, no-hard-tabs)
4551-4551: Hard tabs
Column: 1(MD010, no-hard-tabs)
4552-4552: Hard tabs
Column: 1(MD010, no-hard-tabs)
4553-4553: Hard tabs
Column: 1(MD010, no-hard-tabs)
4554-4554: Hard tabs
Column: 1(MD010, no-hard-tabs)
4556-4556: Hard tabs
Column: 1(MD010, no-hard-tabs)
4557-4557: Hard tabs
Column: 1(MD010, no-hard-tabs)
4558-4558: Hard tabs
Column: 1(MD010, no-hard-tabs)
4560-4560: Hard tabs
Column: 1(MD010, no-hard-tabs)
4561-4561: Hard tabs
Column: 1(MD010, no-hard-tabs)
4562-4562: Hard tabs
Column: 1(MD010, no-hard-tabs)
4563-4563: Hard tabs
Column: 1(MD010, no-hard-tabs)
4564-4564: Hard tabs
Column: 1(MD010, no-hard-tabs)
4566-4566: Hard tabs
Column: 1(MD010, no-hard-tabs)
4567-4567: Hard tabs
Column: 1(MD010, no-hard-tabs)
4568-4568: Hard tabs
Column: 1(MD010, no-hard-tabs)
4570-4570: Hard tabs
Column: 1(MD010, no-hard-tabs)
4572-4572: Hard tabs
Column: 1(MD010, no-hard-tabs)
4573-4573: Hard tabs
Column: 1(MD010, no-hard-tabs)
4574-4574: Hard tabs
Column: 1(MD010, no-hard-tabs)
4575-4575: Hard tabs
Column: 1(MD010, no-hard-tabs)
4576-4576: Hard tabs
Column: 1(MD010, no-hard-tabs)
4578-4578: Hard tabs
Column: 1(MD010, no-hard-tabs)
4580-4580: Hard tabs
Column: 1(MD010, no-hard-tabs)
4581-4581: Hard tabs
Column: 1(MD010, no-hard-tabs)
4582-4582: Hard tabs
Column: 1(MD010, no-hard-tabs)
4583-4583: Hard tabs
Column: 1(MD010, no-hard-tabs)
4585-4585: Hard tabs
Column: 1(MD010, no-hard-tabs)
4586-4586: Hard tabs
Column: 1(MD010, no-hard-tabs)
4609-4765: LGTM - MarketBalances endpoint documentation is comprehensiveThe documentation for the MarketBalances endpoint follows best practices:
- Clear endpoint description
- Well-structured request/response examples
- Proper parameter tables and type definitions
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
4658-4658: Hard tabs
Column: 1(MD010, no-hard-tabs)
4659-4659: Hard tabs
Column: 1(MD010, no-hard-tabs)
4660-4660: Hard tabs
Column: 1(MD010, no-hard-tabs)
4661-4661: Hard tabs
Column: 1(MD010, no-hard-tabs)
4662-4662: Hard tabs
Column: 1(MD010, no-hard-tabs)
4664-4664: Hard tabs
Column: 1(MD010, no-hard-tabs)
4666-4666: Hard tabs
Column: 1(MD010, no-hard-tabs)
4667-4667: Hard tabs
Column: 1(MD010, no-hard-tabs)
4668-4668: Hard tabs
Column: 1(MD010, no-hard-tabs)
4672-4672: Hard tabs
Column: 1(MD010, no-hard-tabs)
4673-4673: Hard tabs
Column: 1(MD010, no-hard-tabs)
4674-4674: Hard tabs
Column: 1(MD010, no-hard-tabs)
4675-4675: Hard tabs
Column: 1(MD010, no-hard-tabs)
4676-4676: Hard tabs
Column: 1(MD010, no-hard-tabs)
4678-4678: Hard tabs
Column: 1(MD010, no-hard-tabs)
4679-4679: Hard tabs
Column: 1(MD010, no-hard-tabs)
4680-4680: Hard tabs
Column: 1(MD010, no-hard-tabs)
4681-4681: Hard tabs
Column: 1(MD010, no-hard-tabs)
4682-4682: Hard tabs
Column: 1(MD010, no-hard-tabs)
4683-4683: Hard tabs
Column: 1(MD010, no-hard-tabs)
4684-4684: Hard tabs
Column: 1(MD010, no-hard-tabs)
4685-4685: Hard tabs
Column: 1(MD010, no-hard-tabs)
4686-4686: Hard tabs
Column: 1(MD010, no-hard-tabs)
4688-4688: Hard tabs
Column: 1(MD010, no-hard-tabs)
4689-4689: Hard tabs
Column: 1(MD010, no-hard-tabs)
4690-4690: Hard tabs
Column: 1(MD010, no-hard-tabs)
4692-4692: Hard tabs
Column: 1(MD010, no-hard-tabs)
4693-4693: Hard tabs
Column: 1(MD010, no-hard-tabs)
4694-4694: Hard tabs
Column: 1(MD010, no-hard-tabs)
4695-4695: Hard tabs
Column: 1(MD010, no-hard-tabs)
4696-4696: Hard tabs
Column: 1(MD010, no-hard-tabs)
4698-4698: Hard tabs
Column: 1(MD010, no-hard-tabs)
4699-4699: Hard tabs
Column: 1(MD010, no-hard-tabs)
4700-4700: Hard tabs
Column: 1(MD010, no-hard-tabs)
4702-4702: Hard tabs
Column: 1(MD010, no-hard-tabs)
4704-4704: Hard tabs
Column: 1(MD010, no-hard-tabs)
4705-4705: Hard tabs
Column: 1(MD010, no-hard-tabs)
4706-4706: Hard tabs
Column: 1(MD010, no-hard-tabs)
4707-4707: Hard tabs
Column: 1(MD010, no-hard-tabs)
4708-4708: Hard tabs
Column: 1(MD010, no-hard-tabs)
4710-4710: Hard tabs
Column: 1(MD010, no-hard-tabs)
4711-4711: Hard tabs
Column: 1(MD010, no-hard-tabs)
4712-4712: Hard tabs
Column: 1(MD010, no-hard-tabs)
4713-4713: Hard tabs
Column: 1(MD010, no-hard-tabs)
4715-4715: Hard tabs
Column: 1(MD010, no-hard-tabs)
4716-4716: Hard tabs
Column: 1(MD010, no-hard-tabs)
4760-4760: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
4768-4900: LGTM - DenomMinNotional endpoint documentation is properly formattedThe documentation for the DenomMinNotional endpoint is well organized with:
- Clear endpoint purpose
- Complete request/response examples
- Proper parameter definitions
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
4820-4820: Hard tabs
Column: 1(MD010, no-hard-tabs)
4821-4821: Hard tabs
Column: 1(MD010, no-hard-tabs)
4822-4822: Hard tabs
Column: 1(MD010, no-hard-tabs)
4823-4823: Hard tabs
Column: 1(MD010, no-hard-tabs)
4824-4824: Hard tabs
Column: 1(MD010, no-hard-tabs)
4826-4826: Hard tabs
Column: 1(MD010, no-hard-tabs)
4828-4828: Hard tabs
Column: 1(MD010, no-hard-tabs)
4829-4829: Hard tabs
Column: 1(MD010, no-hard-tabs)
4830-4830: Hard tabs
Column: 1(MD010, no-hard-tabs)
4834-4834: Hard tabs
Column: 1(MD010, no-hard-tabs)
4835-4835: Hard tabs
Column: 1(MD010, no-hard-tabs)
4836-4836: Hard tabs
Column: 1(MD010, no-hard-tabs)
4837-4837: Hard tabs
Column: 1(MD010, no-hard-tabs)
4838-4838: Hard tabs
Column: 1(MD010, no-hard-tabs)
4840-4840: Hard tabs
Column: 1(MD010, no-hard-tabs)
4841-4841: Hard tabs
Column: 1(MD010, no-hard-tabs)
4842-4842: Hard tabs
Column: 1(MD010, no-hard-tabs)
4843-4843: Hard tabs
Column: 1(MD010, no-hard-tabs)
4844-4844: Hard tabs
Column: 1(MD010, no-hard-tabs)
4845-4845: Hard tabs
Column: 1(MD010, no-hard-tabs)
4846-4846: Hard tabs
Column: 1(MD010, no-hard-tabs)
4847-4847: Hard tabs
Column: 1(MD010, no-hard-tabs)
4848-4848: Hard tabs
Column: 1(MD010, no-hard-tabs)
4850-4850: Hard tabs
Column: 1(MD010, no-hard-tabs)
4851-4851: Hard tabs
Column: 1(MD010, no-hard-tabs)
4852-4852: Hard tabs
Column: 1(MD010, no-hard-tabs)
4854-4854: Hard tabs
Column: 1(MD010, no-hard-tabs)
4855-4855: Hard tabs
Column: 1(MD010, no-hard-tabs)
4856-4856: Hard tabs
Column: 1(MD010, no-hard-tabs)
4857-4857: Hard tabs
Column: 1(MD010, no-hard-tabs)
4858-4858: Hard tabs
Column: 1(MD010, no-hard-tabs)
4860-4860: Hard tabs
Column: 1(MD010, no-hard-tabs)
4861-4861: Hard tabs
Column: 1(MD010, no-hard-tabs)
4862-4862: Hard tabs
Column: 1(MD010, no-hard-tabs)
4864-4864: Hard tabs
Column: 1(MD010, no-hard-tabs)
4866-4866: Hard tabs
Column: 1(MD010, no-hard-tabs)
4867-4867: Hard tabs
Column: 1(MD010, no-hard-tabs)
4868-4868: Hard tabs
Column: 1(MD010, no-hard-tabs)
4869-4869: Hard tabs
Column: 1(MD010, no-hard-tabs)
4870-4870: Hard tabs
Column: 1(MD010, no-hard-tabs)
4872-4872: Hard tabs
Column: 1(MD010, no-hard-tabs)
4874-4874: Hard tabs
Column: 1(MD010, no-hard-tabs)
4875-4875: Hard tabs
Column: 1(MD010, no-hard-tabs)
4876-4876: Hard tabs
Column: 1(MD010, no-hard-tabs)
4877-4877: Hard tabs
Column: 1(MD010, no-hard-tabs)
4879-4879: Hard tabs
Column: 1(MD010, no-hard-tabs)
4880-4880: Hard tabs
Column: 1(MD010, no-hard-tabs)
4903-5060: LGTM - DenomMinNotionals endpoint documentation is completeThe documentation for the DenomMinNotionals endpoint includes all necessary components:
- Clear description
- Request/response examples in both Python and Go
- Well-defined parameter tables
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
4952-4952: Hard tabs
Column: 1(MD010, no-hard-tabs)
4953-4953: Hard tabs
Column: 1(MD010, no-hard-tabs)
4954-4954: Hard tabs
Column: 1(MD010, no-hard-tabs)
4955-4955: Hard tabs
Column: 1(MD010, no-hard-tabs)
4956-4956: Hard tabs
Column: 1(MD010, no-hard-tabs)
4958-4958: Hard tabs
Column: 1(MD010, no-hard-tabs)
4960-4960: Hard tabs
Column: 1(MD010, no-hard-tabs)
4961-4961: Hard tabs
Column: 1(MD010, no-hard-tabs)
4962-4962: Hard tabs
Column: 1(MD010, no-hard-tabs)
4966-4966: Hard tabs
Column: 1(MD010, no-hard-tabs)
4967-4967: Hard tabs
Column: 1(MD010, no-hard-tabs)
4968-4968: Hard tabs
Column: 1(MD010, no-hard-tabs)
4969-4969: Hard tabs
Column: 1(MD010, no-hard-tabs)
4970-4970: Hard tabs
Column: 1(MD010, no-hard-tabs)
4972-4972: Hard tabs
Column: 1(MD010, no-hard-tabs)
4973-4973: Hard tabs
Column: 1(MD010, no-hard-tabs)
4974-4974: Hard tabs
Column: 1(MD010, no-hard-tabs)
4975-4975: Hard tabs
Column: 1(MD010, no-hard-tabs)
4976-4976: Hard tabs
Column: 1(MD010, no-hard-tabs)
4977-4977: Hard tabs
Column: 1(MD010, no-hard-tabs)
4978-4978: Hard tabs
Column: 1(MD010, no-hard-tabs)
4979-4979: Hard tabs
Column: 1(MD010, no-hard-tabs)
4980-4980: Hard tabs
Column: 1(MD010, no-hard-tabs)
4982-4982: Hard tabs
Column: 1(MD010, no-hard-tabs)
4983-4983: Hard tabs
Column: 1(MD010, no-hard-tabs)
4984-4984: Hard tabs
Column: 1(MD010, no-hard-tabs)
4986-4986: Hard tabs
Column: 1(MD010, no-hard-tabs)
4987-4987: Hard tabs
Column: 1(MD010, no-hard-tabs)
4988-4988: Hard tabs
Column: 1(MD010, no-hard-tabs)
4989-4989: Hard tabs
Column: 1(MD010, no-hard-tabs)
4990-4990: Hard tabs
Column: 1(MD010, no-hard-tabs)
4992-4992: Hard tabs
Column: 1(MD010, no-hard-tabs)
4993-4993: Hard tabs
Column: 1(MD010, no-hard-tabs)
4994-4994: Hard tabs
Column: 1(MD010, no-hard-tabs)
4996-4996: Hard tabs
Column: 1(MD010, no-hard-tabs)
4998-4998: Hard tabs
Column: 1(MD010, no-hard-tabs)
4999-4999: Hard tabs
Column: 1(MD010, no-hard-tabs)
5000-5000: Hard tabs
Column: 1(MD010, no-hard-tabs)
5001-5001: Hard tabs
Column: 1(MD010, no-hard-tabs)
5002-5002: Hard tabs
Column: 1(MD010, no-hard-tabs)
5004-5004: Hard tabs
Column: 1(MD010, no-hard-tabs)
5005-5005: Hard tabs
Column: 1(MD010, no-hard-tabs)
5006-5006: Hard tabs
Column: 1(MD010, no-hard-tabs)
5007-5007: Hard tabs
Column: 1(MD010, no-hard-tabs)
5009-5009: Hard tabs
Column: 1(MD010, no-hard-tabs)
5010-5010: Hard tabs
Column: 1(MD010, no-hard-tabs)
5054-5054: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5062-5250: LGTM - MsgRewardsOptOut message documentation is well structuredThe documentation for the MsgRewardsOptOut message follows best practices:
- Clear message purpose
- Complete request examples in both Python and Go
- Proper parameter definitions and response format
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
5158-5158: Hard tabs
Column: 1(MD010, no-hard-tabs)
5159-5159: Hard tabs
Column: 1(MD010, no-hard-tabs)
5160-5160: Hard tabs
Column: 1(MD010, no-hard-tabs)
5162-5162: Hard tabs
Column: 1(MD010, no-hard-tabs)
5163-5163: Hard tabs
Column: 1(MD010, no-hard-tabs)
5165-5165: Hard tabs
Column: 1(MD010, no-hard-tabs)
5166-5166: Hard tabs
Column: 1(MD010, no-hard-tabs)
5167-5167: Hard tabs
Column: 1(MD010, no-hard-tabs)
5171-5171: Hard tabs
Column: 1(MD010, no-hard-tabs)
5172-5172: Hard tabs
Column: 1(MD010, no-hard-tabs)
5173-5173: Hard tabs
Column: 1(MD010, no-hard-tabs)
5174-5174: Hard tabs
Column: 1(MD010, no-hard-tabs)
5175-5175: Hard tabs
Column: 1(MD010, no-hard-tabs)
5177-5177: Hard tabs
Column: 1(MD010, no-hard-tabs)
5178-5178: Hard tabs
Column: 1(MD010, no-hard-tabs)
5179-5179: Hard tabs
Column: 1(MD010, no-hard-tabs)
5180-5180: Hard tabs
Column: 1(MD010, no-hard-tabs)
5181-5181: Hard tabs
Column: 1(MD010, no-hard-tabs)
5182-5182: Hard tabs
Column: 1(MD010, no-hard-tabs)
5183-5183: Hard tabs
Column: 1(MD010, no-hard-tabs)
5184-5184: Hard tabs
Column: 1(MD010, no-hard-tabs)
5185-5185: Hard tabs
Column: 1(MD010, no-hard-tabs)
5187-5187: Hard tabs
Column: 1(MD010, no-hard-tabs)
5188-5188: Hard tabs
Column: 1(MD010, no-hard-tabs)
5189-5189: Hard tabs
Column: 1(MD010, no-hard-tabs)
5191-5191: Hard tabs
Column: 1(MD010, no-hard-tabs)
5192-5192: Hard tabs
Column: 1(MD010, no-hard-tabs)
5193-5193: Hard tabs
Column: 1(MD010, no-hard-tabs)
5194-5194: Hard tabs
Column: 1(MD010, no-hard-tabs)
5195-5195: Hard tabs
Column: 1(MD010, no-hard-tabs)
5197-5197: Hard tabs
Column: 1(MD010, no-hard-tabs)
5198-5198: Hard tabs
Column: 1(MD010, no-hard-tabs)
5199-5199: Hard tabs
Column: 1(MD010, no-hard-tabs)
5201-5201: Hard tabs
Column: 1(MD010, no-hard-tabs)
5203-5203: Hard tabs
Column: 1(MD010, no-hard-tabs)
5204-5204: Hard tabs
Column: 1(MD010, no-hard-tabs)
5205-5205: Hard tabs
Column: 1(MD010, no-hard-tabs)
5206-5206: Hard tabs
Column: 1(MD010, no-hard-tabs)
5207-5207: Hard tabs
Column: 1(MD010, no-hard-tabs)
5209-5209: Hard tabs
Column: 1(MD010, no-hard-tabs)
5210-5210: Hard tabs
Column: 1(MD010, no-hard-tabs)
5211-5211: Hard tabs
Column: 1(MD010, no-hard-tabs)
5213-5213: Hard tabs
Column: 1(MD010, no-hard-tabs)
5214-5214: Hard tabs
Column: 1(MD010, no-hard-tabs)
5215-5215: Hard tabs
Column: 1(MD010, no-hard-tabs)
5217-5217: Hard tabs
Column: 1(MD010, no-hard-tabs)
5218-5218: Hard tabs
Column: 1(MD010, no-hard-tabs)
5220-5220: Hard tabs
Column: 1(MD010, no-hard-tabs)
5221-5221: Hard tabs
Column: 1(MD010, no-hard-tabs)
5222-5222: Hard tabs
Column: 1(MD010, no-hard-tabs)
5224-5224: Hard tabs
Column: 1(MD010, no-hard-tabs)
5226-5226: Hard tabs
Column: 1(MD010, no-hard-tabs)
5228-5228: Hard tabs
Column: 1(MD010, no-hard-tabs)
5229-5229: Hard tabs
Column: 1(MD010, no-hard-tabs)
5230-5230: Hard tabs
Column: 1(MD010, no-hard-tabs)
5231-5231: Hard tabs
Column: 1(MD010, no-hard-tabs)
5233-5233: Hard tabs
Column: 1(MD010, no-hard-tabs)
5320-5580: LGTM - MsgAuthorizeStakeGrants message documentation is comprehensiveThe documentation for the MsgAuthorizeStakeGrants message is well organized with:
- Clear message purpose and description
- Complete request/response examples
- Well-defined parameter tables and type definitions
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
5393-5393: Hard tabs
Column: 1(MD010, no-hard-tabs)
5394-5394: Hard tabs
Column: 1(MD010, no-hard-tabs)
5395-5395: Hard tabs
Column: 1(MD010, no-hard-tabs)
5397-5397: Hard tabs
Column: 1(MD010, no-hard-tabs)
5399-5399: Hard tabs
Column: 1(MD010, no-hard-tabs)
5401-5401: Hard tabs
Column: 1(MD010, no-hard-tabs)
5403-5403: Hard tabs
Column: 1(MD010, no-hard-tabs)
5404-5404: Hard tabs
Column: 1(MD010, no-hard-tabs)
5405-5405: Hard tabs
Column: 1(MD010, no-hard-tabs)
5409-5409: Hard tabs
Column: 1(MD010, no-hard-tabs)
5410-5410: Hard tabs
Column: 1(MD010, no-hard-tabs)
5411-5411: Hard tabs
Column: 1(MD010, no-hard-tabs)
5412-5412: Hard tabs
Column: 1(MD010, no-hard-tabs)
5413-5413: Hard tabs
Column: 1(MD010, no-hard-tabs)
5415-5415: Hard tabs
Column: 1(MD010, no-hard-tabs)
5416-5416: Hard tabs
Column: 1(MD010, no-hard-tabs)
5417-5417: Hard tabs
Column: 1(MD010, no-hard-tabs)
5418-5418: Hard tabs
Column: 1(MD010, no-hard-tabs)
5419-5419: Hard tabs
Column: 1(MD010, no-hard-tabs)
5420-5420: Hard tabs
Column: 1(MD010, no-hard-tabs)
5421-5421: Hard tabs
Column: 1(MD010, no-hard-tabs)
5422-5422: Hard tabs
Column: 1(MD010, no-hard-tabs)
5423-5423: Hard tabs
Column: 1(MD010, no-hard-tabs)
5425-5425: Hard tabs
Column: 1(MD010, no-hard-tabs)
5426-5426: Hard tabs
Column: 1(MD010, no-hard-tabs)
5427-5427: Hard tabs
Column: 1(MD010, no-hard-tabs)
5429-5429: Hard tabs
Column: 1(MD010, no-hard-tabs)
5430-5430: Hard tabs
Column: 1(MD010, no-hard-tabs)
5431-5431: Hard tabs
Column: 1(MD010, no-hard-tabs)
5432-5432: Hard tabs
Column: 1(MD010, no-hard-tabs)
5433-5433: Hard tabs
Column: 1(MD010, no-hard-tabs)
5435-5435: Hard tabs
Column: 1(MD010, no-hard-tabs)
5436-5436: Hard tabs
Column: 1(MD010, no-hard-tabs)
5437-5437: Hard tabs
Column: 1(MD010, no-hard-tabs)
5439-5439: Hard tabs
Column: 1(MD010, no-hard-tabs)
5441-5441: Hard tabs
Column: 1(MD010, no-hard-tabs)
5442-5442: Hard tabs
Column: 1(MD010, no-hard-tabs)
5443-5443: Hard tabs
Column: 1(MD010, no-hard-tabs)
5444-5444: Hard tabs
Column: 1(MD010, no-hard-tabs)
5445-5445: Hard tabs
Column: 1(MD010, no-hard-tabs)
5447-5447: Hard tabs
Column: 1(MD010, no-hard-tabs)
5448-5448: Hard tabs
Column: 1(MD010, no-hard-tabs)
5449-5449: Hard tabs
Column: 1(MD010, no-hard-tabs)
5451-5451: Hard tabs
Column: 1(MD010, no-hard-tabs)
5452-5452: Hard tabs
Column: 1(MD010, no-hard-tabs)
5453-5453: Hard tabs
Column: 1(MD010, no-hard-tabs)
5454-5454: Hard tabs
Column: 1(MD010, no-hard-tabs)
5456-5456: Hard tabs
Column: 1(MD010, no-hard-tabs)
5457-5457: Hard tabs
Column: 1(MD010, no-hard-tabs)
5458-5458: Hard tabs
Column: 1(MD010, no-hard-tabs)
5459-5459: Hard tabs
Column: 1(MD010, no-hard-tabs)
5461-5461: Hard tabs
Column: 1(MD010, no-hard-tabs)
5462-5462: Hard tabs
Column: 1(MD010, no-hard-tabs)
5464-5464: Hard tabs
Column: 1(MD010, no-hard-tabs)
5465-5465: Hard tabs
Column: 1(MD010, no-hard-tabs)
5466-5466: Hard tabs
Column: 1(MD010, no-hard-tabs)
5468-5468: Hard tabs
Column: 1(MD010, no-hard-tabs)
5469-5469: Hard tabs
Column: 1(MD010, no-hard-tabs)
5481-5481: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5515-5515: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5535-5535: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5545-5545: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5554-5554: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5563-5563: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5573-5573: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5581-5830: LGTM - MsgActivateStakeGrant message documentation is properly formattedThe documentation for the MsgActivateStakeGrant message includes all necessary components:
- Clear message purpose
- Complete request/response examples
- Well-defined parameter tables and response format
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
5651-5651: Hard tabs
Column: 1(MD010, no-hard-tabs)
5652-5652: Hard tabs
Column: 1(MD010, no-hard-tabs)
5653-5653: Hard tabs
Column: 1(MD010, no-hard-tabs)
5655-5655: Hard tabs
Column: 1(MD010, no-hard-tabs)
5657-5657: Hard tabs
Column: 1(MD010, no-hard-tabs)
5659-5659: Hard tabs
Column: 1(MD010, no-hard-tabs)
5660-5660: Hard tabs
Column: 1(MD010, no-hard-tabs)
5661-5661: Hard tabs
Column: 1(MD010, no-hard-tabs)
5665-5665: Hard tabs
Column: 1(MD010, no-hard-tabs)
5666-5666: Hard tabs
Column: 1(MD010, no-hard-tabs)
5667-5667: Hard tabs
Column: 1(MD010, no-hard-tabs)
5668-5668: Hard tabs
Column: 1(MD010, no-hard-tabs)
5669-5669: Hard tabs
Column: 1(MD010, no-hard-tabs)
5671-5671: Hard tabs
Column: 1(MD010, no-hard-tabs)
5672-5672: Hard tabs
Column: 1(MD010, no-hard-tabs)
5673-5673: Hard tabs
Column: 1(MD010, no-hard-tabs)
5674-5674: Hard tabs
Column: 1(MD010, no-hard-tabs)
5675-5675: Hard tabs
Column: 1(MD010, no-hard-tabs)
5676-5676: Hard tabs
Column: 1(MD010, no-hard-tabs)
5677-5677: Hard tabs
Column: 1(MD010, no-hard-tabs)
5678-5678: Hard tabs
Column: 1(MD010, no-hard-tabs)
5679-5679: Hard tabs
Column: 1(MD010, no-hard-tabs)
5681-5681: Hard tabs
Column: 1(MD010, no-hard-tabs)
5682-5682: Hard tabs
Column: 1(MD010, no-hard-tabs)
5683-5683: Hard tabs
Column: 1(MD010, no-hard-tabs)
5685-5685: Hard tabs
Column: 1(MD010, no-hard-tabs)
5686-5686: Hard tabs
Column: 1(MD010, no-hard-tabs)
5687-5687: Hard tabs
Column: 1(MD010, no-hard-tabs)
5688-5688: Hard tabs
Column: 1(MD010, no-hard-tabs)
5689-5689: Hard tabs
Column: 1(MD010, no-hard-tabs)
5691-5691: Hard tabs
Column: 1(MD010, no-hard-tabs)
5692-5692: Hard tabs
Column: 1(MD010, no-hard-tabs)
5693-5693: Hard tabs
Column: 1(MD010, no-hard-tabs)
5695-5695: Hard tabs
Column: 1(MD010, no-hard-tabs)
5697-5697: Hard tabs
Column: 1(MD010, no-hard-tabs)
5698-5698: Hard tabs
Column: 1(MD010, no-hard-tabs)
5699-5699: Hard tabs
Column: 1(MD010, no-hard-tabs)
5700-5700: Hard tabs
Column: 1(MD010, no-hard-tabs)
5701-5701: Hard tabs
Column: 1(MD010, no-hard-tabs)
5703-5703: Hard tabs
Column: 1(MD010, no-hard-tabs)
5704-5704: Hard tabs
Column: 1(MD010, no-hard-tabs)
5705-5705: Hard tabs
Column: 1(MD010, no-hard-tabs)
5707-5707: Hard tabs
Column: 1(MD010, no-hard-tabs)
5708-5708: Hard tabs
Column: 1(MD010, no-hard-tabs)
5709-5709: Hard tabs
Column: 1(MD010, no-hard-tabs)
5710-5710: Hard tabs
Column: 1(MD010, no-hard-tabs)
5712-5712: Hard tabs
Column: 1(MD010, no-hard-tabs)
5713-5713: Hard tabs
Column: 1(MD010, no-hard-tabs)
5715-5715: Hard tabs
Column: 1(MD010, no-hard-tabs)
5716-5716: Hard tabs
Column: 1(MD010, no-hard-tabs)
5717-5717: Hard tabs
Column: 1(MD010, no-hard-tabs)
5719-5719: Hard tabs
Column: 1(MD010, no-hard-tabs)
5720-5720: Hard tabs
Column: 1(MD010, no-hard-tabs)
5732-5732: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5766-5766: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5786-5786: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5796-5796: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5805-5805: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5814-5814: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
5824-5824: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
source/includes/_derivatives.md (4)
5-144: Documentation for L3DerivativeOrderBook endpoint looks goodThe new endpoint documentation is well-structured and includes all necessary components:
- Clear description of functionality
- IP rate limit group specification
- Request parameters with examples in Python and Go
- Response parameters with JSON schema tables
- Complete parameter descriptions
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
47-47: Hard tabs
Column: 1(MD010, no-hard-tabs)
48-48: Hard tabs
Column: 1(MD010, no-hard-tabs)
49-49: Hard tabs
Column: 1(MD010, no-hard-tabs)
51-51: Hard tabs
Column: 1(MD010, no-hard-tabs)
53-53: Hard tabs
Column: 1(MD010, no-hard-tabs)
54-54: Hard tabs
Column: 1(MD010, no-hard-tabs)
55-55: Hard tabs
Column: 1(MD010, no-hard-tabs)
56-56: Hard tabs
Column: 1(MD010, no-hard-tabs)
60-60: Hard tabs
Column: 1(MD010, no-hard-tabs)
61-61: Hard tabs
Column: 1(MD010, no-hard-tabs)
62-62: Hard tabs
Column: 1(MD010, no-hard-tabs)
63-63: Hard tabs
Column: 1(MD010, no-hard-tabs)
64-64: Hard tabs
Column: 1(MD010, no-hard-tabs)
66-66: Hard tabs
Column: 1(MD010, no-hard-tabs)
67-67: Hard tabs
Column: 1(MD010, no-hard-tabs)
68-68: Hard tabs
Column: 1(MD010, no-hard-tabs)
69-69: Hard tabs
Column: 1(MD010, no-hard-tabs)
70-70: Hard tabs
Column: 1(MD010, no-hard-tabs)
71-71: Hard tabs
Column: 1(MD010, no-hard-tabs)
72-72: Hard tabs
Column: 1(MD010, no-hard-tabs)
73-73: Hard tabs
Column: 1(MD010, no-hard-tabs)
74-74: Hard tabs
Column: 1(MD010, no-hard-tabs)
76-76: Hard tabs
Column: 1(MD010, no-hard-tabs)
77-77: Hard tabs
Column: 1(MD010, no-hard-tabs)
78-78: Hard tabs
Column: 1(MD010, no-hard-tabs)
80-80: Hard tabs
Column: 1(MD010, no-hard-tabs)
81-81: Hard tabs
Column: 1(MD010, no-hard-tabs)
82-82: Hard tabs
Column: 1(MD010, no-hard-tabs)
83-83: Hard tabs
Column: 1(MD010, no-hard-tabs)
84-84: Hard tabs
Column: 1(MD010, no-hard-tabs)
86-86: Hard tabs
Column: 1(MD010, no-hard-tabs)
87-87: Hard tabs
Column: 1(MD010, no-hard-tabs)
88-88: Hard tabs
Column: 1(MD010, no-hard-tabs)
90-90: Hard tabs
Column: 1(MD010, no-hard-tabs)
92-92: Hard tabs
Column: 1(MD010, no-hard-tabs)
93-93: Hard tabs
Column: 1(MD010, no-hard-tabs)
94-94: Hard tabs
Column: 1(MD010, no-hard-tabs)
95-95: Hard tabs
Column: 1(MD010, no-hard-tabs)
96-96: Hard tabs
Column: 1(MD010, no-hard-tabs)
98-98: Hard tabs
Column: 1(MD010, no-hard-tabs)
99-99: Hard tabs
Column: 1(MD010, no-hard-tabs)
100-100: Hard tabs
Column: 1(MD010, no-hard-tabs)
102-102: Hard tabs
Column: 1(MD010, no-hard-tabs)
104-104: Hard tabs
Column: 1(MD010, no-hard-tabs)
106-106: Hard tabs
Column: 1(MD010, no-hard-tabs)
107-107: Hard tabs
Column: 1(MD010, no-hard-tabs)
108-108: Hard tabs
Column: 1(MD010, no-hard-tabs)
109-109: Hard tabs
Column: 1(MD010, no-hard-tabs)
111-111: Hard tabs
Column: 1(MD010, no-hard-tabs)
112-112: Hard tabs
Column: 1(MD010, no-hard-tabs)
136-136: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
1312-1313: New fields added to DerivativeMarket schemaThe documentation has been updated to include two new fields in the DerivativeMarket schema:
admin_permissions: Integer field for admin permission levelsquote_decimals: Integer field for quote token decimal placesThe additions are well documented with clear descriptions.
1394-1401: New AdminPermission enum table is well documentedThe AdminPermission enum table clearly documents all permission levels with their corresponding codes and names. The permissions cover key market parameters like:
- Ticker
- Min price tick size
- Min quantity tick size
- Min notional
- Initial margin ratio
- Maintenance margin ratio
6931-6966: Comprehensive documentation for LocalOrderHashComputationThe documentation for LocalOrderHashComputation is thorough and provides:
- Clear explanation of purpose and benefits
- Implementation details and caveats
- Code examples for gas calculation and error handling
- Links to relevant source code
This is valuable information for HFT/API traders implementing local order hash computation.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
6935-6935: Link fragments should be valid
null(MD051, link-fragments)
6939-6939: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
6955-6955: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
| [ | ||
| {"Parameter": "denom", "Type": "String", "Description": "The token denom", "Required": "Yes"} | ||
| ] No newline at end of file |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Missing Required Parameter: "manager" Field
The JSON structure currently only includes the "denom" parameter. According to the PR objectives and API documentation summary, a "manager" parameter (of type String with the appropriate description) is also required. This omission could lead to client-side misconfigurations or incomplete requests.
Please update the JSON to include both parameters. For example:
[
- {"Parameter": "denom", "Type": "String", "Description": "The token denom", "Required": "Yes"}
+ {"Parameter": "denom", "Type": "String", "Description": "The token denom", "Required": "Yes"},
+ {"Parameter": "manager", "Type": "String", "Description": "The manager's Injective address", "Required": "Yes"}
]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| [ | |
| {"Parameter": "denom", "Type": "String", "Description": "The token denom", "Required": "Yes"} | |
| ] | |
| [ | |
| {"Parameter": "denom", "Type": "String", "Description": "The token denom", "Required": "Yes"}, | |
| {"Parameter": "manager", "Type": "String", "Description": "The manager's Injective address", "Required": "Yes"} | |
| ] |
permissionsmodule endpoints and messagesSummary by CodeRabbit
New Features
Documentation