Pages:
Author

Topic: Bitcoin 2013: The Future of Payments - San Jose, CA - May 17-19, 2013 (Read 17384 times)

newbie
Activity: 42
Merit: 0
member
Activity: 70
Merit: 10
where are videos of Dan Kaminsky from the conference?

Someone kindly posted this recently:

  https://bitcointalksearch.org/topic/video-bitcoin-2013-conference-on-youtube-219519

Kaminsky was on the security one (at least...that's the only one I saw live.)

After midnight when my bandwidth become free I'll watch some of the ones I missed in person.  Satellite connection.  Bummer because I just got bitcoind (along with openssl, boost, berkeleydb, etc) compiled and I would like to be running it to see how it does on a high latency connection.



Cool. Thanks.
legendary
Activity: 1596
Merit: 1099
What is Kaminsky's deal?  Saying there is a 0% chance for Proof-of-Work to survive the year?  Wtf?  He seems a bit misinformed about bitcoin mining.  He thought GPUs couldn't currently mine bitcoin profitably, and he also thought that one entity having over 50% of hash power would result in a bitcoin price of zero, which was obviously not the case when deepbit did it.  He also seems to believe that scrypt is ASIC-proof, which is not true.

He's way off.  Check out @dakami and @jgarzik twitter.  There is even a bet on the floor (that he's trying to back away from).

legendary
Activity: 4690
Merit: 1276
I missed meeting you at the conference D&T!  My favorite way of reading this forum is by doing a search for your posts. ...

Jeez, what were you going to do if you met him?  Hump his leg?

...The general post quality has become so terrible recently compared to a year or two ago, I can't stand it.

Always happy to do my part.

sr. member
Activity: 328
Merit: 250
I missed meeting you at the conference D&T!  My favorite way of reading this forum is by doing a search for your posts.  The general post quality has become so terrible recently compared to a year or two ago, I can't stand it.
donator
Activity: 1218
Merit: 1079
Gerald Davis
What is Kaminsky's deal?  Saying there is a 0% chance for Proof-of-Work to survive the year?  Wtf?  He seems a bit misinformed about bitcoin mining.  He thought GPUs couldn't currently mine bitcoin profitably, and he also thought that one entity having over 50% of hash power would result in a bitcoin price of zero, which was obviously not the case when deepbit did it.  He also seems to believe that scrypt is ASIC-proof, which is not true.

Yeah I was puzzled by that as well.   None of the questioners asked him to clarify.  Of course most of the people lining up to "ask questions" are usually ones trying to push an agenda or make long monologs in the form of questions.   They already have their questions in mind before the panel start.

I wish he would clarify. I mean like it or not Bitcoin can't be changed.  It can be forked but barring a complete consensus of all users (not all miners or developers but all users) the existing network will continue to operate.  Nobody is going to get a consensus on moving from POW.  So not sure how he can be bullish on Bitcoin and at the same time say Bitcoin is dead unless it moves beyond POW.  If true (which I doubt) then Bitcoin is already dead and just doesn't know it.
sr. member
Activity: 328
Merit: 250
What is Kaminsky's deal?  Saying there is a 0% chance for Proof-of-Work to survive the year?  Wtf?  He seems a bit misinformed about bitcoin mining.  He thought GPUs couldn't currently mine bitcoin profitably, and he also thought that one entity having over 50% of hash power would result in a bitcoin price of zero, which was obviously not the case when deepbit did it.  He also seems to believe that scrypt is ASIC-proof, which is not true.
legendary
Activity: 4690
Merit: 1276
where are videos of Dan Kaminsky from the conference?

Someone kindly posted this recently:

  https://bitcointalksearch.org/topic/video-bitcoin-2013-conference-on-youtube-219519

