From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Thu, 01 Oct 2026 10:07:20 -0700 Received: from mail-oo1-f59.google.com ([209.85.161.59]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1xCKFc-0005Qx-2k for bitcoindev@gnusha.org; Thu, 01 Oct 2026 10:07:20 -0700 Received: by mail-oo1-f59.google.com with SMTP id 006d021491bc7-6dccace8338sf2814254eaf.3 for ; Thu, 01 Oct 2026 10:07:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1790874434; x=1791479234; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:message-id:to:from:date:sender:from:to:cc :subject:date:message-id:reply-to:content-type; bh=/APx4eBpJQrve4P3otWX4pZ/13AM61A1+kbof142LEs=; b=yAneNtznYpW43SJ5j9+HovCivWHjIMjciSNNugJfY5IvC0Ha0ZJ75jgEUzVkxc1+Yq 9z9RpM9xWx20xdyHxpKRDhsQk5xoWVnI8QQhC7s4TicCEowL490NgLzawLyrCc4V8ArD xSGP/DEN4L43QB2dnbvmUI5RIsv5qiUH3ht5hJY6K2BkMUwmHvB33gU8PSjdBXOtgg4W pHNtmkf/gwUEOg97JocosJ9R4S4wEmImYd8e+8tuXlR8ehbiXg6r9JgjTZsFIzBJCzLJ zB8A8KuF2EIDXNmZQtc246QCTX99YJonQBHs9nqWd+djNei0avACxjuLO3ZwawxNsIGv XLRA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1790874434; x=1791479234; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:message-id:to:from:date:from:to:cc:subject :date:message-id:reply-to:content-type; bh=/APx4eBpJQrve4P3otWX4pZ/13AM61A1+kbof142LEs=; b=SYf434GPJUEx+H80/zISheFkLrkt7aK+RLFairDN2Jyq7IjonSvFJV7dl8k0BaZIf7 +AUmS7JHgjU0b8YAjYMnFkZmsLyaWyWAGhrlIDHtA8/ghbvxy3iXTGQGTA87XNy+6Grs zdO8f+kRBUPFNIDQegYDceg+ShT9e7I+GCGSARzkZD6TpLeuo22oAt0EkSUzD898ITJh 34WGbR+wkaA8mCmo5/7uxa2a81ANSuyZaZVtp2j+dT4WC7DslsoW2CW0lc84Xa07borE nOI2/5CLsx6suMf1Sg9Y/MAknx7i84lh75wDDJQIW+8We8ClBsOEJ4TiCOzJT9Wrqtoq UPbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790874434; x=1791479234; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:message-id:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to:content-type; bh=/APx4eBpJQrve4P3otWX4pZ/13AM61A1+kbof142LEs=; b=Ij59J/t8XW7vCbmNfTC4CDat3qXYSpbhQkkE1XV4lGRvJn5mRt9dN5CUXh4Xjjrm5A C2Y8ua30h2OEjjljLx8A1qUy6j+zYWd7rWu+/uWu6uEanqezAyxBLsFah63p+3RqknwX ++rQzi+rNDZU0ku+sX2nCDuJGydGMxFtz9Ad7QFtCLjn09lNiNNZZv7iO8yCMP+Kc1r3 Qk8lK2H6vMCISqCYNT4M5pwVABYC9IQAXEoYNZQYVx87H8TS0e/P9o6J/ocKHadyNaho 3AV59FG2/6qKlgQJUGMi9t0Lzd2U7cOQMF1yAOReisD4Js7fo1nsJmsTQ76oSYVHNPE6 pmXg== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AKwUvBwo1kTrwEwPAgoGZ0JpVMx7+rhT5a6Xg6Usj81/T1R+rg9LhqxCaG61VF+0WpsUoH/GdbfCye6THQgd@gnusha.org X-Gm-Message-State: AFuF++m6leXebEWTKLsC6N0G8S2MMxwgjw4CAf7KjxO4Xo5fa3MLJlQA A3z9NBMPU850BvJCWBo4nL8R9MNPEHNxG6xFQP2qmLpAfa7C83jQzfef X-Received: by 2002:a05:6820:4b13:b0:6d7:ee8f:50e5 with SMTP id 006d021491bc7-6dcf4b6ab6cmr4659177eaf.38.1790874433923; Thu, 01 Oct 2026 10:07:13 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="ATskLdcFwCnFTdFxA0aa+jfBkmoPROVIS4lPow8r/DwuasRraw==" Received: by 2002:a05:6871:b2c:b0:49d:f333:97ce with SMTP id 586e51a60fabf-49df333a7e3ls1428872fac.1.-pod-prod-09-us; Thu, 01 Oct 2026 10:07:06 -0700 (PDT) X-Received: by 2002:a05:6808:6f89:b0:4e6:a21a:8c38 with SMTP id 5614622812f47-4f1b907a71fmr5198959b6e.39.1790874426739; Thu, 01 Oct 2026 10:07:06 -0700 (PDT) Received: by 2002:a05:690c:c18b:b0:89f:e265:68a9 with SMTP id 00721157ae682-8ac44ba2c36ms7b3; Wed, 30 Sep 2026 15:33:28 -0700 (PDT) X-Received: by 2002:a05:690c:dc5:b0:8ac:dbb9:21fd with SMTP id 00721157ae682-8acdbb92b46mr3254727b3.104.1790807608096; Wed, 30 Sep 2026 15:33:28 -0700 (PDT) Date: Wed, 30 Sep 2026 15:33:27 -0700 (PDT) From: Oleg Andreev To: Bitcoin Development Mailing List Message-Id: <7aa8774d-c650-457d-9013-dfb817b728d6n@googlegroups.com> Subject: [bitcoindev] Flame: confidential transactions with Bitcoin proof-of-burn consensus MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2572_697915764.1790807607781" X-Original-Sender: Oleganza@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_Part_2572_697915764.1790807607781 Content-Type: multipart/alternative; boundary="----=_Part_2573_380507212.1790807607781" ------=_Part_2573_380507212.1790807607781 Content-Type: text/plain; charset="UTF-8" I've been working on Flame, a Bitcoin "side chain", based on proof-of-burn consensus: a fully decentralized protocol in which nodes continuously burn bitcoins to protect against double-spending. I believe this approach avoids shortcomings of proof-of-stake, merged mining, and alternative proof-of-work protocols. There are no special privileges for developers, miners, or validators. The network architecture combines proposals by Bitcoin developers and a few ideas from other networks, as well as my earlier work, which some of you may know from Chain's TxVM (2017) and Interstellar's ZkVM (2019). Flame provides transaction confidentiality with a programmable constraint system based on Bulletproofs and Ristretto, Taproot-based predicates, Utreexo storage for unspent outputs, and actors with leased storage. I've aimed for a balanced, practical solution for decentralized applications and privacy, with a security model as close to Bitcoin's as possible, while having a purely market-driven adoption strategy that does not require changes to Bitcoin's consensus rules. I suppose proof-of-burn system on top of Bitcoin creates some interesting dynamics for Bitcoin economics: in terms of demand for block space and long-term relative effects on miners' rewards. The overview is available at: https://runflame.org/flame.pdf The work-in-progress implementation: https://github.com/runflame/flame-lib The project is still under development. Mainnet launch is planned for January 2027. Oleg. -- You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/7aa8774d-c650-457d-9013-dfb817b728d6n%40googlegroups.com. ------=_Part_2573_380507212.1790807607781 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I've been working on Flame, a Bitcoin "side chain", based on proof-of-burn = consensus: a fully decentralized protocol in which nodes continuously burn = bitcoins to protect against double-spending. I believe this approach avoids= shortcomings of proof-of-stake, merged mining, and alternative proof-of-wo= rk protocols. There are no special privileges for developers, miners, or va= lidators.

The network architecture combines proposals by Bitcoin= developers and a few ideas from other networks, as well as my earlier work= , which some of you may know from Chain's TxVM (2017) and Interstellar's Zk= VM (2019). Flame provides transaction confidentiality with a programmable c= onstraint system based on Bulletproofs and Ristretto, Taproot-based predica= tes, Utreexo storage for unspent outputs, and actors with leased storage. I= 've aimed for a balanced, practical solution for decentralized applications= and privacy, with a security model as close to Bitcoin's as possible, whil= e having a purely market-driven adoption strategy that does not require cha= nges to Bitcoin's consensus rules.

I suppose proof-of-= burn system on top of Bitcoin creates some interesting dynamics for Bitcoin= economics: in terms of demand for block space and long-term relative effec= ts on miners' rewards.

The overview is available at:
https:= //runflame.org/flame.pdf

The work-in-progress implementation:https://github.com/runflame/flame-lib

The project is still un= der development. Mainnet launch is planned for January 2027.

Ole= g.

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/7aa8774d-c650-457d-9013-dfb817b728d6n%40googlegroups.com.
------=_Part_2573_380507212.1790807607781-- ------=_Part_2572_697915764.1790807607781--