[POLL] Multi-sig or scalability--which is more pressing?

[finkleshnorts]

I know these aren't entirely mutually exclusive.

I am specifically talking about blockchain size/transactions-per-second vs. multi-sig enabled transactions.

My opinion: If bitcoin suddenly absorbs rapid growth and becomes badly bottlenecked, its image will suffer greatly. Multi-sig seems to be more of a luxury feature, even though it does open up a lot of possibilities for the use of bitcoins.

But it seems that scalability is very much on the backburner for now.

Edit: Mods, this may be more suited for dev/technical discussion board.

[1713498120]

1713498120

[benjamindees]

Scalability definitely.  Mostly because multi-sig should wait, for strategic reasons.

[FreeMoney]

Scalability definitely.  Mostly because multi-sig should wait, for strategic reasons.

Tell us more.

[bracek]

many users + poor scalability = bullish

many users + no multi-sig = bearish 

(imo)

[FreeMoney]

many users + poor scalability = bullish

many users + no multi-sig = bearish 

(imo)

You are saying you think scalability the less important?

I think it's more important when I consider worst case scenarios, but mostly I think we have plenty of time until it becomes a real problem and a nice GUI for multi-sig would be awesome.

[Timo Y]

Bitcoin can still absorb massive growth even with the current block size limit. Normal users who do a few transactions a week would simply crowd out low priority transactions such as SatoshiDice.

Say that an average "normal user" does about one transaction per day. The current "throttled" protocol could handle approx. 500,000 such users. 

Transaction fees needed for inclusion could rise, but higher transaction fees are less damaging to bitcoin's reputation than heist after heist being reported in the media.

That's why multisig is more pressing in my opinion.

[Mike Hearn]

Multisig support was already (re)enabled in the protocol with the last release.

Scalability is not on the backburner at all. Right now there's a ton of work going into it:

• Myself and Stefan are upgrading the Satoshi client to use LevelDB, which eliminates IO as a bottleneck on hard disk based nodes. This should make blocks and transactions propagate a lot faster across the network, which in turn should mean mining pools find it profitable to include SatoshiDice transactions again.
• sipa and Matt have been experimenting with different ways of doing pruning, which means you can have a full node that doesn't store the entire block chain. Sipa also has refactored some of the core TX verification code in a way that'll make it easier to multi-thread in future.
• Jeff has been doing some initial work and design proposals for connection filtering, which is needed to make bandwidth usage for lightweight clients linear in wallet activity rather than system activity
• Just generally a bunch of us are working on bitcoinj, which is a lightweight (SPV) implementation of Bitcoin which scales with wallet activity rather than system activity. Eventually nearly all users will be using SPV clients, meaning they won't have to download or process the whole block chain. We can already run Bitcoin on mobile phones, which is a big achievement, but there's still plenty of work left to do.
• Gavin has been finding ways to make hard-forking changes much smoother and easier in future, which will be important when we reach the 1MB limit.

If anything I'd say right now most development effort, at least from "core" developers, is going into scalability.

[hazek]

If anything I'd say right now most development effort, at least from "core" developers, is going into scalability.

This is very awesome and confidence inspiring to hear, keep it up! 

[bracek]

many users + poor scalability = bullish

many users + no multi-sig = bearish 

(imo)

You are saying you think scalability the less important?

I think it's more important when I consider worst case scenarios, but mostly I think we have plenty of time until it becomes a real problem and a nice GUI for multi-sig would be awesome.

I think it is much less dangerous to have bottleneck, than to be open to all kinds of hacking and no escrow

[Technomage]

My opinion is that right now multi-sig is more important. Security is the current problem for Bitcoin, scalability is an upcoming problem. Both are important and should be worked on side by side though.

[waspoza]

• Myself and Stefan are upgrading the Satoshi client to use LevelDB, which eliminates IO as a bottleneck on hard disk based nodes. This should make blocks and transactions propagate a lot faster across the network, which in turn should mean mining pools find it profitable to include SatoshiDice transactions again.

Wow leveldb, fantastic! Good choice.

[acoindr]

While I'm glad there are core technical solutions being pursued to address both issues I think there is more to consider.

