HN user
Yep given the weekly drip feed of information and charging fingerprint matching a high-end NMC battery. I am finding this more and more sus. It's probably a very high end expensive battery but not the miracle that was promised in CES.
Donut Lab drops another VTT report this time focused on High Temperature Performance Here is the TLDR:
The Battery & Test Setup
- Cell tested: Donut Lab "Solid-State Battery V1" – a pouch cell labeled DL2
- Nominal specs: 26 Ah capacity, 3.6V nominal voltage, 94 Wh energy
- Tested by: Independent third-party lab (VTT) at customer request
- Test equipment: PEC ACT0550 cell tester + Weiss climate chamber capable of -40°C to +180°C
- Actual capacity measured: 24.9 Ah (slightly below 26 Ah nominal, but within reasonable variance)
- +80°C discharge: Delivered 110.5% of room-temperature capacity (27.48 Ah vs 24.87 Ah at 24A)
- +100°C discharge: Delivered 107.1% of room-temperature capacity (27.61 Ah at 12A)
- Energy efficiency: ~89-90% round-trip efficiency observed
- Charging: All charging performed at +20°C for safety; cell accepted charge normally after both high-temp tests
Cell used a 2.4kg steel plate on top for mechanical pressure during testing
Post-100°C test: Cell pouch lost vacuum (visible inflation/deflation) but remained electrically functional
No visible damage after 80°C test; cell appeared physically intact after 100°C test despite vacuum loss
Energy density: No weight and volume was mentioned
Cycle life: VTT ran only 3 test cycles total.
Cost Claims: Nothing about cost is mentioned
Material Claims: No chemical analysis or materials analysis.
No abuse testing: No nail penetration, no overcharge, no short-circuit, no crush tests.
First report for Donut lab battery is out. Here is the TLDR
Specs
26 Ah nominal capacity at 1C discharge rate
94 Wh nominal energy with 3.6V nominal voltage
Operates within 2.7V – 4.15V recommended range (max charging to 4.3V)
5C charging (130A): 0-80% in ~9.5 minutes, 0-100% in ~13.5 minutes
11C charging (286A): 0-80% in ~4.9 minutes, 0-100% in ~7.3 minutes
Successfully delivered 98.4-99.6% of charged capacity even after extreme 11C charging
Tested with both one-sided and two-sided heat sinks to simulate real-world conditions
With dual heat sinks: Peak temps of 47°C (5C) and 63°C (11C) — well within safe limits
With single heat sink: Reached 61.5°C (5C) and up to 89°C (11C) — still functional but approaching thermal limit
Energy density: No weight and volume was mentioned
Cycle life: VTT ran only 7 test cycles total.
Cost Claims: Nothing about cost is mentioned
Material Claims: No chemical analysis or materials analysis.
Extreme Temperature Performance: No cold weather testing. No high-temperature testing.
No abuse testing: No nail penetration, no overcharge, no short-circuit, no crush tests.
I built a small web tool that generates a single install command for multiple Linux applications. You select apps and a distribution (Ubuntu, Fedora, Arch, etc.), and it outputs grouped commands for APT, DNF, Pacman, Flatpak, Snap, and AUR, including setup steps when needed.
I built a small web tool that generates a single install command for multiple Linux applications. You select apps and a distribution (Ubuntu, Fedora, Arch, etc.), and it outputs grouped commands for APT, DNF, Pacman, Flatpak, Snap, and AUR, including setup steps when needed.
Inspired by the friction of repeatedly setting up fresh Linux machines.
Hi guys, after your feedback from last time, I have turned my simple storage cost calculator into a financial cost modeling tool. I have made every effort to include all types of costs involved. Do you think I have missed something? I would love to hear your thoughts on it.
I have read and watched these articles and videos where people seem to have a problem with Microservice, Kubernetes, cloud providers, or anything that's not a PHP server sitting behind an nginx running on a $5 VPS. I have also seen the front-end analogy of these types of posts, where anything that is not written using HTML, CSS, and jQuery is unnecessary bloat. I will soon write a blog, which I think will cover more points and nuances of both sides. For now, here are some of my scattered thoughts.
- If deploying your MVP to EKS is overengineering, then signing a year-long lease for bare metal is hubris. Both think one day they will need it, but only one of them can undo that decision.
- Don't compare your JBOD to a multi-region replicated, CDN-enabled object store that can shrug off a DDoS attack. One protects you from those egress fees, and the other protects you from a disaster. They are not comparable.
- A year from now, the startup you work for may not exist. Being able to write that you have experience with that trendy technology on your resume sure sounds nice. Given the layoffs we are seeing right now, putting our interest above the company's may be a good idea.
- Yes, everyone knows modern CPUs are very fast, and paying $300/mo for an 8-core machine feels like a ripoff, but unless you are business of renting GPUs and selling tokens. Compute was never your cost center; it was always humans. For some companies, not being able to meet your SLA due to talent attrition is scarier than the cloud bill.
I know these are one-sided arguments, and I said I would cover both sides with more nuance. I need some time to think through all the arguments, especially on the frontend side. I will soon write a blog.
Most cloud pricing calculators online are built by a cloud provider or storage server seller. As a result, they are too simplistic and always show their option as the cheapest. I have built an actual pricing calculator that takes into account every single variable to give you a detailed yearly breakdown for both scenarios.
You will be surprised to learn that once you start accounting for different variables, on-premises may not always be the cheapest option.
Features: • Comprehensive cost analysis over 1-30 years • Hardware, software, power, bandwidth breakdowns • Real-time cost projections with growth factors • Interactive charts & detailed comparisons • Export-ready financial models
Intresting, I am working on another list of more advance rate limiting algorithms. I will add GCRA there.
Sorry about that that is my blogging platform Hashnode. It was lesser of four evils:
- Medium which paywalls the article and forces you to sign up just to read.
- Substack has same problem, it's great for funneling people to your paid newsletter but there is a sign up banner as soon the page loads.
- Build your own and miss out on the social aspect and there's no proof if the numbers are real.
Does CGNAT do rate limiting? If so then is there some documentation I can lookup.
Now that you have mentioned it should have been working principle or algorithm. It made sense in my head. English isn't my first language sorry about that.
- I like bullet points, they are easy to read.
- "Working" I wanted to keep things consistent.
- Content getting cut was a limitation of iframe. Most blogging platform don't allows you to embed another page. This was best I could do given the limitation.
- I do use AI to bounce ideas, but a lot of effort went into getting the apps working as intended.
It was Shadcn, Tailwind.
Yes, I usually prompt (Claude, GPT and Deepseek),on my rough vision, and take ideas from all of them. They never quite get it right on their own. But for a code that's deploy and forget, AI generated code is good enough.