Added token house grants

[krofax]

Description

Added token house grants from Emily

Tests

Additional context

Metadata

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	9270569
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/677eb4da96ae660008e5e2c1
😎 Deploy Preview	https://deploy-preview-1228--docs-optimism.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request introduces modifications to two files: pages/chain/identity/schemas.mdx and words.txt. In the schemas document, the changes include updating capitalization in various headings and adding a new section on "Schemas related to token house grants," which features a detailed schema for "Token house grant approved." This new schema outlines attributes such as issuer, recipient, project reference UID, amounts approved for user incentives and builders, season, intent, mission, approval date, and metadata URL.

In the words.txt file, several new terms have been added, including "Ankr," "Immunefi," "Mitigations," "Pyth," "Pyth's," "SEPOLIA," "Sepolia," and "voxel," while the term "inteoperates" was removed. These modifications aim to enhance documentation consistency and expand the project's vocabulary.

Possibly related PRs

• Update schemas.mdx #710: This PR updates the schemas.mdx file, which is directly related to the main PR's changes in the same file, focusing on governance contributions.
• Update schemas.mdx #719: This PR also modifies the schemas.mdx file, adding new schemas relevant to Retro Funding, which aligns with the main PR's updates to the same document.
• Update schemas.mdx #727: This PR updates the schemas.mdx file to include additional attester address requirements, which is relevant to the changes made in the main PR.
• Update schemas to add new application attestation schema.mdx #944: This PR updates the schemas.mdx file to reflect changes in the Retro Funding Application schema, which is closely related to the new content added in the main PR.
• Fix duplicated Retro Funding Governance contribution issuer #983: This PR introduces new schemas and updates existing ones in the schemas.mdx file, which is relevant to the changes made in the main PR regarding schema definitions.
• Update schemas.mdx #1024: This PR adds new schemas related to governance contributions in the schemas.mdx file, which connects to the main PR's focus on enhancing schema documentation.

Suggested reviewers

• sbvegan

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 382a714 and 9270569.

📒 Files selected for processing (1)

• pages/chain/identity/schemas.mdx (5 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• pages/chain/identity/schemas.mdx

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

pages/chain/identity/schemas.mdx (1)

101-120: LGTM! Well-structured schema for token house grants.

The new schema section is well-documented and follows the established pattern. The explicit date format specification and clear field descriptions enhance maintainability.

Consider adding descriptions for the currently null fields (refUID and MetadataUrl) to indicate their intended future use.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4daaff2 and 382a714.

📒 Files selected for processing (2)

• pages/chain/identity/schemas.mdx (5 hunks)
• words.txt (6 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

pages/chain/identity/schemas.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

• Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
• Avoid gender-specific language and use the imperative form.
• Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
• Ensure proper nouns are capitalized in sentences.
• Apply the Oxford comma.
• Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
• Use correct spelling and grammar at all times (IMPORTANT).
• For H1, H2, and H3 headers:
  1. Use sentence case, capitalizing only the first word.
  2. Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
  3. Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
• Flag any headers that seem to inconsistently apply these rules for manual review.
• When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
  "

🪛 LanguageTool

pages/chain/identity/schemas.mdx

[grammar] ~42-~42: The singular determiner ‘this’ may not agree with the plural noun ‘organizations’. Did you mean “these”?
Context: ...| parentOrgUID | The attestation UID of this organizations's parent, in case it has ...

(THIS_NNS)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Redirect rules - docs-optimism
• GitHub Check: Header rules - docs-optimism
• GitHub Check: Pages changed - docs-optimism
• GitHub Check: pr-workflow

🔇 Additional comments (2)

words.txt (1)

13-13: LGTM! New terms added correctly.

The new terms have been added in alphabetical order and maintain the existing pattern of including both uppercase and proper case variations where applicable.

Also applies to: 154-154, 203-203, 301-302, 337-339, 413-413

pages/chain/identity/schemas.mdx (1)

18-18: LGTM! Consistent heading capitalization.

The changes to heading capitalization align with the coding guidelines for sentence case in headers while preserving proper nouns.

Also applies to: 144-144, 158-158

[sbvegan]

looks good to merge, the coderabbit nit seems fine to add if you want. We should talk to Emily about the current identity item we have planned for this sprint