![]() generated - true if the spent coins was a coinbase.Every vin field will contain an additional prevout subfield describing the spent output. ![]() The existing /rest/block/ REST endpoint is modified to contain this information too. The getblock RPC command now supports verbosity level 3 containing transaction inputs’ prevout information.RPCs gettxout, getrawtransaction, decoderawtransaction, decodescript, gettransaction verbose=true and REST endpoints /rest/tx, /rest/getutxos, /rest/block no longer return the addresses and reqSigs fields, which were previously deprecated in 22.0. The -deprecatedrpc=addresses configuration option has been removed.The error message returned in the error field now also returns more specific errors when decoding fails. Success and correctness are only guaranteed if fewer than two substitution errors have been made. For example, this will attempt to locate up to two Bech32 errors, and return their locations if successful. The validateaddress RPC now returns an error_locations array for invalid addresses, with the indices of invalid character locations in the address (if known).Information about the existing tracepoints can be found under doc/tracing.md and usage examples are provided in contrib/tracing/. While the API is tested, process internals might change between releases requiring changes to the tracepoints. These can be used for review, debugging, monitoring, and more. Bitcoin Core release binaries for Linux now include experimental tracepoints which act as an interface for process-internal events.Tracepoints and Userspace, Statically Defined Tracing support: Otherwise, please use the rescanblockchain RPC to trigger a rescan. Wallets which require rescanning due to corruption will still be rescanned on startup. The -rescan startup parameter has been removed.Fee estimation now takes the feerate of replacement (RBF) transactions into account.See the new option -cjdnsreachable and doc/cjdns.md Full support has been added for the CJDNS network.As a result of that, Bitcoin nodes listening on non-standard ports would likely not get any Bitcoin Core peers connecting to them. Before this release, Bitcoin Core had a strong preference to try to connect only to peers that listen on port 8333.They will become eligible for address gossip after sending an ADDR, ADDRV2, or GETADDR message. A bitcoind node will no longer rumour addresses to inbound peers by default.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |