What would happen to your exchange if Google decided that it wouldn't authenticate your users any more?
While Google does provides the application, any web site can use it to authenticate. In theory, the application does not need to contact Google per use and is unaware of which web site the application is being used with. More information: http://en.wikipedia.org/wiki/Google_AuthenticatorNow that clears it up. Every day I learn something new and useful. Good work! |
|
|
|
|
Interesting approach. What would happen to your exchange if Google decided that it wouldn't authenticate your users any more?
|
|
|
|
|
MultiBit has a bulk address generation feature that may help you here.
|
|
|
|
Recently I've been receiving emails from various lobbying groups asking for donations. Invariably they all require some kind of credit card transaction or PayPal and so on. I've starting taking the time to respond to each using a fairly standard form letter that I thought I'd share here in case others find it useful. Perhaps if enough of us respond using variations of this letter adjusted to our own preferences it may start to have an impact. I've tried to follow the rules laid out by the wiki article on press releases, let me know where I've introduced fail. ... Hi, I recently received an email from your group asking for donations. I noticed that you are wishing to promote "a more just economy" and to that end I would like to draw your attention to Bitcoin. Bitcoin provides an additional donation strategy that has the following features: + You do not have to pay any fees to receive bitcoins + You do not have to register with anyone to send or receive them + You can exchange bitcoins for most currencies (certainly USD, EUR and GBP) any time or day of the week (24/7) + You can receive donations offline (i.e. you can print the address on paper handouts if required) + You can receive donations from anyone, anywhere in the world (Bitcoin is global) + You are immune from boycotts by payment processors + All the software required to operate them is free and open source + Bitcoin itself promotes a fair and just economy by offering people an internet currency not under anyone's control (no government, no corporation, just a collaborative global effort) In order to receive payments via Bitcoin you need only do 2 things (overall time to complete is under 5 minutes): 1) Download a free and open source program to generate a Bitcoin address (think of it as like an email address to receive donations) 2) Post that Bitcoin address on the same page as your other payment options An example of how it can be used is shown here: http://gary-rowe.com/agilestack/2012/01/09/how-to-accept-bitcoins-on-your-blog-with-no-code/You can find out more about Bitcoin at the main site here: http://bitcoin.orgIf you decide you want to try it out. Then see here for the main client choices: http://bitcoin.org/clients.html. I recommend MultiBit for your requirements. If you have any further questions, I would be happy to answer them for you. Kinds regards Gary |
|
|
|
As of this moment, the latest version of Multibit (v0.3.4) has 50% coverage in Chinese. All the core functionality is covered, but new features (such as exchange ticker integration) and some wallet related text is still in need of updating. We anticipate getting these translations updated soon so feel free to promote MultiBit worldwide  |
|
|
|
Hey man don't jack my thread, I'm ego tripping here! Haha. Do you have a main announcement thread we can discuss your project in?
Apologies - no jacking intended. Just responding to some others concerns about getting this kind of functionality available on other platforms. It's too early for a proper announcement thread, probably next week would be better. Best of luck with the project - it's good to see this kind of work taking place. Keep it up :-) |
|
|
|
Looks like a useful application and a welcome addition to the Bitcoin ecosystem. Well done! On a side note, if anyone is interested in a multi-platform, multi-exchange version of this kind of functionality you may want to keep an eye on MultiBit in the next couple of months. We're currently working in collaboration with Xeiam on a project called XChange which provides a Java library (free, open source under MIT license) that is able to talk to multiple exchanges (both Bitcoin and fiat) and provide a simple developer API. Developers should think of it like JDBC for exchanges (no messing about with individual APIs and protocols like FIX, just a single clean API). Implementations in other mainstream languages are also in the pipeline but we're focusing on Java to get it off the ground. XChange is currently at alpha release (so no big announcement yet) and has the following feature set working in the v0.0.1 branch: MtGox: * get current bitcoin prices (both one-off and streaming over SocketIO) * log in and get account info (subject to providing credentials) Intersango: * get current bitcoin prices (one-off) Other popular Bitcoin exchanges will follow shortly, and the XChange library will be included into MultiBit to support seamless trading operations. This is currently scheduled for end of Q2 2012. For more information, see here: https://github.com/timmolter/XChange/wikiThe main developers are Tim Molter (Xeiam) - lead developer Gary Rowe (MultiBit) - collaborator |
|
|
|
Essentially they did nothing, but for somereason they are all over the news. Welcome to the media of today! :-) Bank noisily does something mildly interesting - NEWS! Bunch of people quietly change the world - tumbleweed Of course, it could just be a slow news day... |
|
|
|
|
Remember that "they caused a revolution" is just news rhetoric to attract attention. They haven't copied Bitcoin - they've just provided a mobile client to their standard account payment systems in a very limited form. An evolutionary development at best, certainly not revolutionary.
|
|
|
|
|
It's not just you. The BBC have run several articles (frequently positive) about Bitcoin (particularly when the exchange rate went through the roof) but, as always, the moment it ceases to have a wow factor it fizzles out. They are probably not introducing it because it would defocus the article.
Reading the comments, most folks seem to be treating the announcement with "Meh" which is typical. The service itself is very limited and given the severe regulatory environment that banks operate under is unlikely to grow into something international which is where Bitcoin wins. It does serve a useful purpose, though, which is to soften up the mainstream to the idea of digital cash which is definitely welcome news.
|
|
|
|
The interface to the brokerage client would need such functions as:
-Inform about the bitcoin balance in a wallet (this would allow automated brokerage whenever the amount of bitcoins in the wallet reaches lower or upper limits)
-Inform about Buy/Sell orders of the user (assuming that the user initiates such orders in the client)
-Payment of bitcoin through the client to a bitcoin buyer in the case that the user want to sell bitcoins
-Inform about bitcoin receiving address generated in the client in the case that the user want to buy bitcoins
-Inform about received bitcoins in the case that the user wants to buy bitcoins
-The whole interface to the brokerage client needs to be encrypted for security reasons Without hijacking the Multibit thread, I'd just like to clarify the purpose of the XChange project. It's intended to act as a common API for any exchange (Bitcoin, fiat, centralised, distributed etc) so that applications can easily use any of them, in combination if required. To that end pretty much all of the above functions are going to be supported. For all operations, a brokerage is considered to be the same as an exchange. When it comes to depositing fiat into the exchange there is a potential issue. XChange won't support this directly (it's not a payment gateway for MasterCard for example) but it would facilitate instructing the exchange to make, say, an authorised debit against a registered bank account if the exchange supported that through it's API. As mentioned, XChange is Java only at the moment, but if anyone wants to start up a sister project, or work within the same repo, using a different language then they are certainly welcome. Just PM me for more details. Finally, by providing a standard API XChange may be able to assist developers of new exchanges by showing them what needs to be available and how to implement it securely, and have a suitable test client all ready to go so they can verify that it all works as intended. |
|
|
|
Is it possible to offer third-party extensions in BIP21? For example, having a bitcoin client support a field like "req-satoshi-detailedamount" or "armory-lowfee", without coordination between the client developers? I can't speak for the whole developer community, but if an arbitrary set of fields was included into the URI with a "req-" prefix and my client didn't understand them it would, correctly, reject the URI. Over use, or un-coordinated use, of this approach would give rise to a lot of broken URIs among clients and an inconsistent user experience. Overall, if you have a field that you think is important enough to have on your URI, submit it to the developer community for widespread acceptance (and review). That's what the BIP is for. |
|
|
|
|
Small correction - it's MultiBit Merchant and is intended to be an open source (MIT license) eCommerce platform for Bitcoin.
|
|
|
|
|
My understanding is that BIP 21 reduces the level of processing of the Bitcoin URI by both humans and machines and makes the overall URI scheme simpler.
To have single representation of an amount fixed as decimal BTCs (decimal biased) means that people can easily read the value as presented in their client in a raw state (e.g. a browser) without having to do any specialised thinking. For example, a member of the general public attempting to decode "amount=500X0Y6" would fail utterly. Equally, machine processing is made simple because there will nearly always be a decimal in place, and further decimal positions (e.g. a move from 8dp to 10dp or whatever) won't invalidate earlier URIs.
The purpose of a URI is to provide a unique resource identifier, and good design typically means that one URI binds to one resource (although others can temporarily point to the same one). In this case the resource is interpreted as a payment request.
The notation for the "required parameter" was going to change from "req:" to "req-" in line with RFC 3986 Section 2.2 "Reserved Characters" but the edits may not have made it to the wiki yet.
|
|
|
|
|
Since it has such a low power consumption and is essentially able to run quietly in the background, it could run bitcoind and act as a full node in the network. That would benefit everyone.
|
|
|
|
This "single click to send bitcoins" is implemented in MultiBit (v0.3+) across Mac, Windows and Linux for all mainstream browsers. It also supports "drag swatch to send bitcoins" as well, just for good measure. You can download it here: http://multibit.org. |
|
|
|
|
Hi Mitchell,
Thanks for stepping up. I would see your efforts working in harmony with the LoveBitcoins.org site, but that's up to you.
I can provide development support if you need it. I specialise in web applications, usually in Java. Feel free to PM me.
Kind regards,
Gary
|
|
|
|
|
Show Posts
