Jeff Bencin
Jeff Bencin
> Could you try this over, say, 1000 blocks Eventually, but that would take a long time. I've been using a benchmark that is reasonably fast so that I can...
@cylewitruk here's the performance on block range 145,000-145,050 with all current PRs (everything used in the previous comment, plus #4425): ```console ❯ hyperfine -w 3 -r 10 "stacks-core/target/release/stacks-inspect.7e5146511 replay-block /home/jbencin/data/next/...
I generated a new `costs-4.clar` contract which includes the recent optimization work (as of commit `80adc2762`). See the diff [here](https://github.com/stacks-network/stacks-core/commit/4361236b11afab82c0085df37b905a35787317cf). Lots of costs went down, but some went up. Can...
@jcnelson or @kantai I'll need some more detail on this in order to start, I'm not familiar with the "anti-entropy state machine" or the network code at all. I assume...
> The rolling hash approach is still required, because it provides linear-time signing and verification. For example, contrast this to Bitcoin's signing and verifying algorithm, which before segwit was quadratic-time...
> And one more question - should we do the same thing for `StacksMicroBlock` as well? It is my understanding that microblocks are going away as of 3.0, so I...
> Then, we'd implement `DeserializeWithEpoch` for `StacksTransaction` such that... Hey @fess-v I'm going to need this same trait for #3974. Let me know if you've added this already. If not,...
Can I just transfer the entire p2p thread like we do with the monitoring thread? Like this: ```rust let monitoring_thread = neon_loop.take_monitoring_thread(); let naka = NakaRunLoop::new( /* ... */ monitoring_thread,...
> Can I just transfer the entire p2p thread like we do with the monitoring thread? Like this: After looking into this a bit more, I don't think this would...