Threshold
Thank you for your questions and concerns regarding the current proposal. I’d like to address these points clearly to help the community understand and make an informed decision:
The pricing shown on Subscan Pro Pricing pertains specifically to our API services, not to the operational and maintenance fees for the explorer service. The explorer's operational costs follow a standardized pricing model that we have consistently applied in on-chain proposals for networks such as Bifrost, Phala, and Interlay. You can verify this standard by reviewing these networks’ proposals.
Due to daily fluctuations in costs, we use the median value of each quarter as the billing basis, specifically May 15 and August 15. This method provides a balanced approach as costs gradually increase over time. Before August 15, the expenses were lower, and after that, they were higher, making August 15 a reasonable estimate close to the average.
799 + 5.3 * 24.42 = 928, and for 3 months, it is 928 * 3 = 2785
Although we do not currently have a public-facing dashboard for tracking usage, developing one is in our plans. However, this does not compromise the accuracy of billing, as even dashboards can be subject to manipulation. Trust remains a key factor in maintaining transparency.
Our pricing model reflects Subscan’s operational costs and the high-quality service we deliver. At present, we only offer this comprehensive service plan. However, we may explore options for a more streamlined version in the future. Notably, we submitted the Q1 invoice to the Basilisk community and received approval, establishing a precedent for trust and a post-payment service arrangement.
We understand if Basilisk needs to reassess its strategic direction due to user volume or budget constraints. If a more cost-effective solution suits Basilisk better at this time, please let us know as soon as possible so we can promptly discontinue services and avoid incurring further costs.
Please note that the current fees represent historical costs that have already been incurred, regardless of the decision to continue using Subscan’s services. These invoices remain valid, as Subscan has already covered considerable expenses upfront. If payment is not received by November 15, we will unfortunately need to suspend services to avoid further costs.
We appreciate the community's mention of the "Origin able to spend up to 50M BSX at once" limit. If necessary, we are prepared to resubmit the proposal to align with this condition.
We value the feedback and concerns of the community. Subscan remains committed to providing transparent, reliable, and high-quality service. If there are any further questions or clarifications needed, please don’t hesitate to reach out.
Thank you for your understanding and trust. We hope this clarifies the key points and helps in making an informed decision. 🙏🏻
Edited
I see several problems with the current proposal, hence my vote is NO until they are solved.
Spender
track, which when clicked reads: "Origin able to spend up to 50M BSX from the treasury at once.", but this proposal is asking for 139.51M BSX, so how is this proposal correct?Thank you 🙏🏻
PS, for the community: I wonder if there are alternatives to Subscan, and/or if other parachains have better deals? What do you think? Is all of this necessary right now, considering the low user adoption? I don't think so.
Edited