Bitcoin Forum
May 02, 2024, 07:19:21 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 [6] 7 8 9 10 »
101  Bitcoin / Development & Technical Discussion / Re: Buyer-Seller Escrow Transactions (with or without 3rd-party) on: April 07, 2012, 02:42:25 AM
The asymmetry is that Alice is the only one with anything at risk.  Maybe Bob is just bored and wants to laugh about people losing money, so he starts advertising stuff he doesn't actually have.  When the person commits money, he delays a bit, then broadcasts LAZY_ALICE.  Worst case (for Bob), he doesn't get anything and gets his laugh.  Best-case, Alice can't figure out how to DISPUTE, and Bob actually gets some money!  Sweet game! 

Alice and Bob sign a contract, Bob is to ship good X, Alice is to provide money. Bob holds 'Lazy_Alice', and Alice holds 'Dispute'. Bob ships the item and forwards the tracking number to Alice. Alice uses 'Dispute' to get most of her money back. What does Bob do?

I think you're wrong about Alice being the one taking all the risk. The symmetry lies in the fact that neither party is really getting any lower risk by such a deal, unless there's an asymmetry between 'Dispute' and 'Lazy_Alice' which would dump all the risk on one party or the other.

Trying to manage dispute resolution between two mutually untrusting parties without a third party is impossible. In the 2-of-3 case, as long as Alice and Bob are really both honest, they can sign for each other and finish the transaction. In the case that either Alice or Bob are dishonest, they cannot agree without arbitration (the money ends up in limbo). Given that the contract is only used where at least one party assumes the other may be dishonest, a 2-of-3 is absolutely required to resolve things if that does turn out to be the case.
102  Bitcoin / Bitcoin Discussion / Re: On the glorification of Bitcoin on: April 06, 2012, 01:39:14 AM
Even the regular dollar symbol seems to be based on a "serpent coiled around a cross", which pharmacies sometimes display. If I start digging around on the Net, I'm sure to find all kinds of occult/religious/pagan history surrounding it.

How about a Tetris-like "B" in bright colours? I know it's a bit Google, but Google is popular, whereas shiny bullion-like designs remind of dodgy poker sites.

http://en.wikipedia.org/wiki/Rod_of_Asclepius

Sometimes also the similar Caduceus is used, both are Greek. "Pagan" is a christian word for "people we're going to torture and make into second-class citizens of christiandom".

The BTC symbol reminds me of the "beli" symbol used on One Piece.



The "staff" going through it isn't any more meaningful than the rod going through a treble (G) clef symbol.


Only the "double staff" that makes the U in U$ has any particular meaning on a currency that I'm aware of.
103  Bitcoin / Bitcoin Discussion / Re: The Free Market, a Real World Test Case on: April 06, 2012, 01:06:19 AM
A file trading site? Which one are you talking about there?

coindl

Of course those industries most tyrannized by the State will be the first adopters of a currency which permits free individuals to remove themselves from that burden.

What's your point?

True, but my point is that besides a couple of exchanges, hardly anyone who can call themselves a businessperson has done anything decent with BTC yet. The more BTC gets a reputation as a "drugs gambling and porn" currency, the less the chances of anybody taking it seriously.

Sure, I believe people should have the freedom to decide to do whatever they want to do. However, I certainly wouldn't call drugs, gambling and porn anything close to the best things in life. If I say "let's go start a utopian society" I would hope your response wouldn't immediately be "Yes! Let's fill it with drugs, gambling and porn!".

It should be expected that Bitcoin will move along a curve of adoption - with happy, complacent status quo markets being at the end of that curve, and disrupted, alienated markets being at the beginning.

I think you have the totally wrong idea about economics. There's no such thing as a "complacent status quo" market. For the consumer a market might appear to be offering the same or more stuff for their dollar, for businessmen it means struggling continuously to make sure your business is efficient and competitive and still exists next year. The efficiency of the free market comes directly from being a few inches from sudden death at all times, and from intelligent businessmen figuring out better/cheaper ways to make it happen. As soon as a market settles into a "happy, complacent status quo" sort of phase, it's time to invest your money somewhere else.

The worst problem faced by economies and currencies with small market caps is wild price swings and fluctuations that occur when capital jumps into or out of the currency. Although the effect is much less with a large market cap, BTC is likely to face that sort of fluctuation until it becomes obsolete. Promoting as much slow, dedicated growth as possible, and discouraging rampant speculation can reduce the problem, but as soon as some idiot like Krugman mentions the word "bitcoin" it's right back to violent swings. Unfortunately, if it takes on a "straight up" kind of curve for a prolonged period, interest rates and RoI fall into the negatives, and the economy stops in favor of hoarding the currency. Fortunately, that is only likely to happen if some idiot exchange starts offering real, resellable options contracts rather than the current, less speculative strict forwards.

don't know about drugs, gambling is somewhat adopted still no big sites where anyone can gable with bitcoins. porn hasn't adopted Bitcoin at all

Silk Road, the largest economic usage of BTC, is about 99% drugs and 1% money laundering. "Gambling" didn't adopt bitcoin, bitcoin adopted gambling. Same with porn.
girls gone bitcoin

Regardless of whether big industries adopt it or not, the currency is what you can (directly) buy with it, and that list isn't terribly long.
104  Bitcoin / Bitcoin Discussion / Re: On the glorification of Bitcoin on: April 06, 2012, 12:02:23 AM
Well, more on topic, personally the only thing I would change about the bitcoin 'logo' is to clearly give it only one strike through the B rather than two. The double strike through the USD symbol is an accentuated "U", so that the design makes a "US". Conversely, there are no "U"s in bitcoin.
105  Bitcoin / Bitcoin Discussion / Re: The Free Market, a Real World Test Case on: April 05, 2012, 11:33:25 AM
Lol the great bitcoin economy indeed. The largest industry in BTC is drugs, followed by gambling, followed by porn, then a file trading site and a few people selling trinkets on bitmit. At least some of the banks are decent, not including MtGox.
106  Bitcoin / Development & Technical Discussion / Re: Bitcoin smartcard Point of Sale terminal on: April 05, 2012, 11:25:49 AM
For regular smart cards, maybe they could be paired with some type of online service that keeps an eye on merchants and perhaps validates transactions based on buying patterns.  At the very least, it would be nice to receive some type of statement at the end of the month to be able to detect fraud.  Otherwise, with nothing but the blockchain to go by, it would be basically impossible to know whether your grocer has a hacked POS terminal that is ripping you off.

If you have access to a desktop running bitcoind or other client, it should be trivial to get said client to track tx to/from your card address. Remembering which tx went where is another story, but at least you could have some idea.

Then on top of that add interfacing with the merchant's accounting system.  And besides magstripe and contact/contactless credit cards, you're competing with Paypal and Dwolla and that new Canadian Mint thing.  It's likely that none of those will cooperate to share hardware. Sad

Do paypal and dwolla have physical POS methods that don't rely on VISA or mastercard? Maybe I'm missing something. That canadian mint thing sounds like a citizen tracking collar to me. It'll be a disaster of human rights and a disaster of identity theft. I don't think Canada is really the ideal market for bitcoin anyway.
107  Bitcoin / Bitcoin Discussion / Re: On the glorification of Bitcoin on: April 05, 2012, 06:00:48 AM
In practice, many societies seem to strive for some kind of healthy middle ground, whereby the worst aspects of both are limited. There is usually some kind of framework to include things that don't "fit" the market model. For example: prisons, a public healthcare system, a road code, an education system, and so on. Some may argue that if societies simply enforce a "user pays" policy to everything, it'll be fine. But in many cases that attitude is demonstrably wrong. For example, a mentally ill criminal with no family or friends is stuck in an institution to protect all the die-hard capitalists on the outside. Who pays?

Your friendly torte insurance company. The problem isn't that society needs prisons and government goons to bash down your door and force you to pay for them. The problem is that prisons, as a "rehabilitation program", teach offenders to become career criminals rather than just petty offenders.

People go to prison out of a background of child abuse, and are then subjected to further abuse in prison, reinforcing the lesson that violence and dishonesty are the solution to their problems. Sure, there are problems where externalities aren't easily avoidable, but the solution is never to get a big group of assholes with guns and have them tell everyone what to do and steal money from everyone on an ongoing basis to pay for said activities.

The solution to keeping child molesters away from your children is not to administer TSA agents to molest your children legally at the airport, mall, school and so on.

Does wikipedia require a totalitarian tax collection agency to operate?
108  Bitcoin / Development & Technical Discussion / Re: Buyer-Seller Escrow Transactions (with or without 3rd-party) on: April 05, 2012, 05:43:00 AM
It's not so clear cut who pays for overhead fees.  If you consider credit cards, it's always been the seller.  If it's PayPal transfers, again it's the seller.  Why not here, too?

