Topic: [DSH] Dashcoin (Cryptonote, automated source) - page 26. (Read 216695 times)

how much must be the price for a BTC market?

how much must be the price for a BTC market?

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:

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

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


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.

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

transfer 0 address 100000
Money successfully sent, transaction

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

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

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:
Here is what they probably use:

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
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.

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

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.

I released Subtoshi about a month and a half ago, so Dashcoin could be traded.  Dashcoin has since been listed on Poloniex, and the trade volume on Subtoshi has dropped.  As of now, Subtoshi is costing me more to run than it is bringing in.  I am glad that Subtoshi was able to get Dashcoin trading going, but now that trading has died down, and for the reasons I stated before, I have decided to close down Subtoshi.  Thank you to everyone who used Subtoshi. I hope it provided useful.

The plan for Subtoshi's closing is as follows
Deposits will be disabled on October 26th, a week from today.
Trading will be disabled on October 31st.
After that, the exchange will remain open for withdrawals until December 31st.

I will have a more official announcement later on the website, and will be sending out an email regarding the closing of Subtoshi to everyone who has registered.

Something wrong with the GUI wallet,it crashed and pop up a window saying running time error.

The Dashcoin Wallet GUI is here! Right now it is Windows only.  Mac and Linux builds will come later.  You can download it here:

http://sourceforge.net/projects/dashcoinwalletgui/files/latest/download

This version contains the following features.  It will be updated as more features are added:

• Syncs blockchain with network
• Can load/generate a wallet
• Loads balance
• Loads address
• Lists transaction history (sends and receives)
• Can send Dashcoin

Github: https://github.com/pwstegman/DashcoinWalletGUI

To import an already existing wallet, copy wallet.bin, wallet.bin.address.txt, and wallet.bin.keys to the same directory as the wallet GUI.  Rename the files to wallet.bin, wallet.bin.address.txt, and wallet.bin.keys if they are not already named that.

I expect to complete the script for sending the payments later today or tomorrow. I already automated the process of getting the failed transactions and I am halfway through sending.

So what about transactions that never made it from pools like extremepool or even democats (or any of the open source pools)? Will those failed TXs ever be resent to miners that never received them or is it a manual process? I know extremepool won't be doing any manual payouts like that for me, I already asked. Between extremepool and democats I never received >50M DSH that should have made it to me.

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: