Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create ics27-multiplexed-requirements.md #6281

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

womensrights
Copy link
Contributor

@womensrights womensrights commented May 8, 2024

Description

Requirements for to enable multiplexed interchain accounts - many controllers controlling many host accounts through a single channel


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against the correct branch (see CONTRIBUTING.md).
  • Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/).
  • Added relevant godoc comments.
  • Provide a conventional commit message to follow the repository standards.
  • Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
  • Re-reviewed Files changed in the GitHub PR explorer.
  • Review SonarCloud Report in the comment section below once CI passes.

Summary by CodeRabbit

  • Documentation
    • Introduced a comprehensive guide outlining business and functional requirements for enhancing the Interchain Accounts feature, addressing user pain points and outlining objectives for improved usability and scalability.

Copy link
Contributor

coderabbitai bot commented May 8, 2024

Walkthrough

Walkthrough

The ics27-multiplexed-requirements.md file has been updated to provide comprehensive business and functional requirements for enhancing the Interchain Accounts (ICA) feature in the Cosmos ecosystem. The document addresses user pain points and outlines objectives for improving scalability, usability, and flexibility. There were no changes made to the declarations of exported or public entities within this document.

Changes

Files Change Summary
docs/requirements/ics27-multiplexed-requirements.md Updated to include a detailed summary of requirements for enhancing the Interchain Accounts feature, addressing user pain points and outlining objectives for improved scalability, usability, and flexibility. No changes to the declarations of exported or public entities.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Out of diff range and nitpick comments (7)
docs/requirements/ics27-multiplexed-requirements.md (7)

11-11: Consider adding a comma after "Account Flexibility" for better readability.


13-13: Consider using "time-consuming" with a hyphen for correct spelling.


19-19: Use "add-on" with a hyphen in this context for correct spelling.


26-26: Use "per-user" with a hyphen when used as an adjective.


56-56: Consider adding a comma after "requirements" for better readability.


83-83: Use "per-user" with a hyphen when used as an adjective.


85-85: Ensure consistency in spelling; use either "acknowledgement" or "acknowledgment" throughout the document.

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between edd41da and 60f8465.
Files selected for processing (1)
  • docs/requirements/ics27-multiplexed-requirements.md (1 hunks)
Additional Context Used
LanguageTool (7)
docs/requirements/ics27-multiplexed-requirements.md (7)

Near line 11: Possible missing comma found.
Context: ... are listed: - Account Flexibility - Currently host accounts can only be of type `Base...


Near line 13: This word is normally spelled with a hyphen.
Context: ...uts and subsequent channel closures are time consuming and difficult to manage - *Scalability...


Near line 19: This noun is usually spelled with a hyphen.
Context: ...iddleware solves this problem but is an add on to the application rather than a defaul...


Near line 26: In this context, “per-user” forms an adjective and is spelled with a hyphen.
Context: ...nt management for accounts created on a per user basis - To streamline workflows using t...


Near line 56: Possible missing comma found.
Context: ...desirable, it is out of scope for these requirements as a solution is applicable to applicat...


Near line 83: In this context, “per-user” forms an adjective and is spelled with a hyphen.
Context: ...implementing additional middleware on a per user basis | ------------ | ------ | | 3.06 ...


Near line 85: Do not mix variants of the same word (‘acknowledgement’ and ‘acknowledgment’) within a single text.
Context: ...in account and return the result in the acknowledgement | ------------ | ------ | ### 4 - Ho...

GitHub Check Runs (1)
lint failure (3)

docs/requirements/ics27-multiplexed-requirements.md: [failure] 53-53: Headings should be surrounded by blank lines
docs/requirements/ics27-multiplexed-requirements.md:53 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "# Functional requirements"] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md022.md


docs/requirements/ics27-multiplexed-requirements.md: [failure] 54-54: Headings should be surrounded by blank lines
docs/requirements/ics27-multiplexed-requirements.md:54 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "## Assumptions and dependencies"] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md022.md

Path-based Instructions (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 9

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 60f8465 and b766721.
Files selected for processing (1)
  • docs/requirements/ics27-multiplexed-requirements.md (1 hunks)
Additional Context Used
LanguageTool (7)
docs/requirements/ics27-multiplexed-requirements.md (7)

Near line 13: This word is normally spelled with a hyphen.
Context: ...uts and subsequent channel closures are time consuming and difficult to manage - *Scalability...


Near line 17: Possible missing comma found.
Context: ...nsfer could succeed and the ICA message fail resulting in an incomplete workflow. ...


Near line 19: This noun is usually spelled with a hyphen.
Context: ...iddleware solves this problem but is an add on to the application rather than a defaul...


Near line 26: In this context, “per-user” forms an adjective and is spelled with a hyphen.
Context: ...nt management for accounts created on a per user basis - To streamline workflows using t...


Near line 57: Possible missing comma found.
Context: ...desirable, it is out of scope for these requirements as a solution is applicable to applicat...


Near line 84: In this context, “per-user” forms an adjective and is spelled with a hyphen.
Context: ...implementing additional middleware on a per user basis | ------------ | ------ | | 3.06 ...


Near line 86: Do not mix variants of the same word (‘acknowledgement’ and ‘acknowledgment’) within a single text.
Context: ...in account and return the result in the acknowledgement | ------------ | ------ | ### 4 - Ho...

Path-based Instructions (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
womensrights and others added 4 commits May 8, 2024 21:44
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 24

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between b766721 and 7715ce3.
Files selected for processing (1)
  • docs/requirements/ics27-multiplexed-requirements.md (1 hunks)
Additional Context Used
LanguageTool (7)
docs/requirements/ics27-multiplexed-requirements.md (7)

Near line 11: Possible missing comma found.
Context: ... are listed: - Account Flexibility - Currently host accounts can only be of type `Base...


