Sagefund

sagefund

a SWOT analysis is an evaluation of the fundamental, operational, technical, social, economic, and even to some degree administrative elements of a project. This is not a model to be used for trading purposes. (NFA, ) Note: DYOR Composed of four elements, Strengths, Weaknesses, Opportunities, and Threats, a analysis framework provides excellent insight for establishing a high-level understanding of the state of a project's well-being through the lens of a birds-eye view. SWOT It can help formulate decisions around which areas require more attention, set performance goals, and organize a foundational understanding of where a project is headed. Rarely (if ever) used in crypto, it is time to apply this timeless method of evaluation to the digital asset space. Today, Sia (SC), the OG marketplace and decentralized cloud storage provider that is based on a proof-of-work system, will get a SWOT. 💪 Strengths (Internal) (Helpful) Sia is one of the oldest remaining generation one projects that actually had its first token sale (at the time called Sianotes) before Ethereum ever had its own. Arriving on the scene in that generation also imbued a fundamental system architecture that is rooted in proof-of-work, arguably the most decentralized consensus model. Moreover, being rooted so early in the budding industry that was extremely tightly knit (due to very few participants) gave the project immense potential exposure to build relationships with many of today's most prominent market participants. Being an OG Whenever users are entering agreements for network resources, the SC coin must be locked up in an escrow account. Because Sia is a Proof-of-work system, there is no native "staking" modules, however, there is a strong resemblance of SFA (stake-for-access) business logic. This potentially can create positive medium-term upward pressure on the SC token price. Contract Model for Acquiring Network Services Cost Effective Storage Considering that Sia was established as far back as 2013 in an MIT Hackathon and its blockchain was operational in 2015, it is astounding that even after a multitude of new generation solutions came to market, Sia still remains one of the most affordable in terms of storage cost. Coming in at approximately $2.00 per Terabyte per month, Sia's storage costs rank 2nd across the entire decentralized market (behind only Filecoin) and leaps ahead of any centralized solution. Settlement with the SEC Both a strength and a weakness. Resolving issues with the SEC through a settlement positions Sia well to avoid regulatory kurfuffle in the future. In the event of any global crypto crackdown, a foundation of compliance gives them an opportunity to circumvent being targeted. Should other decentralized solutions that have not been able to and will not be given a chance to resolve their regulatory relationships, Sia will, by pure serendipity, inherit all of their market shares. The settlement was around their dual token model SC and SF. SC (Siacoins) have been deemed not a security, however, the SF (SiaFund) tokens were deemed a security as they pay out portions of revenue generated by utilization of the underlying network. SF is now registered with the SEC as a digital security. There are three applications that are already deployed as beta's/alpha's available on GitHub or are currently in the process of being developed that will serve as the endpoints that enhance user experiences. Renterd, hostd, and walletd. Renterd is a consumer-facing application for creating contracts and buying network storage. Hostd is an administrative panel for network storage providers to organize their operations. Walletd will serve as the focal point for interacting with SC and SF (Siafund) tokens. Development of User Interfaces The role of SC and its economic significance in the Sia ecosystem is very direct and simple. Given that the SC must be locked into contract escrows and that network utilities can only be paid for in SC, in the event that the demand for on-chain storage explodes, the unit value of SC should follow/lead very closely in tandem. If the token value explodes upwards, it can be assumed that over the next weeks/months, the amount of new contracts will likely increase. Strong Network-to-Token Dependency 😞 Weaknesses (Internal) (Harmful) Perpetual inflation of a digital asset exerts a constant downward drag on price. While the inflation rate (as a percentage of total circulating supply) will eventually taper off around the 2.9% mark, the simple fact that it never stops turns the SC into a poor choice for value retention. Unlimited max Supply Even though this problem is currently being addressed, the fact that after so many years on the market, they have not been able to provide something so fundamental/basic is a bit strange. While other projects are able to attract new users, Siacoin is unable to because of something as seemingly trivial as an interface. Lacking Adequate User Interfaces While Proof-of-work is the "puritans" Sybil protection mechanism, the application of it is very limited due to the prohibitive costs associated with its computation. Moreover, POW is subject to limitations based on the processing capabilities (as measured against the level of security provided). Having to work with POW in decentralized file storage systems creates design constraints that potentially hold back the system from realizing necessary levels of scalability. POW algorithm for Decentralized File Storage Both a strength and a weakness. In the SEC settlement, the Sia Foundation arrived at their SF (SaiFund) token being recognized as a security. With this acknowledgment, the ownership of SF is more convoluted than ever before and a huge turnoff for any potential investors because now they know that is they own SF they are immediately liable to the full extent of securities law. Settlement with the SEC Extreme Downwards Drag on Token Value The economic model does not position itself as overly effective, in fact, the majority of the tokeomic design is net-negative on the value of the digital asset itself. No incentive for providers to hold/keep the SC after getting paid, very weak incentive for users to speculate, perpetual inflation, strange (ineffective) attempts at implementing a burn mechanism, and a splitting token model (SC/SF) that accrues to the SF holders, only expediting selloff pressures. 🧐 Opportunities (External) (Helpful) The category that Sia is operating in is considered to be among the largest and primed for continued growth at a CAGR of ~23.4%. The demand for computation shall continue to rise alongside the development of mankind and all of his creations (especially with AI). As computation grows so does the need for memory in which to store all of its associated data. Growth of Decentralized Storage Sector 😳 Threats (External) (Harmful) Skynet Labs Shutdown The entire Sia ecosystem was initially conceived by Nebulas Inc., which later split into two entities that were wholly responsible for developing, promoting, and managing the network. One of these entities was Sky Labs, which contributed tremendously to the business development side of things, bringing tremendous value to the network in the form of new contracts. After the unwind and shutdown of it Sia experienced an ~88% drop in the total active contracts and had an equally strong decline in the instantiation of new ones. *Note on this, whenever the shutdown transpired, other environmental problems (namely Filebases technical hiccups) caused compounded issues. The decentralized Storage sector is easily one of the most promising in terms of the evergrowing market size. Coupled with the highly intelligent caliber of players at the table here that are improving functionality and presenting *potentially better storage solutions, Sia can be rendered suboptimal over the course of time and disregarded. Modernized Competition In crypto, community is everything. Siacoin's long history and insane funding (raising over $300 million USD) would incline us to think that they would have a strong community due to incentives, marketing, and affiliations with influencers. That is not so. The foundation overlooking Sia has disappointed and angered its community so many times with so many downright strange decisions (such as its massive $20,000,000 treasury burn where they literally said they don't know what to do with it because they are scared of potential taxes) that they have been loosing all their original believers and have not been able to recoup any of them. Significant decline of community Takeaway: This one's a heartbreaker. The Siacoin mission is great, but the technology is now so far behind, and the community so far detached that the project seems to be living on a prayer. A lot of delays, controversial system architecture decisions, bag fumbling by the foundation, and involvement with the SEC. There is a disbalance of positives to negatives, with the negatives outnumbering the positives and outweighing their importance. I give them tremendous respect and credit for being able to resolve things with the SEC and still prove the project to have staying power after the fact. Unfortunately, it seems that rather than being beneficiaries of the first generation, they fumbled the bag due to leadership errors and poor decisions; that gap seems to have tilted outside of the realm of a potential recovery and will be taken by newer generation projects. Conclusion: I really want to like Siacoin. I am a huge proponent of proof-of-work systems. I love the Generation One philosophies. However, the current objective state of Sia is disappointing. It seems that even if they deliver on all of their promises, it simply will not be enough to make the project as valuable as it was once perceived to be. Something that was not addressed in depth here is the controversial dual token model that Sia has within its ecosystem: SC and SF. Simply put, SC is the native token for conducting transactions and paying the network fees and SF is a token that earns a portion of all network fees. I am not a fan of dual token models because of how much it skews the vectors at which potential value is captured. Not to mention that SF doesn't even provide governance rights, and over 85% of the supply is owned by the Sia Foundation. Hell no. Would I invest in SC (Siacoins)? All respect to the project, I want to see them succeed, but under the current circumstances, I would never invest in the digital asset. No. Would I invest in SF (Siafunds)? Even though it is SEC-compliant and provides revenue, I simply do not believe that out of all the opportunities in the crypto industry, this one is worth spending time or taking a risk on. If you know something that I don't or feel as though I might have missed anything worth noting, please do share, I would tremendously appreciate some feedback. Thank you so much for reading, I hope this serves you well on your journey. Live long and prosper 🥂 Also published here.

The Siacoin (SC) SWOT Analysis

The Scandinavian peoples hold to-day a position

obj = ItemObject()
.addItem( )
.addItem( )
.removeItem( ) const new 'a' 'b' 'c' Is there anyone who doesn't like ? It makes programming so much easier. I recently experimented on converting a callback based API into a fluent api. fluent interfaces Let's take the following class as an example. It has 3 methods and each expects a callback. If we wanted to run all of them in order, we would have to call them in a nested way as shown at the bottom of the snippet. Callback = ; Task {
  func1(callback?: Callback){
    setTimeout( { .log( ); callback && callback();
    }, );
  }

  func2(callback?: Callback){
    setTimeout( { .log( ); callback && callback();
    }, );
  }

  func3(callback?: Callback){
    setTimeout( { .log( ); callback && callback();
    }, );
  }
} obj = Task();
obj.func1( {
  obj.func2( {
    obj.func3();
  })
}); export type ( )=> err?: , data?: any any void export class => () console 'function 1' return 1000 => () console 'function 2' return 1000 => () console 'function 3' return 1000 const new => () => () This will run as you would expect. Each function will run in order and 1 second apart. However, wouldn't it be nicer if we could chain methods? Ok long story short, here is how I accomplished it: Callback = ; Stage {
  func: Callback;
  callback: Callback;
} FluidTask { stack: Stage[] = []; isRunning = ; stager(func: Callback, callback?: Callback){ .stack.push({ func, callback }); (! .isRunning){ .stageRunner();
    }
  } stageRunner(){ stage = .stack.shift(); (!stage){ .isRunning = ; ;
    } .isRunning = ;
    stage.func( {
      stage.callback && stage.callback(err, data); .stageRunner();
    });
  } _func1(callback?: Callback){
    setTimeout( { .log( ); callback && callback();
    }, );
  } _func2(callback?: Callback){
    setTimeout( { .log( ); callback && callback();
    }, );
  } _func3(callback?: Callback){
    setTimeout( { .log( ); callback && callback();
    }, );
  }

  func1(callback?: Callback){ .stager( ._func1(cb), callback); ;
  }

  func2(callback?: Callback){ .stager( ._func2(cb), callback); ;
  }

  func3(callback?: Callback){ .stager( ._func3(cb), callback); ;
  }
} FluidTask()
.func1()
.func2( .log( ))
.func3()
; export type ( )=> err?: , data?: any any void interface export class private private false private this if this this private const this if this false return this true ( )=> err, data this private => () console 'function 1' return 1000 private => () console 'function 2' return 1000 private => () console 'function 3' return 1000 this ( )=> cb this return this this ( )=> cb this return this this ( )=> cb this return this new => () console 'function 2 has finished' and voila! Let me explain what's going on! There are two main methods and . stager stageRunner stack: Stage[] = []; isRunning = ; stager(func: Callback, callback?: Callback){ .stack.push({ func, callback }); (! .isRunning){ .stageRunner();
    }
  } private private false private this if this this method expects two arguments. The first one is the function to be executed and the second one is the callback to be called when the function is done. It pushes these two values the stack and if it's not running we will call the method . stager stageRunner stageRunner(){ stage = .stack.shift(); (!stage){ .isRunning = ; ;
    } .isRunning = ;
    stage.func( {
      stage.callback && stage.callback(err, data); .stageRunner();
    });
  } private const this if this false return this true ( )=> err, data this This method will be called recursively. It will take the first item out and easy enough, if it's undefined, it will mark as not running and return. If it has an item, that means we have the function. We call the function with a callback that wraps the original callback that we stored. func This is the reason why we needed to save the original callback so that we can know when the execution finishes. And then the obvious, call . stageRunner Let's look at one of the methods now! _func1(callback?: Callback){
    setTimeout( { .log( ); callback && callback();
    }, );
  }

  func1(callback?: Callback){ .stager( ._func1(cb), callback); ;
  } private => () console 'function 1' return 1000 this ( )=> cb this return this In , the function calls the method and passes in a callback function: This is the function to be executed. func1 stager (cb)=> this._func2(cb) When its turn, essentially the following will happen: this._func2((err, data) => callback(err, data)); and finally so that we can return the object reference to chain  other methods. return this; FluidTask()
