🌱 KevinOnFrontEnd

Crazy Eights demo using the Chia Gaming Framework with Mental Poker. With commutative encryption, it is possible to achieve a central deck hidden from both players. Soon we will know the cost of each move, if it has to go on-chain, especially the reveal, since the private key makes it significantly heavier. Even so, I expect it to use around 1–2% of a block’s capacity.

Check out a new beta version of XCH.ninja at beta.xch.ninja for tracking the @chia_project prefarm - Tracks pending/clawback status on vault spends - Tracks "Buy XCH with ACH" sale activity - Tracks transfers between cold and warm wallets - Analytics page with price, inflation, and run rate charts

Tokenization of assets can unlock many unique use cases, but it has to be done carefully and with specific intent. feat. @vskapoor

Edward Snowden said it the best: "When you say 'I don't care about the right to privacy because I have nothing to hide,' that's no different than saying 'I don't care about freedom of speech because I have nothing to say.'" "Simply because you are following the law, doesn't mean that you'll be exempt from governmental interference in your private life."

An undo button, isn't that how it should be? Transact with peace of mind.

This is a really impactful release. The AI angle might sound overstated, but if anything, I think it may be understated. I wouldn’t be surprised to see a couple more soft forks in the coming months to reach a peaceful equilibrium with motivated attackers. Things are moving in the right direction though.

Version 2.7.0 of the Chia reference client is now available for download. We are urging the entire community of farmers, node operators, and ecosystem partners to adopt this update immediately. This contains a soft fork release that will activate at block 8,655,000, around April 29/30 – the same block as the soft fork changes in 2.6.0 which was released on February 11. Read more on this release here: chia.net/2026/03/26/chi…

I treated myself to one of these today. Can't wait for it to arrive =) xteink.com/products/xtein…

I finally decided to move some funds over to my #Chia cloud wallet. I just need to be able buy $xch in it from the UK.

Arcade21 will bring the Games and the Dev Tools. The protocol is open. The tools are open. The tables will be open soon enough. @MrDennisV and I are hard at work daily to bring you premium games in a premium experience. Stay tuned. Find out more at Arcade21.Games

Airdrop complete! Here are the stats: Recipients: 169,808 🤯 Total amount: 20m CRT = 2% of total supply Max amount: 607k CRT 🥇 Allocation:👇

On-ramp your USD to Chia and earn 3.2% APY in a Circuit savings vault. No intermediaries. Backed by real cashflows. This is why DeFi will win.

@splitXCH @tii_bag 😂😂😂😂😂😂😂

@KevinOnFrontend @tii_bag Nah, just below what it takes to make a Netflix stream stable 😂

I shared my wifi password with my neighbour and he's been using it for 5 months. Today I asked to be added to their Netflix but he said that its his wife who pays for the Netflix and she refused. Well,I cut them off from my wifi and he has the audacity to come ask why I did so

Get it while it's hot

got mine!

@mrcic3 @MrDennisV One does not simply charge people to build on a public, decentralized, permissionless blockchain

I may or may not have a game i am working on, while trying to learn blender. 👀

just gonna leave this here... no reason... @Arcade21Games #devlife on #chia

Kubernetes is beautiful. Every Concept Has a Story, you just don't know it yet. In k8s, you run your app as a pod. It runs your container. Then it crashes, and nobody restarts it. It is just gone. So you use a Deployment. One pod dies and another comes back. You want 3 running, it keeps 3 running. Every pod gets a new IP when it restarts. Another service needs to talk to your app but the IPs keep changing. You cannot hardcode them at scale. So you use a Service. One stable IP that always finds your pods using labels, not IPs. Pods die and come back. The Service does not care. But now you have 10 services and 10 load balancers. Your cloud bill does not care that 6 of them handle almost no traffic. So you use Ingress. One load balancer, all services behind it, smart routing. But Ingress is just rules and nobody executes them. So you add an Ingress Controller. Nginx, Traefik, AWS Load Balancer Controller. Now the rules actually work. Your app needs config so you hardcode it inside the container. Wrong database in staging. Wrong API key in production. You rebuild the image every time config changes. So you use a ConfigMap. Config lives outside the container and gets injected at runtime. Same image runs in dev, staging and production with different configs. But your database password is now sitting in a ConfigMap unencrypted. Anyone with basic kubectl access can read it. That is not a mistake. That is a security incident. So you use a Secret. Sensitive data stored separately with its own access controls. Your image never sees it. Some days 100 users, some days 10,000. You manually scale to 8 pods during the spike and watch them sit idle all night. You cannot babysit your cluster forever. So you use HPA. CPU crosses 70 percent and pods are added automatically. Traffic drops and they scale back down. You are not woken up at 2am anymore. But now your nodes are full and new pods sit in Pending state. HPA did its job. Your cluster had nowhere to put the pods. So you use Karpenter. Pods stuck in Pending and a new node appears automatically. Load drops and the node is removed. You only pay for what you actually use. One pod starts consuming 4GB of memory and nobody told Kubernetes it was not supposed to. It starves every other pod on that node and a cascade begins. One rogue pod with no limits takes down everything around it. So you use Resource Requests and Limits. Requests tell Kubernetes the minimum your pod needs to be scheduled. Limits make sure no pod can steal from everything around it. Your cluster runs predictably.