[DSH] Dashcoin (Cryptonote, automated source)

[lostisland]

I think i messed up when trying to send coins to myself...

transfer 0 address 100000
Money successfully sent, transaction <txnumber>

They didnt show up in my wallet afterwords...any ideas?

[tricass]

once dash have ease of sending transaction, i'll send some donation..

I have some finding about the recent transaction problem. I knew what was the problem when I fixed my test pool - transactions with size bigger than 10,000 bytes were hardly accepted in the blockchain. I took my investigation further and here are my finding:

1. Minergate uses old or modified code:
This is the code from the current version on Dashcoin:

#define CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE 20000

Here is what they probably use:

#define CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE 10000

2. Minergate started to use this code on 2014/10/06 10:28:17
I looked at the blockchain for odd blocks and they started to appear here:
http://chainradar.com/dsh/blocks/2241/30

67225   14-10-06 10:28:17   576   1   63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110

Before this block all blocks have size >17,000 bytes, which means all pools have honest code before this point of time (CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE with value 20000)

http://chainradar.com/dsh/block/63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110

Proof that the block is Minergate's:
https://minergate.com/pool-stats/dsh/23491
Search for   63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110

3. Minergate used correct code before 2014/10/06 10:28:17
Here is a Minergate's block just 2 blocks below the first strange block I showed above.

67225   14-10-06 10:28:17   576   1   63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110
67224   14-10-06 10:28:43   27286   3   87e8bd5e525649322ed3e5a7d582629917353b06680ba4c035736c03d6834a40
67223   14-10-06 10:17:47   23295   4   4e2dad2aa98dab526f9ea269c0d6dc0388ebb20af159e95c71df3f0bcd8bfdbe

Proof that the block is Minergate's:
https://minergate.com/pool-stats/dsh/23491
Search for   4e2dad2aa98dab526f9ea269c0d6dc0388ebb20af159e95c71df3f0bcd8bfdbe

How this is affecting the network:
1. Transactions with >10000 bytes will break with frequency, related to how much of the hashrate Minergate controls. This produce a snowball effect - the more failed transaction - more people goes to Minergate, because the other pools cannot send transactions.
2. The higher number of transaction failed leads to the constant need of reset and cache delete.

How to act:
DO NOT MINE AT MINERGATE
To improve the effective transaction median and reduce the rejected transactions, we must put Minergate's hashrate percent to minimum as possible until they fix their daemon.

Spread the hashrate between pools
Lets don't make the same mistake again and give so much power to a single pool.

Make sure you are running dashcoind with version 1.0.2

dashcoind --version

The fact that Minergate had a version with CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE 20000 before their version with value 10000 makes me almost certain this is not a simple mistake.

okay...moving my miners off mg.

but can you tell me how sending large amounts from mg seems to work almost all the time and i struggle with amounts 10x smaller from simplewallet given they reduced this parameter? i've was able to send 3 separate 24M DSH txns from there that arrived within a very short period of time when my 2M DSH txns from my simple wallet would take hours if not a day to get there

[slb]

I think i messed up when trying to send coins to myself...

transfer 0 address 100000
Money successfully sent, transaction <txnumber>

They didnt show up in my wallet afterwords...any ideas?

See FAQ:  http://dashcoin.net/faq/
"My transaction says sent, but it never showed up."

okay...moving my miners off mg.

but can you tell me how sending large amounts from mg seems to work almost all the time and i struggle with amounts 10x smaller from simplewallet given they reduced this parameter? i've was able to send 3 separate 24M DSH txns from there that arrived within a very short period of time when my 2M DSH txns from my simple wallet would take hours if not a day to get there

Long story short:

* Your daemon is programmed to sends transactions up to 20,000 bytes
* Minergate is programmed to accept and send transactions up to 10,000 bytes
* Minergate controls big chunk of the network
Result:   Transactions in range 10,000 - 20,000  have hard time to pass

If an attacker flood the network with transactions just over 10,000 bytes (like 10,536 bytes or 11,057 bytes), it makes practically impossible for real transactions over 10,000 bytes to pass.

The transaction size depends on the number of inputs, outputs (payees), and mixin. You can easily have a transactions for amount 10,000DSH with size 12,000 bytes   and in the same time you can easily have a transaction for amount 5,000,000DSH with size 3,000bytes.