.func1()
.func2( .log( ))
.func3()
.func1( .log( ))
; new => () console 'function 2 has finished' => () console 'this is fun'

Fluent Interface With Callbacks

How to Chat With Your Data Using OpenAI, Pinecone, Airbyte and Langchain: A Guide

It’s not a long time ago when creating an iOS app or widget was solely available only for Objective-C or Swift developers with a solid Apple dev background (and of course, macOS device for development). These days, with a app, it’s possible to create a native iOS widget even with basic JavaScript knowledge. Scriptable In this short tutorial, we’ll create an iOS home screen widget that will display scraped content directly on our iOS device home screen. For example purpose, we’ll scrape losers page, we’ll get ticker symbol, name, and daily percentage change. Our script will also serialize these pieces of data into a JSON data source. This JSON file will be updated and published every hour by GitHub Actions. In the end, we use the Scriptable app for getting this JSON data and transform them into an iOS widget. yahoo.finance Of course, we could scrape URL directly using just JavaScript in our Scriptable script, however, we don’t need this data in real-time and I believe python and its packages are more suitable for this kind of task. Scriptable what? is an app for iOS devices. In a nutshell, it allows you to write JavaScript code that will be under the hood translated into native iOS code. It provides you with a variety of nice APIs for creating an iOS widget user interface, networking, notifications, and . For skilled iOS developers, this might sound like magic (or it might remind you React Native, Cordova, or even PhoneGap). If you are wondering how it works under the hood I’d recommend this with the creator of Scriptable, . Scriptable many more great podcast Simon B. Støvring Battleplan Scrape the URL and create JSON with the scraped content Persist and serve data source JSON via GitHub pages Update JSON content every hour with GitHub action Get JSON content in Scriptable’s JavaScript Setup and present iOS widget You’ll also need an iOS device with an installed Scriptable app, a GitHub account, and $0 for infrastructure. 1. Scrape the URL and create JSON with the scraped content Create new GitHub repo and add a new python script (in my case ). main.py requests bs4 BeautifulSoup os json datetime

