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

# Technical Details

## Contract Addresses

### Solana

* **Contract Address:** [4UWX6gpAiHW1Nr11TXitLWRi3H3cWiYm7qAKVyKosoLF](https://solscan.io/token/4UWX6gpAiHW1Nr11TXitLWRi3H3cWiYm7qAKVyKosoLF)
* **Token Standard:** SPL (Solana Program Library)
* **Decimals:** 6
* **Network:** Solana Mainnet

### Ethereum

* **Contract Address:** [0x2b679fd2dd133162a501e2d9ddda850ccd7a837b](https://etherscan.io/token/0x2b679fd2dd133162a501e2d9ddda850ccd7a837b)
* **Token Standard:** ERC-20
* **Decimals:** 18
* **Network:** Ethereum Mainnet

## Token Specifications

### Basic Info

* **Token Name:** SolFart
* **Symbol:** SOLF
* **Total Supply:** 100,000,000,000 (100 billion)
* **Contract Type:** Standard token (no special features)

### Technical Parameters

```
Solana:
- Token Program: Token-2022 Program
- Mint Authority: Disabled (fixed supply)
- Freeze Authority: Disabled (no freezing)
- Close Authority: Disabled (no closing)

Ethereum:
- Standard: ERC-20
- Mintable: No (fixed supply)
- Burnable: Yes (users can burn tokens)
- Pausable: No (no pause function)
```

## Security Measures

### Smart Contract Security

* **Audited contracts** - Third-party security audit completed
* **Multi-signature wallets** - Team funds require multiple signatures

## Cross-Chain Functionality

### Bridge Details

* **Bridge Provider:** Wormhole (Solana ↔ Ethereum)
* **Security Model:** Guardian network with 19 validators
* **Transfer Time:** \~10-15 minutes
* **Fees:** Variable based on network congestion

### How Cross-Chain Works

1. **Lock tokens** on source chain
2. **Verify transaction** through bridge validators
3. **Mint tokens** on destination chain
4. **Redeem tokens** when bridging back

## Technical Architecture

### Solana Implementation

```
Program: Token-2022 Program
Mint: Fixed supply, no mint authority
Metadata: On-chain metadata with IPFS images
Transfer: Standard SPL transfer
```

### Ethereum Implementation

```
Standard: ERC-20 OpenZeppelin
Functions: transfer, approve, transferFrom
Events: Transfer, Approval
Metadata: EIP-5267 compliant
```

## Integration Details

### DEX Integration

* **Raydium (Solana):** Liquidity pool creation
* **Uniswap (Ethereum):** V3 pool creation
* **Orca (Solana):** Alternative DEX option
* **SushiSwap (Ethereum):** Cross-chain DEX

### CEX Integration

* **Gate.io:** Initial listing planned
* **MEXC:** Secondary listing planned
* **KuCoin:** Future listing consideration
* **Binance:** Long-term goal

## Monitoring & Analytics

### On-Chain Analytics

* **Token holders** - Real-time holder count
* **Transaction volume** - Daily trading volume
* **Price tracking** - Multiple price feeds
* **Liquidity monitoring** - Pool health tracking

### Off-Chain Analytics

* **Social metrics** - Twitter, Discord, Telegram activity
* **Exchange data** - CEX trading volume and price
* **Community growth** - New holder acquisition
* **Marketing effectiveness** - Campaign performance tracking

***

*Next: How to Participate →*


---

# 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://sol-fart.gitbook.io/solfart-whitepaper/technical-details.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.