[lostisland]

I think i messed up when trying to send coins to myself...

transfer 0 address 100000
Money successfully sent, transaction <txnumber>

They didnt show up in my wallet afterwords...any ideas?

See FAQ:  http://dashcoin.net/faq/
"My transaction says sent, but it never showed up."

okay...moving my miners off mg.

but can you tell me how sending large amounts from mg seems to work almost all the time and i struggle with amounts 10x smaller from simplewallet given they reduced this parameter? i've was able to send 3 separate 24M DSH txns from there that arrived within a very short period of time when my 2M DSH txns from my simple wallet would take hours if not a day to get there

Long story short:

* Your daemon is programmed to sends transactions up to 20,000 bytes
* Minergate is programmed to accept and send transactions up to 10,000 bytes
* Minergate controls big chunk of the network
Result:   Transactions in range 10,000 - 20,000  have hard time to pass

If an attacker flood the network with transactions just over 10,000 bytes (like 10,536 bytes or 11,057 bytes), it makes practically impossible for real transactions over 10,000 bytes to pass.

The transaction size depends on the number of inputs, outpouts (payees), and mixin. You can easily have a transactions for amount 10,000DSH with size 12,000 bytes   and in the same time you can easily have a transaction for amount 5,000,000DSH with size 3,000bytes.

Thanks!

[nopedope89]

I have some finding about the recent transaction problem. I knew what was the problem when I fixed my test pool - transactions with size bigger than 10,000 bytes were hardly accepted in the blockchain. I took my investigation further and here are my finding:

1. Minergate uses old or modified code:

First of all, I use the latest version of dashcoind from 16 Sep on my pool. Here is the --version output:

Code:

> dashcoind --version
2014-Oct-20 10:18:48.631403 Starting...
2014-Oct-20 10:18:48.633060 dashcoin v1.0.2.358()
dashcoin v1.0.2.358()

2. Minergate started to use this code on 2014/10/06 10:28:17
I looked at the blockchain for odd blocks and they started to appear here:
http://chainradar.com/dsh/blocks/2241/30

67225   14-10-06 10:28:17   576   1   63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110

Secondly the statement that MinerGate has moved to modified daemon code on 10/06/2014 is totally incorrect. CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE represents a base median value of block total transactions size and can be shifted forward. As you can see the current median of 63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110 'malicious' block equals 23,142 bytes, which means it can contain up to 23 Kb of transactions. Real block size depends on the daemon's tx pool state - the mining pool have nothing to include into the block if it is empty. So, since this isn't correct, the remaining statements are incorrect also.

Lastly - for whose benefit? Please answer what my pool will gain from this potential modification?

[mitache365]

how much must be the price for a BTC market?

[crypto_currency]

how much must be the price for a BTC market?

300 XMR satoshi+

[1 1 0 0 1 1 1 0 0 0 1]

Not sure what's going on with the new wallet today.  Last night it was working okay.  It let me send a 1 million dash at a time to poloniex.  Today I can't even send over 1000 dash.  I've restarted the wallet several times.  Any help?

[Rantzbitz]

how much must be the price for a BTC market?

The moment we can get the price stable above 300XMR for a good period of time a btc market at Poloniex will be added im sure.

[DenisZabar]

Not sure what's going on with the new wallet today.  Last night it was working okay.  It let me send a 1 million dash at a time to poloniex.  Today I can't even send over 1000 dash.  I've restarted the wallet several times.  Any help?

+1

[pwstegman]

Not sure what's going on with the new wallet today.  Last night it was working okay.  It let me send a 1 million dash at a time to poloniex.  Today I can't even send over 1000 dash.  I've restarted the wallet several times.  Any help?

+1

This shouldn't be an issue with the wallet, but rather with the network.  See slb's last post on the issue with large transactions for an explanation.  If however, when you say the wallet is not working, you mean the wallet is throwing errors, then please post whether you were using the wallet command line version or the GUI, and the exact error message it gave.

[PestoQuinty]

Not sure what's going on with the new wallet today.  Last night it was working okay.  It let me send a 1 million dash at a time to poloniex.  Today I can't even send over 1000 dash.  I've restarted the wallet several times.  Any help?

+1

