Hi,
will this Frontend also work for coin daemons of PoS Coins like Hyper or Audiocoin ?
Regards
Topic: [ANNOUNCE] +Coin Web UI for Bitcoin and its forks. (Read 6264 times)
Old thread is old, but +Coin is still alive and working.
Has just been updated to Bootstrap 3 so it looks a little nicer (thanks to X-NicON)
Has just been updated to Bootstrap 3 so it looks a little nicer (thanks to X-NicON)
I've updated it and submitted a pull request for a bunch of updates.
It's poorly written, probably buggy, and you could possibly loose all your coins, but hey, it works for me
I highly recommend using is with a secure web server (https://) you have to log into so that the data transfers are encrypted. Otherwise your passphrase for the wallet would be transmitted in plain text.
It's poorly written, probably buggy, and you could possibly loose all your coins, but hey, it works for me
I highly recommend using is with a secure web server (https://) you have to log into so that the data transfers are encrypted. Otherwise your passphrase for the wallet would be transmitted in plain text.
The point was originally to run it on a personal web server, (e.g. namecoin used to only have namecoind on windows, so webui = much better). I don't have too much time myself right now, but it shouldn't be too hard for someone to implement a login system.
ALSO - I donated 0.01 to tip4commit for -Coin. So anyone who adds new features or fixes them will get a small payment ( the small number in the tip4commit image below )
I've updated it and submitted a pull request for a bunch of updates.
It's poorly written, probably buggy, and you could possibly loose all your coins, but hey, it works for me
I highly recommend using is with a secure web server (https://) you have to log into so that the data transfers are encrypted. Otherwise your passphrase for the wallet would be transmitted in plain text.
It's poorly written, probably buggy, and you could possibly loose all your coins, but hey, it works for me
I highly recommend using is with a secure web server (https://) you have to log into so that the data transfers are encrypted. Otherwise your passphrase for the wallet would be transmitted in plain text.
as promised a while ago i am sending you my source code with the changes for addressbook, many wallets and so on..
please integrate it in github. i am only working with subversion..
download: http://www.ltc-charts.com/wallet-admin-clean.zip
i hope its useful for somebody
please integrate it in github. i am only working with subversion..
download: http://www.ltc-charts.com/wallet-admin-clean.zip
i hope its useful for somebody
to make a small donation, but your work has any further updates. I do not know if the creator intent to leave it as is or will have to update it over time.
Lacking the creation of btc addresses, address book, maybe the link blockchain when you send btc ... in short, the work is really well done I love it and I would like
Lacking the creation of btc addresses, address book, maybe the link blockchain when you send btc ... in short, the work is really well done I love it and I would like
Hey this is slick.
I've added support to enter wallet passphrase.
Why are you using the GET method for the send form? This will post your rpc user name and password to the https access_log. Not a good Idea. The Method every time you call the rpc through a FORM should be "POST". You should open up all the file and change all the METHOD from GET to POST then change all of the $_GET to $_POST.
it's pretty simple.
add the following under "amount" input in index.php
then in send.php about line 16 (just after the first "try" open bracket{
the number "1" in the second value it the timeout so your wallet is decrypted for one second which in plenty of time to send.
Also if you are accessing your bitcoind from a second box over a public network be sure you bitcoin.conf file includes
otherwise your rpc username and password will be sent in clear text each time you make a call.
I've added support to enter wallet passphrase.
Why are you using the GET method for the send form? This will post your rpc user name and password to the https access_log. Not a good Idea. The Method every time you call the rpc through a FORM should be "POST". You should open up all the file and change all the METHOD from GET to POST then change all of the $_GET to $_POST.
it's pretty simple.
add the following under "amount" input in index.php
Code:
then in send.php about line 16 (just after the first "try" open bracket{
Code:
$nmc->walletpassphrase($_POST['walletpassphrase'], 1);
the number "1" in the second value it the timeout so your wallet is decrypted for one second which in plenty of time to send.
Also if you are accessing your bitcoind from a second box over a public network be sure you bitcoin.conf file includes
Code:
rpcssl=1
otherwise your rpc username and password will be sent in clear text each time you make a call.
There are no updates? Too bad it was a good GUI for bitcoind!
For now it works, I haven't had any time to work on it, and nobody has reported any problems so far really.
I'm also interested on it! Can you upload it somewhere? ( maybe on git )
My version is already on github, check the first post. If you mean xchrix's version, he hasn't replied since I've been contacting him for months, so I'm unable to grab the source from him.
Does it support encrypted wallets? Without that whole thing isn't viable, I'm not putting unencrypted wallet on live server...
If I have time, I'll add encryption support to +Coin sometime soon.
I'm also interested on it! Can you upload it somewhere? ( maybe on git )
It is on git: https://github.com/Someguy123/-Coin/branches , but last change is 6 months ago.
hey
i am using your great +coin for a while now and i have modified it a little bit
- added addressbook
- select from which account to send coins from
- getinfo output on startpage
- support for multiple wallets!
- https connection to wallets
is someone interested in this features?
Does it support encrypted wallets? Without that whole thing isn't viable, I'm not putting unencrypted wallet on live server...i am using your great +coin for a while now and i have modified it a little bit
- added addressbook
- select from which account to send coins from
- getinfo output on startpage
- support for multiple wallets!
- https connection to wallets
is someone interested in this features?
Did you publish your version of code?
I'm also interested on it! Can you upload it somewhere? ( maybe on git )
There are no updates? Too bad it was a good GUI for bitcoind!
i am more the subversion guy i will just send the source to someguy123 so he can upload it
i will just send the source to someguy123 so he can upload it 
Yep, and if you put it up on github you could send a pull request through to someguy123 ...
hey
i am using your great +coin for a while now and i have modified it a little bit
- added addressbook
- select from which account to send coins from
- getinfo output on startpage
- support for multiple wallets!
- https connection to wallets
is someone interested in this features?
i am using your great +coin for a while now and i have modified it a little bit
- added addressbook
- select from which account to send coins from
- getinfo output on startpage
- support for multiple wallets!
- https connection to wallets
is someone interested in this features?
Looks good so far :-) Just a couple of can't connect errors, but it should be because of the bitcoin client preoccupied with synchronizing.
Yeah, unfortunately while bitcoin is downloading blocks, the RPC is ridiculously slow, and I can't really do anything about that. 
Looks good so far :-) Just a couple of can't connect errors, but it should be because of the bitcoin client preoccupied with synchronizing.
Watching...
Any news on this?
Yeah, thanks to twmz I guess I'll just go all public domain with this code.I'm planning on CC since that allows most things, but I have a new issue... I'm unsure what the licensing issues I'll have if I throw it under CC considering:
- Bootstrap is Apache v2
- and JSONRPC-PHP is GPL v2
Can anyone good with licenses explain to me whether I'm allowed to release my code under Creative Commons, and whatever steps I have to do to ensure I'm not breaking their licenses?
First, please don't release software under Creative Commons. Creative Commons wasn't designed for software (it's designed for content: photos, books, music, etc). See http://wiki.creativecommons.org/Frequently_Asked_Questions#Can_I_apply_a_Creative_Commons_license_to_software.3F
Second, IANAL, but if you use a GPL's library like JSONRPC-PHP and if you choose to distribute your application to others then your code must also be GPL (or public domain, since that means you are relinquishing your copyright altogether). If this isn't something you want to be forced to do, then don't use the JSONRPC-PHP library (JSON RPC is not that complex... you could probably just whip up a couple wrapper functions yourself if you had the desire). Apache v2, on the other hand, is a pretty restriction-less license. In fact, it may be one of the licenses you might want to concider instead of using Creative Commons as it basically says "do whatever you want, just don't blame me, and don't remove my copyright notices, etc").
I'm going to be releasing the first version on my github in the next few hours under public domain
Been watching out for something along these lines.
Taking the first step is half the journey ... good stuff.
Taking the first step is half the journey ... good stuff.
Any news on this?
I'm planning on CC since that allows most things, but I have a new issue... I'm unsure what the licensing issues I'll have if I throw it under CC considering:
- Bootstrap is Apache v2
- and JSONRPC-PHP is GPL v2
Can anyone good with licenses explain to me whether I'm allowed to release my code under Creative Commons, and whatever steps I have to do to ensure I'm not breaking their licenses?
First, please don't release software under Creative Commons. Creative Commons wasn't designed for software (it's designed for content: photos, books, music, etc). See http://wiki.creativecommons.org/Frequently_Asked_Questions#Can_I_apply_a_Creative_Commons_license_to_software.3F
Second, IANAL, but if you use a GPL's library like JSONRPC-PHP and if you choose to distribute your application to others then your code must also be GPL (or public domain, since that means you are relinquishing your copyright altogether). If this isn't something you want to be forced to do, then don't use the JSONRPC-PHP library (JSON RPC is not that complex... you could probably just whip up a couple wrapper functions yourself if you had the desire). Apache v2, on the other hand, is a pretty restriction-less license. In fact, it may be one of the licenses you might want to concider instead of using Creative Commons as it basically says "do whatever you want, just don't blame me, and don't remove my copyright notices, etc").
So... Anyone want to help with my question above ^ so that I can finally release it?
Some quick questions:
Appart from that, cool project even if you use it on your local machine with XAMPP (or linux)
- Does the bitcoind need to run on the same server as the php files?
- Does the wallet need to be in the same place?
Appart from that, cool project even if you use it on your local machine with XAMPP (or linux)
1. No, it uses host/port, it uses the JSONRPC, so it would allow connecting to say yourdomain.com on 8333 if it's forwarded, and identify using its bitcoind username and password.
2. Same as above, it uses the JSONRPC, so the bitcoind server you connect to is responsible for the wallet.
After seeing this, I must say I would really like to have a look at this.
Since parts of the code could even be used as a codebase for other implementations, the less restrictive the license is (within your limits), the most people and projects will be able to reuse it for their own implementations. So Unlicense would fit into that criteria IMHO.
Watching this!
Since parts of the code could even be used as a codebase for other implementations, the less restrictive the license is (within your limits), the most people and projects will be able to reuse it for their own implementations. So Unlicense would fit into that criteria IMHO.
Watching this!
I'm planning on CC since that allows most things, but I have a new issue... I'm unsure what the licensing issues I'll have if I throw it under CC considering:
- Bootstrap is Apache v2
- and JSONRPC-PHP is GPL v2
Can anyone good with licenses explain to me whether I'm allowed to release my code under Creative Commons, and whatever steps I have to do to ensure I'm not breaking their licenses?
Some quick questions:
Appart from that, cool project even if you use it on your local machine with XAMPP (or linux)
- Does the bitcoind need to run on the same server as the php files?
- Does the wallet need to be in the same place?
Appart from that, cool project even if you use it on your local machine with XAMPP (or linux)
After seeing this, I must say I would really like to have a look at this.
Since parts of the code could even be used as a codebase for other implementations, the less restrictive the license is (within your limits), the most people and projects will be able to reuse it for their own implementations. So Unlicense would fit into that criteria IMHO.
Watching this!
Since parts of the code could even be used as a codebase for other implementations, the less restrictive the license is (within your limits), the most people and projects will be able to reuse it for their own implementations. So Unlicense would fit into that criteria IMHO.
Watching this!
good job, do you have any experience with ruby on rails, im about to deploy a beta version of and app today and i would like to have you on the team.
No not really, though I could probably pick up ruby quite easily if I needed to...I'm mostly just PHP.
good job, do you have any experience with ruby on rails, im about to deploy a beta version of and app today and i would like to have you on the team.
uhh, how secure is it?
Not very.Throw on apache Auth-Basic though, and it should be good enough, plus if you hide it in /derpy/derpy/derpy/nobody/will/ever/guess/ on your web server, it's unlikely someone would stumble upon it
If you had fail2ban, auth-basic would be good enough since they get an IP ban after 3 attempts anyway.
uhh, how secure is it?
I've been working on the +Coin webUI for a while, my main purpose was originally for a namecoin management system, though I lacked time and effort for it, eventually I needed a webUI for bitcoind due to bitcoin-qt's instability while using p2pool (0.5.2), so I continued my work on it.
(Psst. If you submit a pull request and accept it, you'll get some BTC if your github is linked to tip4commit)
So far, it currently has the following features working:
OLD VERSION: http://i55.tinypic.com/24mc1go.png
CURRENT VERSION:
Version 0.01 Alpha - Released under UNLICENSE (public domain) and is available on my Github: https://github.com/Someguy123/-Coin
(Psst. If you submit a pull request and accept it, you'll get some BTC if your github is linked to tip4commit)
So far, it currently has the following features working:
- Listing transactions
- Sending coins
- Compatibility with any *coind that uses the bitcoinRPC (inc. Litecoin, Namecoin, Feathercoin)
- In standard PHP, so it's easy to deploy onto a normal webserver (Great for managing coind's on your VPS/Dedi)
- Colour coded send/recieves, and colour coded confirmations
- A really nice bootstrap interface
- The ability to list how much BTC/whatever is in an account, and then to list the addresses contained in the account.
- Able to display confirmed/unconfirmed balance (All transactions are "confirmed" at 6 in +Coin, including generated ones. I haven't bothered to separate it yet.)
OLD VERSION: http://i55.tinypic.com/24mc1go.png
CURRENT VERSION:
Version 0.01 Alpha - Released under UNLICENSE (public domain) and is available on my Github: https://github.com/Someguy123/-Coin
Jump to: