Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Programmable Data Pricing #186

Open
DanMacDonald opened this issue Feb 5, 2025 · 0 comments
Open

Programmable Data Pricing #186

DanMacDonald opened this issue Feb 5, 2025 · 0 comments

Comments

@DanMacDonald
Copy link
Collaborator

Programmable Data Pricing (permission required)

Pricing Programmable Data

Base Fee

Beyond bandwidth costs, unpacking and deserializing chunks for use in IrysVM introduces computational overhead, requiring spam mitigation.

  • The base_fee during testnet for 1MB of Programmable Data is $0.01.
  • There is a minimum cost of $0.01 for Programmable Data transactions.

Congestion Pricing

The base_fee for Programmable Data can adjust by ±12.5% per block, similar to Ethereum gas fee adjustments.

  • Increase:

    • If more than 50% of the 7,500 available chunks are used, the base_fee increases linearly, up to +12.5% if all 7,500 chunks are used.
  • Decrease:

    • If no chunks are used, the base_fee decreases linearly, up to -12.5% when the block contains zero Programmable Data chunks.
    • The base_fee has no ceiling but has a floor of $0.01.

Priority Fees

If the base_fee is rising due to congestion but there is still competition for Programmable Data capacity, users can include a priority fee (paying above the base_fee) to incentivize transaction inclusion in a block.

Economic Mechanism

  • The base_fee for Programmable Data transactions is deposited into the treasury when included in a block. This creates deflationary pressure on the native token, increasing its purchasing power.
  • Priority fees (paid above the gas_fee for compute and base_fee for Programmable Data) are paid directly to the block producer.
@DanMacDonald DanMacDonald added this to the 1. Multi-Node Consensus milestone Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant