There has not yet been a single report of someone's account-to-account payment being delayed by Dwolla when paid using the cash balance from the sender's Dwolla account.  Every such account-to-account transfer that is entered gets processed instantaneously (i.e., within seconds).  

Now when I send a payment to someone else and I don't have enough funds in my Dwolla account so I instead click the source: "bank account", then the transfer will show the status as pending until Dwolla does an ACH pull from my bank (minimum 3 day delay.)  That is not Dwolla's fault, that is the ACH network on which Dwolla uses.

Now the recent change that Dwolla made was to block the ability to send payments to certain recipients until a checklist of requirements (i.e., 30 days since Dwolla first transferred funds from you account, verify to Dwolla your SSN, enable Hub page) is first completed.  But if there is no block,then the transfer is instant -- Dwolla does not delay the payment.

So please, if you have specific information that describes where Dwolla is delaying payments please share the details, otherwise you are spreading misleading information.

Arduino based project using a mini printer here:



 - http://learn.adafruit.com/mini-thermal-receipt-printer


Though this would only work if the paper was used to transfer / scan via paper for a short while, before the image disappears:

How does one take delivery then after exercising the option?

And either the same troll or another, .. flip?:
 - https://bitcointalk.org/index.php?action=profile;u=52804

Will this bet stay open until Tuesday or is Gingrich's pre-announcement of his announcement sufficient to close this bet?

 - http://betsofbitco.in/item?id=155

 - http://www.foxnews.com/politics/2012/04/25/gingrich-to-suspend-presidential-campaign-next-tuesday-sources-say

gpg: requesting key 30A2134D from hkp server keys.gnupg.net
gpg: key 30A2134D: public key "paulo_" imported

I am paulo_, and I operate BTCPHP.com.
gpg: Signature made Tue 24 Apr 2012 11:45:00 PM PDT using RSA key ID 30A2134D
gpg: Good signature from "paulo_"
Primary key fingerprint: 065E D859 2B2D 20D5 6C12  E80A 666D 9FB9 30A2 134D[/tt]

Very good, thank you!

