utils: use container based cli

[EmbeddedAndroid]

Summary of Changes

The util scripts currently are using host binaries for running commands against devnet. This can be confusing to users as we also provide wrappers for accessing the same binaries running inside the container devenv.

Some examples are:

https://github.com/stacks-network/sbtc/blob/main/devenv/bitcoin/bin/bitcoin-cli

https://github.com/stacks-network/sbtc/blob/main/devenv/sbtc/bin/sbtc

Implements: stacks-network/sbtc#224

This PR switches the utils scripts to use the wrappers for container binaries. For the binaries running inside devenv, it must use the service hostnames otherwise localhost will cause them to fail.

Testing

Risks

The biggest risk I see is, if the sbtc container (romeo) crashes, the sbtc command: https://github.com/stacks-network/sbtc/blob/main/devenv/sbtc/bin/sbtc will not be able to run, as the container stopped.

How were these changes tested?

Tested locally with devenv

What future testing should occur?

We need to automate the entire flow via stacks-network/sbtc#215

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[codecov]

Codecov Report

Merging #229 (b8a3c9a) into main (9dabedd) will decrease coverage by 40.13%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #229       +/-   ##
===========================================
- Coverage   78.88%   38.76%   -40.13%     
===========================================
  Files           5       45       +40     
  Lines         270     5167     +4897     
  Branches       47       47               
===========================================
+ Hits          213     2003     +1790     
- Misses         56     3163     +3107     
  Partials        1        1               

Flag	Coverage Δ
unittests	78.88% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 40 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[friedger]

Looks good

[EmbeddedAndroid]

Hold on a moment, I need to update this PR for the merge conflict and one additional fix.

[friedger]

I just fixed the merge conflicts. Sorry, It is your task, I guess. And @CAGS295 needs to review again :-)

[CAGS295]

Did we lose the options changes?

[EmbeddedAndroid]

yeah let me sort this out.

[friedger]

My fault 😓

[EmbeddedAndroid]

Ok this is working for me, deploy_contracts, mine, deposit and withdrawal.

./up.sh
**wait for stacks to start mining**
./utils/deploy_contracts.sh
docker compose down sbtc
docker compose up sbtc -d
./utils/mine_btc.sh 200
./utils/deposit.sh
./utils/withdraw.sh

[CAGS295]

@EmbeddedAndroid, how do you check that stacks-node is ready to deploy contracts? The heuristic I've used so far is checking for stacks height # 2.

[EmbeddedAndroid]

@EmbeddedAndroid, how do you check that stacks-node is ready to deploy contracts? The heuristic I've used so far is checking for stacks height # 2.

that is what I'm doing, polling the api until I see stack height of 2+

[friedger]

LGTM

[friedger]

Looks good