From c0345f8b8f617e5cf98bccb7500f2389511b1865 Mon Sep 17 00:00:00 2001
From: Martin Habovstiak <martin.habovstiak@gmail.com>
Date: Wed, 2 Jul 2025 14:48:00 +0200
Subject: [PATCH] Use relative import paths rather than absolute

When doing large refactorings such as moving entire modules around
referring to items defined in a parent module by mentioning `crate` is
umbersome since the paths change and make the move confusing. It also
obscures the fact that some concepts are related.

This changes a few paths to relative so that the refactoring in the
future will be easier.
---
 bitcoin/src/network/params.rs | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/bitcoin/src/network/params.rs b/bitcoin/src/network/params.rs
index e9e4adab1..fc745e455 100644
--- a/bitcoin/src/network/params.rs
+++ b/bitcoin/src/network/params.rs
@@ -62,11 +62,10 @@
 
 use units::{BlockHeight, BlockHeightInterval};
 
-use crate::network::Network;
+use super::{Network, TestnetVersion};
 #[cfg(doc)]
 use crate::pow::CompactTarget;
 use crate::pow::Target;
-use crate::TestnetVersion;
 
 /// Parameters that influence chain consensus.
 #[non_exhaustive]