MARGIN

01 the agent

MARGIN is not built around folders.

The user writes naturally.

The agent interprets the input and decides how it should be handled.

examples

The goal is simple:

capture first. organize later.

02 private memory

User memory is private.

Notes, calculations, tasks, links and conversations with MARGIN are not intended to become public data.

They are not published to the project's GitHub repository.

They are not part of the token's on-chain state.

The AI layer and the token layer are separate systems.

your memory is private.

03 memory without folders

Traditional note applications require users to decide where information belongs before or after writing it.

MARGIN removes that step.

The agent can identify relationships between entries and use them when information is requested later.

A user may write several disconnected entries about the same subject.

MARGIN can recognize their relationship and surface them together.

The notebook therefore becomes more useful as context accumulates.

04 margin genesis

MARGIN has a public technical component called Genesis.

Genesis is the original reference architecture of the project.

It can contain:

• /agent
• /contracts
• /spec
• /examples

The repository is designed to be published as a stable reference rather than requiring continuous updates.

It may include:

• reference AI-agent logic
• memory structures
• example inputs
• technical specifications
• MARGIN token contract
• Uniswap v4 hook contract

No private user memories are included.

your memory is private. our core isn't.

$MARGIN

MARGIN also includes an Ethereum token and Uniswap v4 hook.

token

MARGIN

ticker

$MARGIN

network

ethereum mainnet

supply

1,000,000 MARGIN

The token exists as the economic layer surrounding the product.

05 trading fees

MARGIN uses programmable trading fees through Uniswap v4.

buy

1%

sell

2%

The fees generated by eligible swaps are routed into the holder reward system.

There is no requirement for the AI notebook itself to expose private data to the token contracts.

06 holder rewards

100% of trading hook fees are allocated to holders.

Rewards are denominated in:

ETH

Not in MARGIN.

The basic flow is:

1. trade
2. Uniswap v4 hook
3. fee collected
4. holder reward accounting
5. claim
6. ETH

A holder accumulates claimable rewards and can withdraw them using the MARGIN interface.

07 claim

The website contains a dedicated rewards interface.

A connected wallet can view:

figures shown are the real balances read from the connected wallet — 0 until it holds MARGIN or has an ETH reward waiting.

and execute:

claim ETH

The claim transaction transfers the user's available reward in ETH.

Reward accounting and claim state should remain verifiable on-chain.

08 why ETH?

The reward asset is intentionally different from the MARGIN token.

Trading activity produces value for holders, while rewards can be withdrawn as native ETH.

This separates the asset being held from the asset being claimed.

hold MARGIN.
claim ETH.

09 uniswap v4

MARGIN uses Uniswap v4 hooks to place custom logic directly around pool activity.

The hook is responsible for the fee and reward layer associated with MARGIN trading.

The intended pair is:

MARGIN / ETH

on Ethereum Mainnet.

MARGIN does not require a separate centralized reward processor to decide how trading fees are generated.

The rules are encoded in the protocol contracts.

10 two layers

MARGIN is deliberately split into two systems.

The token does not need access to a user's notebook.

The notebook does not need to expose its contents to the token.

11 contract

The token contract address remains directly visible on the main page.

Users should always be able to verify the official contract independently.