
Liking art on mallow costs $0 and can help artists gain visibility
✓Co-Founder and CTO of @mallowdotart banner by @rgb0x00

Liking art on mallow costs $0 and can help artists gain visibility

Techtonic is live now on @mallowdotart 999 unique pieces, a long-form generative collection exploring pixels and natural movement. Digital systems with a life of their own, colliding and breaking apart, ebbing and flowing over time. .11 Sol per piece, happy collecting!


gm london

ITS HERE 🌸 Your art. Your wallet. The mallow wallet is out now. Collect, curate & display digital artwork across Solana, Tezos and Ethereum - all in one place. Get it on iOS & Android ↓↓

available now: wallet.mallow.art

Woah, kinda cool. At this moment it seems mallow wallet is the only Solana wallet that supports sending cnft v2 😁



An open letter to the Solana Foundation on the new SFDP rules On November 6, the Solana Foundation announced new rules for the Solana Foundation Delegation Program: a twelve-month membership term, graduation at 300k SOL of external stake, a hard cap of 100 validators, and the retirement of existing members in weekly tranches. We are writing because we believe these changes work against decentralization, and because they will push out many of the hardest working and best-faith operators Solana has ever had. These are the quiet ones. They do not run marketing campaigns or pick fights on X for impressions. They run nodes, they run them well, and they make valuable contributions to the network while doing it. ◆ The incubator model has not worked ◆ SFDP was built as a launchpad for new validators, and that was the right goal when the validator set needed bootstrapping. That job is done. The goal posts need to move. On paper, twelve months of delegation followed by forced graduation is a sink-or-swim model: incubate new operators, let natural selection remove the ones who cannot make it. In practice it will play out differently. Validators will join, collect earnings for twelve months, and leave. That is not a net new independent operator. It is a short-term tenant. The deeper problem is that attracting stake outside SFDP is close to impossible unless you are already in the superminority. The highest-staked validators keep attracting even more stake, so the superminority is shrinking in count while growing in share. Under these rules it sits on top of a constantly churning set of 100 SFDP nodes. Churn is not decentralization. It is a revolving door with an ever-smaller group of ever-larger operators on the other side. Meanwhile, the operators who actually push the network forward are the ones being cut. The people who tirelessly tested the new governance system before it went live. The people who moved their nodes to different ASNs, at their own cost, because ASN diversity mattered. The people who lose sleep for urgent upgrades. The people who carried Alpenglow to mainnet, which we come back to below. Those are the operators this program is now designed to remove. The longer you have been on Solana, the worse this program is for you. ◆ The Teraswitch outage is the case study ◆ When Teraswitch went down, the network did not halt. It stayed up because enough stake was spread across enough independent validators on enough different ASNs to keep consensus alive. That distribution did not happen by accident. It existed because SFDP supported the number of validators it did and because SFDP created the ASN rule. And stake on Solana increased after the outage. The market saw a network absorb a major provider failure without blinking, and rewarded it. Shrink the program to 100 validators and concentrate the rest with a handful of operators, and the next provider outage ends very differently. The Foundation is dismantling the exact safety margin that kept the chain from halting. The numbers are not abstract. At the operator level, Solana's Nakamoto coefficient is 8 today. It was 6 until Alpenglow raised the liveness threshold from 33% to 40%. At the 20% safety threshold, the coefficient is 3. That is a long way from the 18 or so that gets repeated in marketing. These rules push every one of those figures the wrong way. ◆ Alpenglow was carried by independents, and independents are paying for it ◆ Alpenglow did not reach mainnet on its own. It got there because of the community cluster, and the community cluster was run almost entirely by independent validators. Not a single operator from the superminority participated. The largest validators on the network, the ones about to receive the stake being taken from us, contributed nothing to the most important upgrade Solana has shipped. The history matters. When independent validators raised concerns about 200ms block times and the operational/financial load it put on smaller operators, the Foundation's answer was to participate in the Alpenglow community cluster and accelerate the migration. So we did. We paid for the extra servers. We stayed up until 2 and 4 AM through dozens of regenesis’s. We absorbed weeks of accelerated block times and accompanying doubling vote costs, on the understanding that Alpenglow would make it worth it. Alpenglow migrated to mainnet a few weeks ago. Before most of us have earned back a fraction of what that period cost, SFDP is retiring us. The entire burden of 200ms and the Alpenglow migration on independent validators, and the moment the work was done, the Foundation moved to cut us. At minimum, the operators who carried that upgrade should be allowed to run on Alpenglow mainnet under existing delegation for six months before any retirement takes effect. That way they can recover their costs. ◆ Who actually contributes to the network ◆ Measured against stake, lower-staked validators contribute far more back to the network than their higher-staked counterparts. This is not a matter of character. It is structural. Large operators have investors and shareholders who expect profit to be maximized. Testnet participation, client diversity work, community infrastructure, and governance testing do not make money. The largest operators are therefore discouraged from doing any of it, and for the most part they do not. Alpenglow is the clearest example. Independent operators are the opposite. We are expected to contribute, we are judged on it, and we do. SFDP spent years building that expectation into its own criteria. The new rules now retire the operators who met the bar and hand the stake to operators who are built not to. ◆ Institutional delegation is moving stake in the wrong direction ◆ Our understanding is that the Foundation intends to redirect stake toward institutional validators. Institutions outsource risk; that is what they do. We expect the long-term result to be institutions white-labelling through a small number of existing superminority operators. Stake taken from independent validators will end up concentrated with the operators who already hold the most of it. That is centralization in its purest form. There is a harder truth underneath this. The independent validator set was the proof point. Early community operators were what made Solana credible enough for the people in suits to start paying attention and writing checks. Decentralization was the pitch. Now that the money has started to arrive, the operators who were the pitch are being shown the door to make room for it. People who gave Solana their everything deserve better than being used as leverage and then being thrown away. Decentralization is not a vanity metric. It is not a position to take the moral high ground from when criticizing a competitor like Hyperliquid, and it is not a narrative to be respun each time compliance requirements get clarified. Decentralization is why this industry exists in the first place. Institutions are not bad actors (usually). But they are not network stewards. They have no mandate to care about client diversity, ASN spread, or testnet participation, and no operational capacity to contribute to any of it even if they wanted to. The better outcome for everyone is to route that stake to the independent operators who have already proven they will protect it. ◆ SFDP needs a purpose again ◆ If the program no longer exists to support independent operators or diversity, and the incubator model does not work in practice, it is fair to ask what the program exists for. We propose it becomes a long-term independent contributor program, where the contribution being measured is network health itself: uptime through upgrades, client diversity, ASN and geographic diversity, supporting new innovative initiatives like community cluster participation, governance testing, etc. The operators who carried Alpenglow testing are exactly the people such a program should be rewarding. Inactivity means removal. Operators who do this work should be rewarded for as long as they keep doing it, not retired on a calendar, and not asked to become something other than validators to stay eligible. That model aligns the program's incentives with the long-term success of the network. Arbitrarily picking 100 validators and churning them once a year aligns them with nothing. ◆ What we are asking for ◆ 1. Pause the weekly retirement tranches until the community has been consulted. 2. Give current members who participated in the Alpenglow community cluster a minimum of six months of continued delegation on Alpenglow mainnet before any retirement takes effect. 3. Publish the analysis behind the arbitrary 100-validator cap, and twelve-month figures. 4. Open a formal consultation with current SFDP members before the rules are finalized. 5. Adopt the contributor model above as a replacement for, or alongside, the incubator model. Solana's resilience was built by people who showed up when it was hard and did not expect to be thanked. We are asking the Foundation not to design them out of the network. ◆ This is what the independent set actually does ◆ The independent validator set, even within Layer33, has been able to achieve many things. Across this group alone, we have: ◆ Supported the official Solana testnet faucet with validator rewards from over 33 million testnet SOL delegated across more than 5k stake accounts, replenishing roughly 450k testnet SOL per month so new validators and developers can deploy before touching mainnet ◆ Built the devnet faucet and the Solana Hardware Compatibility List that operators use to spec machines ◆ Been among the first mainnet validators to run Frankendancer, and later to adopt full Firedancer, on our own hardware, before client diversity was a talking point ◆ Made open source contributions to solana-program, Firedancer, and DoubleZero, plus open source tooling that lets operators switch clients and handle updates automatically ◆ Built a free public API and chart suite for validator and network data that powers dozens of tools and sites across the ecosystem ◆ Built public dashboards that have repeatedly exposed malicious validator behavior around delayed blocks and held bad actors accountable ◆ Shipped the first UI for diagnosing skipped block issues, and staking tools for tip harvesting and stake account cleanup ◆ Co-authored the Validator Voting Behavior Study Built Nakaflow, which tracks Solana's Nakamoto coefficient against other chains ◆ Contributed to governance design from the beginning, and are key contributors to the new governance platform launching in 2026 ◆ Run the monthly validator community call continuously for more than three years ◆ Co-founded the Block Zero validator conference, and organized and sponsored every edition since inception ◆ Built validator infrastructure in underserved regions, including the only major validator between Dallas and Miami and the oldest Brazil-based validator, both on dedicated hardware ◆ Won multiple Solana hackathons ◆ Still host multiple hackathons across Solana every year ◆ Created one of the first Solana-native transaction indexing platforms, used by consumers and teams to understand on-chain activity at scale ◆ Built early DAO and governance tooling adopted by BONK and other Solana-native projects ◆ Built stake pools and delegation tooling that route stake toward performance and decentralization ◆ Reinvested validator revenue into Solana-native startups, hackathon track sponsorships, free web3 security education, and ongoing donations to animal welfare, clean energy, and men's health charities ◆ Kept genesis validators running on our own fleets across multiple locations, delegating our own stake to other operators who contribute to network health ◆ Made up the bulk of the Alpenglow community cluster, on our own servers and our own time, to get the upgrade to mainnet faster Several of these have been running for three years or more with no end date. That is what a long-term contributor looks like. A twelve-month clock does not describe it. None of this was required. None of it counts under the new rules. With these changes actioned, institutions like Figment get propped up and the independent validator set gets dismantled. Under that model, none of the above would have existed, and the next round of contributions like these will not exist either. The independent validator set is normally quiet. We work siloed in our own day-to-day operations. Decentralized, you might say. We focus on validator and network performance, not for ourselves, but so that Solana thrives. For all of us to come together and speak out against a single change means something is truly broken. This letter may disappear into the void as the Foundation moves to support the large institutional players, the ones who do not care about Solana, at the expense of the people who do. Even so, we wanted our position on the record. L33

