# Design an in-memory key-value database that supports the following commands and fully handles nested transactions.

## Core Operations:
SET <key> <value>: Sets the value for a key.

GET <key>: Returns the value for a key.

UNSET <key>: Removes the key and its value.

## Transaction Operations:
BEGIN: Starts a new transaction scope. If a transaction is already active, this starts a nested transaction.

COMMIT: Applies all changes made in the current transaction scope and all its active nested transactions to the parent scope (or to the main database state if no parent exists). After a successful commit, the transaction scope is closed.

 ROLLBACK: Discards all changes made in the current transaction scope and all its active nested transactions, restoring the state to what it was when the BEGIN command was issued for the current scope. After a successful rollback, the transaction scope is closed.

## Implementation Goal:

Design the primary data structures and outline the logic for SET, COMMIT, and ROLLBACK to ensure nested transactions operate correctly. Explain how the state of the database is managed across multiple transaction layers.