nyuuzyou/wikis huggingface dataset:
Wall of Coins

Wall of Coins is a bitcoin exchange service owned and operated by Genitrust, Inc. It's a fully transparent peer-to-peer market for buying and selling Bitcoin. This is a first that is both a secure live and fixed exchange for the users. Wall of Coins directly connects buyers and sellers in a manner that is intelligent, trustworthy, and secure. We are also the first fully transparent market, and the first to store funds entirely in cold storage.
As of now, Wall of Coins is operating in Sarasota, Florida (USA) and it has opened its doors for Canada, Brazil, Germany, Latvia, Poland and Philippines last December 2015. Early 2016, the platform has also provided more methods other than cash deposit to buyers.
==Deposit Addresses==
In the interest of full transparency, all Wall of Coins deposit addresses are stored on this secure, separate server. We believe that all cryptocurrency markets should do this, so we are taking the lead. Wall of Coins' creators, Genitrust, Inc, will forever adhere to this policy, as it is simply the Bitcoin way: full transparency and entirely peer-to-peer. As the entire internet is currently not 100% peer-to-peer, we will do what we can to keep Wall of Coins, and its services such as the Index of Deposits, as peer-to-peer as possible.
==GPG Verification==
The company's GPG keys are hosted on a separate web server. Both the Wall of Coins company GPG key and our CEO's GPG key are used to sign the Index of Deposits.
== Customer Service ==
Wall of Coins offers a professional customer support via toll-free number, live chat, and email. This allows team members to reach out to various users and assist them with their inquiries and concerns.
== Buying ==
Wall of Coins ensures quality yet fast service for buyers. They have following features:
* 3 payment methods: Bank of America's Teller Assist, cash deposit in various bank branches, and MoneyGram deposit. More methods will be provided soon! 
* Choice to choose the best rate for their coins. Various ads may help buyers choose the best rate for their inputted amount in their orders.
* Only the phone number and email address are needed. Identity verification is not necessary to make a transaction.
== Selling ==
* Choice of creating dynamic or static pricing for the rates
* Has watch-only wallet addresses for funds - wallets are fully transparent, and all funds are never co-mingled into another customer's account.
* 100% rapid cold storage with strict internal policies.
* Advanced "Man-in-the-middle" payment attack security - Wall of Coins has an artificial intelligence layer that detects fraudulent transactions.
==See Also==
* Buying bitcoins
* Selling bitcoins
* Trading bitcoins
==External Links==
* Wall of Coins website 
* Instagram account 
* facebook account 
* Bitcointalk thread 
==References==
Category:Exchanges
ru:Wall of Coins
Wallet.Net

A Secure Remote JSON-RPC BitCoin Wallet Management App Written in .Net.
==Features==
* Full Featured GUI
* Ability to view/sort/filter transactions
* A full address book capability
* Ability to use the "Accounts" feature of bitcoin
* Sending Money
** Using memos/notes
** Using address book
** With variable optional fee
* A full "RPC Shell" as I call it, providing a commandline like interface to the bitcoin JSON-RPC API.
*Built-in SSH Functionality (not requiring outside SSH client or certificate app). That provides the following: (note SSH is disabled currently due to some bugs)
** Secure Encrypted Tunnel to the remote bitcoin host
** Uses an already trusted service (SSH), and the associated daemon, which are typically very secure.
** Limits potential attack vectors since on the bitcoin host, only SSH need be exposed. Making it virtually invisible (bitcoin is undetectable) to a potential attacker.
** Your authentication through the tunnel is done over the encrypted channel.
==History==
This project was first made available July 2, 2011.
==External Links==
* Wallet.Net project on GitHub
* Download Packages (zip containing windows installer)
Category:User Interfaces
Category:Frontends
Category:Free Software
Category:License/GPLv3
Category:Open Source
WalletBit/API/Getnewaddress

The following information may no longer be true, WalletBit service was suspended
 See https://bitcointalk.org/index.php?topic=249751.new
 
 The article is kept only as historic documentation.