1/ Been working on a tool to help people find money they left in old protocols. Most from 2021-2022. I HIGHLY recommend if you were around in the early days of Solana and did any NFT bidding, used defi protocols, it is worth looking your wallet up. It is quick & fast.

Introducing the Parsed Events Scan API Find the transactions you need in any Solana address’s history, already parsed, 10x faster and 30x cheaper Filter by named program instructions, discriminator prefix, token mint address, native SOL, or any combination of filters

🚨 PSA for anyone running a Linux server, node, or relay CVE-2026-98432 is a critical Linux kernel bug (CVSS 9.8). Someone on the internet can send crafted TCP packets and take over your machine. No login needed. Ubuntu and Red Hat haven't shipped a fixed kernel yet. Debian, SUSE, Oracle and Amazon have. What to do today: 1. Check your kernel: uname -r Fixed versions: 6.1.190+, 6.6.159+, 6.12.113+, 6.18.56+, 7.2.10+ or 7.3+. Below that, you're exposed. 2. If your distro has a fix, update and reboot. 3. If not, block the attack. It needs TCP packets with "IP options," which normal traffic never uses. One nftables rule drops them. Log what gets dropped so you can see if someone's probing you. 4. Turn off MPTCP unless you need it: sysctl -w net.mptcp.enabled=0 Programs built with Go 1.24+ use MPTCP automatically, and that's how the known exploit gets in. 5. Make it survive a reboot, and check it still works after one. If you run a Bitcoin node, a Lightning node or a Nostr relay, your machine is on the internet by design. Do this today. Self-hosting is freedom. Patching is part of the job. 🛡️

👨👩👧👦 Solana NFT Community finalists: @monkedao @claynosaurz @galacticgeckosg @mallowdotart Voting is live until November 9 Group chat loyalty is about to get tested. Vote here: solana.com/breakpoint/awards

Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified. The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far. Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete. As an immediate precaution, Binance has: - temporarily suspended deposits and withdrawals while security checks are completed; - revoked the affected address authorisation; - engaged law enforcement and blockchain intelligence partners to trace and recover funds. Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice. Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions. binance.com/en/support/annou…