In a sense those approaches are focused very near the problem. They deal with them in a core technical way rather than a more practical way.

Let's say both issues are resolved as imagined. What happens then? Little Timmy says okay grandma you just download the wallet client and install it - no it's simple really - then wait for it to download the blockchain.  Before you send any money to your address remember to back up your wallet, in 3 places! That's simple too, you just find the wallet.dat file on your computer... Okay, now you are ready to receive and send money. To do that give out your receive addresses; they are long strings of characters, just remember to wait for 6 confirmations for all payments!

Do you really see that working for mainstream users?

I don't. I see things happening a much different way. Most users will use eWallets for transactions which solves the scalability issue and helps the security issue.

People can understand using online services like PayPal, logging in with their password and paying to someone's email address. They can see their balance easily and they know how to give out their email to receive payments.

Right now you're thinking, but they have to put too much trust in eWallets! No, not necessarily. The eWallets don't hold big BTC balances. They are really just transactional.

People store the majority of their coins safely offline in a hardware wallet.

Yes, what we need to be working on is hardware wallets. The Bitcoin Card is one example of this, but I think that may end up a bit fussy, possibly pricey, and tricky to use for many users.

We need someone to manufacture hardware wallets as follows:

Hardware Wallets

A hardware wallet is about the size of a DSL modem. It's composed of a very simple cpu/motherboard, small solid state hard drive, NIC, probably an LCD screen, and a few ports as I'll describe. It has a clean Linux install and a Bitcoin client. MSRP about $70.00.

Little Timmy tells grandma what to do:

Okay, grandma, just go to BestBuy, or this website and buy the bitcoin solid wallet (hmm i like how that sounds!). Open the package and plug it in. Connect the cable to the Internet and press the "on" button. When the light turns green it's ready to use!

On the screen you will see it says "receive address" followed by a long string of characters. Don't worry about that right now. In the package you will see two USB sticks. Take one and plug it into the USB slot. Press the top button that says "backup wallet". When the light turns green remove the USB stick, plug in the other USB stick and press the "backup wallet" button again. Put the USB sticks in two separate safe places, like a bank safe deposit box for one, and home safe for the other.

Now you're ready to use Bitcoin!

Go to WalletBit.com and sign up with an email and password. You will also have to go to Mt.Gox and sign up to buy some bitcoins, but for now I'll just send you some to get started and you can pay me later. In fact, I've already sent coins to your WalletBit account because I know your email address!

Log in to WalletBit and you'll see them there! You can pay anybody just by using their email address.

What's the SolidWallet for? Oh that's when you're ready to really get into Bitcoin and you will hold lots of them. Remember your "receive address" it showed? Well, when you do buy lots of bitcoins, like on Mt.Gox, you will send them to that address. It's easy. Then when you want to fill up your balance at WalletBit just log in there and click "Deposit Bitcoins". Unplug your computer keyboard and plug it into the back of the SolidWallet and press the "Send" button on top. Type the long address shown by WalletBit, just do it carefully and double check it. Press the "BTC amount" button on top and type the number of bitcoins you want to deposit. Press the "Send" button again. That's it! Your SolidWallet screen will show your new balance.
______

If you notice, this solves (or helps significantly) three problems: security, bitcoin scalabilty (most transactions happen on eWallet databases), and usability.

[kwukduck]

Without the security multi-sig offers , there will never be enough people to even get to a scalability problem. Multi-sig is one thing that could make bitcoin really stand out.

[cypherdoc]

Multisig support was already (re)enabled in the protocol with the last release.

Scalability is not on the backburner at all. Right now there's a ton of work going into it:

• Myself and Stefan are upgrading the Satoshi client to use LevelDB, which eliminates IO as a bottleneck on hard disk based nodes. This should make blocks and transactions propagate a lot faster across the network, which in turn should mean mining pools find it profitable to include SatoshiDice transactions again.
• sipa and Matt have been experimenting with different ways of doing pruning, which means you can have a full node that doesn't store the entire block chain. Sipa also has refactored some of the core TX verification code in a way that'll make it easier to multi-thread in future.
• Jeff has been doing some initial work and design proposals for connection filtering, which is needed to make bandwidth usage for lightweight clients linear in wallet activity rather than system activity
• Just generally a bunch of us are working on bitcoinj, which is a lightweight (SPV) implementation of Bitcoin which scales with wallet activity rather than system activity. Eventually nearly all users will be using SPV clients, meaning they won't have to download or process the whole block chain. We can already run Bitcoin on mobile phones, which is a big achievement, but there's still plenty of work left to do.
• Gavin has been finding ways to make hard-forking changes much smoother and easier in future, which will be important when we reach the 1MB limit.

