Yes, both are on the roadmap. Can't say for sure on timeline, but hopefully this year.

We're working to build up more liquidity on the exchange, which will attract more users and make trading easier.

We're always a bit surprised at the number of Bitcoiners who haven't actually used Lightning very much!

We're all for hodling BTC in cold storage, but we think more Bitcoiners should move some BTC onto Lightning and try out all the apps, services, and ways to use BTC on this network. This is a big part of the reason we enabled on-chain deposits to Kollider Wallet. It's a super simple way to get on-chain BTC onto Lightning.

Outside of that, we strongly believe that we need to focus on making Bitcoin more useful and more usable in order to attract a ton more users. Which is why UI/UX is such a big focus of ours.

Appreciate the kind words and the support! We also agree on the USDC and USDT part. To your questions"

The synthetics and the backend of the wallet are actually handled in an open source project that we maintain. Its called Lndhubx and you can find it here: https://github.com/kolliderhq/lndhubx. Anyone can deploy this and issue their own synthetics. This would also work for a single person who has a node and wants to hedge some of their node balance.

Yes we think so. DLC's are quite promising. However there is a lot to learn as well in terms of behaviour of these synthetics as well as building up the liquidity. Right now we think that the most important thing is to get people in as smoothly and easily as possible. Once DLC's are ready and battle tested we can just swap out the backend, users and liquidity providers will be there in masses. Also as mentioned above, part of the counterparty risk can be mitigated by just plugging into many exchanges, not just Kollider. For example, you could hedge part of your synthetic on Kollider, some on Okex, some on Deribit and so on. Distribute the risk. We think this can already make a meaningful difference if shit hits the fan with any of those. You could have a DAO with an insurance fund that pays out if one of them vanishes.

There are 3 scenarios where a depeg occurs: a. Bitcoin price tanks and longs get liquidated to a point where buy liquidity vanishes and no one takes on these short (synthetic stable coin holders). In this scenario Kolliders risk engine will deleverage everyone and synthetic stable coin holders will be paid back Bitcoin of the amount of synthetics they hold at that time. b. Exchange gets hacked or disappears. c. Long periods of negative funding. For a) and c) we think that a model where there is an insurance fund that is managed by a DAO could mitigate the damage of these scenarios by paying for the losses. For b) using a basket of different venues could significantly de-risk this scenario.

Good question. Right now it's not clear how AI will affect trading. We're all pretty interested in AI and stay up to date on most developments and tools, so we'll continue playing around with it.

It's possible that in the future AIs will use BTC as their primary currency, even among one another. So maybe it will be mostly AIs trading at some point in the far future!

Kollider is still primarily a trading platform.

Kollider Exchange powers basically everything that we do. The synthetic stablecoins and the swaps that are built into the wallet are only possible because they're powered by the exchange on the back end. The synthetic stablecoins are actually created using derivatives to hedge BTC on the exchange. So in some ways, the wallet is really an app that's build on top of the exchange infrastructure.

We're definitely excited about Nostr, especially because we think there's going to be a growing crossover between the world of Lightning and the world of Nostr, hence the relay as well as building a lot of Nostr features into the wallet to make it super easy for users to access both.

This is a good primer!

Plus:

Right now we only support Chrome, Firefox, and Brave. But we'll take a look and see what we can do!

Yes you can. Just go to Settings -> Nostr -> Edit and copy your keys in there. Keep in mind that your keys are stored in local storage of your Browser. If you're switching your browser or whipe your local storage the keys are gone. Make sure you back them but but I'd guess you've done that if you bring your already existing keys.

Generally we're not opposed to kyc and would always want to comply with the rules and regulations of specific jurisdictions. We think that kyc is a small price to pay for people that can't access an open and permissionless banking system today. Subscribing to a no kyc forever regime also means that the company could probably never grow to a meaningful size. For now payments and sizes of lightning network transactions are small but in time we think this will grow and some form of kyc will be necessary. Maybe not for everyone.