===Generate new Bitcoin address===
$fields = array(
 'merchant' => 'owner@example.com',
 'label' => 'TEST'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['label'] . ':' . 'API Key'));
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/getnewaddress');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
If successful $response will contain your new bitcoin address, otherwise empty.
WalletBit/API/Lookup

The following information may no longer be true, WalletBit service was suspended
 See https://bitcointalk.org/index.php?topic=249751.new
 
 The article is kept only as historic documentation.
===Lookup deposit to Bitcoin address===
$fields = array(
 'merchant' => 'owner@example.com',
 'address' => '1BPeF1tGHQj1tHoyZkFps1QKCbnqdx2yHE'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['address'] . ':' . 'API Key'));
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/lookup/deposit');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
If successful $response returns a json encoded array containing batch number, amount, fee, confirmations, txid, address and timestamp of deposit to the provided Bitcoin address, otherwise empty.
WalletBit/API/Send

The following information may no longer be true, WalletBit service was suspended
 See https://bitcointalk.org/index.php?topic=249751.new
 
 The article is kept only as historic documentation.
===Send to Email or Bitcoin address===
$fields = array(
 'merchant' => 'owner@example.com',
 'customer_email' => 'johnsmith@example.com',
 'address' => ,
 'amount' => 0.01000000,
 'details' => 'You got Bitcoins!'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['customer_email'] . ':' . $fields['amount'] . ':' . 'API Key'));
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
if ($response == '1')
{
}
If 'customer_email' is not on WalletBit, it will try to send to the defined bitcoin address.
WalletBit/API/SendTo

The following information may no longer be true, WalletBit service was suspended
 See https://bitcointalk.org/index.php?topic=249751
 
 The article is kept only as historic documentation.
===Send to Email or Mobile number (SMS)===
$fields = array(
 'merchant' => 'owner@example.com', // Requires a valid WalletBit account with API key.
 'to' => '4550142790',	// Email or Mobile number
 'from' => '4591614856', // Email, Name or Phone number
 'details' => 'You got Bitcoins!' // Message to recipient
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['to'] . ':' . $fields['from'] . ':' . 'API Key'));
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/sendto');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = json_decode(curl_exec($ch));
curl_close($ch);
if (is_object($response))
{
 // everythings good
 if ($response->status == 1)
 {
 // any bitcoin sent to this address will be forwarded
 print $response->address;
 }
 else
 {
 // print error message
 print $response->message;
 }
}
==Send Bitcoin Methods==
Parameters:
Merchant - WalletBit email
To * - The recipient's email address or mobile phone number (712 mobile networks in 212 countries)
From - The sender's name, phone number or email address
Details - Optional details to include. (22 characters message limit on phone messages)
* Numbers MUST be in their international format, (no leading zeroes). The UK number 0870 711 111 will become 44870711111
Return:
Status - Indicating if the transaction was successful by a one or zero.
Message - Response from sendTo containing possible errors or similar.
Address - A Bitcoin address. Send bitcoins to it, and it will be forwarded immediately.
When bitcoin is sent to the generated bitcoin address, the system will send out IPN to the defined url in your account.
Our sendTo system covers 712 mobile networks in 212 countries — we can reach almost all mobile phones, however please test if we can reach your mobile or the mobile you want to send to, prior to utilize sending bitcoin via SMS. If the mobile is not covered, you can still enjoy sending instant to email addresses with WalletBit.
WalletBit/API/Sent

===Sent to Email or Bitcoin address===
$fields = array(
 'merchant' => 'owner@example.com',
 'customer_email' => 'johnsmith@example.com',
 'address' => ,
 'amount' => 0.01000000,
 'details' => 'You got Bitcoins!'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['customer_email'] . ':' . $fields['amount'] . ':' . 'API Key'));
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
if ($response == '1')
{
}
If 'customer_email' is not on WalletBit, it will try to send to the defined bitcoin address.
WalletPaperbackup

