#Nov 14 Namada Validator Circle ๐ก
1 messages ยท Page 1 of 1 (latest)
Hello hello
๐
GM DRY RUN COSMONAUTS
Hi
๐
hey hey! things are looking pretty good, eh
๐
Hey hey!
Howdy guys ๐ค
Hello guys

Hi all
Hello ๐
๐
๐
Hi everyone ๐
Yo ๐!
Hello!
From Devcon with luv 
i swear we had several people warning us that this wouldn't work. tbh i think what makes it work is that active stakers delegate to active validators, and these are the best folks to launch a chain
What are thoughts on dry-run so far?'
Very smooth.
anyone else get excited to see this secret menu?
https://interface.namada-dryrun.tududes.com/settings/features
One of best I've seen. From my end, no issues.
Hey all
Transfer ?
I agree
oh! if you're happy with how that went, pls tweet about it! it signals operational confidence ๐
of course it's gated by the chain phase of the Dry Run, but exciting to see
In the next hour (maybe after this session), I'll put the phase 3 proposal on-chain - looks like there were no objections to my proposal on the forum
We should collect the pain points if there are any and try to smooth them out for mainnet.
Cool ๐. . . . I'm enjoying the dry run, going smoothly for me
i started collecting some. i think we could make a forum topic for this
Someone should sacrifice and get slashed, just to make sure slashing is also working properly ๐
๐
๐
Actually a good idea
I think whoever suggested it will test it ))))๐
Definitely.
- A FAQ for things like a missing CometBFT installation
- Best practices for key management
- Different ways to fund validator transactions
- A guide for verifying the proposal
...
I have the question. How people get the signing info from the chain without metric from grafana
Most people are facing problems related to basic steps. .. I believe. Such as setting up the wallets and nodes with cometbft
okay that's good to know. why are people having these problems?
Exactly. The wallet thing was a bit tricky, since you have to copy over validator-wallet.toml to the remote server, but there you do not have the keypair to sign the transactions. And from a security point of view, one should not do that on the remote server. Instead, the validator-wallet.toml has to be imported to a secure local machine, probably the one used to create the pre-genesis files in the first place.
On a secure local machine, you will need the pre-genesis wallet.toml in ~/.local/share/namada/pre-genesis/ and validator-wallet.toml in ~/.local/share/namada/pre-genesis/$VALIDATOR_ALIAS/.
Then execute namadac utils join-network --chain-id $CHAIN_ID --genesis-validator $VALIDATOR_ALIAS
Moving the keys from one server to another. Not setting up cometbft properly and not adding the peers
Cometbft does automatically install if one builds from source (make install). Perhaps that portion that gets called could be made more readily available (I believe it's just a script that gets called).
i'm not an experienced operator. should this be heavily flagged in the docs? guides?
is there an additional way that this could be mitigated?
I think that would be super helpful. The steps could be added to a hackmd.io mainnet launch instruction page.
And loved the idea about the dry-run
@river shadow, we should emphasize this in the guide and in docs
๐
Also in the official doc
I agree, that's very good to have this test.
are there tools that would make this better for mainnet?
There might be edge cases, like a validator who removed the original pre-genesis folder. Then the wallet.toml and validator-wallet.toml have to be restored from a backup or seed phrase.
A script that verifies everything is setup and on the correct version might be helpful for some. This script would assume default directories and if you do something more bespoke, that would not be covered.
The script @night ocean has developped could help for a basic check. (namada & cometbft version...)
Maybe we could find some other elements to add to it if needed/relevant?
This is the checker from Andrei I'm talking about:
https://gist.github.com/andreidavid/82cb0d26650e94709c4f0fc45e5b64e5
@sly mango wdyt?
I am a bit concerned about the more bespoke situations (looking at myself ๐ renaming the pre-genesis folder), but maybe I was the only weird one.
Namada wallet for mobiles will be awesome,
I like the idea of having a simple script to check on vali configs for launch
Happy to add new checks/features if required ๐
Can we have a tally of operators who faced non-standard situations / other problems so far?
I'm also playing around with a Namadillo instance that has the features ungated based on the chain. (off topic rn)
I'm going to sling it up on the TuDudes instance
can folks let Andrei know what may be helpful to add?
Add support for docker and the ability to set custom directories so that all users can use it, regardless of their setup.
I only had a small problem with staking or voting via the interface, but then realized I was on the wrong URL (interface.namada.tududes instead of interface.namada-dryrun.tududes) ๐ .
So if anyone hits that problem, double check the link lol.
I remember there was an issue with voting via binary on CLI while using the alias.
What will be the mainnet URL?
perhaps I redirect that one to dry run for now as campfire is on the backburner (no pun intended)
Oh yeah, that also. The sig < 1 thingy? Was that remedied by pasting the entire address instead of alias?
If everything goes well on the dry run, then Mainnet? I want to learn more about the timeline and planning ๐.
Which is actually a bug isn't it? As I do remember during SE that we were able to use aliases when voting with a delegator address.
Can we recover the exact specifics of the issue - sounds new to me?
I personally voted yesterday from the CLI with a delegator using my alias with no problem at all
The script starts from the service definition and tries to infer the setup from that config, so depending on the custom changes it should still work
Core configuration - only this section needs manual updating
SERVICE_FILE="/etc/systemd/system/namada_dryrun.service"
Speaking of URLs, might be worth reminding DNS is an attack surface, like DNS spoofing and redirecting to a malicious clone of the website that drains wallets. Happens too often in crypto. There are ways to mitigate such attacks, like DNSSEC.
I had not problem at all, but when we did with @ripe jackal's address, it barked, but he was able to get it done via interface.
ohh yeah, @cosmic pendant i also had the same issue
@sly mango wrong url!
@ripe jackal correct me if I'm forgetting the details
Can we create a Google table and post there when an error occurs?
yes, I had the wrong URL 
going to do this
i think we should wait until we have gone through the phases before honing in on a launch date
โโโโโโโโBA
Guys, if we want to figure out an issue like the proposal voting with alias, we need to provide ALL relevant details needed to reproduce an issue. Show all commands run, all their outputs, and the outputs of extra commands that would give important context (like namadaw list in this case). Plus , pls make a github issue about it!!!
Just showing a single error string without any other info doesn't help anyone understand the exact steps taken to get there @cosmic pendant @sly mango
Hmm, we should try again when the proposal for phase 3 starts and see if using the alias still doesn't work with voting. And if using the entire address does. I myself haven't tested that part.
Yeah apologies, understood.
Spork has opened an IBC channel to mainnet Osmosis, and Sirouk / TuDudes are setting up another relayer to support
if anyone else is up for helping support, we can make a thread to coordinate in #archived-dry-run-chatter
Is that about the 0 out of 1 signatures found thing? That I think could be solved by setting up the validator account locally as I described earlier in this circle.
@modest knot how are things going with the Ledger app? (they are like two weeks past Zondax's Oct 30 prediction)
That would be caused by the lack of the validator keypair when only importing validator-wallet.toml on a remote server. It is a sign that one is attempting to run validator commands remotely, which is risky anyway.
We will cover that in a guide.
We also support it since yesterday. If anyone wants to support relaying take into account that for relayer address a genesis address with balance would be needed โ๏ธ
once the rate limits for OSMO are increased..
๐จ do not send more OSMO to Dry Run than you are willing to lose ๐จ
I'm not so sure if this is the same. I couldn't vote with addresses I used to make prebonds with (using just the alias). Even tried to reimport them using my mnemonic phrases.
in this case @ripe jackal was voting with his delegator address, with his explicit wallet alias used for signing
In other words, veight was attempting to vote from the wallet he used to bond pre-genesis to our validator
@modest knot are there any Namada protocol updates you think may be coming before mainnet?
if there isn't anything further, i think we can call it here
excited for the next phase ๐ ๐
great chatting, see y'all in #archived-dry-run-chatter ๐