nyuuzyou/wikis huggingface dataset:
Preev

Preev is a site that allows anyone to see the current Bitcoin exchange rate and convert any amount to or from a wide choice of crypto- and fiat currencies.
400px|frameless|right
== Price source ==
Price data is constantly updated from multiple exchanges. The default price shown is a weighted average rate of these exchanges. A specific source can be alternatively chosen from settings menu.
== Features ==
400px|frameless|right
* One can keep track of current exchange rate even while working in other browser tabs just by keeping this site open and looking at the rate in its tab.
* It is possible to compare Bitcoin to gold, silver, platinum and palladium by using their respective converters.
* 64 currently (as of April 2014) supported currencies with possibility of bookmarking your favorite ones.
* The site is optimized for use on phones and tablets.
== Development ==
Preev is developed and maintained by fennec
== See also ==
* Exchanges
== References ==
Preev.com
Press.bitcoin.org

This page shall serve as a meeting point for volunteers of the Bitcoin.org Press Center project.
== Project Goal: ==
Create and maintain a web resource for members of the press to find information about Bitcoin.
== Resources: ==
* Project Roadmap
== Volunteer Contact List ==
* Joerg Platzer
* Saivann Carignan
* Mike Hearn
* Stefan Thomas
* ak-ka@gmx.net
* David Barnes
Price controls

Price controls are governmental restrictions on the prices that can be charged for goods and services in a market. The most common are prohibitions to charge more than X for goods or services (maximum price) or the prohibition on paying less than Y (minimum price). A less common restriction is to impose an exact price for a certain good, making it illegal to charge more or less than the official rate.
Price controls are an example of central planning or authoritarian control of the economy.
==Examples==
Common examples of price controls include minimum wage laws, fixed exchange rates, centrally mandated interest rates, etc.
==History==
Price controls have been documented since the Code of Hammurabi in 1754 BC. Roman Emperor Diocletian also issued an Edict on Maximum Prices in 301 AD. The Law of the Maximum passed in France in 1793 AD during the French Revolution is also a well known example.
==Criticism==
Price controls subvert the market price discovery mechanism and thus impede the free interplay of the forces of supply and demand. Criticisms are generally divided into ethical and utilitarian arguments:
*Utilitarian arguments focus on the effects that price controls have on the economy. By distorting supply and demand maximum prices (if set below the market rate) will cause shortages of the good in question. Minimum prices (if set above the market rate) tend to create a surplus of the good affected. Because Price controls can restrict exchanges which would have happened in a voluntary market, a priori benefiting both parties to the exchange, they destroy value and reduce economic growth.
*Ethical criticism of Price controls focus on the fact that they are an attack on property rights and free markets. They are an imposition of the planners will on those of market participants and restrict voluntary trade. Enforcing price controls also requires a substantial attack on privacy and an increase of surveillance.
Prime

Commercially licensed high-end bitcoin exchange software.
==Advantages==
Prime claims to be developed with software craftsmanship in mind. It strives for correctness, security, simplicity and source code beauty. No rush and careful engineering are considered more important than rich feature set and "time-to-market".
==Estimated Time of Arrival==
Prime is expected to be ready for purchase by the end of 2014.
==API==
Prime API is a work in progress.
==Specification==
Prime specification draft is a work in progress.
==History==
Development started on April 17, 2013.
==See Also==
* Buying bitcoins
* Selling bitcoins
==External Links==
==References==
Category:Exchange software
Category:EWallets
Prime API

==Introduction==
Prime API is based on JSON, delivered through HTTPS and is mostly REST-ful.
API URIs always start with a marker "/v1" to make the version explicit.
All timestamps are returned in ISO 8601 format:
 YYYY-MM-DDTHH:MM:SSZ
==Public API==
Public API calls are available without authentication.
==Private API==
Private API calls require authentication via:
* Your personal API key and optionally
* IP address
Private API is off by default. You need to enable it in your profile.
You are expected to pass the API key as a HTTP header:
 Authorization: PrimeExchange 84ffsOscok1Asbbqj28gcscv86M3nj4bRIamFaKe
