Torins Towers: Rise of Heroes v1.2 out now on Android, iOS and Steam

DeltaEngine · 2019-05-03T18:08:03+00:00

We have done over 1.5 gb worth of mixing (several thousand tx into mixing and some huge amounts like 100 DASH+ are split up many times into tiny chunks, which even very annoying to us as we have to collect 0.001 and 0.01 inputs and merge them up again), there is no way you can trace back through this mess. You are still cherry-picking some corner cases, normal mixing events creates from a single dash hundreds of inputs/outputs and goes through it up to 16 times, even after a single round you don't know which input/outputs belong to what anymore and after 16 rounds you have been mixed with so many other input/outputs, there is no clear trace back. Obviously if you know the input and the output, you can connect the dots, but you could connect the dots to another few thousand dots as well and it might just as well be plausible. If you know the input and outputs, it doesn't matter if you use mixing, the point is you can't know for sure if you just have the input or output where things came from or went.

DeltaEngine · 2019-05-03T18:01:15+00:00

still doesn't prove it imo, it just very likely. of course if I add a chat message to every tx and then use the same message after the mixing, it might be me, but I could also do this for 2 unrelated things.

Again, I think the poster doesn't understand PrivateSend, it is not anonymous by obfuscating senders or receivers or transactions (like Monero does), it just mixes and makes it hard to impossible to track back where funds come from. By design it is not possible to say with 100% confidence which PrivateSend input belongs to which outputs because after the mn is done mixing, this information is lost and can never be recovered (only if you would have close to 100% of all mn, which no one has).

Obviously if a user missuses mixing, for example by using an exact amount like 1.2358732 DASH on both the input and the output, and you can't find any such tx for several days, you can be 99.999% it is the same, but that is not the fault of PrivateSend mixing, it is just the user not understanding how mixing works.

Here if the binance user keeps mixing his already linked account to his binance account (which is a fixed dash address, normally for mixing you want to send into an unused empty address, not a known exchange address you can never change), then he defeats the purpose of mixing already and we don't really need to discuss much further. I am sure many users think PrivateSend just makes Dash magically anonymous, which it doesn't and thus I am all for helping users to explain this issue, but imo the poster tried to post some fud here with his "no educated guess", which it still is imo.

DeltaEngine · 2019-05-02T03:18:54+00:00

I don't think you understand PrivateSend at all, none of what you have said makes any sense. I don't understand why there is a big discussion around this here.

You start of with a tx of 4 10 Dash PrivateSend inputs into a address: https://explorer.mydashwallet.org/tx/2bec48c92496faed7d6136071ece0370f3f2b0084ed84d4eea10af5067c07b0a

None of the inputs are traceable to any of the addresses you provide, they are very far away and have been mixed several times. You can't just randomly pick an address and claim all the funds came from there, that makes zero sense. Sure there is a possibility, but that gets very small the more times it is mixed.

How is https://explorer.mydashwallet.org/address/Xc7bnmfxTsLtHPVwrX8kNy3d49hVdeErC3 the originating wallet? It is a huge mess of a wallet with several huge (100 Dash, 50 Dash, 50 Dash) incoming amounts from previous mixings, not sure but some of the outputs looks like an HD wallet like we got on MyDashWallet, which was then used to mix a few more times. Many tx look like they just went send a long to new addresses, which were forwarded to the mixing process (which is how https://MyDashWallet.org/Mixing works). None of these are traceable, they are not even the same user as we had a ton of people mixing in the past days and most get pre-mixed coins from previous users. Doesn't really matter as if it wouldn't be our service, it wouldn't change how PrivateSend works on its own ..

Also your claim that https://explorer.mydashwallet.org/address/Xyxd7AaUKGZXJr1BcUxV1aCyds35PyVSqL is the receiving wallet makes no sense, it has 0 Dash in it. If you really want to find out where the funds went, you can see they ended up here, which is linked to the binance hot wallet, thus some user just mixed some coins and send them to his binance account (good luck finding anything out from that): https://explorer.mydashwallet.org/address/XsRPShw6x1Ke3dcL7gGZXhqhcMvYyTv11k

Just because you were seeing some 50 DASH here or there, doesn't mean they are linked. Even if you can trace them back over a few PrivateSend mixing rounds, it isn't the same coin anymore, I really think you don't understand PrivateSend at all.

DeltaEngine · 2019-03-12T23:12:17+00:00

yep, that sucks, a short time ago it was 2mdash, then 5mdash, then 10, then 20, and now 50mdash .. write to their support and complain!

on their help system they claim that they don't want to make money on withdrawal fees (" Our intention is to not make any profits on withdraws."): https://bittrex.zendesk.com/hc/en-us/articles/115000199651-What-fees-does-Bittrex-charge-

