Encapsulate

On-chain profile

Backed by five years of operating experience, Encapsulate secures 28 networks and $70M+ in delegated stake, delivering high uptime, rigorous key management, and open-source tooling for the validator community. **Networks we validate:** Ethereum, Sui, Monad, NEAR, Avalanche, EigenLayer, Axelar, Zilliqa, Mina, Starknet and 18 others — [full list](https://encapsulate.xyz) **Digital presence** * Website: https://encapsulate.xyz * X: https://x.com/encapHQ * GitHub: https://github.com/encapsulate-xyz * LinkedIn: https://www.linkedin.com/company/encapsulate-xyz * Discord: `kingsuper`, `kowshikvajrala` **Contact** * Email: [email protected] * Telegram: `aditya_encapsulate` **Why we want to validate on gno.land** On most chains we validate, the way in is capital. Here it is building, and every validator has the same vote — that is a set worth joining. Gno suits us too: we have run Go and Cosmos-SDK infrastructure for years, so the language is already familiar. **Contributions** * **gno forms** — a realm that publishes forms and collects responses on chain, with gnoweb as the only UI, so collecting structured input no longer needs a Web2 backend. Live at [/r/nym-encapsulate001/forms](/r/nym-encapsulate001/forms) · [source](https://github.com/encapsulate-xyz/gnoforms) * **[gnolang/gno#6140](https://github.com/gnolang/gno/issues/6140)** — an unticked checkbox in a `gno-form` submits its value regardless, making every boolean parameter unconditionally true. Filed with an on-chain reproduction and a workaround. * **[gnolang/gno#6141](https://github.com/gnolang/gno/issues/6141)** — `gno-select` cannot set its visible label. * **[gnoland-ansible](https://github.com/encapsulate-xyz/gnoland-ansible)** — deploys, upgrades, snapshot-syncs and monitors gno.land nodes with Vault-secured keys. **Planned for gno forms:** more field types (email, checkbox, radio), per-form response numbering, and sealed responses if anyone wants them. Alongside: public endpoints, snapshots and monitoring for gno.land.