loosers_url = loosers_response = requests.get(loosers_url)
loosers_page = BeautifulSoup(loosers_response.text, )
loosers_table = loosers_page.find( )
looser_rows = loosers_table.find_all( )

result_json_content = {}
result_json_content[ ] = datetime.datetime.now().strftime( )
result_json_content[ ] = [] looser_row looser_rows:
  cells = looser_row.find_all( )
  ticker = cells[ ].find( ).string
  name = cells[ ].text
  change = cells[ ].find( ).string
  result_json_content[ ].append({ : ticker, : name, : change
  })

loosers_json_filename = os.path.exists(loosers_json_filename):
  os.remove(loosers_json_filename) open(loosers_json_filename, ) loosers_json_file:
  json.dump(result_json_content, loosers_json_file) import from import import import import 'https://finance.yahoo.com/losers/' 'html.parser' 'tbody' 'tr' 'timestamp' '%c' 'loosers' for in 'td' 0 'a' 1 4 'span' 'loosers' 'ticker' 'name' 'change' 'docs/result.json' if with 'a' as This python script gets the content of the URL using the package. With we’ll find data we are interested in (ticker symbol, name, and percentage). At the end of the script, we are using and packages for serializing and storing JSON on the path. We'll later publish this docs directory to GitHub pages so our data source is available for our iOS widget. requests BeautifulSoup JSON os docs/result.json Do not forget to add . requirements.txt beautifulsoup4