The seller, who passes those fees onto the consumer either by higher S&H or by higher prices overall.

In the case of Bitcoin, the network can be the third party.  That's what the 2-of-2 version is:  both parties agree on the terms (that only further agreement from both parties will be accepted) and the network holds it until they're ready for disbursement.  Of course, even with good intentions, the death of one party or HDD failure could lead to un-recoverable funds -- which is why I wouldn't recommend it for any substantial value.  But if you're purchasing something for under $100, I think it's acceptable (and third-parties may not want to deal with small tx, anyway).

I don't see how that solves anything. If Alice wants to buy something from Bob for 10BTC, and Alice doesn't trust Bob to deliver and Bob doesn't trust Alice to pay, how does "the network" decide if Bob has delivered or not to know whether to sent the money to Alice or Bob? If Alice is "lazy", then Bob might have to wait until the contract n-locktime expires to get his money, which might be a long time. Worst case if the tx can't be finished without both parties signing it, then if Alice is lazy Bob might never get his money, and if Bob is crooked then Alice can't get her money back.

I highly recommend third-parties, but I think it should be possible not to use them.  And people who use silk-road would probably agree with me (though I am making no formal endorsement of silk road or drugs in general:  just an example of where executing transactions between untrusted parties may be desirable without a third party).

Plus, the benefit of using 2-of-3 is that there's a lower threshold of trust needed for the third-party -- there is no risk that they take the bitcoins and run.  They'd have to collude with the one of the parties to do that.  All that matters is that they are impartial to the two parties involved.

If you've figured out some magical way to do escrow without a trusted third party to settle disputes, I'd love to hear it, but it seems technically impossible to me. As I mentioned the best you're likely to do is to lock the money up on the blockchain so your third party doesn't need to be trusted to hold it, just to release it to the deserving party. That's really not much better than what's possible now, although it might streamline things a bit.
109  Bitcoin / Development & Technical Discussion / Re: Buyer-Seller Escrow Transactions (with or without 3rd-party) on: April 05, 2012, 02:54:17 AM
Whatever overhead fees are incurred are on the buyer, who is asking for the service. I don't think it's possible to do escrow without a third party, at least not one which would be acceptable to both involved parties. The best you could do would be to store the deposited money to a "virtual address" on the blockchain so that your third party can't just steal the money (unless he's already in collaboration with the seller).

On the other hand, for a proxy-seller like bitmit it might make more sense to escrow the money to a proxy account so that the proxy service can collect their fees as well as guarantee their own buyers against seller abuse. Escrow can't work without at least one trusted third party anyway, which is why amazon is so successful, since customers know they can get their money back most of the time even with an unrated seller.
110  Other / Beginners & Help / Re: Block Chain Summary or Ledger or Balance on: April 05, 2012, 02:13:20 AM
After re-reading this thread more thoroughly, I came to some other conclusions.

1. Going forward bandwidth is likely to be as much of a problem as storage. A client working with summaries will still have to download all new transactions, and thus will be unsuitable for cellular internet connection.

2. If Bitcoin becomes ubiquitous there will probably be billions of used addresses, so summary storage will still requires tens of gigabytes.

...

4. Gains are likely not to be much above what pruning can do...

An estimate I made earlier:

Quote
-When you prune merkle trees, you still have to keep the block header, all of the merkle tree hashes, and the full tx of any tx that have any unspent txOuts, including all of the txIns, all of the scripts for the txIns, all of the txOuts (including spent txOuts) plus all of the scripts for the txOuts. Verifying tx still requires either a full pruned blockchain or that you trust centralized nodes to provide you with the correct merkle tree entries that you request.

-For the linked ledger system, you throw away all but the unspent txOuts plus the scripts for the unspent txOuts. All block headers older than a certain time can be discarded along with all of the merkle hashes and tx, and each client only needs to keep 4-5 weeks of blockchain and 3 ledgers (1 for an old seeding period, 1 backup, 1 current), of which 2 weeks of blockchain and 2 ledgers can be compressed since they're seldom if ever needed.

-If all unspent txOuts which have the same address are added together and condensed, that would reduce the size of a ledger by ~50% or more. This would also require using the full value of an acct as txIn, but that also reduces the size of txIns on the blockchain as a result.

