the joint
Legendary
Offline
Activity: 1834
Merit: 1020
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 26, 2014, 04:16:07 PM |
|
Faster confirmation times do have benefits:
Many transactions are never confirmed for one reason or another. If I am selling something, I want to make sure that I will eventually get the bitcoins. If a transaction is confirmed once, then it is extremely likely to be confirmed many times, even if the first is orphaned. So one confirmation is fine for me even if confirmation times are short, and shorter confirmation times are more convenient.
Another benefit is a better distribution of block rewards. If there are more block rewards, then the chances of getting a block reward is higher. That reduces the need for mining pools.
Yes, the largest benefit to short confirmation times is that 1 confirmation is infinitely better than 0 confirmations. As a result, very short confirmation times are hands-down better for convenience-store-like transactions (assuming that the time isn't so short that you end up with intolerably high rates of orphans, etc.). Really, anything beyond 15-30 seconds becomes a legitimate issue for these transaction types. One confirmation is not better then 0/unconfirmed necessarily. If the confirmation time is too short then it would be very easy to attack the network and people would have a false sense of security when they see that a TX has n confirmations. When the block confirmation time is longer you will know that it will take more resources to double spend the TX (assuming there is a sufficient TX fee and the TX is well propagated) I think this is nitpicking a little bit. You're talking about a false sense of security from someone who assumes that 1 confirmation at an average of (for example) 30-second confirmation times provides the same level of security as 1 confirmation at an average of 10-minute confirmation times. But, regardless of psychology, if you *had* to chose between 0 confirmations at n-second confirmation times or 1 confirmation at n-minus-m-second confirmation times, which would you pick? The point is that one confirmation at any confirmation rate is preferable to 0 confirmations, and therefore *is* necessarily better.
|
|
|
|
|
StevenS
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 26, 2014, 07:24:59 PM |
|
But it would take resources to intentionally orphan the last block in order to double spend a transaction with 1 confirmation. It takes no resources to double spend a transaction with zero confirmations. So, there is some security improvement when you compare 0 confirmations and a longer block time, to 1 confirmation with a short block time.
I understand what you are saying. But help me understand the Bitcoin protocol here. Let me know if I have some of this wrong: The Bitcoin network is interconnected nodes that share unconfirmed transactions by broadcasting them among the nodes. A wallet application joins the network by connecting to one or more of these nodes. When BTC is sent from one wallet to another, it is sent through the network and the receiving wallet sees the transaction. A transaction must be verified by a node before it is sent to the next node. Part of this verification is a check to see if it duplicates an input from another transaction, either one in the blockchain or one in the unconfirmed pool. Thus, it is difficult to double-spend because the transaction with a duplicate input would have to be introduced into the network before the 1st has propagated. Not only that, but the double-spend would only work if the recipient of the 2nd transaction was connected to a part of the network to which the 1st transaction hadn't been propagated. Thus, to protect against a double-spend, the recipient only has to wait long enough for the transaction to propagate through most of the network. This is less time than the wait for the transaction to be confirmed in a block.
|
|
|
|
remotemass
Legendary
Offline
Activity: 1122
Merit: 1017
ASMR El Salvador
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 26, 2014, 09:28:17 PM |
|
I would: make all coins of an address that has not been used for 10 years be moved to a void address. This would force everyone to move their coins to a new address once that time limit was about to be reached, and so we would always know how many coins are "alive".
|
{ Imagine a sequence of bits generated from the first decimal place of the square roots of whole integers that are irrational numbers. If the decimal falls between 0 and 5, it's considered bit 0, and if it falls between 5 and 10, it's considered bit 1. This sequence from a simple integer count of contiguous irrationals and their logical decimal expansion of the first decimal place is called the 'main irrational stream.' Our goal is to design a physical and optical computing system system that can detect when this stream starts matching a specific pattern of a given size of bits. bitcointalk.org/index.php?topic=166760.0 } Satoshi did use a friend class in C++ and put a comment on the code saying: "This is why people hate C++".
|
|
|
itsAj
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 26, 2014, 10:29:32 PM |
|
Faster confirmation times do have benefits:
Many transactions are never confirmed for one reason or another. If I am selling something, I want to make sure that I will eventually get the bitcoins. If a transaction is confirmed once, then it is extremely likely to be confirmed many times, even if the first is orphaned. So one confirmation is fine for me even if confirmation times are short, and shorter confirmation times are more convenient.
Another benefit is a better distribution of block rewards. If there are more block rewards, then the chances of getting a block reward is higher. That reduces the need for mining pools.
Yes, the largest benefit to short confirmation times is that 1 confirmation is infinitely better than 0 confirmations. As a result, very short confirmation times are hands-down better for convenience-store-like transactions (assuming that the time isn't so short that you end up with intolerably high rates of orphans, etc.). Really, anything beyond 15-30 seconds becomes a legitimate issue for these transaction types. One confirmation is not better then 0/unconfirmed necessarily. If the confirmation time is too short then it would be very easy to attack the network and people would have a false sense of security when they see that a TX has n confirmations. When the block confirmation time is longer you will know that it will take more resources to double spend the TX (assuming there is a sufficient TX fee and the TX is well propagated) I think this is nitpicking a little bit. You're talking about a false sense of security from someone who assumes that 1 confirmation at an average of (for example) 30-second confirmation times provides the same level of security as 1 confirmation at an average of 10-minute confirmation times. But, regardless of psychology, if you *had* to chose between 0 confirmations at n-second confirmation times or 1 confirmation at n-minus-m-second confirmation times, which would you pick? The point is that one confirmation at any confirmation rate is preferable to 0 confirmations, and therefore *is* necessarily better. I would disagree. My point is that 1 confirmation on a ten minute block chain is more secure then 10 confirmations are on a 1 minute block chain. The reason for this is because of the higher number of orphans that will occur on a 1 minute block chain. In order to successfully double spend a TX that is well propagated throughout the network and contains an appropriate TX fee you generally need to find the next block after the TX is sent (you could also find enough consecutive blocks after the TX is sent but this would be more expensive). If you have a 1 minute block time then it will take less resources to find the next block (it will also take less resources to find enough consecutive blocks to overcome the chain that confirmed your TX).
|
|
|
|
catlinhappy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 27, 2014, 09:05:57 AM |
|
It would certainly be the restriction of transaction confirmation interval to one.
|
|
|
|
Mars not Moon
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 67
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 27, 2014, 10:05:02 AM |
|
I think the present bitcoin system is pretty stable and working well. I have no problem with confirmation times either.
|
|
|
|
barbarousrelic
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 27, 2014, 01:03:46 PM |
|
But it would take resources to intentionally orphan the last block in order to double spend a transaction with 1 confirmation. It takes no resources to double spend a transaction with zero confirmations. So, there is some security improvement when you compare 0 confirmations and a longer block time, to 1 confirmation with a short block time.
I understand what you are saying. But help me understand the Bitcoin protocol here. Let me know if I have some of this wrong: The Bitcoin network is interconnected nodes that share unconfirmed transactions by broadcasting them among the nodes. A wallet application joins the network by connecting to one or more of these nodes. When BTC is sent from one wallet to another, it is sent through the network and the receiving wallet sees the transaction. A transaction must be verified by a node before it is sent to the next node. Part of this verification is a check to see if it duplicates an input from another transaction, either one in the blockchain or one in the unconfirmed pool. Thus, it is difficult to double-spend because the transaction with a duplicate input would have to be introduced into the network before the 1st has propagated. Not only that, but the double-spend would only work if the recipient of the 2nd transaction was connected to a part of the network to which the 1st transaction hadn't been propagated. Thus, to protect against a double-spend, the recipient only has to wait long enough for the transaction to propagate through most of the network. This is less time than the wait for the transaction to be confirmed in a block. You're close. Bitcoin nodes relay new transactions to each other, but they don't necessarily (and don't usually) mine a new block when relaying new transactions. Until a new block is mined that includes a new transaction, (usually 10 minutes on average, but this varies) it is not certian which transaction will be included in the blockchain (confirmed) and which transaction will be ignored*. Miner software has to decide which one to include. It is up to the miner to decide how to rectify this situation, and I'm not certain how off-the-shelf miner software typically handles it. I've asked in this thread here: https://bitcointalk.org/index.php?topic=758658.0*And even when a new block is mined that includes your transaction, there is a small chance (if other miners quickly mine two blocks in a row without your transaction) that this block may be replaced by another block that doesn't include your transaction.
|
Do not waste your time debating whether Bitcoin can work. It does work.
"Early adopters will profit" is not a sufficient condition to classify something as a pyramid or Ponzi scheme. If it was, Apple and Microsoft stock are Ponzi schemes.
There is no such thing as "market manipulation." There is only buying and selling.
|
|
|
marcotheminer (OP)
Legendary
Offline
Activity: 2072
Merit: 1049
┴puoʎǝq ʞool┴
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 27, 2014, 07:41:47 PM |
|
Any more opinions - bump
|
|
|
|
wasserman99
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 01:08:25 AM |
|
But it would take resources to intentionally orphan the last block in order to double spend a transaction with 1 confirmation. It takes no resources to double spend a transaction with zero confirmations. So, there is some security improvement when you compare 0 confirmations and a longer block time, to 1 confirmation with a short block time.
I understand what you are saying. But help me understand the Bitcoin protocol here. Let me know if I have some of this wrong: The Bitcoin network is interconnected nodes that share unconfirmed transactions by broadcasting them among the nodes. A wallet application joins the network by connecting to one or more of these nodes. When BTC is sent from one wallet to another, it is sent through the network and the receiving wallet sees the transaction. A transaction must be verified by a node before it is sent to the next node. Part of this verification is a check to see if it duplicates an input from another transaction, either one in the blockchain or one in the unconfirmed pool. Thus, it is difficult to double-spend because the transaction with a duplicate input would have to be introduced into the network before the 1st has propagated. Not only that, but the double-spend would only work if the recipient of the 2nd transaction was connected to a part of the network to which the 1st transaction hadn't been propagated. Thus, to protect against a double-spend, the recipient only has to wait long enough for the transaction to propagate through most of the network. This is less time than the wait for the transaction to be confirmed in a block. This is not 100% true. However it is true most of the time. In order for someone to get around this they would need to have access to mining resources that would include a block in it's found block that would double spend a TX prior to an unconfirmed TX being confirmed. For most smaller to medium sized transactions this risk would be pretty small.
|
|
|
|
cccarnation
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 146
Merit: 10
One Token to Move Anything Anywhere
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 07:03:41 AM |
|
It would be my holdings ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
|
BitsBitsBits
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 07:15:45 AM |
|
the 21 mio limit ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif) ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fwww.tfmetalsreport.com%2Fsites%2Fdefault%2Ffiles%2Fpictures%2Fpicture-404.jpg&t=665&c=fGwoQxJZhdB00w) Why is that an issue? ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif) Or is that cause you want it to be double that, litecoinguy? ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
|
unexecuted
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 175
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 07:16:21 AM |
|
Improve the architecture, use Zero-knowledge proofs so that you only need the headers plus the latest ZKP to know that it is a full valid chain, and then you'd only need the UTXO set to know your balance and spend your coins. And the headers would contain a Merkle tree hash of the current UTXO set in each block so you can directly see which known UTXO's have been spent even without needing to see the actual transactions, you just need them for incoming transactions to you.
|
|
|
|
mistercoin
Legendary
Offline
Activity: 1045
Merit: 1000
https://r.honeygain.me/XEDDM2B07C
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 04:06:28 PM |
|
I would add the ability to store data in the blockchain, such as music, text files and others, displacing the data across the networks computers.
|
|
|
|
odolvlobo
Legendary
Offline
Activity: 4424
Merit: 3325
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 04:15:10 PM |
|
I would add the ability to store data in the blockchain, such as music, text files and others, displacing the data across the networks computers.
LOL Don't you think a block chain filled with music files would be a problem? Think about it.
|
Join an anti-signature campaign: Click ignore on the members of signature campaigns. PGP Fingerprint: 6B6BC26599EC24EF7E29A405EAF050539D0B2925 Signing address: 13GAVJo8YaAuenj6keiEykwxWUZ7jMoSLt
|
|
|
mistercoin
Legendary
Offline
Activity: 1045
Merit: 1000
https://r.honeygain.me/XEDDM2B07C
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 04:17:24 PM |
|
I would add the ability to store data in the blockchain, such as music, text files and others, displacing the data across the networks computers.
LOL Don't you think a block chain filled with music files would be a problem? Think about it. XD Perhaps. Maybe exclude the music files, and limit it to data like texts, and size-limited apps. Could also be used for things like date specific confirmations that require proof that such and such was done on X day. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
|
odolvlobo
Legendary
Offline
Activity: 4424
Merit: 3325
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 05:58:40 PM |
|
I would add the ability to store data in the blockchain, such as music, text files and others, displacing the data across the networks computers.
LOL Don't you think a block chain filled with music files would be a problem? Think about it. XD Perhaps. Maybe exclude the music files, and limit it to data like texts, and size-limited apps. Could also be used for things like date specific confirmations that require proof that such and such was done on X day. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) Maybe a separate peer-to-peer file sharing system would work better. That way every person wouldn't have to maintain a copy of every file. We could name it "bit-something", maybe "bit torrent". I like that name. Let's make it.
|
Join an anti-signature campaign: Click ignore on the members of signature campaigns. PGP Fingerprint: 6B6BC26599EC24EF7E29A405EAF050539D0B2925 Signing address: 13GAVJo8YaAuenj6keiEykwxWUZ7jMoSLt
|
|
|
the joint
Legendary
Offline
Activity: 1834
Merit: 1020
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 06:15:52 PM |
|
Faster confirmation times do have benefits:
Many transactions are never confirmed for one reason or another. If I am selling something, I want to make sure that I will eventually get the bitcoins. If a transaction is confirmed once, then it is extremely likely to be confirmed many times, even if the first is orphaned. So one confirmation is fine for me even if confirmation times are short, and shorter confirmation times are more convenient.
Another benefit is a better distribution of block rewards. If there are more block rewards, then the chances of getting a block reward is higher. That reduces the need for mining pools.
Yes, the largest benefit to short confirmation times is that 1 confirmation is infinitely better than 0 confirmations. As a result, very short confirmation times are hands-down better for convenience-store-like transactions (assuming that the time isn't so short that you end up with intolerably high rates of orphans, etc.). Really, anything beyond 15-30 seconds becomes a legitimate issue for these transaction types. One confirmation is not better then 0/unconfirmed necessarily. If the confirmation time is too short then it would be very easy to attack the network and people would have a false sense of security when they see that a TX has n confirmations. When the block confirmation time is longer you will know that it will take more resources to double spend the TX (assuming there is a sufficient TX fee and the TX is well propagated) I think this is nitpicking a little bit. You're talking about a false sense of security from someone who assumes that 1 confirmation at an average of (for example) 30-second confirmation times provides the same level of security as 1 confirmation at an average of 10-minute confirmation times. But, regardless of psychology, if you *had* to chose between 0 confirmations at n-second confirmation times or 1 confirmation at n-minus-m-second confirmation times, which would you pick? The point is that one confirmation at any confirmation rate is preferable to 0 confirmations, and therefore *is* necessarily better. I would disagree. My point is that 1 confirmation on a ten minute block chain is more secure then 10 confirmations are on a 1 minute block chain. The reason for this is because of the higher number of orphans that will occur on a 1 minute block chain. In order to successfully double spend a TX that is well propagated throughout the network and contains an appropriate TX fee you generally need to find the next block after the TX is sent (you could also find enough consecutive blocks after the TX is sent but this would be more expensive). If you have a 1 minute block time then it will take less resources to find the next block (it will also take less resources to find enough consecutive blocks to overcome the chain that confirmed your TX). But it's a completely different issue to talk about 1 confirmation on a ten-minute avg. block time vs. 10 confirmations on a one-minute avg. block time than it is to talk about 0 confirmations on a ten-minute avg. block time vs. 1 confirmation on a one-minute avg. block time. Again, the point I'm getting at is simply about the importance of the very first confirmation. No matter how you spin it, 1 confirmation regardless of the avg. block time is infinitely better than 0 confirmations at any avg. block time. There's a huge difference between the two scenarios, and while you can debate (and be correct) about the false sense of security provided by confirmations with rapid avg. block times, it's undeniable that 1 confirmation is always better than 0. Always.
|
|
|
|
bitbaby
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 08:46:10 PM |
|
AND why?Just 1 thing, for I it would be transaction times, cause waiting for those confirmations is wayy too long sometimes ![Cry](https://bitcointalk.org/Smileys/default/cry.gif) I would like to see some improvements in security and scam prevention, I know it's almost impossible but I wish there was some way to catch people who take bitcoins and run away like all the website scams (wallets/mining) etc.
|
|
|
|
odolvlobo
Legendary
Offline
Activity: 4424
Merit: 3325
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
August 28, 2014, 10:28:00 PM |
|
AND why?Just 1 thing, for I it would be transaction times, cause waiting for those confirmations is wayy too long sometimes ![Cry](https://bitcointalk.org/Smileys/default/cry.gif) I would like to see some improvements in security and scam prevention, I know it's almost impossible but I wish there was some way to catch people who take bitcoins and run away like all the website scams (wallets/mining) etc. If you willingly give your money to an anonymous stranger somewhere on the planet, then there is nothing that Bitcoin can ever do to get it back.
|
Join an anti-signature campaign: Click ignore on the members of signature campaigns. PGP Fingerprint: 6B6BC26599EC24EF7E29A405EAF050539D0B2925 Signing address: 13GAVJo8YaAuenj6keiEykwxWUZ7jMoSLt
|
|
|
|