Topic: Chrome Bitcoin Extension Bounty(260 and more BTC were paid.) - page 6. (Read 29620 times)

No effect.

Hmmm, should be:

(Wrench) -> Options -> Under the Hood -> Content Settings -> Notifications

I think they're enabled by default though, so that might not be the problem.

How do I turn on notification?

Thanks for your comments, everyone. I'll try to respond to most of them here...

I guess I didn't read this thoroughly the first time. You might need to turn on notifications. I know this can be annoying, but it is a first test version.


Yes, it is pretty dirty. It was the easiest thing I could think of that I can access with javascript the way Chrome processes the dialog menu click. I'll have to mess around and see if it's even possible to access something like the address= parameter you suggest.



Yes, but it is limited by Chrome. It's for storing options specific to the extension. If you want to avoid entering a password, you can't exactly use the JSON-RPC. If you want it to use a service like mybitcoin.com, you will have to enter a password and a captcha every time you do something. Any time you enter input it could be stored or forwarded to a dozen other sites and you'd never know. I do intend to open up the source, though.

I'm going to make some updates and see if I can fix the send dialog so it doesn't have to use notifications. Then I'll post the source, ugly as it is.

HTML 5 defines 'data attributes' for this use:

http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#embedding-custom-non-visible-data-with-the-data-*-attributes

So this could be:



This has the advantage of validating with HTML 5 validators.

For now the client have no ability to show the send window after JSON-RPC request. I guess it shouldn't have such an option at all because JSON-RPC is for silent operations by design. To prevent exploits and malicious operations the code of the extension should be reviewed before installing or updating. The problem is that chrome extensions update silently if no additional permissions were requested since the last update. At least (most of) the extensions are written on javascript so they are open source by definition. Well, they may be obfuscated and packed though.

Why? Network connection, name and password is already enough to steal money by bitcoin transaction.

Ideally it would not give the name and password to plugin. Plugin can ask GUI client by JSON for payment dialog. The client could show a window with the amount and address, which would be passed from plugin by JSON.

Anyway, I think that using some URI is preferable than slow HTML parsing.

To give it (or to exploit) an opportunity to steal a wallet.dat file?

Bitcoin Extension Options
JSON-RPC Server: http://
Username:
Password:


The plugin can read files in the user's system? I would like to avoid entering any password entering and addresses

Browsers ignore tags which are unknown. If they did not do this  to give an error then the new versions of html never began to be used.

You suggested a new tag. So W3C should add it to the HTML5 standard immediately!

This is a dirty hack, although this does not seem as it. It will ruin the caching of images, at least.

I suggest use a new tag:





or



for built-in into plugin "pay" buttion

No, it does not send bitcoins for me too. Chrome 8.

Does your balance show up when you click the Bitcoin browser button?
Make sure you're right-clicking after hilighting.
You may also need to reload the page the address is on if you had it opened before you installed.

I highlighted a bitcoin address and click on send bitcoin but nothing happens.

The balance of my bitcoin wallet shows though.

I'll update my above post to include this as well.

https://chrome.google.com/extensions/detail/hhbhfoohbnjkdcndbhjlicijccioklea

I wouldn't mind testing it.

I actually sort of gathered that from some of your last few posts in this thread. What I've done is still fairly useful even if it doesn't meet your requirements. A stand-alone client in the form of a browser extension is a tad more complicated. The best way I can think to do it would be to interface with something like mybitcoin.com, which I'll look into. I just don't have the resources to host that end of it. You don't owe me a bounty, at least until I deliver on that.

Would you mind helping me test this extension? I just learned how to build them yesterday, so this one is a big step toward stuff like you're looking for.

What I have in mind doesn't require the use of a bitcoin daemon. It should be self-contained as a bitcoin client.

Simplicity is the driving goal here. It should be so easy that grandmas can use it.

Sorry that I didn't emphasize it strongly enough. So I will pay once the chrome extension is available for installation or it is available as source code. I will pledge more bitcoins for the development of a self-contained browser extension for bitcoin.

Ok, posting a handful of screenshots here. I'm going to run through a couple more tests and then put it up on google and post the link in here. I'd like to take some time and tidy up the code a bit, but if everyone's that desperate to look at it, I'll give you what I've got. Functionality is fairly basic at this point, but here's what it does:

- Makes a Bitcoin Icon in the browser you can click to check your balance.
- You will need to right-click that Icon and go to options to set it up.
- Allows you to hilight the text of a bitcoin address and right-click to choose a "Send Bitcoins" option, which opens a notification and lets you enter an amount to send.
- The same "Send Bitcoins" option shows up when you right-click an image. This works a little different. If someone sets up a payment button using a graphic that says something like "Buy Now for 100 BTC!", they can set it up to work with the extension by loading the graphic like this:


Placing the amount before the | and the address after. The amount can be left blank, but you have to include the | before the address. The amount will then automatically get filled in as seen in screenshot 1.

You have to have Bitcoin running and in -server mode (which means setting up the RPC user and password options in bitcoin.conf). And don't forget to set the extension options or the other functions won't work. I've only tested this on two XP machines running Chrome 7 and Bitcoin 0.3.14 and one of them I had to specify the rpc login credentials on the command line for some reason.

That's about the gist of it. Pretty basic so far, but it should be expandable to include things like:
- SSL
- Generate and paste a new receive address
- Periodically check balance and alert changes
- mybitcoin.com interface
- Use mtgox.com data to show balance in USD

I'll post back later with the google URL to install it.

https://chrome.google.com/extensions/detail/hhbhfoohbnjkdcndbhjlicijccioklea