Matthew Zipkin

🥪

No: https://discord.com/channels/822591034202521641/825772593180704768/992125032060944564 > Free cheese sandwich to whoever opens issue #100!

The `chain` folder also currently includes the addr and tx indexes. Those will get moved out to their own folder hopefully with indexer refactor in hsd v5 (to pull from...

Oooh, here's a thought: Send all OPEN's to a `nulldata` address! A nulldata address is the segwit-only version of `OP_RETURN`. It uses witness program version `31` (which is otherwise invalid)...

As part of this issue, we may want to consider a soft fork that makes 0-value `OPEN`s unspendable, and then migrate the UTXO set database to clear out the hundreds...

Idea: hsd wallet could just have a `--no-resend` option and check it in `walletDB.syncNode()`

This should definitely be linked to https://github.com/handshake-org/hsd/issues/487 Maybe the behavior is like this: Every time we connect to a node and complete the handshake on either channel, check if we...

Can you explain your use case a bit more? This action is potentially risky since a BID without REVEAL can destroy money, and the wallet may not have the private...

but whats wrong with just using the wallet's next receive address? https://github.com/handshake-org/hsd/blob/107ed2be9280bb4292d21330e7d1ace62da9a002/lib/wallet/wallet.js#L1694 I'm just wondering if this is so useful we need to change the API and continue to maintain...

@buffrr and I have discussed this a lot as well but the issue is how to handle re-orgs (more on that in a sec). Your point about getting SOA from...