The 2025 Roadmap talks about several things and I know resources are limited but a browser extension is being built [1] and I assume the “foundations” still work.
Yesterday I tried this [2] xxDK example which couldn’t work (CORS errors, probably thanks to the many outstanding validators), so I wonder does anyone use anything at all and how this browser extension can be built when simply connecting to the network seems challenging.
I can’t find that post where validators were told that those who sabotage their configuration to save bandwidth and other resources (presumably helps when running a bunch on the same node?) and I don’t know if Haven or any other client can connect and use the network.
It appears that a bounty to refresh xxDK (and make sure the examples can work) would be helpful. (Something could be said about how validators manage get paid to undermine the network, but I’ve said that many times already.)
Tools to check validator setups are needed. I had published one a while back but it doesn’t provide a ton of useful information for how to fix problems:
The associated post got removed because people were panicking thinking the foundation was going to push it through. It was my proposal.
We will need to add to this tool an SSL certificate check for the web interface at minimum, I think.
That is hilarious!
It’s like removing a video of a cop chasing a thief because forum members couldn’t bear the thought of seeing the cop catch the thief.
Pushing it is exactly what the Foundation should have done, but as we’ve learned from the FAQs - if I got that right - they aren’t even authorized to implement basic network-saving measures…
I wonder what the “Lame Validators Matter!” activists from xx Discord think about this.
They’ve been suspiciously quiet on the forum - it seems they feel the community has achieved nirvana in which the lamest of validators have been liberated and manage to escape the eternal circle of re-election (samsara)
You tell us than you leave but you seem still here hidden under another nickname like you do on Discord and probably still present there.
I don’t think people panicking but report an issue who isn’t on the validator side. We haven’t anymore a beta network to test that and ask validators to modify parameters and check what happen.
The goal was keep an healthy and growing network. Community have already do many actions resulting a price dropping and now a network who shrink with all issues resulting. You have a direct responsibility to what happen now. Network was healthy with a waiting queue before you cause a mess and “leave”.
I have detected recently a new bug on gateway side but may be useless to report this bug in actual state.
The only thing we should do right now and who isn’t even proposed here because that’s the first priority. It’s removing the perm server and fully decentralizing the network.
Before we do that all other things are useless now. This network should run from herself what ever the number of validators or the team. So please stop to distribute coin, stop to take time for useless thing like this bug and decentralizing this network.
One time this step is done we can work on another step quietly.
We encountered an issue with the examples and some level of CORS, but managed to bypass it. We are utilising the existing systems within Haven to push the KV directly to the extension storage, eliminating the need to make network requests and use that part. Our primary usage was xxDK-WASM for this.
In the past, we have solved these CORS issues by setting the correct permissions in HTTP headers or by adjusting the requested permission requirements.
Network was healthy with a waiting queue before you cause a mess and “leave”.
I’m curious just how incompetent I am as a user… Let’s see…
“Last time I used Haven to connect to xxNetwork without difficulties…”
this week
last month
last quarter
in 2024
0voters
I haven’t been able to use Haven for probably 10 months now because validators have been doing such an awesome job for a very long time.
If clients don’t work well because validators are doing a lousy job, decentralization of permissioning is the least of all problems.
Another network where I’m active just cut dozens of validator slots at once because the bottom-ranked bastards were milking and sabotaging instead of helping. That was one of my best days in that community although I don’t validate there.
But worrying about users and making sure the network can actually work aren’t major concerns to you. Validators come first, to deliver decentralized, planet-scale, state actor-resistant PQ messaging. The fact that barely anyone can connect to this network is a minor issue which can easily be solved if 50 more validators join the network without barely anything at stake.
Good to hear that and great work finding workarounds.
It seems not much of that is documented, is it?
It’d be nice if xxDK (including -WASM) got code and doco updates to make developer on-boarding easier. The anemic xx Council should he giving smaller tips for anyone capable of improving technical documentation and driving these incremental improvements with small resources and minimal friction, but the ones who still show signs of life seem to be busy with the other thing.
I haven’t been able to use Haven for probably 10 months now because validators have been doing such an awesome job for a very long time.
I have issue since first day due to browser compatibility or whatever the issue was but not the validator. The issue of the ssl certificate isn’t on validator side. Why we can’t select an entry gateway by example to solve this quickly ?
I never check anything but see a fixed list of gateway manually selected to do that if it’s still the case every validator who have leave can just cause these type of issues.
If clients don’t work well because validators are doing a lousy job, decentralization of permissioning is the least of all problems.
It’s only one tool but the network run and work well. So it’s may be just some issues on dev side and not on validators side.
I honestly don’t care about your private life.
On a decentralized network the network should be able to do self-healing. The rules should be included inside the network if the network permit that all is fine.
Yes more you have gateway more way to reach the network so it will of course solve the issue if the issue come like you write from the validators side who isn’t the case. When any gateway can reach the network anyone can run a local gateway connect through a local gateway and hide communication and destination with other traffic who is much more secure than connect to a random gateway who can be monitored by state actor.
You seem not have evolved but most probably a lost cause.
Duh. It obviously weakens your anonymity by several orders of magnitude.
How would a user even know which gateway to select?
Awesome idea! Now we just need to tell our army of idling developers to spend the rest of 2025 creating such rules. How come I didn’t think about that before!
Validators with objectively unusable gateways are malicious and should be warned and banned in short order.
Of course, none of this can happen when parasitism is tolerated or even encouraged. Why should anyone ensure their gateway runs fine when they can cripple it, save CPU, RAM and network resources and make more money that way? And that’s completely harmless - all the user needs to do is select some other gateway. Easy-peasy!
How would a user even know which gateway to select?
Your own local gateway the only one who is perfectly safe and not leak any data like even your ISP can’t know if you are connected or not due to other traffic. The base concept of “mixnet”.
unusable gateways
It’s a software bug who not generate correctly the certificate who can’t be fixed at all on validator side. We haven’t any control on this generation or these certificates. Blame yourself if you want.
gateway runs fine
If a gateway not run fine you have issue with your cmix node actually rewards is to the validator and nominators both will received less money.
Selecting local gateway is for security when you reach an outside IP your ISP/government or anyone can know where you are connected and can know what you do. Give them metadata and trace back IP connections with date/time so know you.
I see, that’s why we need 600 million validators, so that everyone can use their own gateway.
So it’s a known issue and the Council can’t/won’t posted a bounty to have it fixed, then?
That’s BS. First, if you’re not a validator there’s no “local gateway” in the first place so even this bad advice isn’t applicable to almost anyone on the planet but the few hundred (okay, maybe 150) people who run nodes. Second, if you are a validator, using local gateway surely correlates with more network flow on gateway’s connections and decreases your anonymity gaining you nothing.
Not millions but thousand yes it the minimal requirement to resist to any attacks.
So it’s a known issue and the Council can’t/won’t posted a bounty to have it fixed, then?
I’m not inside the council but they know the issue like it’s stated even here without error.
if you’re not a validator there’s no “local gateway”
That’s an issue reported long time ago. We should run a local gateway to be able to hide all metadata correctly.
For the second point no like rounds happen with or without processing data so send “noise” to hide any traffic. You are perfectly hidden with a gateway running 24/24h. If you launch gateway only to be connected it’s a little less secure because can look time frame of gateway usage and messages posted.
