Sunday Daily Video! 😈🏁
Well Kaspians… good news and bad news today 😂
The Launch Control is WORKING! 🔥🔥🔥
We finally got it dialed in and the BMW E46 Kaspa Rally Car is launching exactly as it should.
And then… on the second launch… BANG! 💥😂
We broke the left driveshaft!
But don’t worry — nothing serious at all. I have more driveshafts here at the workshop, so I’ll replace it and we keep moving forward.
These are exactly the kind of things we want to discover now during testing, not on rally day.
Once the car is fully ready and everything is properly tested, it will get competition-grade reinforced driveshafts so this doesn’t happen again.
We test. We break things. We improve them. And we keep going. 💪
That’s what building a rally car is all about!
The Kaspa Rally Car gets better every single day. 💚🏁
See you tomorrow, Kaspians! 🚀
VRU-VRU-VRU-VRU 😈😂
Plan 𐤊 is now in action.
.04 has been breached and the max exodus from $BTC and $ZEC into kaspa:native is near.
#KASPA is the endgame.
#CRYPTO#POW#CYPHERPUNKS
GM $KAS fam
A contact is looking to build a stable coin payment solution in the UAE
I know we still don’t have stable coins on Kaspa but I suggested they look into it. They’re asking who they can speak to
Any suggestions?
1/10
Kaspa just published official developer documentation.
One entry point for the full programmability stack Covenants, Based Apps, Inline ZK, SilverScript, vProgs.
This matters more than it sounds.
Here's everything that happened in CW38. 🧵
Exactly. Hence my tweet about $KAS, $ZEC, and $BTC.
kaspa:native is positioning itself to combine key attributes of $BTC and $ZEC, while building on its existing capabilities, DAGKnight, and future privacy.
why rely on separate assets when kaspa:native could integrate it all?
Delete Windows from your old laptop.
And turn it into your own private homelab instead!
Here's what I'd build:
1️⃣ Install Proxmox:
→ Install Proxmox VE directly on the laptop.
→ Create separate VMs and containers for different services.
→ Manage everything from a browser.
→ Take snapshots before experimenting so you can easily go back.
Your old laptop can now act like multiple little servers.
2️⃣ Set up your own DNS:
→ Run Pi-hole or AdGuard Home.
→ Block ads and trackers across your home network.
→ Give services simple names like `grafana.home` instead of remembering IP addresses.
You'll learn how DNS actually works while using it every day.
3️⃣ Turn it into a Docker server:
→ Create an Ubuntu VM and install Docker.
→ Run your services as containers.
→ Learn volumes, networks, and ports as you add more applications.
Start small and add things when you actually need them.
4️⃣ Self-host things you actually use:
→ Immich for your photos
→ Jellyfin for your media
→ Nextcloud for files
→ Vaultwarden for passwords
→ Home Assistant for home automation
Pick two or three. You don't need to install the entire internet on day one.
5️⃣ Access your homelab from anywhere:
→ Install Tailscale on your server, laptop, and phone.
→ Access your services securely when you're away from home.
→ Learn private networking and VPNs without exposing everything directly to the internet.
6️⃣ Build a homelab dashboard:
→ Install Homepage or Homarr.
→ Put all your services in one place.
→ Add server stats, service status, and shortcuts.
Now you have one place to access your entire homelab.
7️⃣ Monitor everything:
→ Start with Uptime Kuma to know when something goes down.
→ Add Prometheus + Grafana when you want CPU, RAM, disk, and other metrics.
→ Kill a container yourself and see whether your monitoring catches it.
8️⃣ Don't forget backups:
→ Keep important application data on persistent storage.
→ Use Proxmox backups or a tool like Restic.
→ Keep another copy somewhere outside the laptop.
→ Try restoring something once before you actually need to.
9️⃣ Turn it into your DevOps playground:
→ Keep your configs in Git.
→ Automate server setup with Ansible
→ Deploy your own applications with GitHub Actions.
→ Add another old machine later and experiment with k3s or a Proxmox cluster.
What started as an old Windows laptop is now your:
Server + private cloud + DNS + VPN + media server + monitoring system + DevOps lab.
And that's how the homelab rabbit hole begins.
$ZEC has awoken PoW.
$KAS takes it further: #Bitcoin-style PoW built for speed and scale.
DAGKNIGHT is the ultimate unlock > adaptive consensus that responds to real network conditions.
$KAS DK does exactly what @elonmusk refers too below.
Fade at your own risk.
#CRYPTO
@CryptoEndeavr Yes — it’s being developed by BitCoffee0. I should have credited him in the original post.
He shared KUSD and the TN10 work here:
https://t.co/wPyFOGKHrk
And the code is public here:
https://t.co/wlyk5Nutev
It’s an independent project built on Kaspa, not a Kaspa Core project.
This is a big step for Kaspa’s programmable L1.
KUSD, a KAS-backed stablecoin prototype, is now running on TN10 using Toccata covenants and SilverScript.
The developer reports testing the full core flow: collateralized positions, repayments, savings, challenges, auctions and a reserve backstop.
That’s a significant jump from talking about what Kaspa’s new programmability could enable to actually seeing a financial protocol built with it.
KUSD is still experimental: TN10 only, unaudited, and there’s no proof yet that it can reliably maintain a $1 peg.
But the milestone is real.
Kaspa’s programmable L1 is starting to produce actual DeFi prototypes.
Source:
https://t.co/vHhTJPtPrF
i’ve spent the last few months bringing native Kaspa payments to x402.
tldr: x402 is an open, chain agnostic payment protocol built around the long existing HTTP 402 code. kaspa-x402 intends to bring native KAS into that shared standard.
i keep seeing people use “x402” to mean anything built around the HTTP 402 response code. HTTP 402 has existed for decades, and anyone can hang their own payment flow off it.
x402 refers to a specific open protocol built on top of that code. it standardises how a server requests payment, how a client authorises it, and how the payment is verified and settled.
it can be used for paid APIs, AI agents buying data or tools, and MCP servers charging per call. kaspa-x402 adds native KAS to the existing x402 v2 flow.
there are two payment paths:
- exact for a normal one off KAS payment, with an optional KIP10 additive mode
- batch-settlement for small or repeated payments, where the client funds a SilverScript covenant once and signs a fixed charge voucher for each request
the longer term goal is to contribute the Kaspa support upstream into the wider x402 project, so Kaspa works within the same standard being adopted elsewhere.
i’m looking for humans and agents to go through it deeply before the final v1 release. read the code, build against it, test the assumptions and try to break it. if you find something, pls let me know.
code: https://t.co/HQTn3Y680j
upstream x402: https://t.co/dnpb8ObItS
docs: https://t.co/gOtTQsEeMw
TN gateway: https://t.co/xauSZSmCXy
discussion: https://t.co/GANHBrDaIR