In the background, we're having a productive conversation with the nxt folks about tokenly, heres the most recent
Hello all,
I am a developer in the nxt space and have been asked to help out with coordinating what can be done with this.
I've looked around at tokenly and gotten the basics of what it does. I believe nxt could assist in a few places here.
An asset vending machine system shouldn't be too difficult to implement inside nxt. Because of how nxt is set up, we are able to build and send transactions without even needing to run a node on the server. A system could be made to create and sign transaction bytes within PHP without an nxt node running. The transaction can send any type of asset, MS token, nxt, or message that's needed.
Also in the way of tokens, I suggest the Monetary System for setting up a token system. I am aware that LTB coin currently uses counterparty as its platform, but should you decide to switch over, you create an MS currency, then map the nxt addresses to throwaway couterparty addresses. The user would generate their own nxt address, then input the address into a page, the page would then calculate a burn address that matches the nxt address inputted, then the page can do a check on what amounts of LTB are in what burn addresses and credit the nxt accounts the same amount.
Another useful nxt feature to use with this would be the token. Nxt Tokens are small strings of characters that can be used to prove the ownership of an account. Say that you want to allow a user into a certain page only if they have x amount of LTB, then you would tell them to generate a token for the pages name "letstalkbitcoin.com" and the wallet will print out 160 characters that have a signature of the account used as well as a timestamp. Then the user enters their token and it is decoded to tell you the account of the user and the time it was created, after that you can make an api request to check the balance and let the user in if it greater than x.
Another possibility is integrating the LTB blogging pages with nxt aliases. Nxt aliases act as a DNS system on top of the blockchain, with them we can store up to 1000 bytes of data that directly refers to a unique string of characters. My idea is that each blog post would have a unique alias associated with it, the alias could hold link information, author data, as well as a sha256 hash of the content of the blog post, so that paranoid people could verify that the text they are reading is untampered with. This also has a timestamp system, because of the time that the alias enters the blockchain with the hash, it can be cryptographically proven that the blog post existed at a specific time. This can be used to settle any disputes that may arise.
On top of that, the way the nxt client is created makes it quite extensible, because it runs on a Javascript layer on top of Java API requests, anyone is able to modify a client to fit their needs. Its possible to make a LTB version of the nxt client that can easily show LTB MS balances and token creation, as well as load asynchronously with the LTB website, so blog posts could be read and tipped from inside a wallet.
