TRN-808 Sylo Data Pallet #917

JCSanPedro · 2025-01-08T00:02:56Z

Description

The PR implements and adds the Sylo Data Verification Pallet to the runtime.

Protocol RFC - https://www.notion.so/futureverse/RFC-Sylo-Data-Verification-Protocol-14a0cb4dab3d808389eddaab37a2c767

The pallet allows users to register and manage resolvers, and also create and manage validation records.

Resolvers

A resolver is intended to be an external service capable of storing and providing off-chain data. The pallet allows a user to register a resolver, which would include an identifier and a list of service endpoints. A resolver is identified by a ResolverId, which loosely follows the DID Specification.

The ResolverId is comprised of two components: a method and identifier. The method describes what kind of resolver it is. All resolvers registered on chain are considered "sylo" resolvers, and will all use the same reserved string for their resolver method.

The account which registers the resolver is considered the controller of the register, and is capable of modifying or removing the resolver later.

Validation Records

The pallet allows a user to create a validation record through the create_validation_record extrinsic. A validation record references an externally stored piece of data, and is intended to be used to validate the integrity and authenticity of offchain data.

A validation record will have the following attributes:

data_id - A string representing the id. Validation records are stored in a double map, using the data_id as well as the author's account id.
author - The account which created the record. Will have the ability to modify and or delete the record in the future.
resolvers - A list of ResolverIds which reference how to fetch the data. All resolvers using the reserved sylo method must be registered onchain.
data_type - A string acting as a hint to clients as to what type of data it is.
tags - A list of strings acting as additional metadata information
entries A list of validation record entry. Each entry represents a distinct version of the data. It includes a checksum for integrity, and also a block number for when the entry was created.

Notes

Payment - All extrinsics related to managing validation records and resolvers are paid using Sylo tokens. This is achieved by modifying the OnChargeTransaction implementation for the FeeProxy, to detect sylo related extrinsics, and force the swap.

Release Notes

Key Changes

Adds the Sylo Data Verification Pallet to the runtime

Type of Change

Runtime Changes

Extrinsic Changes

Added

Sylo: register_resolver
Sylo: update_resolver
Sylo: unregister_resolver
Sylo: create_validation_record
Sylo: add_validation_record_entry
Sylo: update_validation_record
Sylo: delete_validation_record

zees-dev · 2025-01-08T01:21:40Z

runtime/src/lib.rs

+	pub const MaxResolvers: u32 = 10;
+	pub const MaxTags: u32 = 10;
+	pub const MaxEntries: u32 = 100;
+	pub const MaxServiceEndpoints: u32 = 10;
+	pub const SyloStringLimit: u32 = 500;


could reduce space for these vars:

Suggested change

pub const MaxResolvers: u32 = 10;

pub const MaxTags: u32 = 10;

pub const MaxEntries: u32 = 100;

pub const MaxServiceEndpoints: u32 = 10;

pub const SyloStringLimit: u32 = 500;

pub const MaxResolvers: u8 = 10;

pub const MaxTags: u8 = 10;

pub const MaxEntries: u8 = 100;

pub const MaxServiceEndpoints: u8 = 10;

pub const SyloStringLimit: u16 = 500;

zees-dev · 2025-01-08T01:23:50Z

runtime/src/weights/pallet_sylo.rs

weights need to be generated via CI - the runner would commit the updated weights

zees-dev · 2025-01-08T01:26:38Z

pallet/common/src/test_utils.rs

@@ -723,3 +723,26 @@ macro_rules! impl_pallet_scheduler_config {
 		}
 	};
 }
+
+#[macro_export]
+macro_rules! impl_pallet_sylo_config {


nice; thanks for this

zees-dev · 2025-01-08T01:28:47Z

pallet/fee-proxy/Cargo.toml

@@ -23,6 +23,7 @@ pallet-evm = { workspace = true }
 pallet-assets-ext = { workspace = true }
 pallet-dex = { workspace = true }
 pallet-futurepass = { workspace = true }
+pallet-sylo = { workspace = true }


may need an entry in the std = [ feature below.

zees-dev · 2025-01-08T03:19:58Z

pallet/fee-proxy/src/impls.rs

will wait for validated E2E tests to approve changes here

zees-dev · 2025-01-08T03:52:38Z

pallet/sylo/src/types.rs

I dont think we need explicit/restrictive trait-bounds for all the types.
Can take a look at the pub struct SaleInformation<AccountId, BlockNumber> { in pallet/crowdsale/src/types.rs file to see struct declarations which just consume a generic.

I tried something like

pub struct ResolverId<Str> { pub method: Str, pub identifier: Str, } pub trait ToDid { fn to_did(&self) -> Vec<u8>; } impl<T: Get<u32>> ToDid for ResolverId<BoundedVec<u8, T>> { .. }

but didn't feel like it cleaned up the code, as in the lib implementation, I then had to reference the full type like this ResolverId<BoundedVec<u8, T::StringLimit>> everywhere

zees-dev · 2025-01-08T03:54:40Z

pallet/sylo/src/lib.rs

+		#[pallet::weight({
+			T::WeightInfo::set_payment_asset()
+		})]
+		pub fn set_payment_asset(origin: OriginFor<T>, payment_asset: AssetId) -> DispatchResult {


event needs to be emitted for all state changes.

zees-dev · 2025-01-08T03:54:56Z

pallet/sylo/src/lib.rs

+		#[pallet::weight({
+			T::WeightInfo::set_sylo_resolver_method()
+		})]
+		pub fn set_sylo_resolver_method(


same here (emit event)

zees-dev · 2025-01-08T03:55:37Z

pallet/sylo/src/lib.rs

+			T::WeightInfo::set_payment_asset()
+		})]
+		pub fn set_payment_asset(origin: OriginFor<T>, payment_asset: AssetId) -> DispatchResult {
+			ensure_root(origin)?;


rather than using root; use the ApproveOrigin account (passed in via runtime)

zees-dev · 2025-01-08T03:55:53Z

pallet/sylo/src/lib.rs

+			origin: OriginFor<T>,
+			resolver_method: BoundedVec<u8, T::StringLimit>,
+		) -> DispatchResult {
+			ensure_root(origin)?;


same here (use approved origin)

zees-dev · 2025-01-08T04:02:06Z

pallet/sylo/src/lib.rs

+			let mut resolver =
+				<Resolvers<T>>::get(identifier.clone()).ok_or(Error::<T>::ResolverNotRegistered)?;
+
+			ensure!(who == resolver.controller, Error::<T>::NotController);
+
+			resolver.service_endpoints = service_endpoints.clone();
+
+			<Resolvers<T>>::insert(identifier.clone(), resolver);
+
+			Self::deposit_event(Event::ResolverUpdated {
+				id: identifier.to_vec(),
+				controller: who,
+				service_endpoints,
+			});
+
+			Ok(())


nit: instead of getting and inserting:

Suggested change

let mut resolver =

<Resolvers<T>>::get(identifier.clone()).ok_or(Error::<T>::ResolverNotRegistered)?;

ensure!(who == resolver.controller, Error::<T>::NotController);

resolver.service_endpoints = service_endpoints.clone();

<Resolvers<T>>::insert(identifier.clone(), resolver);

Self::deposit_event(Event::ResolverUpdated {

id: identifier.to_vec(),

controller: who,

service_endpoints,

});

Ok(())

<Resolvers<T>>::try_mutate(&identifier, |maybe_resolver| {

let resolver = maybe_resolver.as_mut().ok_or(Error::<T>::ResolverNotRegistered)?;

ensure!(who == resolver.controller, Error::<T>::NotController);

resolver.service_endpoints = service_endpoints.clone();

Self::deposit_event(Event::ResolverUpdated {

id: identifier.into_vec(),

controller: who,

service_endpoints,

});

Ok(())

})

zees-dev · 2025-01-08T05:39:02Z

pallet/sylo/src/lib.rs

+			let resolver =
+				<Resolvers<T>>::get(identifier.clone()).ok_or(Error::<T>::ResolverNotRegistered)?;
+
+			ensure!(who == resolver.controller, Error::<T>::NotController);
+
+			<Resolvers<T>>::remove(identifier.clone());


nit: unnecessary clone (memory allocations) can be removed i think

Suggested change

let resolver =

<Resolvers<T>>::get(identifier.clone()).ok_or(Error::<T>::ResolverNotRegistered)?;

ensure!(who == resolver.controller, Error::<T>::NotController);

<Resolvers<T>>::remove(identifier.clone());

let resolver = <Resolvers<T>>::get(&identifier).ok_or(Error::<T>::ResolverNotRegistered)?;

ensure!(who == resolver.controller, Error::<T>::NotController);

<Resolvers<T>>::remove(&identifier);

zees-dev · 2025-01-08T05:40:55Z

pallet/sylo/src/lib.rs

+			let who = ensure_signed(origin)?;
+
+			ensure!(
+				<ValidationRecords<T>>::get(who.clone(), data_id.clone()).is_none(),


Suggested change

<ValidationRecords<T>>::get(who.clone(), data_id.clone()).is_none(),

<ValidationRecords<T>>::get(&who, &data_id).is_none(),

zees-dev · 2025-01-08T05:41:52Z

pallet/sylo/src/lib.rs

+		pub fn validate_sylo_resolvers(
+			resolvers: BoundedVec<ResolverId<T::StringLimit>, T::MaxResolvers>,
+		) -> DispatchResult {
+			let reserved_method = <SyloResolverMethod<T>>::get();
+
+			// Ensure any sylo data resolvers are already registered
+			for resolver in resolvers {
+				if resolver.method == reserved_method {
+					ensure!(
+						<Resolvers<T>>::get(resolver.identifier).is_some(),
+						Error::<T>::ResolverNotRegistered
+					);
+				}
+			}
+
+			Ok(())
+		}


nit:

Suggested change

pub fn validate_sylo_resolvers(

resolvers: BoundedVec<ResolverId<T::StringLimit>, T::MaxResolvers>,

) -> DispatchResult {

let reserved_method = <SyloResolverMethod<T>>::get();

// Ensure any sylo data resolvers are already registered

for resolver in resolvers {

if resolver.method == reserved_method {

ensure!(

<Resolvers<T>>::get(resolver.identifier).is_some(),

Error::<T>::ResolverNotRegistered

);

}

}

Ok(())

}

pub fn validate_sylo_resolvers(

resolvers: &BoundedVec<ResolverId<T::StringLimit>, T::MaxResolvers>,

) -> DispatchResult {

let reserved_method = <SyloResolverMethod<T>>::get();

resolvers

.iter()

.filter(|resolver| resolver.method == reserved_method)

.try_for_each(|resolver| {

ensure!(

<Resolvers<T>>::contains_key(&resolver.identifier),

Error::<T>::ResolverNotRegistered

);

Ok(())

})

}

zees-dev · 2025-01-08T05:42:41Z

pallet/sylo/src/lib.rs

+				Error::<T>::RecordAlreadyCreated
+			);
+
+			Self::validate_sylo_resolvers(resolvers.clone())?;


Suggested change

Self::validate_sylo_resolvers(resolvers.clone())?;

Self::validate_sylo_resolvers(&resolvers)?;

zees-dev · 2025-01-08T05:43:51Z

pallet/sylo/src/lib.rs

+				}]),
+			};
+
+			<ValidationRecords<T>>::insert(who.clone(), data_id.clone(), record);


