Can’t speak for the Core team so this is my own view of the situation. There has been some nice work on slatepacks which can be used today by exchanges. Unfortunately, I don’t think they have implemented the new flow yet. This is not something the Core team can solve. The transition will take time and is up to exchanges to do it. There will be some additional improvements (almost lock free txs) to the flow that should make it even better for exchanges. I am quite happy with the progress I’ve seen in the last year and am confident we will get there.
i’am an avg user and honestly i can’t understand your frustration. transaction on grin are little bit different, once you understand how things works it will be more fluent.
Grin ++ and niffler are making things easy. we will need maybe some tutorials for beginners
No, I mean even previous versions. You need to have error handling because things can go wrong due to interactivity. Unfortunately, they often don’t have this handling in place. Slatepacks could improve this if integrated correctly.
That’s like saying a computer is unusable because someone doesn’t know how to use it and it is clearly far from being unusable This is why we need to improve the documentation and make some easy to follow introduction to Grin so that anyone can understand how to use it.
Sorry I didn’t make it more clear, but I was talking about the exchanges, not you. My guess is that most of them have poorly implemented Grin integration because they are not used to interactive transactions. I could be wrong though, but I know some of them certainly do have that and is why they have so many support tickets.
Hello, first of all I’m sorry to hear that you’ve lost coins, I hope it’s not permanently. What happened?
The phrase you quote (“Electronic transactions for all”) is not something that comes from a core decision. We, the people who were around and active on the forum at the time, had a lot of different ideas for what Grin’s vision and mission statement, should be. What we wanted Grin to aim to reach, at some point. We even took a vote about it, but in the end were not able to reach a conclusive decision when we tried to agree on a final mission statement. I did some digging in the old meeting notes just now and found this note that you might find interesting:
I think it’s accurate to say that we’d like Grin to be usable for everyone. I also think it’s accurate to say that we’re not there yet, we have a lot of work to do before we get there. That’s why we’re here.
If you think something is incorrect in the text on the website, you have a chance to improve it for all of us, you can make suggestions or submit a pull request against the repo directly: https://github.com/mimblewimble/site