Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Problem: Attestation fees not based on result size

Open
#1,200 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go

Research direction

Start by locating request_attestation() and the existing ERC-20 transfer or fee-handling path. Trace how the result byte size and max_fee parameter are available, then verify that the configurable base fee and per-byte rate produce the stated formula, abort above max_fee, and retain revenue in the network. Document the final formula.

Written by the indexing model from the issue text.

Description

Attestation requests need dynamic fee calculation based on result byte size to ensure fair pricing for the network.

Acceptance Criteria:

  • Fee calculation function implemented
  • Formula: base_fee + (result_bytes * per_byte_rate)
  • Configurable parameters: base_fee, per_byte_rate
  • Fee charged via ERC-20 transfer in request_attestation()
  • Transaction aborts if calculated fee > max_fee parameter
  • Fee revenue stays with network (no distribution in MVP)
  • Documentation of fee formula
Dominant language
Go
Stars
7
Forks
3
Avg merge
3h 2m
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from trufnetwork/node

All issues in trufnetwork/node

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.