Send funds to a handle via cloud wallet!

Always great to see: - new community projects - XCHandles support across the ecosystem 💚

very hard to price tokens without an AMM is my guess 😅

The reward distributor codebase has gone through many reviews, both by humans and agents. Some time ago, I asked @Rigidity16 for one such review of the code for CATalog. On May 5, 2026, he spotted a bug related to how the refund process works - the process of asserting a slot existed was itself flawed, and allowed someone to 'prove' that arbitrary slots existed. I quickly realized this extended beyond CATalog to XCHandles and the reward distributor. This was well before XCHandles was deployed. The only at-risk dApp was the DataLayer Minions reward distributor, which used the pattern when starting a new epoch. Fortunately, the action is only executable on August 29 each year, which gave us more than enough time to prepare for a recovery. On August 29, 2026, I successfully forged an epoch slot and was able to recover 100% of the DIG locked in the distributor. The DIG that was allocated to staked NFTs but not claimed by their owners yet will be sent to the appropriate addresses at a later date. The remaining DIG will be used to seed 19 years of rewards for the new distributor. Rewards will be added on Monday to give everyone time to migrate. Given recent developments, the codebases for the reward distributor, XCHandles, and CATalog have also been recently scanned by the latest models, including Daybreak Blue and Fable 5/5.1. I would also like to give a special thanks to @hadamcik , who was the first to use Daybreak Blue to audit the code and privately sent me his findings. Those findings included two viable attack paths, both of which have now been patched. The action layer CHIP contains a warning about the insecure 'slot oracle' pattern along with the fix (having each slot also store a counter). Thank you to everyone for migrating promptly, as well as everyone who helped review and secure the code.