Legal Documentation
SERVICE LEVEL
AGREEMENT
This Service Level Agreement ("SLA") between Campione Infrastructure, a division of
MaxResults4U Business Solutions ("Provider"), and the subscribing client ("Client")
defines the standards of service delivery, uptime commitments, incident response
procedures, and remedies for service failures.
Section 01
Definitions
For the purposes of this Agreement, the following terms shall have the meanings set forth below:
- "Provider" means Campione Infrastructure, a division of MaxResults4U Business Solutions, headquartered in Land O Lakes, Florida, USA.
- "Client" means the individual, company, or entity that has entered into a service agreement with the Provider.
- "Service" means any infrastructure service provided by the Provider, including but not limited to: Stellar Horizon API access, validator node monitoring, node infrastructure setup, Chainlink oracle services, Lightning payment rails, and blockchain consulting.
- "Downtime" means any period during which the Service is unavailable or non-functional, excluding Scheduled Maintenance windows.
- "Monthly Uptime Percentage" means the total number of minutes in a calendar month minus the number of minutes of Downtime, divided by the total number of minutes in that calendar month.
- "Incident" means any unplanned interruption or degradation of Service quality.
- "Critical Incident" means complete service unavailability affecting Client operations.
- "Service Credit" means a credit applied to Client's account for future billing periods.
Section 02
Service Coverage
This SLA applies to the following services offered by Campione Infrastructure:
| Service |
Coverage |
Network |
Status |
| Stellar Horizon API |
Dedicated API endpoint access |
Stellar Mainnet |
Active |
| XRPL Validator |
Trusted validator participation |
XRP Ledger Mainnet |
Active |
| Stellar Validator |
SCP consensus participation |
Stellar Mainnet |
Active |
| Chainlink Oracle |
Data feed delivery |
Ethereum Mainnet |
Deploying |
| Bitcoin Lightning |
Payment routing node |
Bitcoin Mainnet |
Pending |
| Node Setup Service |
End-to-end node deployment |
Multi-chain |
Active |
| Validator Monitoring |
24/7 node health monitoring |
Multi-chain |
Active |
| Infrastructure Consulting |
Technical advisory services |
All networks |
Active |
Section 03
Uptime Commitment
Monthly Uptime Guarantee
99.9%
Maximum allowable downtime: 43.8 minutes per month · 8.7 hours per year
The Provider commits to maintaining a Monthly Uptime Percentage of 99.9% for all active Services. This commitment is measured on a calendar month basis and applies to all paid service tiers.
Uptime Measurement
Uptime is measured continuously using automated monitoring systems. The Provider monitors:
- Service endpoint availability (HTTP response codes)
- Node synchronization status
- Network connectivity
- API response times
- Validator participation rates
Uptime Tiers
| Monthly Uptime |
Classification |
Client Action |
| ≥ 99.9% |
SLA Met |
No action required |
| 99.0% – 99.9% |
Minor Breach |
Eligible for 10% service credit |
| 95.0% – 99.0% |
Major Breach |
Eligible for 25% service credit |
| < 95.0% |
Critical Breach |
Eligible for 50% partial refund |
Section 04
Incident Response
Critical Incident Response Time
4 Hours
From incident detection to active remediation for Priority 1 incidents
Incident Priority Levels
| Priority |
Description |
Response Time |
Resolution Target |
| P1 Critical |
Complete service unavailability |
4 hours |
8 hours |
| P2 High |
Significant degradation affecting operations |
8 hours |
24 hours |
| P3 Medium |
Partial degradation, workaround available |
24 hours |
72 hours |
| P4 Low |
Minor issues, no operational impact |
48 hours |
7 days |
Incident Response Procedure
- Detection — Automated monitoring detects service degradation
- Notification — Client notified via email within 30 minutes of detection
- Assessment — Provider assesses severity and assigns priority level
- Remediation — Active remediation begins within response time window
- Resolution — Service restored and Client notified of resolution
- Post-Incident Report — Written report delivered within 48 hours of resolution
Reporting an Incident
Clients may report incidents via:
- Email: maxresults4u@gmail.com — Subject: [INCIDENT] Service Name
- Response guaranteed within 4 hours for P1 Critical incidents
Section 05
Scheduled Maintenance
The Provider may perform scheduled maintenance that temporarily affects service availability. Scheduled maintenance is excluded from uptime calculations provided the following conditions are met:
- Client receives 48 hours advance notice via email
- Maintenance window does not exceed 4 hours per occurrence
- Scheduled maintenance occurs no more than twice per month
- Maintenance is performed during off-peak hours (2:00 AM – 6:00 AM EST)
Emergency Maintenance
Critical Security Updates
Emergency maintenance for critical security patches may be performed with 2-hour notice. These windows are capped at 2 hours and excluded from uptime calculations.
Section 06
SLA Breach Remedies
In the event of an SLA breach, Clients are entitled to the following remedies. Remedies are provided as Service Credits or Partial Refunds applied to the Client's account.
Service Credits
Service Credits are applied to the Client's next billing cycle and calculated as a percentage of the monthly service fee:
| Uptime Achieved |
Credit / Refund |
Type |
| 99.0% – 99.9% |
10% of monthly fee |
Service Credit |
| 95.0% – 99.0% |
25% of monthly fee |
Service Credit |
| < 95.0% |
50% of monthly fee |
Partial Refund |
How to Claim a Remedy
- Submit claim to maxresults4u@gmail.com within 30 days of the incident
- Include: Service name, incident dates, and description of impact
- Provider will verify claim within 5 business days
- Approved credits applied to next billing cycle
- Approved refunds processed within 10 business days
Maximum remedy in any calendar month shall not exceed 50% of the monthly service fee for that service.
Section 07
Exclusions
The following circumstances are excluded from uptime calculations and SLA breach remedies:
- Scheduled Maintenance — as defined in Section 5
- Force Majeure — natural disasters, war, government actions, pandemics
- Blockchain Network Issues — outages caused by the underlying blockchain network (e.g., XRP Ledger, Stellar network) outside Provider's control
- Third-Party Infrastructure — failures of DNS providers, internet service providers, or upstream data centers
- Client Actions — downtime caused by Client's misconfiguration or misuse
- DDoS Attacks — distributed denial of service attacks targeting Provider infrastructure
- Beta Services — services explicitly marked as beta or experimental
- Free Tier Services — services provided at no charge
Section 08
Security Standards
The Provider maintains the following security standards across all infrastructure:
Infrastructure Security
- Firewall Protection — UFW firewall with port-level access controls on all servers
- Intrusion Prevention — Fail2ban active on all servers, blocking brute force attacks
- SSH Security — Key-based authentication only, password login disabled
- Regular Updates — Security patches applied within 48 hours of release
- Access Control — Principle of least privilege applied to all system accounts
Validator Key Security
- All validator keys stored with hardware-level protection
- Keys backed up in encrypted offline storage
- Key rotation procedures documented and tested
Compliance
- ISO 20022 Aligned — All networks operated are ISO 20022 registered or compatible
- CLARITY Act Ready — Infrastructure designed for post-legislation compliance
- US Based Operations — All infrastructure operated from United States jurisdiction
Section 09
Data & Privacy
- The Provider does not store, sell, or share Client private keys or wallet credentials
- API usage logs are retained for 90 days for debugging and billing purposes
- Client contact information is used solely for service delivery and incident communication
- The Provider complies with applicable US data protection regulations
- Clients retain full ownership of all data transmitted through Provider infrastructure
Section 10
Reporting & Transparency
Monthly Reports
Clients on monitoring plans receive monthly reports including:
- Uptime percentage achieved
- Number of incidents and resolutions
- Maintenance windows performed
- Security events detected and mitigated
- Performance metrics and trends
Public Status
Infrastructure status is publicly verifiable at:
- XRPL: xrpscan.com/validator/n9LbTCkNpn2X7jGBX4UJCkdVwmXKGaHu1jbcJK6U1GPF2wtES1D8
- Stellar: stellar.expert/explorer/public/account/GDMAAY42V4XQUYPKRSSQRQHP4YZH6LXDGYSKXKP3OSH5F7MKFNWLVNVH
- TOML Files: campioneinfrastructure.com/.well-known/
Section 11
Termination
By Client
- Monthly services: Cancel with 30 days written notice
- Annual services: Cancel with 60 days written notice — no refund for remaining term
- One-time services: Non-cancellable once work has commenced
By Provider
- Provider may terminate with 30 days written notice for any reason
- Provider may terminate immediately for non-payment, abuse, or illegal activity
- Pro-rated refund provided for Provider-initiated terminations
Section 12
Contact & Escalation
| Contact Type |
Details |
Response Time |
| General Inquiries |
maxresults4u@gmail.com |
24 hours |
| Billing Issues |
maxresults4u@gmail.com — Subject: [BILLING] |
24 hours |
| P1 Critical Incident |
maxresults4u@gmail.com — Subject: [INCIDENT P1] |
4 hours |
| SLA Breach Claims |
maxresults4u@gmail.com — Subject: [SLA CLAIM] |
5 business days |
| Security Issues |
maxresults4u@gmail.com — Subject: [SECURITY] |
2 hours |
Governing Law
This Agreement shall be governed by and construed in accordance with the laws of the State of Florida, United States of America. Any disputes arising under this Agreement shall be resolved in the courts of Pasco County, Florida.
By subscribing to any service offered by Campione Infrastructure, the Client agrees to the terms of this Service Level Agreement. This SLA is effective as of March 30, 2026 and supersedes all previous agreements.