With so many cryptocurrencies available, the process of finding a mobile application that supports all the coins one holds is a bit cumbersome. Multiply that by five, and you get what it is like to find something like this for Monero or XRP, both of which have excellent standalone wallets, but integration that leaves much to be desired in others.
Edge, a multi-coin wallet that focuses primarily on providing a secure platform to hold and trade cryptocurrencies, has just announced that it is integrating Monero and XRP into its platform, which also offers support for Bitcoin, Bitcoin Cash, Dash, Ethereum, Litecoin, Feathercoin, and Zcoin.
“We’ve listened closely to our community over the last few months and found a strong demand for these currencies on the Edge platform. Both communities are different but they face the same issue: How do we hold and use our currency? Edge is proud to announce that they can now find that option here,” said Paul Puey, Edge’s CEO.
Because of Monero’s intense focus on privacy, we were curious to find out just how the coin’s behavior would be affected by Edge’s integration. We approached Paul Puey to ask him a couple of questions about this cryptocurrency in particular.
Our Q&A
CV: How much collaboration did Edge get on the Monero team’s end?
PP: We were in constant chat communication on Telegram. They helped us a lot with the understanding of the protocol and libraries needed to get Monero integrated. We couldn’t have done it without their support.
CV: One of Monero’s prized features, as is mentioned in your press release, is the implementation of ring signatures. Just how much is Edge going to make use of RingCT? And what level of ring signatures can we expect to be used in transactions by default?
PP: We utilize the library created by the MyMonero team, which I believe defaults to 5 ring signatures for each transaction.
CV: Would Edge users be able to adjust the number of ring signatures used in their transactions?
PP: Not in this release. We try to keep it simple and give users good defaults.
This article appeared first on Cryptovest