Inspiration
While completing my studies in the U of Nicosia Masters degree in Crypto Currency, I dreamed of creating my own "Wall Street" - my own next Gen Crypto based Fintech, Financial Instruments. And to do that I decided what I needed was "Tokenized in a Box" The tokenzied system of predefined smart contract types embodies an immense intellectual capital for correct legal business fintech workflows. This implies a significant learning curve to become proficient at designing smart contracts based on the tokenized core set of Assets and Actions. A "tokenized in a box" platform accessible to the individual student of tokenized would be of great value for learning and later professional contract modelling purposes. Subsequently I branched out into Social Good applications such as project "greenlight" for creating Attestations of Recovery for COVID19 Survivors.
What it does
Tokenized has not yet publicly released any app to assist a person to see it working first-hand. I strongly believe that product needs a personal evaluation tool to assist as many people as possible to quickly experience it. Using python3 the greenlight app I wrote orchestrates the existing Tokenized services into a relatively usable REST API and provides a sample python script which demonstrates creating a smart contract for Common Shares and performs common smart contract Actions such as Transferring shares. I believe the Shareholder functionality is useful in a wide variety of applications.
How I built it
I read the setup guide "Tokenized-smart-contract-agent-setup-final.pdf" and decided to implement it in python code rather than having to perform manual steps at the console. I wrote a python 3 flask REST API to orchestrate the Development / Debugging version of tokenized by having the python code monitor and parse the debugging messages coming back from the Tokenized Command Line Interpreter (CLI) and then act appropriately to script the CLI to execute common processing tasks for the smart contract. I purposely avoided modifying the golang layers because all the docs on how to run it were in terms of CLI commands and my goal was to create a useful tool soon for the purpose of running contracts to study and learn tokenized smart contract design soon - not to become an expert on the golang api for no real operational learning benefit. In a later phase, for sure I plan to morph my CLI-based approach into using the golang API plus payment channels.
Challenges I ran into
The design of the current release "bucks the trend" / uses tokenized "in a way that was not intended" by leveraging the Command Line Interface (CLI) and the tracing messages of the debug build, but this approach can be easily shown to be the most productive at the current time. A straight forward path exists to ultimately evolve this implementation to be compatible with the mainstream code. There exists a tutorial in Tokenized-smart-contract-agent-setup-final.pdf but it only hinted at the 'how to' in certain critical steps. So I had to ask questions on the tokenized forum and then run many experiments. A major challenge has been to get the 'sync' operation working reliably. It works well now. Another challenge is to host greenlight. Within this deadline I am only able to host it from my laptop. I have plans to soon host it in the Cloud. Creating a UI rich enough to represent this kind of blockchain business processing also required much research. Within this deadline, I was only able to find an appropriate UI Sample and build it and then I provided detailed notes on my plans to modify the Sample to work with greenlight. I have provided the Android .apk of the sample to give an idea on how it will ultimately work.
Accomplishments that I'm proud of
I created a BSV app of significant value to both business and individuals over the long term.
What I learned
My plan was good. I know what I am doing. The python program works great. I got a lot of great info from responses to my tokenized forum questions. I correctly concluded that the tokenized debug build logging is sufficiently rich and structured to be able to support Orchestrating the Smart Contract Workflow automation via python scripts wrapped in a REST API. dyndns does not work with many home WIFI Routers anymore. I tried to setup my laptop to host greenlight to external IP addresses outside my home router network, but no luck. So I will have to move the code to Google App Engine in the cloud so that everyone can run it. I will do that soon.
What's next for greenlight
-Move the code to a Serverless platform to make it easier to demo. -Continue working to complete a Minimum Viable UI -Demo what I already have working to Major Fintech players in Manhattan. -Work on a payment channel to replace the development mode debugging messages that my code depends on so that the production release of the code can be used without debugging messages but instead, the production code stream will be enhanced to output necessary events to a payment channel and the python code will listen to the necessary events on the payment channel rather than parse debugging messages. -Develop the many other spinoff application ideas I have for my tokenized-based tools.
greenlight Youtube videosl: https://www.youtube.com/watch?v=XhmSKv9SeYw greenlight overview https://www.youtube.com/watch?v=_7hU16gOv9Q demo running on virtual box - Part 1
Log in or sign up for Devpost to join the conversation.