What happened??

OKPAY

YA!  I just noticed that too.

Damn you BTC-E.

websocket seems up.

or maybe not.

seem to be just reloading an stale order book.

I've used Citibank, Wells Fargo and Bank of America personal accounts to wire funds to Bitcoins Direct.  The Fees range between 18 (BofA) to 30(WF) for same day wire transfer (we are both in the United State).  Actual same day delivery time is usually with in the hour (in my experience).

For Citibank and Bank of America you can create a wire payee and send online.  (Some banks will also need to verbally confirm the payee you are adding the first time by a phone call to avoid fraud.  The Bank will not leave a message if they call you and get voice mail if you do not state your name on your out going message.  I've delayed some initial transfers due to this).  The wire just silently failed and I had to follow up with the bank to find out what happened.     

For Wells Fargo personal accounts there is no online function.  I actually had to go into the bank to add Bitcoins Direct to send a wire.   I prefer Wells Fargo for their p2p payment function (only between personal account).

Also, as all other clients have commented here, I've always received nothing but prompt payment and outstanding customer service the many times I've purchased coin from Bitcoins Direct.  Thank you.

Love it!

Very catchy tune.

Don't know anything about these new US exchanges.

https://bitbox.mx
(I've traded with him personally)

https://beta.kraken.com/

https://www.crypto.st/

updated original post with Board Member Jon Matonis public comments.

https://bitcointalk.org/index.php?topic=194295.msg2016417#msg2016417

Has Charlie Shrem or Roger Ver commented anywhere yet?

Thx.

And before that he was what???

I wouldn't call peter venessess powerful.  Who is he again??

Evidently gox didn't release anything. That is the problem.

The Linux Foundation history of litigation has been made else where.

https://gist.github.com/gavinandresen/5509626

I'm not familiar with the history, but it can't be beneficial.

so you are fucking LOADED!  What's your point.  Ha!

i. Gavin Andresen, Bitcoin Developer residing or doing business in Amherst, MA, USA.
https://gist.github.com/gavinandresen/5509626

ii. Peter Vessenes, CEO of CoinLab and residing or doing business in Bainbridge Island, WA, USA.
http://coinlab.com/status

iii. Charles Shrem, CEO of BitInstant residing or doing business in Brooklyn, NY, USA.


iv. Roger Ver, CEO of MemoryDealers residing or doing business in Santa Clara, CA, USA.
https://109.201.133.65/index.php?topic=193922.msg2013531#msg2013531

v. Patrick Murck, Principal at Engage Legal, PLLC residing or doing business in Washington, DC, USA.


vi. Mark Karpeles, CEO of MtGox.com and residing or doing business in Tokyo, Japan.
https://mtgox.com/pdf/20130503_coinlab_lawsuit.pdf

vii. Satoshi Nakamoto, at satoshin@gmx.com, author of the white paper “Bitcoin: A Peer-to-Peer Electronic Cash System” published on http://bitcoin.org and owner of the PGP Public Key with fingerprint: 5EC948A1.
(founding member-- REALLY??)  how so??  - anyway not comment from him either.

UPDATE:
Jon Matonis - Board Member (from Twitter)
https://twitter.com/jonmatonis

jonmatonis 3 May
@BTCBROKER I think you mean CoinLab. As I am on the board & the foundation is still considering the matter, I will have to defer commenting.
Jon Matonis ‏@jonmatonis 3 May
@BTCBROKER Statement for now is that foundation will take steps that are in the best interest of bitcoin, not individual board members.

UDATE: posting by Jon Matonis on the foundation blog.
https://bitcoinfoundation.org/blog/?p=180

Did I miss anything (else).

+1
Multiple high value transactions his PayPal and bank transfers for my bitcoin.
Never a problem.

bitcoin-24  please send out a press release or contact me and I'll do it for you.  This is good news people need to hear about.

thx.

These should be questions for Peter Vessenes not Gavin.  He just happens to have the forethought to post here.

I don't think Peter has weighed in.

Gavin,

Is the board meeting open to all members?

It is on the agenda?

I'm a member and this is the first I'm hearing about it.

Thx.

The better question is What is YOUR plan to help support the foundation to this end.  The foundation is all of us, (or any of you who choose to join).  It will be through our efforts collectively that we will further support the widespread adoption and acceptance of bitcoin.

Remember when you print a finger there are three fingers pointing back at you.

If you are not part of the solution then you are probably part of the problem.

This is a very important discussion.

Glad we are having it.

I expect to hear more clarity at the conference about the bitcoin's goals and plans and learn more about ways I can participate.

Is this a new feature of blockhain.info. 

I've been getting these email from blockchain.info for the past few days.

Never seen one before.


Authorize log-in attempt

An attempt to login to your blockchain.info wallet was made from an unknown browser. Please confirm the following details are correct:

Time: 2013-04-27 16:09:36
IP Address: 121.54.58.138 (Philippines)
User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31



Delivered-To: myemail@gmail.com
Received: by 10.229.150.196 with SMTP id z4csp2704qcv;
        Sat, 27 Apr 2013 09:09:29 -0700 (PDT)
X-Received: by 10.68.65.134 with SMTP id x6mr52995969pbs.219.1367078969410;
        Sat, 27 Apr 2013 09:09:29 -0700 (PDT)
Return-Path: <bounces+318715-b6c4-myeamil=gmail.com@mail.blockchain.info>
Received: from o1.mail.blockchain.info (o1.mail.blockchain.info. [198.21.6.174])
        by mx.google.com with SMTP id tk6si13447587pbc.16.2013.04.27.09.09.28
        for <myemail@gmail.com>;
        Sat, 27 Apr 2013 09:09:29 -0700 (PDT)
Received-SPF: pass (google.com: domain of bounces+318715-b6c4-myemail=gmail.com@mail.blockchain.info designates 198.21.6.174 as permitted sender) client-ip=198.21.6.174;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of bounces+318715-b6c4-fdajkddcek=gmail.com@mail.blockchain.info designates 198.21.6.174 as permitted sender) smtp.mail=bounces+318715-b6c4-fdajkddcek=gmail.com@mail.blockchain.info;
       dkim=pass header.i=@sendgrid.me
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=
   content-type:mime-version:content-transfer-encoding:from:to
   :subject; s=smtpapi; bh=FcGT7ee4N8yKhJ0b5SF3G7gSPqs=; b=D2DIimbS
   +V03gq+k5D85HddkJ9gpURqV6/UujrqTrDO6FzmLYyG5l/Fdf8+d030SZIkvglPk
   Vlq6/9WTm/45aHVPZqEcc3q12W3lR2RFlTg5mMI6AL2lzG+1ZxVutgFq7y9+dL6I
   WRBot2B7Mz57MCEAcG3OGy0oYbPc2DgQ+xw=
Received: by 10.42.83.27 with SMTP id filter-116.15633.517BF8385
        Sat, 27 Apr 2013 16:09:28 +0000 (UTC)
Received: from MzE4NzE1 (unknown [82.145.55.247])
   by mi16.sendgrid.net (SG) with HTTP id 517bf838.60e1.bec97e
   for <fdajkddcek@gmail.com>; Sat, 27 Apr 2013 11:09:28 -0500 (CST)
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: wallet@blockchain.info
To: fdajkddcek@gmail.com
Subject: Authorize log-in attempt
Message-ID: <1367078968.6662252349225259@filter-116>
Date: Sat, 27 Apr 2013 16:09:28 +0000 (UTC)
X-SG-EID: pozTKVS8Lu50fMG2jTIRpA1VjetYZa15tAklDGgdfiP+jd+Wu4qjYT7Nz3cXXfT2lUKl1/UcYy18DewQ4OfYa+eukgsHDdH7rHvZyisJrV90ypVP/RwYxPX4YTes0CEEchJj/itgAkHswGavS73bgQ==