# Smart Accounts

Nika uses embedded wallets with MPC key management to provide a secure, seamless, and non-custodial DeFi experience across both EVM and Solana. 

Our architecture differs slightly between EVM and Solana, optimized for each ecosystem's primitives. The approach significantly reduces technical friction, especially for newcomers, and provides seamless cross-chain transactions without manually juggling wallets or bridging tokens. 

Users do not need browser extensions, seed phrases, or native gas tokens to get started, while still retaining the ability to export and fully control their private keys at any time.

***

### Embedded Wallets (Dynamic MPC) <a href="#primary-integrations" id="primary-integrations"></a>

Nika uses Dynamic Embedded Wallets on both EVM and Solana.

These wallets are:

* Created at signup (email or social login)
* Secured using MPC (Multi-Party Computation) split keys
* Fully non-custodial by design
* Exportable by the user at any time

### MPC Key Model <a href="#primary-integrations" id="primary-integrations"></a>

Instead of a single private key existing in one place:

* The private key is cryptographically split
* Key shares are distributed between:
  * The user's device
  * Secure infrastructure components
* No single party ever holds the full key by default

This significantly reduces the risk of key compromise while preserving full ownership.

{% hint style="info" %}
**Important:**

MPC does **not** mean custodial. Users can always export their full private key if desired.
{% endhint %}

***

### Chain-Specific Architecture <a href="#primary-integrations" id="primary-integrations"></a>

While both wallets are provisioned via Dynamic and secured via MPC, EVM and Solana differ at the execution layer.

#### EVM EIP-7702 Smart Wallet Execution <a href="#dynamic" id="dynamic"></a>

On EVM, Nika uses EIP-7702, which allows an EOA to temporarily behave like a smart account without migrating assets into a permanent smart contract wallet. This is fundamentally different from EIP-4337.

Key properties:

* The wallet remains an EOA
* Assets live at the EOA address
* Smart-account-like logic is enabled during execution
* No separate "vault" contract holds funds

This preserves full wallet compatibility with the broader EVM ecosystem

#### Gas Sponsorship (EVM) <a href="#dynamic" id="dynamic"></a>

* Gas fees are sponsored via ZeroDev infrastructure
* Users are not required to hold ETH or native gas tokens
* Gas abstraction is handled transparently during execution
* Costs are covered via Nika's fee and routing architecture

#### EVM Key Export <a href="#dynamic" id="dynamic"></a>

* Users can export their EVM private key
* Importing into MetaMask or any other wallet will:
  * Show full balances
  * Allow full control of asserts
* No smart-contract lock-in or hidden vaults

***

#### Embedded Solana (SVM) Wallet <a href="#dynamic" id="dynamic"></a>

On Solana, the embedded wallet:

* Is a standard Solana keypair
* Directly holds SOL and SPL tokens
* Users the same MPC split-key model via Dynamic

There is no account abstraction layer on Solana—transactions are signed and executed natively.

#### Gas Sponsorship (Solana) <a href="#dynamic" id="dynamic"></a>

* Gas fees (SOL) are sponsored via Nika's own gas wallet
* Users do not need to hold SOL to transact
* Fee abstraction is handled internally at execution time

#### Solana Key Export <a href="#dynamic" id="dynamic"></a>

* Users can export their Solana private key
* Importing in Phantom, Solfare, or other wallets will:
  * Show balances normally
  * Provide full signing authority

***

#### Onboarding Flow <a href="#onboarding-with-email-or-social-login" id="onboarding-with-email-or-social-login"></a>

1. User signs up using email or social login
2. Dynamic provisions:
   1. One embedded EVM wallet
   2. One embedded Solana wallet
3. Wallets are immediately usable
4. Gas fees are abstracted automatically

No extensions. No seed phrases required upfront.

***

#### Why This Architecture <a href="#onboarding-with-email-or-social-login" id="onboarding-with-email-or-social-login"></a>

This design allows Nika to deliver:

* Zero-friction onboarding
* Gasless UX by default
* Full compatibility with DeFi protocols
* No asset lock-in
* Strong security via MPC

All while keeping users in control.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://nikafinance.gitbook.io/docs/reference/smart-accounts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.