So you are sayiing that when looking at the blockchain (e.g., using http://Blockchain.info ) you can see the transaction from Mt. Gox (based on the date and the amount) to your address, but then there is another transaction that occurred after where the funds have since been spent?


Which client?  Are you using passphrase encryption?


Bitcoin transactions are nonreversible so if the above scenario is what occurred (a transaction spent your coins and it wasn't you that spent them) then yes, the funds are gone.
 

Nobody can spend your coins unless they have access to your private keys stored in your wallet.  There are differing levels of protection, suitable for different requirements.  Of course, a paper wallet created offline using a bootable CD and an "air gap" to the network is one of the most secure methods, but that isn't convenient.    Adding passphrase encryption to your wallet is going to protect your wallet from the risk where your wallet.dat somehow gets into the wrong hands.    It won't protect you though if your system is compromised with spyware that contains keylogging software, for instance.  Running the Bitcoin client locally does have the dependency that your system is kept secure.

There are protections that will protect even against that risk, to some degree.  Mt. Gox, for instance, offers a Yubikey hardware device that is needed in order to login and withdraw from your account with them.  There are other solutions from other exchanges as well.  Even Blockchain offers an optional two-factor authentication method.

But if your coins were spent and you didn't do it, then the prudent course of action is to assume your system is compromised and proceed with an appropriate course of action from there.  If you still have other bitcoins stored, then backup the wallet and recover the funds elsewhere first.

Nice ... you have a website now:
 - http://bitfare.org

Because they don't know which block it will end up in, and if they waited until 1 confirmation it would no longer be an instant payout (which is the real attraction here,  along with knowing the "proof is in the blockchain" as far as being able to verify that there is no cheating).

The thing is, the player doesn't care which secret is used, they just want to verify that the secret that was supposed to be used when the wager was placed is the exact same one that truly was used in determining the result.

So currently the criteria that determines which secret to use is simply the date that the service first sees the transaction.  The reason that there is a new secret every day is that the secret is revealed only after one full day after the deadline has passed (e.g., the secret for wagers processed on the 10th of the month is kept secret until the end of the 11th of the month, and then revealed at the start of the 12th of the month.

There are two other variables that could help.  The address that the wager is being sent to, and the amount.  That's it though.

So one approach would be to have a different wager address for every day.  That's not very good for usability.   Even limiting that, like toggling between two addresses day-to-day, might be something to help with this situation, bit it wouldn't be ideal.

The other approach would be accommodate an optional signal indicating which secret is to be used by encoding that into the wager amount.   Take a list of secrets numbered sequentually, there is odd and even numbers.  Adding a Satoshi to the wager amount (e.g., a 0.1 wager would be 0.10000001) would require that when determining the result  the closest odd-numbered secret must be used.  Then the a 0.10000002 wager would require that the closest even-numbered secret is used.

Neither of these is useful to the person playing by manually doing a copy and paste of the wager address -- you don't want them to be thinking of time of day, etc.  But I foresee the day there is an iPad app, for example, acting as a gaming terminal with a local wallet.  This device provides a dead-simple user interface to the game.  The logic in that app would automatically handle whatever is necessary to eliminate the risk where it is ambiguous as to which secret should be used.   And I suppose, of the methods above, having a different address for each secret would be the most correct approach.  Since it is a piece of code determining which address to use it really doesn't matter that it changes day-to-day then.

So, there's the solution.  

Keep the existing list of addresses which are used when doing manual betting.   Those wagering manually extend trust that the service is not cheating on the end-of-day wagers.  Then for the the automated systems a set of addresses that are associated with each secret are created ahead of time.  If there are any wagers sent after the address expires then those wagers get returned.   Since the addresses are known well in advance, the device could start using the following day's address an hour or so earlier just to ensure to not get too close to the expiration to prevent submitting any bets that would get returned.

This issue regarding being able to specify which secret a bet is against probably isn't necessary to address right away.  A player can avoid the risk by simply not betting near when the time switch occurs.  But the site should consider making an API that will allow an automated gaming termine to send a calendar date + bet choice (e.g., under 48,000) request.  The response will be the return the hash of the secret that will be used for that day as well as the bitcoin address for that specific wager (e.g., for the under 48,000 bet) on that day.

Just an update:


 - http://freenetworkfoundation.org/?p=859

The domain is registered with a name, but the registrar doesn't verify names so that cannot be relied on.  The SSL cert is self-signed, so that isn't useful for verification either.  To confirm that you are the Paulo_ in the WoT, would you consider posting a message here, signed for verification?   e.g., something like "BTCPhp.com is owned and operated by me."?

Or that the 17 year old founder is now 18 and attending college in Australia.  Since you cannot serve two masters, operating bitcoin's second largest (by volume of funds transacted) business on the side is the one that had to get moved to have someone else take care of it.
 - http://twitter.com/#!/zhoutong/status/185745407064817664

Ah, ... perfect.  Two weeks expiration is fine then, IMO.

Some conversation about this topic here:

 - http://bitcointalk.org/index.php?topic=74615.0


There is a market for something like that, I would bet.

Maybe that means incremental?

Like the equivalent of a partial fill perhaps?   E.g., you were willing to buy 10 BTC at $5 but there were only 4 sold at that price before the price bounced back up?  And you are then left with a 6 BTC buy order at $5?

If trades at an exchange rate at CampBX dropped below your bid then it should have executed in full, but that's easy enough to see:
 - http://bitcoincharts.com/charts/cbxUSD#rg5ztgSzm1g10zm2g25

For solo mining or p2p mining.  For normal use as a wallet, it should be fine.

There are so few users of it though, if there was some oddball problem in there somehow, it wouldn't be noticed by that many.
 - http://bitcoinstatus.rowit.co.uk/versions.html

Latest "killer" project.

This would be an app in the mobile gambling category.

Needed is a mobile app (native for Android) or mobile-enabled web app (which works on Android, iPhone, iPad, Windows mobiles, etc.) that acts as a front end to http://www.SatoshiDice.com  (that one, specifically, for now.  Eventually the app would be used against some other nearly identical instant-payout blockchain wagering).

Holds a wallet, preferably running transactions through Blockchain's host.

Probably would not ever get approved for App Store for U.S. as this is probably considered an gambling app, so maybe the web app would offer a higher user base potential.

Unfortunately, this service appears to no longer function (no response to @PayBitBack tweets.

There is another tipping service now.  It has a wallet that you fund before you tip, but from there it works in a similar fashion.
 - http://www.BTCTip.com

Are you looking to build a business, to help an open source project, or just apply bitcoin to solve a problem?

Also, what type of skills?  e.g., a C++ dev that can debug threading issues is different from a front-end web dev w/ UX skills that can crank out a great new site.  And interests?   Finance (e.g., trading bots), Mobile, Embedded, etc.?

Any reason you won't use a more recent release?