public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Bryan Bishop <kanzure@gmail•com>
To: mm-studios <mm@mm-studios•com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>,
	Bryan Bishop <kanzure@gmail•com>
Subject: Re: [bitcoin-dev] brickchain
Date: Wed, 19 Oct 2022 08:54:11 -0500	[thread overview]
Message-ID: <CABaSBaxCkJvNqojEX3q7bCg857dCGUwD-XRuAKw7315aL6c-BQ@mail.gmail.com> (raw)
In-Reply-To: <mOBAWIbHTgkSrCJ9IEBJgArqUNYcNSDQawhUzaiYyliaPDQT_YDfI5CLoDPZgEt43mePJof-CJfxzFxgXMUe6ONDJ4j5Bzk1QGjd50S9gb8=@mm-studios.com>

[-- Attachment #1: Type: text/plain, Size: 425 bytes --]

Hi,

On Wed, Oct 19, 2022 at 6:34 AM mm-studios via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> Fully filled brick B0, with a hash that doesn't meet the difficulty rule,
> would be broadcasted and nodes would have it on in a separate fork as usual.
>

Check out the previous "weak block" proposals:
https://diyhpl.us/~bryan/irc/bitcoin/weak-blocks-links.2016-05-09.txt

- Bryan
https://twitter.com/kanzure

[-- Attachment #2: Type: text/html, Size: 1054 bytes --]

  parent reply	other threads:[~2022-10-19 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19  9:04 mm-studios
2022-10-19 13:40 ` angus
2022-10-19 22:47   ` mm-studios
2022-10-19 13:54 ` Bryan Bishop [this message]
2022-10-19 14:24 ` Erik Aronesty
2022-10-19 16:03   ` mm-studios
2022-10-19 21:34     ` G. Andrew Stone
2022-10-19 22:53       ` mm-studios
2022-11-08 14:16     ` Erik Aronesty
2022-11-08 14:25       ` mm-studios
2022-11-08 15:49         ` Erik Aronesty
2022-11-08 16:31           ` mm-studios

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=CABaSBaxCkJvNqojEX3q7bCg857dCGUwD-XRuAKw7315aL6c-BQ@mail.gmail.com \
    --to=kanzure@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=mm@mm-studios$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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