Suggested change

<ValidationRecords<T>>::insert(who.clone(), data_id.clone(), record);

<ValidationRecords<T>>::insert(&who, &data_id, record);

zees-dev · 2025-01-08T05:44:14Z

pallet/sylo/src/lib.rs

+		) -> DispatchResult {
+			let who = ensure_signed(origin)?;
+
+			let mut record = <ValidationRecords<T>>::get(who.clone(), data_id.clone())


Suggested change

let mut record = <ValidationRecords<T>>::get(who.clone(), data_id.clone())

let mut record = <ValidationRecords<T>>::get(&who, &data_id)

zees-dev · 2025-01-08T05:45:15Z

pallet/sylo/src/lib.rs

+			let mut record = <ValidationRecords<T>>::get(who.clone(), data_id.clone())
+				.ok_or(Error::<T>::RecordNotCreated)?;
+
+			record.entries.force_push(ValidationEntry {
+				checksum: checksum.clone(),
+				block: <frame_system::Pallet<T>>::block_number(),
+			});
+
+			<ValidationRecords<T>>::insert(who.clone(), data_id.clone(), record);
+
+			Self::deposit_event(Event::ValidationEntryAdded {
+				author: who,
+				id: data_id.to_vec(),
+				checksum,
+			});
+
+			Ok(())


nit:

Suggested change

let mut record = <ValidationRecords<T>>::get(who.clone(), data_id.clone())

.ok_or(Error::<T>::RecordNotCreated)?;

record.entries.force_push(ValidationEntry {

checksum: checksum.clone(),

block: <frame_system::Pallet<T>>::block_number(),

});

<ValidationRecords<T>>::insert(who.clone(), data_id.clone(), record);

Self::deposit_event(Event::ValidationEntryAdded {

author: who,

id: data_id.to_vec(),

checksum,

});

Ok(())

<ValidationRecords<T>>::try_mutate(&who, &data_id, |maybe_record| {

let record = maybe_record.as_mut().ok_or(Error::<T>::RecordNotCreated)?;

record.entries.force_push(ValidationEntry {

checksum,

block: <frame_system::Pallet<T>>::block_number(),

})?;

Self::deposit_event(Event::ValidationEntryAdded {

author: who,

id: data_id.into_vec(),

checksum,

});

Ok(())

})

zees-dev · 2025-01-08T05:46:42Z

pallet/sylo/src/lib.rs

+			let mut record = <ValidationRecords<T>>::get(who.clone(), data_id.clone())
+				.ok_or(Error::<T>::RecordNotCreated)?;
+
+			if let Some(resolvers) = resolvers.clone() {
+				Self::validate_sylo_resolvers(resolvers.clone())?;
+				record.resolvers = resolvers;
+			}
+
+			if let Some(data_type) = data_type.clone() {
+				record.data_type = data_type;
+			}
+
+			if let Some(tags) = tags.clone() {
+				record.tags = tags;
+			}
+
+			<ValidationRecords<T>>::insert(who.clone(), data_id.clone(), record);
+
+			Self::deposit_event(Event::ValidationRecordUpdated {
+				author: who,
+				id: data_id.to_vec(),
+				resolvers: resolvers
+					.map(|resolvers| resolvers.iter().map(|resolver| resolver.to_did()).collect()),
+				data_type: data_type.map(|data_type| data_type.to_vec()),
+				tags: tags.map(|tags| tags.iter().map(|tag| tag.to_vec()).collect()),
+			});
+
+			Ok(())


more efficient as we only clone if/when required:

Suggested change

let mut record = <ValidationRecords<T>>::get(who.clone(), data_id.clone())

.ok_or(Error::<T>::RecordNotCreated)?;

if let Some(resolvers) = resolvers.clone() {

Self::validate_sylo_resolvers(resolvers.clone())?;

record.resolvers = resolvers;

}

if let Some(data_type) = data_type.clone() {

record.data_type = data_type;

}

if let Some(tags) = tags.clone() {

record.tags = tags;

}

<ValidationRecords<T>>::insert(who.clone(), data_id.clone(), record);

Self::deposit_event(Event::ValidationRecordUpdated {

author: who,

id: data_id.to_vec(),

resolvers: resolvers

.map(|resolvers| resolvers.iter().map(|resolver| resolver.to_did()).collect()),

data_type: data_type.map(|data_type| data_type.to_vec()),

tags: tags.map(|tags| tags.iter().map(|tag| tag.to_vec()).collect()),

});

Ok(())

<ValidationRecords<T>>::try_mutate(&who, &data_id, |maybe_record| {

let record = maybe_record.as_mut().ok_or(Error::<T>::RecordNotCreated)?;

if let Some(ref new_resolvers) = resolvers {

Self::validate_sylo_resolvers(new_resolvers)?;

record.resolvers = new_resolvers.clone();

}

if let Some(ref new_data_type) = data_type {

record.data_type = new_data_type.clone();

}

if let Some(ref new_tags) = tags {

record.tags = new_tags.clone();

}

Self::deposit_event(Event::ValidationRecordUpdated {

author: who,

id: data_id.into_vec(),

resolvers: resolvers.map(|r| r.iter().map(|resolver| resolver.to_did()).collect()),

data_type: data_type.map(|dt| dt.into_vec()),

tags: tags.map(|t| t.iter().map(|tag| tag.into_vec()).collect()),

});

Ok(())

})

zees-dev · 2025-01-08T05:48:46Z

pallet/sylo/src/lib.rs

+			let who = ensure_signed(origin)?;
+
+			ensure!(
+				<ValidationRecords<T>>::get(who.clone(), data_id.clone()).is_some(),


Suggested change

<ValidationRecords<T>>::get(who.clone(), data_id.clone()).is_some(),

<ValidationRecords<T>>::contains_key(&who, &data_id),

zees-dev · 2025-01-08T05:49:02Z

pallet/sylo/src/lib.rs

+				Error::<T>::RecordNotCreated
+			);
+
+			<ValidationRecords<T>>::remove(who.clone(), data_id.clone());


Suggested change

<ValidationRecords<T>>::remove(who.clone(), data_id.clone());

<ValidationRecords<T>>::remove(&who, &data_id);

zees-dev · 2025-01-08T05:49:56Z

pallet/sylo/src/lib.rs

+			Ok(())
+		}
+
+		pub fn payment_asset() -> Option<AssetId> {


seems redundant; can just call the type function directly IMO

zees-dev · 2025-01-08T05:55:39Z

pallet/sylo/src/benchmarking.rs

+
+		let mut service_endpoints = BoundedVec::new();
+		for _ in 1..q {
+			service_endpoints.force_push(bounded_string::<T>("https://service-endpoint.one.two.three"));


probaby push max string size here too; we need upper bound test

zees-dev · 2025-01-08T05:56:19Z

pallet/sylo/src/benchmarking.rs

+		for _ in 1..q {
+			service_endpoints.force_push(bounded_string::<T>("https://service-endpoint.one.two.three"));
+		}
+	}: _(origin::<T>(&alice), identifier, service_endpoints)


worthwhile having benchmark validations; you can look at other benchmarks (maybe crowdsale pallet) - which has examples of quick validations post-test.
A single validation should do.

zees-dev · 2025-01-08T05:58:10Z

pallet/sylo/src/mock.rs

+	type WeightInfo = ();
+}
+
+#[derive(Default)]


