Tags: Manny27nyc/namecoin-core
Tags
Namecoin Core 0.21.0.1 This release is identical to the major 0.21.0 release in the main codebase, but includes some fixes to build scripts that allow it to work properly with Gitian.
Namecoin Core 0.21.0 This is a new major release of Namecoin Core. It is based on the upstream release of [Bitcoin Core 0.21.0](https://github.com/bitcoin/bitcoin/releases/tag/v0.21.0). It contains some user-visible, Namecoin-specific changes to the RPC interface. In particular: - [namecoin#194](namecoin#194): name_show now errors by default for expired names instead of returning them. - [namecoin#329](namecoin#329): An optional new index can be created, which allows looking up names by hash. - [namecoin#362](namecoin#362): The new RPC method namepsbt can be used to construct PSBTs with name operations.
Namecoin Core 0.19.0.1 This is a bug-fix release for Namecoin Core 0.19, which includes in particular the upstream fix for an uninitialised variable read from Bitcoin Core 0.19.0.1.
Namecoin Core 0.19.0 This is a new major release of Namecoin Core. It contains all of the updates done in upstream [Bitcoin Core 0.19.0](https://github.com/bitcoin/bitcoin/releases/tag/v0.19.0), minor improvements to the Namecoin code, and the following Namecoin-specific user visible change: The mempool now allows multiple updates of a single name (in a chain of transactions). This is something that is allowed in blocks already, i.e. it is just a policy change. The `name_update` RPC command still prevents such transactions from being created for now, until miners and relaying nodes have updated sufficiently. More details can be found in [namecoin#322](namecoin#322).
Namecoin Core 0.18.0 This release is mostly based on Bitcon Core 0.18.0, which a few Namecoin specific changes: - BIP16, CSV and Segwit will be activated at block height 475,000 on mainnet and 232,000 on testnet. See [namecoin#239](namecoin#239) for a discussion. - The `options` argument for `name_new`, `name_firstupdate` and `name_update` can now be used to specify per-RPC encodings for names and values by setting the `nameEncoding` and `valueEncoding` fields, respectively. - `name_scan` now accepts an optional `options` argument, which can be used to specify filtering conditions (based on number of confirmations, prefix and regexp matches of a name). See [namecoin#237](namecoin#237) for more details. - `name_filter` has been removed. Instead, `name_scan` with the newly added filtering options can be used. - `ismine` is no longer added to RPC results if no wallet is associated to an RPC call.
PreviousNext