sendfrom sends from an account, not an address.  Accounts are just internal ledgers in your wallet.  They do not map to addresses.

The standard Satoshi client cannot send from a specific address.  You need this:  https://bitcointalk.org/index.php?topic=24784

Nope.  2^16 = 65536 .

If the rest of the network has 11.6 TH, and you have 11.6 TH, you have 50%.  If you go up to 23.2 TH, you'd have 67%.

I don't know why it's letting you do that; I'm pretty sure you're not supposed to.

If you want a server and GUI at the same time, run bitcoin-qt with -server .

Yes, that's the current situation, but the whole thread is about trying to make 0-confirmation transactions safe even for high value irreversible exchanges.  There COULD be a demand for those if it was safe to do.

I'm just saying it doesn't work because it's still vulnerable to essentially the same attacks.

He can if he's also the miner: Purchase goods with zero confirmations; try to mine a double-spend; usually end up getting the goods for a fair price, but occasionally successfully solve the next block and get the entire forfeited amount back as fees.

This is also still open to Finney attacks: mine until he solves a block (including the conflicting transaction); purchase goods with zero confirmations; then release the block.  This succeeds unless someone else solves a block between making the payment and the delivery of goods.

Bitcoin is the joke.

We're just not sure who the joke's on yet. 

I support this.  It's a good idea even outside double-spend-confiscation.



The node is not guaranteed to be on the same LAN after being restored.  for instance, a laptop may be carried over to the IT department for a restore.

Also: are unconfirmed txes actually stored and sent to new nodes after the initial flooding?  I seem to recall that if you're not on the net at the time of the initial broadcast you won't hear about it until you see it in a block.

It is possible for people create non-fraudulent double-spends.  A common case: if they forgot to include a sufficient fee and the transaction goes into limbo, they can resend it with a fee.  Under this proposal there's a small chance they could lose the entire balance if a miner who considers the no-fee transaction to be valid and then mines them both.  Evil miners could even hoard such transactions hoping for the opportunity to confiscate a large fee.

Or another: they send a transaction while their LAN is disconnected from the network (another machine on their LAN sees it); they restore from backups; their restored client doesn't show the transaction so they resend it; when the LAN reconnects to the internet both transactions are transmitted and then confiscated.

tl;dr: it takes (difficulty * 2³²) hashes to solve a block on average.

It's Berkeley instead of JSON, but why not just use the actual blockchain?

If your goals are to create something for widespread popular use, I suggest creating a standard on top of 802.11 ad-hoc mode.  This would give you:

Built in radios in most smartphones
economical battery use
Very high data rates / short bursts
The ability to both broadcast the blockchain and unicast requests for old blocks
Reasonable range as bidirectional ISM devices go
Quite good range (much better than you get with usual wifi usage) when blind-broadcasting the blockchain from a fixed station (IIRC you can use up to 2w total, and you won't hit the EIRP limits with an omni antenna)
Mature multiple-access and collision recovery implementation
No hardware development cost
The convenience of developing on top of IP

If your goals are to have a fun radio hacking project, carry on. 

You should place a Limit at 5.1 and a Stop at 4.9.

The limit order will be filled whenever buyers bid more than 5.1.  If there are only enough bids to take part of your order, only part will sell, but it will all be at 5.1.  If you're dealing with small amounts it will generally get filled completely since the whole market can't go over 5.1 until your order is filled.  In other words, your entire order will be filled at 5.1000 before the market hits 5.1001.

A Stop order means to liquidate immediately at market price.  When the price is crashing no one will be buying at 4.9 - so it has to accept lower bids in order to finish liquidating.  Trailing Stop works the same, except it automatically raises the liquidation price as the market rises.  IE, the Stop price will be higher, but the immediate liquidation in a down market will still require selling under the Stop price.

A related measure of velocity: https://en.bitcoin.it/wiki/Bitcoin_Days_Destroyed

I'd say it depends where you can find someone willing to rent you an RV for BTC.    There are lots of private owners who rent out so it's a possibility.

http://privatemotorhomerental.com/
http://www.1rvrentals.com/

It's the Bitcoin virus!  Don't spend it or else someone else will get it! 

You just might make it out of bat country in one piece.

Please send back pictures of some burning paper wallets for those of us who can't make it.  Don't forget to censor the keys. 

That part I encourage you to do.    But realize that if you're just looking for a wild party you're better off in Vegas.

If you go to Burning Man, don't be a tourist; participate in creating an alternative culture.

They have about as much in common as an industrial meth lab has with a bunch of hippie pot farmers.  There are probably some dealers who bridge both communities, but no, they are not like-minded individuals.

I think you're looking for a rave.

In Burning Man, one of the core principles is to create a city-scale money-free gift economy for a week at a time.  Advertising money there, even alternative money, is not going to be taken well.   Selling T-shirts will make you look like fools.