2000MB * .035 = 70MB Per ledger
70MB * 2 = 140MB of ledgers that can be compressed
33MB (est weekly block size with reduced txIns) * 3 = 99MB uncompressed blockchain (maximum, varies)
66MB compressible blockchain (2wks historical for seeding)

70 + 99 = 169MB uncompressed
140 + 66 = 206MB compressible

I think your 500MB estimate for pruned merkle trees is overly optimistic. I'll believe it when I see it. Assuming you can compress data to 66% of original using zip or similar, with ledgers you'd only keep a maximum of about 305MB, and only 215MB for a lite client.

Condensing unspent txOuts into per-address balances and forcing full address value for txIns would reduce both network bandwidth incurred per tx and blockchain space by a modest amount. Making pubkeys easily reversible from addresses would eliminate the redundancy of publishing your pubkey along with the signature when spending, which would reduce per-tx bandwidth requirements a bit more.

On second look, 13 weeks total/2-3 weeks per client would probably be the most economical, which is easily less than 50% the size of a fully pruned blockchain with the current standard.

3. Rapidly dropping transaction history will limit what you can do with the Bitcoin system...

I don't see how this improves on the (future planned) status quo of full or pruned blockchains on servers, lightweight clients on devices.

AFAIK the only things dropping tx history prevent you from doing are
A: Using the blockchain as a permanent timestamp server or as a file server, both of which are outside the scope of bitcoin anyway, not to mention would contribute considerably to size.

and

B: Long term data mining of the blockchain, which would only be used by law enforcement (who could still retain as much as they wanted) and identity thieves.

As far as long term goes, I think it's relevant to compare BTC to say, VISA. VISA does, on average, the equivalent of 1.2 million tx per block, or around 360MB per block, or 52GB per day. For this they have one to a few large centralized datacenters, which are in turn served by one to a few large digital clearing houses. Each of these has some absurd internet hookup for handling all of the necessary dataflow, paid for by near-draconian fees which are usually paid by merchants and thus are paid for by, although opaque to, consumers.

BTC, on the other hand, is extremely extremely redundant redundant redundant. Every independent miner and every full client carries the full weight of documenting the transaction history as well as the full network load for outstanding tx. In order for the BTC network to handle the same sort of tx volume as VISA, every miner must then have the full network capacity of VISA as well as the storage capacity to maintain an indefinitely large transaction history.

Ultimately this is unavoidable for any secure payment system, however for BTC there are other considerations that are quite relevant even right now. For example, due to the size of the blockchain, most miners (or at least most of the hashing power) would rather have DeepBit take a big chunk of fees and do all the tx verification and blockchain storage for them, rather than store the whole thing and get no-fees-plus-donations on P2Pool.

The pruned blockchain model doesn't fix this very well, and ultimately the idea pushes tx verification onto centralized mining pools, with clients being forced to request merkle tree data from tx sent to their accounts in order to verify it. That would only add further redundancy and strain the network capacity of the centralized nodes moreso than VISA's servers deal with currently.

More importantly, the only thing resisting the tendency of increased centralization of BTC and direct reliance on cartels is Moore's Law. Quite obviously, BTC user demand has the capacity to grow much faster than Moore's law. Reducing the per-tx network requirements moderately and reducing the per-tx-per-block storage requirements by more than an (computing) order of magnitude would be a big step towards weighting the trend back towards decentralization. Fully (or at least mostly) solving the centralization problem can only be done through the block reward, since tx volume tends to scale with market cap, such that the value of the block reward scales with the BTC economy. IMO fees are incapable of supporting the network due to the level of redundancy present, and will only tend to reduce its use value.
111  Other / Beginners & Help / Re: Block Chain Summary or Ledger or Balance on: April 04, 2012, 08:55:11 AM
The space saving I had in mind is precisely what people think it is, I am just storing address balances. It's like I have a modified bitcoin client that has all the known public keys with non-zero balances. And again, this is all based on the block chain.
Again, this can be included in a new protocol (which allows forcibly merging several outputs of the same address), but in the current protocol, knowing the balance of every address is useless.

