Support paying fees in other assets

Open
#1,302 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
blockchain

Research direction

Start by tracing where policyAsset is read and how fee policy, mempool acceptance, and fee estimation use it. Clarify the map of accepted assets, the multiplier update rules, and how fee estimation should respond to price changes; done means fees can be paid in multiple assets without affecting consensus.

Written by the indexing model from the issue text.

Description

Currently fees are expected in the asset set in policyAsset. This is a single asset. It would be cool if this could be extended to a map of multiple assets and a multiplier back to the default one. Fees have no effect on consensus, so this is just a policy/mempool change. Fee estimation would be a bit more complicated, but I think even by only updating the multipliers sporadically, the fee estimation algo might actually allow for the funcs to slowly change the multiplier if the price changes.

Dominant language
C++
Stars
1.2k
Forks
418
Avg merge
1d 23h
Merged PRs (30d)
15

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 ElementsProject/elements

All issues in ElementsProject/elements

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.