---
title: "Discussion on \"A Kava validator on my existing stack — how the plan came together, and what the second chain will do differently\" | Hashnode"
description: "Discussion on \"A Kava validator on my existing stack — how the plan came together, and what the second chain will do differently\". Most validator writeups skip the money question. This one starts there — why Kava, and what 28 days running it taught me before chain two."
url: "https://hashnode.com/posts/kava-validator-existing-stack/6a6bb0af34196aba1cd85aea"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A Kava validator on my existing stack — how the plan came together, and what the second chain will do differently](https://jjozzietech.hashnode.dev/kava-validator-existing-stack?utm_source=hashnode&utm_medium=feed)

Most validator writeups skip the money question. This one starts there — why Kava, and what 28 days running it taught me before chain two.

Jul 30 · 17 min read · jjozzietech.hashnode.dev  
Read the article

-   [#homelab](https://hashnode.com/tag/homelab)
-   [#validator](https://hashnode.com/tag/validator)
-   [#kava](https://hashnode.com/tag/kava)
-   [#cosmos](https://hashnode.com/tag/cosmos)
-   [#horcrux](https://hashnode.com/tag/horcrux)
-   [#threshold-signing](https://hashnode.com/tag/threshold-signing)
-   [#depin](https://hashnode.com/tag/depin)
-   [#ha](https://hashnode.com/tag/ha)

## Written by

[JJozzieTech](https://hashnode.com/@jjozzietech)

@jjozzietech · Sydney, Australia

  
[View profile](https://hashnode.com/@jjozzietech)

Enterprise lab. Sydney rack. I write about what actually breaks.

Sydney-based infrastructure operator. Enterpriselab, DePIN workloads, and the incident logs behind them. I write about what actually breaks.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
