Http Get support for NFT feature #22

laruh · 2024-05-05T03:21:44Z

In the PR the Proxy layer handles the request method type according to the "proxy_type" field specified in the application configuration.

enum ProxyType was provided. It enumerates different proxy types supported by the application, focusing on separating feature logic.

#[serde(rename_all = "snake_case")]  
pub(crate) enum ProxyType {  
    Quicknode,  
    Moralis,  
}

enum PayloadData was provided. It is supposed to handle different payload types related to request to proxy layer.
docker-compose.yml is configured for development and local test.

TODOs

validation_middleware for Moralis reqs
test ^ with multiple requests properly (this is more a note to the reviewers, that middleware still needs to be tested):
UPD: validation_middleware_moralis works in particular for multiple requests to NFT moralis endpoints. If rate exceed, you will get NOT_ACCEPTABLE error and have to wait some time before sending more requests
add an optional "rate_limiter" field to the ProxyRoute structure. This will allow us to provide unique rate limits for specific features if necessary. If None proxy will just use the default "rate_limiter" params which you can find in Readme in current configuration file example
update readme

Request example

curl --url "http://127.0.0.1:7783" --data '{
  "userpass": "'$USERPASS'",
  "method": "enable_eth_with_tokens",
  "mmrpc": "2.0",
  "params": {
    "ticker": "MATIC",
    "mm2": 1,
    "swap_contract_address": "0x9130b257D37A52E52F21054c4DA3450c72f595CE",
    "swap_v2_contracts":{
	    "maker_swap_v2_contract": "0x9130b257D37A52E52F21054c4DA3450c72f595CE",
	    "taker_swap_v2_contract": "0x9130b257D37A52E52F21054c4DA3450c72f595CE",
	    "nft_maker_swap_v2_contract": "0x9130b257D37A52E52F21054c4DA3450c72f595CE"
    },    
    "fallback_swap_contract": "0x9130b257D37A52E52F21054c4DA3450c72f595CE",
    "nodes": [
      {
        "url": "https://polygon-rpc.com"
      }
    ],
    "erc20_tokens_requests": [],
    "nft_req": {
      "provider":{
        "type": "Moralis",
        "info": {
          "url":"http://localhost:6150/nft-test",
          "proxy_auth":true
        }
      }
    }
  }
}'

PS: if you want to test feature locally, you can run docker containers with docker compose commands. DM me about nft url for app config.

Build image

docker compose build

Run containers in the background (detached mode)

docker compose up -d

Open a new terminal window or tab and execute this command to follow the logs of all services defined in a Docker Compose file. The -f or --follow option ensures that new log entries are continuously displayed as they are produced, while the -t or --timestamps option adds timestamps to each log entry.

docker compose logs -f -t

Stop containers

docker compose down

Closes #21

…general generate_payload_from_req func; doc comms; add url crate

…et_url_payload

…re doc comms

…type is enough

…ize, and for general impl path in req uri have to represent only inbound_route

laruh · 2024-05-07T04:36:39Z

Here is the example of how to send request from komodo-defi using proxy layer for Nft feature. You should add /nft path to proxy base url.

enable_eth_with_tokens request example

curl --url "http://127.0.0.1:7783" --data '{
  "userpass": "'$USERPASS'",
  "method": "enable_eth_with_tokens",
  "mmrpc": "2.0",
  "params": {
    "ticker": "MATIC",
    "mm2": 1,
    "swap_contract_address": "0x9130b257D37A52E52F21054c4DA3450c72f595CE",
    "fallback_swap_contract": "0x9130b257D37A52E52F21054c4DA3450c72f595CE",
    "nodes": [
      {
        "url": "https://polygon-rpc.com"
      }
    ],
    "erc20_tokens_requests": [],
    "nft_req": {
      "provider":{
        "type": "Moralis",
        "info": {
          "url":"http://localhost:6150/nft"
        }
      }
    }
  }
}'

enable_eth_with_tokens response example

{
  "mmrpc": "2.0",
  "result": {
    "current_block": 56669925,
    "eth_addresses_infos": {
      "0xf622…b6a2": {
        "derivation_method": {
          "type": "Iguana"
        },
        "pubkey": "0412....b81",
        "balances": {
          "spendable": "1.89373072555993582",
          "unspendable": "0"
        }
      }
    },
    "erc20_addresses_infos": {
      "0xf622…b6a2": {
        "derivation_method": {
          "type": "Iguana"
        },
        "pubkey": "0412....b81",
        "balances": {}
      }
    },
    "nfts_infos": {
      "0x48c75fbf0452fa8ff2928ddf46b0fe7629cca2ff,5": {
        "token_address": "0x48c75fbf0452fa8ff2928ddf46b0fe7629cca2ff",
        "token_id": "5",
        "chain": "POLYGON",
        "contract_type": "ERC1155",
        "amount": "1"
      },
      "0xc06a6ab4c2b0ed14ed5692adf324a9a463259c43,0": {
        "token_address": "0xc06a6ab4c2b0ed14ed5692adf324a9a463259c43",
        "token_id": "0",
        "chain": "POLYGON",
        "contract_type": "ERC1155",
        "amount": "1"
      },
      "0x22d5f9b75c524fec1d6619787e582644cd4d7422,201": {
        "token_address": "0x22d5f9b75c524fec1d6619787e582644cd4d7422",
        "token_id": "201",
        "chain": "POLYGON",
        "contract_type": "ERC1155",
        "amount": "3000000000000000000"
      }
    }
  },
  "id": null
}

…_http_get, have general validation_middleware func which handle all PayloadData types

laruh · 2024-05-12T08:04:18Z

UPD: faced some issues in wasm target. Need to change nft reqs to regular POST format in komodefi repo and do some changes here.

onur-ozkan · 2024-05-13T04:58:40Z

UPD: faced some issues in wasm target. Need to change nft reqs to regular POST format in komodefi repo and do some changes here.

Feel free to ping me once it's ready so I can make a review here.

…BLE error if rate exceed for HTTP GET request

laruh · 2024-05-13T09:33:07Z

Feel free to ping me once it's ready so I can make a review here.

@onur-ozkan its r2r.
made some changes to properly handle requests to the proxy by modifying incoming requests with specific payload data to use GET method.

laruh · 2024-05-23T05:00:47Z

Update: Just read the comment here #22 (comment) and it seems that this is what @onur-ozkan requested

Yes, thats what I wanted to clarify. The examples provided were related to quicknode requests, for which we dont need to catch and remove path segments. That was confusing.

I was uncertain whether handling two different logics (for one req type we can take uri.path() without checks, for another we have to get first path segment) within the general code, where we need to find ProxyRoute, is a good approach since it adds additional checks and manipulations with the URI.

I wanted to know if adding the inbound_route and then removing it is what we want (in the context of nft feature implementation)

UPD: "outbound_route" in configs for nft feature should be not moralis original base url, but komodo moralis proxy

…rent stage only quicknode feature supports both websocket and http.

laruh · 2024-05-24T09:52:52Z

@shamardy @onur-ozkan I suggest doing a Quicknode refactoring in HTTP headers as a separate issue with new pull requests (in the Defi framework and proxy repositories). This approach will make development and review easier. The pull request in the KomodoDefi Framework already contains a lot of code changes related to other features and should be merged first.

shamardy

LGTM! Only one non-blocker comment from my side.

shamardy · 2024-06-21T21:16:56Z

src/net/http.rs

+    // If we leave this code line `let proxy_route = match cfg.get_proxy_route_by_inbound(req.uri().to_string()) {`
+    // inbound_route cant be "/test", as it's not uri. I suppose inbound actually should be a Path.
+    // Two options: in `req.uri().to_string()` path() is missing or "/test" in test is wrong and the whole url should be.
+    let proxy_route = cfg.get_proxy_route_by_inbound("/test").unwrap();


Is this comment still needed? I see that you already use path()

oh, yes, should remove it, as it was supposed to be an important note for reviewers on pr's early stages.
fixed it 226db21

…ft-support-refactor-quicknode

…node refactor quicknode: move SignedMessage to Header

onur-ozkan

Do we have an automated deployment anywhere for this repository? @smk762 This PR contains lots of breaking changes, if we pull the latest changes to the live APIs, we should implement the necessary changes on kdf side before merging this.

onur-ozkan · 2024-06-27T04:47:52Z

src/net/http.rs

+/// Value
+pub(crate) const APPLICATION_JSON: &str = "application/json";
+/// Header
+pub(crate) const X_FORWARDED_FOR: &str = "x-forwarded-for";


Suggested change

/// Value

pub(crate) const APPLICATION_JSON: &str = "application/json";

/// Header

pub(crate) const X_FORWARDED_FOR: &str = "x-forwarded-for";

/// Header value for `hyper::header::CONTENT_TYPE`

