onflow / onflow/flow

Move Storage Fees into Transaction Fees

Open
#791 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Feedback
Dominant language
Go
Stars
361
Forks
159
PR merge metrics
No merged PRs in 30d

Description

Issue To Be Solved

Currently storage fees are too complicated for dapps to handle.

There is ongoing discussion about new transaction fees ( gas usage etc ). Don't you think it would be feasible to get rid of Storage Fees in this opportunity ? I am sure there can be a mathematical sweet spot there.

Some options:

  • Increased fee for writing to storage depending on the storage usage.
  • Some fixed fee for storage read / write ( Depending on the bytes read/write )

Still minimum account balance for creation can stay ( or adjusted ) , but it without storage fees, user experience would be much better in my opinion.

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.

Research direction

The issue names no files, tests, or entry points. Start by locating the transaction-fee and storage-fee areas, then review the existing fee discussion; done would require an agreed fee model and an implementation scope before coding can begin.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
blockchain
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.