Problem: A typical HW today would display the "destination" of a transaction in the form of a bitcoin address. The correct usage would be for a user to verify this address on a third device (mobile phone, for example). Proposed improvement: The HW could know pubkeys or xpubs it does not hold the private keys for, and display a label (or understand it for logic reasons, such as "expected pubkeys" as the previous example). Problem: currently HW cannot "identify" addresses or keys. To level-up from that, instead of putting byte strings on a stack, you could have some other data structure than a stack -- eg one that allows nesting. The thing that's most appealing to me about bitcoin script as it stands (beyond "it works") is that it's really pretty simple in an engineering sense: it's just a "forth" like system, where you put byte strings on a stack and have a few operators to manipulate them. To me, it seems like chia lisp is a better answer to the problem here than the Simplicity language. Granted, I've only really been looking at chia lisp for a bit over a week, but it really seems to me like a case where it might be worth putting that philosophy into practice.
And while I've never really coded in lisp at all, my understanding is that its biggest problems are all about doing things efficiently at large scales -- but script's problem space is for very small scale things, so there's at least reason to hope that any problems lisp might have won't actually show up for Youtu site this use case. This wouldn’t be any more effective at preventing fee sniping, but it would provide a good reason for regular wallets to set their nSequence values to the same values that are required for transactions in certain multisignature-based contract protocols, such as ideas for coinswaps and taproot-enabled LN. While this can be exploited for fee attacks, it is a bigger threat to pre-signed transactions protocols. Coins are bought with national currencies, and a fee is paid for every transaction. TXHASH opcode to specify which parts of a spending transaction should be serialized and hashed, with the hash digest being put on the evaluation stack for later opcodes to use. While I mainly foresee issues/improvements that may affect Revault, I would be really happy to see people joining this thread with any other ideas and remarks that would benefit some parts of Bitcoin that I overlooked.
>
So, will we need to be keeping track of the UTXO actually not being moved while it is the stand-in to have announced the channel? If you don't assume the computer on which the transaction is crafted is compromised, then you don't need a hardware wallet. If you assume it may be compromised, then the HW needs to be able to defend against those. The article highlights that the average carbon intensity of electricity consumed by the Bitcoin network may have increased from 478.27 gCO2/kWh on average in 2020 to 557.76 gCO2/kWh in August 2021. The carbon footprint provided by the Bitcoin Energy Consumption Index is based on this carbon intensity. However, there are a number of projects seeking to reduce the carbon footprint of Bitcoin and cryptocurrency in general. You can exchange XMR for BTC there too. If you don't want to mine bitcoin, it can be bought using a cryptocurrency exchange. This isn’t fractional-reserve bitcoin, is it?</<br>r>
The first thing to remember is that the crypto market, including Bitcoin, is extremely volatile. One of the things people sometimes claim about bitcoin as an asset, is that it's got both the advantage of having been first to market, but also that if some altcoin comes along with great new ideas, then those ideas can just be incorporated into bitcoin too, so bitcoin can preserve it's lead even from innovators. Gavin Andresen was the former lead maintainer for the software client. Of course, you can also buy Bitcoin in person if you know someone who holds BTC or if you find a seller on a peer-to-peer Bitcoin marketplace. In the case where a user does not pay the fee, the company can take this as a signal that they are no longer interested in the service. This compensates the company for the case where their liquidity is NOT being used. That way they can put their liquidity to use somewhere else that is more productive for the rest of the network. I should add a command to timestamp a file that way. It seems to end up equivalent to doing things in a list oriented way to me. A high Bitcoin dominance ratio typically infers altcoins are doing poorly in the market, or at the very least poorly when compared with Bitcoin.