I wanted to add a little sidenote to this remark: those 14 days are not set in stone... They're not part of the bitcoin protocol.

There is no cental mempool, every node keeps unconfirmed transactions in it's own mempool for a certain amount of time. The default setting of bitcoin core nodes is 14 days (at least, it used to be 14 days IIRC), but every node can chose to set a higher or lower amount of time. Also, there are other node implementations (and i have no idear what their default setting is). On top of this, the mempool also has a maximum size, if it's full, transactions will be pruned from the node's mempool (so it's possible at times of mempool congestion that your tx is dropped from most mempools after less than 14 days).

Bottom line: after 14 days, an unconfirmed transaction will be dropped from the mempool of the majority of the nodes, but defenatly not all of them. It's possible to see a transaction be dropped from most mempools after 14 days, but still see it end up in a block after 31 days if the mining node was running with a non-standard setting... So, by just recreating the transaction without looking at the unspent outputs that were used in the dropped transaction, it's possible the receiver will end up being payed twice. This is why it's a good idear to re-use the same unspent output when re-creating a transaction that was dropped from most mempools...

It might sound really technical, but it's important to know the difference

Well, you asked for tips  

1) I've never heared about the wallet you're using... I have no idear if it's a desktop wallet or an online wallet, or how it works or what their feature set is... Maybe it's a good idear to switch to a more common wallet instead? Electrum gives you the option to customise your fees and it has opt-in rbf and CPFP built in to the gui. This means electrum is well equiped to give you complete controll over your fees (while giving you all the information you need to make the decission) AND it's setup to help you get transactions unstuck by bumping the fee (with opt-in RBF tx's) or by creating a CPFP (in case you're the receiver, or if you opted out RBF). Wasabi wallet is another good alternative with a similar feature set (at least when it comes to not getting your tx's stuck). Both wallets can be coupled to the most popular hardware wallets to, so if you ever decide you need more security, you won't have to climb a new learning curve since you can just use a ledger or a trezor hw wallet using exactly the same electrum or wasabi gui.

2) instead of thinking in dollars and euro's, think in transaction size. The fee is calculated in satoshi per vByte... Not in satoshi per transacted FIAT equivalent

3) learn how to use sites like this one: https://jochen-hoenicke.de/queue/#0,24h . If you have opted in rbf and you use a wallet that shows you the transaction size and lets you pick the fee, this site helps you to set the correct fees

4) learn that, as long as there is trust between the sender and the receiver, nothing really bad can happen. A transaction either confirms, or it gets pruned from the mempool of most nodes after a couple of weeks... As long as there is trust between the sender and the receiver, the worst that can happen is that the sender has to re-send the funds after a couple of weeks... As long as you both have controll over your wallets, and you used the correct addresses on the correct network, nothing really bad can happen. Things are different when you pay somebody and there's a time limit (like for example, if you pay in an online shop): in this case you might want to overpay a little, so you don't get into troubles if your tx doesn't confirm on time.

I don't really get what you're trying to say here...
Fresh coins = coins coming from a coinbase reward, coins without history... This is basically the unofficial defenition of fresh coins... You already understood this from the start, since you initially said you were working with russian and chinese miners.

I personally think that somebody could make a lot of money selling the unspent outputs from a coinbase reward at a higher profit margin... The thing is: if you promise fresh coins, you have to deliver fresh coins, not start telling us the coinbase rewards are hidden, mixed, aged,... This means nothing to us, fresh = fresh, not mixed, split up, aged, hidden,.... Some of these things don't make any sense at all, hence i label them "smoke and mirrors" (in other words: a clever way of distracting people by dragging in a lot of technical details newbies might not comprehend).

Age does NOT come into this equation by the way. Like i said in my previous post: if Satoshi himself would sell the coinbase reward of one of the first couple of hundred blocks he mined 10 years ago, the unspent output funding the buyer's address would only be 1 step away from a coinbase reward, hence it would be called "fresh" by any definition of the word. Fresh has nothing to do with age, but only with the distance between the analysed unspent output and the unspent output generated as a coinbase reward.


I don't really have a suggestion... The thing is: you can not, under any circumstances promise to dispense "fresh coins from russian and chinese mining farms" but then send somebody funds that are in no way coming from any mining reward dozens of levels deep. It's just that simple...

If you open up a butcher shop and you sell only pig's meat, you cannot sell (cheaper) chicken's meat instead. You said you were selling pig, when i get the meat i bought from you analysed, it better be coming from a pig. If it's chicken, the exuse that the chicken was fed some expired pig's meat a week ago will not stand.
You are selling fresh coins, so they'd better be fresh. If not you'll need to rebrand your operation. The blockchain is an open ledger. Anybody can parse all the blocks and follow the trail of unspent outputs. If you twist the truth, you'll get caught.
There's a market for a normal mixer, there is no shame in being one... There probably will be a market for somebody that doesn't want his mixing output coming from other clients of your mixer.... There's probably a market for people that want to be payed using funds that can be directly linked to coinbase rewards... Just see which category you fit in and tell the truth... That's the only way you'll have a sustainable business. If you twist the truth, you'll start getting negative trust on bitcointalk and other forum's, you'll get negative reviews on many platforms, you'll get negative messages on twitter, reddit,... and you'll only get a handfull customers a day.


I see you didn't answer a single one of my questions, so i'll ask them again... Could you please provide an answer?

• Do you stand by your claim that says you're providing fresh coins?
• Do you understand that, in the bitcoin world, fresh means: "coming from a coinbase reward"?
• Is TryNinja telling the truth when he posted the withdrawal transaction id?
• Do you see a flaw in my logic when i dug 5000 of the closest transactions funding TryNinja's output and only found 2 very distant coinbase rewards adding allmost nothing?
• Do you see a flaw in my logic when i calculated that only 0,000000000000000019% of the value funding TryNinja's "clean" addresses comes from a coinbase reward from the 5000 closest transactions funding those clean addresses?
• Are you still unwilling to let your partners prove they are real miners by mining a block using a new address as a coinbase reward without adding an identifying OP_RETURN and sign a message using this new address (so there is no way to identify them?)
• Last time, i identified the 2 blocks that could very remotely be linked to TryNinja's output to be coming from 1THash&58COIN. Are they your partners?
• Apparently, in a PM to Vod, you claimed to have "a way of sending coin without revealing the sending address". If this is true, you should share the technical details... If it's just security trough obscurity you are NOT protecting your clients. Only by sharing technical details, we can asses if the method you claim to have discovered is valid, and will keep on protecting your clients in the future. If you are unwilling to give the method, i can only assume it does not exist, or it's a method that will sooner or later be discovered by others that can then use it to de-anonimise your past clients
• Do you understand that, when you say you have 50 BTC but proof nothing, we are a big sceptical?
• Do you understand that, when you say you have 50 BTC but your site tells us you have >5000 BTC, you are putting complete trust in the hands of your partners? What if somebody initialises a 100 BTC mix and your partner's api is not completely working (or then ran away), you'll be standing there unable to provide a mix eventough you promised to do so?
• Once again: are you the developer or are you defending somebody else's script?
• Once again: do you understand all the technical details of your operations or did you pay somebody else to do it for you?
• Once again: why are the security headers not yet fixed
• Why do you run an nginx version with known vulnerability's
• Why do you include external javascript

you can have a copy of the script i run on my tbtc testnet faucet... This being said, you'll probably have to add some extra features and security checks if you want to run it on the main net to avoid abuse.

https://tbtc.mocacinno.com/

You're free to send me a PM if you're interested (i won't give any support tough, so it's just the python backend, the php frontend and the database scheme... everything else you need to work out on your own)

I'm a dog with a bone, not a genius
I'm trying to protect this community, that's all...

By the way: you're telling me you thank me for the analysis, but don't address the main issue that was proven by this analysis....


Okay... Let me give you the ELI5(~ish), TL;DR; version...
Let me be clear from the start: I found a flaw in the safety of your mixing. I kindly discuss. This is more important to you than (well... you never said than what it was more important). Anyways, it's important to me to protect the community, so that should be enough motivation. Please read in full and understand my findings and questions before you answer... If not, your answer will be incomplete or unfunded.

Please, respond giving evidence... Tell me where i'm wrong... Show me the flaws in my way of thinking... Point out where exactly you have those fresh coins... I'm not a deity, i can make mistakes... I can overlook things, i can make calculation errors, i can have wrong assumptions... My script can have bugs, my graphs can be incorrectly interpreted. It's up to you (the business owner) to point out these flaws in order to regain the trust of your potential customers and not drive them away with smoke and mirrors. Since we're working with a technology that's clear, open source and well described, you should be able to do so using hard facts.

My concrete questions... could you answer them to stop this discussion once and for all?:

• Do you stand by your claim that says you're providing fresh coins?
• Do you understand that, in the bitcoin world, fresh means: "coming from a coinbase reward"?
• Is TryNinja telling the truth when he posted the withdrawal transaction id?
• Do you see a flaw in my logic when i dug 5000 of the closest transactions funding TryNinja's output and only found 2 very distant coinbase rewards adding allmost nothing?
• Do you see a flaw in my logic when i calculated that only 0,000000000000000019% of the value funding TryNinja's "clean" addresses comes from a coinbase reward from the 5000 closest transactions funding those clean addresses?
• Are you still unwilling to let your partners prove they are real miners by mining a block using a new address as a coinbase reward without adding an identifying OP_RETURN and sign a message using this new address (so there is no way to identify them?)
• Last time, i identified the 2 blocks that could very remotely be linked to TryNinja's output to be coming from 1THash&58COIN. Are they your partners?
• Apparently, in a PM to Vod, you claimed to have "a way of sending coin without revealing the sending address". If this is true, you should share the technical details... If it's just security trough obscurity you are NOT protecting your clients. Only by sharing technical details, we can asses if the method you claim to have discovered is valid, and will keep on protecting your clients in the future. If you are unwilling to give the method, i can only assume it does not exist, or it's a method that will sooner or later be discovered by others that can then use it to de-anonimise your past clients
• Do you understand that, when you say you have 50 BTC but proof nothing, we are a big sceptical?
• Do you understand that, when you say you have 50 BTC but your site tells us you have >5000 BTC, you are putting complete trust in the hands of your partners? What if somebody initialises a 100 BTC mix and your partner's api is not completely working (or then ran away), you'll be standing there unable to provide a mix eventough you promised to do so?
• Once again: are you the developer or are you defending somebody else's script?
• Once again: do you understand all the technical details of your operations or did you pay somebody else to do it for you?
• Once again: why are the security headers not yet fixed
• Why do you run an nginx version with known vulnerability's
• Why do you include external javascript

So, here's the TL;DR; part:

• We are talking about bitcoin.
• Bitcoin uses a decentral ledger that contains (in parsable form) an unambiguous list of transactions. Each transaction uses unspent outputs as an input and creates new unspent outputs as an output (unless it's a coinbase transaction, this one only creates a new unspent output without having an input). This creates a possibility to follow the trail of unspent outputs BACK to the "fresh coins".
• It's ALWAYS possible to follow the trail of unspent outputs back to the point of the coinbase transactions... if an unspent output is still in the UTXO, it might (in some cases) technically be possible to hide who will be able to spend this utxo, but once it's spent we can always follow the trail
• I dug 5000 hops deep from the transaction funding TryNinja's mixing output¹⁺². You promise fresh coins, 5000 is waaaaay over the top, but my initial tests with a reasonable amount of hops turned up nothing interesting so i dug deeper... I'd expect fresh coins to pop up a maximum of 3 or 4 steps away if you're saying they're fresh.... Mind you: steps... Aging does NOT come into play. Satoshi's addresses were funded with coinbase rewards >10 years ago. If he's spend those coinbase rewards today, there would only be 1 step between the coinbase reward and the address funded by spending the coinbase reward eventough the coinbase reward was added to the utxo set 10 years ago. Aging is not a factor here.
• I was able to proof that there were only 2 coinbase transactions in these 5000 hops, they were 17!!!!! steps away.
• 2 coinbase transactions in 5000 hops 17 steps away is NOT good... As a reference, i scanned 500 hops for the last transaction funding my own public address, and i found 47 coinbase transactions, some of them 6!!!! steps away³. Mind you: this wasn't result of a mix or some promise to get payed with "fresh" coins... It was just a signature payment (IIRC), so i'd even expect the coins to be "dirtyer" than "average" coins (yeah, i know, dirtyer and cleaner are just terms... fungibility is the key here, but still a promise of fresh coins is a promise of fresh coins).  Also, realise that for your funds i went 10x deeper, so I should have turned up 10 times more, not 23 times less coinbase transactions.
• A small calculation can proof⁴ that ony 0,000000000000000019% of TryNinja's funds could VERY remotely be linked with a coinbase transaction in the 5000 closest transactions leading up to his transaction. Don't tell me this is by design. If your mixer created hundreds of transactions to hide the source of the funds for just a handfull of clients, you wouldn't be charging a 3% fee. Each of these hops has a price, both in tx fees, hardware resources and time... No way you tumbled these funds hundreds of times to payout a couple clients.
• Sure, if i'd go 50.000 or 100.000 hops, or 10.000.000 hops, we'd probably end up with a lot of coinbase transactions... But it would be more than a stretch to call them "fresh". When the network started, there was nothing. Every unspent output can ultimately be traced back to a coinbase reward if you dig deep enough... This doesn't mean they are "fresh" tough

Now, once again: i'm not saying that your mixer is bad per sé... I'm just saying that many of your claims (like the "fresh coins" claim) are provably false or at least very shaky and unproven (not unprovable, but unproven)...
Sure, there is fungability, and the most important part of a mixer is breaking the link between two wallets. It's very well possible your mixer is doing exactly this... I didn't dig into those transactions funding your output wallet... I have focussed on the "fresh coins" promise, and i think i succesfully proved this is not the case.
A 5000 node search should have turned up more than 0,000000000000000019% of the funds coming from a coinbase reward. If you'd open up a bar and you used the same percentage to dilute your whiskey, you'd be filling a bathtub (158 liters) with tap water and then adding  0.03 femtoliter of whiskey... That's basically just opening a whiskey bottle a couple of centimers above the water surface and closing it up right away... Do you think your customers would be happy if they ordered a whiskey and they got a small glass of water from a bottle that has been standing next to a whiskey bottle for a couple of hours? I, for one, wouldn't be to happy about this, even if you said that all water was once whiskey that got pissed out and filtered by nature at one point in it's life, or if you started to explain how exactly you opened the whiskey bottle and how long it stood next to the water bottle before you sold me tap water as being whiskey...

---

---

---

Details:
Source 1
here's the sourcecode of the script I wrote, so you can check it out for yourself:
https://github.com/mocacinno/howfarfromcoinbase/


Source 2
a nice graph showing just how far those coinbase rewards are from TryNinja's withdrawal... Mind you: everything not in the path between the coinbase rewards and the withdrawal tx has been pruned:
Tryninja-coinbase
(the image is so big i decided to create a link)


Source 3
As a comparison: the last unspent output funding my public address... Uncleaned, no promises of "fresh" coins. Mind you: everything not in the path between the coinbase rewards and the withdrawal tx has been pruned:
mocacinno-coinbase
(the image is so big i decided to create a link)


Source 4
Now, compare it to
tx bdfbfee25cd935abb128fc632faa9a105d0ae7b6d1ab32b8cc15e452ce2372af spends the coinbase unspent outputs:
IN : 30.40966025 BTC
IN(coinbase): 13,44039925 BTC
%(coinbase) = 13,44039925/30.40966025 = 44,2%
We continue with the unspent output funding address 3FToeoKAHiPPGmPP3V61JukhVkGttyWsau with 0.02090359 BTC
This means, 0.02090359 * 0.442 = 0.01 BTC is coming from the coinbase rewards at this point (and i'm rounding upwards here...)

the next tx: 9a2ec09aa7ada4c581e8b36d5ff56e09b784c547d7e11e9b8d01d03b5fa145e6
IN : 9.73792545 BTC
IN(coinbase): 0.01 BTC
%(coinbase) = 0.01/9.73792545 = 0,00103%
We continue with the unspent output funding address bc1q6f7usdrwhldsmjlagyw3xqxlm5r30ac8vzuds3 with 0.00721000 BTC
This means, 0.00721000 * 0,0000103 = 0,0000000743 BTC is coming from the coinbase rewards at this point (and i'm rounding upwards here...)

the next tx: 60efc87dd0d3630b24f12785aae3eaac05e494f6e98a9e54d295c0f6e1ae366f
IN : 0.00679735 BTC
IN(coinbase): 0,0000000743 BTC
%(coinbase) = 0,0000000743/0.00721000= 0.0000103%
We continue with the unspent output funding address bc1q386274dh4ggx8qh4xplwevk3s406dpk6xasqpq with 0.00002130 BTC
This means, 0.00002130* 0.000000103 = 0.0000000000022BTC is coming from the coinbase rewards at this point (and i'm rounding upwards here...)

the next tx: bf080035ff8f7106f2efb2cbbc67a0f0492da7848d3e89525d6b818b43662fd8
IN : 0.00679735 BTC
IN(coinbase): 0.0000000000022 BTC
%(coinbase) = 0.0000000000022/0.00679735= 0.000000000324%
We continue with the unspent output funding address 39yNZHRzKESkjkNXeHswW5FM7U74Ns3r7K with 0.00630000 BTC
This means, 0.00630000 * 0.00000000000324= 0.0000000000000205BTC is coming from the coinbase rewards at this point (and i'm rounding upwards here...)


the next tx: 33e5ba37967cd58803f2590eb7654ad52e16ba47563d2585fa163f46f04c290a
IN : 10.93865414 BTC
IN(coinbase): 0.0000000000000205 BTC
%(coinbase) = 0.0000000000000205 /10.93865414 = 0.0000000000000019%
We continue with the unspent output funding address bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq with 1.11585090 BTC
This means, 1.11585090 * 0,000000000000000019= 0.0000000000000000212 BTC is coming from the coinbase rewards at this point (and i'm rounding upwards here...)

the next tx: 18a6e8f710c4940fee550d391a0d6866f28d055e4c64ba9345a911b46500f485
IN :
1.14340176 BTC
IN(coinbase): 0.0000000000000000212  BTC
%(coinbase) = 0,0000000000000000212 /1.14340176= 0.000000000000000019%
We continue with the unspent output funding address bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq with 1.09772462 BTC
This means, 1.11585090 * 0,00000000000000000019= 0.000000000000000000212 BTC is coming from the coinbase rewards at this point (and i'm rounding upwards here...)

At this point, the unspent output funding bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq is being recycled and recycled... So the %coinbase remains the same @0,000000000000000019%
This goes on to the transaction paying TryNinja... So TryNinja received 99,999999999999999981% coins that are hundreds of nodes away from any coinbase transaction and you tell us you're using fresh coins....

Solo mining would only work for this enterprise if he spent millions in hardware and runs a mining farm that has a total hashrate on par with the biggest mining pools... I'd be surprised if this was the case.

An other option is if he has a deal with one of the biggest mining pools, but in this case i'd expect them to confirm they have a deal with user cajancharles

I'll try to give an answer to your questions... A bit unstructured, but still valid

It might sound extravagant, but those 100 sat/byte and 75 sat/byte are not sufficient at the moment. This is why your transaction remains unconfirmed (so my initial idear was correct)

Some of these transactions are indeed using an unspent output from an unconfirmed transaction (see my first post).

Yes, transactions withing your own wallet need to be confirmed to.

AFAIK, those quantum computer rumours are just FUD.

You've been here a long time, i guess you already know not to trust PM's from individuals that promise to manually mine your transaction, right? You need a significant amount of hashrate to make that promise, so if the person offering you to help isn't from one of the top-10 pools, they're probably just trying to scam you.

This being said: viaBTC's free accelerator still works, aswell as their paying accelerator... However, since the used fee was < 4sat/byte the free accelerator probably won't accept your tx.

If you don't find a miner to help you, you can still wait untill the average feerate drops significantly, then attempt a CPFP. The process is pretty easy, but you'll end up paying a fee that's equal to the sum of the fee that should have been payed for the stuck transaction PLUS the fee that should be payed for the child transaction MINUS the fee that was already payed PLUS a little bit extra to be sure... It works, but at a cost... Not funny if somebody paying you cheaps out on the fee and you get stuck with the problems.

Good luck!

ouch... Didn't know that... I'm still running an older version.
To bad, this startup parameter was quite usefull imho, i've used it several times.

Thanks for the update

It shouldn't be a problem to create a transaction funding an addres generated by the same wallet... The reason why your transaction remains unconfirmed must be something else: insufficient fees? Not broadcasted? invalid transaction?
EDIT: i just realised you looked at your transaction(s) on a block explorer, so they're probably broadcasted... Invalid Insufficient fees is still an option tough, or maybe the unspent output was used in 2 transactions? Hard to say without knowing the tx id.

I had a hard time following the rest of your story, but if you use the unspent output generated by an unconfirmed (parent) transaction to create a child transaction, the parent transaction HAS to be confirmed first (or at the same time) as the child transaction. It's impossible for the child transaction to be confirmed if the parent is unconfirmed. Both parent and child ending up in the same block is fine tough...

Last point: if i understand your story correctly, it looks like you didn't lose your funds... Backup your wallet.dat and try abandontransaction from the gui, or (if everything else fails), start your wallet with -zapwallettxes

OR... Alternatively, export your private keys and import them into electrum... Do realise that doing this might be a bad idear security-wise... It's just not a good idear to start manipulating unencrypted private key(s), so i'd personally consider your wallet to be potentially exposed and start a new wallet just to be sure...

EDIT: fixed a typo...

Indeed, 0.003 per anonimity set, so yes, in your example that would be a 0.3% fee.
This fee is not customizable.

However, there are some additional rules that do influence the fee, like for example: the smallest participant doesn't pay a fee, remixing is cheaper, tx fee fluctuations have an impact, very small change can get added to the fee.

This makes it very hard (if not impossible) to say which fee you'll pay beforehand... But overall, i've never overpayed compared to traditional mixers (chipmixer is an exception since it allows you to chose your own fee), but most mixers charge >1% as a mixing fee, and so far i've never payed more than 1% using wasabi's coinjoin implementation.

Agree with everything you said, just wanted to add that a house might be a bad example... I'd personally rather sell a house with a 0 conf transaction than a car... I mean, what's the buyer going to do: perform a 51% attack and move your house to a different country . If a reorg was to happend AND the transaction paying for your house was to be left out of the longest chain (the chain with the biggest cumulative diff) AND the buyer double spent (or the tx dropped from the mempool after a while), you could still take your house back, since it is no longer payed for... If you sell a car, the buyer can drive off onto a boat and ship your car to a different country within a couple of hours, so i'd require at least a couple of confirmations for that deal

Same goes, for example, for memberships: imagine paying for netflix using crypto, but executing a succesfull doublespend... What's the worst that can happen from netflix's point of view if they accepted 0 conf tx's? Giving a hacker a free 1 hour preview before closing his account due to incomplete payment?

Same goes, for example, for many small shops: imagine buying a coffee with crypto and having to wait 20-30 minutes before your payment gets accepted? I guess a coffee bar would accept 0 conf payments because they would lose customers if they didn't. And in case somebody executed a double spend: just treat it like any other shoplifter: file a police report, give them the security camera footage and issue a lifetime ban for the doublespender...

Bottom line: if you sell something expensive that can be moved out of your reach in a short time: wait at least a couple confirmations... If you sell something online that cannot be taken back: wait a couple of confirmations...
If you sell something you can take back, or something that cannot be moved out of your reach: sure, wait a couple confirmations, but a 0 conf tx wouldn't be the end of the world... If you get scammed, just take back your property or close the account.

0.1 is ballpark correct at this moment in time. If you want to know the exact value, all you need to do is open wasabi and look.....

At this moment, 9th of februari 2020 @ 12:56 CET: 0.1005216

This number fluctuates all the time... I've even complained about this very high value in the past, but it seems like nobody is willing to change due to the fees being to much for smaller value inputs

I'm sorry to say that, given your rank, you won't be able to join any repectable signature campaign... Those campaigns are usually looking for longtime members with loads of merit and a long posting history.

You can join the mega-spammers by joining one of those fake token creator's campaings that pay you in homemade token shares to spam their crap all over the internet while hoping the price peaks at the actual release date so they can drop their bags and get rich... They're called bounty hunters... But as you could probably read between the lines, i'd discourage you to do so: you're wrecking the forum to have a small chance of getting a payout by posting links all over your social media to lure your friends and followers into buying a token they don't need....

Do you have any marketable skills?

Usually scammers steal images to be used on their webpages and profiles... Use google image search.... If it's a stolen photo, it has 0 value. If it's a real photo it might have 0.0000000001 value: in other words, it only has a value IF somebody recognizes the photo AND if you find somebody in the same country as the person in the photo that is willing to start legal proceedings against this person.

So... After a huge search.... I DID find a couple coinbase transactions. I assumed i'd find some, after all, every trace has to end with a coinbase transaction (per defenition), so if you search long enough, you're bound to find one eventually...
Before you jump into the air and tell me you were right all along, skip to the bottom for my conclusion...

I had to plow trough 313900 outputs (i can post them if you want), but i found 2 coinbase transactions that can be linked remotely to TryNinja's output:
transaction 8def694164f5fc811041738f3db4518f21078cc112a7acb4cdd806c9942c469a is a coinbase transaction funding address 147SwRQdpCfj5p8PnfsXV2SsVVpVcz3aPq with 6.96556045 BTC
transaction 6cc2919828a42560696e173577b9adfa7a0dabc7fb35143856b9210eb331b4b3 is a coinbase transaction funding address 147SwRQdpCfj5p8PnfsXV2SsVVpVcz3aPq with 6.47483880 BTC

both unspent outputs are merged with a thirth one (>10 BTC) and  spent in transaction bdfbfee25cd935abb128fc632faa9a105d0ae7b6d1ab32b8cc15e452ce2372af funding:
1MQgJCTEvxE17hnQgjR1QYzpgLEWjRX5zw with 0.00501127 BTC
14UeiGPDfPiBuhc6jXrcBR8ntS1SfCWUBa with 0.00512741 BTC
3Psydwi2jcn1g4jfkYHfoZ9wZPjjm9Sjj7 with 0.00516750 BTC
3Hmga8nbWxE34MuaXYn8RQjzLAtiNsj2ZQ with 0.00520982 BTC
34E4k6Xqp78UnzZgkcEdE4pxeXzFg7yEWq with 0.00521250 BTC
1Fve39anikQgaVKedQKAtLyuWX9bLDWnV7 with 0.00524362 BTC
1NDwNwjzy4tX6ZFn2T69JYMjPvuBgezkm7 with 0.00524362 BTC
19E6roGm5tCyD6AFkdHiVEhVBH7jDmDg4C with 0.00524968 BTC
3HMArbkQicJ7rQCqsxKh5jiad7Pana3zkM with 0.00525150 BTC
1PP4RvShCV7xFxZqDCxAa6xAJLDHuFZKUy with 0.00540578 BTC
1EJtJjf6Vu2cScP8uQYSjmwkazji5GGZ6d with 0.00540578 BTC
1KPHGbJZoSuBp41sAUB1WZHFFxfpUt2yLL with 0.00543816 BTC
1C5x8ffRrvUrxVrvtDcYBjCNoGM9kbH6uz with 0.00559730 BTC
1Pzrca66w4RwW6FcAdvh28nNtXX9manBZa with 0.00562635 BTC
18KgNkD4rjW4cEzwWZMxCj4DHUY9yhp1xg with 0.00839326 BTC
15L3z1fWhXk42sEbqdfoqY5mog1bnFHDYH with 0.01007898 BTC
1LQHiawVEPUXtHvrd8T4ok6QhJhZVN5phd with 0.01025409 BTC
15a31zVR1WwUjqsPoq1TtnGLaoYTLB3iig with 0.01065146 BTC
34oqXGWjPTpyoaXAkTgiQaDUphZaWKoEU2 with 0.01067721 BTC
12ePzbhQ1QkNLDbggpWGtNbB4twU3mBV4w with 0.01070690 BTC
3C91jAH4k1YLaHcushcKX6Pi6V9hcAqRAt with 0.01087643 BTC
3Nq3zkbP7aYndSGXRXmhVh1NnFPjD5tCEZ with 0.01095148 BTC
3GS2b9MZYUPsC2txrLFE7mJ4AZ27NPCciK with 0.01119629 BTC
3FiaietwfudsceKtaF8R4ePq1UbsCVxmAV with 0.01119629 BTC
1F5HEa6hLcBAVugvzjs7jbtzTACSxfNgrp with 0.01119629 BTC
1NsW6UaJpVkdx514iAY12BtWUjMjayBH5A with 0.01119629 BTC
1NhAEP5anBsctjqHipwwYY9wHbQMJoCK5u with 0.01138206 BTC
1Gx8X4hD3v6ez9dYUcqRvFeXMAGdaGcV92 with 0.01171708 BTC
1ML3WNk1baBB93GhMeLVh2e1eBKLUdPRp7 with 0.01367560 BTC
14tkX1Kqvd1N3oyiCjMPcNkXLDJVXtt9Wk with 0.01380522 BTC
1PseYvD11DjqXqAZX4tJAKxJheVdtUbhQS with 0.01547518 BTC
1Cin6NH9AbfDsSzk8AtzJb4sUs3VQBYEFA with 0.01612188 BTC
1Fxof3ieRisPuwAWrxBRQzqnx1ATTFxQ5S with 0.01612474 BTC
1JrecstpYy4FySLtgioTNbPXP71kJFPE4F with 0.01692190 BTC
1MVeoxyHnWTbfVpomrmDmu9e4A8r8Qynfm with 0.02003738 BTC
3FToeoKAHiPPGmPP3V61JukhVkGttyWsau with 0.02090359 BTC
138Cx6a4xmrfJX9SdryQtPacrPZwM9VAqD with 0.02483641 BTC
1JZxcGkoha6X1wSZNZEQ7BmpTm1SwrYoVa with 0.02946865 BTC
349guFMvdxY1UNcNLpbMrXkVnzfFyZuzPS with 0.03341718 BTC
37AtakbqF25Cngm1CSRiBx5gfjSnqDtC2H with 0.03893783 BTC
1MwJqkVZHGubrJ81X7o5fbgS4WYRr2o87r with 0.04328409 BTC
1F78SCR7DdizX1butsL7yxpYZXfVdPfmU9 with 0.04357264 BTC
13421KktHanJycg4nWkUMjM8B9vTCxBxWP with 0.04561205 BTC
15BPohaEyFQFvvMiSmeVYLdDhybdtTVyUR with 0.05359435 BTC
18PjNagRQkfQxUmY9Fo38F92QyFVvV4aXo with 0.05366102 BTC
17pXe5gAhSy9aaagKDP9dYVXhbjP4onuAN with 0.05664444 BTC
32ctGhN8rCwYNG6uGR49AbJHfs7S9ArUYf with 0.06720418 BTC
157mPXB4E1rUjt5g3ZdqCXA6uwqhebkZAZ with 0.07712358 BTC
1CRvGBxu1qMiCEVzAiZKrYV8hYuMqa1yM9 with 0.20542902 BTC
12ssutCnF1fVd7cBiQWLUxWAxoiaVdsE3u with 0.00000822 BTC
1BMjmWXy7hnYnJwCY1GYUsL9Ya9WdVZyTW with 29.27911400 BTC

3FToeoKAHiPPGmPP3V61JukhVkGttyWsau was funded with 0.02090359 BTC, this unspent output is used in transaction 9a2ec09aa7ada4c581e8b36d5ff56e09b784c547d7e11e9b8d01d03b5fa145e6.
This transaction merges 10 unspent outputs, some of witch have a value of > 9 BTC. So, the unspent output funding 3FToeoKAHiPPGmPP3V61JukhVkGttyWsau is neglectible... but still following addresses get funded:
bc1qncma32m7v7w9a28pwt4ks0gtqqmzqvh4j7yslh with 0.00111097 BTC
1BxZA5hKyYKkw1jgmVN4JjeF6aF31thjoy with 0.00121535 BTC
31iNgVe4Nk8UtVwRJmnsANGyKSmJkt3Sup with 0.00187000 BTC
3MUCTbBkJKUwvGKyzN5k7QjDD7sUZ4TjmA with 0.00203000 BTC
3MZV3vaX6rcjeLPQs8KMan85cYkGQZHeHH with 0.00247000 BTC
3KqMjyPEWLCo5f1pJE1NEzp1VDeocs7A8s with 0.00253285 BTC
1SDfw3JTJsRgvLwuZr1Hyc3c8mPFkUwaM with 0.00288000 BTC
1F99adPu7RDzWfWb6knbRgzPa4LdiFR8se with 0.00305000 BTC
bc1ql4qu72e77dqwctcvxl2ky04lmfmuvd95neexr6 with 0.00318126 BTC
3Nfum67ZTa9foM9uATqxVP5hAdLHU6LnqL with 0.00330000 BTC
bc1q7w6u859mxpyv2t39szz97v5ujcvyn2n7grpkr4 with 0.00334599 BTC
bc1qzfm04yrfyethmj6r0dn87yggfm4es9rlh7ue80 with 0.00341000 BTC
3FRypXPdooZRqNbQEy23Za6HMuM14BPEKV with 0.00370323 BTC
3KPqJbAHT74mSUABRv3pGxNyxGJ2y7JKN3 with 0.00395000 BTC
13rygUDJS8qmRtk74JiHUV1quMDiPKbkoF with 0.00406000 BTC
bc1qyxzj4vcwgpf8rx2ygjmsye4juxggqc6al68l0f with 0.00518170 BTC
1CJXd3xEPLANCYDUHqExPbu9DwjamwwU4W with 0.00532000 BTC
1FRtPaviNjPMiXUhQT6F3nvwbkjXkbX4AB with 0.00560000 BTC
bc1qml2zun2r0nry60eajxjqmvutjc2xm96p25e7gg with 0.00611406 BTC
bc1qp9xl93vvlt4pp0t9096ssn9ry46zlcqwv4zr6p with 0.00616000 BTC
179YYG9hd47QZ6AWU5DbXr9gX692xRuzjZ with 0.00652944 BTC
1Nc6TPyLSKAURyBJEZAEXgzP8ZJyjzeSQQ with 0.00695000 BTC
bc1q6f7usdrwhldsmjlagyw3xqxlm5r30ac8vzuds3 with 0.00721000 BTC
37ApUhsMN5BZLUHY4kXNFMGWgMJXT19UiR with 0.00766887 BTC
3QGoj6FTzFiDPJCzQwrQ2YnEiC4cvKfzsj with 0.01027000 BTC
3NPmgExHzypJyxWRKZfgDo2fwBAYGP5HJE with 0.01028000 BTC
bc1q3u8llhemahgsvn6sjkeh4yqgfsu8wg2dx6mj5c with 0.01365248 BTC
3DjkSjsshiEAyEbBs99cyKrp1mPMdeerLh with 0.01426073 BTC
bc1qe8v796sdquswkmhxp4kdaym3g7v78qhmmxzg7s with 0.01480887 BTC
1L8M1RuD2zircusECrWJZzc3gBRTgbpBYT with 0.01643555 BTC
1318NBDhbYLczu6YiguKc9fpgRe4xTrKBs with 0.01667080 BTC
13CoJjQBRjzvnDePQuQvk5MH1UHvEqFR2U with 0.01844079 BTC
bc1ql9nn04klgr272meuhatpcef2jewhydksnfsnwm with 0.02495043 BTC
37Yyq7iJJ5y11n5mDgLGa5fYGH8vqw3L31 with 0.04127425 BTC
32C7ksV9QD2Y352gaEPRhtEt3xL3acBwnS with 0.04526000 BTC
389F8Nj8d1BHAEFN3sgDSbbuq6n5hu8wLd with 0.05309070 BTC
1549qhLjBpsWXoDUFoxPSf81p8LozvVYnY with 0.05826013 BTC
1BTE4ZrscjwSnTrbNuPgWsYBykPKoNjDzx with 0.06259264 BTC
32CDbuHFWQYZKaj7NvvU5m6PEMh2DLFoCj with 0.08521727 BTC
3H3HnhgQNRJ6EK64nguG6Ns3C84FzFNhZD with 0.08579921 BTC
3Q1Fmd3DiqoXCUieCNMpgDrc751Lesv6G5 with 0.09118619 BTC
36rdQi9cW7rhjp9L8r6XvapDrTA4UuyN9a with 0.09296400 BTC
3GdMfVJvXDtzY7t3v7dYzm23RHfLRBfC1H with 0.09961279 BTC
3McvBp1ZpgFQUvtMgpnkz4BxxUjU4ARsW7 with 0.10308730 BTC
3Gk5NXjRr6KYjg88hNJpRXpqKSk5mYF426 with 0.10655585 BTC
3GrBgm9RKHHGt4etdwfjZwK11hAKQQ8s8v with 0.11052300 BTC
3Bi7jWrGMso7EHabPrXbmonv4bmC7FBbyu with 0.11320200 BTC
3JUCSCreEHADF8gBb6av5wjuamYQjtXXGF with 0.12563400 BTC
3NzHAfwLUkPLTb25UA1Ao6DZ4VddQA6ZCD with 0.15607179 BTC
12nbxYHVgVdP4wVF9eoa4vb5bdLrR8yShS with 0.19277000 BTC
3CDsXPsg7d9t3Ah6RUzzVTkCxRvNLWtygT with 0.20055816 BTC
3MkQohaonKcNTJTbSV6HQS4bkT2MeJDn9B with 0.20691671 BTC
34wdNYp6JfWo3qpva8QsJKpEGhCiNjDeqh with 0.30000000 BTC
3GMhMAYiYScUFAXUzDthqkoGh6jBGZjESE with 0.33361896 BTC
1No7Gfb4WMSP83v4UyZcnt47EsqWPh8Wnk with 0.53173408 BTC
3CSCn8vp9JiBSFcYf4EE7p1AvsBgAWFoMs with 6.30097501 BTC

bc1q6f7usdrwhldsmjlagyw3xqxlm5r30ac8vzuds3 was funded with 0.00721000 BTC , this unspent output is used in transaction 60efc87dd0d3630b24f12785aae3eaac05e494f6e98a9e54d295c0f6e1ae366f.
following addresses get funded:
bc1q386274dh4ggx8qh4xplwevk3s406dpk6xasqpq with 0.00002130 BTC
3FKdyA28KPePVCqn7JTeG84yPSgPf3XQa8 with 0.00700000 BTC

bc1q386274dh4ggx8qh4xplwevk3s406dpk6xasqpq was funded with 0.00002130 BTC, this unspent output is used in transaction bf080035ff8f7106f2efb2cbbc67a0f0492da7848d3e89525d6b818b43662fd8.
This transaction merges 3 unspent outputs, some of witch have a value of > 300 times the value of the output that can be remotely linked to the coinbase transaction. So, the unspent output funding bc1q386274dh4ggx8qh4xplwevk3s406dpk6xasqpq is neglectible... but still following addresses get funded:
39yNZHRzKESkjkNXeHswW5FM7U74Ns3r7K with 0.00630000 BTC
bc1qtuyyc560nkc64xrzg2hmfs9zfcy08p32knernt with 0.00005535 BTC

39yNZHRzKESkjkNXeHswW5FM7U74Ns3r7K was funded with 0.00630000 BTC, this unspent output is used in transaction 33e5ba37967cd58803f2590eb7654ad52e16ba47563d2585fa163f46f04c290a.
This transaction merges 21 unspent outputs, some of witch have a value of > 10 BTC. So, the unspent output funding 39yNZHRzKESkjkNXeHswW5FM7U74Ns3r7K is neglectible... but still following addresses get funded:
bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq with 1.11585090 BTC
3ByKbDxF1iAMRVjBQFBXq6rRhatn3ht62V with 9.81882623 BTC

bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq was funded with 1.11585090 BTC, this unspent output is used in transaction 18a6e8f710c4940fee550d391a0d6866f28d055e4c64ba9345a911b46500f485.
this transaction merges 2 unspent outputs, but at least the value of the trace we're following is the biggest for once. following addresses get funded:
bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq with 1.09772462 BTC
37JyhLx9UEKReCaWUcrQruL235dDESVeXA with 0.04159130 BTC
3LLwYJM7MAo4QShH2T4b6TtrXuAUX9Bnd7 with 0.00376290 BTC

bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq was funded with 1.09772462 BTC, this unspent output is used in transaction 790b6b5288ee7aa8f461cc508a0cd66df759cf942d28e73fd2b36eb1ab9fb32b.
following addresses get funded:
bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq with 1.05052544 BTC
16bS3XJHsPm6FrQ8CkabgzKLbjPB63Evic with 0.00333120 BTC
36LTHYxEKAUwH3svuEaMMd4H5WsPHPiJCb with 0.01004610 BTC
1HyPD91iSoqj4jATEoGwfDZE8H4wHxvPHr with 0.01512420 BTC
1GJWFqcU7AF1hHULVpT8a2fWCkLpSvbjVt with 0.01268650 BTC
14vjPjaGvnEAfuUMYEPZEKDVoBDpieYGrg with 0.00563310 BTC

bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq was funded with 1.05052544 BTC, this unspent output is used in transaction 8bad716ea8b1d939cc65ef0755c9a4cdda16b0e214777c048306803660f07079.
following addresses get funded:
bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq with 1.02979074 BTC
19a6Ajzk1mEcLWmVESmyS1N3UhfpXCwsuj with 0.00524740 BTC
14zXdS59qqAX7CPg4s5UTEH54LTPV56Jiw with 0.01145850 BTC
3DacLhaPUFgu9gyHiR3xyQx1LvNugny5ww with 0.00376210 BTC


bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq was funded with 1.02979074 BTC, this unspent output is used in transaction 317c506231050fb91e28280879341c558ae13721526e3da5c40f8bcd0b9c0993.
following addresses get funded:
bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq with 1.01522632 BTC
1sNvVCBGHZ6VgCmJPneFFTsGS9B2FsofS with 0.00869840 BTC
1JrkMDBEBZV1zsqCzWXuRRe5oxbUwfhiLh with 0.00563640 BTC

bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq was funded with 1.01522632 BTC, this unspent output is used in transaction 317c506231050fb91e28280879341c558ae13721526e3da5c40f8bcd0b9c0993.
following addresses get funded:
bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq with 1.00244913 BTC
3Me7uCA7ygHwDcKYmL95Eev2SK7GY99Z4m with 0.00995139 BTC
17a4H8hsEg2y6xcrRydQyjxkcxWmvJfrXW with 0.00259700 BTC

bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq  was funded with 1.00244913 BTC, this unspent output is used in transaction 83ea3e871ecc9cec72c498f3d8698646c9aa9bdef82dd3991bbc58bfd49b6e0f.
following addresses get funded:
bc1qq904ynep5mvwpjxdlyecgeupg22dm8am6cfvgq with 1.00244913 BTC
3Me7uCA7ygHwDcKYmL95Eev2SK7GY99Z4m with 0.00995139 BTC
17a4H8hsEg2y6xcrRydQyjxkcxWmvJfrXW with 0.00259700 BTC

3Me7uCA7ygHwDcKYmL95Eev2SK7GY99Z4m was funded with 0.00995139 BTC, this unspent output is used in transaction 5f357c4369d74f38f8a7230b497b5a7c20741a97c3744571422407d7dca70f05.
following addresses get funded:
3H7YJooRbp69PttCagcyozsRSLNNDuYAga with 0.00011719 BTC
3CvaLN1zcJTF9qMZx8KhHSEwJ59DxZemer with 0.00965718 BTC

3CvaLN1zcJTF9qMZx8KhHSEwJ59DxZemer was funded with 0.00965718 BTC, this unspent output is used in transaction a88c84f418796d540615ca6b4acfc1ed2f23460430b0d6640e615fc1a04d4a80.
following addresses get funded:
3FYgikz3JL99eiNSaeM9pnozX2u1TnZD7z with 0.00102000 BTC
3BeQHdZMwE7gAfYYPzg2DHCPLJoRRkuBoK with 0.00853364 BTC

3BeQHdZMwE7gAfYYPzg2DHCPLJoRRkuBoK was funded with 0.00853364 BTC, this unspent output is used in transaction 746d1dfb24afd3c4322f003b9c78a21f062ee307ed970fbc043d98ee4655201c.
following addresses get funded:
33MZENT6Lg4Hc7fRJoaBEkvhng8GWCvuRp with 0.00026000 BTC
37gnxrPCzC1dTJtGJAYCegPt2RKaXvTtF6 with 0.00817010 BTC

37gnxrPCzC1dTJtGJAYCegPt2RKaXvTtF6 was funded with 0.00817010 BTC, this unspent output is used in transaction 8b09f9702a90270769872af44bc5f6db1d7658b48ac62e1d50ebc7d1df6c8f46.
following addresses get funded:
1LP8WPE2C1UzKogfLWhu18UgpsVhwrpNbU with 0.00021240 BTC
12XSTJTz3PRWV3Nai3gVk6tVGK8xPwe5vD with 0.00060135 BTC
3BoDB5FCFKZFgXuDGx956GFiMZLK8eaPMB with 0.00723049 BTC

3BoDB5FCFKZFgXuDGx956GFiMZLK8eaPMB was funded with 0.00723049 BTC, this unspent output is used in transaction 9840051b37ae9e979526fb744c6ae222eeee0aafdad176400c82dcbf55a65733.
following addresses get funded:
3EaAoRdnrbWQujm1irZ4XUw91sghLMszAF with 0.00068210 BTC
3LmhRaUXAPsS6mZGr7RiyBzwTBxSiaEUQg with 0.00645320 BTC

3LmhRaUXAPsS6mZGr7RiyBzwTBxSiaEUQg was funded with 0.00645320 BTC, this unspent output is used in transaction a576790d4b0180611d9703d86538f943120ce928dafc4daf016128a66fb4730a.
This was TryNinja's transaction....

So, bottom line... Final conclusion... You got lucky (i assume)...
If i disregard ALL inputs that have nothing to do with any coinbase transaction (more than 300.000!!!!) and ONLY focus on the traces that could be remotely linked to the two coinbase transactions, one could *theoretically* say that TryNinja's outputs contains a tiny percentage of fresh coins...
I mean, the percentage is truely tiny... IF you look at the transaction spending the coinbase rewards (so, the very first step):
bdfbfee25cd935abb128fc632faa9a105d0ae7b6d1ab32b8cc15e452ce2372af
value in: 30.40966025 BTC
value in from the coinbase rewards: 13,44039925 BTC
value out to the rest of our trace: 0.02090359 BTC
So, at this point in time, 99,9% of the "fresh" coins dissapear from our trace, only 0.1% remains...

The next transaction 9a2ec09aa7ada4c581e8b36d5ff56e09b784c547d7e11e9b8d01d03b5fa145e6 decimates this fraction even further....

Even then, there's a huuuuuge distance between the coinbase transactions and TryNinja's transaction, and this was the ONLY time in your output stream that i've ever encountered any coinbase transactions: you got lucky (i assume)...

Both blocks were mined by a miner using 1THash&58COIN in his OP_RETURN. These guys seem to have a webpage: https://www.1thash.com/ .

Nobody could tell you... Only guess:
https://jochen-hoenicke.de/queue/#0,24h


The only thing i can tell you is that 8Mb of tx's have payed more than 14 sat/byte... So if everybody would stop broadcasting transactions and the average time between 2 blocks stayed ~10 minutes, it would still take another 80 minutes before your transaction would end up in a block (on average).

If, over the next few hours/days more than 1Mb of new tx's with a fee >14 sat/byte get broadcasted per 10 minutes, you'll have to wait... If over the next hours/days less than 1Mb of new tx's with a fee of > 14 sat/byte get broadcasted, you'll move closer to the top and see your odds of ending up in a block increasing...

Okay... Put your money where you mouth is...
TryNinja payed 20% in total, he says his addresses got funded using transaction a576790d4b0180611d9703d86538f943120ce928dafc4daf016128a66fb4730a
Show me which coinbase rewards that have been used to pay him...

And please, don't start telling me that you need to protect your client's security, the tx id is known... It's out there... You cannot take it back... Anybody can follow the trace of unspent outputs if he/she has enough time to follow the trace... I followed it to a reasonable depth, but i could not discover any coinbase transaction within reasonable distance from tx a576790d4b0180611d9703d86538f943120ce928dafc4daf016128a66fb4730a. You promised to pay your clients with fresh coins, so you should be able to give this info since it's now considered to be PUBLIC knowledge.

You have the wallet, you should be able to give us the exact trace from coinbase transaction x to payout transaction a576790d4b0180611d9703d86538f943120ce928dafc4daf016128a66fb4730a, so please tell us which block and the trace from this block to TryNinja's payout.

Once again: no smoke an mirrors... It's a public ledger, the data is final and known to anybody... I couldn't find any coinbase transactions, but maybe i'm wrong... Use the public ledger and information anybody could find to prove TryNinja wasn't scammed into an inferior product. "Aged" and "split" mine didley squad, you promised fresh coins, you should be able to prove that this is what you delivered. Mixing with used coins is already pretty sketchy since you said you'd be providing "fresh" coins, but at this point i'd even be willing to overlook this fact if you could prove that within a reasonable distance of tx a576790d4b0180611d9703d86538f943120ce928dafc4daf016128a66fb4730a there is any coinbase reward that was controlled by you...

Works perfectly fine without a hitch for me... Maybe a tad bit slower than usual, but nothing mayor... So i guess your funds are fine

Looks really nice... And fun
I'm not a gambler, but i did try it out... Entered your donation address as a receiving address since i don't want to plunder your wallet, but everything works exactly as you said.. Here's the withdrawal transaction:
https://blockstream.info/testnet/tx/f39c02c3ba5229d4758e428fb30c96410e7495a3316ead161643b5fae717a1de

The beauty of the testnet is that people offering testnet services aren't competing (at least, not according to me), i think you made a great service and i hope you'll make it work in the long run....

By the way, if you want a subdomain of mocacinno.com or unblur.ninja, give me a shout I have a lot more domains in my portfolio, but most of them are linked to my irl identity... That being said, if you're ok with a subdomain, but not with mocacinno.com or unblur.ninja, i could have a look to see if i can offer you something else.
something like https://cointables.unblur.ninja is easyer to remember than a plain ip...