This shouldn't be an issue with the wallet, but rather with the network.  See slb's last post on the issue with large transactions for an explanation.  If however, when you say the wallet is not working, you mean the wallet is throwing errors, then please post whether you were using the wallet command line version or the GUI, and the exact error message it gave.

I just sent 8mil coins in a single transaction (to Polo) with 15DSH fee without problems with your wallet.

[DenisZabar]

Not sure what's going on with the new wallet today.  Last night it was working okay.  It let me send a 1 million dash at a time to poloniex.  Today I can't even send over 1000 dash.  I've restarted the wallet several times.  Any help?

+1

This shouldn't be an issue with the wallet, but rather with the network.  See slb's last post on the issue with large transactions for an explanation.  If however, when you say the wallet is not working, you mean the wallet is throwing errors, then please post whether you were using the wallet command line version or the GUI, and the exact error message it gave.

Here it is :
2014-Oct-21 00:27:40.789409 [P2P7]Transaction with id= <3ad87bb05cd580f338443c4e0e7feec72a4b4ff22bca85fd11adead7e08d84d8> used already spent inputs
2014-Oct-21 00:27:40.789409 [P2P7]Transaction verification failed: <3ad87bb05cd580f338443c4e0e7feec72a4b4ff22bca85fd11adead7e08d84d8>
2014-Oct-21 00:27:40.789409 [P2P7][176.9.47.243:7280 OUT]Tx verification failed, dropping connection

[pwstegman]

Not sure what's going on with the new wallet today.  Last night it was working okay.  It let me send a 1 million dash at a time to poloniex.  Today I can't even send over 1000 dash.  I've restarted the wallet several times.  Any help?

+1

This shouldn't be an issue with the wallet, but rather with the network.  See slb's last post on the issue with large transactions for an explanation.  If however, when you say the wallet is not working, you mean the wallet is throwing errors, then please post whether you were using the wallet command line version or the GUI, and the exact error message it gave.

Here it is :
2014-Oct-21 00:27:40.789409 [P2P7]Transaction with id= <3ad87bb05cd580f338443c4e0e7feec72a4b4ff22bca85fd11adead7e08d84d8> used already spent inputs
2014-Oct-21 00:27:40.789409 [P2P7]Transaction verification failed: <3ad87bb05cd580f338443c4e0e7feec72a4b4ff22bca85fd11adead7e08d84d8>
2014-Oct-21 00:27:40.789409 [P2P7][176.9.47.243:7280 OUT]Tx verification failed, dropping connection

First rename wallet.bin to wallet.old.bin, and then open the wallet "wallet.bin".  The wallet will say it cannot find "wallet.bin" (as it was renamed), and it will begin to resync the wallet.  When that is done, try to send the transaction again.

If the above does not work, then rename wallet.bin to wallet.old.bin, and then go to %appdata%/dashcoin, and delete blockscache.dat, p2pstate.bin, poolstate.bin.  Open the daemon, and wait for the blockchain to resync.  Then, open simplewallet, and open "wallet.bin".  It will say wallet.bin cannot be found (as it was renamed), and it will begin to resync the wallet.

Once you are done, and the wallet is working again, you can safely delete wallet.old.bin.

[superresistant]

 
Is Dashcoin alive ?

EDITED

[anonimus]

Is Dashcoin alive ?

Do you guys hate Monero or something ?

We can like dsh, xmr, bcn, etc.

Personally i like criptonote coins.

Why do you think everybody hates monero?

[superresistant]

We can like dsh, xmr, bcn, etc.
Personally i like criptonote coins.
Why do you think everybody hates monero?

I just removed the question. It's not important.

[pwstegman]

Is Dashcoin alive ?

EDITED

What makes you think it's not?  A lot has been going on, just look through the thread.

[arielbit]

dash is alive of course, what i like about it in the beginning was it tried to be as cheap as possible traded at a otc thread and a sub satoshi exchange.

mined with nvdia and amd gpu, cpu, windows and linux....released when miners are optimized..no question about fairness.

right now it is still very cheap, at less than 2 btc you can have a billion dsh.

in time maybe dash will be independent from bytecoin development..might change to POS after all coins are mined like XDN..who knows, i'm keeping a few millions long term.

edit: and there are active devs

[crypto_currency]

DSH is the only coin that I think worth mining currently.