Here I can see that my State-Domain (i.e. account) is available in 10 perspectives. The last one at index 9 is the current perspective.<\/p>\n

I can choose to time-travel all the way back to the first state. For this I type \u2018sync\u2019 followed by the perspective of my choice.<\/p>\n

$\"\"$

Synchronizing with a chosen perspective.<\/p><\/div>\n

if I type ‘sync’ alone, the \u22ee\u22ee\u22ee<\/span>VM<\/strong> will synchronize with the current state of the network i.e. with the most recent perspective.<\/p>\n

$\"\"$
Synchronizing with the current world-view.<\/p><\/div>\n
Let\u00a0me see if it actually worked by checking the reported balance:<\/p>\n
$\"\"$
Balance seemingly differs from the one in the past.<\/p><\/div>\n
Certainly it worked! \ud83d\ude01After all, it\u2019s been conceived, researched and implemented by Wizards\ud83e\uddd9. How could it not\ud83d\ude06.<\/p>\n
As you may see above, the values are different. It\u2019s like using a Time-Machine. Congratulations! You\u2019ve just learned not only how to escape the Sandbox, you\u2019ve already learned how to teleport yourself back and forth in time! Can Ethereum do this? Don\u2019t think so.. Let\u2019s keep going!<\/p>\n
The story about Ethereum<\/h4>\n
Why is Ethereum being mentioned in here? Well, to get a better perspective on things in short. Folks behind Ether never managed to research and implement effective data pruning for their VM. Here such mechanics are integrated on day 1. Not only that, as you\u2019ve just seen, you may teleport yourself back and forth across states with ease.<\/p>\n
Accessing previous state in Ethereum is impossible in short, from the perspective of a smart-contract.<\/p>\n
Here are sample places where you may read up on these subjects:<\/p>\n
\n
https:\/\/ethereum.stackexchange.com\/questions\/10534\/do-the-ethereum-clients-store-historic-state-or-just-current-state<\/a><\/li>\n
https:\/\/ethereum.stackexchange.com\/questions\/47215\/how-can-we-obtain-the-state-value-of-a-variable-from-previous-block-number-using<\/a><\/li>\n
https:\/\/ethereum.stackexchange.com\/questions\/29024\/how-to-get-all-historic-changes-of-a-state-variable-in-a-smart-contract<\/a><\/li>\n<\/ul>\n
Folks at Ether built up on Bitcoin.. well, we\u2019ve researched everything from the bottom up there\u2019s not a single line in common with other projects. We\u2019ve learned from the best and what you\u2019re seeing right now is a true peace of Art. It is\ud83d\ude4f.<\/p>\n
State-Channels and Off The Chain Transactions<\/h4>\n
These are already described quite a lot within the White Paper as far as theory goes. Here we are about practice.<\/p>\n
What\u2019s wrong with on-the-chain transactions? Is there anything wrong with these?<\/p>\n
As you might know, decentralized state-machines, they\u2019ve got a problem. They do not scale so well. If somebody is trying to sell you yet another decentralized computer, you might want to think twice. You need to be aware that both Bitcoin and Ethereum these are products. Somebody is trying to make money on. Either by being an owner or by trying to make returns from investments. Both of these are brands. Both can be assumed to be riding on the peoples\u2019 lack of technical knowledge to some extent. Back when Ethereum was coming out, it caught many by surprise. It actually painted visions of a decentralized computer whereas they\u2019ve ended up with a DOS-like code execution system nobody knows how to use. Sorry, there\u2019s no decentralized computer from the perspective of a typical end-user as far as Ethereum goes. There never was to be. Don\u2019t get me wrong. Folks at Ether, together with its mastermind, Vitalik, they did a lot. But all in all it can be said that just the Bitcoins\u2019 programming language got replaced by a different one.<\/p>\n
Let\u2019s get back to off-the chain and on-the-chain transactions.<\/p>\n
Be it Bitcoin, Ethereum, or even \u22ee\u22ee\u22ee<\/span>GRIDNET OS<\/strong>. Changes done to the decentralized system, they need to replicate across the network. Thus transactions no more are only financial transactions\u00a0sensu stricto but are closer in their meaning within the data processing realm. They can represent arbitrary authenticated operations that are to be executed by nodes maintaining the system.<\/p>\n
Now imagine millions of users use the platform simultaneously. What happens? It gets stuck. What if you were to reward for propagation of data packets of the entire Internet? Would it be possible? Well certainly not with the current blockchain systems.<\/p>\n
Enter \u22ee\u22ee\u22ee<\/span>GRIDNET OS<\/strong> which boards unique implementation of the researched by us State-Less Blockchain Channels, and the related Multi-Dimensional Token Pools.<\/p>\n
Here we are after practice not science so lets stick to it.<\/p>\n
The Snake Multiplayer Game\ud83d\udc0d<\/h4>\nA tutorial describing how to play the game is available\u00a0 here<\/a>.<\/p>\n
Here we are after more technicalities, we will also get to see how to cash-out the received tokens. So that to receive the actual \u22ee\u22ee\u22ee<\/span>GRIDNET Bacis Units (GBUs)<\/p>\n
The game, when launched, tries to access a token pool which was made available by the full-node\u2019s Operator, the one the user is connected to.<\/p>\n
For this to work, the operator has to do sacrifice a certain amount of assets. Those sacrificed assets were not ultimately lost, however. Those would be used to create an off-the-chain value store. The data store is represented on-the-chain by an innovative data structure nicknamed the Multi-Dimensional Token-Pool. The total cumulative value comprising the token pool is up to the value of the sacrificial transaction. Each Pool is comprised of (multiple) dimensions. You may think of each dimension as of a bank. Each such bank can be used to keep rewarding single, unique recipient. When rewarding from the given bank one keeps releasing new versions of a Transmission Token. The recipient may choose to cash-out the Transmission Token anytime but each such operations involves a fee, thus it\u2019s in the recipient\u2019s best interest to keep receiving updated versions off of Transmission Token as long as possible (until resources from a given dimension get depleted or once the recipient is not to receive additional rewards) and cash maximum value at a single processing fee.<\/p>\n
Sounds reasonable? It is\ud83d\ude0a.<\/p>\n
So. For you to be able to receive rewards by playing the Crypto-Snake\ud83d\udc0d game, the Operator sacrificed\u00a010 MILLION GBUs. Now that\u2019s a lot\u00a0\ud83d\ude43.
\nThe Operator used the receipt of the sacrificial transaction to generate a Token-Pool. What are some of the important Token Pool details?<\/p>\n
It would be best to take a look at help displayed by the Token-Pool generation utility:<\/p>\n
$\"\"$
The Token-Pool generation utility.<\/p><\/div>\n
\n
The value – this one is computed automatically for you. The token pool generation utility takes the receipt of a sacrificial transaction and looks it value up.<\/li>\n
The number of dimensions. – that parameter tells how many peers you\u2019ll be able to reward simultaneously.\u00a0The more dimensions the bigger the Token Pool\u2019s data structure and the more expensive it will be to deploy. From our research it turns out you should never be in need to use a token pool with more than 30-100 dimensions. Even when using things like a decentralized YouTube, we plan to deploy.<\/li>\n
Value of a single token – that also gets calculated for you automatically if you don\u2019t provide. It\u2019s the value of a single token within each of the dimensions. Note: value tokens\u00a0within each dimension are the same.<\/li>\n<\/ul>\n
Let\u2019s go about generating a Token Pool of our own!<\/h4>\n
$\"\"$
A sacrifice needs to be made.<\/p><\/div>\n
First I sacrifice 10000 GBUs. The QR will be shown I confirm on the mobile app.<\/p>\n
$\"\"$
Confirming sacrificial transaction with the mobile app.<\/p><\/div>\n
Nice! The important thing to me is the Receipt. I\u2019ll use it while generating the Token Pool.<\/p>\n
Let\u2019s go about using the token-pool utility now.<\/p>\n
Important: We are about to issue yet another transaction. Once containing a Multi-Dimensional Token Pool which will be generated by the mobile app.
\nThus, we need to bing the \u22ee\u22ee\u22ee<\/span>VM<\/strong> into the current state. Otherwise nonce value associated with your account as seen by your \u22ee\u22ee\u22ee<\/span>VM<\/strong>, one used by the Transaction\u2019s Composer would be out of sync and the resulting transaction – rejected.\u00a0Use the \u2018sync\u2019 command now <\/strong>to synchronize with the network now.<\/p>\n
<\/p>\n
$\"\"$
Time to generate the actual Token Pool.<\/p><\/div>\n
I\u2019ve synced and executed \u2018genpool\u2019 just to see the help screen.<\/p>\n
Time to begin formulating new transaction by executing the \u2018Begin Transaction\u2019 command, i.e. \u2018bt\u2019.<\/p>\n
and then executing the \u2018genpool\u2019 command by providing it with the sacrificial transaction,meaning the Receipt of it.<\/p>\n
Let\u2019s go! You\u2019ll be notified that quite a big QR Intent is to be rendered within the Terminal. The system attempts to automatically detect\u00a0the size of your Terminal and warn you or even pause\u00a0execution and wait for you to increase the Terminal\u2019s Width (by resizing its window) should \u22ee\u22ee\u22ee<\/span>GRIDNET OS<\/strong> detect that the width is insufficient.<\/p>\n
$\"\"$
Enormous QR code on the way let us not be afraid.<\/p><\/div>\n
$\"\"$
Certainly the mobile app handles it just fine.<\/p><\/div>\n
That’s quite a BIG QR Intent indeed. Rendered using UNICODE 1.1 characters from the DOS era. The technology never ceases to amaze us.
\nThe mobile GRIDNE Token app seems to have no trouble scanning it as well.<\/p>\n
Once scanned you’ll be shown with a mobile screen looking like one on an iPhone below:<\/p>\n
$\"\"$
Looking good. Certainly the app understands.<\/p><\/div>\n
The app says that you can SWIPE your finger for more. And it actually means it! Let us try shall we\u00a0\ud83d\ude01 Simply swipe to the left on the upper bluish field.<\/p>\n
<\/p>\n
$\"\"$
Well, indeed it does.<\/p><\/div>\n
What just happened? How does the app know.. how does it understand what I\u2019m about to commit? \ud83e\udd2f\u00a0Well:<\/p>\n
\n
the mobile app boards a #GridScript decompiler of its own<\/li>\n
in some cases the mobile app is required to perform computations on its own so it needs to understand perfectly well what\u2019s being done and how the results of computations are about to be delivered to the network.<\/li>\n<\/ul>\n
Here the app, being the only trusted device on the system as per our Security-Threat models, is asked by one of the full nodes to generate a Token Pool. See, the Token Pool couldn\u2019t be generated by the full-node itself as the resulting data structure needs to contain a secret value which cannot be known to the full-node itself. See.. Wizards\ud83e\uddd9\ud83e\uddd9\u200d\u2640\ufe0f really, really.. they took their work.. seriously. They\u2019ve saved upon nothing \ud83d\ude4f<\/p>\n
The description which you see is generated dynamically. Really. What you\u2019re seeing is dynamically generated HTML and CSS representing the tasks to be executed by the mobile app. The app strives to provide\u00a0as accurate description as it possibly can. The cool thing about it is that the app can represent operations it has never been initially prepared for or operations that Wizards\ud83e\uddd9\ud83e\uddd9\u200d\u2640\ufe0f haven\u2019t initially envisioned.<\/p>\n
If you’ve kept track of\u00a0the Project\u00a0for some time already you know very well that the autonomous remote Log-Me-In functionality described\u00a0here\u00a0<\/a>has been implemented and deployed without requiring any updates to the mobile app itself. It simply worked and provided custom, new messages within the mobile app\u2019s UI.<\/p>\n
Let’s keep going and confirm actions\u00a0within the mobile app. An onion routed connection to the very \u22ee\u22ee\u22ee<\/span>VM<\/strong> hosting your SSH session would be initiated and established. The mobile app would keep\u00a0notifying you upon any changes to its status. Interestingly the app receives updates about both the network-layer connectivity, the decentralized state-machine operations, results of tasks related to the remote peer.. and a few others\ud83d\ude06 Quite smart it is, still everything is wrapped in a very minimalistic UI with all the details hidden away for your convenience.<\/p>\n
<\/p>\n
$\"\"$
Onion Routing data to the network.<\/p><\/div>\n
<\/p>\n
If everything goes well, soon\u00a0enough you\u2019ll get to see confirmation within the SSH terminal that a Token Pool has been generated and delivered from the mobile app. The representation of the token Pool Delivered from the mobile app is \u2018disarmed\u2019, meaning it does not contain the secret value but it is enough to be put into the decentralized state machine\u2019s storage and validate any consecutive token you might be issuing on its behalf later on.<\/p>\n
$\"\"$
Disarmed token pool generated by the mobile app has been delivered to the Terminal.<\/p><\/div>\n
An interesting thing to note: the \u22ee\u22ee\u22ee<\/span>VM<\/strong> has already generated, fully autonomously, source code of a transaction whose instructions instruct the decentralized state machine to register the very token pool you mobile app has just delivered. How cool is that? How amazingly sophisticated. Let us keep going, shall we?<\/p>\n
You may view the transaction\u2019s source code by using the previously mentioned \u2018vt\u2019 instruction. There could be a very short friction as the source code is generated. The large portion of text is the base64 encoded Token Pool your mobile app has just provided.<\/p>\n
<\/p>\n
$\"\"$
Lurking into the source code of auto-generated transaction..<\/p><\/div>\n
<\/p>\n
As you may see the entire transaction is 5723 bytes in length.<\/p>\n
$\"\"$
The wall of text is base64 encoded TokenPool data.<\/p><\/div>\n
<\/p>\n
Let\u2019s commit! There\u2019s nothing to wait for. Use Commit Transaction (\u2018ct\u2019). The \u22ee\u22ee\u22ee<\/span>VM<\/strong> would automatically calculate the costs based on the encountered transactions. All you need to do is accept the proposed values\ud83d\ude4f.<\/p>\n
The VM<\/strong> would now show yet another QR intent which asks for your permission to sign and broadcast the just generated transaction. Once you confirm the mobile app would sign it and then onion route it across the network (end-to-end encryption for anonymity at all times).<\/p>\n
<\/p>\n
$\"\"$
We need to broadcast TX instructing for registration of the Token Pool.<\/p><\/div>\n
You are constantly being notified about results…<\/p>\n
$\"\"$
Done!<\/p><\/div>\n
Presumably the transaction got published successfully and is now being processed by the decentralized network of full nodes.<\/p>\n
At any point you may check status of the previous transaction by using the \u2018getresult\u2019 command. If you don\u2019t provide parameter, it will check the result of the most recent transaction. You may, however, provide it with a custom receipt. The utility would contact the network and fetch result along with the stack-frame including meta-data should anything have gone wrong.<\/p>\n
$\"\"$
In the end token pool is stored within a file on the decentralized file-system.<\/p><\/div>\n
Luckily, everything went just fine. Like above you may CD into my directory i.e. use \u2018cd \/CodesInChaos\u2019 and then enter the TokenPools directory to see that the token pool under the name \u2018sample\u2019 indeed is there. What a joy! You may also use full path right away ex.\u00a0\u2018cd \/CodesInChaos\/TokenPools\u2019<\/p>\n
$\"\"$
We may see into it with parameterized Linux-like commands.<\/p><\/div>\n
\u2018sample\u2019 is just another file on the\u00a0GRIDNET OS\u2019 Decentralized File System<\/strong>. This very file is stored in the\u00a0GRIDNET OS<\/strong>Eternal Storage,<\/strong>\u00a0meaning full redundancy at each and every full-node.<\/p>\n
You may use Linux-style \u2018less\u2019 command to view its contents. You may want to use the\u00a0-tp<\/strong>\u00a0parameter so that the binary interpretation layer kicks in and the binary code is treated as a Token-Pool with all the fields depicted as in the picture above.<\/p>\n
How to be using Tokens From a Token Pool will be a subject for another tutorial! Something is telling us you\u2019ll be getting to know how to use these from the GRIDNET Desktop Graphical User Interface very, very soon\u00a0\ud83d\ude01.<\/p>\n
Cashing Out Of Tokens<\/h4>\n
So you\u2019ve played Crypto-Snake a lot and now you want to cash-out your rewards? It\u2019ve very simple.<\/p>\n
Say I had my current Snake Token equal to \u201cCETH71fZGK8nc6yctJBjKTzy7cG92DSsRQhGA6aUzbP5uN82p4zY1VoWo3LLzz3PvQ9uH63zz5bGts3VaZ2myS6oKDadKKYeYi4HchcivMwcqHq799z9dqPnkXajfT1\u201d<\/p>\n
Let\u2019s see what the xtt command shows when I try to cash it out in SandBox. We may use the\u00a0\u2018xtt\u2019<\/strong>\u00a0command, as in the picture below.<\/p>\n
$\"\"$
Cashing out of Tokens generated from a Token Pool.<\/p><\/div>\n
so looks like I would get 10GBUs were I to wrap this code in BT <-> CT block and commit.<\/p>\n
If I want more, I can play Crypto snake further by providing this token during game start<\/p>\n
While playing, I gathered 2 bags of coins. The app provided me with a new token equal to:<\/p>\n
racTiXpHsLyVTfBzNp43A4GK1Pyfmjy3GPFZL54MU3jtm9DX6cyx1DjUxbCy6rY2C9ZcYxYjnNpb6VFEb6fXeykxjq6Nui6tgoiAW6TLDpg122R99F6qv6W74CXSKriK<\/p>\n
$\"\"$
having more!<\/p><\/div>\n
Let’s try to cash it out shall we !<\/p>\n
$\"\"$
The system recognizes the additional reward.<\/p><\/div>\n
Looking good! After collecting 2 more bags of coins in single-player I now have 30GBUs to cash out. Note that it\u2019s not really worthwhile for me to do so since the fees are higher than the rewards. Gotta play Snake some more!\ud83d\ude06.<\/p>\n
Thank you for reading stay tuned!<\/p>\n
This post has been written by CodesInChaos ~one of the Wizards\ud83e\uddd9\ud83e\uddd9\u200d\u2640\ufe0f<\/p>\n
<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
\u22ee\u22ee\u22ee\u00a0Today we will be looking at Stateless-Channels, as described within some of our research papers and Multi-Dimensional Token Pools in particular –…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-375","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/posts\/375","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/comments?post=375"}],"version-history":[{"count":39,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/posts\/375\/revisions"}],"predecessor-version":[{"id":441,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/posts\/375\/revisions\/441"}],"wp:attachment":[{"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/media?parent=375"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/categories?post=375"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/tags?post=375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Let\u2019s go about generating a Token Pool of our own!<\/h4>\nA sacrifice needs to be made.<\/p><\/div>\nFirst I sacrifice 10000 GBUs. The QR will be shown I confirm on the mobile app.<\/p>\n