[Intermediate]: Write a Blog Post on HIP 1313: High Volume Entity Creation

[aceppaluni]

🧩 Intermediate Contributors

This issue is intended for contributors who are already very familiar with the
Hiero Website codebase and its architectural patterns.

You should feel comfortable with:

• Netlify previews and tests
• The Hiero website repository structure
• understanding Hugo templating concepts without step-by-step guidance
• Editing and organizing Markdown at scale
• Making pull requests with minimal guidance
• navigating layouts/, content/, partials/, and static/
• following the standard PR workflow without additional onboarding

If this is your very first contribution to the project, we recommend starting with a few
Good First Issues before working on this one.

🐞 Problem Description

HIP-1313: High-Volume Entity Creation has recently been approved by the TSC.
Link for approval can be found here hiero-ledger/hiero-improvement-proposals#1313

Currently, the Hiero website does not yet have a blog post covering HIP 1313. As a result:

Community members cannot read a structured overview of HIP 1313 on the site.
There is no centralized reference for key points, discussion, and links to the proposal.
This reduces visibility for important protocol improvements and upcoming changes.
Why this matters:

HIPs (Hiero Improvement Proposals) are critical for communicating protocol changes, governance decisions, and technical improvements. Publishing a blog post for HIP 1313:

Keeps the community informed.
Increases engagement with the protocol discussion.
Provides a canonical reference on the website for contributors and external audiences.

💡 Expected Solution

We should write a blog post detailing the approved HIP

• Add a new blog post for HIP 1313 in the /content/posts/ directory.
• Ensure metadata in front matter includes: title, date, author, summary and featured image banner
• Include links to the HIP 1313 proposal in the post body.
• Maintain consistent styling with other blog posts.
• Ensure the post is visible in the blog list and renders correctly on the website.

🧠 Implementation Notes

1. Create Blog Post File
   • Path: content/posts/hip-1261.md
   • Add front matter, for example:

+++
title = "HIP 1261: [Short Descriptive Title]"
date = 2026-02-11T12:00:00-07:00
author = "Contributor Name"
abstract = "An overview of HIP 1261 and its implications for the Hiero protocol."
featured_image = "/images/posts/hip-1261.png"
+++

2. Write Blog Post Content

   • Include sections:
     a. Introduction / Background
     b. Overview of HIP 1261
     c. Motivation and goals
     d. Implementation or technical details (if applicable)
     e. References and links to the official HIP markdown file

   • Use Markdown for headings, lists, links, images, and code blocks.

3. Optional Assets

   • If using diagrams or images, place them in static/images/

4. Test Locally

   • Run locally
   • Verify:
     a. The new post appears in /posts/
     b. Layout and formatting match existing posts
     c. Links, images, and headings render correctly
     d. Post shows in the blog feed

5. Commit and Open PR

   • Commit changes with DCO and GPG-signed commits:

git add content/posts/hip-1261.md
git commit -s -S -m "Add blog post for HIP 1261"
git push origin <branch-name>

✅ Acceptance Criteria

To merge this issue, the pull request must:

• Fully address the problem described above
• Follow existing project conventions and patterns
• Include tests or example updates where appropriate
• Pass all CI checks
• Include a valid changelog entry
• Use DCO and GPG-signed commits

📚 Additional Context or Resources

• Website Developer Docs

[mohityadav8]

/assign

[exploreriii]

@coderabbitai plan

[coderabbitai]

Coding Plan

Summary

• Create a single markdown file at content/posts/hip-1313.md using TOML front matter and following the exact structure of existing HIP posts (hip-1261.md, hip-1137.md)
• Content covers the high-volume throttle lane opt-in mechanism, variable pricing, supported transaction types, and ecosystem impact based on the approved HIP specification
• No code changes required; this is a pure content addition following established patterns
• Deliverables: blog post file, featured image in public/images/, and changelog entry

Design Choices

Design Choice 1: Featured image creation approach

Options Considered:

1. Create a new custom image specific to HIP-1313 (e.g., /images/hip-1313-banner.png)
2. Reuse an existing generic HIP or protocol-related banner image from public/images/

Chosen Option: 1

Rationale: Creating a dedicated image maintains consistency with other HIP posts that have unique banners, and the ticket explicitly lists "featured image banner" as a deliverable. If custom image creation is not feasible, the fallback image (/images/HI60000_GetInvolvedBanner_V1.jpg) will be used automatically.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Create HIP-1313 Blog Post

This phase delivers the complete blog post including the markdown file with front matter, structured content, featured image, and changelog entry.

Task 1: Create Blog Post File with Front Matter

Create the markdown file with properly formatted TOML front matter following existing HIP post conventions.

• Create new file at content/posts/hip-1313.md
• Use TOML front matter delimited by +++ (not YAML)
• Include required fields: title (format: "HIP-1313: High Volume Entity Creation"), date (current date in ISO 8601 format with timezone), featured_image (path to image in /images/)
• Include strongly recommended fields: abstract (one-sentence summary), [[authors]] block with name and organization
• Include optional fields: categories = ["Blog"], tags array including ["HIP", "Entity Creation", "Throttling", "Protocol"], duration (estimate ~5-6 min read)
• Reference content/posts/hip-1261.md and content/posts/hip-1137.md for exact formatting patterns

Task 2: Write Blog Post Content Sections

Author the blog post body following the structure established by existing HIP posts.

• Begin with 1-2 opening paragraphs (no heading) providing context and hook about high-volume entity creation
• Use --- horizontal rules as section dividers between all major sections
• Include these ## sections following the hip-1137.md pattern:
  • Introduction and Background: Context on current throttling limitations for entity creation
  • What is HIP-1313?: Explain the parallel "high-volume" throttle lane concept and opt-in mechanism (high_volume flag)
  • Motivation and Goals: Why this matters—enabling high-throughput use cases while preserving network stability
  • Technical Implementation: Cover the bool high_volume = 25 wire change, supported transaction types (CryptoCreate, TokenCreate, FileCreate, etc.), variable-rate pricing with multiplier, and the new high_volume_pricing_multiplier result field
  • Impact on the Ecosystem: Benefits for developers, SDK support (Transaction.setHighVolume()), Mirror Node API changes
  • Conclusion: Summary and forward-looking statement
  • References: Link to the HIP-1313 specification on GitHub (https://hips.hedera.com/hip/hip-1313 or the GitHub PR)
• Use bold for key terms, unordered lists for features/benefits
• No code blocks (consistent with other HIP posts), no raw HTML, no Hugo shortcodes

Task 3: Add Featured Image

Provide a featured image for the blog post card and header.

• Add image file to public/images/ directory (e.g., public/images/hip-1313-high-volume-entity-creation.png)
• Use naming convention consistent with existing posts (kebab-case, descriptive)
• Reference the image in front matter as /images/hip-1313-high-volume-entity-creation.png
• If creating a custom image is not feasible, document that the fallback image will be used and update front matter accordingly

Task 4: Add Changelog Entry

Document the addition in the project changelog.

• Update CHANGELOG.md under the ## [Unreleased] section
• Add an ### Added subsection if not present (per Keep a Changelog format)
• Add bullet entry: - Add blog post for HIP-1313: High Volume Entity Creation

🤖 Prompt for AI agents

This phase creates the complete HIP-1313 blog post as a pure content addition —
no application code changes are required.

**1. Create `content/posts/hip-1313.md`**
- Use TOML front matter delimited by `+++` (not YAML `---`)
- Refer to `content/posts/hip-1261.md` and `content/posts/hip-1137.md` for exact
front matter field formatting and structure
- Required front matter fields:
  - `title = "HIP-1313: High Volume Entity Creation"`
  - `date` in ISO 8601 format with timezone (current date)
  - `featured_image = "/images/hip-1313-high-volume-entity-creation.png"`
- Strongly recommended front matter fields:
  - `abstract`: one-sentence summary of the post
  - `[[authors]]` block with `name` and `organization`
- Optional front matter fields:
  - `categories = ["Blog"]`
  - `tags = ["HIP", "Entity Creation", "Throttling", "Protocol"]`
  - `duration` (~5-6 min read)

**2. Write the blog post body**
- Start with 1-2 opening paragraphs (no heading) as context/hook
- Separate all major sections with `---` horizontal rules
- Include the following `##` sections in order:
- **Introduction and Background** — current throttling limitations for entity
creation
- **What is HIP-1313?** — the parallel "high-volume" throttle lane and opt-in
`high_volume` flag
  - **Motivation and Goals** — high-throughput use cases and network stability
- **Technical Implementation** — `bool high_volume = 25` wire change, supported
transaction types (CryptoCreate, TokenCreate, FileCreate, etc.), variable-rate
pricing with multiplier, and the `high_volume_pricing_multiplier` result field
- **Impact on the Ecosystem** — developer benefits, SDK support via
`Transaction.setHighVolume()`, Mirror Node API changes
  - **Conclusion** — summary and forward-looking statement
  - **References** — link to https://hips.hedera.com/hip/hip-1313
- Use **bold** for key terms and unordered lists for features/benefits
- Do NOT use code blocks, raw HTML, or Hugo shortcodes

**3. Add the featured image**
- Place the image file at
`public/images/hip-1313-high-volume-entity-creation.png`
- Use kebab-case, descriptive naming consistent with existing post images
- If a custom image cannot be created, update the `featured_image` front matter
field to use the fallback `/images/HI60000_GetInvolvedBanner_V1.jpg`

**4. Update `CHANGELOG.md`**
- Add the entry under `## [Unreleased]` → `### Added` (create the subsection if
absent)
- Entry: `- Add blog post for HIP-1313: High Volume Entity Creation`

Research

The Hiero website is a Next.js application that renders blog posts from Markdown files in content/posts/. Posts use TOML front matter (delimited by +++) and are parsed by src/lib/posts.ts. Two existing HIP posts (hip-1261.md and hip-1137.md) serve as direct templates, using consistent section structures with ## headings and --- dividers. Images are stored in public/images/ and referenced with absolute paths like /images/filename.png. The CHANGELOG follows Keep a Changelog format.

---

🚀 Next Steps

🤖 All AI agent prompts combined

This phase creates the complete HIP-1313 blog post as a pure content addition —
no application code changes are required.

**1. Create `content/posts/hip-1313.md`**
- Use TOML front matter delimited by `+++` (not YAML `---`)
- Refer to `content/posts/hip-1261.md` and `content/posts/hip-1137.md` for exact
front matter field formatting and structure
- Required front matter fields:
  - `title = "HIP-1313: High Volume Entity Creation"`
  - `date` in ISO 8601 format with timezone (current date)
  - `featured_image = "/images/hip-1313-high-volume-entity-creation.png"`
- Strongly recommended front matter fields:
  - `abstract`: one-sentence summary of the post
  - `[[authors]]` block with `name` and `organization`
- Optional front matter fields:
  - `categories = ["Blog"]`
  - `tags = ["HIP", "Entity Creation", "Throttling", "Protocol"]`
  - `duration` (~5-6 min read)

**2. Write the blog post body**
- Start with 1-2 opening paragraphs (no heading) as context/hook
- Separate all major sections with `---` horizontal rules
- Include the following `##` sections in order:
- **Introduction and Background** — current throttling limitations for entity
creation
- **What is HIP-1313?** — the parallel "high-volume" throttle lane and opt-in
`high_volume` flag
  - **Motivation and Goals** — high-throughput use cases and network stability
- **Technical Implementation** — `bool high_volume = 25` wire change, supported
transaction types (CryptoCreate, TokenCreate, FileCreate, etc.), variable-rate
pricing with multiplier, and the `high_volume_pricing_multiplier` result field
- **Impact on the Ecosystem** — developer benefits, SDK support via
`Transaction.setHighVolume()`, Mirror Node API changes
  - **Conclusion** — summary and forward-looking statement
  - **References** — link to https://hips.hedera.com/hip/hip-1313
- Use **bold** for key terms and unordered lists for features/benefits
- Do NOT use code blocks, raw HTML, or Hugo shortcodes

**3. Add the featured image**
- Place the image file at
`public/images/hip-1313-high-volume-entity-creation.png`
- Use kebab-case, descriptive naming consistent with existing post images
- If a custom image cannot be created, update the `featured_image` front matter
field to use the fallback `/images/HI60000_GetInvolvedBanner_V1.jpg`

**4. Update `CHANGELOG.md`**
- Add the entry under `## [Unreleased]` → `### Added` (create the subsection if
absent)
- Entry: `- Add blog post for HIP-1313: High Volume Entity Creation`

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For design choice 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!

[ayesigaisaac]

Hi @mohityadav8

I’d like to work on this issue (#433).

I’ll create the HIP-1313 blog post following the existing Hiero blog structure and make sure it matches the current styling/content conventions.

Thanks!

[mohityadav8]

Hi @ayesigaisaac
Thanks for asking but I have already created a pr #445 on this issue and that's under review 😊

[ayesigaisaac]

Ok .. let me work on another ones

…

On Sun, 17 May 2026 at 13:44, Mohit Yadav ***@***.***> wrote: *mohityadav8* left a comment (hiero-ledger/hiero-website#433) <#433 (comment)> Hi @ayesigaisaac <https://github.com/ayesigaisaac> Thanks for asking but I have already created a pr #445 <#445> on this issue and that's under review 😊 — Reply to this email directly, view it on GitHub <#433 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BLPLHYLOB3IYTTELNLAAJP343GJZVAVCNFSM6AAAAACYYF4UFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINZQGMZTEMBZGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[aceppaluni]

@ayesigaisaac Would this interest you? #451

If so please leave a comment to be assigned. Thank you!

[ayesigaisaac]

Yesss am interested

…

On Tue, 19 May 2026 at 21:18, aceppaluni ***@***.***> wrote: *aceppaluni* left a comment (hiero-ledger/hiero-website#433) <#433 (comment)> @ayesigaisaac <https://github.com/ayesigaisaac> Would this interest you? #451 <#451> If so please leave a comment to be assigned. Thank you! — Reply to this email directly, view it on GitHub <#433 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BLPLHYODJXJNZP6CSL2TS3D43SQO7AVCNFSM6AAAAACYYF4UFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIOJQG4ZDMOJYGY> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ayesigaisaac]

@aceppaluni assign me to any open issue