From: Oleg Andreev <oleganza@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Flame: confidential transactions with Bitcoin proof-of-burn consensus
Date: Wed, 30 Sep 2026 15:33:27 -0700 (PDT) [thread overview]
Message-ID: <7aa8774d-c650-457d-9013-dfb817b728d6n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1893 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 2231 bytes --]
next reply other threads:[~2026-10-01 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 22:33 Oleg Andreev [this message]
2026-10-04 13:18 ` [bitcoindev] Re: Flame: confidential transactions with Bitcoin proof-of-burn consensus waxwing/ AdamISZ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7aa8774d-c650-457d-9013-dfb817b728d6n@googlegroups.com \
--to=oleganza@gmail.com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox