Description
Revenue-share distributions have different tax treatments (ordinary income, capital gains, return of capital). Add a TaxBucket field on report_revenue so downstream indexers and tax engines can categorize each disbursement without out-of-band annotation.
Requirements and context
- Must be secure, tested, and documented
- Should be efficient and easy to review
- Relevant code:
Revora-Contracts/src/lib.rs
- Bucket must be encoded into the indexed event topic for filterable subscription
Suggested execution
- Fork the repo and create a branch
git checkout -b feat/tax-bucket-tagging
- Implement changes
- Add
enum TaxBucket { Ordinary, Capital, ReturnOfCapital, Custom(Symbol) }
- Persist bucket in
PeriodRevenue and surface it on claim events
- Document mapping to common jurisdictions in README
- Validate security and correctness assumptions
Test and commit
- Run tests
- Cover edge cases
- Override revenue must preserve original bucket unless explicitly overridden
- Include test output and security notes
Example commit message
feat: tag report_revenue with TaxBucket for downstream tax engines
Guidelines
- Minimum 95 percent test coverage
- Clear documentation
- Timeframe: 96 hours
Description
Revenue-share distributions have different tax treatments (ordinary income, capital gains, return of capital). Add a
TaxBucketfield onreport_revenueso downstream indexers and tax engines can categorize each disbursement without out-of-band annotation.Requirements and context
Revora-Contracts/src/lib.rsSuggested execution
git checkout -b feat/tax-bucket-taggingenum TaxBucket { Ordinary, Capital, ReturnOfCapital, Custom(Symbol) }PeriodRevenueand surface it onclaimeventsTest and commit
cargo test --allExample commit message
feat: tag report_revenue with TaxBucket for downstream tax enginesGuidelines