Near line 13: This word is normally spelled with a hyphen.
Context: ...uts and subsequent channel closures are time consuming and difficult to manage - *Scalability...


Near line 19: This noun is usually spelled with a hyphen.
Context: ...iddleware solves this problem but is an add on to the application rather than a defaul...


Near line 26: In this context, “per-user” forms an adjective and is spelled with a hyphen.
Context: ...nt management for accounts created on a per user basis - To streamline workflows using t...


Near line 57: Possible missing comma found.
Context: ...desirable, it is out of scope for these requirements as a solution is applicable to applicat...


Near line 84: In this context, “per-user” forms an adjective and is spelled with a hyphen.
Context: ...implementing additional middleware on a per user basis | ------------ | ------ | | 3.06 ...


Near line 86: Do not mix variants of the same word (‘acknowledgement’ and ‘acknowledgment’) within a single text.
Context: ...in account and return the result in the acknowledgement | ------------ | ------ | ### 4 - Ho...

Path-based Instructions (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
| 3.04 | The controller of the interchain account should be able to receive information about the balance of the interchain account in the acknowledgment after a transaction was executed by the host | ------------ | ------ |
| 3.05 | The user of the controller should be able to receive all the information contained in the acknowledgment without implementing additional middleware on a per user basis | ------------ | ------ |
| 3.06 | Callbacks on the packet lifecycle should be supported by default | ------------ | ------ |
| 3.07 | A user can perform module safe queries through a host chain account and return the result in the acknowledgement | ------------ | ------ |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure consistency in the spelling of "acknowledgment".

- in the acknowledgement
+ in the acknowledgment

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.

Suggested change
| 3.07 | A user can perform module safe queries through a host chain account and return the result in the acknowledgement | ------------ | ------ |
| 3.07 | A user can perform module safe queries through a host chain account and return the result in the acknowledgment | ------------ | ------ |

docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 7715ce3 and ebf6dbc.
Files selected for processing (1)
  • docs/requirements/ics27-multiplexed-requirements.md (1 hunks)
Additional Context Used
LanguageTool (3)
docs/requirements/ics27-multiplexed-requirements.md (3)

Near line 17: Possible missing comma found.
Context: ...nsfer could succeed and the ICA message fail resulting in an incomplete workflow. ...


Near line 26: In this context, “per-user” forms an adjective and is spelled with a hyphen.
Context: ...nt management for accounts created on a per user basis - To streamline workflows using t...


Near line 84: In this context, “per-user” forms an adjective and is spelled with a hyphen.
Context: ...implementing additional middleware on a per user basis | ------------ | ------ | | 3.06 ...

GitHub Check Runs (1)
lint failure (2)

docs/requirements/ics27-multiplexed-requirements.md: [failure] 26-26: Lists should be surrounded by blank lines
docs/requirements/ics27-multiplexed-requirements.md:26 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- To facilitate performant cro..."] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md032.md

Path-based Instructions (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between ebf6dbc and 0933ce7.
Files selected for processing (1)
  • docs/requirements/ics27-multiplexed-requirements.md (1 hunks)
Additional Context Used
LanguageTool (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Near line 11: Possible missing comma found.
Context: ... are listed: - Account Flexibility - Currently host accounts can only be of type `Base...

GitHub Check Runs (1)
lint failure (3)

docs/requirements/ics27-multiplexed-requirements.md: [failure] 26-26: Lists should be surrounded by blank lines
docs/requirements/ics27-multiplexed-requirements.md:26 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- To facilitate performant cro..."] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md032.md


docs/requirements/ics27-multiplexed-requirements.md: [failure] 73-73: Table column count
docs/requirements/ics27-multiplexed-requirements.md:73:145 MD056/table-column-count Table column count [Expected: 4; Actual: 6; Too many cells, extra data will be missing] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md056.md

Path-based Instructions (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 13

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 0933ce7 and d4b9f0b.
Files selected for processing (1)
  • docs/requirements/ics27-multiplexed-requirements.md (1 hunks)
Additional Context Used
LanguageTool (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Near line 11: Possible missing comma found.
Context: ... are listed: - Account Flexibility - Currently host accounts can only be of type `Base...

GitHub Check Runs (1)
lint failure (2)

docs/requirements/ics27-multiplexed-requirements.md: [failure] 26-26: Lists should be surrounded by blank lines
docs/requirements/ics27-multiplexed-requirements.md:26 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- To streamline workflows usin..."] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md032.md

Path-based Instructions (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"


The current pain points for existing ICA users are listed:

- *Account Flexibility* - Currently host accounts can only be of type `BaseAccount`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding a comma after "listed" for better readability.

- The current pain points for existing ICA users are listed:
+ The current pain points for existing ICA users are listed:

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.

Suggested change
- *Account Flexibility* - Currently host accounts can only be of type `BaseAccount`

Comment on lines 25 to 26
Enable different account types, to be controlled remotely
- To streamline workflows using token transfer and interchain accounts in combination
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lists should be surrounded by blank lines for proper markdown formatting.

- Enable different account types, to be controlled remotely
- To streamline workflows using token transfer and interchain accounts in combination
+ 
+ Enable different account types, to be controlled remotely
+ - To streamline workflows using token transfer and interchain accounts in combination
+ 

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.

Suggested change
Enable different account types, to be controlled remotely
- To streamline workflows using token transfer and interchain accounts in combination
Enable different account types, to be controlled remotely
- To streamline workflows using token transfer and interchain accounts in combination

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 12

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between d4b9f0b and 48f6984.
Files selected for processing (1)
  • docs/requirements/ics27-multiplexed-requirements.md (1 hunks)
Additional Context Used
Path-based Instructions (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Comment on lines +25 to +26
- Enable different account types, to be controlled remotely
- To streamline workflows using token transfer and interchain accounts in combination
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lists should be surrounded by blank lines for proper markdown formatting.

+ 
- Enable different account types, to be controlled remotely
- To streamline workflows using token transfer and interchain accounts in combination
+ 

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.

Suggested change
- Enable different account types, to be controlled remotely
- To streamline workflows using token transfer and interchain accounts in combination
- Enable different account types, to be controlled remotely
- To streamline workflows using token transfer and interchain accounts in combination

docs/requirements/ics27-multiplexed-requirements.md Outdated Show resolved Hide resolved
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (13)
docs/requirements/ics27-multiplexed-requirements.md (13)

5-5: Remove trailing space.

Remove the trailing space at the end of the line for cleaner formatting.

- These requirements aim to alleviate current pain points and enhance the usability of the feature. 
+ These requirements aim to alleviate current pain points and enhance the usability of the feature.

13-13: Add a hyphen to "time-consuming".

Add a hyphen to form the correct adjective.

- Timeouts and subsequent channel closures are time consuming and difficult to manage
+ Timeouts and subsequent channel closures are time-consuming and difficult to manage

17-17: Remove trailing space.

Remove the trailing space at the end of the line for cleaner formatting.

- The transfer could succeed and the ICA message fail, resulting in an incomplete workflow. 
+ The transfer could succeed and the ICA message fail, resulting in an incomplete workflow.

19-19: Add a hyphen to "add-on".

Add a hyphen to form the correct adjective.

- the callbacks middleware solves this problem but is an add on to the application rather than a default
+ the callbacks middleware solves this problem but is an add-on to the application rather than a default

21-21: Consider changing "Whitelisiting" to "Whitelisting".

Correct the spelling error for clarity.

- *Whitelisiting messages* - this devex is more complicated than having a blacklist
+ *Whitelisting messages* - this devex is more complicated than having a blacklist

47-47: Correct the spelling of "principle" to "principal".

Correct the spelling error for clarity.

- Nolus enables users to borrow assets and use the inflation from staking rewards to repay the interest on the principle.
+ Nolus enables users to borrow assets and use the inflation from staking rewards to repay the interest on the principal.

52-52: Remove trailing space.

Remove the trailing space at the end of the line for cleaner formatting.

- Nomos enable NFTs to be minted on Injective on host accounts controlled from the Xion chain, providing a single interface for users, enabling chain abstraction. 
+ Nomos enable NFTs to be minted on Injective on host accounts controlled from the Xion chain, providing a single interface for users, enabling chain abstraction.

57-57: Remove trailing space.

Remove the trailing space at the end of the line for cleaner formatting.

- Although having atomic transfer plus action workflows with Interchain Accounts is desirable, it is out of scope for these requirements, as a solution is applicable to applications beyond Interchain Accounts alone. 
+ Although having atomic transfer plus action workflows with Interchain Accounts is desirable, it is out of scope for these requirements, as a solution is applicable to applications beyond Interchain Accounts alone.

67-67: Remove trailing space.

Remove the trailing space at the end of the line for cleaner formatting.

- | 1.01 | The host chain should accept all message types by default and maintain a blacklist of message types it does not permit | ------------ | ------ | 
+ | 1.01 | The host chain should accept all message types by default and maintain a blacklist of message types it does not permit | ------------ | ------ |

73-73: Correct the table formatting by ensuring the correct number of cells per row.

Ensure consistency in table formatting for clarity.

- | 2.01 | The controller of the interchain account must have authority over the account on the host chain to execute messages | -- | ----------- | 
+ | 2.01 | The controller of the interchain account must have authority over the account on the host chain to execute messages | ------------ | ------ |

84-84: Add a hyphen to "per-user" to form the correct adjective.

Ensure consistency in the use of compound adjectives.

- without implementing additional middleware on a per user basis
+ without implementing additional middleware on a per-user basis

86-86: Remove trailing space.

Remove the trailing space at the end of the line for cleaner formatting.

- | 3.07 | A user can perform module safe queries through a host chain account and return the result in the acknowledgment | ------------ | ------ |  
+ | 3.07 | A user can perform module safe queries through a host chain account and return the result in the acknowledgment | ------------ | ------ |

100-100: Remove trailing space.

Remove the trailing space at the end of the line for cleaner formatting.

- | 5.01 | The number of packet round trips to register an account, load the account with tokens and execute messages on the account should be minimised | ------------ | ------ | 
+ | 5.01 | The number of packet round trips to register an account, load the account with tokens and execute messages on the account should be minimised | ------------ | ------ |
Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 48f6984 and c69b856.

Files selected for processing (1)
  • docs/requirements/ics27-multiplexed-requirements.md (1 hunks)
Additional context used
Path-based instructions (1)
docs/requirements/ics27-multiplexed-requirements.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

@damiannolan
Copy link
Member

Should this be merged or closed? Or migrated elsewhere for the time being.

I'm also fine with leaving it sit. Just doing some housekeeping 🧹

@womensrights
Copy link
Contributor Author

I think it should be merged, can always be changed later but given its a draft think its fine

Copy link
Contributor

@DimitrisJim DimitrisJim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sgtm to merge even as draft.

Copy link
Member

@damiannolan damiannolan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree with @DimitrisJim. Feel free to merge if you want. Could maybe add a notice at the top of document that it is a draft or something like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants