Internet Computer Wiki - User contributions [en]

Troubleshooting Unhealthy Nodes

2024-10-16T11:58:29Z

Malith: IC UDP port block issue diagnosis

== Troubleshooting node deployment ==
This guide is designed for troubleshooting ''unhealthy'' nodes—those are nodes that successfully ''installed'' IC-OS and ''registered'' with the IC, but on the [[Node Deployment Guide (with an HSM)|dashboard]], show a status that is NOT either “Awaiting Subnet” or “Active in Subnet”.

If your node did NOT successfully install IC-OS or if it failed to register with the IC, consult the [[Troubleshooting Node Deployment Errors]] guide.

== Verify and understand node health status==

=== Background ===
The dashboard provides real-time status of each node in the network. Nodes are identified by the principal of the currently deployed operating system (the "Node ID"), so the Node ID will change upon node redeployment. Node Providers are expected to maintain a private record correlating each server with its Node ID. This record is crucial for tracking, especially when nodes are redeployed with new Node IDs.

====Metrics and Monitoring ====
Metrics are collected from nodes situated in three key geographical locations: Frankfurt (FR1), Chicago (CH1), and San Francisco (SF1). Each location is equipped with an independent monitoring and observability system. These systems apply specific rules to identify normal and abnormal node behaviors.

==== Alerts and Troubleshooting ====
When a node exhibits abnormal behavior, an ALERT is triggered by the monitoring system. The nature of the alert is indicated on the dashboard under the node's status. This is an example of a "Degraded" node:[[File:Dashboard-degraded-node.png|center|frameless|499x499px]]