== PaperBack Encrypted Paper Backup of your Wallet ==
=== Basics ===
A program called PaperBack«2» allows a user to encrypt and print a paper copy of a file, to restore the file you scan or provide a image of the printed paper and it decodes the file
«It should be noted this guide is for Windows Only, A Linux based guide is coming soon»
''
=== How to use with your Wallet ===
#Download PaperBack from the location provided before
#Open PaperBack
#Open Options and select the options you wish to have (For more info, read the page provided above)
#Drag and drop the file (wallet.dat) into the window for printing
##File -> Save to bitmap, It will ask you what file to encode, and then where to save the bitmap
=== Restoring your Wallet ===
#Scan or provide the bitmap of the backup
#Wait for processing
#Save wallet.dat
=== Example ===
Here is the first Image: Encoded Image
Its a empty wallet.dat with Encryption on (AES-256), standard options past that
Here is the damaged copy, Opened in GIMP saved as a JPEG at 4% Compression, then converted back into a Bitmap: Damaged Re-Encoded Image
ECC had to correct 56bytes of bad data.. once decoded the md5 hashes where the same!
Here is a screenshot asking for the password (The password is "bitcoin")
Screen Shot
Example of printed output
Guide By: Jrwr 01:44, 24 June 2011 (GMT)
Wallet Security Dos and Don'ts

This article should not be considered as a replacement for the more in-depth articles on best practices, however key points in wallet security:
== Do ==
* DO seek to understand what you are doing, before you do it
* DO verify understanding by testing with testnet
* DO encrypt your wallet with a strong passphrase
* DO use recommended software from the list at https://bitcoin.org/en/choose-your-wallet
* DO make multiple redundant backups of your wallet
* DO keep your OS up to date and run a virus scanner
* DO manage significant amounts in offline wallets
* DO prepare for black swan disaster scenarios when dealing with large sums (e.g., fire & water damage, theft, head injury and death)
== Don't ==
* DO NOT trust an untrustworthy device or program to generate your wallet keys
* DO NOT generate cold storage keys on Internet-connected machines.
* DO NOT reconnect to the Internet a machine that has had access to cold storage keys.
* DO NOT reuse a wallet encryption passphrases with online services
* DO NOT store your wallet on cloud storage (Dropbox, etc.)
* DO NOT re-use addresses
== See also ==
* Securing your wallet
* Hardware wallet
* Cold storage
* How to set up a secure offline savings wallet
Wallet Security Dos and Don'ts (Windows)

== In general ==
== When using Windows specifically ==
*Do use keyfiles to encrypt your wallets
*Do use a good antivirus and firewall, and keep them up to date (but understand their limitations). 
*Do keep your installed programs updated to the latest version.
*Do uninstall all programs that you don't use regularly.
*Do run programs from questionable sources inside a virtual machine, such as VirtualBox.
*Do browse questionable websites from inside a virtual machine.
*Do connect the bitcoin client and IRC via Tor. 
Category:Instructional
Category:Security
es:Qué se debe y qué no se debe hacer respecto a la seguridad del monedero (Windows)
Wallet Security Dos and Don'ts (general)

*Don't keep all your bitcoins in one wallet.
*Don't develop a carefree attitude towards wallet security. Handle bitcoins with the same amount of diligence as you handle physical cash. 
*Don't use a password for wallet encryption that you use elsewhere on the web.
*Don't use weak passwords. If a password is easy to remember without rehearsal, it is probably weak.
*Don't forget your passwords. If you write them down on a piece of paper, keep that piece of paper in safe storage (safety box, etc.).
*Don't run bitcoin wallet software on an untrusted or badly maintained machine. 
*Don't run software that has been copied illegally (eg, "warez")
*Don't send bitcoins to a wallet that hasn't been backed up beforehand.
*Don't send unencrypted copies of your wallets over the Internet.
*Don't store unencrypted copies of your wallets on online backup/storage services.
*Don't run or install programs from questionable sources on the system where you are running bitcoin wallet software.
*Don't insert any devices of doubtful origin.
*Don't store unencrypted copies of your wallets on a device that you insert into machines of friends, at work, or while traveling.
*Do wipe your HD and perform a clean OS install if you believe your computer has been compromised.
*Do keep at least one offline savings wallet.
*Do backup your spending wallet regularly.
*Do keep dated versions of each backed up wallet.
*Do encrypt all wallets as soon as they leave your system.
*Do keep encrypted backups of all your wallets in at least 3 physically separate locations.
*Do use strong, unique passwords to encrypt your wallets.
*Do update your operating system with the latest security patches.
*Do invest time and money in order to secure any large number of bitcoins 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.
Wallet encryption