pub(crate) const APPLICATION_JSON: &str = "application/json";

/// Header key for `hyper::header::CONTENT_TYPE`

pub(crate) const X_FORWARDED_FOR: &str = "x-forwarded-for";

updated docs e81cfb9

onur-ozkan · 2024-06-27T05:08:26Z

src/net/http.rs

+    let inbound_route = match req.method() {
+        // should take the second element as path string starts with a delimiter
+        &Method::GET => req.uri().path().split('/').nth(1).unwrap_or("").to_string(),


Could you explain why?

to extract inbound_route in GET method case

https://komodoproxy.com/nft-feature/api/v2.2/0x1f9090aaE28b8a3dCeaDf281B0F12828e676c326/nft/transfers?chain=eth&format=decimal&order=DESC

targets https://moralis.io/api/v2.2/0x1f9090aaE28b8a3dCeaDf281B0F12828e676c326/nft/transfers?chain=eth&format=decimal&order=DESC

In POST request it is easy to extract inbound_route, as its the whole path.
For GET we decided to include inbound_route in Url, not in header or body.
Which means that we will need to get inbound_route from Url and change Url on the step when we send req to target.

The problem is this will not work with the configuration other than /something inbound.

Let's say we have this configuration:

inbound_route: String::from_str("/").unwrap(), outbound_route: "http://localhost:8000".to_string(),

or:

inbound_route: String::from_str("/something/else").unwrap(), outbound_route: "http://localhost:8000".to_string(),

in this case, unwrap_or will be triggered and inbound_route become an empty string.

What about doing this: Iterate over the inbound routes from the configuration and check if the request path starts with any of them. Once you find the matching inbound route, extract that part from the request path and add it to the outbound route.

There is an edge case in this logic that needs to be handled; if you have inbound routes like /nft/special and /nft in the configuration, both will return true for starts_with on a request path like demo.com/nft/special/1/2/3. In such cases, if multiple inbound routes return true for starts_with, we should always pick the longest one.

The problem is this will not work with the configuration other than /something inbound.

Let's say we have this configuration:

inbound_route: String::from_str("/").unwrap(), outbound_route: "http://localhost:8000".to_string(),

or:

inbound_route: String::from_str("/something/else").unwrap(), outbound_route: "http://localhost:8000".to_string(),

in this case, unwrap_or will be triggered and inbound_route become an empty string.

What about doing this: Iterate over the inbound routes from the configuration and check if the request path starts with any of them. Once you find the matching inbound route, extract that part from the request path and add it to the outbound route.

There is an edge case in this logic that needs to be handled; if you have inbound routes like /nft/special and /nft in the configuration, both will return true for starts_with on a request path like demo.com/nft/special/1/2/3. In such cases, if multiple inbound routes return true for starts_with, we should always pick the longest one.

The easiest way was just include inbound string in Header, then you can have any inbound_route what you want. So you dont have to do check iterations and dont do complex re creation of Url, just change base url

I still can do some changes on kdf side and move proxy inbound route to header

But if you prefer to have /path1/path2/etc rout right in Path, I will do the inbound routs search to find the exact match of /path1/path2/etc inbound in Path. But then I suggest to do the req url change in get_proxy_route_by_inbound function and remove matching from Url, so we wont need to search the matching again to remove it in modify_request_uri function.

I still can do some changes on kdf side and move proxy inbound route to header

That brings the old discussion where we talk about "putting inbound route to the request". For ref, I suggest to look how other layer7 proxy servers work (e.g., nginx, traefik, etc).

But if you prefer to have /path1/path2/etc rout right in Path, I will do the inbound routs search to find the exact match of /path1/path2/etc inbound in Path.

In practice, we can not have every possible route registered in the configuration, unfortunately.

In practice, we can not have every possible route registered in the configuration, unfortunately.

Didnt get it, after finding the list of matched routs (by first segment), I suggest to go trough each path element until we exclude all matched elements.
If there are two routs in config: /nft, /nft/service1/, and request Url matches only the first variant
https://komodoproxy.com/nft/api/v2.2/0x1f9090aaE28b8a3dCeaDf281B0F12828e676c326/nft/transfers?chain=eth&format=decimal&order=DESC
We should stop at service1 as match for this element is not found

Done here 6422433

onur-ozkan · 2024-06-27T05:12:28Z

src/proxy/mod.rs

+    Quicknode {
+        payload: QuicknodePayload,
+        signed_message: SignedMessage,
+    },
+    /// Moralis feature requires only Signed Message in X-Auth-Payload header
+    Moralis(SignedMessage),


Since #23 this is same for quicknode too if I am not mistaken.

It means that Moralis feature in Proxy layer needs only sig message from us, while Quicknode needs sig message + payload. I will add doc comm for Quicknode and update Moralis doc to avoid confusion

onur-ozkan · 2024-06-27T05:19:23Z

src/proxy/mod.rs

+/// Parses the request body and the `X-Auth-Payload` header into a payload and signed message.
+///
+/// This function extracts the `X-Auth-Payload` header from the request, parses it into a `SignedMessage`,
+/// and then reads and deserializes the request body into a specified type `T`.
+/// If the body is empty or the header is missing, an error is returned.
+async fn parse_body_payload<T>(


Header is not part of the body, so function name and its documentation doesn't seem to be connected.

changed namings for both parse functions e81cfb9

onur-ozkan · 2024-06-27T05:25:42Z

src/proxy/moralis.rs

+    // Remove the first path segment
+    let mut path_segments: Vec<&str> = req_uri
+        .path()
+        .split('/')
+        .filter(|s| !s.is_empty())
+        .collect();


I suppose this is the same reason why we skip the first segment during inbound route parsing.

Yes, in modify_request_uri we should remove inbound_route from req uri and change base url

onur-ozkan · 2024-06-27T05:28:40Z

src/proxy/moralis.rs

+/// Modifies the URI of an HTTP request by replacing its base URI with the outbound URI specified in `ProxyRoute`,
+/// while incorporating the path and query parameters from the original request URI. Additionally, this function
+/// removes the first path segment from the original URI.
+async fn modify_request_uri(


Is there any particular reason for making this function async ?

you are right, should should be sync e81cfb9

…sync

laruh · 2024-06-27T06:44:49Z

This PR contains lots of breaking changes, if we pull the latest changes to the live APIs, we should implement the necessary changes on kdf side before merging this

I did changes on komodefi side
KomodoPlatform/komodo-defi-framework#2100 - contains moralis changes
KomodoPlatform/komodo-defi-framework#2129 - quicknode changes

of course we should test #2129 before merging it in dev (I mean 2129 already contains 2100 changes, so we can test both moralis and quicknode updates with it) using some test proxy service.

laruh · 2024-06-27T10:36:44Z

https://github.com/KomodoPlatform/komodo-defi-proxy/actions/runs/9691846400/job/26744135818?pr=22#step:4:331

last nightly lint started to fail. will check it

UPD: fixed there 765f584
it is related to issue rust-lang/rust#123748

…y_route_by_uri_inbound` test, update modify_request_uri logic

onur-ozkan · 2024-07-02T07:54:16Z

src/ctx.rs

+            let remaining_path: String = path_segments.iter().skip(matched_segments).fold(
+                String::new(),
+                |mut acc, segment| {


You know the total size already - Can you consider preallocating String size here?

onur-ozkan · 2024-07-02T07:59:51Z

src/ctx.rs

+        for r in &self.proxy_routes {
+            let route_segments: Vec<&str> = r
+                .inbound_route
+                .split('/')
+                .filter(|s| !s.is_empty())
+                .collect();
+            // Count the number of segments that match between the route and the path
+            let matched_segments = route_segments
+                .iter()
+                .zip(&path_segments)
+                .take_while(|(route_seg, path_seg)| route_seg == path_seg)
+                .count();


Not a blocker but depending on the request and route configuration, this can cause lots of iterations (from parent to sub iterations).

I did something like this, which should be more sufficient:

fn find_route_from_url(incoming_url: &Url, routes: &[Route]) -> Option<Route> { let path = incoming_url.path(); let mut matched_route: Option<&Route> = None; for route in routes { if path.starts_with(&route.inbound) { if let Some(r) = matched_route { if r.inbound.len() > route.inbound.len() { continue; } } matched_route = Some(route); } } matched_route.cloned() } fn inbound_url_to_outbound_url(inbound_url: Url, route: &Route) -> Url { let inbound_url_str = inbound_url.to_string(); let path = inbound_url_str .split_once(inbound_url.host_str().unwrap()) .expect("inbound url must contain a host") .1; let path = path .strip_prefix(&route.inbound) .expect("Route doesn't match with the given inbound url."); let url = format!( "{}/{}", route.outbound.strip_suffix('/').unwrap_or(&route.outbound), path.strip_prefix('/').unwrap_or(&path) ); Url::parse(&url).expect("valid url") }

the test function:

#[test] fn find_best_match() { fn test_helper(inbound_url: Url, routes: &[Route]) -> String { let route = find_route_from_url(&inbound_url, routes).unwrap(); let result = inbound_url_to_outbound_url(inbound_url, &route); result.to_string() } let routes = vec![ Route { inbound: "/".into(), outbound: "https://k.com".into(), }, Route { inbound: "/demo".into(), outbound: "https://kmd.com".into(), }, Route { inbound: "/demo/demo".into(), outbound: "https://komodo.com".into(), }, Route { inbound: "/demo/demo/demo".into(), outbound: "https://kdf.com/komodo".into(), }, ]; let inbound = Url::parse("https://rproxy-app.service/hello/there").unwrap(); let expected_outbound_url = "https://k.com/hello/there"; let actual_outbound_url = test_helper(inbound, &routes); assert_eq!(actual_outbound_url, expected_outbound_url); let inbound = Url::parse("https://rproxy-app.service/demo/some/stuff/").unwrap(); let expected_outbound_url = "https://kmd.com/some/stuff/"; let actual_outbound_url = test_helper(inbound, &routes); assert_eq!(actual_outbound_url, expected_outbound_url); let inbound = Url::parse("https://rproxy-app.service/demo/demo/okay?q=123").unwrap(); let expected_outbound_url = "https://komodo.com/okay?q=123"; let actual_outbound_url = test_helper(inbound, &routes); assert_eq!(actual_outbound_url, expected_outbound_url); let inbound = Url::parse("https://rproxy-app.service/demo/demo/demo/1/2/3").unwrap(); let expected_outbound_url = "https://kdf.com/komodo/1/2/3"; let actual_outbound_url = test_helper(inbound, &routes); assert_eq!(actual_outbound_url, expected_outbound_url); }

I did something like this, which should be more sufficient

in your example you use Url type from url crate. Do you suggest to add this dependency? Currently we use only Uri

upd: I suppose I can do it with Uri

Yes, it should be possible with uri crate too (if not feel free to add Url 2.2.2 as it's already in our dependency stack).

Updated in this commit e3d81fa

moved delete inbound from Uri logic back to modify uri function, so get route just gets proxy route, modify function modifies Uri

…, move delete inbound from Uri to modify_request_uri

onur-ozkan

It feels quite risky but I assume we don't do any automatic deployments for this repository. So let's ship this and hope nothing breaks.

I wish we had already resolved #16 (':

laruh added 10 commits April 30, 2024 19:52

impl PayloadData which has JsonRpcPayload and GetUrlPayload; provide …

2434bd3

…general generate_payload_from_req func; doc comms; add url crate

remove Unnecessary trailing semicolon

91aa895

use get_proxy_route_by_inbound func in http_handler, add test_parse_g…

f4fab5a

…et_url_payload

rename GetUrl to HttpGet and GetUrlPayload to HttpGetPayload, some mo…

7abd17c

…re doc comms

provide PayloadData type in proxy and validation_middleware funcs

ac1c9e2

impl proxy_http_get

93d5563

docker-compose.yml for local tests and app json config

04d8728

impl modify_request_uri func

3136f4b

use modify_request_uri func in proxy_http_get

84a1f62

remove url dependency, as for modify_request_uri functionality Uri …

d980f64

…type is enough

laruh self-assigned this May 5, 2024

laruh added 3 commits May 6, 2024 17:25

return Url type in HttpGetPayload. we need it for Deserialize, Serial…

69fe4b8

…ize, and for general impl path in req uri have to represent only inbound_route

update note in modify_request_uri

e022f40

update log name in macro_rules! log_format

412739e

laruh requested a review from onur-ozkan May 6, 2024 14:23

laruh mentioned this pull request May 6, 2024

feat(nft-swap): add standalone maker contract and proxy support KomodoPlatform/komodo-defi-framework#2100

Merged

laruh added 2 commits May 7, 2024 09:45

provide error message in logs

bca2338

remove header::CONTENT_LENGTH from http get request

80d92fb

laruh added 2 commits May 8, 2024 14:29

simplify upsert_address_rate_in_pipe func, impl validation_middleware…

0294f19

…_http_get, have general validation_middleware func which handle all PayloadData types

rename proxy_eth to proxy_json_rpc

cacce87

shamardy self-requested a review May 9, 2024 13:04

laruh changed the title ~~HTTP GET request support~~ [wip] NFT feature support May 12, 2024

laruh changed the title ~~[wip] NFT feature support~~ Http Get req support May 12, 2024

add get_req: bool param into parse_payload function

8a201da

laruh force-pushed the nft-support branch from cbf355e to 8a201da Compare May 12, 2024 10:03

provide optional rate_limiter field in ProxyRoute, return NOT_ACCEPTA…

8bd9d87

…BLE error if rate exceed for HTTP GET request

laruh added 2 commits May 23, 2024 17:47

update GET req handling for Moralis

e607cbb

use req.uri().path() to find ProxyRote in websocket. Note: in the cur…

e98cf08

…rent stage only quicknode feature supports both websocket and http.

refactor quicknode: move SignedMessage to Header

d86b97f

This was referenced Jun 5, 2024

refactor quicknode: move SignedMessage to Header #23

Merged

ERC721/ERC1155 support adding for EVM protocols KomodoPlatform/komodo-defi-framework#900

Open

shamardy approved these changes Jun 21, 2024

View reviewed changes

laruh and others added 3 commits June 22, 2024 14:01

review: remove note about inbound_route in test

226db21

Merge remote-tracking branch 'refs/remotes/origin/nft-support' into n…

db6e9cd

…ft-support-refactor-quicknode

Merge pull request #23 from KomodoPlatform/nft-support-refactor-quick…

c66f316

…node refactor quicknode: move SignedMessage to Header

onur-ozkan reviewed Jun 27, 2024

View reviewed changes

onur-ozkan added in progress and removed under review labels Jun 27, 2024

review: update docs, rename parse functions, modify_request_uri non a…

e81cfb9

…sync

state unit types explicitly to adapt to new never type fallback

765f584

laruh force-pushed the nft-support branch from d06a2be to efce9fa Compare June 30, 2024 06:25

laruh added under review and removed in progress labels Jul 1, 2024

impl get_proxy_route_extracting_uri_inbound func and `test_get_prox…

6422433

…y_route_by_uri_inbound` test, update modify_request_uri logic

laruh force-pushed the nft-support branch from 73f2122 to 6422433 Compare July 1, 2024 03:44

onur-ozkan reviewed Jul 2, 2024

View reviewed changes

review: avoid multiple iterations in get proxy with Uri functionality…

e3d81fa

…, move delete inbound from Uri to modify_request_uri

onur-ozkan approved these changes Jul 8, 2024

View reviewed changes

onur-ozkan merged commit 547b493 into main Jul 8, 2024
24 checks passed

onur-ozkan deleted the nft-support branch July 8, 2024 10:25

laruh mentioned this pull request Jul 10, 2024

NFT RPC Methods Docs update KomodoPlatform/komodo-docs-mdx#270

Merged

Http Get support for NFT feature #22

Http Get support for NFT feature #22

Conversation

laruh commented May 5, 2024 • edited by onur-ozkan Loading

laruh commented May 7, 2024 • edited Loading

laruh commented May 12, 2024 • edited Loading

onur-ozkan commented May 13, 2024

laruh commented May 13, 2024

laruh commented May 23, 2024 • edited Loading

laruh commented May 24, 2024 • edited Loading

shamardy left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

onur-ozkan left a 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

laruh Jun 27, 2024 • edited Loading

Choose a reason for hiding this comment

laruh Jun 27, 2024 • edited Loading

Choose a reason for hiding this comment

onur-ozkan Jun 27, 2024 • edited Loading

Choose a reason for hiding this comment

laruh Jun 27, 2024 • 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

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

laruh commented Jun 27, 2024

laruh commented Jun 27, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

laruh Jul 2, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

onur-ozkan left a comment

Choose a reason for hiding this comment

laruh commented May 5, 2024 •

edited by onur-ozkan

Loading

laruh commented May 7, 2024 •

edited

Loading

laruh commented May 12, 2024 •

edited

Loading

laruh commented May 23, 2024 •

edited

Loading

laruh commented May 24, 2024 •

edited

Loading

laruh Jun 27, 2024 •

edited

Loading

laruh Jun 27, 2024 •

edited

Loading

onur-ozkan Jun 27, 2024 •

edited

Loading

laruh Jun 27, 2024 •

edited

Loading

laruh commented Jun 27, 2024 •

edited

Loading

laruh Jul 2, 2024 •

edited

Loading