chore: refactor naming references to Utility-Protocol and Utility-contracts

Author: elizabetheonoja-art

.github/workflows/ci.yml

@@ -1,4 +1,4 @@
-name: IoT-Billing-Service CI
+name: Utility-Protocol CI
 
 on:
   push:

AUDIT_READY_RUNBOOK.md

@@ -1,4 +1,4 @@
-# Audit-Ready Runbook — IoT-Billing-Service Contracts
+# Audit-Ready Runbook — Utility-Protocol Contracts
 
 **Contract ID (Testnet):** `CB7PSJZALNWNX7NLOAM6LOEL4OJZMFPQZJMIYO522ZSACYWXTZIDEDSS`  
 **Network:** Stellar Testnet — replace `--network testnet` with `--network mainnet` for production  
@@ -36,7 +36,7 @@
 
 ## 1. Executive Summary
 
-The IoT-Billing-Service Contracts platform provides a decentralized utility streaming protocol with comprehensive security measures including:
+The Utility-Protocol Contracts platform provides a decentralized utility streaming protocol with comprehensive security measures including:
 
 - **Tamper-proof nonce synchronization** for IoT device liveness verification
 - **Time-of-Use tariff pricing** with 24-hour schedules
@@ -535,9 +535,9 @@ Level 4 (1 hour): Community, Public Relations
 ```
 
 **Emergency Channels:**
-- Signal Group: `iot-billing-emergency`
+- Signal Group: `utility-protocol-emergency`
 - Telegram: `@iotbilling_emergency`
-- PagerDuty: `iot-billing-security`
+- PagerDuty: `utility-protocol-security`
 
 ---
 
@@ -582,7 +582,7 @@ Level 4 (1 hour): Community, Public Relations
 
 ## Conclusion
 
-This runbook provides comprehensive procedures for managing the IoT-Billing-Service Contracts platform with the new security improvements implemented in Issues #260-263. The platform is now audit-ready with enterprise-grade documentation, comprehensive security measures, and operational procedures that meet the highest standards for decentralized utility management.
+This runbook provides comprehensive procedures for managing the Utility-Protocol Contracts platform with the new security improvements implemented in Issues #260-263. The platform is now audit-ready with enterprise-grade documentation, comprehensive security measures, and operational procedures that meet the highest standards for decentralized utility management.
 
 **Next Steps:**
 1. Schedule external security audit with Zealynx

CONTRIBUTING.md

@@ -1,10 +1,10 @@
-# Contributing to Billing-contracts
+# Contributing to Utility-contracts
 
-Welcome to the Billing-contracts project! This guide will help you contribute effectively, whether you're working on hardware (C++/Arduino) or smart contracts (Soroban/Rust).
+Welcome to the Utility-contracts project! This guide will help you contribute effectively, whether you're working on hardware (C++/Arduino) or smart contracts (Soroban/Rust).
 
 ## Project Overview
 
-Billing-contracts is a utility billing system built on Stellar that allows:
+Utility-contracts is a utility billing system built on Stellar that allows:
 - Individual meter billing and management
 - Group billing for property managers
 - Real-time balance monitoring
@@ -156,8 +156,8 @@ make test
 
 ### 1. Fork and Clone
 ```bash
-git clone https://github.com/your-username/Billing-contracts.git
-cd Billing-contracts
+git clone https://github.com/your-username/Utility-contracts.git
+cd Utility-contracts
 ```
 
 ### 2. Create Feature Branch
@@ -263,7 +263,7 @@ Include:
 
 ## 📞 Get Help
 
-- **Discord**: [IoT-Billing-Service Community](https://discord.gg/iotbilling)
+- **Discord**: [Utility-Protocol Community](https://discord.gg/iotbilling)
 - **GitHub Issues**: For bug reports and feature requests
 - **Documentation**: Check the `/docs` directory
 - **Examples**: See `/examples` directory
@@ -274,4 +274,4 @@ By contributing, you agree that your contributions will be licensed under the sa
 
 ---
 
-Thank you for contributing to Billing-contracts! 🎉
+Thank you for contributing to Utility-contracts! 🎉

EMERGENCY_RUNBOOK.md

@@ -1,4 +1,4 @@
-# Emergency Runbook — IoT-Billing-Service Contracts
+# Emergency Runbook — Utility-Protocol Contracts
 
 **Contract ID (Testnet):** `CB7PSJZALNWNX7NLOAM6LOEL4OJZMFPQZJMIYO522ZSACYWXTZIDEDSS`  
 **Network:** Stellar Testnet — replace `--network testnet` with `--network mainnet` for production  

README.md

@@ -1,4 +1,4 @@
-# IoT-Billing-Service Contracts
+# Utility-Protocol Contracts
 
 Soroban smart contracts for a decentralized utility metering and streaming protocol on Stellar. Supports prepaid/postpaid billing, continuous streaming, variable-rate tariffs, gas buffers, ZK-SNARK sensor privacy, multi-sig governance, and emergency response.
 
@@ -19,7 +19,7 @@ Soroban smart contracts for a decentralized utility metering and streaming proto
 ## Project Structure
 
 ```
