Introduction

About

A powerful command-line interface for interacting with the BLENDER smart contract on the Pepe Unchained blockchain.

After using this interface, the linkage between the sender and the recipient will be broken, ensuring enhanced privacy and security during transactions.

Features

Secure deposit with a unique secret hash
Withdrawal using a secret key
Easy setup and quick start
Compatibility with Pepe L2
Enhanced logging with stylish outputs
Privacy-focused transactions with broken sender-recipient linkage
Easy integration with existing blockchain applications
Real-time monitoring of deposit and withdrawal activities
Detailed event logs for transparency and troubleshooting

Frequently Asked Questions

Q: What is the Blender CLI tool?
A: It’s a command-line interface for interacting with the Blender smart contract on Pepe Unchained blockchain, enabling secure PEPU token deposits and withdrawals.

Q: Is there a mobile version of the CLI tool? A: No, the CLI is designed for desktop environments (Windows/macOS/Linux) only.

Q: Who maintains this project?
A: The GenesisLab Development Team maintains this open-source project with community contributions.

Q: Does Blender support other blockchains? A: Currently, it only operates on the Pepe Unchained blockchain. Cross-chain functionality may be added in future updates.

Q: What happens if I lose my secret?
A: After 30 days, unclaimed deposits can be refunded to the original address using the refund function.

Q: Can I use a hardware wallet?
A: Not directly - current implementation requires private key in .env. For security, use dedicated wallet with minimal funds.

Technical Questions

Q: How are deposits secured?
A: Each deposit generates a unique cryptographic secret hash using keccak256, ensuring only the secret holder can withdraw funds.

Q: Are there deposit limits? A: No quantity limits, but amounts must match exact tiers (100/1k/10k/100k/1M PEPU).

Q: How do I update the CLI? A: Run git pull in the installation directory, then pnpm install to update dependencies.

Q: Where are wallet credentials stored?
A: Private keys are never stored - only read from .env file at runtime. The CLI has no internal storage mechanism.

Q: Why display balances before/after transactions?
A: The displayBalances() function shows real-time PEPU/BLENDER changes, helping verify successful operations.

Q: How are secrets generated?
A: Using ethers.utils.randomBytes(32) for cryptographically secure randomness, then hashed with keccak256 per contract requirements.

Q: How to change recipient address?
A: Update RECIPIENT_ADDRESS in .env - withdrawals always send to this address through withdraw() function parameter.

Troubleshooting

Q: Why is my transaction failing?
Common issues:

Insufficient BLENDER tokens for fees (requires 1000 BLENDER)
Invalid deposit amount (must be 100/1k/10k/100k/1M PEPU)
Incorrect RPC endpoint in .env

Q: Where are my secrets stored?
A: Secrets are saved locally in secrets.json - back up this file securely.

Q: What happens if .env is missing values?
A: CLI crashes immediately with “Cannot read properties of undefined” - always verify all .env variables are set before launching.

Project Support

Q: How can I contribute?
A: Submit pull requests or report issues on our GitHub repository.

Q: Where can I get help?
A: For technical support, email blender4pepu@proton.me with detailed error logs.

Prerequisites

Ensure you have the following installed:

Node.js: A JavaScript runtime for building and running the application.
pnpm: A fast, disk space-efficient package manager.
git: A distributed version control system for managing source code.

Installation

Clone the repository and install dependencies:

# Clone the repository
git clone https://github.com/Blender4Pepu/blender_cli.git
cd blender-cli

# Install dependencies
pnpm install

# Create a .env file
cp .env.example .env

Environment Variables

Ensure your .env file is correctly set up:

# Fixed Values
RPC_URL="https://rpc-pepe-unchained-gupg0lo9wf.t.conduit.xyz"
TOKEN_ADDRESS="0x0afB32Dc4CC0595654DC71A61a3132b3d90538f9"
CONTRACT_ADDRESS="0x8D0FE0b5D53378AF6dA4015F57B4932e5dB42e2d"

# User Parameters
PRIVATE_KEY=""
RECIPIENT_ADDRESS="0x..."

Start CLI

Start the CLI with:

node index.js

1 — Deposit: Make a deposit in PEPU with a secret hash.
2 — Withdraw: Withdraw deposited funds using a secret.
0 — Exit: Close the CLI.

