Vertpunk is a fork of Coinpunk modified for use on the Vertcoin network.
Vertpunk is experimental beta software based on beta software upstream. Be Forewarned. Use at your own risk.
Like Coinpunk, Vertpunk is aimed at developers, power users, and sysadmins interested in running their own web-based Vertcoin wallet.
Vertpunk is also used to power the open source web-based Vertcoin wallet service at vtc.li.
Vertpunk requires the vertcoin-watchony version of vertcoind to function.
See the Install Guide
Like Coinpunk, Vertcoin is also intended for advanced users only. Kyle says it best:
If you've never worked on your own server before, and don't know how to do things like backup your database, I strongly recommend using a desktop client or hosted wallet provider like coinpunk.com instead. Coinpunk tries to be simple as possible, but like Gitlab, it does require a lot of knowledge to be run properly.
Vertpunk would not be possible without Coinpunk. Please see below to see how you can help with the upstream project.
Coinpunk updated to the latest version of SJCL, which has fixed a bug that caused PBKDF2 hashes to be inconsistent from the standard.
This has been fixed, but it will not work with wallets created before this commit. Please be mindful of this when upgrading Coinpunk if you are already running it in production.
Also, we are switching to a release-based system, so you should checkout one of the tagged versions instead of using master. The 0.3 series will not contain any breaking changes, but the 0.4 releases will. So please use a 0.3 release if you are using Coinpunk in production.
Run your own Bitcoin wallet service.
Coinpunk is a web application that allows anyone to run their own self-hosted Bitcoin wallet service that is accessible from your web browser anywhere in the world. It's free, open source, and you can install it on your server right now.
Coinpunk is aimed at developers, power users, and sysadmins interested in running their own web-based Bitcoin wallet.
Coinpunk is also used to power coinpunk.com, the first fully open source web-based wallet service.
The latest version is a major rewrite that uses hybrid-wallets: encryption is done in the browser via a client-side application, which can be run separately from the server. This makes it much harder for hackers to steal Bitcoins by breaking into servers.
Coinpunk is in beta. It is set to testnet by default, and it is recommended that only developers and testers only use it at this time (especially in production).
- Fast, lightweight, efficient
- Responsive design - works well on mobile devices
- Easily create new accounts
- Send and receive bitcoins
- Detailed reports on transactions
- Ability to create and name new receive addresses ("Website Donations", "Bake Sale", etc)
- Built with Node.js and HTML5
- Standards compliant, easy to upgrade - Uses bitcoind via the JSON RPC
See the Install Guide, or the OSX Install Guide.
If you've never worked on your own server before, and don't know how to do things like backup your database, I strongly recommend using a desktop client or hosted wallet provider like coinpunk.com instead. Coinpunk tries to be simple as possible, but like Gitlab, it does require a lot of knowledge to be run properly.
Kyle Drake. Illustration by Kyle Wilson.
Click here to see the contributor list.
Donations help me to keep working on Coinpunk and keep it free and open source, without having to worry about income. Any amount is really helpful! Thank you so much.
The Coinpunk donation Bitcoin address is 1MHbxLgsgFQyvWkW1qiZs1HaXxU4S4LuWH
Also if you are planning on running Coinpunk on a VPS, you can use this link to sign up for DigitalOcean and it gives us a referral bonus we can use to pay for the servers.
Again, thank you. ❤️
Help us build! We're in beta right now and seeking help to find bugs. If you are interested in contributing, jump in! Anyone is welcome to send pull requests. Issue reports are good too, but pull requests are much better. Here's how you do it:
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Write the code, and tests to confirm it works
- Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request
See docs/H4XX0RZ.md.