lightninglabs / lightninglabs/taproot-assets
[feature]: Change in meta-data size
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
I would love to have the feature to specify meta-data size limits in the litd.conf file individually.
I assume it's not an technical issue rather a decision the team made to not bloat litd nodes unresponsibly.
Maybe universes can decide on their metafield sizes individually at some point.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how litd.conf is parsed and where metadata-size limits are enforced; the issue names no files, tests, or entry points. Clarify whether limits should be configured individually or decided per universe, then establish the expected behavior and tests with the maintainers before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100