I had that same idea. By itself it wouldn't save blockchain space by much, but condensed into a ledger it could allow you to keep much less blockchain for basically the same security. It would also work well combined with your proof of stake concept, using ledger hashes every, say 138 out of 144 blocks, with every 144th being signed.
112  Bitcoin / Development & Technical Discussion / Re: Bitcoin smartcard Point of Sale terminal on: April 03, 2012, 05:41:42 AM
I was talking more about security from merchant overcharging, and for that matter, since BTC is spent by referring to previous txOuts, you'd have to load all the txOuts onto your card, or trust the merchant to construct a tx with the proper amounts that pays you the proper change. If the merchant is using a USB smart-card reader, they would have even more room for messing with clients since there are no software restrictions on a general computer as opposed to a specialized card payment unit.

That's exactly the point.  You can put multiple addresses on a smart card, verify the transaction amounts with a display, and create all the transactions right on the card.  There's absolutely zero need to trust merchants.

How do you get them on there? In order for a card to create tx it would have to have the relevant txIns, in which case it could also know its own balance, and could use a simple interface for "locking in" the settling price for a tx prior to pin input. Again, though, that requires having a computer and a card reader for loading and managing it, or else a bank which can do it for you.
113  Bitcoin / Development & Technical Discussion / Re: One proposal for hindering antisocial blocks on: April 03, 2012, 05:33:43 AM
I mean of course that the block reward is kept constant. (That we do take this protocol change in the future.)

Nobody (I guess you are?) is even suggesting block reward will be kept constant.  The fixed # of coins is a cornerstone of Bitcoin.  Changing that now (even if desirable) will never happen.

Actually I've considered that alternative from time to time. A very low (long run < 1%/y) inflation rate is basically just as good as zero inflation, with the added benefit of replacing lost coins. The main problem is that there's no guarantee that the block reward will be enough to pay for mining, but similarly there is no guarantee that it won't completely pay for mining and make tx fees basically superfluous. That would require predicting the future market price for BTC, the cost of a future mining rig, the number of rigs required to handle the future tx throughput, which you'd also need to predict, and so on.

The same limitations of multiple, unpredictable variables makes it somewhere between difficult and impossible to make any determinations about efficient mining incentives. The major advantage to being able to predict something like that is that then you could charge a standard fee rate or no fees and basically every tx could still be verified by the next block. Given that "change" can't be spent till at least 1 confirmation (I assume anyway), the time consideration can become a major bottleneck for the use value of BTC.
114  Bitcoin / Development & Technical Discussion / Re: Bitcoin smartcard Point of Sale terminal on: April 03, 2012, 05:10:51 AM
That and, what's the price difference between a USB card reader + supercard with screen and such vs the cost of the cheapest BTC runnable smartphone?

I imagine the "supercards" are less than $20.  The point is that once you have a display and keypad, you don't need a reader.  So the cost is similar.

you could just input the price they display to you on your card, enter your pin, then hit send. The card signs a tx with only that exact value so they can't change the price after you begin entering your pin. It could be doable but it seems a bit complicated imo.

No, there's no need to manually enter the transaction amount.  Transactions can be sent over the wire.  This is irrelevant.

I was talking more about security from merchant overcharging, and for that matter, since BTC is spent by referring to previous txOuts, you'd have to load all the txOuts onto your card, or trust the merchant to construct a tx with the proper amounts that pays you the proper change. If the merchant is using a USB smart-card reader, they would have even more room for messing with clients since there are no software restrictions on a general computer as opposed to a specialized card payment unit.

I agree, it would be nice, but you'll have to seed the market.  Markets can be big or small as in mass marketing or niche market. They can be high margin or they can generate losses. Markets in the strategic design sense is separate from profits.  People can seek profitable markets are narrow their definition to make the market more profitable (i.e., exclude poorer people) A market is just a collection of people who you believe will benefit from your good or service.  For programmers it's like a collection of objects, where objects are always human being.

It is important to be able to visualize the participants you are looking to serve. It is difficult to design a system for a foreign market w/out understanding their infrastructure. In one design I had to go back to flip phones (SMS) and a middle office because that was the only reliable technology people in that market had access to on a consistent basis. When defining a market segment I look for what is the most accessible, low-cost technology at the POS for both customer and merchant. So in the case of Greece solutions may well look more like M-Pesa (9 million people in 3 years! A top down authoritarian model. They're being studied at all the top B-schools now) or the mobile solution in Ghana (open source with equal rights to participation for all consumers and all telcos) Don't assume that b/c those economies are lesser developed that they haven't found a way to exchange value without using the debit and credit card networks, b/c they have an in that sense they are years ahead of the US (ironic isn't it?) Mass market access to mobile payment, elite only access to Visa/MC.