Kaminsky was on the security one (at least...that's the only one I saw live.)

After midnight when my bandwidth become free I'll watch some of the ones I missed in person.  Satellite connection.  Bummer because I just got bitcoind (along with openssl, boost, berkeleydb, etc) compiled and I would like to be running it to see how it does on a high latency connection.

hero member
Activity: 615
Merit: 500
where are videos of Dan Kaminsky from the conference?
legendary
Activity: 905
Merit: 1011
In practice that probably wouldn't bloat the UTXO set at all.
legendary
Activity: 1078
Merit: 1006
100 satoshis -> ISO code
Some day I'd like to see accounting software that uses Bitcoin addresses for individual accounts, let's you book entrees and move money around all day internally off blockchain, then at the end of the day balance out all the transactions and post the resulting ending balance transfers to the blockchain. That would allow for a third party permanent public record to reconcile to, and would allow a company to run its accounting finances on the Bitcoin network without spamming it with transactions (you can do multiple transfers between multiple addresses in a single transaction). That may contribute to blockchain bloat a bit, but it the verifiable account entrees in the chain may be s service businesses would gladly pay for.

Yes. That's the sensible middle-ground which hopefully will be reached in the future. It reduces the problem of small transactions hitting the blockchain, but also keeps the blockchain open for all, instead of restricting it to bitcoin-banks similar to how the Fedwire system operates.
legendary
Activity: 1680
Merit: 1035
Some day I'd like to see accounting software that uses Bitcoin addresses for individual accounts, let's you book entrees and move money around all day internally off blockchain, then at the end of the day balance out all the transactions and post the resulting ending balance transfers to the blockchain. That would allow for a third party permanent public record to reconcile to, and would allow a company to run its accounting finances on the Bitcoin network without spamming it with transactions (you can do multiple transfers between multiple addresses in a single transaction). That may contribute to blockchain bloat a bit, but it the verifiable account entrees in the chain may be s service businesses would gladly pay for.
sr. member
Activity: 328
Merit: 250
I was responding to: "the blockchain size will increase linearly".

I don't think there is sufficient consensus as to what will happen once the blocksize limit is removed. However the odds are very slim that it will remain a straight line.

The blockchain is not currently increasing in size linearly in a straight line, as you can see here:
http://blockchain.info/charts/blocks-size?timespan=all&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=

It is increasing exponentially because we are in the adoption stage where more users are added.  Once bitcoin reaches its potential market size, or once it hits a blocksize limit, the blockchain size will increase linearly.  We will never see sustained exponential growth in the number of monetary transactions that humans need to conduct.

Bitcoin merchant adoption and transaction fees have grown 1000% over last year, which is an extremely high rate that temporarily outpaces hard drive capacity growth, but this cannot be sustained very long.  Hard drive space and internet speed show no signs of slowing their exponential growth rates, so they will always outpace the bitcoin blockchain in the long run.  Exponential growth will always win out over linear growth.  People will be able to store the blockchain on their personal computers forever.
legendary
Activity: 1680
Merit: 1035

For Mtgox it's a bit harder.

I remember MtGox used to pay Eligius pool directly for it to accept their free transactions. As in personal contract as opposed to mining fees. I don't know if that changed, whether they are using someone else, or if it stopped completely.
donator
Activity: 2058
Merit: 1054
it is still in the miner's best interest to keep a block size limit in place.
Miners are not a monolithic entity. If miners try to keep a grassroots size limit, every individual miner has an incentive to mine a bigger block and scoop up all those floating transaction fees. This is a classical tragedy of the commons scenario.

There needs to be a good tx fee mechanism that properly sponsors both the amortized cost of hashing and the marginal cost of processing (storage, verification, communication). To sponsor hashing you need to limit (or charge for) the total value sent in a block; to sponsor storage and communication you need to limit the block data size; to sponsor verification you need to limit the total script complexity.
Can you tell me where I can research various entities and see if they pay fees?   I wanted to see how much people like dice and gox pay back into the system since they are the largest users of capacity.  I am not familiar enough with everything to know how to do this.
SatoshiDice is easy - their addresses are constant and public, and you can look them up. In fact if you go to the blockchain.info homepage you'll see that almost half the transactions are SD, and labelled as such. AFAICT they always pay a fee.

For Mtgox it's a bit harder.
legendary
Activity: 2380
Merit: 1019
Be A Digital Miner
it is still in the miner's best interest to keep a block size limit in place.
Miners are not a monolithic entity. If miners try to keep a grassroots size limit, every individual miner has an incentive to mine a bigger block and scoop up all those floating transaction fees. This is a classical tragedy of the commons scenario.

There needs to be a good tx fee mechanism that properly sponsors both the amortized cost of hashing and the marginal cost of processing (storage, verification, communication). To sponsor hashing you need to limit (or charge for) the total value sent in a block; to sponsor storage and communication you need to limit the block data size; to sponsor verification you need to limit the total script complexity.
Can you tell me where I can research various entities and see if they pay fees?   I wanted to see how much people like dice and gox pay back into the system since they are the largest users of capacity.  I am not familiar enough with everything to know how to do this.
legendary
Activity: 4690
Merit: 1276

Ah, you are right.  It's a small wonder that it is a bit cumbersome to dig up and not exactly front page on the Bitcoin marketing literature.

As I read this, it reminds me that I actually have seen it before (which is probably why something in the back of my mind kept me from denying it outright as impossible.)  I probably read it shortly before I went on my tirade about it being a fucking lie to call Bitcoin 'p2p', or at least will be.

It also probably corresponds to the time when I started suspecting Bitcoin of emitting some whiffs of Ponzi-tiveity and looking out of the corner of my eye for the location to the doorway.

donator
Activity: 2058
Merit: 1054
it is still in the miner's best interest to keep a block size limit in place.
Miners are not a monolithic entity. If miners try to keep a grassroots size limit, every individual miner has an incentive to mine a bigger block and scoop up all those floating transaction fees. This is a classical tragedy of the commons scenario.

There needs to be a good tx fee mechanism that properly sponsors both the amortized cost of hashing and the marginal cost of processing (storage, verification, communication). To sponsor hashing you need to limit (or charge for) the total value sent in a block; to sponsor storage and communication you need to limit the block data size; to sponsor verification you need to limit the total script complexity.
legendary
Activity: 905
Merit: 1011
I was responding to: "the blockchain size will increase linearly".

I don't think there is sufficient consensus as to what will happen once the blocksize limit is removed. However the odds are very slim that it will remain a straight line.
legendary
Activity: 1596
Merit: 1099
That does not hold true once the blocksize limit is removed, which will happen eventually.

There is insufficient consensus to make that prediction.

Pages:
Jump to: