DA-07 · LESSON 05

Deployment environments

KEY DEFINITIONS

Terms used in this lesson

Regtest: A private Bitcoin test network where the operator can create blocks instantly for repeatable experiments.
Proof-of-work target: The maximum header-hash value accepted for a block; lowering it makes valid hashes harder to find.
Identifier: Identifier: a value used to distinguish one request, object, or participant from another.
Oracle: A system that reports outside information, such as a market price, for use by a protocol.

Regtest, Mutinynet, testnet targets, staging names, and mainnet readiness must be identified by actual configuration and deployed artifact, not labels.

35 min Difficulty 5/5 Not started

VISUAL MODEL

See the whole mechanism before going step by step

Use the diagrams to orient yourself. Then the guided explanation below teaches every part in depth.

4 explanatory views

CONCEPT-SPECIFIC MAP · ducat vaultA Ducat action moves one Bitcoin-anchored vault state to a successorSelect any state to inspect its exact role.

RELATIONSHIP MAPInputs, rule, and outputs

01
PREDECESSORCurrent vault outpoint
The current Bitcoin output anchors collateral and identifies the state being spent.
02
REQUESTDeployment environments
The Deployment environments workflow proposes one exact action and successor state.
03
POLICYProfile, oracle, signatures
Applicable policy, price evidence, authorization, and transaction shape are checked.
04
BITCOIN SPENDScript-valid transaction
Bitcoin miners and nodes can include only a transaction that satisfies Bitcoin rules.
05
SUCCESSORNew outpoint and state
Ducat validators reconstruct debt, collateral, token, and account changes from the confirmed transaction.

Rule shown: Bitcoin checks the spend; Ducat components independently reconstruct and validate the additional protocol state.

STAGE 1 OF 5PREDECESSOR: Current vault outpoint

The current Bitcoin output anchors collateral and identifies the state being spent.

Governing relationship: Bitcoin checks the spend; Ducat components independently reconstruct and validate the additional protocol state. Complete path: 1. PREDECESSOR, Current vault outpoint. The current Bitcoin output anchors collateral and identifies the state being spent. 2. REQUEST, Deployment environments. The Deployment environments workflow proposes one exact action and successor state. 3. POLICY, Profile, oracle, signatures. Applicable policy, price evidence, authorization, and transaction shape are checked. 4. BITCOIN SPEND, Script-valid transaction. Bitcoin miners and nodes can include only a transaction that satisfies Bitcoin rules. 5. SUCCESSOR, New outpoint and state. Ducat validators reconstruct debt, collateral, token, and account changes from the confirmed transaction.

1. State transitionWhat exists, what changes, and what results

BEFORE

A deployment manifest is named alpha-mainnet but reports Bitcoin chain testnet4, test coins, a test Data Streams feed, protocol commit 96cfbe996f8f, oracle commit bd394c3763b…

MECHANISM

Verify genesis, address network, node endpoint, chain tip, and expected protocol anchor rather than trusting a target label.

AFTER

The evidence supports a test environment with captured build references and no observed unified oracle deployment. The name does not establish mainnet or real-funds readiness.

Text equivalent: Starting from A deployment manifest is named alpha-mainnet but reports Bitcoin chain testnet4, test coins, a test Data Streams feed, protocol commit 96cfbe996f8f, oracle commit bd394c3763b4, and an empty deployed unified-workflow ide… The mechanism begins when Verify genesis, address network, node endpoint, chain tip, and expected protocol anchor rather than trusting a target label. The resulting lesson is The evidence supports a test environment with captured build references and no observed unified oracle deployment. The name does not establish mainnet or real-funds readiness.

2. Mechanism pathSelect a stage to inspect its job

STAGE 1 OF 4

Identify the actual Bitcoin network

Verify genesis, address network, node endpoint, chain tip, and expected protocol anchor rather than trusting a target label.

Complete path: 1. Identify the actual Bitcoin network: Verify genesis, address network, node endpoint, chain tip, and expected protocol anchor rather than trusting a target label. 2. Identify running artifacts: Record commit, build digest, configuration, keys, workflow ID, database version, and deployment time for every component. 3. Identify funds and operators: State whether funds are synthetic, test coins, or real, and who controls each service and key. 4. Identify reliability promises: Public test chains, temporary cloud services, and local regtest have different reorg, reset, uptime, and support expectations.

3. Rule and failure boundaryWhat accepts the result and where it can stop

ACCEPTED PATH

The worked case executes the named inputs and checks in the displayed order. Public test chains, temporary cloud services, and local regtest have different reorg, reset, uptime, and support expectations.

CHANGED CONDITION

A missing, malformed, stale, unauthorized, or inconsistent required input stops at its first named boundary. Only actual network, artifact, key, fund, and runtime evidence establishes the environment.

Important distinction: A mainnet-named deployment target proves the system uses real Bitcoin mainnet and production services. Only actual network, artifact, key, fund, and runtime evidence establishes the environment.

Text equivalent: The accepted path is enforced by The worked case executes the named inputs and checks in the displayed order. Public test chains, temporary cloud services, and local regtest have different reorg, reset, uptime, and support expectations. If the required condition changes, A missing, malformed, stale, unauthorized, or inconsistent required input stops at its first named boundary. Only actual network, artifact, key, fund, and runtime evidence establishes the environment.

Loading lesson visuals...

Learn the idea

Regtest is a private locally controlled Bitcoin chain. Mutinynet and testnet are public testing environments with different reliability and reset risks. Staging is an operator-controlled application environment. A name containing mainnet does not prove mainnet readiness or real-funds enablement.

GUIDED EXPLANATION1/4 ideas inspected

Identify the actual Bitcoin network

Verify genesis, address network, node endpoint, chain tip, and expected protocol anchor rather than trusting a target label.

The worked example follows the explanation

Inspect every idea above to open it.

Important distinction“A mainnet-named deployment target proves the system uses real Bitcoin mainnet and production services.”

Only actual network, artifact, key, fund, and runtime evidence establishes the environment.

FINISH LEARNING FIRST

The questions unlock after every required learning activity

Inspect every guided idea, open the worked example, rebuild its mechanism, and complete the deterministic lesson tool. Your progress is saved automatically.