I appreciate the kind words, but I would just like to make a note that if you think the official “devs” are doing nothing…. You are likely not paying attention. Things change, all the time. Maybe not as fast as we would all like. But I can see the changes. A lot of it is just not super user visible.

Something to talk about with Cappy.... It's quite honestly, expensive. It's what I was alluding to with why Rabby dropped #PulseChain support. But regardless of that expense, I feel like we need these features. One way of making this able to exist long term, is actionable fees. Like on swaps. But honestly, while it's probably a requirement to have, I personally dislike egregious fees. So most of those, I will be capping at 0.25%. Which is the Rabby default and something I agree with as reasonable. But I also want to try to do something better. So I am also playing with the idea of adding Cappy Pro. This will be fully on chain settled, self swapping to stables (it will auto dump what you put in). Cappy Pro would be a subscription, $5/30 days of enablement. At minimum it will offer 3 things for up to 3 addresses. 1. Reduced fees on swaps and such (0.1%) 2. Proxied Private RPC. Cappy's API will strip metadata from your TX's and proxy the TX through its API RPC backend. So no other RPC or actor will know your IP or other identifiable information. Just that you used Cappy to sign the TX. (and maybe later will round robin that through various VPN's so they don't even tie back to Cappy). 3. TX watcher, something we all love to do. Add a list of addresses you want to monitor and it will concatenate the view of TX's involving those addresses. With label support. (maybe push notifications in the future). 3a. (Maybe) whale watching. Put in a token address and it will show live TX history of any movement over a certain balance size. Do you agree with this, disagree with this? Are these features things you would like to see exist? I'm working to publish the first beta release of Cappy this weekend if possible.

Fair points, but "multisig + timelock fixes it" has its own graveyard. Ronin ($625M): 5-of-9 validators, Sky Mavis controlled 4 directly plus a stale Axie DAO delegation. One phished employee = full threshold. Harmony ($100M): 2-of-5 with keys in plaintext on the same servers. Two compromises, bridge empty. Multichain ($125M): "MPC" that ran entirely under the CEO's personal cloud account. He got detained in Kunming, funds walked out behind him. The decentralization was theater in every case. Timelocks cut both ways. A 24h delay means the legitimate owner also can't patch a live exploit for 24 hours. Implementation bug gets found, attacker drains, fix sits in the queue. Historically more bridges die to impl bugs than admin key compromise. And if the key does get compromised, the timelock just turns it into a 24-hour exit race. Gas spikes, attacker frontruns withdrawals or uses private mempools. The fast and plugged-in get out. Average holder checking Twitter on a Saturday still loses. Not defending the EOA setup as optimal. The point is every option here is a different failure mode, not a strict upgrade. EOA: holder rugs or gets compromised. Multisig: signers collude or get phished together. Timelock: can't react to exploits. Federated validators: liveness and collusion (Wormhole, Nomad). Pick your poison. There's no config that removes trust, only ones that reshape it.

There are a couple other ways. (this is not an all inclusive list) One is a secondary malicious extension in the browser. The most obvious method is to override / intercept window.ethereum. But another is the extension sitting in between external API fetches and manipulating the DAPP to do something unintended. That includes RPC calls that are not from the wallet itself. Ad blockers historically have had the power needed to pull this off. Another is cache poisoning. Of which there are a few ways to achieve. But getting some kind of front end render proxy to cache a bad JS chunk, or API result. Typical done by achieving a desync in between the frontend proxy and UI server, you can squeeze in some extra headers / body data that gets appended into the next request. Say in the next request you sneak in some headers that makes the proxy believe the data came from the UI server (as the UI server is just regurgitating them back). Now the proxy is serving manipulated data from cache until it expires. The first one, users need to practice good opsec. At the very least Cypto should be it's own browser profile with no unnecessary extensions. The second one is thwarted by locally running self contained apps. Or by ensuring you app has no need other make external calls (fully self contained) and checksumming its own chunks on load. In any case, supply chain attacks on valid tools are almost always possible. Here's a good talk on desync: youtube.com/watch?v=FJbuAyxT…

