Jan 23 Namada Validator Circle 🟡

[final wadi]

validators! have a question you've been wanting answered? finding something challenging? have a suggestion? this is the place/time to get these addressed!

[wooden badge]

👋

[pulsar otter]

[karmic bloom]

Good day everyone

[trail nymph]

[karmic bloom]

👋

[neon canopy]

[pallid pasture]

👋

[halcyon drift]

gmgm

[tribal hound]

👋

[unkempt comet]

Hi. guys

[visual yarrow]

👋

[quiet owl]

Shiedmorning

[cunning gazelle]

[terse flame]

👋

[final wadi]

heyy! how goes?

i'm so excited for Phase 3
it's taking longer than expected, but for good reasons. i'm glad that solid folks are on it

[mild echo]

👋

[gusty ice]

Hello everyonee

[halcyon bone]

Hello 🖖

[final wadi]

i think @bronze glade is like 10k meters high, flying over the Pacific ocean somewhere

with an internet connection maybe? 👀

[karmic bloom]

LoL 😅

[finite steeple]

heyloo

[bronze glade]

Hello from a plane!

Hopefully my internet stays alive through this

[mild echo]

Not flying to the moon? 😝

[crisp rock]

Hi all

[bronze glade]

Moon is next stop after Los Angeles lol

[mild echo]

https://www.youtube.com/watch?v=Cd_THG241GA
For everyone to wait for the real start

[trail nymph]

Mars is in trend recently)))

[hexed path]

fly to the mars

[spice vigil]

hi all 🙌

[cunning obsidian]

Shield morning 🫡

[final wadi]

things are looking pretty good for the first post-mainnet software release: https://github.com/anoma/namada/milestone/25

it will be great to get Housefire upgraded

should be a pretty easy upgrade, yeah? nothing that needs governance approval, no migration. just halt, swap binary, resume

