Peter Todd

ACK

"Be an otherwise valid [TRUC](https://github.com/bitcoin/bips/blob/master/bip-0431.mediawiki) transaction adhering to the corresponding topological constraints" What is the rational to limit ephemeral outputs to being spent by transactions adhering to the TRUC standard?...

> > What is the rational to limit ephemeral outputs to being spent by transactions adhering to the TRUC standard? The goal of ensuring that dust outputs are immediately spent...

One approach here could just be to tell people they may need to import their seed into a wallet like Bitcoin Core that does in fact have a much larger...

This BIP is missing an explanation of how it is expected to work with future nVersion upgrades. Eg if we add a third consensus critical transaction version, how should that...

TRUC behavior is not desirable for all transactions; it is not a clear upgrade. Thus, the obvious question is how do we expect a future soft fork version upgrade to...

So an obvious example of where TRUC's use of v3 transactions would cause a problem is if we had a situation similar to v2 transactions, where an upgrade happened that...

@Kruwed > For payments in coinjoin, it is sensible to allow users to pay directly to reused addresses. Denying this ability only forces them to consume extra block space by...

On Sat, Mar 29, 2025 at 09:04:40AM -0700, prononext wrote: > prononext created an issue (opentimestamps/opentimestamps-client#157) > > It would by really nice to have the -d Hash Input possibility...

> where should I start in your opptinion? Look at the code of course! Starting with: https://github.com/opentimestamps/opentimestamps-client/blob/master/otsclient/args.py