This page describes the algorithm used for encrypting the wallet.dat file used in the original Bitcoin client.
Wallet encryption uses AES-256-CBC to encrypt only the private keys that are held in a wallet. The keys are encrypted with a master key
which is entirely random. This master key is then encrypted with
AES-256-CBC with a key derived from the passphrase using SHA-512 and
OpenSSL's EVP_BytesToKey and a dynamic number of rounds determined by
the speed of the machine which does the initial encryption (and is
updated based on the speed of a computer which does a subsequent
passphrase change). Although the underlying code supports multiple
encrypted copies of the same master key (and thus multiple passphrases)
the client does not yet have a method to add additional passphrases.
At runtime, the client loads the wallet as it normally would, however
the keystore stores the keys in encrypted form. When the passphrase
is required (to top up keypool or send coins) it will either be queried
by a GUI prompt, or must first be entered with the walletpassphrase
RPC command. This will change the wallet to "unlocked" state where the
unencrypted master key is stored in memory (in the case of GUI, only for
long enough to complete the requested operation, in RPC, for as long as
is specified by the second parameter to walletpassphrase). The wallet is
then locked (or can be manually locked using the walletlock RPC command)
and the unencrypted master key is removed from memory.
== Implementation details of wallet encryption ==
When the wallet is locked, calls to sendtoaddress, sendfrom, sendmany, and keypoolrefill will return Error -13: "Error: Please enter the wallet passphrase with walletpassphrase first."
When the wallet is unlocked, calls to walletpassphrase will fail.
When a wallet is encrypted, the passphrase is required to top up the
keypool, thus, if the passphrase is rarely entered, it is possible that
keypool might run out. In this case, the default key will be used as the
target for payouts for mining, and calls to getnewaddress and getaccount
address will return an error. In order to prevent such cases, the keypool
is automatically refilled when walletpassphrase is called with a correct
passphrase and when topupkeypool is called (while the wallet is unlocked).
Note that the keypool continues to be topped up on various occasions when
a new key from pool is used and the wallet is unlocked (or unencrypted).
When wallet passphrase enrcyption becomes enabled, any unused keys from the keypool are flushed (marked as used) and new keys protected with encyption are added. For this reason, make a new backup of your wallet so that you will be able to recover the keys from the new key pool should access to your backups be necessary.
Category:Technical
Wallet import format

A wallet import format (WIF, also known as a wallet export format) is a way of encoding a private ECDSA key so as to make it easier to copy.
==Private key to WIF==
1. Take a private key.
 0C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D
2. Add a 0x80 byte in front of it for mainnet addresses or 0xef for testnet addresses. Also add a 0x01 byte at the end if the private key will correspond to a compressed public key.
 800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D
3. Perform SHA-256 hash on the extended key.
 8147786C4D15106333BF278D71DADAF1079EF2D2440A4DDE37D747DED5403592
4. Perform SHA-256 hash on result of SHA-256 hash.
 507A5B8DFED0FC6FE8801743720CEDEC06AA5C6FCA72B07C49964492FB98A714
5. Take the first 4 bytes of the second SHA-256 hash; this is the checksum.
 507A5B8D
6. Add the 4 checksum bytes from point 5 at the end of the extended key from point 2.
 800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D507A5B8D
7. Convert the result from a byte string into a base58 string using Base58Check encoding. This is the wallet import format (WIF).
 5HueCGU8rMjxEXxiPuD5BDku4MkFqeZyd4dZ1jvhTVqvbTLvyTJ
==WIF to private key==
1. Take a wallet import format (WIF) string.
 5HueCGU8rMjxEXxiPuD5BDku4MkFqeZyd4dZ1jvhTVqvbTLvyTJ
2. Convert it to a byte string using Base58Check encoding.
 800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D507A5B8D
3. Drop the last 4 checksum bytes from the byte string.
 800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D
4. Drop the first byte (it should be 0x80, however legacy Electrum or some SegWit vanity address generators may use 0x81-0x87). If the private key corresponded to a compressed public key, also drop the last byte (it should be 0x01). If it corresponded to a compressed public key, the WIF string will have started with K or L (or M, if it's exported from legacy Electrum etc) instead of 5 (or c instead of 9 on testnet). This is the private key.
 0C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D
==WIF checksum checking==
1. Take the wallet import format (WIF) string.
 5HueCGU8rMjxEXxiPuD5BDku4MkFqeZyd4dZ1jvhTVqvbTLvyTJ
2. Convert it to a byte string using Base58Check encoding.
 800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D507A5B8D
3. Drop the last 4 checksum bytes from the byte string.
 800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D
4. Perform SHA-256 hash on the shortened string.
 8147786C4D15106333BF278D71DADAF1079EF2D2440A4DDE37D747DED5403592
5. Perform SHA-256 hash on result of SHA-256 hash.
 507A5B8DFED0FC6FE8801743720CEDEC06AA5C6FCA72B07C49964492FB98A714
6. Take the first 4 bytes of the second SHA-256 hash; this is the checksum.
 507A5B8D
7. Make sure it is the same as the last 4 bytes from point 2.
 507A5B8D
8. If they are, and the byte string from point 2 starts with 0x80 (0xef for testnet addresses), then there is no error.
== References ==
Wave of bits

The wave of bits is an explosive growth in the bitcoin tipping industry, chiefly on Reddit and Twitter (#waveofbits) via ChangeTip. It began around November 6, 2014Looks like Changetip is suddenly getting that attention it very well deserved. and continued for several weeks. As a result the ChangeTip and Bitcoin subreddits appreciated significantly as thousands of new interested users investigated.http://www.reddit.com/r/Bitcoin/comments/2lsbhc/what_is_causing_this_recent_tipping_trend/clxooot
==References==
Category:2014 events
WeExchange

A bitcoin currency exchange/trading platform.
==Adding Funds==
===USD===
* A MtGox redeemable code is the method for depositing USD funds.
===CAD===
* Interac E-Transfer
===AUD===
* Bank wire transfer (transfer must include reference message).
===BTC===
* Bitcoins funds can be deposited at no charge. 
The BTC deposit address does not expire or change and later deposits to the same address can be made.
BTC funds deposited are available for trading after six confirmations.
==Withdrawing Funds==
===BTC===
* There is no fee for BTC withdrawal.
Withdrawals are sent through the Bitcoin network unless the Bitcoin address is the deposit address for another WeExchange account and then it is handled internally with no transaction on the blockchain.
===USD===
* A MtGox redeemable code is the method for withdrawing USD funds.
===CAD===
* Interac E-Transfer
===AUD===
* Bank wire transfer
==Trading==
For an introductory period of time there is no charge (no commission/fee) for trades on the currency exchange.
==Security==
Login and withdrawals can be protected with multi-factor authentication (also referred to as two-factor authentication or 2FA) using Google Authenticator.
==History==
The exchange emerged from its limited (invite-only) operations on December 8, 2012WeExchange.
The exchange is operated in Australia by WeExchange Australia, Pty. Ltd and in the U.S. by WeExchange, Inc of Texas.
==See Also==
* Buying bitcoins
* Selling bitcoins
==External Links==
* WeExchange.co website
==References==
Category:Exchanges
Category:EWallets
What is Bitcoin?

The most-widely known video that introduces Bitcoin.
The video was created following a bounty offer for an animated movie. Bounty for Bitcoin Animated Movie The video was posted on YouTube on March 22, 2011.What is Bitcoin? The bounty was awarded to JustMoon and the 8,511.96 BTC award was distributed on April 05, 2011.Does WeUseCoins Deserves the Full Bounty?
The award recipient created the Bitcoin Marketing Fund and donated most of the bounty award proceeds to the fund.
==External Links==
* What is Bitcoin? video on YouTube
* What is Bitcoin? (German) video on YouTube
* What is Bitcoin? (Italian) video on YouTube
* What is Bitcoin? (Russian) video on YouTube
==References==
Category:Introduction
Category:Marketing