PhiloNauta
5.4K posts
@Philo_Nauta
Circle Lead - Governance Development Circle in @Xerberus_io DAO LLC - Governance, DAOs and DeSci. MSc in Philosophy of Science, Technology and Society.
How important was risk mitigation in the design of Frankencoin? Today, Managing Director of the Frankencoin Association @jonk93 will join @snj_peters from @xerberus, which are building the risk-rating standard for digital assets, for a talk about what makes Frankencoin currently lead their pools ratings. 5 PM CET on the @xerberus X account
Sprint Recap – WebApp V3.5.0 This sprint brings the Systemic Risk Graph, giving every dendrogram page a new way to visualise how risk connects across assets, pools, protocols, and organisations. We’ve also added a new Overview tab, improved dispute handling, and onboarded a large wave of new entities. Key Updates: 1/7 - Systemic Risk Graph > New systemic map view toggle on asset, pool, and protocol dendrogram pages > Force-directed graph showing every entity reachable from the selected subject > Rated nodes stay visible, while unrated leaf nodes cluster by strongest neighbour > Depth controls, hover tooltips, redesigned legend, and copy-address buttons > Dedicated side panel for inspecting individual nodes and clusters > Clearer visual markers, including triangle markers for protocols 2/7 - Entity Overview > New Overview tab with modular risk surfaces and an executive summary > Per-domain LLM summaries across Full Analysis and individual domain tabs > Titled highlights and granular-map markers throughout the overview > Tooltip explaining how the Market Median benchmark is calculated > Added new Protocol Cross Chain domain with website links on dendrogram pages 3/7 - Disputes > Rejected disputes can now be reopened from dispute cards and the resolution panel > Disputes are more resilient during infrastructure issues, with better recovery and escalation when LLM providers fail 4/7 - Ratings & Pools > Multi-select chain filter added to the Pools table > Chain identity now shown on every Pool row > Asset count remains visible on the ratings table > Chain, platform, and curator filters now persist in the URL 5/7 - Improvements > Edit-profile shortcut added next to user identity on the dashboard > XP and leaderboard footers aligned with shared paging > XP history can now be filtered by event type > Branded SVG logos added for Ethereum and Arbitrum Gnosis and Monad chains registered with logos and title-case fallback > Pruned domains hidden from the risk profile vector chart > Metadata chips consolidated into a single FilterSummaryBar > Improved wording on the Systemic Map “no rating yet” tooltip 6/7 - Fixes > Systemic graph connection fixes so graphs stay connected > Domain tabs restored on Organisation pages > Broken optimised images now fall back to source images > Pre-v2 summary responses render empty instead of crashing > XP table pagination now keeps the first page filled > Fixed systemic graph blank-canvas issue > Individual systemic graph nodes capped at 30, with the rest clustered > Clicking the risk feed now auto-switches to the relevant dendrogram tab 7/7 - Integrations > 50+ new pools > 50+ new assets > 20+ new organisations > 7 new protocols What’s Next? > Authoring - enabling the community to contribute towards subscores and mechanisms, > Backend clean-up — making the app faster and smoother > MCP — expanding how agents and tools connect into the platform > Quantitative subscores — deeper data-driven subscores
The exploit that broke Aave wasn't really about Aave. 23.5 Degrees unpacks the exploit chain reaction today at 1 PM UTC. @ben_solstice and @RyanDay are joined by @WCTNoah (@WhaleCoinTalk), @mauricedotxyz (@solflare), and @snj_peters (@Xerberus). Set your reminder below.
What looked like over-engineering yesterday looks like risk management today. Three HYPE++ deployments ( our flagship). Three chains. Zero bridges between them. Here’s why. Most asked question we get: “why do you have three strategies with the same name on three chains?” Answer: we built the OFT bridge. We chose not to deploy it. Not because we couldn’t. Because we shouldn’t. Each HYPE++ vault is an ERC-4626 with OFT-compatible code. Deployed, readable, unwired. Because wiring it up means underwriting the bridge config, the peer trust, the DVN set, the executor. Extra risk we do not get paid for as D2 depositors (yes, we have skin in the game). Our choice: three separate deployments on @arbitrum ( the original deployed pre $HYPE’s TGE) @HyperliquidX , @base. Users deposit native @USDC or @USDT0_to on their chain. Each vault trades independently. At epoch end, D2 reconciles PnL across deployments so every chain access point shares the same strategy performance. Trade-off we accepted: operational complexity, daily explaining in Discord why three deployments and why no mid-epoch valuations. (@jchoop can confirm this 😅) Trade-off we rejected: multimillion drain from a single peer compromise. Exactly what happened to Kelp’s rsETH OFT adapter this morning. Even @claudeai flagged this as a design flaw in a prior architecture review. Fair critique. But Claude doesn’t have capital at risk. We do. Team capital sits in the same vaults as user capital. Skin in the game changes the calculus on what counts as complexity vs necessary redundancy.
