johba/harb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
harb/docs
History
openhands 9b75817300 fix: SECURITY_REVIEW.md references obsolete recenterAccess pattern (#838) 
- Update M-3 finding: recenterAccess was removed; MIN_RECENTER_INTERVAL
  (60s) cooldown now enforced unconditionally — downgrade severity to
  Informational (resolved)
- Update Access Control Summary: remove recenterAccess rows, reflect
  permissionless recenter() with cooldown
- Update Conclusion: mark M-3 as resolved
- Fix stale M-1 impact note that mentioned recenterAccess as a workaround
- deployment.md: remove Section 3.2 "Set Recenter Access" (setRecenterAccess
  no longer exists); update 3.3 first-recenter comment
- deployment.md: replace recenterAccess() verification call with
  lastRecenterTime() check
- deployment.md §6.1: rewrite Pause Recentering note — no access-control
  switch exists, cooldown is the only rate limiter
- deployment.md §6.5: remove stale setRecenterAccess(0xdEaD) instruction

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-16 14:43:37 +00:00
..
technical fix: SECURITY_REVIEW.md references obsolete recenterAccess pattern (#838) 2026-03-16 14:43:37 +00:00
ARCHITECTURE.md fix: Hardcoded TWAP/cooldown values not documented (#825) 2026-03-15 19:51:52 +00:00
ci-pipeline.md fix: Housekeeping: remove tracked logs/review.log + fix stale CI URL in docs (#187) 2026-02-23 11:30:37 +00:00
codeberg-api.md fix: Clean up dead code and stale domain references across landing + web-app (#189) 2026-02-23 13:04:02 +00:00
dev-environment.md fix: refactor AGENTS.md into progressive-disclosure structure (#184) 2026-02-23 09:46:35 +00:00
ENVIRONMENT.md fix: red-team.sh sudo strips FORK_URL before docker compose sees it (#729) 2026-03-14 08:30:49 +00:00
getting-started.md docs: layered information architecture (#140) (#163) 2026-02-20 09:01:11 +01:00
how-it-works.md docs: layered information architecture (#140) (#163) 2026-02-20 09:01:11 +01:00
mainnet-bootstrap.md fix: address review feedback on mainnet-bootstrap runbook (#728) 2026-03-14 18:35:48 +00:00
PRODUCT-TRUTH.md fix: Hardcoded TWAP/cooldown values not documented (#825) 2026-03-15 19:51:52 +00:00
README.md docs: layered information architecture (#140) (#163) 2026-02-20 09:01:11 +01:00
testing.md fix: refactor AGENTS.md into progressive-disclosure structure (#184) 2026-02-23 09:46:35 +00:00
UX-DECISIONS.md fix: remove staking references from landing page 2026-02-22 16:49:02 +00:00

README.md

KrAIken (Harb)

A token system where your tokens earn for you — backed by real ETH, governed by transparent on-chain rules.

What is it?

KRK is a token on Base (Ethereum L2). When you hold KRK tokens, they're backed by ETH in a trading vault — there's a built-in minimum value your tokens can't drop below.

You can stake your tokens to earn a share of every trade. The longer you stake, the more you accumulate. But there's a twist: someone else can challenge your position by committing to a higher earning rate. If that happens, you get compensated at market value — you never lose money, you just get bought out.

The system adjusts itself automatically based on how people are staking. No manual intervention, no hidden operators. Everything is on-chain and verifiable.

Quick Links

Key Numbers

  • 20,000 staking positions available (20% of total supply)
  • 30 earning rate tiers from 1% to 97% yearly
  • 3-day minimum hold before a position can be challenged
  • ETH-backed floor price — your tokens always have a minimum value

Is it safe?

The contracts are not yet audited. The code is open source and deployed on Base. Use at your own risk, and never invest more than you can afford to lose.