https://github.com/0xagil/altcha-solver
Altcha POW Challenge Solver
https://github.com/0xagil/altcha-solver
altcha pow-captcha solver
Last synced: 2 months ago
JSON representation
Altcha POW Challenge Solver
- Host: GitHub
- URL: https://github.com/0xagil/altcha-solver
- Owner: 0xagil
- Created: 2024-11-05T13:24:09.000Z (7 months ago)
- Default Branch: master
- Last Pushed: 2024-11-05T13:25:15.000Z (7 months ago)
- Last Synced: 2025-03-26T12:09:26.840Z (2 months ago)
- Topics: altcha, pow-captcha, solver
- Homepage:
- Size: 0 Bytes
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Altcha - SHA-256 Challenge Solver
A high-performance Go implementation of a bidirectional hash challenge solver using parallel processing to find a number that, when combined with a salt and hashed with SHA-256, produces a specific target hash.
## Features
- Bidirectional search (searches from both ends simultaneously)
- Parallel processing with configurable number of workers
- Automatic workload distribution among workers
## How It Works
The solver employs two main strategies:
1. **Bidirectional Search**: Splits the search space into two parts:
- Forward workers search from 0 → middle
- Backward workers search from maxNumber → middle
2. **Parallel Processing**:
- Uses 20 workers (10 forward + 10 backward)
- Each worker handles a specific range of numbers
- First found solution terminates all searches
## Usage
```go
challenge := Challenge{
Algorithm: "SHA-256",
Challenge: "",
MaxNumber: 150000,
Salt: "",
}
result := solveChallenge(challenge)
```
## Perfomance
The official documentation states the following benchmarks for complexity of 100,000:
| Device | Performance | Time to Solve |
|--------|------------|---------------|
| MacBook Pro M3-Pro (2023) | 3 ops/s | 0.33 sec |
| iPhone 12 mini (2020) | 1.2 ops/s | 0.83 sec |
| AWS EC2 (c6a.xlarge) | 1 ops/s | 1 sec |
| Samsung Galaxy A14 (2023) | 0.4 ops/s | 2.5 sec |
| AWS Lambda (1GB) | 0.12 ops/s | 8 sec |
My implementation needs only ~8ms