If anything I'd say right now most development effort, at least from "core" developers, is going into scalability.

this is really encouraging.  thank you guys very much for your great efforts.

[finkleshnorts]

Multisig support was already (re)enabled in the protocol with the last release.

Scalability is not on the backburner at all. Right now there's a ton of work going into it:

• Myself and Stefan are upgrading the Satoshi client to use LevelDB, which eliminates IO as a bottleneck on hard disk based nodes. This should make blocks and transactions propagate a lot faster across the network, which in turn should mean mining pools find it profitable to include SatoshiDice transactions again.
• sipa and Matt have been experimenting with different ways of doing pruning, which means you can have a full node that doesn't store the entire block chain. Sipa also has refactored some of the core TX verification code in a way that'll make it easier to multi-thread in future.
• Jeff has been doing some initial work and design proposals for connection filtering, which is needed to make bandwidth usage for lightweight clients linear in wallet activity rather than system activity
• Just generally a bunch of us are working on bitcoinj, which is a lightweight (SPV) implementation of Bitcoin which scales with wallet activity rather than system activity. Eventually nearly all users will be using SPV clients, meaning they won't have to download or process the whole block chain. We can already run Bitcoin on mobile phones, which is a big achievement, but there's still plenty of work left to do.
• Gavin has been finding ways to make hard-forking changes much smoother and easier in future, which will be important when we reach the 1MB limit.

If anything I'd say right now most development effort, at least from "core" developers, is going into scalability.

this is really encouraging.  thank you guys very much for your great efforts.

This!

[Transisto]

...
Hardware Wallets

A hardware wallet is about the size of a DSL modem. It's composed of a very simple cpu/motherboard, small solid state hard drive, NIC, probably an LCD screen, and a few ports as I'll describe. It has a clean Linux install and a Bitcoin client. MSRP about $70.00.

Little Timmy tells grandma what to do:

Okay, grandma, just go to BestBuy, or this website and buy the bitcoin solid wallet (hmm i like how that sounds!). Open the package and plug it in. Connect the cable to the Internet and press the "on" button. When the light turns green it's ready to use!

On the screen you will see it says "receive address" followed by a long string of characters. Don't worry about that right now. In the package you will see two USB sticks. Take one and plug it into the USB slot. Press the top button that says "backup wallet". When the light turns green remove the USB stick, plug in the other USB stick and press the "backup wallet" button again. Put the USB sticks in two separate safe places, like a bank safe deposit box for one, and home safe for the other.

Now you're ready to use Bitcoin!

Go to WalletBit.com and sign up with an email and password. You will also have to go to Mt.Gox and sign up to buy some bitcoins, but for now I'll just send you some to get started and you can pay me later. In fact, I've already sent coins to your WalletBit account because I know your email address!

Log in to WalletBit and you'll see them there! You can pay anybody just by using their email address.

What's the SolidWallet for? Oh that's when you're ready to really get into Bitcoin and you will hold lots of them. Remember your "receive address" it showed? Well, when you do buy lots of bitcoins, like on Mt.Gox, you will send them to that address. It's easy. Then when you want to fill up your balance at WalletBit just log in there and click "Deposit Bitcoins". Unplug your computer keyboard and plug it into the back of the SolidWallet and press the "Send" button on top. Type the long address shown by WalletBit, just do it carefully and double check it. Press the "BTC amount" button on top and type the number of bitcoins you want to deposit. Press the "Send" button again. That's it! Your SolidWallet screen will show your new balance.
______...

http://www.youtube.com/watch?v=YtdWHFwmd2o&feature=player_detailpage#t=25s
OMG, this is what you'll sound like to grandma !

