Realm
dao:8
Render
Prop #8 - Add valoper moul to the valset
Author: @moul
Valoper profile: moul
moul
moul (Manfred Touron), gno.land contributor since 2022.
-
Validator name: moul
-
Networks and AuM: gno.land only. Ran public full nodes on earlier gno.land networks (betanet, pearl) and currently validating on onyx-1. No assets under management: self-funded and self-operated, not a staking service.
-
Digital presence: https://gno.land/u/moul and https://github.com/moul
-
Contact: already known by the gno.land team.
-
Why validate on gno.land: I have contributed to gno.land since 2022 and run parts of its infrastructure daily. Validating on hardware I own, with the consensus key held in a hardware signer, is the setup I want the network to be able to rely on, and operating it myself is how the operational gaps a cloud node hides get found and fixed.
-
Contributions: long-standing contributor to gnolang/gno, author of developer tooling around it (gnopie, gnoblog, gnohome and others) and of several realms deployed on mainnet, GovDAO T1 member. This validator runs on-premises to help prove out the on-prem validator architecture the team is standardising on, and I report back what breaks.
Setup: on-premises bare metal, Debian 13, consensus key held in a YubiHSM 2 fronted by tmkms, behind a sentry node. The validator accepts no inbound connections from the public network and never dials it.
- Operator Address: g1manfred47kzduec920z88wfr64ylksmdcedlf5
- Signing Address: g1g0yrmdhney8pcaf9rfut4604equz604pszdsyt
- Signing PubKey: gpub1pggj7ard9eg82cjtv4u52epjx56nzwgjyg9zqkwz64dupn9vk4dlm0zy8my8xzysgqulepavucq4kxgxf3djlmt2y0mxr6
- Server Type: on-prem
Validator Updates
- g1manfred47kzduec920z88wfr64ylksmdcedlf5: add (power 1)
Executor created in: gno.land/r/sys/validators/v0
Stats
- PROPOSAL HAS BEEN ACCEPTED
- Tiers eligible to vote: T1, T2, T3
- YES PERCENT: 66.66666666666666%
- NO PERCENT: 0%
- ABSTAIN PERCENT: 0%
Actions
Vote YES | Vote NO | Vote ABSTAIN
WARNING: Please double check transaction data before voting.