Bitcoinˢᵛ Dev Stream 📡
2 subscribers
15 photos
1 video
1 file
402 links
Content stream for ₿ˢᵛ apps developers and students of the original Bitcoin protocol.
https://bitcoinsv.dev
Download Telegram
Forwarded from Deleted Account
I released a library for BSV written in C# called BsvSharp that can be found on as NuGet packages with the source on Github (https://github.com/chrissolutions/CafeLib/tree/main/Enterprise/BsvSharp). BsvSharp is heavily based on KzBSV (https://github.com/kzbsv/KzBsv) written by Tones Notes. I wanted to use KzBSV but it doesn't run within Blazor. Blazor is a tool that is use to write WebApps in C#. With BsvSharp, you can write a BSV application end-to-end in C#. Currently, most of the tooling is written in JavaScript with limits development choices. Hopefully this library will open up BSV development to .NET developers like myself.
Forwarded from CSW - Slack Channel (@RamonQuesada 🌷)
It is very simple.

If you are building node software your job is to build a system that follows the protocol exactly. Not 99.9999999999999999999999999999999999999% - that is insufficient. 100%. No exceptions.

Your next requirement is to completely utterly ignore any Twitter troll telling you about things that they need fixed for their wallet because they are inadequate. This is the point, those developers on Twitter who cannot fix their wallet are inadequate. That’s their problem. If they cannot continue, competition will replace them. This is capitalism.

When those building applications failed to make a simple check that ensures the transaction they are receiving has not been seen on the network before, and by that I mean that every input transaction is completely unseen, and that the fees are at least the minimum amount… Then very simply that person can go out of business. I have no problem with this. In fact, it improves the ecosystem. They can either learn to be better developers or they can move on to something else. Don’t think that there’s any other way of looking at this. We want people in the system who can design something and not whine about changing it. If you mark up your web application because you failed to correctly encode the protocol specification, you don’t go to the various protocol specification bodies on the Internet including the IEEE, IETF, IESG and W3C and continue to bitch to them. You fix the application.

This is not a difficult concept. If you build the application and you don’t include all of the requirements, fix your application. Bitcoin does not change for you.

CSW
Feb 26, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1645875168986649?thread_ts=1645875168.986649&cid=C5131HKFX

https://t.me/CSW_Slack/4087
Forwarded from tomothy