use SystemTime instead of chrono with clock to test validity

Author: johncantrell97

Cargo.toml

@@ -13,6 +13,6 @@ lightning-invoice = "0.25.0"
 
 bitcoin = "0.29.0"
 
-chrono = { version = "0.4.31", default-features = false, features = ["std", "serde", "clock"] }
+chrono = { version = "0.4.31", default-features = false, features = ["std", "serde"] }
 serde = { version = "1.0", default-features = false, features = ["derive", "alloc"] }
 serde_json = "1.0"

src/jit_channel/utils.rs

@@ -2,14 +2,21 @@ use bitcoin::hashes::hmac::{Hmac, HmacEngine};
 use bitcoin::hashes::sha256::Hash as Sha256;
 use bitcoin::hashes::{Hash, HashEngine};
 
+use std::time::{SystemTime, UNIX_EPOCH};
+
 use crate::jit_channel::msgs::OpeningFeeParams;
 use crate::utils;
 
 /// Determines if the given parameters are valid given the secret used to generate the promise.
 pub fn is_valid_opening_fee_params(
 	fee_params: &OpeningFeeParams, promise_secret: &[u8; 32],
 ) -> bool {
-	if chrono::Utc::now() > fee_params.valid_until {
+	let seconds_since_epoch = SystemTime::now()
+		.duration_since(UNIX_EPOCH)
+		.expect("system clock to be ahead of the unix epoch")
+		.as_secs();
+	let valid_until_seconds_since_epoch = fee_params.valid_until.timestamp().unsigned_abs();
+	if seconds_since_epoch > valid_until_seconds_since_epoch {
 		return false;
 	}