Look at the bottom of the page:

https://online.1stnb.com/LoginAdv.aspx

Better start asking around to see if the banks you use have any upcoming changes to their international wire policy in the pipeline.

With an extended public key there is no need for the sender to request a pre-defined number of outputs at the negotiation phase. When a recipient gives a sender a BIP32 key that sender now has the ability to create as many as they will need, forever, with no need for additional negotiation.

What you're talking about is not Bitcoin, and will never be accepted into Bitcoin.

If you want this, make a new cryptocurrency with the feature and see how many people you can convince to switch.

Altcoin discussion belongs in the altcoin discussion area.

Sure, as long as such banks continue to exist.

I'm tempted to create a bet as to whether or not any banks will offer individuals the ability to send funds out of the US via international six months from now.

Do you know what would be the exact opposite of surprising?

If the space between $158.49 and $199.53 took between 30.3 and 34.5 days to cross.

It wouldn't be surprising because based on price history to date*, that's how much time it takes on average to span a tenth of a decade.



*past results are no guarantee of future performance.

Western Union is very expensive compared to wires, and comes with far lower limits on the amount you can transfer.

Any excuse, not matter how flimsy, to pump scamcoin will do, right?

It's still an inexcusably-high amount of metadata to leak.

The alternative is that the forum gives out some token that can be used to find the other person to exchange pubkeys directly, without the forum being able to record the information itself.

For example, your HD wallet client can have Torchat functionality built in, and you post the address in your profile such that anyone wanting to get payment information can point their client to that address.

Substitute Bitmessage, or any other eavesdropping-resistant P2P messaging system, for Torchat as desired.

It just takes a bit more thought to architect the negotiation protocol, but it's not all that complicated. For extra credit, you design the extended pubkey request and exchange protocol to be transport-independent and add a plugin feature to the clients such that you can do it over Torchat, Bitmessage, IRC, I2P, Freenet, or any protocol you can write a transport plugin for.

I track the trend differently - I keep a spreadsheet wherein I track the weekly weighted prices and calculate an average of all the changes.

So far that gives an average weekly change of 6.4%, including the data from all the way back to the first day Mt Gox opened.

Using that gives about $300 by the end of the year, with $1000 being reached slightly under a year from now.

Related:

http://bitcoinism.blogspot.com/2013/06/i-love-smell-of-crony-capitalism-in.html

Here's the same thing happening at a small, state-licenced bank:

https://online.1stnb.com/LoginAdv.aspx
The key here is "Due to recent regulatory changes." This isn't a Chase issue. I bet that we're going to hear more of this happening in the next few days/weeks. Before long, it's not going to be possible for the average person to wire dollars outside the country.

If you're serious the best place to get $30 worth of bitcoins is LocalBitcoins. Just find somebody in your area and pay cash.

Newbies who ask to pay with PayPal are generally suspected of being scammers.

Specifically, for cases such as an employer paying employees. BIP32 solves this problem nicely.

Also, I think AnonyMint had it backwards. Splitting outputs is fine; there are plenty of ways do it safely. Recombining small balances into large balances without sacrificing privacy is the hard part, and that's where CoinJoin can help.

Why would anyone want to give the forum operators the ability to track all their transactions? That's terrible for privacy. I'm never going to give someone an extended public key except for an entity I want to receive payments from.

I saw something similar happen at a local, state-licensed bank:


If you want to know what happens next, study the recent history of Argentina.

I feel like I should be able to refute that, but I don't want to.

The convention I would use is, "Here's an extended public key. I am going to watch the first address defined in this sequence for an incoming payment. After I see it, I'm going to start watching the second address. After I see a payment there I'm going to start watching the third address, etc."

A client can do several things to limit the amount of addresses they need to scan.

First of all there's no reason for a forum to let a single person request 10000 extended public keys.

The forum has it's BIP32 seed and generates a subnode for each registered member.

Each member can go to their account and find the extended public key for them to donate with. They don't ever get a new one because the one they are assigned lets them generate all the deposit addresses they will ever need.

The forum's client has a small lookahead window, like 5 or 10. Whenever a new incoming payments are received the window increments accordingly.

Old addresses are checked for new balances at exponentially-increasing intervals until some cutoff time after which they are only checked manually.

It's awesome that you've got a new video out, even though the thread doesn't belong in this section of the forum.