1(self.webpackChunk_N_E=self.webpackChunk_N_E||[]).push([[3829],{75040:function(e,n,o){(window.__NEXT_P=window.__NEXT_P||[]).push(["/writing/zero-carbon-lime-grants",function(){return o(17994)}])},17994:function(e,n,o){"use strict";o.r(n),o.d(n,{__N_SSG:function(){return h},default:function(){return g},markdoc:function(){return f}});var t=o(67294),i=o(1272),r=o(4211),a=o(84266),s=o(12591),c=o(3486);let l={tags:(0,a.w)(s),nodes:(0,a.w)(c),functions:(0,a.w)({}),...(0,a.w)({})},m=new r.ZP.Tokenizer({allowComments:!0}).tokenize('---\ntype: announcement\nhref: /writing/zero-carbon-lime-grants\ntitle: Frontier supports solutions to produce zero carbon lime with R&D grants\ndescription: Frontier has awarded $2M in R&D grants to Leilac (UK) and SaltX (Sweden) to support the production of zero carbon limeâlime produced without net COâ emissionsâon behalf of Stripe, Shopify, and Google. Zero carbon lime could be a low cost feedstock for several carbon removal applications.\nsocial:\n image: /images/writing/zero_carbon_lime_grants/social.png\nimage: /images/leilac/primary.jpg\ndate: 2026-01-22\npathway:\n - marine_carbon_removal\n - direct_air_capture\n---\n\n[Frontier](/) has awarded $2M in R\\&D grants to Leilac (UK) and SaltX (Sweden) to support the production of zero carbon lime â lime produced without net COâ emissions â on behalf of Stripe, Shopify, and Google. Zero carbon lime could be a low cost feedstock for several carbon removal applications. Frontierâs goal is to accelerate the lowestâcost, most commercially ready processes for producing zeroâcarbon lime, starting with these two companies. \n\n### Why zero carbon lime matters for carbon removal\n\nQuicklime is made by heating limestone, one of the most abundant rocks on Earth. When quicklime later reacts with COâ from the atmosphere or ocean, it turns back into limestone, permanently storing the carbon in a solid rock. Because the reaction is natural and limestone is abundant, quicklime is very compelling for carbon removal, particularly for ocean liming and some approaches to direct air capture. \n\n### Reducing emissions in lime production\n\nToday, making quicklime is carbon-intensive. Limestone is heated to very high temperatures in a calciner, which converts it into quicklime and releases COâ as a by-product. Conventional calciners vent that COâ as process emissions. If they run on fossil fuels, they generate additional emissions on top of that. \n\nThose upstream emissions must be counted against any carbon removal project, and they can significantly erode its climate benefit. Producing quicklime without emissions is therefore a necessary piece of the puzzle to scale carbon removal pathways that rely on it. \n\nOne way to remove emissions from the process is by using electricity instead of fuel to produce heat. This eliminates energy emissions and leaves only the process emissions, which are easy to capture as they are just concentrated COâ. \n\nIn the last decade, several electric calcination technologies have emerged to produce low- or zero-carbon lime for the cement industry, but high costs have limited their uptake. Quicklime intended for carbon removal does not need the same specifications as cement: the purity, particle size, moisture level, and other quality tolerances can be adjusted to reduce the cost of production. Designing electric calcination systems specifically for carbon removal applications could therefore lower the overall cost of quicklime-dependent approaches. \n\n\nConventional versus electric calcination. {% .caption %}\n\n### Meet the projects\n\n{% prose-inset %}\n\n{% project-blog-description "climsup_leilac" /%}\n{% project-blog-description "climsup_saltx" /%}\n\n{% /prose-inset %}'),u=r.ZP.parse(m,{slots:!0}),p=u.attributes.frontmatter?i.ZP.load(u.attributes.frontmatter):{},{components:d}=(0,a.J)(l);var h=!0;let f={frontmatter:p};function g(e){let n=e.markdoc;return r.RZ.react(n.content,t,{components:{...d,...e.components}})}}},function(e){e.O(0,[6130,2649,8391,4321,2222,3061,608,4908,3303,8036,951,8461,2645,2591,2888,9774,179],function(){return e(e.s=75040)}),_N_E=e.O()}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.