I hope this is not the case, and it doesn't make sense.  If you're receiving blocks complete with all transactions and you have addresses in your POST queue for monitortx why would you go out of your way to filter results based on the wallet?  It's an extra step to reduce functionality.

And who's to say the 3rd party is any better at securing their servers?  You just don't know.  

The only time you can actually be demonstrably more secure by using a 3rd party is if the 3rd party provides an SLA (Service Level Agreement) that you can legally enforce in your jurisdiction wherein they agree to become liable for your losses if they screw up, only then is the risk transferred and you don't need to know if they have security flaws.

Not sure how competent we are at that, but we'll give it a shot.

If anyone else reading this thread wants to help with testing, we will gladly throw you some bitcoins to make it worth you while.

Well it's the entire pull request we where thinking of (i.e. push based notification for transactions and blocks, plus generic getblock).  So anyone who contributes to the finalizing of this pull request, once it's actually integrated with the client.

After some additional consideration we are not offering this bounty for a solution that is not integrated with bitcoind.  The goal is to get the feature we want and promote it for inclusion in the client so the community gets the benefit as well without the need for other tools.

However we would definitely pay at least a partial bounty to an interim solution that is client integrated, but not necessarily this complete set. Such as pull based equivalents, or the ability to check arbitrary addresses for payments.

 

We will pay top dollar for experienced bitcoin developers that can help us implement a number of features we have planned. Pay commensurate with experience. If you are a core bitcoin developer, or significant contributor we will given you highest consideration. We will consider a small team as well.

We are not actually looking to make alterations to bitcoind, but we would like to have 1 or more programmers on the team who are intimately familiar with bitcoin.  

Familiarity with unix development is also a requirement.

Experience with any of the following are big plusses: Ruby/Rails, EC2/AWS, Javascript/jQuery, qt, X Code / mac dev, iOS dev, OpenSSL, GNUPG, unix system system security, and general crypto.

Local to Los Angeles is also a big plus.

This is serious full time or part time job offer (we can work with your seclude) for run of project (at least 2 months, a successful project could lead to longer term).

PM me if you are interested.

Thanks

What is the status/eta of this pull request?  Unless integration is eminent we'd be willing to offer a bounty to help accelerate it's release. We really need this feature, our current workaround involving multiple bitcoind instances, and relaunch rescan per user session is catastrophically cumbersome.

Thanks!

We need these features for our applications, so were are prepared to put our money where are mouth is.  We will pay a 25btc bounty for the integration of these features.  To be split between the key participants in making this patch a reality.

Try bitcoinlocator.

More information here:

https://bitcointalk.org/index.php?topic=30503.0

This is what we're working on now.

But trust is a harder problem.  Yelp doesn't improve the trust of brick and mortar stores, the bricks and the mortar do that.  The problem with web of trust is that you must understand what you're trusting.  With Public Key Infrastructure (pki) the web of trust is only Identity.  That is you can 'trust' that the key used to sign one document is indeed the key associated with a particular public key or the same key used to sign a different document, and to the degree that others have also signed the public key, they assert that the person is who he said he is.  This is not the same as saying that the person wouldn't steal from you.

As ebay has proven online reputation systems are difficult to build.  It's always easy to build up a lot of fake reputation, simply to do one scam after which you don't care if you get a single bad review.  We are working on designing a system that is weighted so that it takes many successful transactions to build reputation, but each bad transaction makes a huge negative impact.  We are optimistic that we have a good solution, but we still have a fair amount of work to do before it's ready for prime time.

Meanwhile use bitcoinlocator to trade in bitcoins face to face where trust and identity are much easier to deal with.

I agree we want it to be as easy as possible.  I think removing the captcha for remote authentication is a good idea, we'll look into doing that.  I think there is a way to game it with a self hosted openID server, but we'll see if we can't figure out the right way to implement it.

We want to keep usernames, because it reduces spam accounts, and it provides a way for users to address each other anonymously (features coming soon).


We'll look into Google Latitude.  Emailing people near expiration sound like a good idea.  Email isn't required though, so we still need to find a good average time.

Thanks for the input!

Thanks! Mobile app coming soon.  We're working on it now.

There is a problem in javascript where the contents of the pin info window are actually loaded faster then the the spinner graphic, and so the spinner overwrites the contents.  We are working on that problem right now, however we deployed a version that puts a slight delay in so that it should happen in the correct order.  We'll try to get this tightened up.  

We also made the window bigger by default to help with the scrollbar issue.

Thanks for the spelling fix, and thanks for all your notes!

We require a username and some remote authorization providers don't give one.  We just deployed a change so that if a username is available it will show up in the dialogue. When using a remote authorization the password is always optional. 

We also made links last for 6 weeks now.  This is just for the beta.  We'd love to get input as to the best length of time.  On the one hand you don't want to have to update it too often, on the other we don't what a bunch of pins on the map for people who've moved on, or aren't using the service anymore.

We'll look into making the links a little more clear.

Thanks for your input!

Also here's some information we posted about being an individual/brick and mortar exchange for profit:

https://www.bitcoinlocator.com/exchange.htm

With bitcoin anyone can be an currency exchange. That's why we created BitcoinLocator, so we could make it easier for people to find exchanges anywhere in the world.

Try out www.bitcoinlocator.com.  This is exactly what it's for.

We are already looking into Open Street Maps as a backup to the google maps API.  Along with massively distributed exchanges, it just seems like open source, and open standards are the right way to go for a distributed currency.

Awesome, much appreciated! We'll look into it too. Ping me if you find anything before we do.

Thanks

We are passionate about bitcoin!  Thank you so much for all the support in the first 24 hours already!

We want to be sure to represent every currency with accuracy and respect, so if your currency is not yet represented by bitcoinlocator then we want to know!  Post here or send me a private message and we will make your currency our top priority.  We arbitrarily picked the top 20 currencies as listed buy a few websites, but that doesn't necessarily represent the users of bitcoin.  Tell us which currencies we should add and we will!!

If you can, please link an accurate symbol too so that we can design a map pin that matches.

Thanks!

Currently added to the list and pending are:
Swedish Krona
Israeli New Sheqel