On Sat, Oct 21, 2023 at 09:05:35PM +0100, Antoine Riard via bitcoin-dev wrote:
> In the meanwhile, lightning experts have already deployed mitigations which
> are hardening the lightning ecosystem significantly in face of simple or
> medium attacks. More advanced attacks can only be mounted if you
Available from: https://github.com/petertodd/bitcoin/tree/full-rbf-v25.1
eg:
git clone -b full-rbf-v25.1 https://github.com/petertodd/bitcoin.git
What is this? It's Bitcoin Core v25.1, with Antoine Riard's full-rbf peering
code, and some additional minor updates to it. This does two things
On Tue, Oct 24, 2023 at 03:56:55PM -0700, Olaoluwa Osuntokun via bitcoin-dev
wrote:
> TL;DR: let's just use an automated system to assign BIP numbers, so we can
> spend time on more impactful things.
Yes, an easy way to do that is to use a mathematical function, like SHA256()
or Pubkey().
Of
On Mon, Oct 23, 2023 at 06:32:47PM +0200, Tim Ruffing wrote:
> On Mon, 2023-10-23 at 15:35 +, Peter Todd via bitcoin-dev wrote:
> > Thus
> > we should limit BIP assignment to the minimum possible: _extremely_
> > widespread
> > standards used by the _entire_ Bitcoin community, for the core
> >
On Sat, Oct 21, 2023 at 01:08:03AM -0400, Ethan Heilman via bitcoin-dev wrote:
> OP_CAT fails if there are less than two values on the stack or if a
> concatenated value would have a combined size of greater than the
> maximum script element size of 520 Bytes.
Note that if OP_CAT immediately
Hi all,
After the transaction recycling has spurred some discussion the last
week or so, I figured it could be worth sharing some research I’ve
done into HTLC output aggregation, as it could be relevant for how to
avoid this problem in a future channel type.
TLDR; With the right covenant we can
I have to admit - I'm somewhat baffled at the enthusiasm for a "just CAT"
softfork, since I can't see that it would achieve much. It's indicative to
me that there isn't a compelling example to date that (i) actually has
working code and (ii) only relies upon CAT. I'm not averse to CAT, just
I support OP_CAT, along with reasonable resource-consumption limiters.
Implementation as a UASF would help build confidence in that method.
I also support moving forward on other opcodes as soon as they are
known to be safe and maintainable; whether for introspection, tx
unpinning, or vaults.
Bitcoin Core version v24.2 is now available from:
https://bitcoincore.org/bin/bitcoin-core-24.2/
Or through BitTorrent:
Bitcoin Core version v24.2 is now available from:
https://bitcoincore.org/bin/bitcoin-core-24.2/
Or through BitTorrent:
10 matches
Mail list logo