...where the long string is of course your API key.
It is also possible to pass the API key as a request param:
 ?api_key=84ffsOscok1Asbbqj28gcscv86M3nj4bRIamFaKe
...although this is not recommended as sensitive data should not be passed in the URI.
===Get my deposit address===
 GET /v1/prv/deposit_address/:currency_name.json
* currency_name - obligatory cryptocurrency name, i.e BTC, LTC
Example:
curl -v --request GET http://localhost:3000/v1/prv/deposit_address/BTC.json --header "Authorization: PrimeExchange 84ffsOscok1Asbbqj28gcscv86M3nj4bRIamFaKe"
Response:
 200 OK
 {"address":"n2Ccn5em9gcQyBe2QvZnfzzXq8EZh1ncJj"}
Error response:
 422 Unprocessable Entity
 {"errors":{"currency_name":"is invalid"}}
===Get balances and user data===
 GET /v1/prv/user.json
Example:
curl -i --request GET http://localhost:3000/v1/prv/user.json --header "Authorization: PrimeExchange 84ffsOscok1Asbbqj28gcscv86M3nj4bRIamFaKe"
Response:
 200 OK
{
 "user": {
 "username": "adalovelace",
 "email": "adalovelace@bitcoinfoundation.org",
 "balances": [
 {
 "available": "0.199",
 "total": "0.199",
 "currency_name": "BTC"
 },
 {
 "available": "0.0",
 "total": "0.0",
 "currency_name": "PLN"
 },
 {
 "available": "7.11",
 "total": "7.11",
 "currency_name": "LTC"
 }
 ]
 }
}
* available - the amount you can manage, i.e. to place a new offer
* total - the amount including funds reserved for offers, withdrawals, etc.
===Create a withdrawal request (of cryptocurrency)===
 POST /v1/prv/withdrawal_request.json
* currency_name - obligatory name of the currency like BTC, LTC, PLN
* address - obligatory only for cryptocurrencies
* amount - obligatory
* otp - obligatory when user has set up a Google Authenticator One-Time-Passwords for withdrawals
Example:
curl -i --request POST http://localhost:3000/v1/prv/withdrawal_requests.json --header "Authorization: PrimeExchange 84ffsOscok1Asbbqj28gcscv86M3nj4bRM6sLRdM" \
--data "currency_name=BTC&address=mm2SjeJ64vQokDjnkhvhcv9mGk1VfEJRsk&amount=0.03"
Response:
 201 Created
Error response (missing or invalid OTP):
 401 Unauthorized
{
 "errors": {
 "otp": "is invalid"
 }
}
Error response (invalid params):
 422 Unprocessable Entity
{
 "errors": {
 "currency_name": "is invalid",
 "address": "is_invalid",
 "amount": "is invalid"
 }
}
==References==
Profitability Calculator

Aids in estimating mining profits at current network and market conditions. 
The current difficulty is obtained from Bitcoin Block Explorer.
== See also ==
* Generation Calculator
* Power Calc
==External Links==
* BTCServ - Bitcoin Mining Calculator
* Bitcoin Mining Profitability Calculator - MinerGate
* Bitcoin Profit Calculator - CEX.IO
* Coinish Mining Calculator
* TP's Bitcoin Calculator(useful for pool mining)
* Mining Break Even Calculator (also useful for pool mining)
* Easy BitCoin Mining Calculator (also useful for pool mining)
* Online Bitcoin Profitability Mining Calculator (Russian)
* Blockchained.com Bitcoin Mining Profitability Calculator - (with decline factor)
* Detailed Cloud Mining Profitability Calculator
* Vnbitcoin.org Bitcoin Mining Calculator
Category:Mining
Category:Calculators
Prohibited changes

