Carlos Alejandro Gutiérrez

>2 VMs with public IPs running your fork in this PR - Each VM runs as a seed node with a signer bin. - At least one signer must be...

@AshtonStephens who else can review this?

I have a fix, but it unravels other issues. I'm waiting a bit longer until I can put the case together.

Hi @ldiego08, thank you for your contribution. You need to wait for a core maintainer to approve the workflow. @AshtonStephens

> What's going on with this PR? @AshtonStephens I added a brief description.

blocked by #350

blocked by #350

Partially addresses #282. We would still need to revisit `utils` in another PR.

> The goal should probably be that we can run several signers as defined here: https://github.com/stacks-network/stacks-blockchain/blob/next/stacks-signer/README.md#generate-files Thanks for the heads up. My immediate goal is to unblock the integration pipeline....

@friedger Almost there. I just added clarinet deployments. I may add a deposit or withdrawal test tomorrow based on the script you shared a few days ago.