requests==2.23.0 This file is used by GitHub actions for installing dependencies. 2.Persist and serve data source JSON via GitHub Pages Our JSON data source will be served by GitHub Pages — go to of your repository and enable for your folder in your main branch. At his time, the content of the directory does not exist yet. JSON content will be re-created periodically by the GitHub Action. Settings GitHub Pages docs docs 3. Update JSON content every hour with GitHub action In the root of your create new . .github/workflows/ pythonapp.yml # This workflow will install Python dependencies, run tests and lint with a single version of Python # For more information see: https://help.github.com/actions/language-and-framework-guides/using-python-with-github-actions name: Python application on: push: branches: [ main ] pull_request: branches: [ main ] schedule: - cron: '0 13-23 * * 1-5' jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: Set up Python 3.8 uses: actions/setup-python@v1 with: python-version: 3.8 - name: Install dependencies run: |
        python -m pip install --upgrade pip
        pip install -r requirements.txt - name: Run script run: |
        python main.py - name: Deploy page run: |
        git config --local user.email "action@github.com"
        git config --local user.name "GitHub Action"
        git add docs/result.json -f
        git commit -m "Update docs/result.json" -a
        git push "https://makma:$ @github.com/makma/scriptable-stocks.git" HEAD:main --follow-tags {{ secrets.GITHUB_PERSONAL_TOKEN }} Edit the last line of the script according to your repository name and GitHub handle. This action will run . If you want to change this behavior, just edit the cron expression. In addition, it also pushes serialized JSON into the folder - this behavior is defined in the step. at minute 0 past every hour from 13 through 23 on every day-of-week from Monday through Friday docs Deploy page 4. Get JSON content in Scriptable's JavaScript In the Scriptable app create a new script with the following code.  This is basically the code of the widget on your iOS device. It renders a medium widget with the first seven losers. dataUrl = ; widget = createWidget();
Script.setWidget(widget);
widget.presentMedium();
Script.complete(); { widget = ListWidget(); data = Request(dataUrl).loadJSON(); titleRow = widget.addText( );
    titleRow.font = Font.boldSystemFont( );
    titleRow.textColor = Color.white();
    widget.addSpacer( ); (i = ; i < ; i++) { looser = data.loosers[i]; row = leftColumn.addText( );
        row.font = Font.semiboldSystemFont( );
    } gradient = LinearGradient()
    
    gradient.colors = [ Color( ), Color( )];
    gradient.locations =  [ , ];
    
    widget.backgroundGradient = gradient widget;
} // Variables used by Scriptable. // These must be at the very top of the file. Do not edit. // icon-color: red; icon-glyph: magic; const "https://makma.github.io/scriptable-stocks/result.json" let await async ( ) function createWidget const new const await new let `Losers ` ${data.timestamp} 15 5 for 0 7 const let ` ` ${looser.ticker} ${looser.change} 14 let new new "3a8cc1" new "00A9D6" 0 1 return Change data URL to your JSON data source published on GitHub pages. Protip: Use the Scriptable app directory in your iCloud drive. You can see all your scripts here. Moreover, you can write code directly in your favorite IDE on your PC or Mac. 5. Setup and present iOS widget The last step is adding the widget to your screen. Add a new script to the Scriptable app and add a new Scriptable widget. Select and set your Script. Medium size Your new widget should be displayed now. You can find all the files and source code on . GitHub Disclaimer: I’m not connected with the Scriptable app or Yahoo.

Stories, News & Mentions about SAGEFUND

Sagefund’s Stories on HackerNoon