
flightofthefox.proven
2.8K posts

flightofthefox.proven
@flightofthefox
building cool TEE stuff @proven_network 🦊








ZERO is decentralization sleight of hand: By shifting work over to builders, they claim to have low "validator" requirements... In reality, they only disempowered them! Replacing validators with a new class of builders that require server farms & calling that decentralization!




We are using our existing fiat runway to ensure this handover is executed correctly, supporting critical infrastructure until the community takes the wheel. This is what a mature, decentralized network should look like. Foundations exist to bootstrap, not to govern forever.


CAIR claims that revoking deportation protections for Somali fraudsters, who funneled U.S. taxpayer money to foreign terrorists, is an “Israel first” policy. Do you understand yet how the anti-Israel rhetoric is a massive psyop to push Islamism?




Wishing you all a Merry Christmas together with your loved ones Let’s not forget the reason for the season. Jesus, the King of the universe, was born in a humble stable, not a palace. No crown, no throne, only humility. A timeless reminder that true greatness is found in serving others.




Hyperscale is back! 269k TPS during an internal test. A new record! Rewriting the test scripts to multi-threading, to make use of fewer but more powerful nodes sending transactions, seems to be a good approach on AWS. This is also the first time we moved beyond 40 shards, which opens the road to 500k TPS 🫡 The move from Hetzner to AWS was unexpected and led to some delays; however, I made significant progress in the last week. Next up is a new private test to confirm this set up with a larger group of nodes 🦾



🚨 Update on @Aave's Internal "Civil War" Situation Aave is at a "Break it or Make it" moment. Whatever happens next won't just define the future of crypto's largest bank, it'll also set a precedent for the entire industry. What changed since yesterday 👇 – Voting went live today – Stani voted against (nay) with ~333k (~33% of total voting power so far) – @Marczeller voted abstain, as publicly stated – Major CT voices like @DefiIgnas also chose abstain Current scoreboard: – 62.76% against Aave DAO (Nay) – ~33.18% abstain – Only ~4.06% in favor (Yea) Translation: the DAO is almost certainly losing. If this passes against the DAO, things can get messy. Possible outcomes 👇 A. Scenario 1: Aave DAO forks the frontend and runs independently. This lets the DAO route surplus fees to the treasury, but it comes with massive responsibility around security, updates, maintenance, infrastructure, and ops. It also splits the user base (and trust?) overnight. B. Scenario 2: A full-blown legal tussle between Aave DAO and Aave Labs, potentially in Wyoming, exactly as @tulipking predicted. C. Scenario 3: Nothing happens. The DAO accepts the result and moves on, since it doesn't own the brand, IP, socials, GitHub, npm, naming rights, etc. Also, many won't want a long, public DAO vs. Labs war anyway. A prolonged standoff risks bleeding revenue and weakening the ecosystem further. But, every scenario creates a crack between Aave Labs and Aave DAO. And that's dangerous. Because Aave didn't survive multiple cycles alone. Service providers like @chaoslabs LlamaRisk, BGD Labs, TokenLogic, and @Aavechan are a huge reason Aave not only grew, but also stayed dominant through multiple cycles. For Aave to remain the dominant player, DAO alignment isn't optional, it's existential. And this conflict has to be resolved or decisively settled. Until then, everything is uncertain and the market is already reacting. AAVE is down ~18% in 7 days, despite the SEC officially ending its investigation on Dec 17. But if we zoom out, this vote answers something bigger: 1. Token vs. equity 2. Governance as 'utility' 3. Who actually owns a protocol? This industry has argued about this for years. Aave is about to give us the answer, whether it wants to or not.









