DA-01 · LESSON 08

Protocol profiles and configuration

KEY DEFINITIONS

Terms used in this lesson

Guardian: A Ducat policy-checking signer that can authorize or reject defined protocol transactions.
Oracle: A system that reports outside information, such as a market price, for use by a protocol.
Validator: Software or a participant that independently checks state transitions under a system's rules. The exact role depends on the protocol being discussed.
UNIT: Ducat’s dollar-pegged stablecoin, the asset a borrower can create against bitcoin collateral.
Outpoint: A transaction ID plus output number that identifies one exact prior output.
Runes: A Bitcoin metaprotocol that assigns fungible-token meaning to transaction outputs through off-chain interpretation.
Regtest: A private Bitcoin test network where the operator can create blocks instantly for repeatable experiments.

Network parameters, Guardian keys, oracle keys, ratios, fees, and feature settings are versioned inputs to clients and validators.

65 min Difficulty 4/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
REQUESTProtocol profiles and configuration
The Protocol profiles and configuration 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, Protocol profiles and configuration. The Protocol profiles and configuration 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

Profiles one and two below are illustrative. They teach compatibility checks and are not active network settings.

MECHANISM

Network selection changes address rules, chain data, expected outpoints, and the domain in which commitments are interpreted.

AFTER

Code explains how fields are used. Only a dated, authoritative profile says which network, keys, identities, and policy values a deployment actually uses.

Text equivalent: Starting from Profiles one and two below are illustrative. They teach compatibility checks and are not active network settings. The mechanism begins when Network selection changes address rules, chain data, expected outpoints, and the domain in which commitments are interpreted. The resulting lesson is Code explains how fields are used. Only a dated, authoritative profile says which network, keys, identities, and policy values a deployment actually uses.

2. Mechanism pathSelect a stage to inspect its job

STAGE 1 OF 4

Select the Bitcoin network

Network selection changes address rules, chain data, expected outpoints, and the domain in which commitments are interpreted.

Complete path: 1. Select the Bitcoin network: Network selection changes address rules, chain data, expected outpoints, and the domain in which commitments are interpreted. 2. Bind protocol identities: Guardian and oracle public keys, UNIT Rune identity, protocol anchor, and version fields identify the intended system. 3. Load economic and policy parameters: Ratios, fees, confirmation settings, and feature flags must come from the active profile rather than lesson constants. 4. Reject drift: Clients, Guardians, and validators must agree on compatible profile data or stop before signing and reconstructing different outcomes.

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. Clients, Guardians, and validators must agree on compatible profile data or stop before signing and reconstructing different outcomes.

CHANGED CONDITION

A missing, malformed, stale, unauthorized, or inconsistent required input stops at its first named boundary. Only a dated active profile can establish a current configured value. Test fixtures demonstrate behavior, not live policy.

Important distinction: A value in an example or test is a permanent Ducat parameter. Only a dated active profile can establish a current configured value. Test fixtures demonstrate behavior, not live policy.

Text equivalent: The accepted path is enforced by The worked case executes the named inputs and checks in the displayed order. Clients, Guardians, and validators must agree on compatible profile data or stop before signing and reconstructing different outcomes. If the required condition changes, A missing, malformed, stale, unauthorized, or inconsistent required input stops at its first named boundary. Only a dated active profile can establish a current configured value. Test fixtures demonstrate behavior, not live policy.

Loading lesson visuals...

Learn the idea

A protocol profile is a versioned bundle of network-specific values such as keys, asset identity, ratios, fees, and feature settings. A protocol anchor is an identified on-chain anchor contract whose content names the configuration and signers accepted for that profile. An action version is the numeric version selected by transaction sequence metadata so parsers know which transaction layout and validation rules to apply. Code defines how to use these values; the active profile determines which values apply now.

GUIDED EXPLANATION1/4 ideas inspected

Select the Bitcoin network

Network selection changes address rules, chain data, expected outpoints, and the domain in which commitments are interpreted.

The worked example follows the explanation

Inspect every idea above to open it.

Important distinction“A value in an example or test is a permanent Ducat parameter.”

Only a dated active profile can establish a current configured value. Test fixtures demonstrate behavior, not live policy.

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.