Sabby Anandan

Hi, @dbahatSAP. Thank you for the analysis! If you're familiar with the workflow to improve, please feel free to start a PR. One of us can pair with you to...

@dturanski @sobychacko: Any thoughts on this?

I have had the opportunity to interact with @BowTiedDeployer, and I can say confidently that they genuinely care and want the Stacks community to succeed. Their thoughtful feedback and recommendations...

@smcclellan: This is probably a nice-to-have. Not too pressing.

@MicaiahReid: Woot! I love the thoughtful thinking behind aligning on the `clarinet ` conventions—big fan. Doing these as part of v2.0 would be a great way to consolidate and tighten...

>Hey @sabbyanandan I wanted to point out that the clarinet-sdk is mainly used to be used within Node.js, but not in the browser. So as it is, it could be...

>Any feedback on that? @sabbyanandan @beguene @hugocaillard @lgalabru @MicaiahReid @csgui: If I understand the [data structure](https://github.com/hirosystems/clarinet/issues/1034#issuecomment-1738914627) correctly, it appears we have a few different ways to get the "possible" event-streams...

@hugocaillard: Nakamoto/sBTC is the immediate priority, and access to events via the SDK can take a back seat until you free up. There is no rush; the Platform can pick...

@smcclellan: Once 2.2 ships, could we timebox to review the scope and estimate this effort? There are additional signals from devs using Chainhooks, but they also create things manually, which...

@hugocaillard: It is probably too early right now, but when the time is right, it'd be good to get a sense of the Docker daemon's compute requirements (i.e., what is...