---
description: >-
  KnightSafe is an open framework to make smart accounts secure, authorizable,
  and efficient interactions with dApps, decentralized exchanges and DeFi
  protocols
---

# Overview

## What Can I Do Through KnightSafe&#x20;

### Set Custom Authorization

Owners can create custom authorization for designated roles.  For example, owners could disable the withdrawing right, or prohibit certain protocols or tokens for the designated role.

They are then able to set up smart contracts for DeFi protocols and specific contractual permissions so that the transactions can be taken place with proper authorization and rules.&#x20;

### Setting Whitelist for Token Transactions <a href="#https-app.gitbook.com-o-ag0se5sdos44lkqty2nw-s-jdqf8nh7igc86agpm5vf-knightsafe-protocol-how-to-use-n" id="https-app.gitbook.com-o-ag0se5sdos44lkqty2nw-s-jdqf8nh7igc86agpm5vf-knightsafe-protocol-how-to-use-n"></a>

Owners can restrict traders to only interact on specific protocols or dApps, or to send specific Tokens to whitelisted addresses.

### DeFi Protocols Transactions

Traders can connect to the DeFi protocols and DEX through Wallet Connect, and perform DeFi transactions within their permitted authorized actions, including but not limited to trade, swap, provide liquidity, lending, etc.

## Architecture

The architecture of the KnightSafe protocol is composed of several integral components, each carrying its unique responsibilities. Token handler and dApp handler are designed to separate themselves from each other, allowing iteration of each part and checking authorization of the designated parameters.

<div data-full-width="true"><figure><img src="https://3906423262-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJdqf8NH7igc86AGPm5VF%2Fuploads%2F2byJpJMfzCqtuGlkEVMT%2FPicture1.png?alt=media&#x26;token=2e5915e4-f2ad-40fc-b6f2-b0bc5f9fc1fe" alt=""><figcaption></figcaption></figure></div>
