Search results

Jump to: navigation, search
  • Also, very likely, what he will find are mostly technical specifications - not the best introduction to bitcoin.
    7 KB (963 words) - 18:43, 25 April 2024
  • [[Category:Technical]][[Category:Developer]]
    172 bytes (22 words) - 16:49, 17 February 2012
  • [[Category:Technical]][[Category:Developer]]
    371 bytes (50 words) - 04:31, 15 February 2012
  • Any of the components listed above (e.g. launch schedule, specific technical details) can be skipped from the initial RFC, if the authors wish to hasten
    7 KB (1,117 words) - 04:20, 13 August 2014
  • [[Category:Technical]]
    436 bytes (64 words) - 12:57, 27 June 2020
  • [[Category:Technical]]
    373 bytes (58 words) - 10:05, 13 July 2020
  • === Technical stuff: How can probabilistic transactions be created? ===
    5 KB (924 words) - 06:09, 15 February 2018
  • [[Category:Technical]]
    12 KB (1,999 words) - 02:17, 12 April 2012
  • ...the malicious >50%, the labels "honest" and "malicious" ultimately have no technical meaning, and so just swapping the labels would, absurdly, give a second pro
    11 KB (1,772 words) - 02:51, 25 November 2012
  • Unfortunately engineering such systems is non-trivial and the technical difficulty places this solution out of reach for most traders right now. Th
    13 KB (2,081 words) - 20:37, 29 November 2018
  • ...the malicious >50%, the labels "honest" and "malicious" ultimately have no technical meaning, and so just swapping the labels would, absurdly, give a second pro
    13 KB (2,096 words) - 22:42, 6 May 2013
  • [[Category:Technical]]
    4 KB (605 words) - 19:43, 26 January 2016
  • [[Category:Technical]]
    11 KB (1,756 words) - 16:39, 8 April 2022
  • ...ffline and gives the message "We're currently unavailable right now due to technical issues"<ref>[http://bitcointalk.org/index.php?topic=78556.msg1324894#msg132
    873 bytes (112 words) - 04:07, 9 December 2012
  • [[Category:Technical]]
    7 KB (994 words) - 00:21, 20 July 2021
  • ...al explanation, see Satoshi's [http://www.bitcoin.org/bitcoin.pdf original technical paper]. [[Category:Technical]]
    44 KB (7,257 words) - 01:56, 10 June 2019
  • ...ound in Lightning Network literature that may not be familiar to a general technical audience, including both the new terms created by Lightning Network designe ...d for scenarios where payments can't conveniently be made small enough for technical reasons (such as not being able to pay less than 1 satoshi) or economic rea
    23 KB (3,540 words) - 00:24, 13 July 2022
  • == Technical details ==
    2 KB (257 words) - 03:17, 31 August 2012
  • ==Technical specifications== The standard was split into two pieces and the technical specification can be found in [[BIP 0022|BIP 22]] and [[BIP 0023|BIP 23]].
    15 KB (2,134 words) - 02:01, 26 March 2019
  • ...it ''does'' have a parent. Indeed, in the Bitcoin source code and in more technical discussions, orphan blocks and stale blocks are two separate things: both a
    1 KB (177 words) - 15:34, 16 May 2019
  • [[Category:Technical]]
    1 KB (144 words) - 12:06, 10 February 2015
  • ...s I just mean sending them to an address which is unspendable. The precise technical details of this will vary from cryptocurrency to cryptocurrency. With Bitco === Technical sketch of proof of burn: "Burnt coins are mining rigs!" ===
    32 KB (5,261 words) - 12:10, 15 January 2018
  • *[[:Category:Technical|Category:Technical]]
    11 KB (1,510 words) - 10:59, 14 June 2013
  • [[Category:Technical]]
    692 bytes (99 words) - 04:12, 8 June 2014
  • ...itcoin through the means of continuous polling. The idea is to provide the technical means required for tapping into the power of crowd-sourcing.
    870 bytes (131 words) - 09:10, 26 September 2022
  • ...site insecure & badly designed with no substantial info. Consider finding technical docs, real reviews or removing this device. --> ...-1 E-shop] | [https://ledgerhq.github.io/btchip-doc/bitcoin-technical.html Technical Documentation]
    36 KB (5,332 words) - 08:43, 10 December 2023
  • [[Category:Technical]]
    4 KB (613 words) - 11:15, 5 October 2018
  • BIPS was a Payment Service Provider (PSP) specializing in the technical aspects of accepting cryptocurrencies - such as bitcoin.
    3 KB (493 words) - 09:11, 26 September 2022
  • ...he platform is full of in-depth charts which can be customized by multiple technical indicators and time frame option. * Multiple technical indicators
    2 KB (238 words) - 10:46, 28 June 2016
  • [[Category:Technical]]
    10 KB (1,569 words) - 10:32, 23 June 2020
  • [[Category:Technical]]
    8 KB (1,335 words) - 09:30, 18 February 2022
  • ...h as [[MyBitcoin]] and [[Instawallet]] have failed due to hacks as well as technical mistakes resulting in the loss of some or all funds held on behalf of their [[Category:Technical]]
    9 KB (1,427 words) - 05:17, 21 March 2021
  • [[Category:Technical]]
    2 KB (320 words) - 07:15, 17 February 2022
  • • Indicators/strategies for technical analysis, or any studies that are displayed on the chart
    6 KB (902 words) - 08:30, 3 July 2013
  • .... The company said it was pausing withdrawal requests “to obtain a clear technical view of the currency processes”.<ref name=doughterty2014/> Mt. Gox would ...<ref name=titan /> inciting a search for the missing money. Karpelès said technical issues opened up the way for fraudulent withdrawals. Mt. Gox also faces law
    16 KB (2,159 words) - 03:54, 1 August 2015
  • ...ns you may have, just like you would with other valuables. If you lack the technical expertise, ask or pay somebody else to do it for you.
    2 KB (332 words) - 19:19, 2 December 2013
  • * Easy to use service capable of providing maximum security for non-technical users.
    1 KB (183 words) - 10:30, 26 January 2014
  • === Technical Information ===
    8 KB (1,166 words) - 01:14, 18 March 2015
  • ...n newbies and the technological aspect of Bitcoin through the use of a non technical blog and simple tutorials explained in laymen terms. 99 Bitcoins also opera
    2 KB (375 words) - 22:34, 20 March 2014
  • ...es. All of the plans imply daily payouts, low power cost, and professional technical support. The users signs a two-year contract that can be renewed after it e
    3 KB (456 words) - 09:01, 22 April 2014
  • The site discusses both the technical as well as the social aspects of mining Bitcoin.<br>
    902 bytes (145 words) - 21:17, 1 April 2014
  • ...and the network. It is not a first-tier technical support channel, general technical support questions can be asked in [http://webchat.freenode.net/?channels=bi
    1 KB (169 words) - 20:46, 17 April 2015
  • [[Category:Technical]]
    1 KB (225 words) - 18:43, 19 June 2014
  • ...ng the development of BitLendingClub. Yasen manages all the aspects of the technical implementation of the platform and serves as the CTO of BitLendingClub.
    3 KB (380 words) - 12:23, 23 May 2014
  • ...on location and their local currency. Asmoney make Bitcoin easier for non-technical users to send and receive payments.
    2 KB (298 words) - 23:57, 11 July 2022
  • ...rs/2012_fc.pdf extended abstract] and [http://eprint.iacr.org/2011/677.pdf technical report]).
    1 KB (136 words) - 12:51, 12 June 2014
  • == Technical details ==
    16 KB (2,158 words) - 02:31, 21 July 2015
  • ...ade, the receiving party has no reason to retain the data for the address (technical details simplified) and may discard it.
    9 KB (1,522 words) - 22:41, 11 April 2021
  • ...y Lake Investments Limited (BVI), with Shanghai Trading IT, Inc. providing technical and customer support.
    3 KB (354 words) - 07:58, 10 November 2014
  • This page lists numerous things mining manufacturers should think about on a technical level before releasing a product to ensure it will work best with Bitcoin.
    9 KB (1,435 words) - 00:26, 6 June 2018
  • ...n-cloud-mining-contract-reviews/ Bitcoin cloud mining contracts] with live technical Support, no hidden fees, and instant mining contract delivery. Bitcoin clou
    810 bytes (107 words) - 04:10, 19 May 2016
  • Jed currently leads technical development of Stellar. He writes about the technical elements of the Stellar network on the Stellar.org blog (ex: [https://www.s
    2 KB (204 words) - 13:59, 6 June 2020
  • ...pen orders, along with a number of powerful charting tools that allow both technical analysis and one-click trading.<ref>http://www.coindesk.com/lakebtc-exchang
    2 KB (291 words) - 09:17, 12 September 2014
  • Behind Bitok.com there is a young and efficient team of technical professionals, who possess extensive knowledge and experience in IT project
    3 KB (449 words) - 13:20, 28 July 2020
  • ...dedicated supercomputing platform that features four Tesla units (GT200). Technical data taken from [http://www.nvidia.de/object/tesla_s1070_de.html NVIDIA]</r ...dedicated supercomputing platform that features four Fermi units (C2070). Technical data taken from [http://de.wikipedia.org/wiki/Nvidia_Tesla Wikipedia] (Docu
    131 KB (14,245 words) - 23:09, 13 February 2023
  • [[Category:Technical]]
    12 KB (1,826 words) - 16:16, 8 April 2022
  • [[Category:Technical]]
    2 KB (399 words) - 07:18, 26 July 2018
  • ...on-qualcomm-ventures-key-investor/</ref>,date/specs<ref>https://21.co/faq/#technical-specifications</ref> ...s time seem unrealistic. BitcoinTalk user vs3 holds a large collection of technical information about this chip in his NanoFury repository<ref>https://github.c
    100 KB (13,759 words) - 12:54, 22 January 2018
  • [[Category:Technical]]
    733 bytes (113 words) - 16:36, 8 July 2015
  • ...itcoin currently works (related to scaling) as well as questions about the technical terminology related to the scaling discussion.
    44 KB (6,696 words) - 00:36, 16 July 2021
  • [[Category:Technical]]
    9 KB (1,374 words) - 08:42, 15 May 2024
  • * Gross technical incompetence. <ref>http://archive.is/6C3C9</ref><ref>https://np.reddit.com/ Wright sometimes explains away his apparent technical incompetence by suggesting that the actual development of Bitcoin was perfo
    4 KB (557 words) - 18:01, 27 April 2019
  • [[Category:Technical]]
    15 KB (2,318 words) - 00:41, 24 April 2019
  • [[Category:Technical]]
    17 KB (2,685 words) - 16:01, 4 September 2018
  • [[Category:Technical]]
    17 KB (2,744 words) - 20:32, 21 January 2016
  • [[Category:Technical]]
    13 KB (2,125 words) - 20:27, 21 January 2016
  • ...n newbies and the technological aspect of Bitcoin through the use of a non technical blog and simple tutorials explained in laymen terms. The website showcases
    2 KB (322 words) - 13:04, 10 February 2016
  • ...Bitcoin or its processes or environment. The BIP should provide a concise technical specification of the feature and a rationale for the feature. ...d the BIP to check if it is ready: sound and complete. The ideas must make technical sense, even if they don't seem likely to be accepted.
    34 KB (5,496 words) - 20:07, 24 April 2024
  • [[Category:Technical]]
    2 KB (284 words) - 22:06, 15 January 2018
  • [[Category:Technical]]
    6 KB (924 words) - 16:54, 8 April 2022
  • [[Category:Technical]]
    4 KB (666 words) - 20:09, 17 September 2017
  • [[Category:Technical]]
    10 KB (1,629 words) - 18:35, 28 January 2020
  • ...with a first-class network, together with a highly skilled engineering and technical support team.
    8 KB (1,021 words) - 20:36, 2 June 2020
  • ...ould probably not be said to have consensus. This is commonly the way that technical decisions are made in open source projects, including many Bitcoin open sou
    3 KB (452 words) - 10:33, 28 May 2016
  • ...ide you through the buying/selling process and ready to answer any of your technical questions regarding to bitcoin. The team also offers support by skype (btcd
    3 KB (352 words) - 00:33, 24 April 2019
  • ...actswiki are in multiple cases wrong and the information thereon regarding technical information about Bitcoin appears to be politically-motivated and -edited. ...ckTime presents to the hard-forking narrative, it is being downplayed as a technical objection and stated to be a deprecated function even though it has been an
    2 KB (293 words) - 01:23, 2 July 2018
  • [[Category:Technical]]
    3 KB (404 words) - 07:30, 4 October 2021
  • On a technical level, the consensus rules of bitcoin are controlled by the [[economic majo
    3 KB (420 words) - 06:16, 14 March 2021
  • Technical note: More precisely, it's the ''outputs'' of a transaction which create th [[Category:Technical]]
    4 KB (630 words) - 17:49, 3 July 2017
  • [[Category:Technical]]
    2 KB (320 words) - 03:36, 25 May 2017
  • ==Technical details== [[Category:Technical]]
    2 KB (444 words) - 09:52, 15 September 2021
  • ...echnical issue, and the amount of hashrate or number of nodes or any other technical parameter are almost completely meaningless. [[Category:Technical]] [[Category:Mining]]
    9 KB (1,491 words) - 22:53, 15 May 2021
  • ...its own standard, and for good reasons. BIP39 has some flaws, known in the technical community but not known much wider. They are described [https://electrum.re [[Category:Technical]]
    12 KB (1,921 words) - 17:28, 27 July 2023
  • [[Category:Technical]]
    11 KB (1,622 words) - 02:39, 2 March 2021
  • [[Category:Technical]]
    5 KB (748 words) - 04:25, 14 April 2018
  • See https://en.wikipedia.org/wiki/Trusted_Platform_Module for technical details.
    344 bytes (54 words) - 20:52, 29 November 2018
  • ...on via XML file. This not only serves for the general configuration of the technical basis but is also used to configure the interfaces in order to be able to a
    3 KB (446 words) - 18:59, 19 October 2018
  • ...ons associated with new currencies. Since sidechains are separate systems, technical and economic innovation is not hindered. Despite bidirectional transferabi [[Category:Technical]]
    3 KB (462 words) - 16:56, 8 April 2022
  • * [https://joinmarket.me/blog/blog/coinswaps/ Technical explanation], July 2017
    4 KB (572 words) - 19:41, 23 March 2022
  • [[Category:Technical]]
    9 KB (1,451 words) - 15:03, 28 February 2024
  • ...only one layer of tail-call recursion is admittedly limiting, however the technical challenges to supporting multi-layer tail-call recursion are significant.
    15 KB (2,286 words) - 17:59, 24 September 2019
  • technical debt.
    12 KB (1,921 words) - 17:03, 21 August 2020
  • ...deployments. This simplification of the consensus rules would reduce the technical debt associated with deployment of those consensus changes.
    6 KB (879 words) - 07:58, 2 August 2020
  • SIGHASH_ANYPREVOUTANYSCRIPT bears additional technical and implementation risks
    36 KB (5,382 words) - 18:43, 23 April 2024
  • Such error codes or messages could be used maliciously to phish a non technical user.
    40 KB (5,341 words) - 21:40, 30 April 2024
  • [[Category:Technical]]
    2 KB (306 words) - 18:29, 16 June 2021
  • ...dressed separately (if desired), and this proposal aims to provide a solid technical basis for future protocol upgrades, including the addition of optional auth Besides this fundamentally different treatment of authentication, further technical issues arise when applying TLS or Noise to our desired use case:
    65 KB (9,770 words) - 08:04, 29 September 2023
  • ...ret sharing, has no support for versioning or other metadata, and has many technical design decisions that make implementation and interoperability difficult (f
    38 KB (5,537 words) - 05:05, 30 March 2023
  • ...ng for readers familiar with the MuSig2 paper. However, serialization is a technical detail that is irrelevant for users of MuSig2 interfaces.</ref>
    68 KB (10,863 words) - 09:27, 14 May 2024
  • * You get eliable crypto partner, competent technical support, referral fees and your happy clients.
    5 KB (714 words) - 07:00, 6 March 2024

View (previous 100 | next 100) (20 | 50 | 100 | 250 | 500)