this release extends the expiration time for IBC channels by a lot (this way it's much less likely for an ibc channel to expire, leaving an ibc asset stranded)

ALSO, this expands the cap on addresses in a PGF proposal

[sly raptor]

Is there any risk of an infraction?

[final wadi]

happy to be able to make a single proposal w ~200 addresses for the Donor Drop distribution
..instead of, y'know, 10 proposals each with 20 addresses

[gusty ice]

don't think so, but a halt height could be set if I recall to ensure the update is at the same time tho

[bronze glade]

Yeah, in the end there is quite a lot in this release. I'll try to elaborate in a sec. But I think the general plan should be:

1. Upgrade Campfire testnet
2. Coordinate upgrade of Housefire testnet and let that run for a couple days perhaps
3. Coordinate upgrade of mainnet

I also think for this upgrade that we should choose a block height to halt at and upgrade, as @gusty ice suggested

Do we need to do a signalling gov proposal for this?

[final wadi]

i suspect not, but it depends what the changes are

[hollow totem]

👋

[gusty ice]

i think we can agree on a height w/o a gov prop

[final wadi]

do we have a list of changes?

[bronze glade]

Ideally we can agree on a height without a gov proposal - this would expedite things

Giving a list of changes in a sec...

[wooden badge]

The mainnet was launched on a Tuesday, let's keep Tuesday it's a day that brings us luck for the next upgrade !

[final wadi]

after the mainnet software is v1.1.0, what needs to be done before we execute Phase 3? release of the latest Ledger app (enables people use Ledger for shielded transactions, like those who are helping to bootstrap the shielded pool)

[bronze glade]

Here's an overview of what is included in v1.1.0:

• Extends IBC channel trust period related to expiration time (crucial for Phase 3)
• Increases the number of PGF target addresses in a proposal (to do Donor Drop proposal)
• Improves tx result output
• Improves namadac next-epoch-info
• Various MASP improvements needed for Namadillo
  • SDK endpoint for estimating a user's shielded rewards at next MASP epoch boundary
  • better flow for MASP tx building
• State migration improvements
• Offline signing improvements
• A fix for Ledger Nano S devices (allow IBC support in the absence of MASP support, which unfortunately cannot be included for Ledger Nano S only - other devices will have MASP)
• Fix issue related to a validator node that ends up with Namada config tendermint_mode as non-validator mode
• Add a handful of new and useful SDK endpoints
• Fix the recently brought-up redelegation error messages
• Update shielded address derivation in CLI to be compatible with soon-to-be-released Ledger HW updates
• the initial implementation for supporting cross-chain shielded swaps with Osmosis
  • can in principle be done at CLI now
  • team is beginning work on front-end and interface to optimally support this
• Additional testing

[final wadi]

oh! and Namadillo is a big factor, yeah?

also curious to know if we have what we need for infra support

it's funny, everyone talks about Phase 5, but Phase 3 / 4 is huge

[mild echo]

Wow ! Pretty dense update finally 👏 💪

[final wadi]

the most "political" change, imo, is the extended ibc trust period. feels like we're early enough to forego a governance proposal for that now, tho. i could see changing this in the future to need governance

[bronze glade]

So once we are on v1.1.0 on mainnet, the order of operations for getting to Phase 3 as I see it are:

1. Open IBC channels on Housefire testnet
2. Phase 3 proposal on Housefire testnet and do some community testing (I will make forum post at some point with some recommended action items that we can all do)
3. Be satisfied with Phase 3 on Housefire
4. Open IBC channels on mainnet
5. Deploy Phase 3 proposal on mainnet

[sly raptor]

Phase 3 is enormous, and more than once I have lamented that it should maybe have been split into 2 phases. MASP AND IBC at the same time?!

[mild echo]

5. Deploy Phase 3 proposal on mainnet```
Point 4 can be done before point 5? 🤔

[bronze glade]

Yeah in my view, getting to Phase 3 is def the biggest milestone in terms of technical accomplishments. After we are in Phase 3, getting to the remaining phases should be much quicker and smoother. Likely will not require another upgrade to the protocol software. Maye require some smaller additions to Namadillo in between Phase 3 and 4

[final wadi]

great! and Phase 3 proposal specifically is just to increase the IBC rate & mint limits, yeah?
https://github.com/anoma/namada-governance-upgrades/blob/f1d19a5d4d28595ee73fe8fd15a9b4319bb171ff/phase3/src/lib.rs

[bronze glade]

IBC channels are required to be opened before the Phase 3 proposal, since the Phase 3 proposal will hard-code the channel IDs into them, i.e. need to know things like transfer/channel-X/uosmo and things like this

[final wadi]

#1332031162859651083 message

[final wadi]

oh neat, i didn't know this part

[mild echo]

So as soon as we have housefire upgraded, folks can start to work on the channels?

Who is planning to open channels? From and To which chains?

[bronze glade]

I don't think the IBC trust period will need to be changed in the future after this. It was mildly an oversight that we didn't do this before mainnet started

[mild echo]

If you are planning to open channels please let us know as soon as you have the network info.
We have a dedicated json for that on the Namada ecosystem repo:
https://github.com/Luminara-Hub/namada-ecosystem/blob/main/user-and-dev-tools/mainnet/ibc-relayers.json

[bronze glade]

I've chatted with a lot of operators who are planning to relay IBC channels, I'm keeping a spreadsheet that contains a list of each of them and what channels they will run. Assuming everyone who has committed actually does the relaying, we will have plenty of redundancy for all the channels desired in the Phase 3 proposal

There are about 20 IBC relayers committed

[mild echo]

Do not hesitate to let me know if other key/value pairs are needed

[bronze glade]

@final wadi @mild echo it is in my original internal infra providers spreadsheet

[gusty ice]

Here for sure

Always ready

[final wadi]

looks like Ledger app is almost there
how are things going with Namadillo?

[bronze glade]

Yeah Ledger is in the final stages of testing and validation with Ledger the company itself. Unfortunately, Ledger Nano S will not be able to support MASP (there is not enough storage space on the device itself for the Namada app >= v2.0.0). However, S+ and X are supported.

[dense violet]

We will like do relaying once live. Priorities have been a bit all over the place lately

[mortal saddle]

canonical liver.

[trail nymph]

mentioned multiple times, it should be coordinated to don't have a lot of duplicated channels
the official one must be controlled and monitored by the responsible person

[mortal saddle]

I could read your mind 👁.

[trail nymph]

did you see my typing? 😄

[gusty ice]

canonical channels can be sustained by multiple operators actually

[mortal saddle]

Hehe yes, I just hopped on and thought the same.

[visual yarrow]

he is inside your workstation bro @mortal saddle

[trail nymph]

yep, if there are not 100500 canonical ))

[gusty ice]

but yeah, the one who opens it it's considered the main responsible to keep them up

[bronze glade]

Namadillo improving every day, still has a little bit of work to do to get fully there though. Pls test using it on Campfire tho!!! The more eyes on Namadillo now, the better it will be by Phase 3

Yep @trail nymph thx for bringing up that point, we should coordinate for one particular operator to open up a canonical channel and then get other operators to support only that channel for a given chain

[mortal saddle]

Yeah but we do need to have one open and not open up multiple channels (for a pair), cause I could see this happen.

[gusty ice]

if I recall we did so in SE? or when? we were various updating ibc clients and so (coordinated by Spork thru a spreadsheet)

[mortal saddle]

Ah yes, we did do this indeed.

[bronze glade]

Btw, I will definitely be pushing for a PGF proposal for IBC relayers soon after the Phase 3 start in order to help cover the costs of relayers fees

[final wadi]

we're drawing close to the end!

have a question you've been wanting answered? finding something challenging? have a suggestion? this is the place/time to get these addressed!

[mild echo]

Ok, so it seems I should add a 'canonical' key with the value 'yes' for the responsible person and 'no' for those who help with redundancy?

[final wadi]

lots of different infra providers helping out, how has that been coordinating this, @bronze glade?
i wonder if anyone here is into cat herding 🐈‍⬛ and if that could eventually help free you up to focus on the many other critical tasks you have

[final wadi]

hmm not sure
i think you could probably not, and just not include redundant channels, if someone asks to register it

like if there's an established ATOM channel, and then two weeks later someone opens another ATOM channel, probably nobody will need to know about it

[mild echo]

doesn’t it seem interesting to have a record of those helping with redundancy?

[final wadi]

oops! i'll clarify
the channel is what's cannonical. it can be supported by multiple infra providers

someone could open another channel. this we would not want to record

[bronze glade]

Yeah it could be helpful to onboard someone to help with the "cat-herding" at some point, though I'm good to keep doing it at least for the start of Phase 3

[final wadi]

if there's nothing more, let's close up shop!

great Circle, thanks for joining and engaging 🙂

special thanks to Brent for joining from so high in the sky

[bronze glade]

Thx everyone!!

[mild echo]

Thank you everyone

[karmic bloom]

Happy weekend

[gusty ice]

Have a good one guys

[bronze glade]

Appreciate you all, you the real MVPs