Can these solutions be fully automated? Yes. As for the cost of service, you are essentially getting the Telcos to dump data into a middle office for processing and then you need to be able to send replies to both the merchant and their customer. These Telcos modules are now a commodity product (See BOKU) I can find out how much it costs here in the US if you'd like that reference point. But I don't see why you can't build your own, I mean it's just bits and bytes across a wire like all e-payments. Can't you grab the data from an email client and process it? Yes the run rate could be higher than that of a cobbled together smart card system, (# of SMS messages per month) on the other hand once you write the customer/merchant facing app and automate the middle office (just a big data base with a few rules) you don't have to spend a whole lot of time installing hardware and the merchants won't have to buy any new systems or devices. Oh and for BTCs system users would also need cloud-based wallet services.

Well, I can see that M-Pesa works. Theoretically BTC should work under similar conditions. However, I don't know anything about cloud-based services, and I don't even own a smart phone =\. Where possible, QR codes printed on a receipt are probably the easiest route, requiring only an internet connection to validate, but again that depends on what hardware is available for clients as well as what is typically available for merchants. The only way to find that out is to visit Greece and see what it's like. If smart phones are common and merchants can easily get an internet connected computer, then a flip phone service would only be needed to make it available to the stragglers. If the best anyone can afford is a flip phone, then you're pretty much stuck with centralization, which is a Very Bad Thing in a confiscation-sensitive environment. Also possibly relevant are the fees incurred by said service, although really it shouldn't be more than current banking fees.

Security is another big question, I think. What happens if someone steals your phone? How do you enter a pin or something without your phone recording it? Etc etc.
115  Bitcoin / Development & Technical Discussion / Re: Replacing Bitcoin with Bitcoin2 on: April 03, 2012, 04:13:39 AM
Hmm.. without saving the unspent txOuts from the classic chain, there's no way to keep them spendable in the future. After a certain point, you could condense all the unspent txOuts from the classic chain into a ledger and save it away, but you'd have to maintain backwards compatibility basically forever to make sure that anyone who possibly still had access to classic coins could still spend them into the new chain. Since some of the coins are definitely lost, there's no way to know when it's "safe" to throw away all the remnants of the old chain.

As long as there was an easy old-to-new wallet converter, conversion would be no problem. After a certain amount of time, maybe 50 years, it would probably be safe to dump the remaining classic tx. The biggest problem I can see is that, compared to simply making a new free-floating currency, programming all of that backwards compatibility would be a lot of extra effort and cost. Also you'd have to hold 2 blockchains at once until at least most of the network converted, which might lead to a few double spends if any merchant were still relying on the old protocol for tx verification after the swap was finalized.

