Show Posts
|
|
Pages: [1] 2 3 4 »
|
@splashed, you need an urgent reaction. Someone reported the Metamask splash.tf domain as harmful. It is necessary to request a delisting from the blocklist It appears on Chrome and Opera, while Firefox and Brave open the site normally.
How was this issue fixed? I know of another service that had a similar incident, but for months their issue was never fixed even when they tried to contact metamask to help. In fact, one of the devs or someone like that even started appearing rude. We have created an issue on Metamask's github. We would really appreciate your support on the github issue  We will keep the community updated as the case progresses.
|
|
|
|
I'm glad you're back, but such long delay (~ 4 days) indicates that the development team considers splash.tf a side project or not serious about developing the service.
Yes that is understandable. But you have to realize that the market is not strong at the moment, and we have been self-funding this for longer than a year now. We are serious, but practically we can't be spending all our time on this  What caused the server to be unreachable? Did you take it to the beach or something?  Bills were missed 
|
|
|
|
Hello Everyone. Just a message to address the recent downtime and our absence from the forum. First and most importantly: we were not hacked, funds are safe, and there was no law enforcement action or FBI raid. There has been no security breach, no loss of funds, and no compromise of our infrastructure. The reason for the downtime was much simpler: our team took some time off and failed to communicate that properly in advance. We understand that silence from a service like ours can create concern, and we apologize for that. Our services are now being restored, and we are reviewing pending messages. We appreciate the patience of our users and the Bitcointalk community. Going forward, we will make sure to provide advance notice for reduced availability so this does not happen again. Thank you  splash.tf team Apart from this Metamask thing, there don't seem to be any issues with splash.tf functionality. As far as I can see on the website, there is a regular daily trade with them. There is no reason to contact them separately. Also, I haven't seen that they participate too much in other discussions except those related to their service, so if they see a PM, they will definitely look at their ANN. I assume that escrow has more direct contact with them, so if necessary.
Regarding the Metamask thing, thank you for reporting it and thank you to @SFR for sending us a DM. Since our service doesn't require any wallet connection, we don't think it is an issue. Metamask has been known for showing these false positive. In saying that, we will attempt to contact Metamask or the third party they rely on regarding this.
|
|
|
|
Splash administration, please help. I haven't received two exchanges yet. I created requests on your website for ETH and DAI, and where wallet's gas has run out. What should I do?
Just seen this apologies. But this user has contacted us via the support form and the issues have been resolved 
|
|
|
|
What happened with the liquidity funds on splash.tf, somehow I am convinced that earlier there was significantly more here compared to what is currently shown on the site? Is this a preventive measure or something else?
We have not removed a single satoshi from the liquidity, it's only been increasing from the fees 
|
|
|
|
I checked again, but "Withdraw" button and pressing enter still don't work when I copy/paste my Ethereum address from Coinbase Wallet. It's the version that uses uppercase and lowercase letters checksum, that shouldn't be an issue right? Or does it want it only in lowercase? There doesn't seem to be an event listener on the "Withdraw" button or any POST form for the address field, so nothing actually goes to the server when the button is clicked.  Thank you for that observation. Turns out we tested locally but didn't deploy to the servers. Please refresh and check again, it will work this time. Really. 
|
|
|
|
The withdrawal button doesn't seem to do anything for some reason. No page load or anything like that. I entered an ETH address and tried to withdraw ETH.
Should be fixed, let us know if there are still issues 
|
|
|
|
The withdrawal button doesn't seem to do anything for some reason. No page load or anything like that. I entered an ETH address and tried to withdraw ETH.
We'll have a look. Thanks for reporting 
|
|
|
|
Splashed, kindly approve my referral account. I sent you an email about a week ago.
Will do, thanks for pinging us here. We rarely receive emails, hence we don't check often 
|
|
|
|
Hello OP, I came to report the .onion link is not loading, but clearnet is, maybe you could check what is going on.
It might be good to add the transaction link or pending TX when the splash identifies transactions.
Thanks for the report, should be back up now  Also thanks for the suggestion, we'll add that!
|
|
|
|
OP are you planning to add Dash? I believe privacy-focused coins will be the main focus of the market on this year, while Bitcoin is on sideways...
Zec and XMR have already broken their ATH, Dash has a high probability of repeating the feat.
Most likely not in the forseeable future. Dash isn't really a true privacy coin, the transactions are public and transactions are private only in the mixing sense (like Bitcoin + CoinJoin). XMR is the only one that is private by default and the one we like the most. 
|
|
|
|
OP can you tell us what is going on with Bitcoin reserves on Splash exchange? I can see currently there is only 0.00327283 BTC available, and situation is not much better with ethereum. Even after manually testing myself I got the same low amounts of bitcoin available for exchanging.
Yes users have sold us their XMRs for BTC and ETH over the past week. We have reduced fees for swaps to XMR to incentivize swaps going the other way 
|
|
|
|
If buyers are willing to pay 4% extra and sellers still pay 1%, it makes me think the market isn't in equilibrium.
It's 4% and 0.5% currently, and our XMR reserve has been low for a while, it only increased significantly right before this XMR rally. We could perhaps consider a automated dynamic fee 
|
|
|
|
4% is only for XMR destination, any lower than that and we would have 0 XMR within a few hours  That sounds like good for business to me: who doesn't want to sell all their product quickly?  Then we will need to buy XMR from the market with high fees 
|
|
|
|
I made a few transactions a couple days ago - everything went smooth overall. Took a bit longer than expected to confirm, but no big issues, all good.
Only real bummer is that 4% fee man that stings a little 😅
4% is only for XMR destination, any lower than that and we would have 0 XMR within a few hours 
|
|
|
|
Splash onion link is not working for me today, andI tried switching different identities in Tor browser but nothing worked. Maybe this is something temporary, but owners should take a look and fix this issue. Note that clearnet website is working fine.
Same here, it's not just a problem on your end, clearnet website is also works on my side.
Thank you, we're checking  Update: It's back up now 
|
|
|
|
Maybe return a page that says the user was rate limited. Right now non-dev people might get scared with the raw json request.  At least a big centered h1 that says “stop refreshing too much” etc. Good suggestion  We'll do that if we get more complaints, right now with the increased rate limit it would be very rare to get rate limited under regular usage.
|
|
|
|
I tested it: only six refreshes are enough to get rate limited, and after that it triggers at the third refresh. That's not much and I can imagine that happening.
Would not recommend refreshing like a bot, since you'll most likely get rate limited  Our anti abuse system is quite sophisticated because we don't collect and therefore can't use users' IP address. It's hard to pinpoint a specific reason for getting rate limited, but generally if you just use the service normally you shouldn't get rate limited. With that said, we'll relax the rate limit a little. Thanks for the feedback 
|
|
|
|
This error message appears several times when I open the splash.tf site. Usually, after a refresh, everything loads normally and continues to function without problems. What is this about? Is it maybe a problem with the cache? To note, this only occurs with the splash.tf page and none of the others I use under the same conditions.
How often are you refreshing hehe. We have a rate limit in place to prevent abuse 
|
|
|
|
UpdatesWe've just updated the pricing calculation and algorithm, so it should now more accurately reflect the market price 
|
|
|
|
|