recMEV Installer

This repository contains the installation package for recMEV.

Overview

recMEV installer package provides an automated way to install the recMEV binary on your system. Currently available for:

• macOS
• Linux

The installer places the binary in the system binary directory (/usr/local/bin)

Components

• recmev-v0.18.23-mac: macOS binary
• recmev-v0.18.23-linux: Linux binary
• install.sh: Installation script with platform detection

Installation

Option 1: One-Line Installation (Recommended)

Install recMEV with a single command:

sh -c "$(curl -sSfL https://raw.githubusercontent.com/RECTOR-LABS/recMEV-installer/main/install.sh)"

This method will:

• Create necessary configuration directories
• Download and install the appropriate binary for your system

Option 2: Direct Script Execution

If you've cloned the repository or downloaded the install script:

./install.sh

Option 3: Manual Installation

For users who prefer to perform the installation steps manually:

# Create config directory if it doesn't exist
mkdir -p ~/.recmev

# Download binary (replace OS with either 'linux' or 'mac' based on your system)
curl -fsSL https://raw.githubusercontent.com/RECTOR-LABS/recMEV-installer/v0.18.23/recmev-v0.18.23-OS -o recmev

# Install binary
chmod +x recmev
sudo mv recmev /usr/local/bin/recmev

Installing Specific Versions

To install a specific version of recMEV, you'll need to modify the version number in the installation URL. For example, to install version v0.5.0:

sh -c "$(curl -sSfL https://raw.githubusercontent.com/RECTOR-LABS/recMEV-installer/v0.16.25/install.sh)"

Available versions:

• 0.18.23 - Enhanced token cache system with unified database integration, updated Supabase table references to token_mints, improved token lookup mechanisms, and comprehensive documentation updates for better consistency
• v0.18.22 - Enhanced installation and update system with improved user interaction, comprehensive PATH guidance, and streamlined uninstall process with direct sudo execution
• v0.18.21 - Enhanced cross-compilation infrastructure with improved build system, platform detection, and streamlined uninstall process with better error handling
• v0.18.20 - Streamlined project structure with removal of discover command functionality for improved maintainability and reduced codebase complexity
• v0.18.17 - Major modular configuration system refactoring, enhanced development infrastructure with automated documentation, comprehensive pre-commit hooks, and removal of deprecated database functionality for streamlined architecture
• v0.18.12 - Enhanced development infrastructure with pre-commit hooks, advanced configuration management with Supabase integration, modular help documentation system, and major code refactoring for improved organization
• v0.18.7 - comprehensive help documentation system, and major code refactoring for improved organization
• v0.17.16 - Enhance error handling for wallet accounts commands, improve help message formatting and examples.
• v0.17.15 - Enhanced uninstall command, improved logs with filtering options, and rate-limited transaction history
• v0.17.10 - Version tracking system with build timestamps and enhanced logging functionality
• v0.17.9 - Multi-wallet support with encrypted storage and enhanced security
• v0.16.25 - Session-based wallet authentication and Jupiter v1 API integration
• v0.16.21 - Real transaction handling and price lookups via Jupiter API
• v0.16.3 - Enhanced CLI Logic
• v0.15.14 - Enhanced report command with time filtering and improved terminal UI
• v0.15.13 - Enhanced encryption capabilities and improved wallet security
• v0.15.9 - Improved config command and enhanced logging system
• v0.15.7 - Enhanced stability and performance improvements
• v0.15.6 - Enhanced stability and performance improvements
• v0.15.4 - Shell completion support and version management
• v0.13.10 - Enhanced stability and performance improvements
• v0.13.9 - Bug fixes and stability improvements
• v0.13.8 - Bug fixes and stability improvements
• v0.13.5 - Jupiter DEX integration for token swaps
• v0.13.4 - Enhanced DEX integration and performance improvements
• v0.12.0 - Jupiter DEX integration
• v0.11.0 - Pure Rust TLS implementation
• v0.9.4 - Bug fixes and stability improvements
• v0.9.2 - Enhanced error handling and reporting
• v0.9.1 - Transaction optimization
• v0.9.0 - Major performance improvements
• v0.8.1 - Configuration system update
• v0.7.1 - Transaction batch processing
• v0.6.2 - Stability improvements and bug fixes
• v0.5.6 - Blockchain transaction optimizations
• v0.5.5 - Enhanced monitoring capabilities
• v0.5.4 - Config file format updates
• v0.5.3 - Performance improvements for large transactions
• v0.5.1 - CLI enhancement for readability
• v0.5.0 - First stable release with core functionality
• v0.4.0 - Transaction subsystem complete
• v0.3.5 - Transaction signing improvements
• v0.3.4 - Enhanced logging capabilities
• v0.3.3 - Bug fixes and stability improvements
• v0.3.2 - Configuration enhancements
• v0.3.1 - Improved error messages
• v0.2.4 - CLI interface improvements
• v0.2.3 - Bug fixes and performance enhancements
• v0.2.2 - Configuration system updates
• v0.2.1 - Minor bug fixes and improvements
• v0.2.0 - Redesigned architecture
• v0.1.3 - Initial transaction support
• v0.1.2 - Basic CLI functionality
• v0.1.1 - Bug fixes and improvements
• v0.1.0 - Initial alpha release

You can find all available release versions on our GitHub releases page.

Uninstallation

You can uninstall recMEV using the following commands:

# Basic uninstallation (keeps logs and config)
recmev uninstall

# Full uninstallation (removes all data including logs and config)
recmev uninstall --all

Platform-specific uninstallation notes:

• Both Linux and macOS: Files in system directories like /usr/local/bin require sudo privileges to remove
• The uninstall command will automatically attempt to use sudo if available without password
• If automatic sudo fails, you'll need to use explicit sudo:

# For Linux and macOS
sudo recmev uninstall --all

macOS note: On macOS, the system may prompt for your password when attempting to remove files from /usr/local/bin. This is normal behavior, as these directories are protected by the system.

Manual Uninstallation

If you need to manually uninstall recMEV, follow these steps:

1. Remove the binary:

sudo rm /usr/local/bin/recmev

2. Remove configuration files (optional):

rm -rf ~/.recmev

3. Remove log files (optional):

rm -rf ~/.recmev/logs

4. Remove cache files (optional):

rm -rf ~/.recmev/cache

5. Remove shell completions (if installed):

# Bash
rm ~/.recmev/completion/recmev.bash

# Zsh
rm ~/.recmev/completion/_recmev

# Fish
rm ~/.recmev/fish/completions/recmev.fish

Note: The exact paths may vary slightly depending on your system configuration and installation method.

Post-Installation Verification

After installation, verify that recMEV was installed correctly:

recmev --help

Security

The installation process includes several security measures:

1. HTTPS downloads from trusted sources
2. Secure temporary directory handling
3. System-wide installation with proper permissions

Development

For local development and testing of the installer:

# Set the local development flag
RECMEV_INSTALLER_LOCAL=1 ./install.sh

Platform Notes

The installer automatically detects your operating system and will:

• Install the appropriate binary for Linux or macOS systems
• Exit with an error on unsupported platforms

Troubleshooting

Common issues and solutions:

1. Permission denied

   chmod +x ./install.sh  # Make the script executable

2. Download failed

   • Ensure you have a stable internet connection
   • Try downloading the files again
   • Verify your system is supported (Linux or macOS)

3. Binary not found after installation

   • Ensure /usr/local/bin is in your PATH
   • Try running echo $PATH to verify
   • Try running which recmev to locate the binary

Shell Completions

recMEV supports shell completions for Bash, Zsh, and Fish shells. The installer automatically:

1. Generates completion scripts using the completions command
2. Stores them in ~/.recmev/completion/
3. Attempts to automatically configure completions for your current shell

Manual Generation and Setup

You can also manually generate completion scripts using the completions command:

# Generate completions for your preferred shell
recmev completions bash                          # Generate to current directory
recmev completions zsh -o ~/.zsh/completions     # Generate to specific directory
recmev completions fish -o ~/.config/fish/completions

If automatic setup fails or if you want to manually enable completions:

Bash

Add the following to your ~/.bashrc or ~/.bash_profile:

[ -f ~/.recmev/completion/recmev.bash ] && source ~/.recmev/completion/recmev.bash

Zsh

Add the following to your ~/.zshrc:

# Add recmev completions dir to fpath
fpath=(~/.recmev/completion $fpath)
autoload -U compinit && compinit

Fish

Link the completion file to your Fish completions directory:

ln -sf ~/.recmev/fish/completions/recmev.fish ~/.config/fish/completions/recmev.fish

Testing Completions

After enabling completions and restarting your shell (or sourcing your profile), you can test them by typing:

recmev <TAB>

This should display available commands and options.

Support

For issues, feature requests, or contributions:

• Open an issue on our GitHub repository
• Submit a pull request
• Check existing issues for solutions

License

recMEV Non-Commercial License v1.0. For personal, research, or educational purposes only. See LICENSE file for details.