Quote from: CedricQuotient on March 20, 2015, 06:56:16 PM

Quote from: Blazin604 on March 20, 2015, 04:58:57 PM

What do you guys think of an IN WALLET EXCHANGE? I know something like this is possible as XAI will be implementing one soon. This would also help with making the entire process of converting BTC to SDC more anon.

This plus the ability to share Torrent files and get paid for uploading through the ShadowMarket will make us the Coin killer

Just wanted to point out that XAI is implementing an asset layer, not a decentralized exchange, they are pretty different. Building a true decentralized exchange that does atomic cross-chain transactions is a tall order, and fraught with peril, and is not something I want to attempt to tackle any time soon Tongue

Its a big project, and will take a team of people a fair amount of time. Like a 6 months to 1 year kind of project, not a 1 month kind of project. If, for instance, I wanted to exchange I don't know..say LTC for BTC... facilitating that in a trustless decentralized way while also validating across the other blockchains and accounting for possible forks etc... this is not a tough nut to crack by any means. There are probably a million corner cases to account for.

libsec256 would be cool to see in Shadow, although that's not user-facing, would be a nice optimization.

Protocol encryption would be cool. Use the Shadow encrypted messaging as a way to make an encrypted p2p channel between peers. When they send their version message maybe they exchange keys, then swap over to sending everything encrypted. This wouldn't be terribly hard to implement.

Distribution lists in shadow encrypted messaging might be cool, similar to bitmessage, could open door to building some other things on top of it.

Some defenses against Chainalysis style stuff might be cool to look at, like having transactions broadcast by some other peer, and maybe always rebroadcasting some random set of transactions from the mempool along with it...although that gets tricky I'm pretty sure it can be done in a workable way. Although I guess with the Shadow token there is already some level of protection against their sort of big data analysis/data mining.

Some onion seeds for Shadow would be cool...anyone set any up as hidden services? Not sure if the Shadow code supports onion seeds, I know the newer BTC code does, but you can at the least specify them through config/command line.

Multisig escrow and a user interface for constructing multi-sig transactions would be cool...nobody's done a UI for multisig yet...another thing that would enable other stuff down the road.

Thanks for clearing that up Cedric...glad to see you around here. We could use someone like you around here. Interesting...