黑彩平台改单步骤

About kexplus.com

kexplus.com is dedicated to help Bitcoin to develop in a sustainable way.

Who owns kexplus.com?

Beginning

1
icon

Satoshi Nakamoto and Martti Malmi

kexplus.com was originally registered and owned by Bitcoin's first two developers, and . When Nakamoto left the project, he gave ownership of the domain to additional people, separate from the Bitcoin developers, to spread responsibility and prevent any one person or group from easily gaining control over the Bitcoin project.

2011-2012

2
icon

Bitcoin Core

From 2011 to 2013, the site was primarily used for releasing new versions of the software now called Bitcoin Core. In 2013, the site was redesigned, adding numerous pages, listing additional Bitcoin software, and creating the translation system.

2014

3
icon

Developer documentation was added in 2014

黑彩平台改单步骤Updates, fixes, suggestions and improvements from members of the community are welcome.

Today

4
icon

Site is an independent open source project

Today the site is an independent open source project with contributors from around the world. Final publication authority is held by the co-owners, but all regular activity is organized through the public pull request process and managed by the site co-maintainers.

kexplus.com is not Bitcoin's official website. Just like nobody owns the email technology, nobody owns the Bitcoin network. As such, nobody can speak with authority in the name of Bitcoin.

Then... who controls Bitcoin?

黑彩平台改单步骤Bitcoin is controlled by all Bitcoin users around the world. Developers are improving the software but they can't force a change in the rules of the Bitcoin protocol because all users are free to choose what software they use. In order to stay compatible with each other, all users need to use software complying with the same rules. Bitcoin can only work decently with a complete consensus between all users. Therefore, all users and developers have strong incentives to adopt and protect this consensus.

Mission

  • Inform users to protect them from common mistakes.
  • Give an accurate description of Bitcoin properties, potential uses and limitations.
  • Display transparent alerts and events regarding the Bitcoin network.
  • Invite talented humans to help with Bitcoin development at many levels.
  • Provide visibility to the large scale Bitcoin ecosystem.
  • Improve Bitcoin worldwide accessibility with internationalization.
  • Remain a neutral informative resource about Bitcoin.

Help us

You can report any problem or help to improve kexplus.com on GitHub by opening an issue or a pull request in English. When submitting a pull request, please take required time to discuss your changes and adapt your work. You can help with translations by joining a team on Transifex. Please don't ask for promotion for your personal business or website, except for special cases like conferences. Many thanks to all contributors who are spending time improving kexplus.com!

Maintenance

Website maintainer

Wallet maintainer

Sponsorship

2014 - 2015

2018

Translation

Ar Vicco
Russian

Simon Alexander Hinterreiter
German

Jacob Burenstam
Swedish

Péter Kemenczés
Hungarian

Matija Mazi
Slovenian

Mihai Onosie
Romanian

Bo?tjan Pirnar
Slovenian

Luigigiuseppe Prosperi
Italian

Thomas Pryds
Danish

Pavle Djordjevic
Serbian

Service Contributors

Browser testing

Repository hosting

Translation tools

Continuous integration

Inactive Contributors

Documentation writing

Domain Owners

Co-Owner

Co-Owner

Contributors on GitHub

(1587)
(1380)
(511)
(317)
(159)
(115)
(68)
(60)
(59)
(50)
(38)
(26)
(22)
(22)
(20)
(20)
(19)
(19)
(17)
(15)
(15)
(14)
(14)
(14)
(12)
(12)
(12)
(11)
(9)
(9)
(9)
(9)
(8)
(8)
(8)
(8)
(8)
(8)
(8)
(7)
(7)
(7)
(7)
(7)
(7)
(7)
(7)
(6)
(6)
(6)
(6)
(6)
(6)
(6)
(6)
(6)
(5)
(5)
(5)
(5)
(5)
(4)
(4)
(4)
(4)
(4)
(4)
(4)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)