sdk VS bitcoin-sv

Another possible aspect he could have meant is that there are some frameworks for BSV that just stash a bunch of javascript code in BSV transactions. Whoever consumes those transactions is expected to run that javascript code to put back together some state. It's what cryptofights is using, in a way that generated a silly number of transactions at one point. You can read about it at https://run.network/ for now, although the folks behind it are moving on, so it's unclear what future it will have. As I understand it, the Run sdk is not intended to run in a browser, but in a node.js environment (and all the state stashed in transactions needs to also be stored in a local database for anything non-trivial to work properly.) Still it's all javascript anyway.

Run

Thanks. I'm just trying to get my head around how diferent languages and environments communicate with eachother and work together. For example, I'm building a game using godot, and need to work with a sdk. and found this godot tutorial on how to use third party sdks. My head is spinning like crazy!

Yeah. I've got the ui and api running locally. I was just wondering if there were existing publicly accessible api services, sorta like how the run token protocol allows for purely browser js blockchain dev.

https://run.network is the SDK of the protocol

Cryptofights is using the Run framework as their underlying game engine/storage/BSV integration mechanism. It's a fun little framework. It stores large chunks of javascript source code in strange places, and expects users of the framework to load and run it in a provided sandbox, as a mean of doing smarter things with transactions. While stopping short of calling itself a smart contract platform, it nonetheless purports to let applications create "tokens, contracts, artwork, elections, games, digital pets, and more." It appears that Run is intended to allow users to use someone else's Run code and objects under some conditions, although their docs could be clearer on how and when exactly that would happen.

Whereas UTXO-based designs get parallelizability by design, creating a programming model around them has been harder, and frankly there aren't even that many people trying. Full-transparency, I've been working to solve this problem, and believe I've cracked it. Check out https://run.network if this interests you.

After regular development activity, all bitcoinSV branches show now activity for over a month.

You can read the license at: https://github.com/bitcoin-sv/bitcoin-sv/blob/master/LICENSE

Have you read the BSV license?

For more information please visit https://www.bitcoinsv.io/ and https://github.com/bitcoin-sv/bitcoin-sv/

There you go: https://github.com/bitcoin-sv/bitcoin-sv/commit/f498f103f6cb8bf033b430723c4d3c5cf567e63f