https://tests.bitcoin.it/w/api.php?action=feedcontributions&user=Wtogami&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-28T13:13:44ZUser contributionsMediaWiki 1.30.0https://tests.bitcoin.it/w/index.php?title=Segwit_support&diff=63349Segwit support2017-06-13T11:03:03Z<p>Wtogami: </p>
<hr />
<div><big><big>'''PLEASE NOTE:''' This list is not yet complete.</big></big><br />
<br />
'''Developers: Please add a row for yourself to reflect your positions. If for some reason you don't already have a wiki account that can edit the page, make an account and ask luke-jr for help if you get caught in the anti-spam.'''<br />
<br />
{| class="wikitable"<br />
| {{No}} || doesn't support (but might or might not go along with it with sufficient community support)<br />
|-<br />
| {{Deficient}} || okay with the idea, but considers it to have insufficient community support<br />
|-<br />
| {{Evaluating}} || still evaluating the idea<br />
|-<br />
| {{Wanting}} || positively likes the idea, but considers it to have insufficient community support<br />
|-<br />
| {{Weak}} || better than nothing at all<br />
|-<br />
| {{Acceptable}} || it is a workable solution<br />
|-<br />
| {{Prefer}} || it is what he would choose if it was only up to him and no outside influences<br />
|}<br />
<br />
<!-- README: please keep alphabetically ordered by surname! --><br />
<br />
''Note that support for BIP148 does not mean developers support merging it into Core.''<br />
<br />
{| class="wikitable sortable"<br />
! rowspan=2 colspan=2 | Developer & affiliation* <!-- Using one year before the the creation date of this page as the benchmark. Do not list yourself as affiliated with a project that you haven't made meaningful contributions to since then. --><br />
! Segwit itself<br />
! colspan=3 | Deployment methods<br />
! colspan=2 | Hardfork bundles (Silbert agreement)<br />
|-<br />
! [https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki BIP 141] !! [https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki BIP 148] !! [https://github.com/bitcoin/bips/blob/master/bip-0149.mediawiki BIP 149] !! [https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki BIP 91] || Segwit2x || [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014445.html COOP]<br />
|-<br />
| ฿tcDrak || Core || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}<br />
|-<br />
| Bryan Bishop || || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Andrew Chow || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Matt Corallo || Core || {{Prefer}} || {{No}} || || {{Acceptable}} || {{No|LOL}} ||<br />
|-<br />
| Johnathan Corgan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}<br />
|-<br />
| Luke Dashjr || Core || {{Prefer}} || {{Prefer}} || {{No}} || {{Acceptable|Acc. until July}} || {{No}} || {{Deficient}}<br />
|-<br />
| Christian Decker || Core || {{Prefer}} || {{Acceptable}} || || || || <br />
|-<br />
| Nicolas Dorier || Core || {{Prefer}} || {{Deficient}} || || || ||<br />
|-<br />
| Marco Falke || Core || {{Prefer}} || {{Deficient}} || {{Prefer}} || {{Deficient}} || ||<br />
|-<br />
| Mark Friedenbach || BIP 68/112 || {{Prefer}} || {{Prefer}} || {{No}} || {{Acceptable|Acc. until July}} || {{No|LOL}} || {{No|Nope}}<br />
|-<br />
| Pavel Janik || Core || {{Prefer}} || {{No}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}<br />
|-<br />
| Thomas Kerin || Core || {{Prefer}} || {{Wanting}} || {{Prefer}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Johnson Lau || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || ||<br />
|-<br />
| Eric Lombrozo || || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Greg Maxwell || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Alex Morcos || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} ||<br />
|-<br />
| Pavol "stick" Rusnak || Trezor || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}<br />
|-<br />
| Rusty Russell || c-lightning || {{Prefer}} || {{Prefer}} || || || ||<br />
|-<br />
| Gregory Sanders || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} ||<br />
|-<br />
| Jonas Schnelli || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}<br />
|-<br />
| Jorge Timon || Core || {{Prefer}} || {{No}} || {{Prefer}} || {{Deficient}} || {{No}} || {{No}}<br />
|-<br />
| Peter Todd || Core || {{Prefer}} || {{Acceptable}} || || || ||<br />
|-<br />
| Warren Togami || Elements || {{Prefer}} || {{Prefer}} || {{Acceptable}} || || ||<br />
|-<br />
| Wladimir van der Laan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}<br />
|-<br />
| flix1 || || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{Deficient}} || {{Evaluating}} || {{Evaluating}}<br />
|-<br />
| Leo Wandersleb || Mycelium || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Pieter Wuille || Core || {{Prefer}} || || || || {{No}} ||<br />
|}<br />
<br />
* "affiliation" is an optional field for the company or project the individual is associated with, that most qualifies the person to comment on the matter and is not meant as a company or project endorsement of the individual's position.</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Segwit_support&diff=63295Segwit support2017-06-11T09:26:58Z<p>Wtogami: </p>
<hr />
<div><big><big>'''PLEASE NOTE:''' This list is not yet complete, nor completely vetted by the parties listed for accuracy.</big></big><br />
<br />
'''Developers: Please edit your row (add one if you're missing) to reflect your positions. If for some reason you don't already have a wiki account that can edit the page, make an account and ask luke-jr to give it access.'''<br />
<br />
{| class="wikitable"<br />
| {{No}} || doesn't support (but might or might not go along with it with sufficient community support)<br />
|-<br />
| {{Deficient}} || okay with the idea, but considers it to have insufficient community support<br />
|-<br />
| {{Evaluating}} || still evaluating the idea<br />
|-<br />
| {{Wanting}} || positively likes the idea, but considers it to have insufficient community support<br />
|-<br />
| {{Weak}} || better than nothing at all<br />
|-<br />
| {{Acceptable}} || it is a workable solution<br />
|-<br />
| {{Prefer}} || it is what he would choose if it was only up to him and no outside influences<br />
|}<br />
<br />
<!-- README: please keep alphabetically ordered by surname! --><br />
<br />
''Note that support for BIP148 does not mean developers support merging it into Core.''<br />
<br />
{| class="wikitable sortable"<br />
! rowspan=2 | Developer<br />
! Segwit itself<br />
! colspan=3 | Deployment methods<br />
! colspan=2 | Hardfork bundles (Silbert agreement)<br />
|-<br />
! [https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki BIP 141] !! [https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki BIP 148] !! [https://github.com/bitcoin/bips/blob/master/bip-0149.mediawiki BIP 149] !! [https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki BIP 91] || Segwit2x || [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014445.html COOP]<br />
|-<br />
| ฿tcDrak || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || ||<br />
|-<br />
| Bryan Bishop || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Andrew Chow || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Matt Corallo || {{Prefer}} || {{No}} || || {{Acceptable}} || {{No|LOL}} ||<br />
|-<br />
| Johnathan Corgan || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{No}} || {{No}} || {{Evaluating}}<br />
|-<br />
| Suhas Daftuar || {{Prefer}} || {{No}} || || || ||<br />
|-<br />
| Luke Dashjr || {{Prefer}} || {{Prefer}} || {{No}} || {{Acceptable|Acc. until July}} || {{No}} || {{Deficient}}<br />
|-<br />
| Christian Decker || {{Prefer}} || {{Acceptable}} || || || || <br />
|-<br />
| Nicolas Dorier || {{Prefer}} || {{Deficient}} || || || ||<br />
|-<br />
| Marco Falke || {{Prefer}} || || || || ||<br />
|-<br />
| Michael Ford || {{Prefer}} || || || || ||<br />
|-<br />
| Mark Friedenbach || {{Prefer}} || {{Acceptable}} || || || ||<br />
|-<br />
| Pavel Janik || {{Prefer}} || || || || ||<br />
|-<br />
| Thomas Kerin || {{Prefer}} || {{Wanting}} || {{Prefer}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Johnson Lau || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || ||<br />
|-<br />
| Eric Lombrozo || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Greg Maxwell || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Alex Morcos || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} ||<br />
|-<br />
| Rusty Russell || {{Prefer}} || {{Prefer}} || || || ||<br />
|-<br />
| Gregory Sanders || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} ||<br />
|-<br />
| Jonas Schnelli || {{Prefer}} || {{Wanting}} || {{Acceptable}} || || ||<br />
|-<br />
| Patrick Strateman || {{Prefer}} || || || || ||<br />
|-<br />
| Jorge Timon || {{Prefer}} || {{No}} || {{Prefer}} || {{Deficient}} || {{No}} || {{No}}<br />
|-<br />
| Peter Todd || {{Prefer}} || {{Acceptable}} || || || ||<br />
|-<br />
| Warren Togami || {{Prefer}} || {{Prefer}} || {{Acceptable}} || || ||<br />
|-<br />
| Wladimir van der Laan || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}<br />
|}</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Block_size_limit_controversy&diff=56817Block size limit controversy2015-06-02T05:30:50Z<p>Wtogami: /* Arguments in favor of increasing the blocksize */ Why did you just remove a valid argument?</p>
<hr />
<div>== Introduction ==<br />
<br />
Blocks are limited to 1MB in size. Miners can mine blocks upto the 1MB fixed limit. Any block larger than 1MB is invalid.<br />
<br />
Blocksize limits were put in place for the dual purposes of discouraging economically frivolous transactions from flooding the blockchain and encouraging transactions fees to incentivize miners.<br />
<br />
{{Quote|Once a predetermined number of coins have entered circulation, the incentive can transition entirely to transaction fees and be completely inflation free.|Satoshi Nakamoto <ref>https://bitcoin.org/bitcoin.pdf</ref>}}<br />
<br />
<br />
== Arguments in favor of increasing the blocksize ==<br />
* Bigger blocks (more transactions per second)<br />
* Sidechains and Lightning do not exist.<br />
<br />
== Arguments in opposition of increasing the blocksize ==<br />
* A hard fork requires waiting for sufficient consensus.<br />
* Risk of catastrophic consensus failure{{clarification needed}}<br />
* Orphan rate amplification, more reorgs and double-spends due to slower propagation speeds.<br />
* European/American pools at more of a disadvantage compared to the Chinese pools{{why}}<br />
* No amount of max block size would support all the world's future transactions on the main blockchain (various types of off-chain transactions are the only long-term solution)<br />
<br />
=== Damage to decentalization ===<br />
* Bitcoin is only useful if it is decentralized because centralization requires trust. Bitcoins value proposition is trustlessness.<br />
* The larger the hash-rate a single miner controls, the more centralized Bitcoin becomes and the more trust using Bitcoin requires.<br />
* Running your own full node while mining rather than giving another entity the right to your hash-power decreases the hash-rate of large miners. Those who control hash-power are able to control their own hash power if and only if they run a full node.<br />
* Less individuals who control hash-power will run full nodes if running one becomes more expensive.<br />
* Larger blocks leads to more expensive full nodes.<br />
* Therefore, larger blocks lead to less hashers running full nodes, which leads to centralized entities having more power, which makes Bitcoin require more trust, which weakens Bitcoins value proposition.<br />
<br />
== Entities positions ==<br />
{| class="wikitable sortable"<br />
! Entity<br />
! Supports Larger Blocks<br />
! Supports Hard Fork<br />
|- <br />
| CoinBase<br />
|{{Yes}}<br />
|<br />
|}</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Block_size_limit_controversy&diff=56792Block size limit controversy2015-06-01T21:20:26Z<p>Wtogami: /* Argument in opposition of increasing the blocksize */</p>
<hr />
<div>== Argument in favor of increasing the blocksize ==<br />
* Bigger blocks (more transactions per second)<br />
* Sidechains and Lightning require waiting for development.<br />
<br />
== Argument in opposition of increasing the blocksize ==<br />
* A hard fork requires waiting for sufficient consensus.<br />
* Orphan rate amplification, more reorgs and double-spends due to slower propagation speeds.<br />
* European/American pools at more of a disadvantage compared to the Chinese pools{{why}}<br />
* No amount of max block size would support all the world's future transactions on the main blockchain (various types of off-chain transactions are the only long-term solution)<br />
* Risk of catastrophic consensus failure{{clarification needed}}<br />
<br />
=== Damage to decentalization ===<br />
* Bitcoin is only useful if it is decentralized because centralization requires trust. Bitcoins value proposition is trustlessness.<br />
<br />
* The larger the hash-rate a single miner controls, the more centralized Bitcoin becomes and the more trust using Bitcoin requires.<br />
<br />
* Running your own full node while mining rather than giving another entity the right to your hash-power decreases the hash-rate of large miners. Those who control hash-power are able to control their own hash power if and only if they run a full node.<br />
<br />
* Less individuals who control hash-power will run full nodes if running one becomes more expensive.<br />
<br />
* Larger blocks leads to more expensive full nodes.<br />
<br />
* Therefore, larger blocks lead to less hashers running full nodes, which leads to centralized entities having more power, which makes Bitcoin require more trust, which weakens Bitcoins value proposition.<br />
<br />
{| class="wikitable sortable"<br />
! Entity<br />
! Supports Larger Blocks<br />
! Supports Hard Fork<br />
|- <br />
| CoinBase<br />
|{{Yes}}<br />
|<br />
|}</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Block_size_limit_controversy&diff=56770Block size limit controversy2015-06-01T09:30:35Z<p>Wtogami: /* Argument in favor of increasing the blocksize */</p>
<hr />
<div>== Argument in favor of increasing the blocksize ==<br />
* Bigger blocks (more transactions per second)<br />
* Sidechains and Lightning do not exist.<br />
<br />
== Argument in opposition of increasing the blocksize ==<br />
* Orphan rate magnification, more reorgs and double-spends<br />
* European/American pools at more of a disadvantage compared to the Chinese pools<br />
* No amount of max block size would support all the world's future transactions on the main blockchain (various types of off-chain transactions are the only long-term solution)<br />
* Risk of catastrophic consensus failure<br />
<br />
=== Damage to decentalization ===<br />
* Bitcoin is only useful if it is decentralized because centralization requires trust. Bitcoins value proposition is trustlessness.<br />
<br />
* The larger the hash-rate a single miner controls, the more centralized Bitcoin becomes and the more trust using Bitcoin requires.<br />
<br />
* Running your own full node while mining rather than giving another entity the right to your hash-power decreases the hash-rate of large miners. Those who control hash-power are able to control their own hash power if and only if they run a full node.<br />
<br />
* Less individuals who control hash-power will run full nodes if running one becomes more expensive.<br />
<br />
* Larger blocks leads to more expensive full nodes.<br />
<br />
* Therefore, larger blocks lead to less hashers running full nodes, which leads to centralized entities having more power, which makes Bitcoin require more trust, which weakens Bitcoins value proposition.<br />
<br />
{| class="wikitable sortable"<br />
! Entity<br />
! Supports Larger Blocks<br />
! Supports Hard Fork<br />
|- <br />
| CoinBase<br />
|{{Yes}}<br />
|<br />
|}</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Block_size_limit_controversy&diff=56769Block size limit controversy2015-06-01T09:27:27Z<p>Wtogami: /* Argument in opposition of increasing the blocksize */</p>
<hr />
<div>== Argument in favor of increasing the blocksize ==<br />
* Bigger blocks (more transactions per second)<br />
== Argument in opposition of increasing the blocksize ==<br />
* Orphan rate magnification, more reorgs and double-spends<br />
* European/American pools at more of a disadvantage compared to the Chinese pools<br />
* No amount of max block size would support all the world's future transactions on the main blockchain (various types of off-chain transactions are the only long-term solution)<br />
* Risk of catastrophic consensus failure<br />
<br />
=== Damage to decentalization ===<br />
* Bitcoin is only useful if it is decentralized because centralization requires trust. Bitcoins value proposition is trustlessness.<br />
<br />
* The larger the hash-rate a single miner controls, the more centralized Bitcoin becomes and the more trust using Bitcoin requires.<br />
<br />
* Running your own full node while mining rather than giving another entity the right to your hash-power decreases the hash-rate of large miners. Those who control hash-power are able to control their own hash power if and only if they run a full node.<br />
<br />
* Less individuals who control hash-power will run full nodes if running one becomes more expensive.<br />
<br />
* Larger blocks leads to more expensive full nodes.<br />
<br />
* Therefore, larger blocks lead to less hashers running full nodes, which leads to centralized entities having more power, which makes Bitcoin require more trust, which weakens Bitcoins value proposition.<br />
<br />
{| class="wikitable sortable"<br />
! Entity<br />
! Supports Larger Blocks<br />
! Supports Hard Fork<br />
|- <br />
| CoinBase<br />
|{{Yes}}<br />
|<br />
|}</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Block_size_limit_controversy&diff=56768Block size limit controversy2015-06-01T09:09:32Z<p>Wtogami: /* Argument in opposition of increasing the blocksize */</p>
<hr />
<div>== Argument in favor of increasing the blocksize ==<br />
* Bigger blocks (more transactions per second)<br />
== Argument in opposition of increasing the blocksize ==<br />
* Orphan rate magnification, more reorgs and double-spends<br />
* European/American pools at more of a disadvantage compared to the Chinese pools<br />
* Risk of catastrophic consensus failure<br />
<br />
=== Damage to decentalization ===<br />
* Bitcoin is only useful if it is decentralized because centralization requires trust. Bitcoins value proposition is trustlessness.<br />
<br />
* The larger the hash-rate a single miner controls, the more centralized Bitcoin becomes and the more trust using Bitcoin requires.<br />
<br />
* Running your own full node while mining rather than giving another entity the right to your hash-power decreases the hash-rate of large miners. Those who control hash-power are able to control their own hash power if and only if they run a full node.<br />
<br />
* Less individuals who control hash-power will run full nodes if running one becomes more expensive.<br />
<br />
* Larger blocks leads to more expensive full nodes.<br />
<br />
* Therefore, larger blocks lead to less hashers running full nodes, which leads to centralized entities having more power, which makes Bitcoin require more trust, which weakens Bitcoins value proposition.<br />
<br />
{| class="wikitable sortable"<br />
! Entity<br />
! Supports Larger Blocks<br />
! Supports Hard Fork<br />
|- <br />
| CoinBase<br />
|{{Yes}}<br />
|<br />
|}</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=CryptoPayment&diff=47347CryptoPayment2014-05-13T22:56:32Z<p>Wtogami: /* Disclaimer */</p>
<hr />
<div>'''CryptoPayment''' is a MediaWiki extension to limit spam by requiring a small one-time bitcoin payment before a user is allowed to edit or create pages. While the payment is deliberately small for a normal user, it presents a barrier to a mass-spammer. Funds sent to this Wiki will be used offset moderate expenses (hosting, DDoS protection, security maintenance). If any money is remaining it will go toward funding Bitcoin development.<br />
<br />
==Usage==<br />
<br />
In order to enable your user account to edit pages, log in and visit [[Special:CryptoPayment]], and you'll be given an address to which to send a small amount of bitcoins. The current fee amount is 0.001 BTC, which is presently less than 1 USD.<br />
<br />
Once you send the requested bitcoin amount to the address displayed and your payment is confirmed, your account will automatically be added to the [https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=trusted trusted group] and be afforded edit privileges.<br />
<br />
===Confirmations===<br />
<br />
Payments will be considered paid after it is confirmed in a Bitcoin block.<br />
<br />
==Privacy==<br />
<br />
Please note that with this payment may allow people to connect your bitcoin wallet to your wiki account via blockchain analysis. If this is a concern to you, take the appropriate steps to protect your [[Anonymity]].<br />
<br />
== Code ==<br />
Source will be released after the backend interface to bitcoind is rewritten.<br />
<br />
== Disclaimer ==<br />
This payment is merely a one-time anti-spam measure to enable an account for edit access. The volunteer administrators of this site may revoke edit access for any or no reason, usually in response to abuse or spamming. You are not entitled to any refund under any circumstance.<br />
<br />
==Questions or comments?==<br />
<br />
If you have questions, comments or a support request, please post in the [https://bitcointalk.org/index.php?board=168.0 Bitcoin Wiki Support forum]. We also have a chatroom at [http://webchat.freenode.net/?channels=#bitcoin-wiki #bitcoin-wiki on freenode IRC]. Please ask your question and be prepared to stick around for a few hours before you get a response.</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=CryptoPayment&diff=46788CryptoPayment2014-04-25T07:51:57Z<p>Wtogami: </p>
<hr />
<div>'''CryptoPayment''' is a MediaWiki extension to limit spam by requiring a small one-time bitcoin payment before a user is allowed to edit or create pages. While the payment is deliberately small for a normal user, it presents a barrier to a mass-spammer. Funds sent to this Wiki will be used offset moderate expenses (hosting, DDoS protection, security maintenance). If any money is remaining it will go toward funding Bitcoin development.<br />
<br />
==Usage==<br />
<br />
In order to enable your user account to edit pages, log in and visit [[Special:CryptoPayment]], and you'll be given an address to which to send a small amount of bitcoins. The current fee amount is 0.001 BTC, which is presently less than 1 USD.<br />
<br />
Once you send the requested bitcoin amount to the address displayed and your payment is confirmed, your account will automatically be added to the [https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=trusted trusted group] and be afforded edit privileges.<br />
<br />
===Confirmations===<br />
<br />
Payments will be considered paid after it is confirmed in a Bitcoin block.<br />
<br />
==Privacy==<br />
<br />
Note that this may allow adversaries to connect your bitcoin wallet to your wiki account via blockchain analysis. If this is a concern to you, take the appropriate steps to protect your [[Anonymity]].<br />
<br />
== Code ==<br />
Source will be released after the backend interface to bitcoind is rewritten.<br />
<br />
== Disclaimer ==<br />
This payment is merely an anti-spam measure as a one-time measure to enable an account for edit access. The volunteer administrators of this site may revoke edit access for any or no reason, usually in response to abuse or spamming. You are not entitled to any refund under any circumstance.<br />
<br />
==Questions or comments?==<br />
<br />
If you have questions, comments or a support request, please post in the [https://bitcointalk.org/index.php?board=168.0 Bitcoin Wiki Support forum]. We also have a chatroom at [http://webchat.freenode.net/?channels=#bitcoin-wiki #bitcoin-wiki on freenode IRC]. Please ask your question and be prepared to stick around for a few hours before you get a response.</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=MediaWiki:Loginstart&diff=45264MediaWiki:Loginstart2014-03-23T09:56:53Z<p>Wtogami: Created page with "You must have cookies enabled to log in to {{SITENAME}}. <span style="background-color:#fcaf3e;">'''Note: see CryptoPayment and follow directions to enable edit privilege..."</p>
<hr />
<div>You must have cookies enabled to log in to {{SITENAME}}.<br />
<br />
<span style="background-color:#fcaf3e;">'''Note: see [[CryptoPayment]] and follow directions to enable edit privileges for your account.'''</span></div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=CryptoPayment&diff=45253CryptoPayment2014-03-23T08:07:56Z<p>Wtogami: </p>
<hr />
<div>'''CryptoPayment''' is a MediaWiki extension to limit spam by requiring a small one-time bitcoin payment before a user is allowed to edit or create pages. While the payment is deliberately small for a normal user, it presents a barrier to a mass-spammer. Funds sent to this Wiki will be used offset moderate expenses (hosting, DDoS protection, security maintenance). If any money is remaining it will go toward funding Bitcoin development.<br />
<br />
==Usage==<br />
<br />
In order to enable your user account to edit pages, log in and visit [[Special:CryptoPayment]], and you'll be given an address to which to send a small amount of bitcoins.<br />
<br />
Once you send the requested bitcoin amount to the address displayed and your payment is confirmed, your account will automatically be added to the [https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=trusted trusted group] and be afforded edit privileges.<br />
<br />
===Confirmations===<br />
<br />
Payments will be considered paid after it is confirmed in a Bitcoin block.<br />
<br />
== Code ==<br />
Source will be released after the backend interface to bitcoind is rewritten.<br />
<br />
==Questions or comments?==<br />
<br />
If you have questions, comments or a support request, please post in the [https://bitcointalk.org/index.php?board=168.0 Bitcoin Wiki Support forum]. We also have a chatroom at [http://webchat.freenode.net/?channels=#bitcoin-wiki #bitcoin-wiki on freenode IRC]. Please ask your question and be prepared to stick around for a few hours before you get a response.</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=CryptoPayment&diff=45198CryptoPayment2014-03-22T14:25:49Z<p>Wtogami: Hopefully better grammar.</p>
<hr />
<div>'''CryptoPayment''' is a MediaWiki extension to limit spam by requiring a small one-time bitcoin payment before a user is allowed to edit or create pages. While the payment is deliberately small for a normal user, it presents a barrier to a mass-spammer. Funds sent to this Wiki will be used offset moderate expenses (hosting, DDoS protection, security maintenance). If any money is remaining it will go toward funding Bitcoin development.<br />
<br />
==Usage==<br />
<br />
In order to enable your user account to edit pages, log in and visit [[Special:CryptoPayment]], and you'll be given an address to which to send a small amount of bitcoins.<br />
<br />
Once you send the requested bitcoin amount to the address displayed and your payment is confirmed, your account will automatically be added to the [https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=trusted trusted group] and be afforded edit privileges.<br />
<br />
===Confirmations===<br />
<br />
Payments will be considered paid after it is confirmed in a Bitcoin block.<br />
<br />
== Code ==<br />
Source will be released after the backend interface to bitcoind is rewritten.<br />
<br />
==Uso (Español)==<br />
<br />
Si pagas tu acceso a la wiki en inglés (subdominio en.bitcoin.it/wiki) no podrás editar las páginas en Español. Para editar la wiki en Español (subdominio es.bitcoin.it/wiki/) el enlace a Especial:CryptoPayment es este https://es.bitcoin.it/wiki/Especial:CryptoPayment<br />
<br />
==Questions or comments?==<br />
<br />
If you have questions, comments or a support request, please post in the [https://bitcointalk.org/index.php?board=168.0 Bitcoin Wiki Support forum]. We also have a chatroom at [http://webchat.freenode.net/?channels=#bitcoin-wiki #bitcoin-wiki on freenode IRC]. Please ask your question and be prepared to stick around for a few hours before you get a response.</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Talk:CryptoPayment&diff=45197Talk:CryptoPayment2014-03-22T14:21:58Z<p>Wtogami: </p>
<hr />
<div>==Fee Reduced to 0.003 as of 22 March 2014==<br />
Per the Bitcoin protocol rules, be sure that you include at least a fee of 0.0001 to ensure that this payment will eventually be mined.<br />
<br />
==Amount reduction==<br />
<br />
As the value of BC rose, I propose to reduce the amount.<br />
<br />
0.01BTC is a day's salary in certain countries. And why are you waiting for 6 confirmations if this measure is really only a spam barrier?<br />
21:15, 22 April 2013 (GMT)<br />
<br />
:: This was made back when the price of BTC was in the low two digits. :) Yes payment amount could be reduced, but then you'd have to pay 0.0005 BTC fee for sending < 0.01. <br />
:: Also, 6 conf is required since this uses the MtGox payment processing API, which requires 6 conf. Not really worth it to special-case it. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 13:47, 30 April 2013 (GMT)<br />
<br />
:: To this day, the editing fee is worth 5€ or 5.5$. I already contacted MagicalTux, and posted on Bitcointalk.org (got flamed btw) while BTC was around $100, and I see that the problem is not yet answered. Thanks you MagicalTux for preventing this wiki to gain content and active users ! --[[User:Twix|Twix]] ([[User talk:Twix|talk]]) 22:59, 19 November 2013 (GMT)<br />
<br />
== Require payment for new user creation ==<br />
<br />
I believe that a payment is required on each new user creation, not just in order to gain edit powers.<br />
Currently a new spam user is created every few minutes, and the [[Special:RecentChanges|Recent Changes]] page has become completely spammed.<br />
<br />
[[User:Ripper234|Ripper234]] ([[User talk:Ripper234|talk]]) 10:54, 30 April 2013 (GMT)<br />
<br />
:: Payment is only required to activate edit privileges, hence the flood of spam users. but it's not a bad idea to have it be required for user creation too, to avoid that spam. The problem is that it'd require more development, and mtux doesn't really have time to do this for the wiki right now. <br />
:: In the meantime as a quick hack, you can just filter the recent changes list to exclude everything from the User namespace. [https://en.bitcoin.it/w/index.php?namespace=2&invert=1&title=Special%3ARecentChanges try this]. It's not perfect, since it also excludes user page edits... but it's good. :) [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 13:44, 30 April 2013 (GMT)<br />
<br />
== Informing new users ==<br />
<br />
It's not very clear right now that people need to visit this page to learn how to contribute. I didn't find out until I was reading through some questions on StackExchange, saw somebody someone ask why he couldn't edit.<br />
<br />
I know there's a line on the front page in font-size 10 saying "Anti-spam protection from BitcoinPayment", but people unfamliar with BitcoinPayment will not notice that. When they don't see an edit button they're likely to assume that you either need to wait for manual approval or that you need to know the right people within the community.<br />
<br />
It's been ages since I tried to write code for MediaWiki, so I don't know if on of the following suggestions is possible:<br />
<br />
* don't hide the edit link, but instead redirect the user to this page for instructions<br />
* next to the "Show source" link, show "Want to contribute?"<br />
<br />
Or this solution, which doesn't require code:<br />
* put a text like "If you want to contribute, please read these instructions" in a very prominent place on the landing page.<br />
<br />
<br />
: You're completely right, I was thinking the same thing for a long time. I don't know how to implement it - I just asked it on [http://webapps.stackexchange.com/questions/44319/can-a-mediawiki-moderator-put-a-system-message-for-each-new-user webapps Stackexchange]. If you know of a good way to implement that without having access to the backened/php, let us know. [[User:Ripper234|Ripper234]] ([[User talk:Ripper234|talk]]) 15:44, 17 May 2013 (GMT)<br />
<br />
:: We have edited the "no permission" message to point to BitcoinPayment. Also note that the login screen has had the prominent orange banner mentioning the requirement for BitcoinPayment all this time, also. I suppose "ideally" any user who is not trusted should get a persistent banner in the header or something, but that requires editing on the backend. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 03:47, 24 May 2013 (GMT)<br />
<br />
::: Can we change "View Source" to "Edit" so new users actually get to the explanation screen? --[[User:Luke-jr|Luke-jr]] ([[User talk:Luke-jr|talk]]) 04:55, 25 May 2013 (GMT)</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Template:CryptoPayment&diff=45194Template:CryptoPayment2014-03-22T04:00:41Z<p>Wtogami: </p>
<hr />
<div>CryptoPayment is the wiki's automated anti-spam protection mechanism. A small one-time Bitcoin payment is required before a user is allowed to edit or create pages. While the payment is deliberately small for a normal user, it presents a barrier to a mass-spammer. Funds sent to this wiki will be used to keep the wiki online (cost of domain name and hosting), and remaining funds will be used to support Bitcoin development.<br />
<br />
See [[CryptoPayment]] for more info.<br />
<br />
== Status ==<br />
<br />
{{#ifeq: {{{status}}} | todo | To move forward, you will need to send 0.003 BTC to [bitcoin:{{{addr}}} {{{addr}}}]. }}<br />
<br />
{{#ifeq: {{{status}}} | done | Thank you for your support! }}<br />
<br />
{{#ifeq: {{{status}}} | nologin | You'll need to login to know your status. }}</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Template:BitcoinPayment&diff=45193Template:BitcoinPayment2014-03-22T03:59:55Z<p>Wtogami: Redirected page to Template:CryptoPayment</p>
<hr />
<div>#REDIRECT [[Template:CryptoPayment]]</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Template:CryptoPayment&diff=45192Template:CryptoPayment2014-03-22T03:58:25Z<p>Wtogami: </p>
<hr />
<div>CryptoPayment is the wiki's automated anti-spam protection mechanism. A small one-time Bitcoin payment is required before a user is allowed to edit or create pages. While the payment is deliberately trivially small for a normal user, it presents a barrier to a mass-spammer. Funds sent to this wiki will be used to keep the wiki online (cost of domain name and hosting), and remaining funds will be used to support Bitcoin development.<br />
<br />
See [[CryptoPayment]] for more info.<br />
<br />
== Status ==<br />
<br />
{{#ifeq: {{{status}}} | todo | To move forward, you will need to send 0.003 BTC to [bitcoin:{{{addr}}} {{{addr}}}]. }}<br />
<br />
{{#ifeq: {{{status}}} | done | Thank you for your support! }}<br />
<br />
{{#ifeq: {{{status}}} | nologin | You'll need to login to know your status. }}</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Template:CryptoPayment&diff=45191Template:CryptoPayment2014-03-22T03:57:55Z<p>Wtogami: </p>
<hr />
<div>Cryptopayment is the wiki's automated anti-spam protection mechanism. A small one-time Bitcoin payment is required before a user is allowed to edit or create pages. While the payment is deliberately trivially small for a normal user, it presents a barrier to a mass-spammer. Funds sent to this wiki will be used to keep the wiki online (cost of domain name and hosting), and remaining funds will be used to support Bitcoin development.<br />
<br />
See [[BitcoinPayment]] for more info.<br />
<br />
== Status ==<br />
<br />
{{#ifeq: {{{status}}} | todo | To move forward, you will need to send 0.003 BTC to [bitcoin:{{{addr}}} {{{addr}}}]. }}<br />
<br />
{{#ifeq: {{{status}}} | done | Thank you for your support! }}<br />
<br />
{{#ifeq: {{{status}}} | nologin | You'll need to login to know your status. }}</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=CryptoPayment&diff=45190CryptoPayment2014-03-22T03:53:41Z<p>Wtogami: s/BitcoinPayment/CryptoPayment/</p>
<hr />
<div>'''CryptoPayment''' is a MediaWiki extension to limit spam, by requiring a small one-time bitcoin payment before a user is allowed to edit or create pages.<br />
<br />
While the payment is deliberately trivially small for a normal user, it presents a barrier to a mass-spammer. <br />
<br />
Funds sent to this wiki will be used to keep the wiki online (cost of domain name and hosting), and remaining funds will be used to support Bitcoin development.<br />
<br />
==Usage==<br />
<br />
In order to enable your user account to edit pages, log in and visit [[Special:CryptoPayment]], and you'll be given an address to which to send a small amount of bitcoins.<br />
<br />
Once you send the requested bitcoin amount to the address displayed and your payment is confirmed, your account will automatically be added to the [https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=trusted trusted group] and be afforded edit privileges.<br />
<br />
===Confirmations===<br />
<br />
Payments will be considered paid after it is confirmed in a Bitcoin block.<br />
<br />
== Code ==<br />
Source will be released after the backend interface to bitcoind is rewritten.<br />
<br />
==Uso (Español)==<br />
<br />
Si pagas tu acceso a la wiki en inglés (subdominio en.bitcoin.it/wiki) no podrás editar las páginas en Español. Para editar la wiki en Español (subdominio es.bitcoin.it/wiki/) el enlace a Especial:CryptoPayment es este https://es.bitcoin.it/wiki/Especial:CryptoPayment<br />
<br />
==Questions or comments?==<br />
<br />
If you have questions, comments or a support request, please post in the [https://bitcointalk.org/index.php?board=168.0 Bitcoin Wiki Support forum]. We also have a chatroom at [http://webchat.freenode.net/?channels=#bitcoin-wiki #bitcoin-wiki on freenode IRC]. Please ask your question and be prepared to stick around for a few hours before you get a response.</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=CryptoPayment&diff=45186CryptoPayment2014-03-22T03:40:34Z<p>Wtogami: Wtogami moved page BitcoinPayment to CryptoPayment: Renamed anti-spam plugin</p>
<hr />
<div>'''BitcoinPayment''' is a MediaWiki extension to limit spam, by requiring a small one-time bitcoin payment before a user is allowed to edit or create pages.<br />
<br />
While the payment is deliberately trivially small for a normal user, it presents a barrier to a mass-spammer. <br />
<br />
Funds sent to this wiki will be used to keep the wiki online (cost of domain name and hosting), and remaining funds will be donated to the [https://www.bitcoinfoundation.org/ Bitcoin Foundation]. <br />
<br />
==Usage==<br />
<br />
In order to enable your user account to edit pages, log in and visit [[Special:BitcoinPayment]], and you'll be given an address to which to send a small amount of bitcoins.<br />
<br />
Once you send the requested bitcoin amount to the address displayed and your payment is confirmed, your account will automatically be added to the [https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=trusted trusted group] and be afforded edit privileges.<br />
<br />
===Confirmations===<br />
<br />
Payments require the customary 6 blocks to confirm. However, if you send from MtGox, and don't choose the ''open transaction'' option, confirmation is instant (since the wiki receiving wallet is also MtGox).<br />
<br />
<br />
== Code ==<br />
https://github.com/MtGox/BitcoinPayment<br />
<br />
==Uso (Español)==<br />
<br />
Si pagas tu acceso a la wiki en inglés (subdominio en.bitcoin.it/wiki) no podrás editar las páginas en Español. Para editar la wiki en Español (subdominio es.bitcoin.it/wiki/) el enlace a Especial:BitcoinPayment es este https://es.bitcoin.it/wiki/Especial:BitcoinPayment<br />
<br />
==Questions or comments?==<br />
<br />
If you have questions or would like help with the process, drop by on [http://webchat.freenode.net/?channels=#bitcoin-wiki #bitcoin-wiki on freenode IRC]. Notice that the channel is not very active, so be prepared to stick around for a few hours before you get a response.</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=BitcoinPayment&diff=45187BitcoinPayment2014-03-22T03:40:34Z<p>Wtogami: Wtogami moved page BitcoinPayment to CryptoPayment: Renamed anti-spam plugin</p>
<hr />
<div>#REDIRECT [[CryptoPayment]]</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Talk:CryptoPayment&diff=45188Talk:CryptoPayment2014-03-22T03:40:34Z<p>Wtogami: Wtogami moved page Talk:BitcoinPayment to Talk:CryptoPayment: Renamed anti-spam plugin</p>
<hr />
<div>==Amount reduction==<br />
<br />
As the value of BC rose, I propose to reduce the amount.<br />
<br />
0.01BTC is a day's salary in certain countries. And why are you waiting for 6 confirmations if this measure is really only a spam barrier?<br />
21:15, 22 April 2013 (GMT)<br />
<br />
:: This was made back when the price of BTC was in the low two digits. :) Yes payment amount could be reduced, but then you'd have to pay 0.0005 BTC fee for sending < 0.01. <br />
:: Also, 6 conf is required since this uses the MtGox payment processing API, which requires 6 conf. Not really worth it to special-case it. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 13:47, 30 April 2013 (GMT)<br />
<br />
:: To this day, the editing fee is worth 5€ or 5.5$. I already contacted MagicalTux, and posted on Bitcointalk.org (got flamed btw) while BTC was around $100, and I see that the problem is not yet answered. Thanks you MagicalTux for preventing this wiki to gain content and active users ! --[[User:Twix|Twix]] ([[User talk:Twix|talk]]) 22:59, 19 November 2013 (GMT)<br />
<br />
== Require payment for new user creation ==<br />
<br />
I believe that a payment is required on each new user creation, not just in order to gain edit powers.<br />
Currently a new spam user is created every few minutes, and the [[Special:RecentChanges|Recent Changes]] page has become completely spammed.<br />
<br />
[[User:Ripper234|Ripper234]] ([[User talk:Ripper234|talk]]) 10:54, 30 April 2013 (GMT)<br />
<br />
:: Payment is only required to activate edit privileges, hence the flood of spam users. but it's not a bad idea to have it be required for user creation too, to avoid that spam. The problem is that it'd require more development, and mtux doesn't really have time to do this for the wiki right now. <br />
:: In the meantime as a quick hack, you can just filter the recent changes list to exclude everything from the User namespace. [https://en.bitcoin.it/w/index.php?namespace=2&invert=1&title=Special%3ARecentChanges try this]. It's not perfect, since it also excludes user page edits... but it's good. :) [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 13:44, 30 April 2013 (GMT)<br />
<br />
== Informing new users ==<br />
<br />
It's not very clear right now that people need to visit this page to learn how to contribute. I didn't find out until I was reading through some questions on StackExchange, saw somebody someone ask why he couldn't edit.<br />
<br />
I know there's a line on the front page in font-size 10 saying "Anti-spam protection from BitcoinPayment", but people unfamliar with BitcoinPayment will not notice that. When they don't see an edit button they're likely to assume that you either need to wait for manual approval or that you need to know the right people within the community.<br />
<br />
It's been ages since I tried to write code for MediaWiki, so I don't know if on of the following suggestions is possible:<br />
<br />
* don't hide the edit link, but instead redirect the user to this page for instructions<br />
* next to the "Show source" link, show "Want to contribute?"<br />
<br />
Or this solution, which doesn't require code:<br />
* put a text like "If you want to contribute, please read these instructions" in a very prominent place on the landing page.<br />
<br />
<br />
: You're completely right, I was thinking the same thing for a long time. I don't know how to implement it - I just asked it on [http://webapps.stackexchange.com/questions/44319/can-a-mediawiki-moderator-put-a-system-message-for-each-new-user webapps Stackexchange]. If you know of a good way to implement that without having access to the backened/php, let us know. [[User:Ripper234|Ripper234]] ([[User talk:Ripper234|talk]]) 15:44, 17 May 2013 (GMT)<br />
<br />
:: We have edited the "no permission" message to point to BitcoinPayment. Also note that the login screen has had the prominent orange banner mentioning the requirement for BitcoinPayment all this time, also. I suppose "ideally" any user who is not trusted should get a persistent banner in the header or something, but that requires editing on the backend. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 03:47, 24 May 2013 (GMT)<br />
<br />
::: Can we change "View Source" to "Edit" so new users actually get to the explanation screen? --[[User:Luke-jr|Luke-jr]] ([[User talk:Luke-jr|talk]]) 04:55, 25 May 2013 (GMT)</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Talk:BitcoinPayment&diff=45189Talk:BitcoinPayment2014-03-22T03:40:34Z<p>Wtogami: Wtogami moved page Talk:BitcoinPayment to Talk:CryptoPayment: Renamed anti-spam plugin</p>
<hr />
<div>#REDIRECT [[Talk:CryptoPayment]]</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Bitparking&diff=35835Bitparking2013-03-01T19:42:24Z<p>Wtogami: </p>
<hr />
<div>A [[currency exchange]] allowing the trading between bitcoins (BTC) and other digital currencies include [[Namecoin]] (NMC) and ixcoin (IXC). Bitparking also operates a Namecoin mining pool.<br />
<br />
==History==<br />
<br />
Bitparking launched its BTC/NMC exchange on June 03, 2011<ref>[http://bitcointalk.org/index.php?topic=11694.0 Announcing Bitparking Namecoin Exchange!!]</ref>. Bitparking previously had exchanges for ixcoin and i0coin but they have since closed.<br />
<br />
==See Also==<br />
<br />
* [http://bitparking.com/pool Bitparking NMC mining pool] website<br />
<br />
==External Links==<br />
<br />
* [https://ltcexchange.bitparking.com Bitparking BTC/LTC] Bitcoin/Litecoin Exchange, See: [https://bitcointalk.org/index.php?topic=96917.0 Bitcointalk Discussion]<br />
* [http://exchange.bitparking.com Bitparking BTC/NMC] Bitcoin/Namecoin Exchange<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Exchanges]]</div>Wtogamihttps://tests.bitcoin.it/w/index.php?title=Bitparking&diff=35834Bitparking2013-03-01T19:42:03Z<p>Wtogami: </p>
<hr />
<div>A [[currency exchange]] allowing the trading between bitcoins (BTC) and other digital currencies include [[Namecoin]] (NMC) and ixcoin (IXC). Bitparking also operates a Namecoin mining pool.<br />
<br />
==History==<br />
<br />
Bitparking launched its BTC/NMC exchange on June 03, 2011<ref>[http://bitcointalk.org/index.php?topic=11694.0 Announcing Bitparking Namecoin Exchange!!]</ref>. Bitparking previously had exchanges for ixcoin and i0coin but they have since closed.<br />
<br />
==See Also==<br />
<br />
* [http://bitparking.com/pool Bitparking NMC mining pool] website<br />
<br />
==External Links==<br />
<br />
* [http://exchange.bitparking.com Bitparking BTC/NMC] Bitcoin/Namecoin Exchange, See: [https://bitcointalk.org/index.php?topic=96917.0 Bitcointalk Discussion]<br />
* [https://ltcexchange.bitparking.com Bitparking BTC/LTC] Bitcoin/Litecoin Exchange<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Exchanges]]</div>Wtogami