Skip to content Search Apps Documentation Source Content Run Reset Eval Playground File Folder Download Copy Actions State String Boolean Number Struct Map Slice Pointer Function Closure Reference Nil Package Type Interface Unknown

Valoper's details:

Encapsulate

Validator infrastructure for new chains, since 2020. Early to testnet, quick to upgrade, easy to reach. Trusted by Sui, NEAR, Monad, Lido, Starknet and more.

Networks we validate: Ethereum, Sui, Monad, NEAR, Avalanche, EigenLayer, Axelar, Zilliqa, Mina, Starknet and 18 others — full list

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

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/g1eyr3hfdcup4rr5xlcd63vc5t64a03u9kecx2v0/forms
  • gnolang/gno#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 — gno-select cannot set its visible label.
  • 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.

Profile link