No description
Find a file
openhands b7260b2eaf chore: analysis tooling, research artifacts, and code quality
- Analysis: parameter sweep scripts, adversarial testing, 2D frontier maps
- Research: KRAIKEN_RESEARCH_REPORT, SECURITY_REVIEW, STORAGE_LAYOUT
- FuzzingBase: consolidated fuzzing helper, BackgroundLP simulation
- Sweep results: CSV data for full 4D sweep (1050 combos), bull-bear,
  AS sweep, VWAP fix validation
- Code quality: .gitignore for fuzz CSVs, gas snapshot, updated docs
- Remove dead analysis helpers (CSVHelper, CSVManager, ScenarioRecorder)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-13 18:22:03 +00:00
.claude feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
.husky feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
.woodpecker refactor: consolidate CI and local dev orchestration (#108) 2026-02-03 12:07:28 +01:00
containers feat: add Otterscan block explorer to dev environment (#109) 2026-02-13 14:55:07 +00:00
docker refactor: consolidate CI and local dev orchestration (#108) 2026-02-03 12:07:28 +01:00
docs feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
kraiken-lib feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
landing feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
onchain chore: analysis tooling, research artifacts, and code quality 2026-02-13 18:22:03 +00:00
scripts feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
services feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
tests feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
web-app feat: protocol stats display + parameter sweep fuzzing infrastructure (#106) 2026-02-13 18:09:11 +00:00
.claude-code-supervisor.yml feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
.dockerignore feature/ci (#84) 2026-02-02 19:24:57 +01:00
.gitignore tax rate, version and compose (#70) 2025-10-07 19:26:08 +02:00
.gitmodules chore: remove unused pt-v5-twab-controller submodule (54MB) 2026-02-13 14:37:20 +00:00
AGENTS.md feat: add Otterscan block explorer to dev environment (#109) 2026-02-13 14:55:07 +00:00
CLAUDE.md feat: add ABI validation helpers for Ponder (#29) 2025-09-30 20:02:43 +02:00
docker-compose.yml feat: add Otterscan block explorer to dev environment (#109) 2026-02-13 14:55:07 +00:00
HARBERG.md added web-app and landing 2025-09-23 14:18:04 +02:00
package-lock.json improve web-app config 2025-10-11 10:55:49 +00:00
package.json first integration tests (#64) 2025-10-05 19:40:14 +02:00
playwright.config.ts feature/ci (#84) 2026-02-02 19:24:57 +01:00
README.md Update README.md 2025-09-22 15:38:29 +02:00
TECHNICAL_APPENDIX.md feat: OptimizerV3 with direct 2D staking-to-LP parameter mapping 2026-02-13 18:21:18 +00:00
VERSION_VALIDATION.md refactor: consolidate CI and local dev orchestration (#108) 2026-02-03 12:07:28 +01:00

$HRB is a gig to become successful in DeFi. It is a protocol that implements the fairest ponzi in the world.

This repository structures our approach and manages our collaboration to achieve this goal.

Project Milestones

The fairest ponzi in the world will be launched in 3 stages, each representing a more advanced version of the previous one.

  1. Harberg - a staking market and an speculative laverage platform.
  2. KrAIken - Harberg, but token issuance is governed by an automated liquidity manager.
  3. SoverAIgns - KrAIKen, but the liquidity manager is augmented by AI and deliveres outlandish performance

Project Values and Organization

  • the core value and mantra of the project is: ship, ship, 🚢
  • delivery is valued highest and goes over quality or communication
  • if you see work, do it. most likely every-one but you will lose interest in the project, and you will deliver it by yourself. work this way, take responsibility for everything. document everything methodically in this repository, use .md files, commits, issues(feature request, support issue), and pull requests. if other people still follow this repository collaboration will emerge, and duplication of work will be avoided automatically.
  • no structured communication outside of this repository is relevant for the success, nor will it be rewarded.

open questions

  • multisig? keyholders?
  • payout, shares?

Revenue Sources

  • the tax paid by the stakers will be forwarded to the multisig
  • the liquidity manager contract will collect all liquidity fees and forward them to the multisig
  • at launch of each stage of the project the keyholders will invest a share of the multisig holdings and coordinate to sell at a favorable time. all profits from all sales are the multisigs profits.

Timeline

it would be great if we can launch stage 1 or even 2 for DevCon.

Kick-off Call Harberg

Agenda