=== Verifying node status ===
*Use [https://dashboard.internetcomputer.org/centers the dashboard] to verify the status of your node
**The dashboard can be searched by your '''Node Provider principal''' or '''Node ID'''. If you search by '''Node Provider principal''', you should see the Node ID of your node and click through to the Node Machine page.

=== Understanding node status ===
If the status of your node is NOT either “Awaiting Subnet” or “Active in Subnet”, your node is unhealthy.

The dashboard indicates four possible statuses for each node:

*'''Active in Subnet''' - The node is healthy and actively functioning within a subnet.
*'''Awaiting Subnet''' - The node is operational and prepared to join a subnet when necessary. Node providers still get full rewards for nodes awaiting subnet.
*'''Degraded''' - Metrics can be scraped from the node, indicating it is online, but an ALERT has been raised. This status suggests the node may be struggling to keep up with network demands. For specific troubleshooting steps, identify your degraded node status from the below list.
*'''Offline''' - The monitoring system is unable to scrape metrics, possibly due to node failure or data center outage. Prioritize verifying network connectivity and hardware functionality. For specific troubleshooting steps, see below.

If your node is '''not listed at all''': A missing node from the list may indicate significant issues, requiring immediate attention and troubleshooting. If the node was functioning previously and is now not listed at all, this generally means that it started encountering issues and was removed from the registry. <br />
==Degraded nodes statuses==

===>> IC_OrchestratorFlapping===

'''Explanation:''' Orchestrator coordinates the execution of many IC GuestOS processes, including the IC Replica. If the orchestrator is repeatedly restarting, then the GuestOS and the Replica process likely do not operate as expected.

'''Possible causes:'''
*Networking issues
*Hardware issues
*Software problems

'''Troubleshooting and remediation:'''
*Check if any NNS proposals were recently executed for the nodes in question https://dashboard.internetcomputer.org/governance
* Check if there are some bandwidth limitations on these nodes, and ensure any traffic shaping, QoS, DOS protection, etc, are ''disabled'' on the ISP side
* Perform other [https://wiki.internetcomputer.org/w/index.php?title=Unhealthy_Nodes&veaction=edit#Setting_Up_an_Auxiliary_Machine_for_Network_Diagnostics network diagnostics checks]
* Inspect node logs and metrics, if possible
* Consult other node providers and DFINITY if there are any known software problems with the latest revision that the node(s) are running

===>> IC_Replica_Behind ===

'''Explanation:''' IC Replica is the main process. If the Replica process cannot catch up, then the replica (node) cannot be a productive member of the IC subnet.

'''Possible causes:'''
* Networking issues
* Hardware issues
* Software problems

'''Troubleshooting and remediation:'''
* Check if there are any hardware issues reported by the machine's BMC (Baseboard Management Controller)
* Perform [https://wiki.internetcomputer.org/wiki/Updating_Firmware firmware upgrade]
* Check if any NNS proposals were recently executed for the nodes in question https://dashboard.internetcomputer.org/governance
* Check if there are some bandwidth limitations on these nodes, and ensure any traffic shaping, QoS, DOS protection, etc, are ''disabled'' on the ISP side
* Perform other [https://wiki.internetcomputer.org/w/index.php?title=Unhealthy_Nodes&veaction=edit#Setting_Up_an_Auxiliary_Machine_for_Network_Diagnostics network diagnostics checks]
* Inspect node logs and metrics, if possible
* Consult other node providers and DFINITY if there are any known software problems with the latest revision that the node(s) are running

===>> IC_Replica_Behind_CLOCK ====

==== '''Overview of the Problem''' ====

The clock on the Internet Computer (IC) replica desynced due to UDP port 123 (NTP traffic) being blocked unexpectedly. This led to degraded performance in the IC dashboard.
To resolve this, you need to configure a test environment to simulate the setup, using a bare metal server or VM running Ubuntu 20.04, connected via your IPv6 subnet, and test if chrony is syncing the clock correctly.
If clock sync fails, we will perform a traceroute to identify where the packet drops are happening and consult the ISP if necessary.
==== 2. '''Setting Up the Test Server''' ====

Connect a VM or bare-metal server running '''Ubuntu 20.04''' to your network. Ensure that your '''IPv6 address''' and '''gateway''' are configured correctly.
===== Configure the IPv6 Address and Gateway =====

Open the network configuration file using the following command: <syntaxhighlight lang="shell">
sudo nano /etc/netplan/00-installer-config.yaml </syntaxhighlight>

Add or edit the IPv6 settings as follows: <syntaxhighlight lang="shell">
network: version: 2 ethernets: eth0: dhcp4: no dhcp6: no addresses: - YOUR_IPV6_ADDRESS/64 gateway6: YOUR_IPV6_GATEWAY nameservers: addresses: - 2001:4860:4860::8888 - 2001:4860:4860::8844 </syntaxhighlight>

Apply the configuration: <syntaxhighlight lang="shell">
sudo netplan apply </syntaxhighlight>

==== 3. '''Install and Configure Chrony''' ====

Chrony is used to synchronize the system clock with NTP servers. Install it by running: <syntaxhighlight lang="shell">
sudo apt update sudo apt install chrony -y </syntaxhighlight>

Edit the Chrony configuration file to use NTP pools: <syntaxhighlight lang="shell">
sudo nano /etc/chrony/chrony.conf </syntaxhighlight>

Add the following lines to ensure NTP synchronization: <syntaxhighlight lang="shell">
pool 0.pool.ntp.org iburst pool 1.pool.ntp.org iburst pool 2.pool.ntp.org iburst pool 3.pool.ntp.org iburst </syntaxhighlight>

Save the file and restart Chrony: <syntaxhighlight lang="shell">
sudo systemctl restart chrony </syntaxhighlight>

==== 4. '''Check Chrony Synchronization Status''' ====

Verify if Chrony is syncing with the NTP servers: <syntaxhighlight lang="shell">
chronyc tracking </syntaxhighlight>

Check the sources that Chrony is using to sync: <syntaxhighlight lang="shell">
chronyc sources </syntaxhighlight>

If the synchronization is successful, the chronyc tracking command should show the server is synchronized. If not, proceed to the next step.
==== 5. '''Perform a Traceroute to Diagnose Packet Drop''' ====

If Chrony is unable to sync, the issue might be caused by packet drops on UDP port 123. To identify where the issue is, perform a traceroute to one of the NTP servers (for example, <code>0.pool.ntp.org</code>) on port 123 (UDP): <syntaxhighlight lang="shell">
sudo traceroute -U -p 123 0.pool.ntp.org </syntaxhighlight>

This command will trace the path of UDP packets to the NTP server, allowing you to see where the packet drops occur.
==== 6. '''Interpret the Results''' ====

If the traceroute completes successfully, then the issue might be with the server's firewall or NTP configuration.
If packets are dropped at a specific hop: ** If it’s on your network, check the router, firewall, or switch for any port 123 (UDP) blocks. ** If the issue is with your ISP, the packets might be blocked at their hardware level by IDS/IPS systems. Provide the traceroute results to your ISP's support team for faster resolution.
==== 7. '''Consult ISP''' ====

If packet drops are identified on the ISP side, contact your ISP with the traceroute data. Explain that port 123 (UDP) is blocked and this is causing your IC clock to desync. Even though they might not block the port intentionally, security systems like IDS/IPS might kick in to block this traffic.
----

=== Additional Commands ===

* '''Check UDP open ports on the system:'''
* '''Verify if any firewall rules are blocking UDP port 123:'''
* '''Open UDP port 123 if it's blocked by UFW:'''

==Offline nodes==
Network issues are the main reason why nodes are in an "OFFLINE" state.

* Your node may not be reachable from the IC or
* You may not be able to reach other nodes the IC from your node or
* You may not be able to reach the monitoring servers from your node.

Please refer to the [[Troubleshooting Networking Issues]] guide.

Another possible reason for an OFFLINE node may be that your GuestOS failed to start due to a RAM failure.
==Server Troubleshooting Steps==
These steps may help when a server is unhealthy or has been removed from the network, but the connectivity in the data center is functioning correctly:

# Verify if the server is up and running:
#* Check the power status of the server.
#* Check if the server is displaying any error messages or indicators.
#* If possible, access the server remotely or physically to ensure it is functioning properly.
# Hook up a crash cart and check for errors on the screen, troubleshoot as needed.
# Consider [[Updating Firmware|updating the firmware]] if it has been a long time, and/or if you have recently had other nodes that needed firmware upgrades to become healthy again.
# If no known error is found, please [[Node Provider Roadmap#Milestone Five: Node Machine Onboarding|redeploy the node with a fresh IC-OS image]]

==Frequently Asked Questions==
'''Q: Is the monitoring system open-sourced? How does it communicate with the nodes?'''

A: The monitoring system configuration is not currently open-sourced. However, the node configuration that is required for proper node operation is fully open source. For more information about the node-to-node and node-to-monitoring communication, refer to the [https://sourcegraph.com/github.com/dfinity/ic/-/blob/ic-os/hostos/rootfs/etc/nftables.conf?L54-112 nftables configuration], which is the definitive guide for required open ports on Host OS, and [https://sourcegraph.com/github.com/dfinity/ic/-/blob/ic-os/guestos/rootfs/opt/ic/share/ic.json5.template?L322 similar nftables configuration] for the Guest OS. You can find the configuration for DFINITY-owned DCs and Gen1 node providers here: nftables configuration. We use [https://docs.victoriametrics.com/ Victoria Metrics] for metrics scraping (documentation) and [https://vector.dev vector.dev] for log scraping.

'''Q: What are the destination IPs and Ports for Frankfurt, Chicago, and San Francisco for connectivity troubleshooting?'''

A: At present, detailed node/port information is not publicly accessible, as disclosing this information is considered a security risk. To effectively troubleshoot connectivity issues with your nodes, we recommend setting up a "spot instance" or a temporary virtual machine (VM) with a cloud provider in each of the geographical regions. This approach allows you to test both connectivity and connection stability to your nodes, providing a practical solution for identifying and resolving network-related issues.

'''Q: The dashboard shows offline or degraded status for <DC>, but everything seems fine. What should we do?'''

A: Check if any of these issues are present: firewall restrictions, traffic shaping, DOS protection, or QOS features enabled on the ISP side. These should all be disabled for optimal node operation.

'''Q: Under what circumstances is a node removed from the IC network?'''

A: A node is removed from the IC network when it's deemed unhealthy. The determination of a node's health is made using tooling from https://github.com/dfinity/dre. This tooling assesses nodes based on various metrics and submits a proposal for their removal to maintain the highest level of decentralization possible. However, there are exceptions. For example, an unhealthy node might be temporarily retained if there are ongoing efforts to recover and restore it.

'''Q: How long can a node be down before it's excluded from the IC network?'''

A: There's no set time limit for how long a node can be down before exclusion. The decision is more qualitative and depends on the overall health of the network. Currently, the IC network can tolerate up to 1/3 of nodes in a 13-node subnet being down or unhealthy. This means a subnet can function with up to 4 unhealthy nodes. If the unhealthy nodes do not exceed this threshold, a node might be left in the subnet for a longer period, especially if there are efforts underway to make it healthy again.

'''Q: When are nodes typically removed or replaced?'''

A: Node removals or replacements are currently conducted semi-manually and are typically scheduled for Mondays or Fridays. This timing allows Foundation voters to participate in the decision-making process at the start or end of the workweek. However, as this process is manually conducted, exceptions may occur based on specific circumstances.

'''Q: What are the future plans for node management in the IC network?'''

A: In the medium term, there are plans to automate node replacements. This means node swaps might occur more frequently and systematically, reducing the manual overhead and potentially enhancing the network's resilience and performance.

Note: As with all network operations, these practices are subject to change based on technological advancements and the evolving needs of the IC network. It's always good to refer to https://github.com/dfinity/dre for the most current information and tooling.

'''Q: What is the standard procedure if a faulty component occurs and we have to take the server down for maintenance?'''

At the moment the process is as follows:

#The node provider should give their best to bring the server back up, as soon as possible
#The DFINITY DRE team will monitor the situation and submit any proposals to replace faulty nodes, if necessary, or reach out to individual node providers if node replacements wouldn't be effective enough.

So feel free to do maintenance whenever you need to. If node is not in a subnet, there is no problem to take the node down as long as necessary. If the node is in a subnet, node replication should handle it without problems. Please be aware that we are actively working on reward adjustments based on the number of active and productive nodes, so please try not to make the downtime longer than absolutely necessary, to avoid reward reductions.

One thing that would be really helpful from your side is:

# Find the subnet id in which the node is located, and check how many nodes in the subnet are currently unhealthy
# If there are more than 2 (e.g. 3, 4, ... nodes) unhealthy nodes in the subnet, please consider postponing the maintenance work until the number of unhealthy nodes in the subnet reduces again to under 2.

In the future, any NP will be able to run the [https://github.com/dfinity/dre DRE tooling] and there will be a financial incentive for the node providers to both a) keep all nodes in the subnet healthy, and b) submit proposals to replace unhealthy nodes or to improve decentralization.

Removing a Node From the Registry

2024-08-20T17:14:59Z

Malith: Updated guide for with HSM key

= Removing a node from the registry via DFX =

== When is this necessary? ==
Node operator records allow for some number of nodes to be joined to the network. This is called the '''node allowance'''. Redeploying the same machine will result in the node generating the same IPv6 address. When joining the network any old node-id associated with this address will be removed - and the node allowance will not be affected.

But if the BMC changes - because of a motherboard replacement for example - a new IPv6 address will be generated. In this case the node will appear new to the network upon joining. If the number of nodes deployed matches the node allowance, no new nodes can join.

In this case - the '''old node-id must be removed.'''

== Steps ==
# Ensure that the node does not exist in any subnet.
## If the node is in a subnet - request help on the [[Node Provider Matrix channel|matrix channel]].
## As a last resort, unplugging the node will work. Please alert the matrix channel you are doing this.
# If applicable, get the HSM (NodeOperator Key) from the data center. Skip if you used a `pem` file to create the node operator record.
## Insert it into a computer that has DFX installed and has internet access.
# Using the terminal, execute the following command (Where NODE_ID is the principal as shown on the dashboard of the node to remove):

=== IF USING PHYSICAL HSM: ===
#Configure dfx identity (Optional)
#*MacOS<syntaxhighlight lang="shell">
$ dfx identity new node-operator-hsm --hsm-key-id 01 --hsm-pkcs11-lib-path /Library/OpenSC/lib/opensc-pkcs11.so
</syntaxhighlight>
#*Linux<syntaxhighlight lang="shell">
$ dfx identity new node-operator-hsm --hsm-key-id 01 --hsm-pkcs11-lib-path /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
</syntaxhighlight>
#'''Set the Identity Globally''': You can set the identity globally using the <code>dfx identity</code> command, and then run the <code>dfx canister</code> command without the <code>--identity</code> flag.<syntaxhighlight lang="shell">
dfx identity use node-operator-hsm
</syntaxhighlight>
#Set HSM PIN Globally<syntaxhighlight lang="shell">
export DFX_HSM_PIN=358138
</syntaxhighlight>
#'''Run the Command After Setting the PIN''': Once you’ve set the environment variable, you can run the <code>dfx canister</code> command again:<syntaxhighlight lang="shell">
dfx canister --network ic --identity node-operator-hsm call rwlgt-iiaaa-aaaaa-aaaaa-cai remove_node_directly '(record { node_id = principal "YOUR NODE ID" })'
</syntaxhighlight>

===IF USING NO HSM:===
<code>$ dfx identity import node_operator node_operator_private_key.pem --storage-mode=plaintext

$ dfx canister --network ic --identity node_operator call rwlgt-iiaaa-aaaaa-aaaaa-cai remove_node_directly '(record { node_id = principal "NODE_ID" })'</code>

===When the node is ready to be re-registered:===
*If it was healthy, has had no problems, and does not need firmware or anything else updated, then simply re-insert the HSM and reboot the server, and it will rejoin with the same node ID principal it was deployed with.
*If it had problems, had hardware replaced, had firmware updated, etc., then please do a fresh redeployment.

[[Node Provider Documentation|Return to Node Provider Documentation]]

[[Node Provider Troubleshooting|Return to Node Provider Troubleshooting]]

Node Provider Reward Configuration Guide

2024-03-19T15:45:07Z

Malith: Adding important notice for node_count parameter to account for previous node allocation or node operator record

After onboarding all your nodes, you must submit a reward configuration proposal in order to start receiving node rewards. If you do not do this, you will not receive node rewards.

In the next code block:

*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6 from the [[Node Provider Onboarding]]).
*Replace the <code>NODE_OPERATOR_PRINCIPAL</code> value with your node operator principal (step 7.1 from the [[Node Provider Onboarding]]).
*Replace <code>NODE_1_MACHINE_ID</code>, <code>NODE_2_MACHINE_ID</code> ... <code>NODE_N_MACHINE_ID</code> with the node machine IDs for all N of your node machines (found on the [https://dashboard.internetcomputer.org/ dashboard])
*Replace <code>NODE_COUNT</code> with the number of nodes you are setting a reward configuration for. *Important : ''If you adding nodes to a previous node allocation or updating previous node operator record you have to make sure the total node count should be accounted for'' <code>NODE_COUNT</code> ''parameter''
1. Create the proposal<syntaxhighlight lang="shell">
$ NEURON_ID = XXXXXXXXXXXXXXXXXXXX
$ NODE_OPERATOR_PRINCIPAL = xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-update-node-operator-config \
--proposer $NEURON_ID \
--summary "Set rewards for the following nodes:

* NODE_1_MACHINE_ID
* NODE_2_MACHINE_ID
* ...
* NODE_N_MACHINE_ID
" \
--node-operator-id $NODE_OPERATOR_PRINCIPAL \
--rewardable-nodes '{"type3.1": NODE_COUNT}'
</syntaxhighlight>

The default reward configuration for gen2 nodes is <code>type3.1</code>. If a different node configuration is applicable to your node models, replace this value.

Example reward configuration proposal for 3 gen2 nodes:
<syntaxhighlight lang="shell">
$ NEURON_ID = 13419667327548602649
$ NODE_OPERATOR_PRINCIPAL = uqquy-76uhn-2mys5-dh54e-85ntr-sr953-redif-zkte3-94ndi-st2i1-93t
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-update-node-operator-config \
--proposer $NEURON_ID \
--summary "Set rewards for the following nodes:

* sed94-atzdo-rltqy-tmnhr-fvspg-fat3p-sdbjp-7q3jg-dgfcq-zrlap-cqe
* uq4uy-76uhn-2mys5-dh54e-85ntr-sr953-redif-zkte3-94ndi-st2i1-93t-sdjsl-vjlfn-6duch-vskdu-26pf5-cwibg-zooqk-sdn2e-cgugm-tae
* 39esy-hmrb2-nfvao-t42co-tqfed-y3i7c-xqxyp-idt2w-wgmgr-l4x7l-gae
" \
--node-operator-id $NODE_OPERATOR_PRINCIPAL \
--rewardable-nodes '{"type3.1": 3}'
</syntaxhighlight>

2. Find the proposal on <nowiki>https://dashboard.internetcomputer.org/governance</nowiki> and wait until it's executed.

3. In order to expedite the speed of your proposal's approval, it is best to create a post in this forum thread to raise awareness of your proposal.

File:Server invoice geodd.pdf

2024-02-07T03:40:18Z

Malith:

File:Board resolution for Loan.pdf

2024-02-07T03:38:57Z

Malith: Board resolution for acquiring credit facility to deploy new servers to ICP given by community approval in August 2023.

== Summary ==
Board resolution for acquiring credit facility to deploy new servers to ICP given by community approval in August 2023.

File:Bank Letter.pdf

2024-02-07T03:37:40Z

Malith: Letter from bank mentioning that credit facility was undertaking as per board resolution to deploy new servers to ICP and has been approved

== Summary ==
Letter from bank mentioning that credit facility was undertaking as per board resolution to deploy new servers to ICP and has been approved

Geodd Pvt Ltd

2024-01-25T03:57:08Z

Malith: Update / Remove SEO crawling on private data

==Identity Proof==

'''Company Type:''' Limited Liability

'''Regulator:''' Department of the Registrar of Companies (DRC)

'''Sri Lankan Business Registration Number:''' PV00276344

'''Sri Lankan Company Tax Identification Number :''' 103565030

==Company Registration==

'''SHA256:''' 7721d1fbd02ee25e444448b9d2e287d09099965e7e72957674b4e829afadf78a

For company verification purposes, please proceed by scanning the provided QR code.
[[File:Business Registration True Copy.pdf|888x888px|alt=|center]]

==Company Verification==

To ensure total transparency, I've also attached a certified verification PDF. Please feel free to scan the QR code or use the embedded links to view the up-to-date information about our active directors.

'''SHA256:''' 8aabbdfe7530f6234fd28248bd10b422727df4a8063a2bdfaf6e3db2a021c25c

[[File:Certified Verification.pdf|848x848px]]

==Self-declaration==
'''SHA256:''' 8db4231dfadf5ba266ab441caf43ae28b8a3294e880ea6e804159885d1384c1f

[[File:Self Declaration ICP.pdf|alt=|776x776px|Icaria Systems Pty Ltd - Node Provider Self-declaration (ESIGNED).pdf]]

Node Provider Matrix channel

2024-01-12T13:37:43Z

Malith: Adding Geodd Contact Details

There is an open Matrix room (channel) that is intended to be a forum for potential and existing Node Providers as well as anybody else who would like to follow the node provider discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org

The runs runs on the open, public, and decentralized Matrix network. Matrix [https://matrix.org/clients/ has many clients] you can use. One of the popular clients is element.io, which is very similar to Slack, and offers a web UI, a [https://element.io/download desktop app], and a mobile app.

We strongly recommend that you add [https://ems-docs.element.io/books/element-cloud-documentation/page/element-settings an email address in the Element Profile settings] and to [https://element.io/help#settings3 enable notifications for missed messages].

If you are a Node Provider, please also add your Node Provider contact details on the Matrix room, to facilitate communication.
{| class="wikitable"
|+
!Node Provider Name
!Node Provider Id
!DC list
!Matrix aliases
|-
|1G
|7k7b7-4pzhf-aivy6-y654t-uqyup-2auiz-ew2cm-4qkl4-nsl4v-bul5k-5qe
|fm1
|
|-
|43rd Big Idea Films
|sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe
|hu1
|John Harris
|-
|87m Neuron, LLC
|eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe
|pl1, dl1, lv1
|
|-
|9Yards Capital
|spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe
|jv1, ch2, ny1
|
|-
|ACCUSET SOLUTIONS
|cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe
|gn1
|sagcryptoicp
|-
|Adam Dymecki
|n32q7-33lmk-m33tr-o5ltb-po6cb-tqqrr-2x6wp-pzhw7-ymizu-o3fyp-sqe
|
|
|-
|A Dog's Boutique, LLC
|uvawj-nnt3i-4ch3a-hruy4-hyfjn-7owvl-wgkli-uq2hd-e6lkq-v4b2o-4ae
|
|
|-
|Allusion
|rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae
|an1, br1, br2
|<nowiki>Paul De Cannière (Allusion), Roald | Aviate Labs, Louise Velayo | Aviate Labs</nowiki>
|-
|Anonstake
|kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae
|
|
|-
|ANYPOINT PTY LTD
|fwnmn-zn7yt-5jaia-fkxlr-dzwyu-keguq-npfxq-mc72w-exeae-n5thj-oae
|
|
|-
|Archery Blockchain SCSp
|7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe
|
|
|-
|Arjay LLC
|l2kri-jarwr-7whc4-pjdpn-n6hlb-45ltr-l6ghm-twttl-pcsvt-rynko-dqe
|
|
|-
|Artem Horodyskyi
|diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe
|bt1, li1, ma1, pa2, rg3, ta2, wy1
|ar-111
|-
|Aspire Properties
|2byzn-q2crt-hgczo-eruff-6p7af-pemor-n2z4z-6d2sd-wvdqa-yqvxb-mqe
|
|
|-
|Bigger Capital
|7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe
|me3, aw1
|Dallas W
|-
|Bitmoon
|mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe
|
|
|-
|Blockchain Development Labs
|7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae
|
|
|-
|BlockTech Ventures, LLC
|ks7ow-zvs7i-ratdk-azq34-zio2b-gbekj-qjicg-pfhp3-ovhgu-k5qql-dae
|
|
|-
|BLP22, LLC
|sma3p-ivkif-hz7nu-ngmvq-ibnjg-nubke-zf6gh-wbnfc-2dlng-l3die-zqe
|
|
|-
|Bohatyrov Volodymyr
|dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae
|bn1,ba1,ma1,rg3,si1,ta1,wa2
|volobo
|-
|Boolean Bit, LLC
|qdj4d-76lh3-w2q5i-kwjcd-643pq-pk42d-cziag-4hkau-35gib-m7s33-6qe
|
|
|-
|Brener, Inc.
|2wxxr-qwylo-n7dhz-6co6m-iektd-vl7dn-ocvyc-xazaf-hbfxq-66spe-aae
|
|
|-
|Conic Ventures
|i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe
|ns1, ld1
|Sebastian Mengwall
|-
|Coplus Limited
|jz47c-irtey-dr2nb-wienh-emhaz-jo6ua-gsbho-t2z5j-l7kbf-5i7p5-5ae
|
|
|-
|CRM52 Systems, LLC
|7nxxb-6qgm4-fftx3-xkwpj-sjrcm-tzmk5-dvuqk-l4ei4-3hvii-scwnj-tae
|
|
|-
|DFINITY Operations SA
|bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe
|mr1, sh1, zh2
| Katie Peters, sasa-tomic, Sven Fischer, eerokelly, garym-dfn, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O, tthebst
|-
|DFINITY USA Research LLC
|lq5ra-f4ibl-t7wpy-hennc-m4eb7-tnfxe-eorgd-onpsl-wervo-7chjj-6qe
|
| Katie Peters, sasa-tomic, Sven Fischer, eerokelly, garym-dfn, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O, tthebst
|-
|DFINITY USA Research LLC
|r2qgy-abcek-yc2ot-3powq-gayr6-4dibc-jvvfl-ri376-gmfmw-u2v7w-4qe
|bo1
| Katie Peters, sasa-tomic, Sven Fischer, eerokelly, garym-dfn, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O, tthebst
|-
|DRMxTech Enterprises, LLC
|olgti-2hegv-ya7pd-ky2wt-of57j-tzs6q-ydrpy-hdxyy-cjnwx-ox5t4-3qe
|
|
|-
|Exaion
|xo7ih-nswlt-hbq3n-v5ixi-etu7j-sasg6-fjf4p-zx6or-cc7c3-pnh7t-2ae
|
|
|-
|Fidgitville Ventures LLC
|ob633-g55bt-y6pu5-5iby6-jmcvi-oylqs-q6ahw-cvecq-5ckeh-m4wws-nae
|
|
|-
|Finteck LLC
|x3zyd-pkcbf-5n3w2-n7uov-2qrbt-d3kfn-ojdd7-pxog5-vpqnt-6lex5-fqe
|
|
|-
|Fractal Labs AG
|wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae
|
|
|-
|Fritz Huie
|67gkg-gkgzz-g2ubz-3cc6h-jr3zm-twsii-7i325-r3gzr-kp2kh-dwxg6-pqe
|
|
|-
|FUM Capital, LLC
|zgupw-boshs-mg6kz-2ciwm-upk7g-igjpn-75t3p-np6g4-47l7q-nuefa-6qe
|
|
|-
|Geodd Pvt Ltd
|eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe
|cm1
|@malithh
|-
|GeoNodes LLC
|5wedd-dwi2c-ybr2g-benav-qlgc7-vifbt-qz3ml-ymopp-uaide-ilpkb-tae
|
|
|-
|George Bassadone
|lksfo-j2smg-76m4c-jwasz-e5exl-gptsk-jvtc7-zvm34-ezk4g-p2xjt-dqe
|
|
|-
|Giant Leaf, LLC
|wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae
|
|
|-
|Goat, LLC
|p6fou-ngmgk-rxc6t-7ckzz-hojr2-kk6r3-xnlrk-ewzvu-g6xms-rfafz-zae
|
|
|-
|Goodsir, LLC
|myrs2-bc6j6-mydpr-2jmli-l45mu-35ybt-c34mo-kjpve-zmaao-ajusy-nqe
|
|
|-
|Honeycomb Capital (Pty) Ltd
|nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae
|
|honeycombcapital
|-
|Iancu Aurel
|i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae
|
|
|-
|Icaria Systems Pty Ltd
|ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe
|mn2
| Icarus
|-
|IC Pros
|srga3-cikqa-srnxx-rwejf-672jj-5o6qy-tuzsa-khds3-2ofjw-5gnew-mae
|
|
|-
|Illusions In Art (Pty) Ltd
|optdi-nwa4m-hly3k-6ua4n-sqyxf-yahvb-wps77-ddayn-r7zcz-edla5-7qe
|
|
|-
|InfoObjects
|7ws2n-wqorv-vmo4m-5e222-n42c3-hk43s-ei3kp-4hpbn-xlkzo-jgv7i-tqe
|
|
|-
|Internet Computer Explorer
|i7v7g-cwjtl-gzd2s-nt2ko-4d5su-vh64h-bqu4h-rio26-tbaej-dtj6d-fae
|
|
|-
|Ivanov Oleksandr
|ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae
|pa1,ma1, bt1, rg1, wy1, li1, ta2
|alexnod
|-
|Jeffrey Schnettler
|5zqo2-omblo-i7knq-qyrfu-mjccn-tljyd-qslab-b7ukn-7tshi-pbeke-pae
|
|
|-
|Jimmy Quach
|dzxyh-fo4sw-pxckk-kwqvc-xjten-3yqon-fm62b-2hz4s-raa4g-jzczg-iqe
|
|
|-
|Jonathan Ziskind
|qcs4o-yswwp-7ozhg-m2ago-ytjyl-zlckb-raykw-fi5hl-cflyt-4beyv-zqe
|
|
|-
|Joseph Stella
|f5wg2-kl4aq-cj4ym-nq7ul-i4kxy-t4x3x-yiyc5-3wlu6-opzwd-o5qes-hae
|
|
|-
|Karel Frank
|unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe
|jb1, jb2, sc1
|lerak
|-
|KLAW Media, LLC
|pcwis-xaq3p-xvasz-5cfws-oelni-xs72v-acbwz-umxnq-nb2bc-ziyuu-sqe
|
|
|-
|Kontrapunt (Pty) Ltd
|py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe
|
|
|-
|Krishna Enterprises
|zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae
|
|
|-
|Krishna Sriram
|sajvr-l5iok-rj6c2-r76co-k2mde-d3kir-pnmjs-443f6-lxto4-pu55q-uae
|
|
|-
|Lauren Dymecki Chickvara
|abscc-3lezh-oezci-5i3kz-pkwlc-ozz3r-5wv4n-htujn-rtajh-6cgyv-jae
|
|
|-
|Lukas Helebrandt
|efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe
|bn1
|@lukas:greensteps.cn
|-
|Luke Jacobson
|6dwst-olsa5-tagsr-jylgj-oicju-rf42e-o7job-gedre-fgoxt-7br62-jqe
|
|
|-
|Maksym Ishchenko
|4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae
|bn1,ma2,bt1,rg1, wa1,ba1,ta1
|77676m
|-
|Marc Johnson
|xfvlz-qkgs4-xyeyx-lbke5-aarza-ovi52-wzpxl-3p27l-ov6ki-csxv6-qqe
|pr1

es1

NZ1
|@mj518
|-
|Marvelous Web3
|7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe
|
|
|-
|Mary Ren
|vdzyg-amckj-thvl5-bsn52-2elzd-drgii-ryh4c-izba3-xaehb-sohtd-aae
|
|
|-
|MB Patrankos šūvis
|4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae
|
|
|-
|Mika Properties, LLC
|3siog-htc6j-ed3wz-sguhu-2objz-g5qct-npoma-t3wwt-bd6wy-chwsi-4ae
|
|
|-
|MI Servers
|izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe
|
|
|-
|Mitchel Guerra
|4anlt-yam7x-eodmx-ik7mo-nl3kx-t35fj-52hfy-uv4jj-u2iea-ntg76-pqe
|
|
|-
|Moon Block Ventures
|sdal5-w2c3d-p3buy-zieck-2wyuj-eu5bn-rkfe6-uuspi-o4n2b-gpei7-iae
|
|
|-
|Mostly Wholesome, Inc.
|ou3o7-akyjc-ldwd5-anyjn-l2buz-cwhbg-nehlc-abkde-qtc7w-fozdi-hae
|
|
|-
|Neptune Partners
|4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae
|
|
|-
|NoviSystems, LLC
|hk7eo-22zam-kqmsx-dtfbj-k5i6f-jg65h-micpf-2cztc-t2eqk-efgvx-vqe
|ny2, fm1
|novisystems
|-
|OneSixtyTwo Digital Capital
|6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe
|
|
|-
|Origin Game
|cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe
|
|
|-
|Palnu_Logistics
|pfcmh-uqedc-ijkjz-mdo35-bvprd-2vtlw-ktod5-npgfc-pgbq4-akaen-uqe
|
|
|-
|Paul Legato
|yr4eg-kwk3m-q44vj-ale35-2mtxk-5dyn7-vgppx-z6tcw-kzo4o-ezpm5-fqe
|
|
|-
|Peggy Shafaghi
|72idx-a7c3y-nrcwc-lboj4-mmsas-sfdpm-gq23i-h2yuy-lykcj-vrxn2-jqe
|
|
|-
|Philippe Chapparone
|2c4m6-25hos-qroi3-mk4aj-nog6s-zbzcv-ccpcc-cbv7s-sjy6p-bv3g5-fae
|
|
|-
|Pindar Technology Limited
|r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae
|
|Robert Song, alexa-zhang410, Miles Million
|-
|Power Meta Corporation
|4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae
|
|
|-
|Prayit Jain
|waj5k-wlyvv-jbj4n-vxwjm-dmkyg-uw2nl-ggojp-34kln-wgx3n-d7xih-5qe
|
|
|-
|Privoxy Solutions, LLC
|trxbq-wy5xi-3y27q-bkpaf-mhi2m-puexs-yatgt-nhwiy-dh6jy-rolw5-zqe
|
|privoxy (@privoxy:matrix.org)
|-
|Rachel Dymecki
|chnsu-yaqt5-6osy5-au4zn-li6yu-nufmw-dewrt-utkiu-twd76-ujypw-rae
|
|
|-
|Richard Ma
|egb3e-rzi2e-vpsmm-akysp-l2owk-4dgst-b5hmg-xrkwa-cr3uk-zlzds-mae
|
|
|-
|Richard Suarez
|cmcjw-6c5ve-4zjnt-lipnl-2lp43-oh5wk-ewciz-xyvnv-m2rz5-hkm6a-hqe
|
|
|-
|Ricky Sidhu
|q22bo-3uyqa-jvtpt-gapjk-pseor-esx4a-zyb74-vzea4-o7nx2-tafgq-hae
|
|
|-
|Rishi Sachdev
|6tg64-cdfoh-kl35i-p6qti-sose3-746lr-jk5ex-phuvu-jfu3d-5svwa-7qe
|
|
|-
|Rivram Inc
|ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae
|nm1,mtl1
|@ritvick
|-
|Rodney Zorrilla
|bgprp-b2mnt-ci5in-57vuk-p7qvo-tj2tb-5w5su-qwenk-gbe77-mnuiq-sqe
|
|
|-
|Ronnie Pellizzari
|wwxec-c2gd2-bu5on-ktpwz-z2ph3-vlr4p-m7ztf-6ck7r-nt3r4-fxbdq-mae
|
|
|-
|Russell Ford
|p5jx4-lsrog-ep5o3-5uudg-opdg3-ur45z-xeefi-4ejfz-47t2k-riwfv-dae
|
|
|-
|Scott Hallock
|i6sxi-fks25-viets-mboa7-3i23b-qeocf-e57qj-ar6vy-2mchu-xb5vp-aqe
|
|
|-
|Shelburne Ventures, LLC
|a24zv-2ndbz-hqogc-ev63f-qxnpb-7ramd-usexl-ennaq-4om4k-sod6u-gae
|
|
|-
|Staking Facilities
|niw4y-easue-l3qvz-sozsi-tfkvb-cxcx6-pzslg-5dqld-ooudp-hsuui-xae
|
|
|-
|Starbase
|sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae
|
|
|-
|Starseed Technology, LLC
|ruxoj-jnqql-uau6o-xwrtb-ufde4-geddn-mnhni-wpew4-zhzi5-xjrxi-lqe
|
|
|-
|Sygnum Bank
|6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe
|
|
|-
|Tomahawk.vc
|ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae
|
|
|-
|Virtual Hive Ltd
|wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae
|fr2
|Chris B
|-
|Vladyslav Popov
|3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae
|pa2,ma2,si1,rg1, wy1,li1,ta2
|vladyslav_p
|-
|Wancloud limited
|g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe
|hk1
|<nowiki>hashbamboo | HashQuark, Daniel | HashQuark</nowiki>
|-
|Web3game
|64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe
|
|
|-
|William Zelver
|usau7-upgoh-sg464-6qnso-lud42-nxho6-ith26-a2jhq-q5bgy-ajeou-4ae
|
|
|-
|Wolfhound LLC
|6mifr-stcqy-w5pzr-qpijh-jopft-p6jl3-n2sww-jhmzg-uzknn-hte4m-pae
|
|
|-
|Wolkboer (Pty) Ltd
|mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae
|jb3
|wolkboer
|-
|Zondax AG
|hzqcb-iiagd-4erjo-qn7rq-syqro-zztl6-cpble-atnkd-2c6bg-bxjoa-qae
|
|
|-
|ZTLC PTE LTD
|xsrwt-tl3tk-n3aya-rafh3-ta6xu-eviw5-ae5dg-2f3bf-siaab-wdwdo-dqe
|
|
|}

Geodd Pvt Ltd

2023-06-06T04:48:50Z

Malith: Update alignment issue

==Identity Proof==

'''Company Name:''' Geodd Pvt Ltd

'''Company Type:''' Limited Liability

'''Regulator:''' Department of the Registrar of Companies (DRC)

'''Sri Lankan Business Registration Number:''' PV00276344

'''Sri Lankan Company Tax Identification Number :''' 103565030

==Company Registration==

'''Name:''' Geodd Pvt Ltd - Company Registration True Copy.pdf

'''SHA256:''' 7721d1fbd02ee25e444448b9d2e287d09099965e7e72957674b4e829afadf78a

For company verification purposes, please proceed by scanning the provided QR code.
[[File:Business Registration True Copy.pdf|888x888px|alt=|center]]

==Company Verification==

To ensure total transparency, I've also attached a certified verification PDF. Please feel free to scan the QR code or use the embedded links to view the up-to-date information about our active directors.

'''SHA256:''' 8aabbdfe7530f6234fd28248bd10b422727df4a8063a2bdfaf6e3db2a021c25c

[[File:Certified Verification.pdf|848x848px]]

==Self-declaration==

'''Name:''' Geodd Pvt Ltd - Node Provider Self-declaration (ESIGNED).pdf

'''SHA256:''' 8db4231dfadf5ba266ab441caf43ae28b8a3294e880ea6e804159885d1384c1f

[[File:Self Declaration ICP.pdf|alt=|776x776px|Icaria Systems Pty Ltd - Node Provider Self-declaration (ESIGNED).pdf]]

Geodd Pvt Ltd

2023-06-05T08:49:45Z

Malith: Node Provider Declaration and Verification Page

==Identity Proof==

'''Company Name:''' Geodd Pvt Ltd

'''Company Type:''' Limited Liability

'''Regulator:''' Department of the Registrar of Companies (DRC)

'''Sri Lankan Business Registration Number:''' PV00276344

'''Sri Lankan Company Tax Identification Number :''' 103565030

==Company Registration==

'''Name:''' Geodd Pvt Ltd - Company Registration True Copy.pdf

'''SHA256:''' 7721d1fbd02ee25e444448b9d2e287d09099965e7e72957674b4e829afadf78a

For company verification purposes, please proceed by scanning the provided QR code.
[[File:Business Registration True Copy.pdf|left|888x888px]]

To ensure total transparency, I've also attached a certified verification PDF. Please feel free to scan the QR code or use the embedded links to view the up-to-date information about our active directors.

'''SHA256:''' 8aabbdfe7530f6234fd28248bd10b422727df4a8063a2bdfaf6e3db2a021c25c

[[File:Certified Verification.pdf|848x848px]]

==Self-declaration==

'''Name:''' Geodd Pvt Ltd - Node Provider Self-declaration (ESIGNED).pdf

'''SHA256:''' 8db4231dfadf5ba266ab441caf43ae28b8a3294e880ea6e804159885d1384c1f

[[File:Self Declaration ICP.pdf|alt=|776x776px|Icaria Systems Pty Ltd - Node Provider Self-declaration (ESIGNED).pdf]]

Node Provider Self Declarations

2023-06-05T08:19:02Z

Malith: Adding Geodd Pvt Self Declaration Page

==== Node Provider Self Declarations ====
[[Geodd Pvt Ltd]]

[[Rivram Inc]]

[[InfoObjects Inc]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[PindarTechnologyLimited]]

[[Karel Frank]]

[[Icaria_Systems_Pty_Ltd]]

[[Lukas Helebrandt]]

[[Exaion]]

[[User:James Wang|HashQuark]]

[[Marvelous Web3]]

[[HoneyComb Capital]]

[[6673171 Canada Inc]]

File:Certified Verification.pdf

2023-06-02T03:19:56Z

Malith: Use the links in the PDF to view the current directors of Geodd Pvt Ltd. This file is verified and uploaded in the government website

== Summary ==
Use the links in the PDF to view the current directors of Geodd Pvt Ltd. This file is verified and uploaded in the government website

File:Business Registration True Copy.pdf

2023-06-02T03:17:42Z

Malith: Business Registration Geodd

== Summary ==
Business Registration Geodd

File:Self Declaration ICP.pdf

2023-06-02T03:16:40Z

Malith: Self Declaration Geodd Pvt Ltd

== Summary ==
Self Declaration Geodd Pvt Ltd