We want SecretAgent users to be able to start playing with Hero and understand the unique advancements of FlowHandlers, DOM Extensions, and understand where we are going.
Someone should be able to stand up a single CloudNode on an AWS machine, push a Datastore to that machine and query it. Nothing more. No UI.
Allow payment to be attached to a Datastore and when queried it forces payment to be included. This includes the minimum ecosystem needed for acquiring Argons and using them. It should also cement the conceptual idea that Ulixee’s sidechain is built to run “on top of a blockchain”.
The goal is to make network deployment actually usable at a scale beyond a single CloudNode. This is also what we will use to stand up the alpha version of Ulixee Cloud.
Add, remove and manage your Cloud nodes/clusters. Manage your datastores, track errors and view your revenue. We also plan on adding an ability to plug in 3rd party services which will require support for approving and managing monthly subscriptions.
Add tooling into ChromeAlive to step through scripts, see results of every command, and deeply inspect all parts of a session. This step also involves troubleshooting when a user is blocked (aka, finding probed APIs, reporting issues, etc).
Add a button to ChromeAlive/Builder that allows packaging and deploying on the Cloud. We will run the Datastore when queried and split the proceeds with the Datastore/Domain.
Allow Datastores to be wrapped as NFTs so their revenue stream can be bought and sold on 3rd party NFT marketplaces.
Assistance writing State Generators and Selector Generators by allowing ChromeAlive interface to select attributes, and then testing cross-Session. Extraction gets tree-shaking to figure out selectors automatically.
We are still running the Mainchain through our single CloudNode, and it’s still going no further than the Genesis Block, however, it is using ProofOfKnowledge to verify new blocks. Anyone can now plug in their compute resources into the Ulixee Cloud and participate in the jobs.
We are still running the Mainchain through our single CloudNode, but now ProofOfKnowdge hashes are being used to actually create and connect blocks. However, it is our single CloudNode that verifies them and chooses the block. Shares are awarded. Argon is on “some exchange” so that the price fluctuates. When the price dips Bonds can be bought. Also, people can move their Argons back and forth between the Sidechain and Mainchain. Etc etc.
We are no longer the only CloudNode that can verify and add blocks to the mainchain. However, we will probably keep some form of control/punishment to keep the network in line (i.e., Bounty Hunters or validators or some similar concept). Also, we are likely injecting the oracle data for CPI values, etc.
The Data Liberation Foundation is no longer required. Mojitos!!!!