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

Ingress Proof Reward Fees #184

Open
6 tasks
DanMacDonald opened this issue Feb 4, 2025 · 0 comments
Open
6 tasks

Ingress Proof Reward Fees #184

DanMacDonald opened this issue Feb 4, 2025 · 0 comments

Comments

@DanMacDonald
Copy link
Collaborator

DanMacDonald commented Feb 4, 2025

Related to #181
Depends on #183

Current Milestone Tasks

  • Add a consensus config param for the number of ingress-proofs required to promote data (default 1)
  • Add a consensus config param for how many ingress-proofs must come from submit ledger miners (default 1)
  • Make sure Perm Data Price includes the minimum_storage_fee from Term Storage Pricing #183 per required-ingress proof
  • Add the ingress-proof fees to the endowment when the storage tx is posted to the submit ledger
  • When the transaction promotes, reward the miners that provided the ingress-proofs for promotion
  • Validate all of the above during pre-validation of blocks.

Term & Perm Storage Fees (requires permissions)

During the promotion process, Irys requires X number of ingress-proofs to be generated in order to promote a data-storage transaction from the Submit ledger to the Permanent Publish ledger. During single-node testnet this number is one but in multi-node we will want something closer to 10.

The promotion process is described in more detail here

Multi Ledger Tech (requires permissions)

In Irys’s multi-ledger system, each ledger index (slot) has 10 assigned miners responsible for provably storing the Ledger entry data in that slot. To promote a transaction, a certain number (m) of ingress proofs must come from the Submit Ledger miners assigned to store the data about to be promoted. Thus ensuring that m/n of the proofs are from miners actively committed to storing it (increasing the assumptions the protocol can make about the availability of the data). For multi-node testnet, the m value is set to 5.

@DanMacDonald DanMacDonald added this to the 1. Multi-Node Consensus milestone Feb 4, 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