sbtc: automatically deploy contracts

[EmbeddedAndroid]

Description

Now that stacks-sbtc/sbtc#173 has been merged, it would be ideal to have the sbtc container, deploy the contract automatically.

Context

It will help new users if we can automate as much setup as possible, and reduce the risk of a bad experience because of complexity.

Expected Approach

Leverage the setup from what @CAGS295 has done on the integration test container - https://github.com/stacks-network/sbtc/pull/215/files#diff-56bb3d9e8d0e342d456dd54468938fb905f8bea8793ddf7d3393d04a15c28661R9-R25

Acceptance Criteria

• PR adds the feature
• PR is reviewed and merged
• run ./up.sh, wait and then send deposit and withdrawal request

[friedger]

Acceptance criteria:
I can run ./up.sh, wait and then send deposit and withdrawal request

[EmbeddedAndroid]

Acceptance criteria: I can run ./up.sh, wait and then send deposit and withdrawal request

added to acceptance criteria

[janniks]

Will a while-sleep loop in a docker entrypoint as linked above, wait until the loop is done before it starts the dependent docker-compose services?

[CAGS295]

I have found that the script in the link is very effective. Try the following.
Wait for stacks-node rpc to be up. Loop sleep until stacks height is at least two. Use clarinet deployments to submit the contracts.

[janniks]

Cool thanks, I was using a docker compose healthcheck to wait and see when the stacks api /info works.

[CAGS295]

That could work, too. Do you have a snip?

[stjepangolemac]

One thing to note here is that if we deploy contracts immediately Romeo will always process almost all blocks when started up. When working on it there are valid reasons to delay the contract deployment for later so when the environment is tweaked we can only let Romeo process a few blocks. That makes debugging easier.

This is a nitpick and I don't mind this being automated for now. After the hackaton we can reconsider if needed.

[janniks]

diff --git a/devenv/docker-compose.yml b/devenv/docker-compose.yml
index af48a98..e5c518d 100644
--- a/devenv/docker-compose.yml
+++ b/devenv/docker-compose.yml
@@ -59,7 +59,7 @@ services:
     depends_on:
       - bitcoin
     environment:
-      INIT_BTC_BLOCKS: 200
+      INIT_BTC_BLOCKS: 101
       BTC_BLOCK_GEN_TIME: 10
   stacks:
     image: stacks:latest
@@ -92,6 +92,13 @@ services:
     ports:
       - 3999:3999
       - 3700:3700
+    healthcheck:
+      test: "wget -q -t=1 --spider http://localhost:3999/v2/info || exit 1"
+      start_period: 1m
+      start_interval: 3s
+      interval: 10s
+      timeout: 3s
+      retries: 3
     depends_on:
       - postgres
       - stacks
@@ -119,16 +126,20 @@ services:
     build:
       context: ./stacks-explorer/docker
       args:
-        STACKS_EXPLORER_VERSION: 'v1.119.0'
+        STACKS_EXPLORER_VERSION: "v1.119.0"
         GIT_URI: https://github.com/hirosystems/explorer.git
         GIT_BRANCH: v1.119.0
     ports:
       - 3000:3000
     depends_on:
-      - bitcoin
-      - stacks
-      - stacks-api
-      - postgres
+      bitcoin:
+        condition: service_started
+      stacks:
+        condition: service_started
+      stacks-api:
+        condition: service_healthy
+      postgres:
+        condition: service_started
     environment:
       - NEXT_PUBLIC_MAINNET_API_SERVER=http://127.0.0.1:3999
   electrs:

This is what I was playing with RE healthchecks.

[CAGS295]

Could a utils/script be used for deployments instead? I've been using this as an entry point for integration tests. With a few tweaks, it could be used as a utils/script.

echo "Waiting on Stacks API $API_URL"
while ! curl -s $API_URL >/dev/null; do
    sleep 1
done

DEV_READY_HEIGHT=205

# bitcoind get info
echo "Waiting on burn block height $DEV_READY_HEIGHT"
while [ "$(curl -s $API_URL | jq '.burn_block_height')" -lt $DEV_READY_HEIGHT ]; do
    sleep 2
done

#stacks ready to take contracts
STACKS_HEIGHT=2
echo "Waiting on Stacks height $STACKS_HEIGHT"
while [ "$(curl -s $API_URL | jq '.stacks_tip_height')" -lt $STACKS_HEIGHT ]; do
    sleep 2
done

# any other service checks

# push contracts
cd romeo/asset-contract
sed -i "s/localhost:20443/$STACKS:20443/" deployments/default.devnet-plan.yaml
sed -i "s/localhost:18443/$BITCOIN:18443/" deployments/default.devnet-plan.yaml
clarinet deployments apply --no-dashboard -d -p deployments/default.devnet-plan.yaml
cd -

[friedger]

We have deploy_contracts which could include this in there.