Service lifecycle

1. Intention to intent In the first phase, the intelligence engine decodes user's underlying intention and maps them to an intent for operators to execute.

   1. Transaction Preview: The Intelligence Engine assembles a transaction payload based on the End User’s requested service, ensuring End User policies are adhered to

   2. User Authorisation: The End User reviews the payload and signs it, providing cryptographic consent

   3. Submission to Home Chain: The Operator submits the signed transaction to dBOOK’s home chain, initiating the service process

2. Fulfilment

   1. Asset Locking: Once the transaction is processed, the necessary funds are locked in the End User’s account on the home chain

   2. Service Execution: The Operator performs the requested service—this can involve interacting with off-chain entities (e.g., CEXs) or executing on-chain actions (e.g., cross-chain trades)

3. Settlement

   1. Settlement Request: Upon completing the service, the Operator submits a “settle transaction” to the review pool on the home chain

   2. Validator Review: Validators have the option to challenge this request if they detect any issues. In the event of a challenge, the Operator must provide proof of proper service execution

   3. Final Updates: After successful validation (or a resolved challenge), the End User’s and Operator’s accounts are updated accordingly, and any locked funds are released as specified

4. Recommendation

   1. After the transaction is successfully executed, a tailored protocol recommendation—optimised to match the user’s specific goals—is immediately communicated

   2. This recommendation is derived from a real-time analysis of transaction details, user preferences, and prevailing market dynamics, ensuring the suggestion is safe, relevant and actionable

Through these stages, dBOOK ensures users retain self-custody until services are verified, while Operators are incentivised to act honestly under the watchful oversight of Validators.