Took ~24 hours to implement a new blockchain on top of the #Avalanche HyperSDK that allows anyone to mint, transfer, and trade user-created tokens...all on-chain.
Cleaning up the README now and expect to merge it in the morning: github.com/ava-labs/hyper…
#HyperSDKJournal
Cleaning up the README now and expect to merge it in the morning: github.com/ava-labs/hyper…
#HyperSDKJournal
https://twitter.com/_patrickogrady/status/1628587184247939072
To make the trading UX more accessible, the "TokenVM" includes an in-memory order book to track all open offers on-chain (which it then serves over RPC).
Best of all? It only took a couple hundred lines of code for Actions, Auth, and Storage (other packages are boilerplate).
Best of all? It only took a couple hundred lines of code for Actions, Auth, and Storage (other packages are boilerplate).
Core Packages:
Actions: 600 lines of code
Auth: 108 lines of code
Storage: 322 lines of code
The remainder is boilerplate stuff I need to abstract better/wrap in functions so I don't need to re-implement 😅.
Actions: 600 lines of code
Auth: 108 lines of code
Storage: 322 lines of code
The remainder is boilerplate stuff I need to abstract better/wrap in functions so I don't need to re-implement 😅.
Next up: Adding #Avalanche Warp Messaging so you can bridge your user-created assets to other TokenVMs on different Subnets.
Quick Detour....
Decided to do a quick pass on increasing token functionality before migrating my energy to AWM: github.com/ava-labs/hyper…
This will add support for minting from the same token multiple times (instead of just during creation), adding mutating metadata (to support… twitter.com/i/web/status/1…
Decided to do a quick pass on increasing token functionality before migrating my energy to AWM: github.com/ava-labs/hyper…
This will add support for minting from the same token multiple times (instead of just during creation), adding mutating metadata (to support… twitter.com/i/web/status/1…
Just added a bunch of new token functionality. I now think this is enough to merge the TokenVM MVP.
Will do so after getting the README ready: github.com/ava-labs/hyper…
#HyperSDKJournal
Will do so after getting the README ready: github.com/ava-labs/hyper…
#HyperSDKJournal
Another takeaway after working on this improved token functionality is that I find it much easier to add complex functionality than a traditional smart contract (mostly because I just get to write directly in Golang and use all its tooling out-of-the-box):
* I can directly use… twitter.com/i/web/status/1…
* I can directly use… twitter.com/i/web/status/1…
Turns out I accidentally implemented a sandwich-resistant trading mechanism in the TokenVM by requiring orders to be explicitly specified when filling (needed for populating a transaction's "StateKeys")...
Quick Background:
When trading on the TokenVM, you interact directly with… twitter.com/i/web/status/1…
Quick Background:
When trading on the TokenVM, you interact directly with… twitter.com/i/web/status/1…
The obvious downside of this design is that transactions that seek to fill contentious orders (good deals) will probably have non-trivial revert rates.
Will have to keep an eye on that and see if it gets out-of-hand (probably a function of average order size)...
Will have to keep an eye on that and see if it gets out-of-hand (probably a function of average order size)...
Will post a walkthrough + video demo of this when I merge it. I'm having a blast lol.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