I've been working in silence for quite a while now. Tbh, I don't really even know where to start, so cue the rambling and ranting. Regardless of which side of the fence you sit on, no one can argue the past few years haven't been politically and economically wild. For crypto as a whole it feels like a never ending game of tug of war. A lot of X content has become toxic, so I just largely am not interacting these days. But I read, I read a lot of it. I think we like to forget history a bit in this community. $PLS launched off the highs, and the SEC swooped in right after. Very few people want to admit it, but it shook confidence immediately. I mean no other crypto project has survived such a thing at the time. But #PLS $PLSX and $HEX did. However, winning doesn't unshake that confidence. And RH during and after that event took social precautions to protect himself and his creations. Thing is, the guy isn't stupid. Someone once asked me if I thought certain aspects of the launch we rushed because he knew it was coming? And honestly, maybe. I'd attribute at least a non-zero probability to it. And If that were the case, im glad it was rushed. That case may have gone differently otherwise. Do I still think #PulseChain, #HEX, etc... all have futures? Yes. RH has had the opportunity to just straight up bounce from all of this. Why hasn't he? You could point to exhibit A, B, C, D, etc... of how he's likely got the funds to do that and we all could relatively do nothing about it. So why is he still around? I think it's pretty simple. The usual answer, he wants to win. It's in his twitter handle for Christs sakes. I'll go a step further and say he likely also wants us to win by extension, arguably not as much as he wins, but I mean that's pretty locked in at the moment 🤣 That's not to say he hasn't long been encumbered. And in that state, at lot has gone on without him. Much of which is / was bad. $pDAI guys... I pointed out from day one how building all this around a protocol in a dangerous state was a risky move. And I was right about that.... on multiple occasions... But does that matter now? I suppose not as much. In its current state, it's seemingly no longer exploitable. No different than a meme token now. (presumably, not like I have deep dove on any further risks since ESM). So I guess just whale risk mainly now? Now a lot of people here are in the anti-pdai camp. Me too for what it's worth. But I don't care as much about it's negative anymore in its current state. A lot of people are still in the #pDAI camp strongly. We view this as tribalism, but it's important to note that makes all of us in the #PulseChain camp universally. So these day I find myself relatively pDAI neutral. If you guys want to send it to $1 do it. Only whales can stop you, they run out eventually. (insert super strong this is NOT financial advice). Hell you can maybe even use Sigma to help? Or maybe it wont help, idk. Depends on how people use the software. Conversely, when looking at chain state overall... Why is there nearly $50M in stables sitting on the sidelines. Why not just bridge it out if you want out of what you think is a dead chain. Surely leaving it there exposes you to bridge risk? Why all these yield movements, why the $HEX dusts.... Something is happening. People are seemingly waiting to see what that something is. Or I am reading into things, NFA as always. This whole post is just ramblings of someone trying to do the best they can and certainly not any kind of advice. When I look at other ecosystems, I see a level of polish we don't have. I see tooling we don't have, I see a fostered developer environment we don't have. So I've just been building it, painstakingly.... Because someone has to if we want to be taken seriously. And what I've been building has allowed me to get Sigma to where it is. Sigma is so close... Really just in UI mode, performance optimization, going through nice to haves. I don't believe in launching in a non-finished immutable state. So yeah, I take my time. As with everything. But my point with all of this, and the "why" #Sigma question.... It's unifying, anyone can participate. Which tribe you're in doesn't matter. And if you don't like it, don't use it. It's just software you can use or not use. As it should be. The years of tooling work to deliver this has been a lot of work for one guy in silence. In that time AI has appeared. My take, every dev should be using it. Given the right direction and context. It will make you better. If you blindly trust it, it will make you worse. GPT 5.4 audits smart contracts better than most auditing services. Especially if you give it the context of what you are trying to do. Anyways I digress, testnet is soon. Soon more meaning a feeling of near completion not always reality. That how software is. I do think Sigma stands to unify the chain in a common goal, and shift liquidity into more meaningful places, but ultimately it up to the people the decide to use the software or not use it. And after these frameworks I've built will be applied to what I am tentatively calling the universal hex UI. More or less something aggregative of every derivative I can reasonably support. With data and analytics we since lost. So not just $HEX, $HDRN, and $ICSA, but others as well. However, that depends on some aspect of $Sigma to exist first, so sigma first, chain unity first. And last but not least, take care of yourselves and strive to do cool things. If we aren't doing cool things then what's the point? Hope you think my UI looks good, I spent a while on it. /rant