[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[Sub-Ether]

Rumor is Dash price is being held hostage by Vern. Price seems alot lower at Cryptsy. Is this true? A shame if it is. Dash should be alot higher given recent events.

It's not like people will be rushing with their BTCs to buy cheap coins at cryptsy.

I warned someone that I know personally, hes left hundreds of Dash at Cryptsy and didn't act, can't say I didn't try, looking less promising everyday, funny thing is the volume is still pretty high, if you believe that of course.

[dazbarlby]

Happy New Year Guys

I'm creating an infographic and would like somebody to read over the following and tell me if it's accurate.

Thank you

---------------------------------------------
DASH Solves Bitcoins instant Transaction Double Spend Problem

Bitcoin can be received instantly, but until transactions are confirmed by the network they can be easily double spent. This means somebody can send Bitcoin to a retailer they are paying and at the same time send those same bitcoins to themselves.

So which payment becomes valid (known as confirmed), the payment to the retailer or the payment back to themselves?

The way bitcoin works is that transaction messages are sent to the Peer-2-Peer network when a transaction is initiated. So to double spend all somebody has to do is send one transaction message to spend xyz bitcoin with a zero transaction fee (the payment to the retailer) to one node in the network and at the exact same time send another transaction to spend xyz bitcoin with a transaction fee (the payment to themselves) to another node in the network. To the retailer, it looks like they have received the payment and they allow the shopper to walk away with the goods...

...the problem the retailer can't see (but will become obvious 10 minutes later) is the Bitcoin network has a conflict and the way it solves this conflict is very slow and allows the shopper to leave. Bitcoin resolves the conflict by validating the transaction in a block (a collection of transactions). Unfortunately the block can only accept and confirm a finite number of transactions every 10 minutes. Because there are usually more transactions than a block can hold, only certain transactions get accepted into the block. Guess which transaction gets into the next block? that's right, the transaction with the larger fee (the transaction sent back to themselves). So the transaction back to shopper is validated as a genuine transaction on the network and the transaction the retailer thought they had received on their device suddenly vanishes.

By the time the retailer realises they have not been paid (at least 10 minutes later), the shopper has gone.

This is why you should never trust a zero confirmed Bitcoin transaction and it's also why Bitcoin will never be used (without a centralised third party insurer) like cash at offline retailers, vending machines, train stations, taxis, Gas Stations, cinema's and anywhere else you have instant, secure validated transactions.

DASH has solved this major flaw in Bitcoin...

Instead of validating transactions every 10 minutes like Bitcoin, DASH validates transactions in real time on it's 2nd tier masternode network and if there are two conflicting transactions, both transactions are instantly rejected by the network. This means merchants can be assured that when their DASH wallet says they have received DASH, it really is theirs and will never suddenly vanish.

[Sub-Ether]

Happy New Year Guys
I'm creating an infographic and would like somebody to read over the following and tell me if it's accurate.
Thank you

Bitcoin can be received instantly, but until transactions are confirmed by the network they can be easily double spent. This means somebody can send Bitcoin to a retailer they are paying and at the same time send those same bitcoins to themselves.

By the time the retailer realises they have not been paid (at least 10 minutes later), the shopper has gone.
This is why you should never trust a zero confirmed Bitcoin transaction and it's also why Bitcoin will never be used (without a centralised third party insurer) like cash at offline retailers, vending machines, train stations, taxis, Gas Stations, cinema's and anywhere else you have instant, secure validated transactions.
DASH has solved this major flaw in Bitcoin...

Don't retailers allow for the odd loss with double spending on zero confirm as a necessary evil, the kicker is that any large transactions need 1 confirmation at least, so small transactions that incur relatively high charges/user time and bloat the blockchain will be way laid due to the inevitable higher fees that must be introduced in order to counter the lack of scalability, after all when the memory pool has 20,000 unconfirms waiting to go into a block, do you really want to wait until tomorrow morning to get 1 confirmation?

The point also is that instantX is not random, it is instantly locked where as block entry into a bitcoin block is unpredictable to say the least, is that really how businesses can work?

[toknormal]

DASH has solved this major flaw in Bitcoin...

I wouldn't call that a "flaw". I'd just say it was a deficiency when it comes to implementing cash on an electronic platform.

[Solarminer]

Happy New Year Guys

I'm creating an infographic and would like somebody to read over the following and tell me if it's accurate.

Thank you

---------------------------------------------
DASH Solves Bitcoins instant Transaction Double Spend Problem

Bitcoin can be received instantly, but until transactions are confirmed by the network they can be easily double spent. This means somebody can send Bitcoin to a retailer they are paying and at the same time send those same bitcoins to themselves.

So which payment becomes valid (known as confirmed), the payment to the retailer or the payment back to themselves?

The way bitcoin works is that transaction messages are sent to the Peer-2-Peer network when a transaction is initiated. So to double spend all somebody has to do is send one transaction message to spend xyz bitcoin with a zero transaction fee (the payment to the retailer) to one node in the network and at the exact same time send another transaction to spend xyz bitcoin with a transaction fee (the payment to themselves) to another node in the network. To the retailer, it looks like they have received the payment and they allow the shopper to walk away with the goods...

...the problem the retailer can't see (but will become obvious 10 minutes later) is the Bitcoin network has a conflict and the way it solves this conflict is very slow and allows the shopper to leave. Bitcoin resolves the conflict by validating the transaction in a block (a collection of transactions). Unfortunately the block can only accept and confirm a finite number of transactions every 10 minutes. Because there are usually more transactions than a block can hold, only certain transactions get accepted into the block. Guess which transaction gets into the next block? that's right, the transaction with the larger fee (the transaction sent back to themselves). So the transaction back to shopper is validated as a genuine transaction on the network and the transaction the retailer thought they had received on their device suddenly vanishes.

By the time the retailer realises they have not been paid (at least 10 minutes later), the shopper has gone.

This is why you should never trust a zero confirmed Bitcoin transaction and it's also why Bitcoin will never be used (without a centralised third party insurer) like cash at offline retailers, vending machines, train stations, taxis, Gas Stations, cinema's and anywhere else you have instant, secure validated transactions.

DASH has solved this major flaw in Bitcoin...

Instead of validating transactions every 10 minutes like Bitcoin, DASH validates transactions in real time on it's 2nd tier masternode network and if there are two conflicting transactions, both transactions are instantly rejected by the network. This means merchants can be assured that when their DASH wallet says they have received DASH, it really is theirs and will never suddenly vanish.

Dash part needs a change

DASH has an advantage

Dash confirms transactions in blocks in a similar manner to Bitcoin but every 2.5 minutes.  In addition, it has a 2nd tier network that can capture the transaction and lock the funds for 5 blocks while rejecting any double spend attempts during this time.  This technology is called InstantX and makes Dash the true replacement for cash in point of sale purchases

[Sub-Ether]

DASH has an advantage

Just on a point of trivia, Solar, you are no longer the world record holder, check your signature, you will have to surpass 10 million and 1 key pairs if you want the flowery blue ribbon back

[Solarminer]

Happy New Year Guys
I'm creating an infographic and would like somebody to read over the following and tell me if it's accurate.
Thank you

Bitcoin can be received instantly, but until transactions are confirmed by the network they can be easily double spent. This means somebody can send Bitcoin to a retailer they are paying and at the same time send those same bitcoins to themselves.

By the time the retailer realises they have not been paid (at least 10 minutes later), the shopper has gone.
This is why you should never trust a zero confirmed Bitcoin transaction and it's also why Bitcoin will never be used (without a centralised third party insurer) like cash at offline retailers, vending machines, train stations, taxis, Gas Stations, cinema's and anywhere else you have instant, secure validated transactions.
DASH has solved this major flaw in Bitcoin...

Don't retailers allow for the odd loss with double spending on zero confirm as a necessary evil, the kicker is that any large transactions need 1 confirmation at least, so small transactions that incur relatively high charges/user time and bloat the blockchain will be way laid due to the inevitable higher fees that must be introduced in order to counter the lack of scalability, after all when the memory pool has 20,000 unconfirms waiting to go into a block, do you really want to wait until tomorrow morning to get 1 confirmation?

The point also is that instantX is not random, it is instantly locked where as block entry into a bitcoin block is unpredictable to say the least, is that really how businesses can work?

I don't think retailers understand this.  They don't plan for double spends at all.  And for the most part, people spending Bitcoin are honest enough not to try a double spend.  Once it is obvious how big of an issue the double spend problem is, they will just stop using Bitcoin.  Then the transaction fee comes up.  If you need a 1 block confirmation, you are spending the highest of fees ~$.20.  Maybe ok for a large purchase, but a vending machine looks pretty silly when you spend 20% of your Bitcoin on fees for a $1 soda. 

For a payment over the internet, fees the block confirmations are not a big deal.  Shipping is usually $5 anyway, and a 30 min delay for a block isn't a big deal.  Privacy is still a concern, but there are options for mixing.  Bitcoin may survive on internet sales, but point of sale is out.  No matter how many band-aids they use, it just isn't possible.

[Sub-Ether]

Btw, talking of scaling and bitcoin wallet transaction usage with update times, I did a recent Tao ratio, to gauge where its heading and how the blockchain is updating with the seed peers.

3rd August 2015, bitcoin v.0.11.0

Tao sync ratio = 4.144 seconds per hour of wallet behind

22nd December 2015, bitcoin v.0.11.0

Tao sync ratio = 6.625 seconds per hour of wallet behind

Conclusion

Bitcoin is now updating 59.87% slower than it was only 5 months before.
This is to be expected as the number of transactions has more than doubled but does not bode well for the future as user takeup increases.
It may be pointed out that updating maxes out the bandwidth and memory of fairly high spec machines as well.

[dazbarlby]

Btw, talking of scaling and bitcoin wallet transaction usage with update times, I did a recent Tao ratio, to gauge where its heading and how the blockchain is updating with the seed peers.

3rd August 2015, bitcoin v.0.11.0

Tao sync ratio = 4.144 seconds per hour of wallet behind

22nd December 2015, bitcoin v.0.11.0

Tao sync ratio = 6.625 seconds per hour of wallet behind

Conclusion

Bitcoin is now updating 59.87% slower than it was only 5 months before.
This is to be expected as the number of transactions has more than doubled but does not bode well for the future as user takeup increases.
It may be pointed out that updating maxes out the bandwidth and memory of fairly high spec machines as well.

Is the Tao ratio over the past year plotted on a chart somewhere?

[Solarminer]

DASH has an advantage

Just on a point of trivia, Solar, you are no longer the world record holder, check your signature, you will have to surpass 10 million and 1 key pairs if you want the flowery blue ribbon back

This is a true statement...I now hand the blue ribbon back to you, the rightful owner.

I still have another world record you can try for....good luck!

[Sub-Ether]

Is the Tao ratio over the past year plotted on a chart somewhere?

Not monthy readings but there is just enough to make a chart plot over the last 9 months, I'll try to make them more regular for better trend prediction.
Need to update december readings, the biggest difference for bitcoin was when Gavin's memory hop tweaks were introduced in early march 2015, the tao ratio halved down to Tao =2.7 secs/hr but it didn't last long and went upto to 4.7 secs/hr by the end of march 2015, then reduced slightly with v11 and has been climbing ever since
https://dashtalk.org/threads/dash-versus-bitcoin-versus-darkcoin-wallet-update-benchmark-times.4479/

[TanteStefana2]

DASH has an advantage

Just on a point of trivia, Solar, you are no longer the world record holder, check your signature, you will have to surpass 10 million and 1 key pairs if you want the flowery blue ribbon back

LOL, how long did that take? 

[Sub-Ether]

DASH has an advantage

Just on a point of trivia, Solar, you are no longer the world record holder, check your signature, you will have to surpass 10 million and 1 key pairs if you want the flowery blue ribbon back

LOL, how long did that take? 

haha, glad you asked, 8 minutes startup time for that many key pairs is pretty impressive eh. 

''Initial key pair creation time =  4 hr 53 mins, wallet size = 6.3 GB, RAM used = 2.4 GB, and startup time =  8 minutes''

[Sub-Ether]

I still have another world record you can try for....good luck!

haha, funny QR scan code record, thats original
Is it possible to use my 8 inch telescope with 300 times 8-24 mm Hyperion zoom lense and light noise filters or is that considered cheating ?

[Solarminer]

DASH has an advantage

Just on a point of trivia, Solar, you are no longer the world record holder, check your signature, you will have to surpass 10 million and 1 key pairs if you want the flowery blue ribbon back

LOL, how long did that take? 

haha, glad you asked, 8 minutes startup time for that many key pairs is pretty impressive eh. 

''Initial key pair creation time =  4 hr 53 mins, wallet size = 6.3 GB, RAM used = 2.4 GB, and startup time =  8 minutes''

To put that in perspective.  That is like making a new address for every transaction on the bitcoin network as fast as the maximum transaction speed of 5 transactions/sec for 23 days straight.

Or in other words, that wallet has enough addresses to receive every single transaction on the bitcoin network(assuming 80% full blocks) for a month.

[Solarminer]

I still have another world record you can try for....good luck!

haha, funny QR scan code record, thats original
Is it possible to use my 8 inch telescope with 300 times 8-24 mm Hyperion zoom lense and light noise filters or is that considered cheating ?

That would bump you up to the 'with the aid of a lens' category.

For reference the QR code was on a 42" tv run by a raspberry pi.  I didn't have any more wall space to backup, but my phone had more capability.  You can also generate a QR code with additional error correction, so to really max out this distance you need to max out the error correction setting when making the QR code.

[Sub-Ether]

That would bump you up to the 'with the aid of a lens' category.
For reference the QR code was on a 42" tv run by a raspberry pi.  I didn't have any more wall space to backup, but my phone had more capability.  You can also generate a QR code with additional error correction, so to really max out this distance you need to max out the error correction setting when making the QR code.

So I need to get a bigger tv! I will give it a try, think the room is smaller than that, if I use a wall mirror that could double the distance.
There is an optical limit to normal magnification of around 1000 times, although those meta materials can bend the laws of physics but thats even more off topic, anyway happy new year again and byzz, I'm vaporizing about now 

[splawik21]

Tantissimi auguri & happy new year!!!!

[TanteStefana2]

DASH has an advantage

Just on a point of trivia, Solar, you are no longer the world record holder, check your signature, you will have to surpass 10 million and 1 key pairs if you want the flowery blue ribbon back

LOL, how long did that take? 

haha, glad you asked, 8 minutes startup time for that many key pairs is pretty impressive eh. 

''Initial key pair creation time =  4 hr 53 mins, wallet size = 6.3 GB, RAM used = 2.4 GB, and startup time =  8 minutes''

LOL, 8 minutes just to start it!  LOL.  That is actually impressive though, I would think longer.  On my machine, I bet it would have taken 2 days to generate them

[TanteStefana2]

Hey guys, when I start up a Dashd -daemon, I get this notice " sendto: Operation not permitted" after a few seconds.  I don't know what it's supposed to mean?  Anyone know?  The daemon seems to be running ok, and I tried deleting everything except the dash.conf/masternode.conf files, still get this :/  Thanks for any help

Hummmm it seems it could be related to a ipv6 setting... if it doesn't do anything else, I guess I'll not worry,