Deposit Tokens (Mix)

Select 1 — Deposit.
Enter the deposit amount (Valid: 100, 1000, 10000, 100000, 1000000 PEPU).
The CLI will:
- Verify your BLENDER balance for the fee.
- Approve the fee transfer if necessary.
- Generate a unique secret and hash.
- Perform the deposit transaction.
Upon success, your secret and hashed secret will be displayed and saved.

Note: Keep your secret safe! It is required for withdrawal.

Overview

Key Functions

deposit() - Handles deposit with a hashed secret and ensures fee payment.
withdraw() - Allows withdrawal if the correct secret is provided.

Utility Functions

saveSecret() - Safely stores secret information locally.
logSuccess() - Outputs a styled success message.
logError() - Outputs a styled error message.

Example Output

🔮 Blender CLI

1 — Deposit
2 — Withdraw
0 — Exit

➡️  Your choice: 1

Enter deposit amount in PEPU: 100
✅ Deposit successful! TX: 0xabc123...

Contract Details

Constants

uint256 public constant FEE_AMOUNT = 1000 * 10 ** 18;

FEE_AMOUNT: Fixed fee for each deposit in BLENDER tokens (1000 BLENDER).

State Variables

IERC20 public immutable blenderToken;

blenderToken: ERC-20 token used for transaction fees.

mapping(bytes32 => Deposit) public deposits;

deposits: Maps the hashed secret to a Deposit structure.

Deposit Structure

struct Deposit {
    uint256 amount;
    bytes32 hashedSecret;
    uint256 createdAt;
    bool spent;
}

amount: Amount of PEPU deposited.
hashedSecret: Hash of the secret used for withdrawal.
createdAt: Timestamp of the deposit.
spent: Status indicating whether the deposit has been withdrawn or refunded.

Functions

Constructor

constructor(address _blenderToken, address _initialOwner) Ownable(_initialOwner)

_blenderToken: Address of the BLENDER token contract.
_initialOwner: Address of the contract owner.

Initializes the contract with the BLENDER token address and the owner address.

`deposit(bytes32 hashedSecret)`

function deposit(bytes32 hashedSecret) external payable

hashedSecret: Keccak256 hash of the secret required for withdrawal.

Requirements:

Deposit amount must be one of the fixed options (100, 1000, 10000, 100000, or 1000000 ETH).
User must pay 1000 BLENDER tokens as a fee.
The hashed secret must be unique (not previously used).

Emits:

Deposited event on successful deposit.

`withdraw(bytes calldata secret, address payable recipient)`

function withdraw(bytes calldata secret, address payable recipient) external

secret: Original secret used to generate the deposit hash.
recipient: Address where the ETH will be sent.

Requirements:

The provided secret must match the stored hashedSecret.
Deposit must not be already spent.
The recipient address must be valid.

Emits:

Withdrawn event on successful withdrawal.

`refund(bytes32 hashedSecret)`

function refund(bytes32 hashedSecret) external

hashedSecret: Hash of the secret associated with the deposit.

Requirements:

Refund is only available after 30 days from the deposit time.
The deposit must not be already spent.

Emits:

Refunded event on successful refund.

Events

Deposit Event

event Deposited(bytes32 indexed hashedSecret, uint256 amount);

Emitted when a new deposit is made.

Withdraw Event

event Withdrawn(address indexed recipient, uint256 amount);

Emitted when a successful withdrawal is processed.

Refund Event

event Refunded(bytes32 indexed hashedSecret, address to);

Emitted when a refund is issued.

Considerations

Ensure your PRIVATE_KEY is kept secret.
DO NOT share your secret used for withdrawals.
Back up your secrets.json file securely.

Blender Book

Introduction

About

Features

Frequently Asked Questions

General Questions

Technical Questions

Troubleshooting

Project Support

Prerequisites

Installation

Environment Variables

Start CLI

Main Menu

Deposit Tokens (Mix)

Overview

Key Functions

Utility Functions

Example Output

Contract Details

Constants

State Variables

Deposit Structure

Functions

Constructor

`deposit(bytes32 hashedSecret)`

Requirements:

`withdraw(bytes calldata secret, address payable recipient)`

Requirements:

`refund(bytes32 hashedSecret)`

Requirements:

Events

Deposit Event

Withdraw Event

Refund Event

Considerations