Dev Ojha

icon company UC Berkeley, @sikkatech icon location I'm researching STARKs, working on github.com/scipr-lab/libiop, and am a student at UC Berkeley. I am interested in scaling blockchains. I CTF w/ @sicesquad

Results 383 comments of Dev Ojha

feat(x/bank): Replace regex parsing of denom validation to generated parsing

Thanks facu! That matches the speedup what I was expecting much more w/ the IBC denoms haha

feat(x/bank): Replace regex parsing of denom validation to generated parsing

Its likely even higher impact than that -- note that the 2 IBC denom speedups is being watered down by the 4 denoms of length 3 and one of length...

feat(x/bank): Replace regex parsing of denom validation to generated parsing

I'm totally happy with just doing this for denom's! Even in newDecCoins, we only see the validate Denom regex taking notable time in Osmosis

[Performance]: Restructure slashing for more performance

This also may not make sense with the SDK's plans for a staking/slashing refactor, hence my asking if were aligned on problem/fix

[Performance]: Restructure slashing for more performance

Sweet! #1 was shockingly easier than I expected, making a draft PR right now. I just have to get proto compiling working on my new laptop haha

[Performance]: Restructure slashing for more performance

On our latest benchmarks, using IAVL v1 & no fast nodes, we are now seeing the Reads from slashing as taking 11% of our sync time! I am still shocked...

[Performance]: Restructure slashing for more performance

If i wanted to process every 5th block, I just need to do the following pseudocode: ```go if blockheight % 5 == 0 && blockHeight > 0 { for i...

Make a slash governance proposal

Why is that a strong pre-requisite? Chains can just elect to not include this in their governance router

Make a slash governance proposal

Re the questios: 1) I think the only way to do it efficiently in the SDK atm is Now. That will cover unbondings / redelegations though. 2) Hrm, I think...

Make a slash governance proposal

Re: Safety checks, ok if thats the decision, will recreate the issue in the Osmosis fork. Seems like progressing in the SDK on this would be blocked for several months...