-Billing-contracts/
+Utility-contracts/
 ├── contracts/
 │   ├── Cargo.toml                  # Workspace root
 │   ├── utility_contracts/          # Main contract

SECURITY.md

@@ -3,7 +3,7 @@
 ## Reporting a Vulnerability
 
 Please report security vulnerabilities by opening a **private** GitHub Security Advisory at:
-`https://github.com/IoT-Billing-Service/Billing-contracts/security/advisories/new`
+`https://github.com/Utility-Protocol/Utility-contracts/security/advisories/new`
 
 Do **not** open a public issue for security-sensitive findings.
 

contracts/utility_contracts/src/ERRORS.md

@@ -1,4 +1,4 @@
-# IoT-Billing-Service Contract - Error Codes
+# Utility-Protocol Contract - Error Codes
 
 This document provides a mapping of on-chain error codes to user-friendly explanations and suggested actions. When a transaction fails, the frontend can use this guide to display a helpful message instead of a raw error.
 

contracts/utility_contracts/src/Multi_Sig.rs

@@ -80,7 +80,7 @@ pub fn validate_invariants(env: &Env, account: Address) {
 
 
 // --- Grant Stream Listener Contract ---
-// This contract listens for GoalReached events from IoT-Billing-Service and processes grant matches
+// This contract listens for GoalReached events from Utility-Protocol and processes grant matches
 
 #[contracttype]
 #[derive(Clone)]
@@ -128,8 +128,8 @@ pub enum GrantError {
     Unauthorized = 7,
 }
 
-#[contractclient(name = "IoTBillingServiceClient")]
-pub trait IoTBillingService {
+#[contractclient(name = "UtilityProtocolClient")]
+pub trait UtilityProtocol {
     fn get_conservation_goal(env: Env, goal_id: u64) -> super::ConservationGoal;
 }
 
@@ -161,7 +161,7 @@ impl GrantStreamListener {
         );
     }
 
-    /// Called by IoT-Billing-Service when a conservation goal is reached
+    /// Called by Utility-Protocol when a conservation goal is reached
     pub fn on_goal_reached(env: Env, goal_event: super::GoalReachedEvent) {
         let config: GrantConfig = env.storage()
             .instance()

contracts/utility_contracts/src/grant_stream_listener.rs

@@ -6,7 +6,7 @@ use soroban_sdk::{
 };
 
 // --- Grant Stream Listener Contract ---
-// This contract listens for GoalReached events from IoT-Billing-Service and processes grant matches
+// This contract listens for GoalReached events from Utility-Protocol and processes grant matches
 
 #[contracttype]
 #[derive(Clone)]
@@ -89,7 +89,7 @@ impl GrantStreamListener {
             .publish((symbol_short!("GrantInit"),), (admin, treasury));
     }
 
-    /// Called by IoT-Billing-Service when a conservation goal is reached
+    /// Called by Utility-Protocol when a conservation goal is reached
     pub fn on_goal_reached(
         env: Env,
         billing_contract: Address,

docs/BLOCK_EXPLORER_GUIDE.md

@@ -4,7 +4,7 @@ This guide shows users how to verify their utility consumption data ("Usage Drip
 
 ## Overview
 
-The IoT-Billing-Service smart contract records all usage data on the Stellar blockchain, providing:
+The Utility-Protocol smart contract records all usage data on the Stellar blockchain, providing:
 - ✅ **Transparency** - All consumption data is publicly verifiable
 - ✅ **Immutability** - Data cannot be altered once recorded
 - ✅ **Audit Trail** - Complete history of all transactions
@@ -120,13 +120,13 @@ You'll see all transactions involving your account:
 
 #### Step 3: Filter by Contract
 
-Filter transactions to show only those interacting with the IoT-Billing-Service contract.
+Filter transactions to show only those interacting with the Utility-Protocol contract.
 
 ---
 
 ## Understanding Contract Events
 
-The IoT-Billing-Service contract emits several event types that you can track:
+The Utility-Protocol contract emits several event types that you can track:
 
 ### 1. UsageReported Event
 
@@ -291,7 +291,7 @@ Peak hour example:
 
 **Steps:**
 1. Search your provider address
-2. Filter transactions to IoT-Billing-Service contract
+2. Filter transactions to Utility-Protocol contract
 3. Look for `withdraw_earnings` operations
 4. Check amounts and timestamps
 5. Verify against your records
@@ -528,7 +528,7 @@ Example tools:
 - [Stellar Expert Documentation](https://stellar.expert/help)
 - [Stellar Developer Documentation](https://developers.stellar.org/)
 - [Soroban Documentation](https://soroban.stellar.org/)
-- [IoT-Billing-Service Contract Documentation](../README.md)
+- [Utility-Protocol Contract Documentation](../README.md)
 
 ---