These changes are considered to be against the spirit of Bitcoin. Even if all Bitcoin users decide to adopt any of these changes, the resulting cryptocurrency can no longer be considered "Bitcoin" because it has diverged too much from the original design.
=== Require unanimous consent ===
These changes require the consent of every bitcoin-holder:
* Increasing the total number of issued bitcoins beyond 21 million. Precision may be increased, but proportions must be unchanged.
* Any rule that adds required, explicit centralization. For example, a change requiring that all blocks be signed by some central organization.
* Demurrage (deletion or reassignment of coins judged to be "lost" or "unused"). This is highly controversial in the context of currency units; on the other hand it is absolutely essential for namespace entries like Namecoin (which implements Demurrage for namespace entries but not for currency units).
=== Require miner consensus ===
* Changing the bitcoin distribution algorithm such that the subsidy at any given time period is decreased without miner consensus and 3 years notice, or increased beyond improved precision of halving (lossy beginning with block 1,890,000).
=== Fundamental Principles===
All changes and upgrades to the protocol should strive to maintain and reinforce these Principles of Bitcoin
* 21 million coins. 
* No censorship: Nobody should be able to prevent valid txs from being confirmed.
* Open-Source: Bitcoin source code should always be open for anyone to read, modify, copy, share.
* Permissionless: No arbitrary gatekeepers should ever prevent anybody from being part of the network (user, node, miner, etc).
* Pseudonymous: No ID should be required to own, use Bitcoin. 
* Fungible: All coins are equal and should be equally spendable.
* Irreversible Transactions: Confirmed blocks should be set in stone. Blockchain History should be immutable.
=== Disputed ===
* Adding alternatives to Proof of Work such as Proof of Stake. This could change core bitcoin too much, but with widespread agreement of some sort might be possible.
== See Also ==
Hardfork Wishlist for hard forks that might happen and still be called "Bitcoin".
Promotional graphics

Bitcoin-related graphics used for promoting bitcoin either for online use, retail display or other promotional purpose. For graphics in languages other than English, see Promotional graphics (non-English).
==Orange style==
This logo and most of the images in this section were created by bitboy using the symbol designed by Satoshi. They are in the public domain.
===Logo alone===
:BC Logo .png‎
SVG and higher resolutions
===Logo with text===
:BC Logotype.png‎
http://media.tumblr.com/tumblr_lmupioyU7M1qznjpp.png
===Sticker with QR code===
The below PNG image is a low quality (= non-vector) render of the source vector image because the Wiki cannot display SVG files at the moment.
For real usage, especially printing, please use the source SVG image
==="We love Bitcoin" Graphics===
===Bitcoin Accepted Here Buttons===
====Normal size====
:BC_Rnd_64px.png‎
:BC 64px.png‎
:BC nBG 64px.png‎
:BC RnBG 64px.png‎
====High resolution====
==Euro style==
==Gold style==
This logo/image was created by Satoshi Nakamoto, who placed it in the public domain.
==Ƀ: Another Bitcoin Identity==
* 
* 
* 
* 
Ƀ graphic elements are available in SVG format on the dedicated project page.
==New Bitcoin Accepted Here sign for business owners==
* 
* 
Graphic elements are available in Vector .
==External Links==
* New icon/logo (SVG of the gold bitcoin / logo)
* Bigger "B" versions of Bitcoin logotypes
* Ƀ Another Bitcoin identity
* More Bitcoin logos, buttons, and also some other graphics
* Make your "we accept Bitcoin" logo
* A4 Printable "Bitcoin Accepted Here" Sign Generator PDF or PNG
* Liberty starts with free money logo
* In cryptography we trust (yet another Bitcoin icon)
* Bitcoin icons from Bitbash
* Bitcoin Graphics zip
* What is Bitcoin? (Infographic) 
* carbonism's deviantART gallery
* Handsome Code Better Bitcoin
* Stack of bitcoins
* Bitcoin Graphics in Vector Format (Illustrator)
* Bitcoin Clipart Royalty free
* Dollars Not Accepted (Scaleable Vector Graphic & PDF) Public Domain (CC0)
==See Also==
* Bitcoin symbol
Category:Marketing
Proof-of-work combination algorithms

