@btcbattle

BATTLEFIELD: Security Incident, and Why We're Hibernating I want to be straight with you, because you deserve that. What happened. An admin wallet connected to our Weekly Rewards contract was compromised. We rotated keys immediately to contain the exposure. The trade-off: the key that controls reward distribution on the current contract is no longer usable. That means Week 18 rewards cannot be distributed on this contract. What is NOT affected — your past rewards are safe. Weeks 14 through 17 were already finalized on-chain. Claiming does not depend on any admin key. If you have unclaimed rewards from those weeks, they are still there and still yours — please claim them: https://farcaster.xyz/miniapps/5kLec5hSq3bP/battlefield No user wallets were targeted. This was an operational/admin wallet issue on a testnet contract. Why I'm pausing instead of patching. Honestly: I'm overloaded with other commitments right now, and BATTLEFIELD needs a proper, secure rebuild — not a rushed patch on a foundation I no longer trust. Doing it badly would be worse than pausing it openly. So I'm putting the project into hibernation. If I come back. It would be a clean start on fresh, audited-pattern contracts with real key hygiene, plus the things this run taught me: - A reworked Battle Shop - tBATTLE futures reconsidered (scrapped in its current form, the allocation reserved) - A dedicated emergency reserve for weekly rewards so a single compromised key can never freeze distributions again - The whole feature set tightened up No timeline promises. I'd rather under-promise here. Thank you. To everyone who picked an army and fought week after week — it genuinely meant a lot. This is a pause done honestly, not a disappearance. Claim what you've earned, and I'll communicate clearly if anything changes. — [founder]

1 reply

1 recast

4 reactions