Program Charter
This Program Charter defines the operational framework for the MPC Node Infrastructure Financing Program as approved in HSP-007.
For full context, rationale, scope, and parameter definitions, please refer to the original proposal. This Charter focuses on how the program is executed in practice, ensuring transparency, predictability, and reproducibility.
1. Program Design
The MPC Node Signer Program provides ongoing incentives for eligible node operators contributing to MPC infrastructure.
Eligibility & Participation
- Participation is limited to nodes meeting the requirements defined in HSP-007.
- The program enforces a maximum node cap of 21 nodes.
- An Eligible Node Registry will be maintained and published monthly in this thread.
Compensation Model
- Node operators are compensated on a monthly basis (in arrears).
- Compensation is determined using the methodology defined in HSP-007, including:
- Fixed floor and cap mechanics
- A non-discretionary calculation model
- All calculations are deterministic and reproducible by third parties.
Price Reference Methodology
Token price inputs follow the exact methodology defined in HSP-007:
-
Step 1:
- Determine the 180-day trailing arithmetic average of NEAR/USD
- Source: CoinMarketCap daily close at 0:00 UTC
- Window: 180 calendar days ending on the last day of the service month
-
Step 2: Calculate the NEAR payment
- If 180d_avg ≤ $3.00 → payment = 4,600 NEAR
- If 180d_avg > $3.00 → payment = $13,800 / 180d_avg
-
Step 3: Apply SLA adjustment
- Monthly Uptime ≥ 99.0% → 100% of payment
- 95.0% ≤ Monthly Uptime < 99.0% → 50% of payment
- Monthly Uptime < 95.0% → 0% (full forfeiture)
-
Monthly uptime will be tracked and reported on a monthly basis in this thread.
-
This methodology is fixed and cannot be altered without governance approval.
Example scenarios (per node, per month):
180d Avg Price | NEAR Payment | USD Equivalent
$1.50 (floor) | 4,600 NEAR | $6,900
$2.25 | 4,600 NEAR | $10,350
$3.00 | 4,600 NEAR | $13,800
$4.50 | 3,067 NEAR | $13,800
$6.00 | 2,300 NEAR | $13,800
SLA Requirements
- Node performance is evaluated against SLA criteria defined in the proposal, and the SLA agreement signed by House of Stake Foundation and node operators.
- Payout eligibility is strictly tied to SLA compliance.
- Failure to meet SLA requirements results in reduced or forfeited compensation, per defined rules.
2. Operations & Process
Each cycle corresponds to a calendar month. Reporting and payments are executed within a defined period after month-end (as operationally feasible).
- Monitoring
- Node performance is continuously monitored by NEAR One.
- SLA Evaluation
- At the end of each period, node performance is evaluated against SLA thresholds.
- Report Publication (5th)
- Performance report (current cycle, e.g. April 1–30 for report on May 5th)
- Payout report (finalized cycle, e.g. March 1–31 for report on May 5th)
- Challenge Period (5th–12th)
- Operators review and raise disputes for current cycle if needed.
- HoS will start the payout process once the challenge window has closed, and will compensate only for services that remain unchallenged or have had their challenges resolved.
- Finalization & Compliance (12th–18th)
- Disputes resolved
- AML checks completed
- Payment Execution (13th–20th)
- Payments are executed based on finalized results.
3. Transparency & Reporting
Transparency is a core principle of the program.
Monthly Public Report
Each cycle, the following will be published:
a) Performance Report (current cycle, e.g. April 1–30 for report on May 5th):
- Eligible Node Registry
- Per-node SLA performance results
- Detailed payment calculations, cap triggered or not
- Price inputs used in calculations
b) Payout Report (finalized cycle, e.g. March 1–31 for report on May 5th)
- Eligible Node Registry
- Challenges and resolutions
- Final payout amounts
Reproducibility
- All data and formulas used are publicly available.
- Any third party should be able to independently verify:
- SLA outcomes
- Payment calculations
Data Integrity
- Reports are considered the canonical record of program execution.
- Any corrections or amendments will be clearly disclosed.
4. Dispute & Challenge Process
A structured process is in place to handle disputes regarding SLA evaluation or payment calculations.
Submission
- Node operators may submit a dispute via the this forum.
- Disputes must:
- Specify the precise dates, times, and nature of the alleged outages or calculation discrepancies
- Be published at this thread replying to the respective monthly report
Scope of Disputes
Valid disputes may relate to:
- Incorrect SLA evaluation
- Incorrect data inputs
- Calculation errors
Disputes cannot challenge:
- The predefined methodology
- Fixed parameters established in HSP-007
Resolution
- Disputes are reviewed by program administrators in coordination with relevant stakeholders.
- Resolution follows the process defined and agreed between node operators and the House of Stake Foundation.
Timeline
- Disputes must be raised within a 7-days window after report publication.
- Late submissions may not be considered.
Final Notes
This Program Charter is designed to:
- Ensure predictable and rule-based execution
- Eliminate discretionary decision-making
- Enable full transparency and auditability
All program parameters, constraints, and governance authority are defined in HSP-007, which remains the single source of truth for the program.