Hashes have been known to be combined in the following order (Combo11-Combo15):
* BLAKE-256
* Blue Midnight Wish
* Grøstl
* JH
* SHA-3 (Keccak)
* Skein
* Luffa
* CubeHash
* SHAvite-3
* SMD
* ECHO
* Hamsi (Combo13+)
* Fugue (Combo13+)
* Shabal (Combo14+)
* Whirlpool (Combo15)
Proof of Ownership

Proof of Ownership is a method that uses Bitcoin's decentralized ledger (also called blockchain) or Bitcoin-related technologies to track the different owners of a certain information over the time.
This technique can be used by artists or businesses to certify the integrity, date of publication and ownership of their creations or contracts.
== Technology ==
=== Using the Bitcoin blockchain ===
The Bitcoin Core protocol now accepts raw data transactions up to 40 bytes per output using the opcode OP_RETURN.
Putting the hash of the signature of a file's hash in the blockchain makes the owner of the private key associated with the signature the owner of the file in the blockchain (as long as someone else doesn't show up with a proof certified before).
=== Using a new blockchain ===
It's also possible to create a new blockchain for this purpose. This blockchain wouldn't only store coins but also notarized proofs. 
== Content of a proof ==
=== Ownership ===
Only the people with the private key associated with the signature can prove they are the owner.
=== Existence ===
A Proof of Ownership is always attached to a piece of data. Certifying the ownership of a certain information in the blockchain also proves that this information existed at a certain time.
=== Integrity ===
A Proof of Ownership is always attached to a piece of data using cryptographic functions. This makes it impossible to alter the data after certification. If the content is modified, even by a single bit, then the whole certificate becomes invalid.
=== Authenticity ===
Because proofs are logged in the blockchain, it makes it easy to make transfers of ownership and find the original issuer of a certificate. Certificates can’t be “double-spent”.
== Usages ==
* crypto-copyright.com - Decentralized Proof of Ownership using Bitcoin's blockchain
* bitproof.io - Certify your files and ideas for free in the Bitcoin blockchain
* coinsecrets.org - list of metadata recently embedded in the bitcoin blockchain using OP_RETURN outputs.
* github.com Creating OP_RETURN transactions in the blockchain
Category:Proof-of-x
Proof of Publication

A method that uses Bitcoin or Bitcoin-like technologies to authenticate that a certain information was published at a certain date, or was known at a certain date.
The technique entails encoding the secure hash of a certain publication (plaintext) inside the Bitcoin blockchain. It was probablly first described in the paper from 2012 titled "CommitCoin: Carbon Dating Commitments with Bitcoin" (extended abstract and technical report).
== References ==
* proofofexistence.com - Store hashes of data in the blockchain.
* coinsecrets.org - list of metadata recently embedded in the bitcoin blockchain using OP_RETURN outputs.
* Encoding Master Protocol transactions
* OP_RETURN in the Master Protocol
Category:Proof-of-x
Proof of keys day

January 3rd is Proof of keys day.
Every year on January 3rd bitcoiners are encouraged to move their bitcoins to wallets under their full control. By withdrawing from exchanges and other custodians, fractional reserve, "paper bitcoin", ponzis and other frauds are exposed. This makes Bitcoin stronger by removing weak and dishonest players from the market.
Proof of keys day celebrates Bitcoin as a store of value.
Proof of keys day is based on the "Not your keys, not your Bitcoin" and "Don't trust, verify." Bitcoin maxims.
*See also: List of failed exchanges
*See also: Bitcoin holidays
Proper Money Handling (JSON-RPC)

== Overview ==
The original bitcoin client stores all bitcoin values as 64-bit integers, with 1 BTC stored as 100,000,000 (one-hundred-million of the smallest possible bitcoin unit). Values are expressed as double-precision Numbers in the JSON API, with 1 BTC expressed as 1.00000000
If you are writing software that uses the JSON-RPC interface you need to be aware of possible floating-point conversion issues. You, or the JSON library you are using, should convert amounts to either a fixed-point Decimal representation (with 8 digits after the decimal point) or ideally a 64-bit integer representation. In either case, rounding values is required.
Improper value handling can lead to embarrassing errors; for example, if you truncate instead of doing proper rounding and your software will display the value "0.1 BTC" as "0.09999999 BTC" (or, worse, "0.09 BTC").
The original bitcoin client does proper, full-precision rounding for all values passed to it via the RPC interface. So, for example, if the value 0.1 is converted to the value "0.099999999999" by your JSON-RPC library, that value will be rounded to the nearest 0.00000001 bitcoin and will be treated as exactly 0.10 BTC.
The rest of this page gives sample code for various JSON libraries and programming languages.
== BASH ==
 function JSONtoAmount() {
 printf '%.8f' "$1" | tr -d '.'
 }
== C/C++ ==
C/C++ JSON libraries return the JavaScript Number type as type 'double'. To convert, without loss of precision, from a double to a 64-bit integer multiply by 100,000,000 and round to the nearest integer:
 int64_t JSONtoAmount(double value) {
 return (int64_t)(value * 1e8 + (value < 0.0 ? -.5 : .5));
 }
To convert to a JSON value divide by 100,000,000.0, and make sure your JSON implementation outputs doubles with 8 or more digits after the decimal point:
 double forJSON = (double)amount / 1e8;
== ECMAScript ==
 function JSONtoAmount(value) {
 return Math.round(1e8 * value);
 }
== Java ==
 public long JSONtoAmount(double value){
 return (long)(value*100000000L);
 }
== Perl ==
 sub JSONtoAmount {
 return sprintf '%.0f', 1e8 * shift;
 }
== Go ==
The btcjson package provides a more complete version of this function (error checking and so on), but for illustrative purposes, this is useful.
 func JSONToAmount(jsonAmount float64) (int64) {
 var amount int64
 tempVal := 1e8 * jsonAmount
 if tempVal < 0 {
 tempVal = tempVal - 0.5
 }
 if tempVal > 0 {
 tempVal = tempVal + 0.5
 }
 // Then just rely on the integer truncating
 amount = int64(tempVal)
 return amount
 }
== PHP ==
 function JSONtoAmount($value) {
 return round($value * 1e8);
 }
== Python ==
 def JSONtoAmount(value):
 return long(round(value * 1e8))
 def AmountToJSON(amount):
 return float(amount / 1e8)
