Pro-Nodes75 Validator Profile

Hello, Archway community!:wave: My name is Slav. I’m the CEO of Pro-Nodes75 :satellite: validator.

We are happy to join to the Archway community. We will do our best to help Archway chain to prosper.

Entity name and location:

We are Pro-Nodes75:satellite: Validator. Part of our team located in Central Europe, while another - in mid Asia.
Our website.

Infrastructure location:

Our servers located in :de:, :uk:, :poland:, :finland:, :canada:, :singapore:.
We use only dedicated servers, provided by enterprise-grade cloud providers. Besides that, we use few baremetal servers in DC in mid Asia.

Technical make-up of team:

• 2 DevOps Engineers (5+ years of experience). One has PhD in Radio Engineering.
• 1 Backend developer (10+ years of experience in C++, Phyton, Go).

Years of experience:

We’ve been part of the Crypto community since 2017. And we have almost 3 year of experience in validating business. During our operation period we have got not a single slashing event in mainnets. :muscle:

Networks we are you running validators:

We are running mainnet validators for many PoS blockchains. Such as: Archway, Chain4Energy, Composable, Evmos, Forta, Gravity Bridge, Kyve, Konstellation, Mina, Pylons, Solana, Terra, Umee, Uptick.
Overall, we have approximately $3.5M in AUM.

Besides current Mainnets we participated more than 60 different testnets. And currently running more then 15 testnets. Multiple times we were in top 50 in different Incentivized Testnets.

For “fast” blockchains (like Evmos or Defund) we use PebbleDB which helps us to maintain higher uptime.

Security and reliability:

  1. have 2 different sources of alerts for our nodes;
  2. Use AuthZ module for validator’ keys, and dont store it on the validator’ node;
  3. Use a bot for governance alerts to be aware of new proposals;
  4. Validator’ Set up include sentry nodes for ddos protection (which could be used as backup node in case of emergency);
  5. ssh + fai2ban + firewall for secure connection.


We actively participating in governance. Our overall voting rate in mainnets is more than 95%.
For some important or controversial proposals we use following governance framework:

  1. Read relevant discussions at CW or in discord.
  2. Have a discussion among team members.
  3. Discuss proposal within our validator’ community. And trying to understand - is the Proposal good for The chain and for the community, or it’s goals are to get benefits for small group of interests.
  4. Post a feedback at forum, if our questions and concerns haven’t been discussed.
  5. Attend AMA/ Governance meeting with the Project’ team and gove topic’ proposer.
  6. Put our vote onchain.

We prefer not to vote “abstain”. Because in our opinion “abstain” option should be used only in case of conflict interests.

Our contributions in cosmos-ecosystem that we would like to highlight for the community:

We providing IBC relaying service for our mainnets.
We supporting testnets for each chain we validating in.
Besides, we are providing RPC/API endpoints and seed nodes.
We helping to update project’ docs at github, if such a necessity is actual (outdated ibc information/ manuals/ links).
For some projects we provide a public monitoring-dashboards, like for Umee (for Price-feeder monitoring).
We supporting Cosmos ↔ Eth Bridging for Gravity Bridge.
Supporting for our stakers.

We would be glad to provide all our services and skills in favour of Archway prosperity. :rocket:

Twitter : @NSvv28
Discord : SW33 | pro-nodes#0534, shurinoff#5643

Best Regards,
Pro-Nodes75 :satellite: team! :heart: