The Launch of Shadow Cloud

    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Introduction 💭
    db_img

    The Basics of Shadow Cloud

    • The Shadow Ecosystem is a series of trustless infrastructure layers focused on a path to decentralizing the traditional cloud stack. Using distributed ledger technology, Shadow Cloud will take advantage of high-powered mobile storage and compute as well as rapidly reducing costs of enterprise grade data center storage. We call this core technology D.A.G.G.E.R.
    • Powered by Shadow Operators, the network provides builders and businesses with storage and compute solutions to optionally expand their web3 presence, or just simply use some of the most highly performant distributed ledger technology for its low cost and resiliency in business.
    • Now cloud compute makes up $400,000,000,000 (that's billion with a B) per year business, and is expected to increase by another $1T by 2030.
    • The Shadow Platform is a stable high-performance cloud platform on a path to be fully powered by a decentralized network of operators. Unlike traditional cloud platforms, network-generated revenues are sent to Shadow Operators. The Shadow Platform is the only commodity cloud network designed to democratize the hundreds of billions earned each year by traditional cloud platforms without sacrificing performance
    📊Overview
    🧠 Methodology
    🎯The purpose of this dashboard
    ✍About the author
    • To get this information, the solana.core.fact_events tables in the flipsidecrypto database were used It took a lot of time to make a query about this process because of Solana's heavy database, I first used the solana.core.fact_transactions table, but after doing all the work, the data did not come up (query sample), but after a lot of searching, I got this result. I found that each transaction sample is different in the number of Inner Instructions and you can find out what each transaction is related to by filtering their number.
    • Two points:
      • In this dashboard, the transactions (New Drive Storage, Increasing Storage, Decreasing Storage, Requesting To Delete, Recover Drive Marking Immutable Storage, Upload File, Delete Files, and Crank Turned) have been reviewed. It happens and I didn't understand anything about it in the project document, so I can't explain much
      • Upload File and Delete Files seemed to be accessible only in the initial days of the project in the blockchain, and I could not get the other days.
    • I used this contract for this data: 2e1wdyNhUvE76y6yUCvah2KaviavMJYKoRun8acMRBZZ
    • For new and old users, the first transaction of each user is the new user and the subsequent transactions are the old user
    • Also, addresses that had an average of 50 daily transactions or more are active users And I also considered those who were below this number as normal users
    • Only the upload and delete file functions are having issues, and I couldn't manage to retrieve data from a certain date onwards. The problem is that the transaction hashes containing the data were written to a base-58 encoded format in the tables in the database, and there is no command in Snowflake to convert that data back to base-58."
    • The purpose of creating this dashboard is to Key indicators of network performance such as:

    • Transactions over time and what actions are taken

    • New and active users

    • Active storage drives and amount of storage space used

    • $SHDW paid for storage

    • etc. to understand and have a better view of the project

    All queries and codes are written with ❤ and too much ☕ . By Sajjadiii





    Thread🐦

    Loading...
    Loading...
    Loading...
    Loading...