You guys should look at this seriously. I think it can be fixed relatively easily - but if it's ignored it could be a problem for you later.
Chaeplin spent a bunch of time working through every detail to get you a step by step description of the issue.
And no one is responding seriously, no one has given a counter analysis - that is not a good sign for investors.
Can someone show where chaeplin's analysis is flawed? No one has directly responded at any point. Quote a post - draw lines...whatever you need to do.
I came to the same conclusion as him after reviewing a series of transactions yesterday - but it was annoying and took me a long time. If this isn't an issue - can someone just point out where? Or create a counter-example? If you want to be taken seriously - I'm pretty sure it's important and shouldn't be brushed off like it's nothing.
I don't know how you can call it FUD and ignore it......he walked you through the problem.
If you don't understand it...fine - let someone who does argue a counter-analysis. Don't just call it FUD because you don't understand what is going on.
ATCSecure has responded NUMEROUS times that by rev 2 with multi-path, this is a non-issue. Why should he waste any more time on a pattern matcher when this exact problem won't be a problem any more?
You guys are confusing. He since posted a FULL walkthrough. Not the partial from yesterday that was responded to.
Oh, sorry, I didn't realize you guys has conceded the analysis was correct.
That's good, so, the solution is reliant on a second phase....which is awesome.
This is exactly why I was asking for information yesterday about the design. Can't find any real material on it except some not-so-good super high level stuff on the website.
Confusion could have easily been avoided with some information.
It does seem though that you guys want to keep genuine interest away and the dev nor the members of the community - that I'm sure are great - are jumping in a saying much and making anyone feel like there is substance here.