Skip to content

RFC-014: IBP Bandwidth Cost Reduction Measure#14

Open
kukabi wants to merge 1 commit intoibp-network:mainfrom
helikon-labs:helikon-rfc-014-bandwidth-cost-reduction
Open

RFC-014: IBP Bandwidth Cost Reduction Measure#14
kukabi wants to merge 1 commit intoibp-network:mainfrom
helikon-labs:helikon-rfc-014-bandwidth-cost-reduction

Conversation

@kukabi
Copy link
Contributor

@kukabi kukabi commented Nov 23, 2025

Summary

This RFC is a follow-up to RFC-013 regarding hardware pricing reductions, and it proposes lowering bandwidth costs for all members as well, in order to guarantee a 6-month runway for IBP with the current balance of 571K DOT and a conservative DOT rate of $2.

View the full RFC attached.


Vote

On the GitHub RFC PR:

  • 👍 Thumbs up = Aye (approve new pricing effective December 2025)
  • 👎 Thumbs down = Nay (reject proposal)

No reaction = abstain.

@kukabi kukabi changed the title RFC-014 IBP Bandwidth Cost Reduction Measure RFC-014: IBP Bandwidth Cost Reduction Measure Nov 23, 2025
@kukabi kukabi force-pushed the helikon-rfc-014-bandwidth-cost-reduction branch from c271b86 to 76fa708 Compare November 23, 2025 19:47
@miloskriz
Copy link

Hi @kukabi many thanks for putting this proposal together!

Would you consider adding an explicit note that after achieving the target of

(...) lowering bandwidth costs for all members as well, in order to guarantee a 6-month runway for IBP with DOT at $2 USD (...)

we will review and align the costs to the market situation at the time?

Otherwise, the reader may interpret that these discounts are permanent.

Many thanks!

Milos

@kukabi kukabi force-pushed the helikon-rfc-014-bandwidth-cost-reduction branch from 76fa708 to a819f2e Compare November 29, 2025 12:57
@kukabi kukabi force-pushed the helikon-rfc-014-bandwidth-cost-reduction branch from a819f2e to 8b7853e Compare November 29, 2025 12:59
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

Successfully merging this pull request may close these issues.

2 participants