public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Paul Sztorc <truthcoin@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] CTV + CSFS: a letter
Date: Tue, 10 Jun 2025 12:04:14 -0700 (PDT)	[thread overview]
Message-ID: <f8220f1b-831a-4459-8dee-7fc81f4b666cn@googlegroups.com> (raw)
In-Reply-To: <0B7CEBEE-FB2B-41CF-9347-B9C1C246B94D@sprovoost.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1839 bytes --]

> What I _would_ oppose is a Python based alternative implementation and 
activation client like co-signer Paul Sztorc proposed.[3]

I have done no such thing.

The bip300301_enforcer is in rust [0]. Furthermore, it is not an 
"alternative" to Core --  it must connect to Bitcoin Core, via ZMQ. (But it 
is an "activation client" -- of a kind.)

(Anyone who glanced at the github for 2 seconds, would see all of these 
things, by the way.)
(Sjors, you may be confusing my project, with Bitcoin Core, which contains 
python, including a siget-mining-script.)

CUSF is clever -- because it **frees** Core from the headache and 
responsibility of soft fork activation (which I know many people here 
hardly enjoy). That is why it is better -- I can activate my own thing, 
without bothering you all. And I don't have to "compete" with CTV to be 
further ahead "in line" (or whatever). So I am free to appraise CTV 
rationally.

We all know that Core is a meritocracy. And that every decision and 
sentence uttered by Core is a perfect work of divine truth -- free of all 
the flaws that have plagued every other organization throughout history. 
Lucky us! Just think, in other organizations, people sometimes allow their 
prejudice to color their judgement, occasionally jumping to conclusions 
that are incorrect -- not here though. Here it's all based on merit, baby. 
No need for a plan B!

Cheers,
Paul

[0] https://github.com/LayerTwo-Labs/bip300301_enforcer

-- 
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/f8220f1b-831a-4459-8dee-7fc81f4b666cn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2189 bytes --]

  parent reply	other threads:[~2025-06-12  0:02 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 11:40 [bitcoindev] CTV + CSFS: a letter James O'Beirne
2025-06-09 12:51 ` Michael Folkson
2025-06-09 14:41   ` James O'Beirne
2025-06-09 15:56     ` Michael Folkson
2025-06-09 13:51 ` Matt Corallo
2025-06-09 14:43   ` James O'Beirne
2025-06-09 17:51     ` Matt Corallo
2025-06-09 19:27       ` /dev /fd0
2025-06-09 21:12         ` Matt Corallo
2025-06-09 18:55 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-10  2:02   ` Paul Sztorc
2025-06-09 23:02 ` Andrew Poelstra
2025-06-10  2:08   ` David A. Harding
2025-06-10 13:23     ` Andrew Poelstra
2025-06-10 17:17       ` Matt Corallo
2025-06-10 23:42         ` Antoine Riard
2025-06-12  3:34           ` James O'Beirne
2025-06-10 23:42         ` Antoine Riard
2025-06-11 13:52         ` Peter Todd
2025-06-10 14:03     ` James O'Beirne
2025-06-10 16:56       ` Sjors Provoost
2025-06-10 17:15         ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-10 19:04         ` Paul Sztorc [this message]
2025-06-11 18:09         ` Brandon Black
2025-06-10  2:28   ` Melvin Carvalho
2025-06-10 13:19     ` Greg Sanders
2025-06-11 14:12       ` James O'Beirne
     [not found]         ` <CAB3F3Dsf8=rbOyPf1yTQDzyQQX6FAoJWTg16VC8PVs4_uBkeTw@mail.gmail.com>
2025-06-11 16:50           ` James O'Beirne
2025-06-11 18:34             ` James O'Beirne
2025-06-11 20:30             ` Matt Corallo
2025-06-12  0:59               ` Harsha Goli
2025-06-12 18:04                 ` Matt Corallo
2025-06-12 18:38                   ` James O'Beirne
2025-06-12 18:43                     ` Matt Corallo
2025-06-12 19:51                     ` Andrew Poelstra
2025-06-12 22:44                       ` Matt Corallo
2025-06-12  2:06 ` Greg Maxwell
2025-06-12  3:23   ` James O'Beirne

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=f8220f1b-831a-4459-8dee-7fc81f4b666cn@googlegroups.com \
    --to=truthcoin@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