Search results
Create the page "Protocol specification)" on this wiki! See also the search results found.
- A Bitcoin ASIC's specification could be seen as having a certain [[hash per second|hash rate]] (e.g. Gh/s) ...expensive than for another ASIC. If the ASIC has a complex communications protocol, additional relatively expensive components may be required. If an ASIC's8 KB (1,229 words) - 00:26, 24 April 2019
- The specification defines the layers and sets forth specific criteria for deciding to which l ==Specification==16 KB (1,847 words) - 18:00, 24 September 2019
- ==Specification== # Feature discovery is enabled by checking protocol version >= 700123 KB (429 words) - 18:00, 24 September 2019
- == Specification == ..., since sequence number of ffffffff would make lock_time ineffective. This specification demands that all input sequence numbers are 0, not just one of them, which9 KB (1,453 words) - 17:59, 24 September 2019
- explicitly. It also bumps the protocol version to allow peers to == Specification ==3 KB (518 words) - 18:00, 24 September 2019
- ==Specification== This is a hard-forking change to the Bitcoin protocol; anybody running code that fully validates blocks must upgrade before the a5 KB (736 words) - 07:39, 2 August 2020
- A method of altering the maximum allowed block size of the Bitcoin protocol limit is required at protocol level. This feature ensures full nodes retain4 KB (681 words) - 07:37, 2 August 2020
- ==Specification== In the event that future protocol upgrades introduce new signature hash types, compliant software should appl12 KB (1,826 words) - 16:03, 15 December 2021
- ==Specification== ...ctivation is achieved, the maximum block size shall be as described in the specification section, regardless of the version number of the block.10 KB (1,479 words) - 17:59, 24 September 2019
- ==== Using USB-DFU Protocol ==== | 2 || bcdUSB || 2 || 0100h || USB specification release number in binary coded decimal.22 KB (3,104 words) - 07:59, 15 August 2016
- ...ation: [https://github.com/chromaway/ngcccbase/wiki/EPOBC_simple The EPOBC protocol] which allows you to store assets on the [[http://chromawallet.com|Bitcoin ...nting the [https://github.com/chromaway/ngcccbase/wiki/EPOBC_simple EPOBC] protocol.2 KB (278 words) - 14:53, 2 November 2015
- ...r its processes or environment. The BIP should provide a concise technical specification of the feature and a rationale for the feature. ...d implementation, if applicable, must be solid and must not complicate the protocol unduly.34 KB (5,496 words) - 20:07, 24 April 2024
- * (15 Feb 2021) Finalize specification ...e payment codes, however future developments of the reusable payment codes specification will not be distributed via the BIP process.22 KB (3,425 words) - 18:29, 24 April 2024
- Title: Allow zero value OP_RETURN in Payment Protocol This BIP alters the Payment Protocol to allow for zero value OP_RETURN outputs in serialized PaymentRequests.6 KB (975 words) - 17:59, 24 September 2019
- ...n libsecp256k1 after #REPLACE_libsecp256k1_PR), it is still not a complete specification of the consensus rules. Since libconsensus doesn't manage the current state that there's many alternative implementations of the protocol (forks18 KB (2,863 words) - 21:58, 30 April 2024
- ==Specification== ...posal]], as a safe runway prior to switching to Phase 2, while network and protocol infrastructure is improved6 KB (909 words) - 07:50, 2 August 2020
- == Specification == The use of normalized transaction IDs is introduced as a softfork. The specification is divided into three parts:15 KB (2,249 words) - 07:56, 2 August 2020
- ...' by moving part of the transaction data to a structure unknown to current protocol, for example: ==Specification==26 KB (3,935 words) - 23:08, 26 April 2024
- == Specification == *BIP70 Payment protocol6 KB (918 words) - 17:58, 24 September 2019
- ==Specification== A new serialization format for tx messages is added to the peer-to-peer protocol.5 KB (805 words) - 18:00, 24 September 2019
