Re: Open Source Release of a Privacy Focused Cryptocurrency Exchange
Hello, I'm Alison Bobert.
For many years, I've been actively involved in the cryptocurrency space and remain dedicated to Satoshi Nakamoto's original vision, which includes ideas like decentralisation, privacy, inflation resistance, and autonomy from banks and the governments, unlike many institutions today (e.g., the ETH Foundation) that prioritise compliance and centralisation above all.
For many years, I've been actively involved in the cryptocurrency space and remain dedicated to Satoshi Nakamoto's original vision, which includes ideas like decentralisation, privacy, inflation resistance, and autonomy from banks and the governments, unlike many institutions today (e.g., the ETH Foundation) that prioritise compliance and centralisation above all.
Hello Alison Bobert! I am Vod and I guess due to lack of response I'll be your boob licking guide on your crypto adventure! The most important difference with this forum is the money is irreversible, so do not write anything you are not prepared to prove. Once a member is viewed as a liar their history and beliefs do not mean much.
Technical Details
The backend is written entirely in Go, providing cross-platform support (though currently only tested on Windows).It maintains a minimal amount of imports to reduce potential attack surfaces while implementing advanced form parsing for additional security. Price data is retrieved via CoinMarketCap's WebSocket API. The system requires users to run their own full nodes for each supported cryptocurrency - following the essential "don't trust, verify" principle. In my setup, Bitcoin, Litecoin, and Monero nodes ran on one server, while the Ethereum node (using Lighthouse + Geth) ran on another. The architecture leverages Go interfaces, making it easy to add support for additional cryptocurrencies without modifying core design. All operations, including refund processing, are fully automated and utilise anonymised data for troubleshooting. Notably, except for price feeds from CoinMarketCap, all functionality is handled locally through node interactions without relying on third-party services.
The backend is written entirely in Go, providing cross-platform support (though currently only tested on Windows).It maintains a minimal amount of imports to reduce potential attack surfaces while implementing advanced form parsing for additional security. Price data is retrieved via CoinMarketCap's WebSocket API. The system requires users to run their own full nodes for each supported cryptocurrency - following the essential "don't trust, verify" principle. In my setup, Bitcoin, Litecoin, and Monero nodes ran on one server, while the Ethereum node (using Lighthouse + Geth) ran on another. The architecture leverages Go interfaces, making it easy to add support for additional cryptocurrencies without modifying core design. All operations, including refund processing, are fully automated and utilise anonymised data for troubleshooting. Notably, except for price feeds from CoinMarketCap, all functionality is handled locally through node interactions without relying on third-party services.
I like your idea in principle - everything should be transparent and on smart contracts. I don't like the non-KYC part, as that could make it illegal. It is in the spirit of Satoshi, but like any following, it has honest members, and dishonest ones. The bad actors have ruined it for everyone, so consider coding the KYC as an option.
What do you mean by "utilise anonymised data for troubleshooting"? Anonymised data can be used for research, but troubleshooting requires specific information.
Also "It maintains a minimal amount of imports to reduce potential attack surfaces while implementing advanced form parsing for additional security." Programming use libraries/imports, unless you code yourself. With the impressive feature list I don't think you would take the time to write advanced code that is more secure than peer review.
Please don't see this as an attack - I genuinely like your idea. You don't need to clarify/explain anything but if you could describe the features in a different way, I'd be interested in discussing it.