i think we should be able to use the test helpers testext instead od declaring a new/custom one here

zees-dev · 2025-01-08T06:01:06Z

pallet/sylo/src/tests.rs

+	}
+}
+
+fn create_and_register_resolver(


move helper functions to top; i think we follow this approach for most of the tests

zees-dev · 2025-01-08T06:02:26Z

pallet/sylo/src/tests.rs

+	return (data_id, resolvers, data_type, tags, checksum, record);
+}
+
+fn create_resolver_id(method: &str, identifier: &str) -> ResolverId<<Test as Config>::StringLimit> {


dont think this is needed; can inline into the caller function

zees-dev · 2025-01-08T06:05:48Z

pallet/sylo/src/tests.rs

+	}
+}
+
+mod validation_records {


nit: ideally we try create a mod for each extrinsic - which is easier to reason as we can test all flows within the same module.
Examples of this should be in the crowdsale or nft pallet tests.

zees-dev

nice; looking mostly good!
Most of the suggestions are purely syntactical improvements and/or improvements to memory.

Atleast 2 major things are still required:

benchmark weight updates
e2e tests to validate sylo token payment (NOTE: the refund for any over-payment would be given in the native currency)

Other than that; logic seems sound.

JCSanPedro added 12 commits December 16, 2024 13:24

create cargo package for new sylo pallet

91b30bc

implement pallet functionality for registering resolvers

5a7b675

implement tests for registering resolvers

c1c16a7

implement functionality for record validation

d1ef366

implement tests for creating validation records

9e781ef

setup benchmarking for sylo pallet

2b58555

implement remaning sylo extrinsic benchmarks

c65bf9d

modify on charge tx to force sylo fee swap for sylo pallet extrinsics

24cf65b

use a storage value for reserved sylo resolver method

42d44fa

fix mock in fee-control tests

c5a30eb

add more comments to config

cb35ca0

fix tests compiling

744a8b5

zees-dev reviewed Jan 8, 2025

View reviewed changes

runtime/src/weights/pallet_sylo.rs Outdated

Copy link

Contributor

zees-dev Jan 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

weights need to be generated via CI - the runner would commit the updated weights

zees-dev reviewed Jan 8, 2025

View reviewed changes

pallet/fee-proxy/src/impls.rs Outdated

Copy link

Contributor

zees-dev Jan 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will wait for validated E2E tests to approve changes here

zees-dev reviewed Jan 8, 2025

View reviewed changes

JCSanPedro added 4 commits January 10, 2025 11:43

implement integration tests for sylo pallet fees

0abe851

resize constants for sylo config

5b6abc1

use EnsureOrigin and emit event on state change

8c8ac52

avoid unnecessary clones in sylo pallet

d09e6be

JCSanPedro force-pushed the TRN-808-sylo-pallet branch 2 times, most recently from 5a325b7 to 7ed93e4 Compare January 12, 2025 21:26

ensure strings have upper bound in benchmark and add verification

42246f2

JCSanPedro force-pushed the TRN-808-sylo-pallet branch from 7ed93e4 to 42246f2 Compare January 12, 2025 22:47

refactor tests

0fbda1f

JCSanPedro force-pushed the TRN-808-sylo-pallet branch from 30ab16b to 9865f3e Compare January 12, 2025 23:43

fix benchmark verification

36b1522

JCSanPedro force-pushed the TRN-808-sylo-pallet branch from 9865f3e to 36b1522 Compare January 12, 2025 23:59

Update benchmarks for pallet-sylo on TRN-808-sylo-pallet

3cf92d5

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

TRN-808 Sylo Data Pallet #917

TRN-808 Sylo Data Pallet #917

JCSanPedro commented Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

JCSanPedro Jan 13, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025 •

edited

Loading

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025 •

edited

Loading

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev Jan 8, 2025

zees-dev left a comment

	<ValidationRecords<T>>::get(who.clone(), data_id.clone()).is_none(),
	<ValidationRecords<T>>::get(&who, &data_id).is_none(),

	Self::validate_sylo_resolvers(resolvers.clone())?;
	Self::validate_sylo_resolvers(&resolvers)?;

	<ValidationRecords<T>>::insert(who.clone(), data_id.clone(), record);
	<ValidationRecords<T>>::insert(&who, &data_id, record);

	let mut record = <ValidationRecords<T>>::get(who.clone(), data_id.clone())
	let mut record = <ValidationRecords<T>>::get(&who, &data_id)

	<ValidationRecords<T>>::get(who.clone(), data_id.clone()).is_some(),
	<ValidationRecords<T>>::contains_key(&who, &data_id),

	<ValidationRecords<T>>::remove(who.clone(), data_id.clone());
	<ValidationRecords<T>>::remove(&who, &data_id);

TRN-808 Sylo Data Pallet #917

Are you sure you want to change the base?

TRN-808 Sylo Data Pallet #917

Conversation

JCSanPedro commented Jan 8, 2025

Description

Resolvers

Validation Records

Notes

Release Notes

Key Changes

Type of Change

Extrinsic Changes

Added

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

zees-dev Jan 8, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

zees-dev Jan 8, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

zees-dev left a comment

Choose a reason for hiding this comment

zees-dev Jan 8, 2025 •

edited

Loading

zees-dev Jan 8, 2025 •

edited

Loading