> For the complete documentation index, see [llms.txt](https://stoxfi.gitbook.io/stoxfi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stoxfi.gitbook.io/stoxfi-docs/technical-differentiation.md).

# Technical Differentiation

StoxFi applies fully homomorphic encryption to the settlement of tokenized equity positions.

Its technical distinction comes from combining encrypted balances and transfers with cross chain collateral custody and a verifiable redemption path.

The result is a system where the underlying asset remains locked on its original chain while its corresponding position can be represented and transferred confidentially on Ethereum.

### StoxFi Settlement Model

**StoxFi Technical Differentiation**

<figure><img src="https://2963579709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdIccUwMy0hIW7yzdERSR%2Fuploads%2F7OXQMRbnkovxJmjPlaMj%2Fstoxfi-technical-differentiation-venn-centered.png?alt=media&amp;token=fecfa53e-12a4-4fda-93b0-03d942b77390" alt=""><figcaption></figcaption></figure>

The StoxFi model combines four properties:

1. Underlying collateral remains locked in StoxVault
2. Cross chain communication carries instructions rather than assets
3. Balances and transfer amounts operate as encrypted values
4. Redemption converts confidential value back into underlying collateral through verified decryption

These properties define the StoxFi settlement architecture.

### Compared with Standard ERC 20 Assets

A standard ERC 20 stores balances as public integers.

Transfers expose the amount together with the sender and recipient.

StoxFi changes the balance and amount model.

| Property            | Standard ERC 20   | StoxFi Confidential Representation |
| ------------------- | ----------------- | ---------------------------------- |
| Balance             | Public `uint256`  | Encrypted `euint64`                |
| Sender              | Public            | Public                             |
| Recipient           | Public            | Public                             |
| Transfer amount     | Public            | Encrypted                          |
| Balance computation | Public arithmetic | Homomorphic arithmetic             |
| Holder balance      | Public            | Confidential                       |

StoxFi therefore does not attempt to hide the existence of a transfer.

It changes which financial information the transfer exposes.

### Compared with Traditional Token Bridges

Traditional bridge architectures move or recreate token representations across chains.

StoxFi uses a different model.

The underlying asset does not travel through CCIP.

It remains locked in StoxVault on Robinhood Chain.

CCIP carries only instructions.

During shielding, the instruction authorizes creation of the corresponding confidential representation.

During redemption, the instruction authorizes release of the collateral already held by StoxVault.

The cross chain connection therefore provides access to the confidential computation environment rather than relocating the underlying asset itself.

### Collateral and Confidential Execution

StoxFi separates custody from confidential execution.

Robinhood Chain provides the public collateral side.

Ethereum provides the confidential settlement side.

The relationship between them is maintained through:

`locked collateral`

and

`confidential supply × conversion rate`

This gives StoxFi a public collateral relationship while individual confidential balances remain encrypted.

### Compared with Privacy Mixers

StoxFi does not use a mixer model.

A mixer primarily attempts to break the relationship between addresses.

StoxFi does not hide sender and recipient addresses.

Instead, it encrypts balances and transfer amounts.

The privacy objective is therefore different.

StoxFi provides confidential financial values rather than address anonymity.

### Compared with Zero Knowledge Systems

StoxFi uses fully homomorphic encryption rather than a zero knowledge transfer architecture.

A zero knowledge system can prove a statement about hidden information without revealing that information.

StoxFi instead performs computation directly on encrypted values.

For confidential transfers, the contract can evaluate encrypted conditions and update encrypted balances without reading the plaintext amount.

The transfer does not require the contract to decrypt the value before operating on it.

### Encrypted State as Application State

The confidential balance is not simply encrypted data stored for later retrieval.

StoxFi performs protocol logic directly against encrypted state.

For example, a confidential transfer evaluates whether:

`amount ≤ sender balance`

and whether:

`amount ≤ remaining recipient capacity`

These conditions remain encrypted.

StoxFi then uses encrypted selection to determine whether the requested value or zero should move.

This makes encrypted state part of the execution model itself.

### Silent Failure Behavior

Ordinary token transfers often expose insufficient balance through a revert.

That behavior can reveal information about a supposedly confidential position.

StoxFi instead uses encrypted conditions to select between the requested transfer value and zero.

An invalid confidential transfer can therefore complete without publicly revealing whether the sender lacked sufficient balance.

This behavior is specifically designed around confidential state.

### Redemption from Encrypted State

StoxFi also connects encrypted state back to public collateral.

The confidential amount is burned first.

That specific burned value is then made publicly decryptable.

The resulting clear value must be accompanied by valid signatures before the release instruction can be created.

This produces a redemption path from encrypted holdings back to the underlying ERC 20 without introducing an administrative mint or manual release authority.

### Relationship to the FHE Infrastructure

The FHE infrastructure provides the cryptographic computation environment used by StoxFi.

StoxFi applies that infrastructure to confidential settlement of tokenized equity positions.

StoxFi adds the application specific architecture around the encrypted computation layer:

1. Cross chain collateral custody
2. Asset specific vault relationships
3. Decimal conversion
4. Confidential asset representation
5. Structural collateral accounting
6. Cross chain mint instructions
7. Confidential transfer logic
8. Two phase redemption
9. Verified collateral release

The FHE infrastructure and StoxFi therefore perform different roles within the system.

### Relationship to CCIP

CCIP provides the cross chain messaging infrastructure.

StoxFi defines the messages and the application logic surrounding them.

The messaging layer does not custody the underlying stock for StoxFi.

It communicates the instructions that connect collateral state on Robinhood Chain with confidential state on Ethereum.

StoxFi additionally validates the expected source chain, sender, router, and message identifier before acting on an inbound instruction.

### Confidential Settlement Rather Than Confidential Issuance

The StoxFi architecture begins with an existing underlying ERC 20.

The underlying asset is locked as collateral.

Its confidential representation is then created against that locked position.

This differs from a model where a confidential token is simply issued directly on one chain without an external collateral lifecycle.

StoxFi adds:

**Cross chain collateralization**

**Locked underlying assets**

**A public backing relationship**

**Threshold signed redemption**

**Return settlement into the underlying asset**

### Technical Positioning

The technical role of StoxFi can be expressed as:

**Public collateral custody plus confidential execution plus verified redemption.**

The underlying asset remains publicly accounted for in StoxVault.

The confidential representation operates using encrypted balances.

Cross chain instructions synchronize the two sides.

Redemption destroys the confidential value before releasing the underlying collateral.

### Technical Differentiation Summary

StoxFi does not attempt to make every part of an onchain transaction invisible.

Instead, it introduces confidentiality where public tokenized asset infrastructure normally exposes financial values.

Compared with a standard ERC 20, balances and transfer amounts become encrypted.

Compared with a traditional bridge, the underlying asset remains in its vault while instructions cross chains.

Compared with a mixer, StoxFi protects amounts rather than hiding address relationships.

Compared with a zero knowledge transfer architecture, StoxFi performs computation directly on encrypted state.

The resulting architecture is designed specifically around confidential settlement of tokenized equity positions while preserving a verifiable relationship with the underlying collateral.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://stoxfi.gitbook.io/stoxfi-docs/technical-differentiation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