== Common Lisp ==
 (defun json-to-amount (n)
 (coerce (round (* n 1e8)) 'integer))
CAUTION: The CL-JSON library parses numbers as single precision floating-point by
default. The default parsing behavior can be overridden as follows:
 (set-custom-vars :real (lambda (n)
 (json::parse-number (concatenate 'string n "d0"))))
Category:Technical
Category:Developer
de:Korrektes_Handling_von_Geldbeträgen_(JSON-RPC)
ProtoShares

ProtoShares is a coin created by the U.S company called Invictus Innovations.
Owners of PTS will get some stake (10%?) in any future crypto-currency that is launched by Invictus.
Invictus are planning various crypto-currencies that serve different purposes, e.g. BitShares for a CFD/financial market, Keyhotee for identitiy management, and more.
== Launched PTS-derived currencies ==
* MemoryCoin (See manifesto)
== See also ==
* http://invictus-innovations.com/protoshares/
Protocoin

From its documentation:
"Protocoin is pure Python implementation of the Bitcoin protocol parsing and networking. Protocoin doesn’t implement the protocol rules, only the serialization/deserialization procedures and also basic clients to interact with the Bitcoin P2P network.
Protocoin is intended to be used to build clients that will collect statistics of the network, but you can also use it to implement a full Bitcoin client."
Sources are on GitHub.
Category:Stubs
Category:Software
Category:Python
Provable fairness

Provable fairness refers to the technology used by bitcoin casino and gambling sites to verify the outcomes of their games. This allows players to confirm that the outcomes were true and fair without any adjustments or manipulations by the gambling sites between when the bet was placed and when the outcome was revealed.
== Process ==
The basis of the system is the cryptographic hash function and it's difficulty to crack. Before the bet begins the gambling server generates a seed and send this as a hashed function to the player. Client side the player then generates a random seed and this is added to the hash function.https://thebitcoinstrip.com/blog/what-does-provably-fair-mean.html After the bet is complete the player decrypts the hash function to determine that it is the same transaction that began. If the function matches then the bet has been uninterrupted. Any difference in the hash indicates that something has gone wrong with the outcome, most likely as a result of manipulation.http://bitcoinchaser.com/provably-fair-gambling/
== References ==
Pt:Main Page

{| style="width:100%; border:none; background:none;"	
Bem vindo à Bitcoin wiki,
informações sobre Bitcoin para todas as suas necessidades.
 pages. Established April 14, 2010.
Esta wiki é mantida pela comunidade Bitcoin.
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"	Bitcoin
 	
Por que?	
 	
== Outras páginas ==
* Ajuda - Documentação sobre como editar a wiki.
* Sobre - Informação deste site.
* Dumps Fazer backup desta wiki.
</noinclude>__NOTOC____NOEDITSECTION__
Pull request

A pull request is a consistent set of changes in the code base. At any given moment in time Bitcoin Core has many open pull requests. Reviewing pull requests is very important to move forward Bitcoin.
Many pull requests are related to a specific BIP, but this is not always the case.
== Useful resources ==
* List of current open pull requests for Bitcoin Core on GitHub
* How to Review Pull Requests in Bitcoin Core, by Jon Atack, regularly updated (as of 2020)
Purecoin

Purecoin is a Haskell full-node implementation, by Russell O'Connor, available on github (mirrored from darcs). On its completeness and motivations, Russell comments:
* purecoin tries to be as simiple an implementation as I can get away with. The idea is more for documentation than for real use.
* it doesn't handle OP_IF, but I'm pretty sure there are many more unknown incompatibilities.
* I guarentee that purecoin is not entirely compatible with bitcoin
Category:Nodes
Category:Haskell
Pybtc

==Python library for Bitcoin==
Key Features:
* Supports addresses types PUBKEY, P2PKH, P2SH, P2SH-PWPKH, P2WPKH, P2WSH.
* Supports BIP32(Hierarchical Deterministic Wallets), BIP39(Mnemonic code generation)
* Supports BIP141(Segregated Witness)
* Transaction constructor
* Mining pool basic primitives
This software is Open Source.
==Documentation==
Documentation can be found here, or in the source archive. It is built using Sphinx:
https://pybtc.readthedocs.io
==Git==
Source code can be found here:
https://github.com/bitaps-com/pybtc
==PIP==
The library can also be found in the Python package repository
https://pypi.org/project/pybtc
This means that it can be installed using pip install pybtc.
== Project status ==
According to the PyPI page, pybtc is not actively maintained. The page suggests using github instead, which offers far more features.
Category:Open Source
Category:Backends
Category:Defunct_products_or_services
Pycoin

A Bitcoin client built using Python 3 and implements the Bitcoin network protocol.
The project was announce on March 3rd, 2011Announcing Pycoin, a (partial) bitcoin protocol implementation in python3
==See Also==
* Original Bitcoin client
* Bitcoin Network Protocol
==External Links==
* pycoin project page on Gitorious
==References==
Category:Nodes
Category:Wallets
Category:Open Source
Category:Clients
Pyminer

A 'getwork' CPU mining client for bitcoin that provides a reference implementation of a miner, for study. 
It is pure-python, and therefore very, very slow compared to alternatives.
The project was announced on February 16th, 2011New pure-python CPU miner, for fun and testing
==External Links==
* Pyminer repository on Github
* Bitcoin Mining Software
==References==
Category:Miners
Category:Open Source