test BI

[DeathGun44]

🧑‍🎓 Beginner Issue

Welcome! This is a Beginner Issue designed to help you learn the codebase.

🏁 When this issue is complete, you will have:

✅ Researched a file or method in detail
✅ Followed SDK patterns to implement a solution
✅ Researched and identified appropriate programming constructs to solve the problem
✅ Created basic tests
✅ Delivered a clean, review-ready pull request

🐞 Problem Description

💡 Expected Solution

🔍 Research Pointers

🛠️ Implementation Notes

🧠 Beginner Contributors — Prerequisites & Expectations

Caution

Beginner issues are low-risk but we expect a working solution.

Important

We recommend completing at least 3 good first issues before attempting a beginner issue.

Difficulty:

• Requires building knowledge of the specific file(s)
• Beginner to intermediate Coding skills

Tip

You should be comfortable with:

• Forking, branching, committing (with DCO + GPG signing), and opening a pull request without a tutorial
• Reading beginner to intermediate code you did not write and following its patterns
• Handling simple merge conflicts
• Keeping your fork up to date with main by rebasing
• Looking things up on your own before asking for help

If any of that feels unfamiliar, good first issues might still be the most rewarding path for you right now — find one here.
You can always come back when you are ready.

⚠️ AI Usage Policy

• AI can help you understand the codebase and the problem
• Using AI to generate code for beginner issues is strictly discouraged
• Using AI as the main source of research is strictly discouraged, refer to language and library documentation, protobuf definitions and other SDKs.

⏱️ Timeline & Workflow

• Typical time: ~1 Week / ~8 hours.
  🧩 Difficulty: Manageable but requires investigation and testing
  🎓 Best for: Beginner contributors

• 🔴 Completing a beginner issue in 1–3 hours is a red flag.

Tip

Suggested: share your proposed implementation approach as a comment before writing code to get early feedback and avoid wasted effort.

🧪 Testing Requirements

Important

At the beginner level, testing will be necessary but a small component.
The methods you implement should be verified (happy path at least)

How you test depends on the type of change.

Source code changes (e.g. in src/):

• Write basic unit tests
• Run tests locally: uv run pytest tests/unit/<specific_file>_test.py -v
• Integration tests will run automatically when you push

GitHub Actions / workflow changes (e.g. in .github/): Guide

• Test by merging to your fork's main and simulating the scenario

Example script changes (e.g. in examples/):

• Run the example script and confirm output matches expected behavior
• You will need a Hedera Portal account for testnet credentials

🛡️ Quality & Review Standards

Beginner PRs must be working and follow best practices.

1. Working: The implementation must solve the problem and meet the acceptance criteria.
2. SDK Best Practices: The solution should fit well with existing SDK patterns and abstractions.
3. Testing: basic unit and possibly integration tests to demonstrate the implementation works as expected.

⚠️ Breaking changes

• Watch for any changes that could impact existing users, even if they seem small.

🤖 AI notes

• AI has gaps or incorrect understanding of repo-specific patterns, logic, and protobuf schemes.

✅ PR Quality Checklist

Before opening your PR, confirm:

• I have spent the majority of my time researching the problem and building my understanding of the codebase and methods.
• My implementation works and is tested (if applicable).
• Every line of code is personally understood and explainable.
• My changes address what the issue asked for — nothing more, nothing less
• I have applied appropriate linting, code quality, and formatting tools used in this repo.

Before requesting a review, confirm:

• I did not modify files unrelated to this issue
• Clean git history — no rebase artifacts, merge commits, or unrelated files
• My commits are signed: git commit -S -s -m "chore: description" — Signing guide
• I added a CHANGELOG.md entry (if appropriate) under [Unreleased] — Changelog guide
• I have included appropriate tests and all CI checks pass.

📋 Workflow quick reference

You have done this before — here are the links if you need them:

Step	Guide
Claim this issue	Comment /assign below
Sync with main	Rebasing guide
Open a PR and link this issue	PR guide
Resolve merge conflicts	Merge conflicts guide

📚 Resources & Support

🆘 Stuck?

Tip

Comment on this issue: and describe what you have tried. A maintainer will respond.

Python SDK References:

• Windows Setup Guide — platform-specific installation steps
• Pylance guide — inline type checking during development
• Running examples
• Browse closed beginner PRs — see how others did it

References:

• Hedera Protobufs
• Community Calls
• Discord