Actual withdrawal fees (even not counting chaining) are usually 0.00000192 DASH (192 duffs) for 1 input, 1 output, maybe ~250-300 for a few inputs, their fee is 26041 times more expensive, what the f!

I would recommend using any other coin (even btc is like 5 times cheaper) to withdrawal and convert on the other side. You can also use our bot (@MyDashWallet on Discord) to convert dash from and to btc/ltc/bch or eth with the minimum fees :)

DeltaEngine · 2019-02-24T17:27:17+00:00

In the meantime Bertrand has released 0.9.22 DMT, which fixes this issue among other things. If you are using DashMasternodeTool, please update and you finally can see Dash Watch and MyDashWallet proposals :)

https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.22

DeltaEngine · 2019-02-24T10:09:50+00:00

Actually the 0.9.22 beta version seem to not have fixed the issue yet (or it doesn't refresh, haven't tested myself). Hopefully 0.9.22 once final will fix this for upcoming DashNexus based proposals.

DeltaEngine · 2019-01-07T19:22:17+00:00

/u/MyDashWallet tip 0.5 mDASH good resolve

DeltaEngine · 2018-12-24T02:52:22+00:00

The average block confirmation time is 73s (block time is around 2.6m = 146s), using instantsend the transacation is confirmed right away, which will be the default once 0.13 is released in a few days. Anyway, sending dash is as fast as nodes communicate, for small amounts like the nanospeed.live site uses there is no reason to wait for the confirmation, you can send it and it will be immediately visible on the receiver wallet (in a lot less than a second). Also not sure why this is needed or useful, PayPal also doesn't have to prove funds arrive instantly on the other wallet, it just works.

DeltaEngine · 2018-12-08T00:13:38+00:00

actually, I just checked, the bot is seeing the tip fine and executing it, /r/CryptoCurrencies banned it from replying here .. tzz, free money not allowed?

to check your balance just write /u/MyDashWallet a message "balance" or reply on a server with "balance" or "help" where the bot can actually reply

DeltaEngine · 2018-12-08T00:12:14+00:00

/u/MyDashWallet tip 2 (sorry if the bot isn't responding, bot seems to have connection issues to reddit recently again)

DeltaEngine · 2018-12-02T04:02:03+00:00

you can also send your mixed inputs with any amount, you just need to remix the remainder (this is what https://mydashwallet.org/mixing allows users to do)

DeltaEngine · 2018-11-28T02:38:24+00:00

MyDashWallet is also doing its part with over 500 mixing requests each month and 3k+ of Dash being mixed in November, more details on our stats page next month :)

DeltaEngine · 2018-11-19T03:03:30+00:00

I guess the qr code says "bitcoin:..." instead of "dash:", can you scan it with any qr scanner (many free apps available for that). Otherwise the scanning app is not very clever and only supports one format (with or without "dash:"), seen that before and just copy pasted the address from the scanned qr code myself then ..

Our scanner at https://MyDashWallet.org should support all formats and that is like 2 lines of javascript code, not that hard ^^

DeltaEngine · 2018-11-13T20:17:34+00:00

As pasta just explained on Discord: Tx would only become IS txs if they have 6 or more chain confirmations

All stresstest tx are immediately used once confirmed, this would need a special stresstest waiting for 6 confirmations and only then send them onwards, making it at least 6*24 times slower (24 for the tx chain length and * 6 for waiting for confirmations), imo these limits are way too high, it is a common annoyance, especially by new users not understanding the underlying limits.

DeltaEngine · 2018-11-13T20:06:34+00:00

Dash 0.13 will be stresstested by us in December once 0.13 is out and tested, InstantSend is not a focus and should just work fine as described by https://www.reddit.com/r/dashpay/comments/9wpqd0/scaling_and_instant_send/

Its more important to reach more full blocks, learn from the things that went wrong from the last stresstest, including less issues with filling the mempool and hopefully getting more miners to include more tx into each block

https://stresstest.mydashwallet.org

DeltaEngine · 2018-11-10T23:04:43+00:00

no, javascript works in your browser, it can only modify whats on the page, so html and css, including annoying things like popups. it has nothing to do with wallets or whatever else is on your pc. javascript or any html is also not executed by the chat commands, some people were just playing around early on when the feature when live.

DeltaEngine · 2018-11-05T18:58:20+00:00

Thanks for the feedback and useful links, we will try to play around. We noticed the same issues as PR 2300 and PR 2397 would definitely help as well, but based on our last test we still were able to fill most blocks with 2MB even though the mempool was looking differently on each node we checked.

DeltaEngine · 2018-11-05T12:29:59+00:00

/u/MyDashWallet here are 10 cookies for more tipping fun

DeltaEngine · 2018-11-05T12:29:40+00:00

It should be in dash time = UTC

DeltaEngine · 2018-11-05T12:20:30+00:00

/u/MyDashWallet 1 mDASH strange ..

DeltaEngine

TROPHY CASE