Commit ·
87bfbec
1
Parent(s): 72667b2
why do we need two readmes
Browse files- Readme.md +0 -245
- ReadmeMore.md +244 -0
Readme.md
CHANGED
|
@@ -18,248 +18,3 @@ size_categories_planned:
|
|
| 18 |
- n>1M
|
| 19 |
size_categories_notes: We will have many more transactions
|
| 20 |
---
|
| 21 |
-
|
| 22 |
-
# SOLFUNMEME Transaction Cache Dataset
|
| 23 |
-
|
| 24 |
-
Welcome to the SOLFUNMEME Transaction Cache Dataset hosted on Hugging Face! This repository contains a curated collection of JSON caches derived from Solana blockchain RPC queries for the SOLFUNMEME (SFM) token (BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump). The dataset encapsulates transaction metadata, token balance changes, and program interactions, providing a robust resource for exploring the trading dynamics, decentralized finance (DeFi) patterns, and community-driven meme propagation of SFM within the Solana ecosystem.
|
| 25 |
-
|
| 26 |
-
## Dataset Description
|
| 27 |
-
|
| 28 |
-
The SOLFUNMEME Transaction Cache Dataset is a structured archive of Solana transaction data designed to support research, development, and community engagement with the SFM token, a key element of the Zero Ontology System (ZOS). ZOS is a pioneering framework that blends meme coin mechanics with decentralized governance, self-hosted agents, and zero-knowledge machine learning (ZKML) on Solana’s high-throughput blockchain.
|
| 29 |
-
|
| 30 |
-
The dataset abstracts raw transaction data into JSON files, enabling users to:
|
| 31 |
-
- Analyze trading activities, such as buy and sell transactions, on platforms like Raydium.
|
| 32 |
-
- Investigate SFM’s tokenomics, liquidity trends, and market behavior.
|
| 33 |
-
- Apply formal verification techniques (e.g., Lean-based proofs) to ensure transaction integrity.
|
| 34 |
-
- Explore the social and economic dynamics of meme propagation within the SOLFUNMEME community.
|
| 35 |
-
- Inform the development of ZOS-based applications, such as decentralized meme engines or trading bots.
|
| 36 |
-
|
| 37 |
-
## Key Features
|
| 38 |
-
|
| 39 |
-
- **Rich Transaction Metadata**: Captures block times, slots, account balances, token transfers, and program logs for comprehensive analysis.
|
| 40 |
-
- **SFM-Centric**: Focuses on the SFM token (BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump), covering trades, account creations, and token movements.
|
| 41 |
-
- **Optimized for Reusability**: Caches Solana RPC responses to reduce query overhead and ensure reproducibility.
|
| 42 |
-
- **Verification-Ready**: Structured to integrate with formal methods tools (e.g., Lean) for proving properties like token conservation and balance consistency.
|
| 43 |
-
- **Community-Aligned**: Supports the SOLFUNMEME project’s mission to foster decentralized, user-driven meme ecosystems.
|
| 44 |
-
|
| 45 |
-
## Data Sources
|
| 46 |
-
|
| 47 |
-
The dataset is generated by querying Solana’s mainnet RPC endpoint (https://api.mainnet-beta.solana.com) using two core methods:
|
| 48 |
-
1. **getSignaturesForAddress**: Retrieves transaction signatures for the SFM token address, indexing a wide range of activities, including trades, transfers, and account operations.
|
| 49 |
-
2. **getTransaction**: Provides detailed transaction metadata, including:
|
| 50 |
-
- **Timing and Block Data**: Unix timestamps and Solana block heights (slots).
|
| 51 |
-
- **Account Balances**: SOL balances (in lamports) before and after transactions.
|
| 52 |
-
- **Token Balances**: Pre- and post-transaction balances for SFM and other tokens (e.g., Wrapped SOL).
|
| 53 |
-
- **Program Interactions**: Execution logs from programs like Raydium AMM, SPL Token Program, System Program, and Compute Budget Program.
|
| 54 |
-
- **Instructions**: Details of transaction instructions and nested inner instructions (e.g., token transfers within swaps).
|
| 55 |
-
|
| 56 |
-
## Dataset Contents
|
| 57 |
-
|
| 58 |
-
The dataset is organized as follows:
|
| 59 |
-
|
| 60 |
-
### rpc_cache/
|
| 61 |
-
- **method_getSignaturesForAddress_address_BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump_[hash].json**: Lists transaction signatures associated with the SFM token, serving as an index for further exploration.
|
| 62 |
-
- **method_getTransaction_signature_[signature].json**: Contains detailed transaction data, including metadata, balance changes, and program logs.
|
| 63 |
-
- **temp_*.json and temp_*.txt**: Temporary files storing request payloads, responses, and error logs for debugging and transparency.
|
| 64 |
-
- **README.md**: This file, providing an overview, usage instructions, and context.
|
| 65 |
-
- **LICENSE**: Specifies the terms of use for the dataset (e.g., MIT License).
|
| 66 |
-
|
| 67 |
-
## Data Structure
|
| 68 |
-
|
| 69 |
-
Each JSON file adheres to the Solana JSON-RPC 2.0 format, with key fields optimized for analysis:
|
| 70 |
-
- **result.blockTime**: Unix timestamp of the transaction.
|
| 71 |
-
- **result.slot**: Solana block height.
|
| 72 |
-
- **result.meta.preBalances** and **result.meta.postBalances**: SOL balances (in lamports) for accounts before and after the transaction.
|
| 73 |
-
- **result.meta.preTokenBalances** and **result.meta.postTokenBalances**: Token balances for SFM and other tokens, with fields:
|
| 74 |
-
- **accountIndex**: Index in the transaction’s account list.
|
| 75 |
-
- **mint**: Token mint address (e.g., BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump for SFM).
|
| 76 |
-
- **uiTokenAmount.amount**: Token amount in smallest units.
|
| 77 |
-
- **uiTokenAmount.uiAmountString**: Human-readable amount.
|
| 78 |
-
- **result.meta.logMessages**: Program execution logs, identifying interactions with Raydium, Token Program, etc.
|
| 79 |
-
- **result.transaction.message.instructions**: Instructions executed, including program IDs and account indices.
|
| 80 |
-
- **result.transaction.message.addressTableLookups**: Address table lookups for additional account resolution.
|
| 81 |
-
|
| 82 |
-
## Potential Use Cases
|
| 83 |
-
|
| 84 |
-
This dataset enables a range of applications:
|
| 85 |
-
- **Trading Pattern Analysis**: Identify buy and sell transactions by examining token balance changes, supporting studies of market dynamics and investor behavior.
|
| 86 |
-
- **Tokenomics Research**: Analyze SFM’s supply, liquidity, and trading volume to understand its role in the Solana meme coin ecosystem.
|
| 87 |
-
- **Formal Verification**: Use with Lean or other formal methods tools to prove transaction properties, such as non-negative balances or token conservation.
|
| 88 |
-
- **Community Mapping**: Study wallet interactions to uncover patterns of engagement within the SOLFUNMEME community, aligning with ZOS’s meme propagation goals.
|
| 89 |
-
- **DeFi Innovation**: Inform the development of ZOS-based tools, such as decentralized agents, trading algorithms, or governance mechanisms.
|
| 90 |
-
- **Educational Exploration**: Learn about Solana’s transaction model, DeFi protocols, and the intersection of blockchain and meme culture.
|
| 91 |
-
|
| 92 |
-
### Example Use Case: Identifying Trading Activity
|
| 93 |
-
|
| 94 |
-
A common use case is analyzing SFM trading activity on Raydium. For instance, a transaction might show an account gaining SFM tokens (indicating a buy) in exchange for Wrapped SOL, with the Raydium AMM program facilitating the swap. By comparing `preTokenBalances` and `postTokenBalances`, users can quantify token movements and correlate them with market trends or community activity.
|
| 95 |
-
|
| 96 |
-
## How to Use the Dataset
|
| 97 |
-
|
| 98 |
-
### Prerequisites
|
| 99 |
-
- Proficiency in JSON processing (e.g., Python, JavaScript, or Rust).
|
| 100 |
-
- Basic understanding of Solana’s transaction structure and DeFi concepts.
|
| 101 |
-
- Optional: Lean environment for formal verification or dataset extension.
|
| 102 |
-
|
| 103 |
-
### Getting Started
|
| 104 |
-
1. **Clone or Download the Repository**:
|
| 105 |
-
```bash
|
| 106 |
-
git clone https://huggingface.co/[your-username]/solfunmeme-transaction-cache
|
| 107 |
-
cd solfunmeme-transaction-cache
|
| 108 |
-
|
| 109 |
-
Here is the reformatted Markdown with proper heading levels:
|
| 110 |
-
|
| 111 |
-
```markdown
|
| 112 |
-
# SOLFUNMEME Transaction Cache Dataset
|
| 113 |
-
|
| 114 |
-
Welcome to the SOLFUNMEME Transaction Cache Dataset hosted on Hugging Face! This repository contains a curated collection of JSON caches derived from Solana blockchain RPC queries for the SOLFUNMEME (SFM) token (BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump). The dataset encapsulates transaction metadata, token balance changes, and program interactions, providing a robust resource for exploring the trading dynamics, decentralized finance (DeFi) patterns, and community-driven meme propagation of SFM within the Solana ecosystem.
|
| 115 |
-
|
| 116 |
-
## Dataset Description
|
| 117 |
-
|
| 118 |
-
The SOLFUNMEME Transaction Cache Dataset is a structured archive of Solana transaction data designed to support research, development, and community engagement with the SFM token, a key element of the Zero Ontology System (ZOS). ZOS is a pioneering framework that blends meme coin mechanics with decentralized governance, self-hosted agents, and zero-knowledge machine learning (ZKML) on Solana’s high-throughput blockchain.
|
| 119 |
-
|
| 120 |
-
The dataset abstracts raw transaction data into JSON files, enabling users to:
|
| 121 |
-
- Analyze trading activities, such as buy and sell transactions, on platforms like Raydium.
|
| 122 |
-
- Investigate SFM’s tokenomics, liquidity trends, and market behavior.
|
| 123 |
-
- Apply formal verification techniques (e.g., Lean-based proofs) to ensure transaction integrity.
|
| 124 |
-
- Explore the social and economic dynamics of meme propagation within the SOLFUNMEME community.
|
| 125 |
-
- Inform the development of ZOS-based applications, such as decentralized meme engines or trading bots.
|
| 126 |
-
|
| 127 |
-
## Key Features
|
| 128 |
-
|
| 129 |
-
- **Rich Transaction Metadata**: Captures block times, slots, account balances, token transfers, and program logs for comprehensive analysis.
|
| 130 |
-
- **SFM-Centric**: Focuses on the SFM token (BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump), covering trades, account creations, and token movements.
|
| 131 |
-
- **Optimized for Reusability**: Caches Solana RPC responses to reduce query overhead and ensure reproducibility.
|
| 132 |
-
- **Verification-Ready**: Structured to integrate with formal methods tools (e.g., Lean) for proving properties like token conservation and balance consistency.
|
| 133 |
-
- **Community-Aligned**: Supports the SOLFUNMEME project’s mission to foster decentralized, user-driven meme ecosystems.
|
| 134 |
-
|
| 135 |
-
## Data Sources
|
| 136 |
-
|
| 137 |
-
The dataset is generated by querying Solana’s mainnet RPC endpoint (https://api.mainnet-beta.solana.com) using two core methods:
|
| 138 |
-
1. **getSignaturesForAddress**: Retrieves transaction signatures for the SFM token address, indexing a wide range of activities, including trades, transfers, and account operations.
|
| 139 |
-
2. **getTransaction**: Provides detailed transaction metadata, including:
|
| 140 |
-
- **Timing and Block Data**: Unix timestamps and Solana block heights (slots).
|
| 141 |
-
- **Account Balances**: SOL balances (in lamports) before and after transactions.
|
| 142 |
-
- **Token Balances**: Pre- and post-transaction balances for SFM and other tokens (e.g., Wrapped SOL).
|
| 143 |
-
- **Program Interactions**: Execution logs from programs like Raydium AMM, SPL Token Program, System Program, and Compute Budget Program.
|
| 144 |
-
- **Instructions**: Details of transaction instructions and nested inner instructions (e.g., token transfers within swaps).
|
| 145 |
-
|
| 146 |
-
## Dataset Contents
|
| 147 |
-
|
| 148 |
-
The dataset is organized as follows:
|
| 149 |
-
```
|
| 150 |
-
.
|
| 151 |
-
├── rpc_cache/
|
| 152 |
-
│ ├── method_getSignaturesForAddress_address_BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump_[hash].json
|
| 153 |
-
│ ├── method_getTransaction_signature_[signature].json
|
| 154 |
-
│ ├── temp_[cacheKey]_request.json
|
| 155 |
-
│ ├── temp_[cacheKey]_response.json
|
| 156 |
-
│ └── temp_[cacheKey]_error.txt
|
| 157 |
-
├── README.md
|
| 158 |
-
└── LICENSE
|
| 159 |
-
```
|
| 160 |
-
|
| 161 |
-
### rpc_cache/
|
| 162 |
-
- **method_getSignaturesForAddress_address_BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump_[hash].json**: Lists transaction signatures associated with the SFM token, serving as an index for further exploration.
|
| 163 |
-
- **method_getTransaction_signature_[signature].json**: Contains detailed transaction data, including metadata, balance changes, and program logs.
|
| 164 |
-
- **temp_*.json and temp_*.txt**: Temporary files storing request payloads, responses, and error logs for debugging and transparency.
|
| 165 |
-
- **README.md**: This file, providing an overview, usage instructions, and context.
|
| 166 |
-
- **LICENSE**: Specifies the terms of use for the dataset (e.g., MIT License).
|
| 167 |
-
|
| 168 |
-
## Data Structure
|
| 169 |
-
|
| 170 |
-
Each JSON file adheres to the Solana JSON-RPC 2.0 format, with key fields optimized for analysis:
|
| 171 |
-
- **result.blockTime**: Unix timestamp of the transaction.
|
| 172 |
-
- **result.slot**: Solana block height.
|
| 173 |
-
- **result.meta.preBalances** and **result.meta.postBalances**: SOL balances (in lamports) for accounts before and after the transaction.
|
| 174 |
-
- **result.meta.preTokenBalances** and **result.meta.postTokenBalances**: Token balances for SFM and other tokens, with fields:
|
| 175 |
-
- **accountIndex**: Index in the transaction’s account list.
|
| 176 |
-
- **mint**: Token mint address (e.g., BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump for SFM).
|
| 177 |
-
- **uiTokenAmount.amount**: Token amount in smallest units.
|
| 178 |
-
- **uiTokenAmount.uiAmountString**: Human-readable amount.
|
| 179 |
-
- **result.meta.logMessages**: Program execution logs, identifying interactions with Raydium, Token Program, etc.
|
| 180 |
-
- **result.transaction.message.instructions**: Instructions executed, including program IDs and account indices.
|
| 181 |
-
- **result.transaction.message.addressTableLookups**: Address table lookups for additional account resolution.
|
| 182 |
-
|
| 183 |
-
## Potential Use Cases
|
| 184 |
-
|
| 185 |
-
This dataset enables a range of applications:
|
| 186 |
-
- **Trading Pattern Analysis**: Identify buy and sell transactions by examining token balance changes, supporting studies of market dynamics and investor behavior.
|
| 187 |
-
- **Tokenomics Research**: Analyze SFM’s supply, liquidity, and trading volume to understand its role in the Solana meme coin ecosystem.
|
| 188 |
-
- **Formal Verification**: Use with Lean or other formal methods tools to prove transaction properties, such as non-negative balances or token conservation.
|
| 189 |
-
- **Community Mapping**: Study wallet interactions to uncover patterns of engagement within the SOLFUNMEME community, aligning with ZOS’s meme propagation goals.
|
| 190 |
-
- **DeFi Innovation**: Inform the development of ZOS-based tools, such as decentralized agents, trading algorithms, or governance mechanisms.
|
| 191 |
-
- **Educational Exploration**: Learn about Solana’s transaction model, DeFi protocols, and the intersection of blockchain and meme culture.
|
| 192 |
-
|
| 193 |
-
### Example Use Case: Identifying Trading Activity
|
| 194 |
-
|
| 195 |
-
A common use case is analyzing SFM trading activity on Raydium. For instance, a transaction might show an account gaining SFM tokens (indicating a buy) in exchange for Wrapped SOL, with the Raydium AMM program facilitating the swap. By comparing `preTokenBalances` and `postTokenBalances`, users can quantify token movements and correlate them with market trends or community activity.
|
| 196 |
-
|
| 197 |
-
## How to Use the Dataset
|
| 198 |
-
|
| 199 |
-
### Prerequisites
|
| 200 |
-
- Proficiency in JSON processing (e.g., Python, JavaScript, or Rust).
|
| 201 |
-
- Basic understanding of Solana’s transaction structure and DeFi concepts.
|
| 202 |
-
- Optional: Lean environment for formal verification or dataset extension.
|
| 203 |
-
|
| 204 |
-
### Getting Started
|
| 205 |
-
1. **Clone or Download the Repository**:
|
| 206 |
-
```bash
|
| 207 |
-
git clone https://huggingface.co/[your-username]/solfunmeme-transaction-cache
|
| 208 |
-
cd solfunmeme-transaction-cache
|
| 209 |
-
```
|
| 210 |
-
|
| 211 |
-
2. **Explore Transaction Data**:
|
| 212 |
-
- Navigate to `rpc_cache/` and inspect `method_getTransaction_signature_*.json` files.
|
| 213 |
-
- Use a script to filter transactions involving the Raydium AMM program (`675kPX9MHTjS2zt1qfr1NYHuzeLXfQM9H24wFSUt1Mp8`).
|
| 214 |
-
- Identify trading activity by checking token balance changes:
|
| 215 |
-
- **Buys**: SFM balance increases for an account.
|
| 216 |
-
- **Sells**: SFM balance decreases.
|
| 217 |
-
|
| 218 |
-
3. **Example Python Script**:
|
| 219 |
-
See `[read.py]`.
|
| 220 |
-
|
| 221 |
-
4. **Interpret Findings**:
|
| 222 |
-
- Buys reflect community engagement or investment in SFM’s Hyper-Pump Mechanism.
|
| 223 |
-
- Sells may indicate profit-taking or market adjustments.
|
| 224 |
-
- Aggregate data to derive insights into trading volume, liquidity, or wallet activity.
|
| 225 |
-
|
| 226 |
-
|
| 227 |
-
## Limitations
|
| 228 |
-
|
| 229 |
-
- **Temporal Scope**: The dataset reflects transactions up to the latest RPC query, typically limited to 1000 signatures per `getSignaturesForAddress` call. Continuous updates are needed for real-time analysis.
|
| 230 |
-
- **Liquidity Constraints**: SFM’s low liquidity on Raydium may result in sparse or volatile transaction data, affecting analysis depth.
|
| 231 |
-
- **Data Complexity**: Solana’s JSON-RPC responses are detailed and require parsing expertise to extract meaningful insights.
|
| 232 |
-
- **Temporary Files**: The `rpc_cache/` directory includes temporary files (`temp_*.json`, `temp_*.txt`) for debugging, which are not primary analysis targets.
|
| 233 |
-
|
| 234 |
-
## Contributing
|
| 235 |
-
|
| 236 |
-
We encourage contributions to enhance the dataset’s utility:
|
| 237 |
-
1. Fork this repository on Hugging Face.
|
| 238 |
-
2. Add new JSON caches, analysis scripts, or improved documentation.
|
| 239 |
-
3. Submit a pull request with a clear description of your changes.
|
| 240 |
-
4. For code contributions, update the `getSolfunmeme.lean` script on Codeberg and reference this dataset.
|
| 241 |
-
|
| 242 |
-
Please report issues or suggest features on Codeberg. Verified users (via wallet-signed transactions) can participate in the SOLFUNMEME DAO to shape the project’s future.
|
| 243 |
-
|
| 244 |
-
## License
|
| 245 |
-
|
| 246 |
-
This dataset is licensed under the MIT License (`LICENSE`), permitting free use, modification, and distribution, subject to the license terms.
|
| 247 |
-
|
| 248 |
-
## Contact
|
| 249 |
-
|
| 250 |
-
Engage with the SOLFUNMEME community:
|
| 251 |
-
- **Codeberg**: [https://codeberg.org/introspector/SOLFUNMEME](https://codeberg.org/introspector/SOLFUNMEME) (primary communication channel)
|
| 252 |
-
- **Discord**: [https://discord.gg/WASKdrBBzu](https://discord.gg/WASKdrBBzu)
|
| 253 |
-
- **Telegram**: [https://t.me/introsp3ctor](https://t.me/introsp3ctor)
|
| 254 |
-
- **Twitter (Official)**: [https://x.com/zos_sfm](https://x.com/zos_sfm)
|
| 255 |
-
- **Twitter (Developer)**: [https://twitter.com/introsp3ctor](https://twitter.com/introsp3ctor)
|
| 256 |
-
- **Website**: [https://solfunmeme.com](https://solfunmeme.com)
|
| 257 |
-
|
| 258 |
-
## Acknowledgments
|
| 259 |
-
|
| 260 |
-
- **James Michael DuPont (@introsp3ctor)**: Visionary behind SOLFUNMEME and the Zero Ontology System.
|
| 261 |
-
- **Solana Community**: For providing scalable blockchain infrastructure.
|
| 262 |
-
- **Lean Community**: For enabling formal verification of transaction data.
|
| 263 |
-
- **Hugging Face**: For hosting this open-access dataset.
|
| 264 |
-
|
| 265 |
-
This dataset empowers users to delve into the SOLFUNMEME ecosystem, uncovering insights into decentralized trading, meme propagation, and the innovative ZOS framework. Start exploring today!
|
|
|
|
| 18 |
- n>1M
|
| 19 |
size_categories_notes: We will have many more transactions
|
| 20 |
---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ReadmeMore.md
ADDED
|
@@ -0,0 +1,244 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# SOLFUNMEME Transaction Cache Dataset
|
| 2 |
+
|
| 3 |
+
Welcome to the SOLFUNMEME Transaction Cache Dataset hosted on Hugging Face! This repository contains a curated collection of JSON caches derived from Solana blockchain RPC queries for the SOLFUNMEME (SFM) token (BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump). The dataset encapsulates transaction metadata, token balance changes, and program interactions, providing a robust resource for exploring the trading dynamics, decentralized finance (DeFi) patterns, and community-driven meme propagation of SFM within the Solana ecosystem.
|
| 4 |
+
|
| 5 |
+
## Dataset Description
|
| 6 |
+
|
| 7 |
+
The SOLFUNMEME Transaction Cache Dataset is a structured archive of Solana transaction data designed to support research, development, and community engagement with the SFM token, a key element of the Zero Ontology System (ZOS). ZOS is a pioneering framework that blends meme coin mechanics with decentralized governance, self-hosted agents, and zero-knowledge machine learning (ZKML) on Solana’s high-throughput blockchain.
|
| 8 |
+
|
| 9 |
+
The dataset abstracts raw transaction data into JSON files, enabling users to:
|
| 10 |
+
- Analyze trading activities, such as buy and sell transactions, on platforms like Raydium.
|
| 11 |
+
- Investigate SFM’s tokenomics, liquidity trends, and market behavior.
|
| 12 |
+
- Apply formal verification techniques (e.g., Lean-based proofs) to ensure transaction integrity.
|
| 13 |
+
- Explore the social and economic dynamics of meme propagation within the SOLFUNMEME community.
|
| 14 |
+
- Inform the development of ZOS-based applications, such as decentralized meme engines or trading bots.
|
| 15 |
+
|
| 16 |
+
## Key Features
|
| 17 |
+
|
| 18 |
+
- **Rich Transaction Metadata**: Captures block times, slots, account balances, token transfers, and program logs for comprehensive analysis.
|
| 19 |
+
- **SFM-Centric**: Focuses on the SFM token (BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump), covering trades, account creations, and token movements.
|
| 20 |
+
- **Optimized for Reusability**: Caches Solana RPC responses to reduce query overhead and ensure reproducibility.
|
| 21 |
+
- **Verification-Ready**: Structured to integrate with formal methods tools (e.g., Lean) for proving properties like token conservation and balance consistency.
|
| 22 |
+
- **Community-Aligned**: Supports the SOLFUNMEME project’s mission to foster decentralized, user-driven meme ecosystems.
|
| 23 |
+
|
| 24 |
+
## Data Sources
|
| 25 |
+
|
| 26 |
+
The dataset is generated by querying Solana’s mainnet RPC endpoint (https://api.mainnet-beta.solana.com) using two core methods:
|
| 27 |
+
1. **getSignaturesForAddress**: Retrieves transaction signatures for the SFM token address, indexing a wide range of activities, including trades, transfers, and account operations.
|
| 28 |
+
2. **getTransaction**: Provides detailed transaction metadata, including:
|
| 29 |
+
- **Timing and Block Data**: Unix timestamps and Solana block heights (slots).
|
| 30 |
+
- **Account Balances**: SOL balances (in lamports) before and after transactions.
|
| 31 |
+
- **Token Balances**: Pre- and post-transaction balances for SFM and other tokens (e.g., Wrapped SOL).
|
| 32 |
+
- **Program Interactions**: Execution logs from programs like Raydium AMM, SPL Token Program, System Program, and Compute Budget Program.
|
| 33 |
+
- **Instructions**: Details of transaction instructions and nested inner instructions (e.g., token transfers within swaps).
|
| 34 |
+
|
| 35 |
+
## Dataset Contents
|
| 36 |
+
|
| 37 |
+
The dataset is organized as follows:
|
| 38 |
+
|
| 39 |
+
### rpc_cache/
|
| 40 |
+
- **method_getSignaturesForAddress_address_BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump_[hash].json**: Lists transaction signatures associated with the SFM token, serving as an index for further exploration.
|
| 41 |
+
- **method_getTransaction_signature_[signature].json**: Contains detailed transaction data, including metadata, balance changes, and program logs.
|
| 42 |
+
- **temp_*.json and temp_*.txt**: Temporary files storing request payloads, responses, and error logs for debugging and transparency.
|
| 43 |
+
- **README.md**: This file, providing an overview, usage instructions, and context.
|
| 44 |
+
- **LICENSE**: Specifies the terms of use for the dataset (e.g., MIT License).
|
| 45 |
+
|
| 46 |
+
## Data Structure
|
| 47 |
+
|
| 48 |
+
Each JSON file adheres to the Solana JSON-RPC 2.0 format, with key fields optimized for analysis:
|
| 49 |
+
- **result.blockTime**: Unix timestamp of the transaction.
|
| 50 |
+
- **result.slot**: Solana block height.
|
| 51 |
+
- **result.meta.preBalances** and **result.meta.postBalances**: SOL balances (in lamports) for accounts before and after the transaction.
|
| 52 |
+
- **result.meta.preTokenBalances** and **result.meta.postTokenBalances**: Token balances for SFM and other tokens, with fields:
|
| 53 |
+
- **accountIndex**: Index in the transaction’s account list.
|
| 54 |
+
- **mint**: Token mint address (e.g., BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump for SFM).
|
| 55 |
+
- **uiTokenAmount.amount**: Token amount in smallest units.
|
| 56 |
+
- **uiTokenAmount.uiAmountString**: Human-readable amount.
|
| 57 |
+
- **result.meta.logMessages**: Program execution logs, identifying interactions with Raydium, Token Program, etc.
|
| 58 |
+
- **result.transaction.message.instructions**: Instructions executed, including program IDs and account indices.
|
| 59 |
+
- **result.transaction.message.addressTableLookups**: Address table lookups for additional account resolution.
|
| 60 |
+
|
| 61 |
+
## Potential Use Cases
|
| 62 |
+
|
| 63 |
+
This dataset enables a range of applications:
|
| 64 |
+
- **Trading Pattern Analysis**: Identify buy and sell transactions by examining token balance changes, supporting studies of market dynamics and investor behavior.
|
| 65 |
+
- **Tokenomics Research**: Analyze SFM’s supply, liquidity, and trading volume to understand its role in the Solana meme coin ecosystem.
|
| 66 |
+
- **Formal Verification**: Use with Lean or other formal methods tools to prove transaction properties, such as non-negative balances or token conservation.
|
| 67 |
+
- **Community Mapping**: Study wallet interactions to uncover patterns of engagement within the SOLFUNMEME community, aligning with ZOS’s meme propagation goals.
|
| 68 |
+
- **DeFi Innovation**: Inform the development of ZOS-based tools, such as decentralized agents, trading algorithms, or governance mechanisms.
|
| 69 |
+
- **Educational Exploration**: Learn about Solana’s transaction model, DeFi protocols, and the intersection of blockchain and meme culture.
|
| 70 |
+
|
| 71 |
+
### Example Use Case: Identifying Trading Activity
|
| 72 |
+
|
| 73 |
+
A common use case is analyzing SFM trading activity on Raydium. For instance, a transaction might show an account gaining SFM tokens (indicating a buy) in exchange for Wrapped SOL, with the Raydium AMM program facilitating the swap. By comparing `preTokenBalances` and `postTokenBalances`, users can quantify token movements and correlate them with market trends or community activity.
|
| 74 |
+
|
| 75 |
+
## How to Use the Dataset
|
| 76 |
+
|
| 77 |
+
### Prerequisites
|
| 78 |
+
- Proficiency in JSON processing (e.g., Python, JavaScript, or Rust).
|
| 79 |
+
- Basic understanding of Solana’s transaction structure and DeFi concepts.
|
| 80 |
+
- Optional: Lean environment for formal verification or dataset extension.
|
| 81 |
+
|
| 82 |
+
### Getting Started
|
| 83 |
+
1. **Clone or Download the Repository**:
|
| 84 |
+
```bash
|
| 85 |
+
git clone https://huggingface.co/[your-username]/solfunmeme-transaction-cache
|
| 86 |
+
cd solfunmeme-transaction-cache
|
| 87 |
+
|
| 88 |
+
Here is the reformatted Markdown with proper heading levels:
|
| 89 |
+
|
| 90 |
+
```markdown
|
| 91 |
+
# SOLFUNMEME Transaction Cache Dataset
|
| 92 |
+
|
| 93 |
+
Welcome to the SOLFUNMEME Transaction Cache Dataset hosted on Hugging Face! This repository contains a curated collection of JSON caches derived from Solana blockchain RPC queries for the SOLFUNMEME (SFM) token (BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump). The dataset encapsulates transaction metadata, token balance changes, and program interactions, providing a robust resource for exploring the trading dynamics, decentralized finance (DeFi) patterns, and community-driven meme propagation of SFM within the Solana ecosystem.
|
| 94 |
+
|
| 95 |
+
## Dataset Description
|
| 96 |
+
|
| 97 |
+
The SOLFUNMEME Transaction Cache Dataset is a structured archive of Solana transaction data designed to support research, development, and community engagement with the SFM token, a key element of the Zero Ontology System (ZOS). ZOS is a pioneering framework that blends meme coin mechanics with decentralized governance, self-hosted agents, and zero-knowledge machine learning (ZKML) on Solana’s high-throughput blockchain.
|
| 98 |
+
|
| 99 |
+
The dataset abstracts raw transaction data into JSON files, enabling users to:
|
| 100 |
+
- Analyze trading activities, such as buy and sell transactions, on platforms like Raydium.
|
| 101 |
+
- Investigate SFM’s tokenomics, liquidity trends, and market behavior.
|
| 102 |
+
- Apply formal verification techniques (e.g., Lean-based proofs) to ensure transaction integrity.
|
| 103 |
+
- Explore the social and economic dynamics of meme propagation within the SOLFUNMEME community.
|
| 104 |
+
- Inform the development of ZOS-based applications, such as decentralized meme engines or trading bots.
|
| 105 |
+
|
| 106 |
+
## Key Features
|
| 107 |
+
|
| 108 |
+
- **Rich Transaction Metadata**: Captures block times, slots, account balances, token transfers, and program logs for comprehensive analysis.
|
| 109 |
+
- **SFM-Centric**: Focuses on the SFM token (BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump), covering trades, account creations, and token movements.
|
| 110 |
+
- **Optimized for Reusability**: Caches Solana RPC responses to reduce query overhead and ensure reproducibility.
|
| 111 |
+
- **Verification-Ready**: Structured to integrate with formal methods tools (e.g., Lean) for proving properties like token conservation and balance consistency.
|
| 112 |
+
- **Community-Aligned**: Supports the SOLFUNMEME project’s mission to foster decentralized, user-driven meme ecosystems.
|
| 113 |
+
|
| 114 |
+
## Data Sources
|
| 115 |
+
|
| 116 |
+
The dataset is generated by querying Solana’s mainnet RPC endpoint (https://api.mainnet-beta.solana.com) using two core methods:
|
| 117 |
+
1. **getSignaturesForAddress**: Retrieves transaction signatures for the SFM token address, indexing a wide range of activities, including trades, transfers, and account operations.
|
| 118 |
+
2. **getTransaction**: Provides detailed transaction metadata, including:
|
| 119 |
+
- **Timing and Block Data**: Unix timestamps and Solana block heights (slots).
|
| 120 |
+
- **Account Balances**: SOL balances (in lamports) before and after transactions.
|
| 121 |
+
- **Token Balances**: Pre- and post-transaction balances for SFM and other tokens (e.g., Wrapped SOL).
|
| 122 |
+
- **Program Interactions**: Execution logs from programs like Raydium AMM, SPL Token Program, System Program, and Compute Budget Program.
|
| 123 |
+
- **Instructions**: Details of transaction instructions and nested inner instructions (e.g., token transfers within swaps).
|
| 124 |
+
|
| 125 |
+
## Dataset Contents
|
| 126 |
+
|
| 127 |
+
The dataset is organized as follows:
|
| 128 |
+
```
|
| 129 |
+
.
|
| 130 |
+
├── rpc_cache/
|
| 131 |
+
│ ├── method_getSignaturesForAddress_address_BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump_[hash].json
|
| 132 |
+
│ ├── method_getTransaction_signature_[signature].json
|
| 133 |
+
│ ├── temp_[cacheKey]_request.json
|
| 134 |
+
│ ├── temp_[cacheKey]_response.json
|
| 135 |
+
│ └── temp_[cacheKey]_error.txt
|
| 136 |
+
├── README.md
|
| 137 |
+
└── LICENSE
|
| 138 |
+
```
|
| 139 |
+
|
| 140 |
+
### rpc_cache/
|
| 141 |
+
- **method_getSignaturesForAddress_address_BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump_[hash].json**: Lists transaction signatures associated with the SFM token, serving as an index for further exploration.
|
| 142 |
+
- **method_getTransaction_signature_[signature].json**: Contains detailed transaction data, including metadata, balance changes, and program logs.
|
| 143 |
+
- **temp_*.json and temp_*.txt**: Temporary files storing request payloads, responses, and error logs for debugging and transparency.
|
| 144 |
+
- **README.md**: This file, providing an overview, usage instructions, and context.
|
| 145 |
+
- **LICENSE**: Specifies the terms of use for the dataset (e.g., MIT License).
|
| 146 |
+
|
| 147 |
+
## Data Structure
|
| 148 |
+
|
| 149 |
+
Each JSON file adheres to the Solana JSON-RPC 2.0 format, with key fields optimized for analysis:
|
| 150 |
+
- **result.blockTime**: Unix timestamp of the transaction.
|
| 151 |
+
- **result.slot**: Solana block height.
|
| 152 |
+
- **result.meta.preBalances** and **result.meta.postBalances**: SOL balances (in lamports) for accounts before and after the transaction.
|
| 153 |
+
- **result.meta.preTokenBalances** and **result.meta.postTokenBalances**: Token balances for SFM and other tokens, with fields:
|
| 154 |
+
- **accountIndex**: Index in the transaction’s account list.
|
| 155 |
+
- **mint**: Token mint address (e.g., BwUTq7fS6sfUmHDwAiCQZ3asSiPEapW5zDrsbwtapump for SFM).
|
| 156 |
+
- **uiTokenAmount.amount**: Token amount in smallest units.
|
| 157 |
+
- **uiTokenAmount.uiAmountString**: Human-readable amount.
|
| 158 |
+
- **result.meta.logMessages**: Program execution logs, identifying interactions with Raydium, Token Program, etc.
|
| 159 |
+
- **result.transaction.message.instructions**: Instructions executed, including program IDs and account indices.
|
| 160 |
+
- **result.transaction.message.addressTableLookups**: Address table lookups for additional account resolution.
|
| 161 |
+
|
| 162 |
+
## Potential Use Cases
|
| 163 |
+
|
| 164 |
+
This dataset enables a range of applications:
|
| 165 |
+
- **Trading Pattern Analysis**: Identify buy and sell transactions by examining token balance changes, supporting studies of market dynamics and investor behavior.
|
| 166 |
+
- **Tokenomics Research**: Analyze SFM’s supply, liquidity, and trading volume to understand its role in the Solana meme coin ecosystem.
|
| 167 |
+
- **Formal Verification**: Use with Lean or other formal methods tools to prove transaction properties, such as non-negative balances or token conservation.
|
| 168 |
+
- **Community Mapping**: Study wallet interactions to uncover patterns of engagement within the SOLFUNMEME community, aligning with ZOS’s meme propagation goals.
|
| 169 |
+
- **DeFi Innovation**: Inform the development of ZOS-based tools, such as decentralized agents, trading algorithms, or governance mechanisms.
|
| 170 |
+
- **Educational Exploration**: Learn about Solana’s transaction model, DeFi protocols, and the intersection of blockchain and meme culture.
|
| 171 |
+
|
| 172 |
+
### Example Use Case: Identifying Trading Activity
|
| 173 |
+
|
| 174 |
+
A common use case is analyzing SFM trading activity on Raydium. For instance, a transaction might show an account gaining SFM tokens (indicating a buy) in exchange for Wrapped SOL, with the Raydium AMM program facilitating the swap. By comparing `preTokenBalances` and `postTokenBalances`, users can quantify token movements and correlate them with market trends or community activity.
|
| 175 |
+
|
| 176 |
+
## How to Use the Dataset
|
| 177 |
+
|
| 178 |
+
### Prerequisites
|
| 179 |
+
- Proficiency in JSON processing (e.g., Python, JavaScript, or Rust).
|
| 180 |
+
- Basic understanding of Solana’s transaction structure and DeFi concepts.
|
| 181 |
+
- Optional: Lean environment for formal verification or dataset extension.
|
| 182 |
+
|
| 183 |
+
### Getting Started
|
| 184 |
+
1. **Clone or Download the Repository**:
|
| 185 |
+
```bash
|
| 186 |
+
git clone https://huggingface.co/[your-username]/solfunmeme-transaction-cache
|
| 187 |
+
cd solfunmeme-transaction-cache
|
| 188 |
+
```
|
| 189 |
+
|
| 190 |
+
2. **Explore Transaction Data**:
|
| 191 |
+
- Navigate to `rpc_cache/` and inspect `method_getTransaction_signature_*.json` files.
|
| 192 |
+
- Use a script to filter transactions involving the Raydium AMM program (`675kPX9MHTjS2zt1qfr1NYHuzeLXfQM9H24wFSUt1Mp8`).
|
| 193 |
+
- Identify trading activity by checking token balance changes:
|
| 194 |
+
- **Buys**: SFM balance increases for an account.
|
| 195 |
+
- **Sells**: SFM balance decreases.
|
| 196 |
+
|
| 197 |
+
3. **Example Python Script**:
|
| 198 |
+
See `[read.py]`.
|
| 199 |
+
|
| 200 |
+
4. **Interpret Findings**:
|
| 201 |
+
- Buys reflect community engagement or investment in SFM’s Hyper-Pump Mechanism.
|
| 202 |
+
- Sells may indicate profit-taking or market adjustments.
|
| 203 |
+
- Aggregate data to derive insights into trading volume, liquidity, or wallet activity.
|
| 204 |
+
|
| 205 |
+
|
| 206 |
+
## Limitations
|
| 207 |
+
|
| 208 |
+
- **Temporal Scope**: The dataset reflects transactions up to the latest RPC query, typically limited to 1000 signatures per `getSignaturesForAddress` call. Continuous updates are needed for real-time analysis.
|
| 209 |
+
- **Liquidity Constraints**: SFM’s low liquidity on Raydium may result in sparse or volatile transaction data, affecting analysis depth.
|
| 210 |
+
- **Data Complexity**: Solana’s JSON-RPC responses are detailed and require parsing expertise to extract meaningful insights.
|
| 211 |
+
- **Temporary Files**: The `rpc_cache/` directory includes temporary files (`temp_*.json`, `temp_*.txt`) for debugging, which are not primary analysis targets.
|
| 212 |
+
|
| 213 |
+
## Contributing
|
| 214 |
+
|
| 215 |
+
We encourage contributions to enhance the dataset’s utility:
|
| 216 |
+
1. Fork this repository on Hugging Face.
|
| 217 |
+
2. Add new JSON caches, analysis scripts, or improved documentation.
|
| 218 |
+
3. Submit a pull request with a clear description of your changes.
|
| 219 |
+
4. For code contributions, update the `getSolfunmeme.lean` script on Codeberg and reference this dataset.
|
| 220 |
+
|
| 221 |
+
Please report issues or suggest features on Codeberg. Verified users (via wallet-signed transactions) can participate in the SOLFUNMEME DAO to shape the project’s future.
|
| 222 |
+
|
| 223 |
+
## License
|
| 224 |
+
|
| 225 |
+
This dataset is licensed under the MIT License (`LICENSE`), permitting free use, modification, and distribution, subject to the license terms.
|
| 226 |
+
|
| 227 |
+
## Contact
|
| 228 |
+
|
| 229 |
+
Engage with the SOLFUNMEME community:
|
| 230 |
+
- **Codeberg**: [https://codeberg.org/introspector/SOLFUNMEME](https://codeberg.org/introspector/SOLFUNMEME) (primary communication channel)
|
| 231 |
+
- **Discord**: [https://discord.gg/WASKdrBBzu](https://discord.gg/WASKdrBBzu)
|
| 232 |
+
- **Telegram**: [https://t.me/introsp3ctor](https://t.me/introsp3ctor)
|
| 233 |
+
- **Twitter (Official)**: [https://x.com/zos_sfm](https://x.com/zos_sfm)
|
| 234 |
+
- **Twitter (Developer)**: [https://twitter.com/introsp3ctor](https://twitter.com/introsp3ctor)
|
| 235 |
+
- **Website**: [https://solfunmeme.com](https://solfunmeme.com)
|
| 236 |
+
|
| 237 |
+
## Acknowledgments
|
| 238 |
+
|
| 239 |
+
- **James Michael DuPont (@introsp3ctor)**: Visionary behind SOLFUNMEME and the Zero Ontology System.
|
| 240 |
+
- **Solana Community**: For providing scalable blockchain infrastructure.
|
| 241 |
+
- **Lean Community**: For enabling formal verification of transaction data.
|
| 242 |
+
- **Hugging Face**: For hosting this open-access dataset.
|
| 243 |
+
|
| 244 |
+
This dataset empowers users to delve into the SOLFUNMEME ecosystem, uncovering insights into decentralized trading, meme propagation, and the innovative ZOS framework. Start exploring today!
|