Alex Rome : https://alexromesound.com/pages/coaching-program

EDM Tips Accelerator: https://edmtips.com/accelerator/sp3/

Van Murten: https://vanmurten.com/#training

Ethan Davies : https://completeproducerpro.com/which-course-is-right-for-you

tl;dr only apps with real users will gain subsidized pricing. Pricing changes will arrive on August 24th

HOW TO APPLY

1. Download the curated Sample Pack by SKALA and Kid Simius.
2. Create your own original track using the provided samples and let your creativity run free.
3. Record a short video introducing yourself, explaining the story behind your track, and telling us why you want to become part of the El Tony Producer Academy.
4. Submit your track and video via the application form by August 23, 2026.
5. By submitting your application, you agree to our Terms & Conditions for the challenge and also the academy. Please read them carefully.
6. A jury will select eight participants based on the evaluation criteria. The selected producers will be announced by September 6, 2026.

Get your music heard in the TRIP AND BASS Records Demo Drop on TikTok! 

Selected artists will receive live feedback to improve their sound and develop their production skills.

The winner will have the opportunity to release their track on TRIP AND BASS Records and will also receive an official TRIP AND BASS Records merchandise T-shirt.

I have a system collecting data off Coingecko daily that has been going for 2 years. There are 1.4 million records. I loaded the DB into the new chatgpt plus work app and this is what it had to say about Pi after doing a general analysis of the contents of the DB

Pi Network Market Report

Data period: 4 March 2025 to 22 July 2026
Latest reliable database snapshot: 22 July 2026

Executive summary

Pi has not decayed by disappearing from the market. It has remained continuously tracked and inside the top 100. Instead, it has experienced severe and sustained value decay.

Since its first observation in the database:

• Price fell from $1.73 to $0.0919: -94.7%
• Market cap fell from $12.05 billion to $1.01 billion: -91.7%
• Market-cap rank declined from 12th to 65th
• Daily volume fell from $830.6 million to $13.8 million: -98.3%
• Implied circulating supply increased by approximately 57%

Pi is therefore a surviving but heavily depreciated listing. Supply growth softened the market-cap decline relative to the price decline, but it also added continuing sell-side pressure.

---

Current position

Metric	22 July 2026
Price	$0.091871
Market cap	$1.005 billion
Market-cap rank	65
Daily volume	$13.80 million
30-day average price	$0.10483
90-day average price	$0.13696
365-day average price	$0.21569

The price is:

• 12.4% below its 30-day average
• 32.9% below its 90-day average
• 57.4% below its 365-day average

This indicates that the longer-term trend remained decisively downward despite a short recovery from the July low.

---

Performance by period

Period	Price return	Rank movement
7 days	+12.5%	71 to 65
30 days	-32.1%	54 to 65
90 days	-45.2%	49 to 65
180 days	-50.0%	71 to 65
365 days	-80.9%	42 to 65
Since first observation	-94.7%	12 to 65

The seven-day recovery does not yet represent a trend reversal. It followed a new all-time low and remains small compared with the one-, three- and twelve-month declines.

---

Decay following initial appearance

Age	Price	Return from first observation	Rank
Initial	$1.730	--	12
7 days	$1.380	-20.2%	13
14 days	$1.130	-34.7%	21
30 days	$0.6078	-64.9%	31
60 days	$0.5820	-66.4%	33
90 days	$0.6382	-63.1%	34
180 days	$0.3842	-77.8%	47
365 days	$0.1738	-90.0%	50
505 days	$0.0919	-94.7%	65

The most violent repricing occurred in the first month. Pi lost almost two-thirds of its value and fell 19 ranking positions.

There was then a temporary period of relative stability around $0.58 to $0.64, but the longer-term decline resumed.

---

All-time high and all-time low

The database records:

• ATH: $2.99 on 26 February 2025
• ATL: $0.070586 on 14 July 2026

At $0.091871, Pi was:

• 96.9% below its ATH
• 30.2% above its ATL

The database's daily Pi history begins on 4 March, after the ATH. Its highest daily observation in the ranking table is therefore only $1.97, recorded on 5 March.

From that recorded daily peak, the maximum drawdown reached 96.35% on 14 July 2026.

The difference between the current price and the ATL looks large in percentage terms because the base is extremely low. It does not substantially repair the longer-term loss.

---

Market cap and supply

Pi's estimated circulating supply, calculated from market cap divided by price, changed from approximately:

• 6.96 billion Pi on 4 March 2025
• 10.94 billion Pi on 22 July 2026

That is an increase of approximately 3.98 billion Pi, or 57.1%.

This helps explain why:

• Price declined by 94.7%
• Market cap declined by a slightly smaller 91.7%

Without the supply expansion, the same market cap would imply a higher price. Conversely, continuing increases in circulating supply mean demand must keep growing simply to prevent price dilution.

This calculation reflects CoinGecko's reported circulating supply and could also incorporate corrections to its supply estimate.

---

Trading activity

Measure	Volume
First database observation	$830.6 million
Highest recorded	$1.864 billion
Highest-volume date	12 May 2025
365-day average	$32.90 million
90-day average	$15.26 million
30-day average	$14.29 million
Current	$13.80 million

Volume has collapsed by 98.3% from the first database observation.

Turnover relative to market cap fell from approximately:

• 6.9% at the first observation
• 1.37% currently

The market has therefore lost both valuation and trading intensity. Recent volume is also slightly below its 30-day average, so the bounce from the ATL was not accompanied by an exceptional sustained increase in participation.

---

Comparison with Bitcoin

Over Pi's database history:

• Pi: -94.7%
• Bitcoin: -21.3%

Measured against Bitcoin rather than dollars, Pi lost approximately 93.2% of its relative value.

Pi's decline therefore cannot primarily be explained by general cryptocurrency weakness. Most of the underperformance was specific to Pi's valuation, supply and market demand.

---

Comparison with other early-2025 listings

Among 654 coins first appearing during the first quarter of 2025:

• Only 20.2% remained in the database after one year
• Pi did survive
• Among the 132 one-year survivors, the median return was -51.8%
• Pi's one-year return was -90.0%
• Approximately 84% of surviving coins performed better than Pi
• Only 20 of the 132 survivors performed worse

Pi therefore did well on survival and continuing market relevance, but poorly on preserving value.

Its initially high rank makes the comparison more demanding: it began as a $12 billion, rank-12 asset rather than as an obscure lower-ranked listing.

---

Interpretation

Pi's market history can be divided into four phases:

1. Initial speculative valuation

   Pi entered the database at an unusually high $12 billion market cap, following an ATH of $2.99.

2. Rapid price discovery

   The price lost 65% within 30 days as initial holders, exchange traders and circulating supply confronted real market demand.

3. Temporary stabilisation

   Price held broadly around $0.50 to $0.65 during parts of spring and early summer 2025.

4. Prolonged dilution and demand decline

   Supply continued increasing while volume and valuation contracted. Pi eventually fell below $0.10 and reached a new ATL in July 2026.

---

Overall assessment

Pi remains a significant and sufficiently liquid cryptocurrency rather than a failed or vanished listing. A billion-dollar market cap and top-100 position are meaningful.

However, its market data remains strongly bearish:

• Persistent lower prices
• A 96.9% drawdown from ATH
• Severe relative underperformance against Bitcoin
• Falling market-cap rank
• Collapsing trading volume
• Approximately 57% implied supply expansion
• No convincing medium-term reversal yet

The recent rise from $0.0706 to $0.0919 is best described as an ATL rebound inside a continuing downtrend.

A stronger change in direction would require sustained price recovery alongside rising volume, stabilising circulating-supply growth and an improvement in rank -- not merely a short bounce from an exceptionally depressed price.

---

This report analyses the supplied historical database. It is not financial advice.

Qualified immunity is a legal doctrine in United States law that shields government officials, including police officers, from being held personally liable for civil lawsuits unless their conduct violates "clearly established statutory or constitutional rights."

To overcome qualified immunity, plaintiffs are typically required to point to a prior court case with almost identical circumstances where an officer's specific conduct was already ruled unconstitutional.

https://preview.redd.it/cmdiw2el19ah1.png?width=821&format=png&auto=webp&s=c53a095991502bc17115d998a18d9a84f1d01245

services:
  hermes-agent:
    image: nousresearch/hermes-agent:latest
    container_name: hermes-agent
    command:
      - /bin/bash
      - -lc
      - |
        /opt/hermes/.venv/bin/python - <<'PY'
        import os
        from pathlib import Path

        import yaml

        home = Path(os.environ.get("HERMES_HOME", "/home/hermes/.hermes"))
        config_path = home / "config.yaml"
        provider = os.environ.get("HERMES_MODEL_PROVIDER", "dmr").strip().lower()
        dmr_endpoint = os.environ.get(
            "HERMES_DMR_URL",
            "http://modelrunner.docker.internal:12434/engines/v1",
        ).rstrip("/")
        dmr_model = os.environ.get("HERMES_DMR_MODEL", "ai/smollm2")
        dmr_api_key = os.environ.get("HERMES_DMR_API_KEY", "docker-model-runner")
        model = os.environ.get("HERMES_MODEL") or dmr_model
        base_url = (os.environ.get("HERMES_BASE_URL") or "").rstrip("/")
        api_key = os.environ.get("HERMES_API_KEY") or ""
        config_path.parent.mkdir(parents=True, exist_ok=True)
        try:
            config = yaml.safe_load(config_path.read_text(encoding="utf-8")) or {}
        except FileNotFoundError:
            config = {}

        model_config = config.get("model")
        if not isinstance(model_config, dict):
            model_config = {}

        if provider == "dmr":
            model_config.update({
                "provider": "custom",
                "default": model or dmr_model,
                # Docker Compose's `models:` integration injects the reachable
                # in-container endpoint into HERMES_DMR_URL. Do not let the
                # generic HERMES_BASE_URL override it for DMR.
                "base_url": dmr_endpoint,
                "context_length": 65536,
                # Docker Model Runner exposes an OpenAI-compatible API and ignores
                # the bearer token, but Hermes uses presence of a key as configured.
                "api_key": api_key or dmr_api_key,
            })
            existing_custom_providers = config.get("custom_providers", [])
            if not isinstance(existing_custom_providers, list):
                existing_custom_providers = []
            custom_providers = [
                custom_provider for custom_provider in existing_custom_providers
                if not (
                    isinstance(custom_provider, dict)
                    and custom_provider.get("name") == "docker-model-runner"
                )
            ]
            custom_providers.append({
                "name": "docker-model-runner",
                "base_url": model_config["base_url"],
                "api_key": model_config["api_key"],
                "models": {
                    model_config["default"]: {
                        "context_length": 65536,
                    },
                },
            })
            config["custom_providers"] = custom_providers
        elif provider == "anthropic":
            model_config = {
                "provider": "anthropic",
                "default": model,
            }
            if api_key:
                model_config["api_key"] = api_key
        elif provider == "openai":
            model_config = {
                "provider": "openai",
                "default": model,
                "base_url": base_url or "https://api.openai.com/v1",
            }
            if api_key:
                model_config["api_key"] = api_key
        else:
            model_config = {
                "provider": "custom",
                "default": model,
                "base_url": base_url,
            }
            if api_key:
                model_config["api_key"] = api_key

        config["model"] = model_config
        config["platform_toolsets"] = {
            # hermes-cli includes terminal, file, web, skills, todo, and cronjob.
            # Keep the common platform names mapped so WebUI/CLI/gateway sessions
            # all receive the scheduler tool instead of falling back to a narrow
            # or malformed default.
            "cli": ["hermes-cli"],
            "webui": ["hermes-cli"],
            "gateway": ["hermes-cli"],
        }
        config_path.write_text(
            yaml.safe_dump(config, sort_keys=False, allow_unicode=True),
            encoding="utf-8",
        )
        print(f"Configured Hermes from .env: provider={provider}, model={model}")
        PY
        exec /opt/hermes/.venv/bin/hermes gateway run
    models:
      hermes-llm:
        endpoint_var: HERMES_DMR_URL
        model_var: HERMES_DMR_MODEL
    ports:
      - "127.0.0.1:18642:8642"
    volumes:
      - ${HERMES_HOME:-./local/container-data/hermes-home}:/home/hermes/.hermes
      - hermes-agent-src:/opt/hermes
    environment:
      - HERMES_HOME=/home/hermes/.hermes
      - HERMES_UID=${UID:-501}
      - HERMES_GID=${GID:-20}
      - HERMES_MODEL_PROVIDER=${HERMES_MODEL_PROVIDER:-dmr}
      - HERMES_MODEL=${HERMES_MODEL:-}
      - HERMES_BASE_URL=${HERMES_BASE_URL:-}
      - HERMES_API_KEY=${HERMES_API_KEY:-}
      - HERMES_DMR_URL=${HERMES_DMR_URL:-http://modelrunner.docker.internal:12434/engines/v1}
      - HERMES_DMR_MODEL=${HERMES_DMR_MODEL:-ai/smollm2}
      - HERMES_DMR_API_KEY=${HERMES_DMR_API_KEY:-docker-model-runner}
    restart: unless-stopped
    networks:
      - hermes-net

  hermes-webui:
    image: ghcr.io/nesquena/hermes-webui:latest
    container_name: hermes-webui
    entrypoint:
      - /bin/bash
      - -lc
      - |
        for _ in {1..120}; do
          [ -d /home/hermeswebui/.hermes/hermes-agent/.playwright ] && break
          sleep 1
        done
        chmod -R o+rX /home/hermeswebui/.hermes/hermes-agent 2>/dev/null || true
        exec /hermeswebui_init.bash
    depends_on:
      - hermes-agent
    labels:
      - pi.ui.primary=true
    models:
      hermes-llm:
        endpoint_var: HERMES_DMR_URL
        model_var: HERMES_DMR_MODEL
    ports:
      - "127.0.0.1:18787:8787"
    volumes:
      - ${HERMES_HOME:-./local/container-data/hermes-home}:/home/hermeswebui/.hermes
      - hermes-agent-src:/home/hermeswebui/.hermes/hermes-agent
      - ${HERMES_WORKSPACE:-./local/container-data/workspace}:/workspace
    environment:
      - HERMES_WEBUI_HOST=0.0.0.0
      - HERMES_WEBUI_PORT=8787
      - HERMES_WEBUI_STATE_DIR=/home/hermeswebui/.hermes/webui
      - WANTED_UID=${UID:-501}
      - WANTED_GID=${GID:-20}
      - HERMES_WEBUI_PASSWORD=${HERMES_WEBUI_PASSWORD:-}
    restart: unless-stopped
    networks:
      - hermes-net

networks:
  hermes-net:
    driver: bridge

volumes:
  hermes-agent-src:

models:
  hermes-llm:
    model: ${HERMES_DMR_MODEL:-ai/smollm2}
    context_size: 65536

Config_options.yml

title: Hermes Local Configurator
eyebrow: Developer Preflight
description: >
  Configure the local Docker Compose environment. This writes only .env;
  docker-compose.yml turns those values into Hermes runtime config on container start.
output_file: .env
after_save: Saved. Run docker compose up -d --force-recreate when ready.
footer_hint: Then run docker compose up -d --force-recreate.

fixed_values:
  - name: UID
    detect: uid
    env_comment: >
      Current host user ID. The configurator detects this automatically so
      container-written bind-mount files remain owned by your local user.

  - name: GID
    detect: gid
    env_comment: >
      Current host group ID. The configurator detects this automatically and
      passes it to the containers together with UID for bind-mount permissions.

  - name: HERMES_HOME
    value: ./local/container-data/hermes-home
    env_comment: >
      Host path mounted as Hermes home. It stores generated config.yaml,
      sessions, skills, logs, auth files, and persistent agent state.

  - name: HERMES_WORKSPACE
    value: ./local/container-data/workspace
    env_comment: >
      Host path mounted at /workspace in the WebUI container for browsing and
      editing files from the UI.

  - name: HERMES_DMR_API_KEY
    value: docker-model-runner
    env_comment: >
      Dummy bearer token for Docker Model Runner's OpenAI-compatible API.
      Docker Model Runner ignores it, but Hermes expects a configured key.

fields:
  - name: HERMES_MODEL_PROVIDER
    type: hidden
    default: dmr
    env_comment: >
      Selects Docker Model Runner as the local model backend.

  - name: HERMES_DMR_MODEL
    label: Select Local AI model
    type: select
    default: ai/gemma3:1B-Q4_K_M
    required: true
    help: >
      Choose the default local model, Gemma 3. SmolLM2 is the lightest option
      but too naive. Gemma 3 is a stronger small default. Gemma 4 (4B) is
      intended for more capable machines with 8GB of memory and may require a
      large initial download (9GB). Choose Gemma 4 (26B) if you have at least
      24GB of memory.
    env_comment: >
      Model name passed to Docker Model Runner for the local Hermes agent.
      Choose a lightweight model for broad compatibility, or a larger Gemma
      model for better quality on more capable machines.
    options:
      - value: ai/smollm2
        label: SmolLM2 (0.4B) - tiny AI model that works on every laptop. Too naive. (256MB download)
      - value: ai/gemma3:1B-Q4_K_M
        label: Gemma 3 (1B) - small AI model. Default for compatibility (800MB download)
      - value: ai/gemma4:4B-Q4_K_XL
        label: Gemma 4 (4B) - pretty smart AI model. Needs 8GB of memory (7GB download)
      - value: hf.co/google/gemma-4-26B-A4B-it-qat-q4_0-gguf:Q4_0
        label: Gemma 4 (26B) - highest AI quality. Needs 24GB of memory (16GB download)

  - name: HERMES_BASE_URL
    type: hidden
    default: ""
    env_comment: >
      OpenAI-compatible API base URL for OpenAI or custom providers. Blank for
      Docker Model Runner because Compose injects HERMES_DMR_URL.

  - name: HERMES_API_KEY
    label: API key
    type: password
    preserve_if_blank: true
    invalid_preserve_values:
      - docker-model-runner
    help: Leave blank to keep an existing value in .env.
    visible_if:
      field: HERMES_MODEL_PROVIDER
      in:
        - anthropic
        - openai
        - custom
    env_comment: >
      API key for the selected remote provider. Leave blank for Docker Model
      Runner; its dummy token is stored separately in HERMES_DMR_API_KEY.

  - name: HERMES_WEBUI_PASSWORD
    type: hidden
    default: ""
    env_comment: >
      Optional password for the WebUI. Blank by default. Set this before exposing
      the WebUI beyond localhost.

  - name: HERMES_MODEL
    type: hidden
    default: ""

  - name: HERMES_DMR_URL
    type: hidden
    default: ""
    env_comment: >
      Docker Model Runner endpoint override. Usually blank: Docker Compose
      injects the working in-container endpoint automatically.

Effective Date: June 26, 2026

Provider: Pi Community Company (“Company,” “we,” “us”).

Product: SoloHost (“SoloHost” or “Platform”).

1. Definitions

1.1 “SoloHost” means the software platform, registry, orchestration layer, client software, APIs, and related services operated by the Company.

1.2 “Apps” means third-party or Company-distributed software packages, containers, scripts, or services made available through SoloHost.

1.3 “Developer” means any third party that submits or publishes Apps.

1.4 “User” or “Operator” means any individual or entity using SoloHost.

1.5 “User Environment” means all hardware, operating systems, networks, storage, and compute resources controlled by the User.

1.6 “Content” means all code, data, configurations, and materials processed through Apps.

1.7 “Trust Signals” means informational indicators displayed in the Platform, including publisher know-your-customer (KYC) status and aggregated user review counts and scores.

1.8 “Permissions” means access requests by an App, including to files, folders, devices, credentials, networks, services, or interfaces, whether local or remote.

2. Availability; Nature of the Platform

2.1 Availability. SoloHost is available globally to any User who can download Pi Desktop and access the website.

2.2 Self-Hosted Architecture. SoloHost is a software-only platform designed for self-hosted deployment environments. SoloHost is not a cloud hosting provider for end-user workloads and does not operate infrastructure on behalf of Users. All execution of Apps occurs exclusively within the User Environment, or is initiated by the User or as designed by the App Developer, of which the User purports to be the sole operator and controller.

3. No Hardware, Infrastructure, or Managed Hosting

3.1 The Company does not sell, lease, or distribute hardware devices or provide preconfigured physical appliances.

3.2 The Company does not host User applications or data in Company-controlled environments, offer managed compute, storage, or networking, or act as a data processor for User-run Apps.

3.3 Any “turnkey,” “one-click,” or “appliance-like” descriptors refer solely to software configuration experience, not to physical infrastructure or managed services.

4. Eligibility and Authority

4.1 You represent and warrant that you are legally capable of entering into binding agreements, you have authority to bind any entity you represent, and your use complies with applicable laws and regulations.

4.2 We may restrict access at our discretion.

5. Account Security; Credentials; Remote Access

5.1 You are solely responsible for credential security (including keys, tokens, and passwords), device integrity, network exposure and firewall configuration, and access permissions to Apps and services.

5.2 Remote Access. Pi requires Users to log in via a Pi account before accessing the SoloHost App UI for remote access. Users remain solely responsible for the selection, configuration, and ongoing security of all remote access, including safeguarding credentials, tokens, and passwords, and for any consequences of enabling remote connectivity.

5.3 Liability Disclaimer. The Company disclaims liability for compromises, exploits, or vulnerabilities in Apps or the User Environment that may be exposed or exacerbated by remote access features.

6. SoloHost License to Users

6.1 Subject to these Terms, the Company grants Users a non-exclusive, non-transferable, revocable, limited license to install and use SoloHost solely for managing Apps in a User Environment.

6.2 Users may not reverse engineer SoloHost except where legally permitted, circumvent access controls or security systems, resell or sublicense SoloHost without authorization, or use SoloHost to operate a competing registry or platform.

7. Application Ecosystem; Publishers; No Reviews or Vetting

7.1 Third-Party Apps and Publishers. Apps are provided by independent Developers, and the Company does not endorse Apps, guarantee functionality, safety, legality, or performance, or assume responsibility for App outputs or Content.

7.2 No Pre-Publication Reviews. There are no pre-publication checks, security reviews, code reviews, malware reviews, penetration tests, privacy reviews, or legal/regulatory reviews of Apps or publishers by the Company. Publication in SoloHost does not imply approval, endorsement, certification, safety, trustworthiness, or compliance.

7.3 Open Publication. Anyone can publish an App; publishers are independent third parties and do not represent the Company, although the Company may release certain Apps of its own.

7.4 Publisher Persistence. Publishers are not required to maintain contact information, may abandon Apps, and no specific actions occur if a publisher disappears or abandons an App.

7.5 Trust Signals. The Platform may display Trust Signals, including publisher KYC status and aggregated user review counts and scores. Trust Signals are informational only and do not constitute any warranty, endorsement, or assurance.

7.6 User Risk. Users install and operate Apps entirely at their own risk and are solely responsible for all installation and use decisions.

8. Permissions; Operator Consent and Responsibility

8.1 Publisher Permissions. Publishers can request any access permissions. Requested permissions will be disclosed to Operators within the Platform.

8.2 Consent Model. By choosing to install and run an App, the Operator is deemed to have consented to the permissions the App requires. Operators must review requested permissions prior to installation and accept full responsibility for granting them.

8.3 Operator Risk Acknowledgement. Operators assume all risks associated with granting elevated permissions, including potential exposure of files, devices, networks, credentials, and services, and any resulting impacts on security, integrity, availability, confidentiality, or privacy.

9. Local Execution; Resource, Data, and Network Risks

9.1 Capabilities. Apps may consume excessive CPU, memory, or storage; modify or delete files; access local network resources; and expose network services.

9.2 Risk Warnings. Use of Apps may lead to resource exhaustion, file corruption, data loss, network compromise, or unauthorized access. Operators are solely responsible for mitigating such risks.

9.3 Backups, Encryption, Security. SoloHost does not provide backup capability. Operators are solely responsible for backups, encryption, and overall security and maintenance of their systems and Apps.

9.4 Deletion Disclaimer. The Company disclaims liability for any deletion, corruption, or loss of files or data arising from use of the Platform or any Apps.

10. Data Access; Privacy; Telemetry

10.1 App-Level Access. If an App runs on Pi Desktop, SoloHost can potentially access operator application data, configuration files, application databases, and application traffic. Operators generally decide which folders or resources an App can access and grant such access at their sole discretion and risk. However, notwithstanding the foregoing, the Company cannot determine what access may be provided through the design of a Developer’s App. By using a Developer’s App, the Operator is solely responsible for determining what access may be provided, and proceeds at their own risk.

10.2 Company Access to Content. The Company does not claim ownership of User Content and does not access private App data except as technically required for support features explicitly enabled by the User.

10.3 Metadata and Diagnostics. Users grant the Company a limited license to process metadata and diagnostic signals necessary to operate the Platform.

10.4 Telemetry. SoloHost may collect installation/uninstallation events, compatibility signals, error logs/crash reports, and aggregated usage statistics; such data is used to improve stability and security, is not sold as personal data, and is not used to access App Content.

11. Developer Submissions; License to Company

11.1 Developer License Grant. By submitting or publishing an App, the Developer grants the Company a worldwide, perpetual, irrevocable (except as required by law), non-exclusive, royalty-free, sublicensable license to host, store, reproduce, package, containerize, and distribute the App; modify packaging solely for compatibility; display metadata, documentation, and related materials; scan for security vulnerabilities, malware, or policy violations; index and surface the App; and enable download, installation, and updates by Users.

11.2 Caching and Analysis. The Company may cache and retain copies for resilience and distribution efficiency and perform automated analysis for security and compliance purposes.

11.3 Ownership; Open Source Wrappers. Developers retain ownership of their intellectual property. Developers acknowledge that many submissions are wrappers around open-source software and agree to include an appropriate open-source license for the wrapper materials [e.g., MIT License], with all required notices. Developers are responsible for complying with and passing through all applicable open-source obligations.

12. User Licenses to Apps; Open Source Obligations

12.1 Apps are licensed directly by Developers to Users. Open-source Apps are governed by their applicable licenses; proprietary Apps are governed by Developer-specific terms; SoloHost does not grant any license to Apps themselves.

12.2 Where Apps include open-source components, Users must comply with upstream licenses and associated attribution and notice requirements. The Company provides no warranties for open-source software.

13. Security Model; No Vetting; Operator Responsibilities

13.1 No Guarantee of Safety. Self-hosted environments are exposed to misconfiguration risk, Apps may expose services to public networks, and third-party code may contain vulnerabilities; while the Company may provide optional scanning tools or flags for known malicious Apps, it does not guarantee detection of all vulnerabilities or threats.

13.2 No Security Standards. There are no Company-performed pre-publication or ongoing security, privacy, legal, or quality reviews of Apps or publishers; any displayed Trust Signals, including KYC status and user review metrics, are informational only.

13.3 Operator Duties. Users remain fully responsible for hardening systems, applying patches, isolating workloads, securing network access, and reviewing permissions before installation.

14. Prohibited Conduct; Content Policy

14.1 Platform Abuse. Users and Developers may not use SoloHost to violate law, distribute malware, operate botnets, facilitate unauthorized surveillance, infringe IP, evade export/sanctions, provide illegal content hosting, or interfere with platform integrity or security scanning systems.

14.2 App Categories. The Platform does not impose categorical prohibitions on specific App types beyond these Terms; the Platform is intended to help people run local servers and open-source software. Notwithstanding the absence of categorical prohibitions, Users remain responsible for legal compliance, and the Company may exercise takedown rights under Section 15.

15. Platform Modification; Listing Criteria; Takedowns

15.1 Modification Rights. The Company may modify or discontinue SoloHost or any feature, change App listing criteria or availability, remove Apps at any time (including for security reasons), and update APIs, SDKs, or compatibility layers without guaranteeing backward compatibility.

15.2 Discretionary Takedowns. The Company may, in its sole discretion, decline to list, de-list, restrict, or remove any App at any time, for any or no reason, including suspected spam, malware, policy concerns, or legal requests. The Company makes no commitment to take action with respect to any App, even if users report issues, vulnerabilities, or viruses.

16. Fees

16.1 Current Fees. There are no fees currently charged for the SoloHost software.

16.2 Future Network Services. The Company may in the future offer optional network services (for example, a VPN to connect a computer to a user’s phone) that utilize Company servers and may charge usage-based or service fees for such optional services, as disclosed at the time of offering.

17. Disclaimers

17.1 Platform and App Disclaimers. SoloHost is provided “AS IS” and “AS AVAILABLE,” and the Company disclaims all implied warranties of merchantability, fitness for a particular purpose, non-infringement, availability, uptime, and error-free operation. The Company does not warrant App behavior or outputs, the security of User Environments, or cross-system compatibility. The Company does not guarantee the safety, legality, security, or functionality of any App.

17.2 No Endorsement. Publication, listing, ranking, or display of Trust Signals does not constitute endorsement, certification, or approval.

17.3 Data Loss; Deletion. The Company is not responsible for deletion, corruption, inaccessibility, or loss of any data or files resulting from the Platform or any App.

18. Limitation of Liability

18.1 To the maximum extent permitted by law, the Company shall not be liable for indirect, incidental, special, consequential, or punitive damages, including loss of data, revenue, goodwill, or business interruption, and disclaims liability arising from Apps.

18.2 The total aggregate liability of the Company shall not exceed the fees paid to the Company in the 12 months preceding the claim (if any); if no fees were paid, liability is limited to USD $0 to the extent permitted by law.

19. Indemnification

19.1 You agree to defend, indemnify, and hold harmless the Company from claims arising from your use of SoloHost; your installed Apps and their outputs; your violation of law or third-party rights; security incidents originating from your environment; your distribution of malware; your intentional acts that damage, delete or compromise user’s assets or data; and any misuse of the Platform.

20. Suspension; Termination

20.1 We may suspend or terminate access if you violate these Terms, your use poses a security or legal risk, we determine to suspend or terminate in our discretion with or without cause, or as required by law or regulatory authority.

20.2 Upon termination, all licenses granted to you cease immediately and you must uninstall SoloHost; provisions concerning IP, liability, and indemnity survive.

21. Intellectual Property

21.1 All rights in SoloHost software, branding, UI/UX design, documentation, and registry infrastructure remain the exclusive property of the Company, and no rights are granted except as expressly stated.

22. Governing Law; Jurisdiction

22.1 These Terms are governed by the laws of the Cayman Islands, without regard to conflict of laws principles, and disputes shall be subject to the exclusive jurisdiction of Cayman Islands courts, unless otherwise required by mandatory local law.

23. Force Majeure

23.1 The Company shall not be liable for failure or delay caused by internet outages, hosting or infrastructure failures, cyberattacks, government actions, natural disasters, or other events beyond reasonable control.

24. Severability

24.1 If any provision is held invalid or unenforceable, the remainder shall remain in full force and effect.

25. Entire Agreement

25.1 These Terms constitute the entire agreement between Users and the Company regarding SoloHost and supersede all prior agreements.

26. Contact

26.1 Pi Community Company, SoloHost Support. Contact: support+solohost@minepi.com

according to docs uploaded by https://www.reddit.com/r/RecklessBen/comments/1u9p7n7/confirmed_ben_is_represented/

Jon D. Williams https://jondwilliamslaw.com/

Jeremy Delicino : https://jeremydelicino.com/

Both are Salt Lake City Attorneys

Jeremy filed an EXTENSIVE request for discovery on the 18th
https://drive.proton.me/urls/9B09WJ4H2W#9zWjRWwFnyqR

"24. Identify all clothing, including undergarments, of the defendant," 🤭

https://preview.redd.it/qrv9lluiun5h1.png?width=1672&format=png&auto=webp&s=ec3103e02fbeaef24b516051f4429ff384430d9e

https://preview.redd.it/h6dh9nb6ln5h1.png?width=883&format=png&auto=webp&s=bf4de9e6067b93d81f5b14879e79e6ea2dec29ef

https://preview.redd.it/iqibqp08qn5h1.png?width=800&format=png&auto=webp&s=bd0b903524d45d8085be179a585d753834dbbb28

In cryptocurrency, there is normally this relationship between work and value : mining crypto gets easier as the value drops because operators turn off unprofitable machines.

https://preview.redd.it/fet2zk4cbn5h1.png?width=5970&format=png&auto=webp&s=165d2bbe849675e2c6ece28d30afb5fcac0b33d8

Mining Pi stays the same or gets harder as the value drops because ?