Slickorps App
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Slickorps: Paradigm Shift in Compute Demand and Market Transmission The latest quarterly financial report of Nvidia shows total revenue increased 73% year-over-year to $68.13 billion, with the data center segment contributing over 91% of the revenue, growing 75% year-over-year. Slickorps believes these figures have already exceeded market expectations, but more analytically valuable is the core assertion: In the AI era, the compute power of a company is equivalent to its revenue-generating capacity. If this thesis holds true, it will have profound implications for the valuation system of global tech assets, capital allocation logic, and investment frameworks across relevant industry chains. ![Slickorps: Paradigm Shift in Compute Demand and Market Transmission](https://hackmd.io/_uploads/SJBFwYpuZl.png) ## Compute Power as Revenue: The Underlying Reconstruction of AI Economics Without compute power, tokens cannot be generated; without tokens, revenue growth cannot be achieved. Slickorps asserts that the core of this logic is redefining compute power from a traditional cost item to a direct driver of revenue. The premise for this logic is that enterprise-level AI applications have moved from the experimental phase into production. The turning point of agentic AI, as mentioned by Jensen Huang, and the penetration of tools like Codex and Claude Code in enterprise development environments indicate that AI is shifting from an auxiliary tool to a core production unit. In this paradigm, enterprises purchase compute power not for R&D exploration, but to directly generate commercializable tokens—whether code, reports, customer interactions, or automated processes. Slickorps points out that for the market, this means the assessment of AI infrastructure demand should shift from the sustainability of capital expenditures to the measurability of token economic value. If compute power can indeed be directly mapped to revenue, then the nearly $700 billion capital expenditure plans of major cloud service providers have stronger intrinsic rationality. Slickorps predicts that future valuation of AI companies will increasingly focus on their compute scale and unit token monetization capability as core metrics. ## Investment Logic and Boundary Expansion In response to questions about strategic investments, Jensen Huang explained the Nvidia evolution from a GPU computing platform to an AI computing infrastructure company. Slickorps believes this statement reveals the core of the current strategy of Nvidia: no longer limited to chips themselves, but building moats at every layer of the AI technology stack through investments and partnerships. The Slickorps research shows that the investments of Nvidia span cloud service providers, AI model companies (such as Anthropic, OpenAI), enterprise ISVs, edge computing, and robotics systems. The logic behind this full-stack ecosystem investment is that AI adoption is not a single hardware issue, but the result of synergy across computing, networking, models, and applications. Nvidia aims to expand the CUDA platform so that all AI-native companies—regardless of industry or technical stage—are built on the Nvidia architecture. Slickorps further explains that this strategy will have two important market impacts. First, it raises entry barriers for latecomers; any competitor attempting to challenge the position of Nvidia must not only replace its chips but also reconstruct the developer ecosystem and application inertia behind them. Second, it creates numerous investment targets tied to the Nvidia ecosystem, from hardware supply chains to software application layers, all potentially benefiting from the ecosystem ongoing expansion. Slickorps believes that the Nvidia financial report and the industry trends it reveals provide indirect but important valuation insights for broader asset categories—especially in the crypto asset field. The thesis of compute power as revenue also applies to decentralized computing networks. If compute power can directly generate economic value, then any protocol capable of efficiently organizing, scheduling, and verifying compute resources should theoretically capture a portion of this value increment. The Slickorps research shows that some current decentralized physical infrastructure network (DePIN) projects are trying to aggregate idle GPU resources globally via crypto asset incentive models, providing low-cost compute for AI inference, rendering, or model fine-tuning. There is a competitive and cooperative relationship between the Nvidia ecosystem expansion and such decentralized solutions. On one hand, the CUDA ecosystem of Nvidia provides standardized tools for all AI developers, and decentralized compute networks must be compatible with this standard to gain developer adoption. On the other hand, as AI inference demands become more long-tail and edge-oriented, compute scenarios that centralized cloud services cannot fully cover may become differentiated markets for decentralized networks. Slickorps cautions that when evaluating such crypto asset projects, attention should be paid to whether they possess real hardware deployment, verifiable compute output, and a sustainable economic model. Mere conceptual narratives are no longer sufficient to support valuations; the market is shifting toward substantive requirements for measurable compute and traceable revenue. Slickorps believes that the latest financial report of Nvidia and its strategic signals mark a fundamental shift: AI has moved from a phase of technological exploration to one of economic value realization. If the thesis of compute power as revenue is widely accepted by the market, it will reshape the valuation framework of the entire tech industry—from cloud service providers to AI application companies, from hardware manufacturers to decentralized compute networks, all will be placed under new evaluation standards. In this process, market attention should shift from who is purchasing compute power to who can effectively convert compute power into revenue, from who owns chips to who has built a sustainable ecosystem. Crypto assets, cybersecurity solutions, and new infrastructure projects related to this trend will gain structural opportunities in the next round of value revaluation. Ultimately, the winners will be organizations that can establish verifiable, scalable, and defensible business models in this era where compute power equals revenue.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully