Aryan Godara

@Manav-Aggarwal , I've been looking into these three functions ``` // GetRandomBlock returns a block with random data func GetRandomBlock(height uint64, nTxs int) *Block { block, _ := GetRandomBlockWithKey(height, nTxs,...

Other than this, I went through your previous discussions on `assert.New` vs `assert.Method with testing.t as parameter`; I, too, believe the second approach is better and something I've always used...

So, I saw that you had already done a great optimization since Go doesn't allow default values, and using the (...) variadic pattern isn't viable here. So, I looked up...

Hi @Manav-Aggarwal! According to [this](https://github.com/rollkit/rollkit/pull/1342/files/fc8b2386b05271c2bcd5827d1984ab16c01748ad#r1404627394) comment, do we still want the `require.New()` to be removed from all tests and shift to `require.Method()` approach (same with assert). Because rn, it's a...

Hi, @0xfuturistic! Can I begin to work on this issue? First, by trying to reproduce it on my system (I'm using Sonoma 14.1, but can also test this out on...

I'll go through the recent PRs to see the point of failure and understand the problem better. Do you know any specific place to begin looking apart from this, or...

> for sure! it's a tricky problem. @tynes could you provide some direction? Hi, is there any update on this?

> > I'll go through the recent PRs to see the point of failure and understand the problem better. Do you know any specific place to begin looking apart from...

Hi, @sebastianst. Is this issue still open? If so, I'd like to work on this. I saw this issue mentioned in #8130, and it's not assigned to anyone yet.

> @AryanGodara it's still up for grabs! Note that there's a somewhat related PR #8187 but not sure if @Inphi still wants to complete it. I see, I'm going through...