I must have been for too long in your first scenario, I didn't understand the 2nd at all.
All I can tell from it is that it's about 3 time longer in terms of words / instructions.

Oh and what happen when someone steal the "Hardware Wallet" ?

[adamstgBit]

Multisig support was already (re)enabled in the protocol with the last release.

Scalability is not on the backburner at all. Right now there's a ton of work going into it:

• Myself and Stefan are upgrading the Satoshi client to use LevelDB, which eliminates IO as a bottleneck on hard disk based nodes. This should make blocks and transactions propagate a lot faster across the network, which in turn should mean mining pools find it profitable to include SatoshiDice transactions again.
• sipa and Matt have been experimenting with different ways of doing pruning, which means you can have a full node that doesn't store the entire block chain. Sipa also has refactored some of the core TX verification code in a way that'll make it easier to multi-thread in future.
• Jeff has been doing some initial work and design proposals for connection filtering, which is needed to make bandwidth usage for lightweight clients linear in wallet activity rather than system activity
• Just generally a bunch of us are working on bitcoinj, which is a lightweight (SPV) implementation of Bitcoin which scales with wallet activity rather than system activity. Eventually nearly all users will be using SPV clients, meaning they won't have to download or process the whole block chain. We can already run Bitcoin on mobile phones, which is a big achievement, but there's still plenty of work left to do.
• Gavin has been finding ways to make hard-forking changes much smoother and easier in future, which will be important when we reach the 1MB limit.

If anything I'd say right now most development effort, at least from "core" developers, is going into scalability.

this is really encouraging.  thank you guys very much for your great efforts.

This!

This is gr8!

[[Tycho]]

Unplug your computer keyboard and plug it into the back of the SolidWallet and press the "Send" button on top. Type the long address shown by WalletBit, just do it carefully and double check it. Press the "BTC amount" button on top and type the number of bitcoins you want to deposit.

Typing the bitcoin addresses by hand is not a way to go.

[spiccioli]

Multisig support was already (re)enabled in the protocol with the last release.

Scalability is not on the backburner at all. Right now there's a ton of work going into it:

• Myself and Stefan are upgrading the Satoshi client to use LevelDB, which eliminates IO as a bottleneck on hard disk based nodes. This should make blocks and transactions propagate a lot faster across the network, which in turn should mean mining pools find it profitable to include SatoshiDice transactions again.
• sipa and Matt have been experimenting with different ways of doing pruning, which means you can have a full node that doesn't store the entire block chain. Sipa also has refactored some of the core TX verification code in a way that'll make it easier to multi-thread in future.
• Jeff has been doing some initial work and design proposals for connection filtering, which is needed to make bandwidth usage for lightweight clients linear in wallet activity rather than system activity
• Just generally a bunch of us are working on bitcoinj, which is a lightweight (SPV) implementation of Bitcoin which scales with wallet activity rather than system activity. Eventually nearly all users will be using SPV clients, meaning they won't have to download or process the whole block chain. We can already run Bitcoin on mobile phones, which is a big achievement, but there's still plenty of work left to do.
• Gavin has been finding ways to make hard-forking changes much smoother and easier in future, which will be important when we reach the 1MB limit.

If anything I'd say right now most development effort, at least from "core" developers, is going into scalability.

Mike,

I always wanted to ask this question: is there a reason for not separating the client from the DB management and use a real SQL engine like MySQL or PostgreSQL to host the blockchain?

spiccioli

[Mike Hearn]

Bitcoin doesn't need a fully relational database, it just needs a key/value store. A standalone database like MySQL/Postgres would complicate installation a lot! A library equivalent like SQLite would probably be even slower than Berkeley DB which is what's used at the moment.

Right now the core Bitcoin network has run out of disk seeks, which are a finite resource. That's why some mining pools are dropping fee-paying transactions from SatoshiDice. In other words, Bitcoin has already reached a scalability limit and miners are load-shedding in order to keep the orphan rates down.

LevelDB was designed to optimize for reduced disk seeks as its primary goal, and it sacrifies many advanced database features to get that. Its design is one reason Google BigTable is such a high-performance storage system. Fortunately we don't need those advanced features, but we do need more seeks, which is why it makes sense to use it.