From: "/dev /fd0" <alicexbtong@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Table for economic nodes: Covenants Support - Bitcoin Wiki
Date: Wed, 5 Mar 2025 15:09:10 +0530 [thread overview]
Message-ID: <CALiT-ZoTQYx9_4bd1TTzqGCgQJ-rp0meCM14eoNOJLW_mOEo2w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
Hi everyone,
A list of use cases for covenants (WIP) including some killer apps:
https://en.bitcoin.it/wiki/Covenants_Uses
As mentioned in an earlier [email][0], we have added more evaluations from
developers in the table. All reasonable objections have been answered. It's
time for [economic nodes][1] to share their opinion so that we can make
some progress in the discussion.
Once enough entries are added in the 'economic nodes' table, the next step
would be IRC meetings, workshops etc.
I would like to thank all the developers who have added their evaluations.
Matt Black, Jeremy Rubin and stutxo helped me with the use cases wiki page.
[0]: https://groups.google.com/g/bitcoindev/c/QOnpM4Ixmms/m/8m1_l5RSDAAJ
[1]: https://en.bitcoin.it/wiki/Full_node#Economic_strength
/dev/fd0
floppy disk guy
--
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/CALiT-ZoTQYx9_4bd1TTzqGCgQJ-rp0meCM14eoNOJLW_mOEo2w%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 1825 bytes --]
next reply other threads:[~2025-03-05 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 9:39 /dev /fd0 [this message]
2025-03-05 13:32 ` [bitcoindev] Re: Table for economic nodes: Covenants Support - Bitcoin Wiki /dev /fd0
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=CALiT-ZoTQYx9_4bd1TTzqGCgQJ-rp0meCM14eoNOJLW_mOEo2w@mail.gmail.com \
--to=alicexbtong@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