The Run platform consists of jigs (interactive tokens), a JavaScript library for interacting with them, and optional scaling services.
A new jig is created by defining a JavaScript class, instantiating it, and calling methods which generate new Bitcoin transactions for each state update.
Jigs are permissionless, tokenized software objects that support object-oriented principles, and the Run library uses a flexible plugin architecture for different environments.
A demo game shows how players can truly own their in-game assets as jigs, enabling them to trade items outside the application's original scope.
Game logic, such as requiring payment to create an item or restricting actions to specific caller types, is enforced directly within the jig's JavaScript class definition.
Run avoids the performance bottleneck of replaying transaction histories by caching a jig's final state, which is secured by a state hash in the user-signed transaction.
A custom cache implementation prioritizes loading jig state from local memory and browser storage before falling back to fetching it from a game server.
Run plans to offer optional services like a global state cache, pay server, and query server, with a public beta for version 0.6 coming soon.
Copying a jig's code creates a new, distinct object with a unique origin, and Run operates as a hybrid layer 1 and layer 2 protocol for flexibility.
Run provides a base class for fungible tokens that can be extended with custom logic, and it's possible to restrict jig functions using Bitcoin locking scripts.
Jigs can contain partially signed transactions to enable atomic swaps, and the platform functions more like a NoSQL database than a relational one.
46:29Joshua Henslee
33:37Jack Davies & Alessio Pagani
1:16:37Jimmy Nguyen & Steve Shadders
42:37Rafa Jiménez
41:09Evan Freeman
1:06:12Steve Shadders
39:53Brendan Lee
36:55Aaron Russell
Jobs that call for the skills explored in this talk.
Saby Company Page
Sarajevo, Bosnia and Herzegovina
WeMatch GmbH