The biggest killer I can see with the BTC network is that the blockchain might tend to grow significantly faster than hardware (Wirth's Law) leading to increased centralization and increased network costs. If that becomes the case, then managing two blockchains at once might be impractical or impossible.
116  Bitcoin / Development & Technical Discussion / Re: Bitcoin smartcard Point of Sale terminal on: April 03, 2012, 02:11:48 AM
Okay, If I understand you now. If you'd like to build a prototype geared to the Greek market? Because if that's the case, I'd recommend a mobile solution rather than a card based solution. Matters not what kind of phone they have, old flip fone, smartphone... The key to making it work is a middle office. You'd have to build that. Where would customers get their BTCs? From storefronts or online via the exchanges? If I am hearing you about your target market we can work out more details...

Well, I wouldn't exactly call them "my market". I don't have the resources to launch a huge BTC promotion in Greece (nor do I have greek contacts), although I am curious; how could you use BTC with an old flip phone?

Also, that would depend on what technology is commonly affordable/available in Greece. Since "not EUR/ECB" is the most appealing feature of BTC for Greeks, delivering the currency to them requires putting it in whatever form is most available to them. I don't even have the slightest clue what greeks commonly use or have.

I'm only interested in that point because it would be nice to see the people of a country outsmart their multi-hierarchal dictators for once, not particularly because I want to profit from the venture.

My question is, even if you load BTC to your smartcard's address without connecting it to your computer somehow, how does the card know how much is on it?

Obviously it doesn't in that case.  What I'm proposing is that you stick your card into a machine and deposit your $1, the machine sends a +5 BTC transaction, it gets displayed on the card, and you okay it.  The card keeps track of your balance.

For the cards I posted at least, if you browse the site you can see they have cards with keypads as well.  It would be possible to manually set your balance with those.

Quote
More importantly, how do you set your pin without a central authority doing it for you?

Same solution, cards with keypads.  But a pin is not necessarily a requirement, especially when using multisig keys as mentioned.  Ultimately a reader is only like $15 anyways so I think your minimum outlay is going to be around $20 regardless of which type of card you use.

Well if the initial outlay for a USB card reader isn't so bad, and you can get a card with a numpad, then you could just input the price they display to you on your card, enter your pin, then hit send. The card signs a tx with only that exact value so they can't change the price after you begin entering your pin. It could be doable but it seems a bit complicated imo. That and, what's the price difference between a USB card reader + supercard with screen and such vs the cost of the cheapest BTC runnable smartphone?
117  Bitcoin / Development & Technical Discussion / Re: Replacing Bitcoin with Bitcoin2 on: April 03, 2012, 01:32:40 AM
That might be a way to expand the coinbase, for example making 1 old BTC = 10 new BTC or whatever arbitrary value. By swapping them across chains you could avoid backwards compatibility issues with the old chain, and maintain fungibility indefinitely.

The only problem is what happens to people who have bitcoin stashes they can't access for long periods of time? If you have bitcoins hiding away for, say, ~30 years, and everyone else switches over to the new BTC2 or what have you during that time, won't your coins be left on an old, unused defunct blockchain that nobody even keeps anymore?
118  Bitcoin / Development & Technical Discussion / Re: Bitcoin smartcard Point of Sale terminal on: April 03, 2012, 01:26:46 AM
There are a few paper-based analogs. I seem to remember reading of a handful of towns that created there own voucher (currency) that could be used in all the shops in that town.  Maybe Ithaca NY (Cornell) was one?

I believe ithaca uses a time-currency worth about ~$10 an hour. There's also Berkshares and a few others. All of said currencies come with a socialist hook, however.

My question is, even if you load BTC to your smartcard's address without connecting it to your computer somehow, how does the card know how much is on it? Seems to me it'd be up to memory and luck to make sure you didn't overdraft, which would end up sending an invalid tx anyway. More importantly, how do you set your pin without a central authority doing it for you? I think it's also worth noting that if a card continuously re-uses a single address, then it kinda kills your privacy too.

On the merchant end, assuming physical sales, there's still the problem of integrating a bitcoind backend for register and accounting software, and exchange risk. It seems to me CAO/ICS systems would be less affected, if at all except for the inherent exchange risk involved.

Protecting against double spends = easy
Protecting against exchange risk = not so much
Protecting against arbitrary government confiscation and dealing with accounting conversions = jungle gym

In Greece I think all the disadvantages are moot. Greek business owners currently can't get loans, greek people have no money to spend, and the value of the Eur is evaporating out from under them both in government debt and inflation. Anything that would allow them to easily manage their business or even do business at all would be nothing short of deus ex machina for them, and it's not like they give a damn about complying with government tax regulations or anything. They would like nothing better than for the EUR, the ECB, the IMF, the unelected European Commission, and their own unelected government to hurry up and die so they can get on with their lives.
119  Other / Beginners & Help / Re: Hyperdeflation, own half the world by headstart - don't you care at all? on: April 03, 2012, 12:41:03 AM
You don't see a problem with that? Currently a 51% attack "only" alloww the attacker to
* stop the network
* double spend his own coins (reverse txs he created)

If network is reduced to a flat ledger a 51% attack would allow the attacker to change balances of accounts he doesn't own which massively increases the economic value of 51% attack.  Even the potential is damaging.

Obviously you didn't read very far. Ledgers would be validated in the same way as blocks, via hashing power with periodic ledger hashes. They could additionally be verified with proof of stake, and you could reduce the maximum reorg down to 24h of blocks, or possibly even less with additional measures.

Then again 75MB + 50MB per week (say 4 weeks of history retained) = 275 MB which last time I checked > 50MB claimed.  Also that was a back of the napkin estimate.  Someone actually did create a ledger and the size was 10% of full blockchain.  So that would be more like 200MB + 200MB for 4 weeks of history = 400 MB. 

The cost estimate for a pruned blockchain is ~500MB vs 2GB raw so you are saving very little.  Pruned block chain provides most of the space reduction with no loss of security.

If you had read more than one post, you'd know that he got it down to 7% of the total blockchain size, not 10%. 50MB per week suggests a 5GB blockchain by the end of 2012. Either the blockchain is more than doubling in size every year now, which is in excess of moore's law, or you're full of crap on that figure.

Quote
AFAIK pruned merkle trees can only be used to verify your own balance, and not anyone else's. That is, you can't mine using only that, and you if you can't mine then you also can't verify a tx someone has sent to you.

Not correct but at least this time you correctly indicated it it your belief not fact.  

Pruned merkle tree allows verification of blocks, verification of your tx, verification of other users tx, and mining new blocks.  There is no functionality that is lost with the exception of tracing coin history beyond the oldest unspent output.

To verify tx (yours or anyone elses) you simply need to verify the prior outputs of the inputs in the tx to be verified.  By definition those would be included in a pruned blockchain.  Mining doesn't require anything beyond verifying txs other than access to prior blocks block header, the block height, and the ability to verifying work created by peers.

It might be a good idea to actually read the white paper.

You know I put off reading the whitepaper primarily because I assumed it would be a full dissertation. I was disappointed.

However now I understand the way merkle trees work for the most part. Here's a comparison:

-When you prune merkle trees, you still have to keep the block header, all of the merkle tree hashes, and the full tx of any tx that have any unspent txOuts, including all of the txIns, all of the scripts for the txIns, all of the txOuts (including spent txOuts) plus all of the scripts for the txOuts. Verifying tx still requires either a full pruned blockchain or that you trust centralized nodes to provide you with the correct merkle tree entries that you request.

-For the linked ledger system, you throw away all but the unspent txOuts plus the scripts for the unspent txOuts. All block headers older than a certain time can be discarded along with all of the merkle hashes and tx, and each client only needs to keep 4-5 weeks of blockchain and 3 ledgers (1 for an old seeding period, 1 backup, 1 current), of which 2 weeks of blockchain and 2 ledgers can be compressed since they're seldom if ever needed.

-If all unspent txOuts which have the same address are added together and condensed, that would reduce the size of a ledger by ~50% or more. This would also require using the full value of an acct as txIn, but that also reduces the size of txIns on the blockchain as a result.

2000MB * .035 = 70MB Per ledger
70MB * 2 = 140MB of ledgers that can be compressed
33MB (est weekly block size with reduced txIns) * 3 = 99MB uncompressed blockchain (maximum, varies)
66MB compressible blockchain (2wks historical for seeding)

70 + 99 = 169MB uncompressed
140 + 66 = 206MB compressible

I think your 500MB estimate for pruned merkle trees is overly optimistic. I'll believe it when I see it. Assuming you can compress data to 66% of original using zip or similar, with ledgers you'd only keep a maximum of about 305MB, and only 215MB for a lite client.

That's assuming that 6 months of total blockchain are retained over the mining network for seeding so that clients can do a "full verification" on first start, and is still ~1/2 to 1/3 the size of a fully pruned complete blockchain, and ~10% of an unpruned one, even with backups.
120  Bitcoin / Development & Technical Discussion / Re: Bitcoin smartcard Point of Sale terminal on: April 02, 2012, 04:58:30 AM
With a display, at least, there's no reason you couldn't add Bitcoins the same way you spend them.  Even multi-sig backups could probably be made to work without a reader as well.

I don't really get it. If you don't have a smart card interface to your computer, how do you load any coins onto them? By going to some centralized bank? Certainly the grocery store isn't going to offer deposit services for bitcoin cards. If you do have a card interface for your computer, you could set up your pin securely from there and load whatever coins you wanted from your online or offline wallets.

Personally I lean towards the contact smartcards rather than RF.  They are more reliable, and less subject to tampering.  It's less convenient, but not really any less convenient than credit cards currently.

I don't see how a contact based smart card would be any better than an RF card security wise. Neither has a large enough range to allow someone to steal your money remotely, and in both cases you're trusting that the manufacturer of the card reader has made it so that the merchant can't charge more than they said they would without retyping your pin.

AFAIK (from the few RF smartcard readers I've seen, and McDonald's is about the only place I've seen them) most RF card readers don't even require even so much as a pin input, which would be a disadvantage vs contact cards, but the card itself could require a pin to mitigate that problem. On the other hand, requiring a pin would be a disadvantage for small token purchases, like the original usage of smart cards as subway tickets.

Although the price tag of a smart card is way more affordable than a smart phone, I don't think they're well suited to the technology and usage of BTC.
Pages: « 1 2 3 4 5 [6] 7 8 9 10 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!