ic VS Bitcoin

Internet Computer blockchain (ICP) — a general-purpose blockchain system developed by the DFINITY Foundation (written in Rust);

Yes, non-rust dependencies can be a pain. We addressed this issue in three ways: 1. Sometimes, it just works™ if the crate has a copy of the C code and uses the cc crate to compile it. It's usually slow to compile C in a build script, but it works. 2. Sometimes, we write a custom BUILD script for direct dependencies and link external libraries by hand. Example: lmdb and lmdb-sys. 3. If all of the above is not an option or is too much work, we add a native library to the Docker container that runs our builds.

One thing that sticks out to me is that, while their code is open source, it has a restrictive license, the Apache License: https://github.com/dfinity/ic/blob/master/LICENSE - most open source projects opt for the MIT License.

Sources please? https://github.com/dfinity/ic/pulse talks of only ~100 commits (IC only, not including the other repos)

https://github.com/dfinity/ic/graphs/contributors You can see there are many contributors, whose own GitHub profiles show contributions to OTHER projects. For example, just clicking on one contributor, John Wiegley (Principal Engineer at DFINITY), you will see a long history of open source contributions: https://github.com/jwiegley

You can see the code here: https://github.com/dfinity/ic

Ubuntu/Debian: Install LND: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#install-lnd Install Bitcoin Core: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md#linux-instructions

To be able to follow along, you must have both bitcoind and lnd installed.

As mentioned previously, ScriptPubKeys are scripts that embody the locking conditions of bitcoins in a Bitcoin transaction. They are a crucial element of a Bitcoin transaction that specifies the requirements that must be met before an unspent transaction output (UTXO) is used. The ScriptPubKey, combined with the Amount, creates an output of a Bitcoin transaction. Like every other script, ScriptPubKeys are made up of operators and data. During the encoding of a transaction, both data and the operands are represented in hexadecimal format. You can find the hex representation for all operands used in Bitcoin Scripts here.

Which article? Have a look at Luke's CVE and pull request https://nvd.nist.gov/vuln/detail/CVE-2023-50428 https://github.com/bitcoin/bitcoin/pull/28408

From github pull request discussion: https://github.com/bitcoin/bitcoin/pull/28408

See: https://github.com/bitcoin/bitcoin/issues/10494