BTCPay Server VS ASP.NET Core

Bitcoin users abandoned bitpay about six years ago during the blocksize wars, because they joined the bcash attack. Now anyone that wants to accept bitcoin payments, and especiallly through lightning, uses the open-source btcpay.

> It was also an interesting learning experience, implementing it was much harder than we anticipated and I hope others in the same position can benefit from our learnings.

Well done, never mind that guy, he clearly has an axe to grind and doesn't seem to grasp very much other than his out of touch talking points: did you look into using BTCPAY [0] server?

Things are still not as easy as they should, but have seriously advanced in the last few years.

0: https://btcpayserver.org/

Game changer for us is BTCPay Server since a big point of crypto is removing banks/middlemen. Rock solid and bitcoin goes directly to our wallet that we control the private keys for. No Coinbase. No Bitpay. Just actual bitcoin. Highly recommended

Since the transaction which would be running are not going to be that large of a quantities where each and every % matters, I think it would be safer to go with something like nodeless as referred. For some larger operations https://btcpayserver.org/ would be somewhat better. Thank you for the help!

Did you teach them about lightning? BTCPay Server?

Merchant using BTCPay Server

This approach to organizing middleware enhances code readability, maintainability, and reusability. By following this encapsulation pattern, you're adhering to best practices in ASP.NET Core development, ensuring your application remains well-organized and scalable.

🌟.NET 9 Preview 2 ➡️.NET 9 Preview 2 Discussion ➡️ASP.NET Core updates in .NET 9 Preview 2 ➡️ASP.NET Core updates in .NET 9 Preview 2 Release Notes ➡️EF Core updates in .NET 9 Preview 2 ➡️.NET Aspire preview 4 - .NET Aspire

https://github.com/dotnet/aspnetcore/issues/50643

Even if you look at Microsoft’s by far most popular GitHub project, they’re still only half as big as SupaBase. If you believe “the SupaBase story”, SupaBase grew and became twice as large as Microsoft in 3 years. Below is their likes over time if you’re curious, together with a couple of additional “too good to be true” Silicon Valley projects.

https://github.com/dotnet/aspnetcore/issues/10117

To achieve these objectives, we will take inspiration from ASP.NET Core Identity's PasswordHasher class. It incorporates a concept of hash versioning, allowing only the number of iterations to be modified.

yes I watched several courses, may be aim not getting clearly. but i worked with asp.net which uses http call and firebase cloud function also which uses socket connection, for socket connection its makes sense to use observable bcoz there streams of data we can observe once the connection establish ,but for http it need to be call every time.

As I'm not utilizing ASP.NET, despite its resource-intensive nature and occasional unpredictability, I prefer the cost-free option. I'm hesitant to invest in EPPlus or engage in trials, and moreover, I am more proficient with Interop. Given the limited volume of records in my department, there's a preference for utilizing tools covered by our existing license. This avoids the need for navigating through layers of approval within the chain of command and ensures compliance with our contractual agreements and Microsoft's patch management, ultimately aligning with a cost-saving mindset.