Compare commits
227 Commits
developmen
...
developmen
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
aea474b92c | ||
|
|
0e8328a5d7 | ||
|
|
4787a8e8da | ||
|
|
7e40c2b2a0 | ||
|
|
957b08fed1 | ||
| ea6badf4d1 | |||
|
|
7a8e4a0103 | ||
|
|
eda568e4d4 | ||
|
|
a87bc38d1a | ||
|
|
690caa7b6e | ||
|
|
ea58fb9e3a | ||
|
|
f6d24487d9 | ||
|
|
d27ddc4137 | ||
|
|
310a89e307 | ||
|
|
e0e324bf78 | ||
|
|
094951e212 | ||
|
|
a882f57acc | ||
|
|
42e7079593 | ||
|
|
6b8c018f7e | ||
|
|
43b7e9ea24 | ||
|
|
0115ef5f66 | ||
|
|
43353e0889 | ||
|
|
cae3e1a5b6 | ||
|
|
1f59857902 | ||
|
|
0ecf174994 | ||
|
|
14de34756f | ||
|
|
177cecc9a3 | ||
|
|
ac971e9519 | ||
|
|
276fce6dbc | ||
|
|
dfbae164b6 | ||
|
|
559caf36db | ||
|
|
baab9e84c6 | ||
|
|
65e560e50d | ||
|
|
20a1c49b75 | ||
|
|
628a39f976 | ||
|
|
9cb2666000 | ||
|
|
e7624f653b | ||
|
|
bf145f87ac | ||
|
|
939688ac71 | ||
|
|
6278dcd3d3 | ||
|
|
4a1323dede | ||
|
|
74d3462a1a | ||
|
|
609b2fb5f4 | ||
|
|
31b98a422b | ||
|
|
ca5531f9d5 | ||
|
|
bacbf87373 | ||
|
|
49bb187530 | ||
|
|
5ea53d54d9 | ||
|
|
c216b6fa5b | ||
|
|
1a94d7c7cb | ||
|
|
d027fb0ae2 | ||
|
|
4834a8b56a | ||
|
|
18c5a662d1 | ||
|
|
775c492196 | ||
|
|
64d2bf6f0e | ||
|
|
2eb1e99ecc | ||
|
|
90f5d98470 | ||
| ba50135255 | |||
| 107f668dd7 | |||
| 7ed5202d9f | |||
|
|
34af78078d | ||
|
|
dae71b1b67 | ||
|
|
6481b72ae2 | ||
|
|
e35dceb806 | ||
|
|
648fb47db0 | ||
|
|
4b77abef9b | ||
|
|
468fa97908 | ||
|
|
5f82ca334d | ||
|
|
837e6aa79d | ||
|
|
8a8c0e5c74 | ||
| eb23c9d408 | |||
| 25e6ad8e18 | |||
| 60b9782628 | |||
|
|
8360d06f7b | ||
|
|
6ffc8bd7ef | ||
|
|
f761dd6298 | ||
|
|
9bba2b3e1f | ||
|
|
dd0491d857 | ||
|
|
22c33d3f3a | ||
|
|
3fa030adb4 | ||
| f19c4a92d2 | |||
| 11f566b3a0 | |||
| e7f3b05c95 | |||
| f45bcba012 | |||
| 1b4eb23693 | |||
| f1a8069ab3 | |||
| f177207e28 | |||
|
|
581a93bdf6 | ||
|
|
6bee4e651b | ||
|
|
ea9385af6d | ||
| 065ac9c32b | |||
| 425eff8bf0 | |||
| 2c2e0e20a1 | |||
|
|
1c97bdb039 | ||
|
|
c3b6d46cae | ||
|
|
1992515530 | ||
|
|
ce54b4e1bc | ||
|
|
d2bab594a1 | ||
|
|
2d1423a844 | ||
|
|
ac8cedf6ab | ||
|
|
e2639e82e1 | ||
|
|
e32a0b94a4 | ||
|
|
4d1f0be1b6 | ||
|
|
1f2e19dbcb | ||
|
|
9579e429ff | ||
|
|
1185e0b4fe | ||
|
|
a68c36ae69 | ||
|
|
37877a4a9e | ||
|
|
cc11d91432 | ||
|
|
ee420574ad | ||
|
|
9c3e42b1af | ||
|
|
f0a9821180 | ||
|
|
86f6ce120b | ||
| 8df54cc170 | |||
|
|
55632d51a6 | ||
|
|
5f910abee7 | ||
|
|
9776f01cd9 | ||
|
|
6f183b36d0 | ||
|
|
2768083d6f | ||
|
|
3fa8d552cf | ||
|
|
ce16e9006a | ||
|
|
1201f720b5 | ||
|
|
1cab9c4955 | ||
|
|
466d71144e | ||
| 41ae797834 | |||
| 5ac0c39956 | |||
| 51c928c8d8 | |||
| 94353c399d | |||
| a6bd8aa0ca | |||
| 1aececfa66 | |||
|
|
69f4c2812e | ||
| db15d58c29 | |||
|
|
10c453a019 | ||
|
|
f6adc6b29a | ||
|
|
9d716c1409 | ||
| 32fbafd28c | |||
| 7455db7e34 | |||
| c728c33a94 | |||
|
|
79e8e2323c | ||
|
|
48ecdad653 | ||
|
|
bd37a35897 | ||
|
|
f507903233 | ||
|
|
6c897ab674 | ||
| c8989a0199 | |||
| 1eee3fdf1d | |||
|
|
c767799d90 | ||
|
|
5f4c856bbc | ||
|
|
81aa9d7c09 | ||
|
|
3a28580eb4 | ||
|
|
740f0118f1 | ||
|
|
ccfa27a4a7 | ||
|
|
80a1936e04 | ||
| 283f071672 | |||
| d48bd43795 | |||
|
|
112bdbdffc | ||
| c237789bc0 | |||
| 62c4c370f8 | |||
| e89cb51588 | |||
| 6ca7bbd86b | |||
| 3d50fd870d | |||
| b275d5ede5 | |||
| 490a3be5a4 | |||
| 9ef75e8ca0 | |||
| c4b50cb435 | |||
| f88f31840a | |||
| 28cd9cef40 | |||
| 7339145a69 | |||
| e9785f8930 | |||
| dd4edd1709 | |||
| dc5c4e3940 | |||
| 78ea33cf12 | |||
| 1dd3753571 | |||
| 3b100539aa | |||
| 0d4b209a25 | |||
| 6a72d0e9f8 | |||
| 453723d8f2 | |||
| b1f8e28632 | |||
| a48fd797e1 | |||
| a383b3dbb1 | |||
| bdc03f191e | |||
| a37e3569a0 | |||
| fe79ebbcf5 | |||
| 6833c08b0f | |||
| fb0aec2a56 | |||
|
|
18d29487fa | ||
| e94f9c9250 | |||
| c92b7ac27a | |||
| 1737906c97 | |||
| 5c2e805427 | |||
| 61450c5284 | |||
| 8d422d0e33 | |||
|
|
5bd91dd8b9 | ||
| 9e778c3761 | |||
|
|
3ec9b3fa94 | ||
| 1fff9da4c6 | |||
| 15b7187622 | |||
| b5cd12e6f0 | |||
|
|
330b578c29 | ||
|
|
1e511da252 | ||
|
|
6577e42fa9 | ||
| 6e4581f7b9 | |||
| 0b253afe39 | |||
| 84daba0bcf | |||
| 36339dae54 | |||
| ffb8a8f5bd | |||
| 16eaafb5ea | |||
| b417242908 | |||
| 8411ee9f02 | |||
| 2bd157e9b7 | |||
| 762225e816 | |||
| 633af885cc | |||
| 442592db23 | |||
| 7349905e8e | |||
| 02420f41cd | |||
| a508714089 | |||
| 0e6c045411 | |||
| 7dcf8767e8 | |||
| a06dc38b43 | |||
| 0d631e8bf0 | |||
|
|
9770025013 | ||
| cec3da9a69 | |||
| c16701516d | |||
| b28c0bacc9 | |||
| 396549c850 | |||
| 2a7a895e11 | |||
| 0159f76fca | |||
| 256fe586ab |
46
.github/workflows/tf_update_dev.yml
vendored
@@ -1,46 +0,0 @@
|
||||
name: www2.threefold_io
|
||||
on:
|
||||
push:
|
||||
branches: [ development ]
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
name: Deploy
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: pushing latest change on www2.threefold.io
|
||||
uses: appleboy/ssh-action@master
|
||||
with:
|
||||
host: dev.threefold.io
|
||||
username: webuser
|
||||
key: ${{ secrets.TF_SECRET }}
|
||||
port: 34022
|
||||
script: |
|
||||
cd websites/www2/www_threefold_io/
|
||||
git log -1
|
||||
git fetch
|
||||
git reset --hard origin/development
|
||||
sed -i "s/https:\/\/www.threefold.io/https:\/\/dev.threefold.io/g" config.toml
|
||||
./build.sh
|
||||
|
||||
wait:
|
||||
needs: deploy
|
||||
name: Wait for Website Update
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Wait Period
|
||||
id: wait-deploy
|
||||
run: |
|
||||
echo "Sleeping for 30"
|
||||
sleep 30
|
||||
|
||||
checklinks:
|
||||
needs: wait
|
||||
name: Check for Broken Links
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Check for Broken Links
|
||||
id: link-report
|
||||
uses: docker://ghcr.io/threefoldfoundation/website-link-checker:latest
|
||||
with:
|
||||
args: 'https://www2.threefold.io -w 404'
|
||||
46
.github/workflows/tf_update_prod.yml
vendored
@@ -1,46 +0,0 @@
|
||||
name: www.threefold_io
|
||||
on:
|
||||
push:
|
||||
branches: [ master ]
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
name: Deploy
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: pushing latest change on www.threefold.io
|
||||
uses: appleboy/ssh-action@master
|
||||
with:
|
||||
host: www.threefold.io
|
||||
username: root
|
||||
key: ${{ secrets.TF_SECRET }}
|
||||
port: 22
|
||||
script: |
|
||||
cd /opt/www_threefold_io/
|
||||
git log -1
|
||||
git fetch
|
||||
git reset --hard origin/master
|
||||
sed -i "s/https:\/\/dev.threefold.io/https:\/\/www.threefold.io/g" config.toml
|
||||
./build.sh
|
||||
|
||||
wait:
|
||||
needs: deploy
|
||||
name: Wait for Website Update
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Wait Period
|
||||
id: wait-deploy
|
||||
run: |
|
||||
echo "Sleeping for 30"
|
||||
sleep 30
|
||||
|
||||
checklinks:
|
||||
needs: wait
|
||||
name: Check for Broken Links
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Check for Broken Links
|
||||
id: link-report
|
||||
uses: docker://ghcr.io/threefoldfoundation/website-link-checker:latest
|
||||
with:
|
||||
args: 'https://www.threefold.io -w 404'
|
||||
46
.github/workflows/update_dev2.yml
vendored
@@ -1,46 +0,0 @@
|
||||
name: www3.threefold_io
|
||||
on:
|
||||
push:
|
||||
branches: [ development_sasha ]
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
name: Deploy
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: pushing latest change on www3.threefold.io
|
||||
uses: appleboy/ssh-action@master
|
||||
with:
|
||||
host: www3.threefold.io
|
||||
username: webuser
|
||||
key: ${{ secrets.TF_SECRET }}
|
||||
port: 34022
|
||||
script: |
|
||||
cd websites/tmp/www_threefold_io/
|
||||
git log -1
|
||||
git restore .
|
||||
git pull
|
||||
sed -i "s/https:\/\/dev.threefold.io/https:\/\/dev2.threefold.io/g" config.toml
|
||||
bash build.sh
|
||||
|
||||
wait:
|
||||
needs: deploy
|
||||
name: Wait for Website Update
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Wait Period
|
||||
id: wait-deploy
|
||||
run: |
|
||||
echo "Sleeping for 30"
|
||||
sleep 30
|
||||
|
||||
checklinks:
|
||||
needs: wait
|
||||
name: Check for Broken Links
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Check for Broken Links
|
||||
id: link-report
|
||||
uses: docker://ghcr.io/threefoldfoundation/website-link-checker:latest
|
||||
with:
|
||||
args: 'https://www3.threefold.io -w 404'
|
||||
46
.github/workflows/update_www3.yml
vendored
@@ -1,46 +0,0 @@
|
||||
name: www3.threefold_io
|
||||
on:
|
||||
push:
|
||||
branches: [ 3.10.0 ]
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
name: Deploy
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: pushing latest change on www3.threefold.io
|
||||
uses: appleboy/ssh-action@master
|
||||
with:
|
||||
host: www3.threefold.io
|
||||
username: webuser
|
||||
key: ${{ secrets.TF_SECRET }}
|
||||
port: 34022
|
||||
script: |
|
||||
cd websites/www3/www_threefold_io/
|
||||
git log -1
|
||||
git restore .
|
||||
git pull
|
||||
sed -i "s/https:\/\/www.threefold.io/https:\/\/www3.threefold.io/g" config.toml
|
||||
bash build.sh
|
||||
|
||||
wait:
|
||||
needs: deploy
|
||||
name: Wait for Website Update
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Wait Period
|
||||
id: wait-deploy
|
||||
run: |
|
||||
echo "Sleeping for 30"
|
||||
sleep 30
|
||||
|
||||
checklinks:
|
||||
needs: wait
|
||||
name: Check for Broken Links
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Check for Broken Links
|
||||
id: link-report
|
||||
uses: docker://ghcr.io/threefoldfoundation/website-link-checker:latest
|
||||
with:
|
||||
args: 'https://www3.threefold.io -w 404'
|
||||
@@ -85,7 +85,7 @@ Discover the key products that bring us closer to our vision of the new internet
|
||||
image_src="/images/web4_tools3.png",
|
||||
image_alt="TF_products ",
|
||||
|
||||
title_1="3Node",
|
||||
title_1="3NODE",
|
||||
description_1="The backbone of storage and infrastructure, providing compute and data resources. Order today.
|
||||
",
|
||||
button_text_1="Learn More",
|
||||
@@ -96,11 +96,6 @@ Discover the key products that bring us closer to our vision of the new internet
|
||||
button_text_2="Learn More",
|
||||
button_link_2="https://docs.threefold.io/docs/components/3phone/",
|
||||
|
||||
title_3="3Bot",
|
||||
description_3="An AI-powered virtual system administrator helps deploy and manage your digital life.",
|
||||
button_text_3="Learn More",
|
||||
button_link_3="https://docs.threefold.io/docs/components/3bot",
|
||||
|
||||
title_4="3Router",
|
||||
description_4="Smart routers ensure shortest-path connections between nodes and phones with end-to-end encryption. Unlocked after 10,000 pre-orders.",
|
||||
button_text_4="Learn More",
|
||||
@@ -116,13 +111,15 @@ Discover the key products that bring us closer to our vision of the new internet
|
||||
<!-- section 4 Cta -->
|
||||
|
||||
{{ cta(
|
||||
title_1="Build the",
|
||||
title_2="Internet of Tomorrow,",
|
||||
title_3="Today",
|
||||
button_text_1="Take the Next Step",
|
||||
title_1="Building a",
|
||||
title_2="New Internet,",
|
||||
title_3="Together",
|
||||
button_text_1="Participate",
|
||||
button_link_1="/signup",
|
||||
button_text_2="Learn More",
|
||||
button_link_2="/action"
|
||||
button_text_2="Stay Updated",
|
||||
button_link_2="https://t.me/threefoldnews",
|
||||
button_text_3="Chat",
|
||||
button_link_3="https://t.me/threefold"
|
||||
) }}
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 510 B After Width: | Height: | Size: 510 B |
@@ -6,12 +6,12 @@ title = "ThreeFold"
|
||||
description = "Our global digital backbone"
|
||||
|
||||
# When set to "true", a feed is automatically generated.
|
||||
#generate_feed = true
|
||||
generate_feed = true
|
||||
|
||||
# The filename to use for the feed. Used as the template filename, too.
|
||||
# Defaults to "atom.xml", which has a built-in template that renders an Atom 1.0 feed.
|
||||
# There is also a built-in template "rss.xml" that renders an RSS 2.0 feed.
|
||||
#feed_filename = "atom.xml"
|
||||
feed_filename = "atom.xml"
|
||||
|
||||
# The number of articles to include in the feed. All items are included if
|
||||
# this limit is not set (the default).
|
||||
@@ -51,8 +51,8 @@ external_links_no_referrer = true
|
||||
# For example, `...` into `…`, `"quote"` into `“curly”` etc
|
||||
smart_punctuation = true
|
||||
|
||||
#[build]
|
||||
#not_found = "404.md"
|
||||
[build]
|
||||
not_found = "404.md"
|
||||
|
||||
[[taxonomies]]
|
||||
name = "categories"
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "ThreeFold's Vision and Mission"
|
||||
title: "about"
|
||||
description: "Our mission is to empower individuals and organizations with secure, private, and autonomous access to computing resources, ensuring fair cloud access for everyone." # quotation marks to allow colons where used
|
||||
template: "page.html"
|
||||
insert_anchor_links: "left"
|
||||
@@ -24,10 +24,9 @@ The Internet brings the world together, yet much of it is now concentrated in th
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!----------------------------------------------------------------------------------------->
|
||||
|
||||
|
||||
|
||||
<!-- section 2 -->
|
||||
<!-- section 2 (reason) -->
|
||||
|
||||
{{ description_blockquote(
|
||||
title="The Reason Behind It All",
|
||||
@@ -38,12 +37,10 @@ The Internet brings the world together, yet much of it is now concentrated in th
|
||||
|
||||
description_3="For +30 years, we’ve dedicated ourselves to this vision, and ThreeFold is the culmination of that journey. Today, we have a fully operational product (V3) and a thriving community of farmers, users, and partners.",
|
||||
|
||||
description_4="Therefore we believe the Internet needs a fresh start—one that addresses these challenges with a focus on authenticity, equality, and sustainability for everyone."
|
||||
|
||||
|
||||
description_4="Therefore we believe the Internet needs a fresh start—one that addresses these challenges with a focus on authenticity, equality, and sustainability for everyone."
|
||||
) }}
|
||||
|
||||
|
||||
<!----------------------------------------------------------------------------------------->
|
||||
|
||||
<!-- section 3 (AI) -->
|
||||
|
||||
@@ -65,7 +62,7 @@ We must not repeat mistakes of the past. Without decentralization, AI will remai
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<!----------------------------------------------------------------------------------------->
|
||||
|
||||
<!-- section 4 (web4) -->
|
||||
|
||||
@@ -76,7 +73,7 @@ We must not repeat mistakes of the past. Without decentralization, AI will remai
|
||||
|
||||
<div class="max-w-3xl">
|
||||
|
||||
Unlike traditional internet infrastructure, which relies on centralized data centers and corporate control, ThreeFold is built on a global mesh of independent cloud providers—individuals and organizations who contribute data, cloud and network power directly to the ecosytem.
|
||||
Unlike traditional internet infrastructure, which relies on centralized data centers and corporate control, ThreeFold is built on a global mesh of independent cloud providers—individuals and organizations who contribute data, cloud and network power directly to the ecosystem.
|
||||
|
||||
<br>
|
||||
|
||||
@@ -86,7 +83,7 @@ This makes ThreeFold uniquely decentralized at the physical layer, eliminating s
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<!----------------------------------------------------------------------------------------->
|
||||
|
||||
<!-- section 5 (timeline) -->
|
||||
|
||||
@@ -103,15 +100,15 @@ Over the past decades, we’ve tackled complex challenges in areas such as data
|
||||
subtitle_1="Phase I",
|
||||
title_1="Creation of Core Technology",
|
||||
point_1_1="Open Source Development.",
|
||||
point_1_2="Built decentralized, autonomous, edge internet technology",
|
||||
point_1_3="Self-funded and private investment from founders, community, and TF Tech investors",
|
||||
point_1_2="Built decentralized, autonomous, edge internet technology.",
|
||||
point_1_3="Self-funded and private investment from founders, community, and TF Tech investors.",
|
||||
|
||||
subtitle_2="Phase II",
|
||||
title_2="Global Proof Of Concept",
|
||||
title_2="Global Proof Of Concept.",
|
||||
point_2_1="Open Source Development.",
|
||||
point_2_2="50+ Countries.",
|
||||
point_2_3="50,000+ Cores.",
|
||||
point_2_4="25,000,000 GB of Storage",
|
||||
point_2_4="25,000,000 GB of Storage.",
|
||||
point_2_5="Thousands of enthusiasts actively engage with and contribute to the evolution of the ThreeFold Network.",
|
||||
point_2_6="Decentralized reliable compute, network and storage layer for Web 2-3.",
|
||||
point_2_7="Commitments from wonderful projects to build on top of us.",
|
||||
@@ -134,7 +131,7 @@ Over the past decades, we’ve tackled complex challenges in areas such as data
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<!----------------------------------------------------------------------------------------->
|
||||
|
||||
<!-- section 6 (Values) -->
|
||||
|
||||
@@ -146,7 +143,7 @@ Over the past decades, we’ve tackled complex challenges in areas such as data
|
||||
|
||||
) }}
|
||||
|
||||
|
||||
<!----------------------------------------------------------------------------------------->
|
||||
|
||||
<!-- section 7 (Team) -->
|
||||
|
||||
@@ -164,20 +161,18 @@ Over the past decades, we’ve tackled complex challenges in areas such as data
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
<!----------------------------------------------------------------------------------------->
|
||||
|
||||
<!-- section 8 Cta -->
|
||||
|
||||
{{ cta(
|
||||
title_1="Build the",
|
||||
title_2="Internet of Tomorrow,",
|
||||
title_3="Today",
|
||||
button_text_1="Take the Next Step",
|
||||
title_1="Building a",
|
||||
title_2="New Internet,",
|
||||
title_3="Together",
|
||||
button_text_1="Participate",
|
||||
button_link_1="/signup",
|
||||
button_text_2="Learn More",
|
||||
button_link_2="/action"
|
||||
button_text_2="Stay Updated",
|
||||
button_link_2="https://t.me/threefoldnews"
|
||||
) }}
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 510 B After Width: | Height: | Size: 510 B |
BIN
content/blog/3_step_rollout/3_step_rollout.png
Normal file
|
After Width: | Height: | Size: 260 KiB |
142
content/blog/3_step_rollout/index.md
Normal file
@@ -0,0 +1,142 @@
|
||||
---
|
||||
id: 3_step_rollout
|
||||
title: The Three Step Rollout to a Sovereign Agentic Cloud
|
||||
image_caption: technology
|
||||
description: "ThreeFold is enabling a Sovereign Agentic Cloud through three architectural layers: Cloud, Network, and Agents – a new generation of cloud and AI infrastructure."
|
||||
date: 2025-10-17
|
||||
taxonomies:
|
||||
people: [raj_mitra]
|
||||
tags: [tech,grid,community]
|
||||
categories: [tech,grid,cloud]
|
||||
extra:
|
||||
imgPath: 3_step_rollout.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
The internet is evolving once again – but this time, not through the types of platforms or services that defined past waves. What we’re witnessing is the emergence of an **agentic internet**, where autonomous digital agents will become the foundation of online life.
|
||||
|
||||
</br>
|
||||
|
||||
This evolution could unfold in one of two directions:
|
||||
|
||||
- **Centralized**, where a handful of corporations and governments control the agents, their data, and the infrastructure they run on
|
||||
- **Decentralized**, where individuals and communities own their agents, data, and digital environments, creating a more open, sovereign web.
|
||||
|
||||
</br>
|
||||
|
||||
At ThreeFold, we believe the decentralized path requires a new kind of digital foundation – one we call the **Sovereign Agentic Cloud**.
|
||||
|
||||
</br>
|
||||
|
||||
This is not just another version of the internet, it’s the necessary foundation for a decentralized digital ecosystem built for the future: a new generation of cloud and AI infrastructure that is faster, greener, smarter, private, and secure.
|
||||
|
||||
</br>
|
||||
|
||||
Our rollout to this future is unfolding now in three phases:
|
||||
|
||||
- The Cloud: Live
|
||||
- The Network: Live
|
||||
- The Agents: January 2026
|
||||
|
||||
</br>
|
||||
|
||||
Each layer builds on the one before it, sequentially creating the architecture for a truly sovereign agentic cloud.
|
||||
|
||||
</br>
|
||||
|
||||
The **Cloud** lays the groundwork with decentralized compute and storage – the base layer of an independent digital life that expands as new capacity comes online across the grid.
|
||||
|
||||
</br>
|
||||
|
||||
But capacity alone means little without coordination. That’s where the **Network** comes in, connecting distributed nodes into an intelligent mesh where data, models, and services can move freely.
|
||||
|
||||
</br>
|
||||
|
||||
With computation and connectivity in place, the system becomes ready for cognition – the **Agents**. These self-owned AI agents emerge as the logical extension of the architecture, using the Cloud for processing and the Network for communication. Together, they form the first generation of decentralized, autonomous intelligence.
|
||||
|
||||
### **The Cloud**
|
||||
The Cloud forms the foundation, a 100% Kubernetes-compatible compute and storage layer that operates as a global, distributed cloud.
|
||||
|
||||
</br>
|
||||
|
||||
Built on top of the ThreeFold Grid, it draws from independent capacity providers around the world. Each contributes compute, storage, and network resources, forming a resilient, peer-to-peer infrastructure that’s already live today.
|
||||
|
||||
</br>
|
||||
|
||||
This layer makes decentralized Kubernetes real and accessible. Developers can spin up clusters directly across the grid using familiar declarative workflows, autoscaling, monitoring, and logging tools – all without reliance on centralized cloud vendors.
|
||||
|
||||
</br>
|
||||
|
||||
The result is a production-grade environment that offers the usability of conventional clouds combined with the sovereignty, security, and resilience of decentralization. Developers gain the freedom to deploy applications anywhere, anytime, without gatekeepers.
|
||||
|
||||
</br>
|
||||
|
||||
While ThreeFold’s community-driven open-source cloud has been live for years with [builders already commercializing its resources](/blog/tf-decentralized-cloud-new/), this new Kubernetes-based solution marks a major evolution: simplified, commercial-ready, and purpose-built to host the next generation of autonomous agents. It’s the necessary foundation for the sovereign agentic cloud.
|
||||
|
||||
<br/>
|
||||
|
||||
Stay tuned this month for the release of the Kubernetes Cloud.
|
||||
|
||||
### **The Network**
|
||||
The next step extends this foundation into a living, intelligent network layer.
|
||||
|
||||
</br>
|
||||
|
||||
This step introduces a full suite of decentralized network services – including VPN, DNS, CDN, and LLM gateways – all designed to make the underlying grid fully reachable, programmable, and autonomous.
|
||||
|
||||
</br>
|
||||
|
||||
These gateways transform ordinary grid nodes into public-facing endpoints, solving one of the hardest problems in decentralized hosting: achieving global accessibility while providing greater independence from scarce IPv4 addresses and centralized ISPs.
|
||||
|
||||
</br>
|
||||
|
||||
Traffic moves dynamically across the mesh. Every connection is encrypted end-to-end. And instead of relying on fixed routes or central ISPs, the network forms a peer-to-peer overlay that automatically discovers and maintains the most efficient path between nodes.
|
||||
|
||||
</br>
|
||||
|
||||
When a node or connection goes down, the network self-heals, rerouting traffic in real time to maintain uptime. This allows workloads running anywhere on the grid, even on devices without public IPs, to communicate securely and act as if they were hosted in a single, unified data center.
|
||||
|
||||
</br>
|
||||
|
||||
What sets this network apart is not just its autonomy, but its evolutionary behavior. As the grid grows, it adapts, reconfiguring routes, optimizing performance, and expanding reach.
|
||||
|
||||
</br>
|
||||
|
||||
Parts of the network are already operational, with ongoing developments making it ever more powerful, efficient, and resource-rich.
|
||||
|
||||
### **The Agents**
|
||||
The final phase brings the architecture to life: the Agent Layer, the cognitive and operational tier of the Sovereign Agentic Cloud.
|
||||
|
||||
</br>
|
||||
|
||||
Within this layer, every person can have one or more Personal Agents – intelligent digital counterparts that manage tasks, workflows, and communication while maintaining full sovereignty over data and identity.
|
||||
|
||||
</br>
|
||||
|
||||
These personal agents can coordinate networks of "Worker Agents," each capable of handling specialized functions such as research, coding, analysis, or transactions.
|
||||
|
||||
</br>
|
||||
|
||||
Supporting them is a secure foundation of semantic search, private active memory, and long-term, zero-knowledge storage, allowing agents to learn, reason, and operate within encrypted, self-contained sandboxes.
|
||||
|
||||
#### Agent Layer Evolution: From AGI to ACI
|
||||
While much of the world is racing toward AGI (Artificial General Intelligence) – massive centralized systems aiming to replicate human cognition – we’re charting a different course.
|
||||
|
||||
</br>
|
||||
|
||||
Today’s AI giants control nearly all of the compute, data, and infrastructure required to train and deploy large models. This concentration of power brings enormous risks such as surveillance-driven data collection, bias embedded at scale, and energy consumption rivaling entire nations.
|
||||
|
||||
</br>
|
||||
|
||||
ThreeFold’s approach is rooted in Augmented Collective Intelligence (ACI). Not a machine trying to mimic humans, but a system that grows through shared human experience while protecting each individual’s privacy.
|
||||
|
||||
</br>
|
||||
|
||||
There’s no hidden monetization model, no surveillance layer, no opaque black box where your information disappears. Each agent learns locally, contributes globally, and respects the sovereignty of its user. It’s a model of intelligence that grows organically, not hierarchically.
|
||||
|
||||
### **Building The Vision**
|
||||
That is the vision of what we call the Sovereign Agentic Cloud: a fully decentralized ecosystem where the Cloud provides resilient compute and storage, the Network connects nodes into an intelligent, self-healing mesh, and the Agent layer brings autonomous, personal intelligence to life. Together these layers form a self-sovereign foundation for the next generation of digital life.
|
||||
|
||||
</br>
|
||||
|
||||
Development toward this vision is well underway, with the Cloud and Network systems already live and evolving, and agents coming in Q1 2026. Stay tuned via our [news channel](https://t.me/threefoldnews) and [chat](https://t.me/threefold) as the rollout unfolds.
|
||||
@@ -12,7 +12,7 @@ insert_anchor_links: "left"
|
||||
template: "layouts/blog.html"
|
||||
page_template: "blogPage.html"
|
||||
#transparent: true
|
||||
#generate_feed: true
|
||||
generate_feed: true
|
||||
extra:
|
||||
imgPath: tf.png
|
||||
---
|
||||
|
||||
|
Before Width: | Height: | Size: 2.3 MiB After Width: | Height: | Size: 576 KiB |
@@ -10,6 +10,7 @@ taxonomies:
|
||||
categories: [tech,grid,community]
|
||||
extra:
|
||||
imgPath: a_million_nodes.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
Imagine a digital world where control isn't dictated by centralized entities but by the collective power of a million interconnected nodes. This vision is more than just a technological advancement – it embodies a paradigm shift towards re-decentralizing the Internet and putting control back into the hands of its users, as it was originally intended to be.
|
||||
|
||||
|
Before Width: | Height: | Size: 1.0 MiB After Width: | Height: | Size: 264 KiB |
@@ -24,14 +24,4 @@ The second summit saw the birth of Dunia Yetu (meaning "Our World" in Swahili),
|
||||
|
||||
<br>
|
||||
|
||||
Looking ahead to 2024, our vision includes a continued series of gatherings focused on OurWorld, ThreeFold, and other projects and individuals prioritizing a planet-first, people-first approach to support Tanzania and the broader African continent.
|
||||
|
||||
<br>
|
||||
|
||||
More information:
|
||||
|
||||
<br>
|
||||
|
||||
- **Summit I:** Read [Zanzibar Seeks to Become a Digital FreeZone](https://www.thecitizen.co.tz/tanzania/zanzibar/zanzibar-seeks-to-become-digital-freezone--4316150) (via The Citizen) and [Mwinyi Commits to Improvement of Digital Spaces](https://dailynews.co.tz/mwinyi-commits-to-improvement-of-digital-spaces/) (via Daily News Tanzania) for further details.
|
||||
- **Summit II:** Learn more about [Dunia Yetu](https://www.threefold.io/newsroom/duniayetulaunchdar/)
|
||||
- **Dunia Yetu:** Read [Sovereign Internet - A game changer for Tanzania](https://www.thecitizen.co.tz/tanzania/news/national/sovereign-internet-a-game-changer-to-tanzania-startups-ecosystem-growth-449806) (via The Citizen)
|
||||
Looking ahead to 2024, our vision includes a continued series of gatherings focused on OurWorld, ThreeFold, and other projects and individuals prioritizing a planet-first, people-first approach to support Tanzania and the broader African continent.
|
||||
@@ -10,6 +10,7 @@ taxonomies:
|
||||
categories: [tech,grid,community]
|
||||
extra:
|
||||
imgPath: back_to_the_future.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
In 1989, Tim Berners-Lee envisioned a World Wide Web where people everywhere could create, access, and share knowledge freely. It was a bold and beautiful idea: an open, decentralized platform where humanity could collaborate. Born in the halls of CERN and rooted in academia and scientific generosity, the early web was peer-to-peer in spirit and architecture. But somewhere along the way, we lost the plot.
|
||||
|
||||
|
Before Width: | Height: | Size: 1.1 MiB After Width: | Height: | Size: 308 KiB |
|
Before Width: | Height: | Size: 719 KiB After Width: | Height: | Size: 171 KiB |
|
Before Width: | Height: | Size: 517 KiB After Width: | Height: | Size: 157 KiB |
|
Before Width: | Height: | Size: 402 KiB After Width: | Height: | Size: 130 KiB |
|
Before Width: | Height: | Size: 430 KiB After Width: | Height: | Size: 125 KiB |
BIN
content/blog/cloudfare_wtf_happened/cloudfare.jpg
Normal file
|
After Width: | Height: | Size: 7.5 KiB |
BIN
content/blog/cloudfare_wtf_happened/cloudfare_wtf_happened.png
Normal file
|
After Width: | Height: | Size: 40 KiB |
130
content/blog/cloudfare_wtf_happened/index.md
Normal file
@@ -0,0 +1,130 @@
|
||||
---
|
||||
id: cloudfare
|
||||
title: "Cloudflare... Wtf Happened?"
|
||||
image_caption: cloudfare
|
||||
description: A single Cloudflare update knocked out 20% of the internet on November 18th, serving as another reminder of how fragile our centralized web infrastructure really is. So what went wrong?
|
||||
date: 2025-11-19
|
||||
taxonomies:
|
||||
people: [raj_mitra]
|
||||
tags: [tech,grid,community]
|
||||
categories: [tech,grid,cloud]
|
||||
extra:
|
||||
imgPath: cloudfare_wtf_happened.png
|
||||
|
||||
---
|
||||
|
||||
This genuinely felt like groundhog day.
|
||||
|
||||
<br/>
|
||||
|
||||
On Tuesday, 18th November, a fifth of the world’s websites went down as Cloudflare went down. And yes, a lot of, so called, “decentralized” services also went down as a result.
|
||||
|
||||
<br/>
|
||||
|
||||
However, we have seen this movie before. Last month, we saw websites going down due to a [global AWS outage](https://www.threefold.io/blog/what-comes-next/).
|
||||
|
||||
<br/>
|
||||
|
||||
This really begs the question. How resilient is the world wide web, if it is constantly dependent on centralized service providers?
|
||||
|
||||
<br/>
|
||||
|
||||
Let’s understand what exactly happened.
|
||||
|
||||
### **The Update That Broke The Internet**
|
||||
|
||||
Cloudflare’s global outage wasn’t caused by DNS issues, an attack, or any systemic failure across the internet.
|
||||
|
||||
<br/>
|
||||
|
||||
Believe it or not, it just came down to a single configuration file used for bot mitigation. The file in question is automatically generated from live threat-intelligence feeds. It’s meant to update continuously to block bots, abusive traffic, and malicious patterns. At some point before the outage, its size expanded far beyond what the underlying software was built to tolerate.
|
||||
|
||||
<br/>
|
||||
|
||||
Under normal circumstances the system reloads this file without incident. However, this time, the oversized file hit a latent bug inside Cloudflare’s bot-management engine, causing it to crash repeatedly.
|
||||
|
||||
<br/>
|
||||
|
||||
Now, since this component sits in the request path for most Cloudflare products, its failure caused widespread 500 errors across the network.
|
||||
|
||||
<br/>
|
||||
|
||||
Once that service collapsed, the effects rippled through Cloudflare’s global infrastructure. Websites depending on Cloudflare’s CDN, WAF, and bot filtering began failing almost simultaneously. Users saw generic “500 errors,” and even Cloudflare’s own dashboard and API became inaccessible.
|
||||
|
||||
<br/>
|
||||
|
||||
Major platforms like ChatGPT, X, Shopify, Uber, Spotify, Indeed, Claude, Perplexity, Canva, NJ Transit’s digital systems, and countless others were unreachable for hours simply because they are all fronted by Cloudflare’s global network.
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
Eventually, a fix was rolled out by late morning Eastern Time. Engineers patched the underlying issue, reverted the problematic configuration, and gradually restored dependent systems.
|
||||
|
||||
### **What Is the Solution?**
|
||||
|
||||
To his credit, Cloudflare CTO Dane Knecht admitted that the company "failed” its customers. However, an apology isn't enough when a system that is currently responsible for the global trillion dollar economy and other critical services is seemingly so fragile that it can't handle a single company's update.
|
||||
|
||||
<br/>
|
||||
|
||||
Cloudflare “fixed” the issue. But did they actually heal the wound or put a flimsy little band aid? History tells us that it is likely the latter.
|
||||
|
||||
<br/>
|
||||
|
||||
We saw the same pattern with AWS’s regional DNS failure, Microsoft’s global Azure collapse, and CrowdStrike’s faulty update that halted hospitals and grounded planes. Quick patches are applied, but the core fragility remains untouched.
|
||||
|
||||
<br/>
|
||||
|
||||
This isn’t a Cloudflare problem.
|
||||
|
||||
<br/>
|
||||
|
||||
It’s an internet architecture problem.
|
||||
|
||||
<br/>
|
||||
|
||||
And that’s where alternatives must be taken seriously.
|
||||
|
||||
<br/>
|
||||
|
||||
Fixing configuration files is not the solution. Rebuilding the foundation is.
|
||||
|
||||
### **The ThreeFold Alternative: A Different Kind of Internet**
|
||||
|
||||
Instead of patching over the centralization crisis, ThreeFold rebuilds the foundation entirely.
|
||||
|
||||
<br/>
|
||||
|
||||
Instead of a few hyperscale providers powering the world, ThreeFold utilizes thousands of independent capacity providers to contribute compute, storage, and bandwidth to a unified, autonomous grid. Its Sovereign Agentic Cloud is designed around decentralization, autonomy, and distribution. The exact qualities today’s internet has lost.
|
||||
|
||||
<br/>
|
||||
|
||||
ThreeFold works across three layers:
|
||||
|
||||
<br/>
|
||||
|
||||
- **The Cloud:** A decentralized, Kubernetes-compatible cloud running on independent capacity providers instead of hyperscale data centers.
|
||||
- **The Network:** A peer-to-peer mesh with built-in VPN, DNS, CDN, and gateways, creating a self-healing connectivity fabric.
|
||||
- **The Agents:** Autonomous, user-owned digital agents running on decentralized compute, not Big Tech servers.
|
||||
|
||||
<br/>
|
||||
|
||||
Together, these create an internet that grows more resilient as it expands.
|
||||
|
||||
### **Why This Actually Fixes the Problem**
|
||||
|
||||
ThreeFold’s solution represents a return to that original vision of the internet. A decentralized, sovereign, human-aligned internet that isn’t vulnerable to the failure of one company, one region, or one configuration file. As ThreeFold co-founder Florian Fournier puts it:
|
||||
|
||||
<br/>
|
||||
|
||||
*“The internet was meant to be a network of peers, open, resilient, and free. Over time, it became a network of platforms.”*
|
||||
|
||||
<br/>
|
||||
|
||||
ThreeFold’s work is aimed at rebuilding the web from the ground up. This is not a band aid. Our solution dares to restructure what is broken. And In a world where a single file update can cripple platforms worth billions, it’s clear that this is the direction the internet should have taken all along.
|
||||
|
||||
<br/>
|
||||
|
||||
Do you want to join our mission? [Start here](https://threefold.info/mycelium_meet_4nov/docs/) and [stay tuned](https://t.me/threefoldnews).
|
||||
|
Before Width: | Height: | Size: 814 KiB After Width: | Height: | Size: 308 KiB |
|
Before Width: | Height: | Size: 1.2 MiB After Width: | Height: | Size: 351 KiB |
BIN
content/blog/depin_summit_recap/arushacrew.jpg
Normal file
|
After Width: | Height: | Size: 381 KiB |
BIN
content/blog/depin_summit_recap/bridge1.png
Normal file
|
After Width: | Height: | Size: 492 KiB |
BIN
content/blog/depin_summit_recap/bridge2.png
Normal file
|
After Width: | Height: | Size: 434 KiB |
BIN
content/blog/depin_summit_recap/charter.png
Normal file
|
After Width: | Height: | Size: 377 KiB |
BIN
content/blog/depin_summit_recap/dcma.png
Normal file
|
After Width: | Height: | Size: 424 KiB |
BIN
content/blog/depin_summit_recap/demoday.jpg
Normal file
|
After Width: | Height: | Size: 399 KiB |
BIN
content/blog/depin_summit_recap/depin_summit_recap.png
Normal file
|
After Width: | Height: | Size: 306 KiB |
BIN
content/blog/depin_summit_recap/flomombasa.jpg
Normal file
|
After Width: | Height: | Size: 380 KiB |
BIN
content/blog/depin_summit_recap/giraffe.jpeg
Normal file
|
After Width: | Height: | Size: 432 KiB |
230
content/blog/depin_summit_recap/index.md
Normal file
@@ -0,0 +1,230 @@
|
||||
---
|
||||
id: depin_summit_recap
|
||||
title: "From Vision to Reality: DePIN Comes Alive in East Africa"
|
||||
image_caption: DePIN Summit Recap
|
||||
description: A powerful week of community, collaboration, and real-world impact as decentralized infrastructure takes root in East Africa.
|
||||
date: 2025-07-11
|
||||
taxonomies:
|
||||
people: [sam_taggart]
|
||||
tags: [decentralization, event, why]
|
||||
categories: [decentralization, event, why]
|
||||
extra:
|
||||
imgPath: depin_summit_recap.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
*Recapping an incredible DePIN Summit 2025: Africa Edition. Thanks to [EV3](https://ev3.xyz/) for bringing DePIN Summit to East Africa, [Share](https://www.share.inc/), [Singularity Venture Hub](https://www.singularityventurehub.ai/), our own team, [ZICTIA](https://zictia.go.tz/), all of the organizers, venues, various staff and execution teams, speakers, and participants for being a part of this. Thanks as well to [Proof of Coverage](https://x.com/Proof_Coverage) for some of the photos included in this post. Others are my own (see if you can spot the quality difference!).*
|
||||
|
||||
<br/>
|
||||
|
||||
Over the course of a powerful week in East Africa, DePIN enthusiasts, builders, founders, investors, government stakeholders, and dreamers from around the globe gathered for DePIN Summit 2025, a one-of-a-kind gathering that brought decentralized physical infrastructure to life through conversation, community, and concrete impact.
|
||||
|
||||
<br/>
|
||||
|
||||
The summit unfolded in two acts: Mombasa, Kenya and Zanzibar, Tanzania, with some joining for a closing journey to Arusha and sticking around Zanzibar to further solidify discussions and work towards tangible outcomes.
|
||||
|
||||
### **Part I: Mombasa**
|
||||
|
||||

|
||||
|
||||
#### Sunday June 29: Day Zero: Arrival & Alignment
|
||||
|
||||
As the sun set over the Kenyan coast, founders, speakers, and project leads touched down in Mombasa. The [Share](https://share.inc) team, on-the-ground co-organizers of the first leg of the summit, hosted an informal gathering at their HQ, setting the tone for what would be a high-trust, high-purpose summit experience.
|
||||
|
||||
#### Monday June 30: Day One: Learning from the Ground Up
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
We visited two [Bridge International Academies](https://www.bridgeinternationalacademies.com/) where students and teachers are already engaging with digital learning through tablets, despite having a shaky power supply and not having an internet connection on-site. Currently, staff use a single smartphone to upload daily progress.
|
||||
|
||||
<br/>
|
||||
|
||||
Share will soon equip the school with unlimited WiFi access, using its innovative technology to support and elevate the quality of student learning. It’s a powerful initiative, and one that rightly earned them praise for turning bold vision into real-world impact.
|
||||
|
||||
<br/>
|
||||
|
||||
*We’re thinking the obvious – and we’re exploring with the Share team how we can support in bringing ThreeFold nodes to Mombasa to ensure these schools will not have just have their connectivity, but that their own capacity as well.*
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
During our visit, some students showed off local song and dance while others even prepared and performed spoken word poetry on the theme of the Internet. Later, that evening, a community dinner allowed conversations to deepen among builders, speakers, and local partners.
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
*Do you spot our tall friends in the background? An epic photobomb and overall experience at [Nguuni Nature Sanctuary](https://www.nguuninaturesanctuary.org/).*
|
||||
|
||||
#### Tuesday July 01: Day Two: Build on the Beach & Dine on a Dhow
|
||||
|
||||
As a pre-summit kickoff, [**Beach & Build**](https://lu.ma/4gcze4zw?tk=C6ULfS) offered a relaxed afternoon on the Mombasa shoreline, designed for connection, collaboration, and casual networking, setting the tone for the week ahead.
|
||||
|
||||
<br/>
|
||||
|
||||
Later in the evening, we enjoyed “DePIN on Deck,” aboard a traditional Swahili coast dhow boat. With stunning coastal views, fresh seafood, and vibrant conversations, guests enjoyed a relaxed, intimate setting to connect and unwind.
|
||||
|
||||
#### Wednesday July 02: Day Three: DePIN Summit Launches
|
||||
|
||||
The first official summit day featured a full agenda of talks, demos, and showcases. Hosted at the headquarters of [Swahilipot Hub](https://www.swahilipothub.co.ke/), a foundation focused on nurturing youth talent through tech, arts, and entrepreneurship, the summit opened with EV3 and Share explaining why and why now for the summit to be held in Africa and introducing Share as a project.
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
The audience included mostly students and local and international entrepreneurs and founders. ThreeFold co-founder Florian Fournier delivered a keynote on the future of decentralized internet in East Africa.
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
*Florian spoke about the ThreeFold story and showed off one of the original ThreeFold nodes (perched on top of the podium).*
|
||||
|
||||
<br/>
|
||||
|
||||
The other projects that gave keynotes included [DeCharge](https://decharge.network/), [Arkreen](https://www.arkreen.com/), [Titan](https://www.titannet.io/), [Element Pay](https://www.elementpay.net/), [Onocoy](https://onocoy.com/), [WeatherXM](https://weatherxm.com/), [RealityNet](https://www.realitynet.xyz/), [Pickspot](https://www.pickspot.net/), [Qualoo](https://www.qualoo.io/), [Natix](https://www.natix.network/), and more.
|
||||
|
||||
### **Part II: Zanzibar**
|
||||
|
||||

|
||||
|
||||
#### Thursday July 03: Day Zero: Crossing to Zanzibar
|
||||
|
||||
Some speakers and attendees took a chartered flight from Mombasa to Zanzibar, bringing the summit spirit over the Indian Ocean to Spice Island.
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
We were joined by new attendees and warmly welcomed with a sunset session to set intentions for the second leg of the summit.
|
||||
|
||||
#### Friday July 04: Day One: Public Infrastructure Meets Policy
|
||||
|
||||
The first official day of the Zanzibar summit was held at the Madinat Al Bahr. The event brought together global builders and Zanzibar's local ecosystem, including Eng. Shukuru Awadh Suleiman, Director General of [Zanzibar Communication Corporation](https://zictia.go.tz/) (ZICTIA), our partner on the ground on the island.
|
||||
|
||||
<br/>
|
||||
|
||||
ThreeFold co-founder Kristof De Spiegeleer started with a presentation on ThreeFold and what it enables in East Africa and beyond.
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
There were also presentations from WeatherXM, Arkreen, Natix, Reality, Qualoo, [Peaq](https://www.peaq.xyz/) (ThreeFold partner), DeCharge, Share, Swahili Pot, and [Africa Amini Life](https://www.africaaminilife.com/en). Along with that, we had:
|
||||
|
||||
<br/>
|
||||
|
||||
- **Investment Panel**: Investing in DePIN, featuring Dylan, Rapolas, and Volt
|
||||
- **Ecosystem Panel:** Flora ([Sahara Ventures](https://saharaventures.com/)) and Msechu ([Serengeti Angels](https://serengetiangels.com/)) outlined challenges and opportunities across the region, hosted by Sal of EV3
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
Towards the end of the day, Kristof was joined on stage by Eng. Shukuru Awadh Suleiman of ZICTIA to discuss the collaboration between ThreeFold and the government of Zanzibar.
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
Following a long but inspiring day, the guests enjoyed Swahili BBQ with live music and with local artist [Tryphon Evarist](https://www.musicinafrica.net/directory/tryphon-evarist).
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
#### Saturday July 05: Day Two: Demo Day & Closing Ceremony
|
||||
|
||||
At the historic Mbweni Ruins, DePIN builders showcased their hardware, software, and product experiences. Florian led a visit to the land of [Dunia Cyber City and Zanzibar Free Zone](https://ourworld.tf/ventures/).
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
*WeatherXM deployed some of their hardware in Kenya and we’re working on getting a station live here in Zanzibar!*
|
||||
|
||||
<br/>
|
||||
|
||||
Builders from around the world presented real-world solutions for emerging markets.
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
Later, the community gathered with [Light DAO](https://lightdao.one/) for a thought session with Kristof and Florian, followed by a closing celebration with local music and performances to honor both global innovators and the communities they serve.
|
||||
|
||||
<br/>
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
*Students from the [Dhow Countries Music Academy](https://www.zanzibarmusic.org/) in Stone Town, Zanzibar performed and brought summit attendees on stage to participate.*
|
||||
|
||||
### Part III: Arusha
|
||||
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
Following the summit, a group of 35 attendees traveled to Arusha for a post-summit visit to experience authentic Tanzania. The trip included a safari and time with the Maasai tribe at one of their lodges, as well as a visit to a local school where students received tablets on their first day back. Both the lodge stay and the school visit are part of the Africa Amini Life project, with a portion of the lodge proceeds helping to fund the school, medical clinics, and other key local institutions.
|
||||
|
||||
<br/>
|
||||
|
||||
 <br/>
|
||||

|
||||
|
||||
<br/>
|
||||
|
||||
*ThreeFold and Africa Amini Alliance are working to collaborate to bring further digital inclusion to even the most remote communities in Tanzania.*
|
||||
|
||||
<br/>
|
||||
|
||||
Then, nearly twenty of us returned to Zanzibar to reunite with other summit attendees and ground the ideas and discussions from the summit into tangible next steps.
|
||||
|
||||
### Final Reflections
|
||||
|
||||
What an unforgettable experience. We were honored to co-host this landmark event along with EV3 and Share, and deeply proud to have showcased a diverse range of groundbreaking DePIN projects while spotlighting Africa as a powerful hub for emerging technology and innovation.
|
||||
|
||||
<br/>
|
||||
|
||||
From Mombasa to Zanzibar to Arusha, we saw the DePIN vision become real.
|
||||
|
||||
<br/>
|
||||
|
||||
We didn’t just talk about decentralized infrastructure.
|
||||
|
||||
<br/>
|
||||
|
||||
We lived it.
|
||||
|
||||
<br/>
|
||||
|
||||
Onward! Together we build.
|
||||
|
||||
<br/>
|
||||
|
||||
*More to share and more to come as concrete outcomes develop.*
|
||||
BIN
content/blog/depin_summit_recap/kristofkeynote.jpg
Normal file
|
After Width: | Height: | Size: 559 KiB |
BIN
content/blog/depin_summit_recap/lightdao.jpeg
Normal file
|
After Width: | Height: | Size: 388 KiB |
BIN
content/blog/depin_summit_recap/maasai.png
Normal file
|
After Width: | Height: | Size: 408 KiB |
BIN
content/blog/depin_summit_recap/mombasacrowd.jpg
Normal file
|
After Width: | Height: | Size: 428 KiB |
BIN
content/blog/depin_summit_recap/opening.jpg
Normal file
|
After Width: | Height: | Size: 295 KiB |
BIN
content/blog/depin_summit_recap/panel.jpg
Normal file
|
After Width: | Height: | Size: 535 KiB |
BIN
content/blog/depin_summit_recap/schoolvisit.png
Normal file
|
After Width: | Height: | Size: 373 KiB |
BIN
content/blog/depin_summit_recap/tryphon.png
Normal file
|
After Width: | Height: | Size: 362 KiB |
BIN
content/blog/depin_summit_recap/zanzibarreg.jpg
Normal file
|
After Width: | Height: | Size: 391 KiB |
BIN
content/blog/depin_summit_recap/znzcollab.jpg
Normal file
|
After Width: | Height: | Size: 783 KiB |
|
Before Width: | Height: | Size: 1.0 MiB After Width: | Height: | Size: 268 KiB |
|
Before Width: | Height: | Size: 1.3 MiB After Width: | Height: | Size: 310 KiB |
|
Before Width: | Height: | Size: 500 KiB After Width: | Height: | Size: 197 KiB |
@@ -10,7 +10,6 @@ taxonomies:
|
||||
categories: [grid, tech]
|
||||
extra:
|
||||
imgPath: meeting_digital_demands1.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
*This article was originally published by Emilie Ouwerx, a former member of the ThreeFold team.*
|
||||
|
||||
|
Before Width: | Height: | Size: 829 KiB After Width: | Height: | Size: 222 KiB |
|
Before Width: | Height: | Size: 1.4 MiB After Width: | Height: | Size: 410 KiB |
|
Before Width: | Height: | Size: 884 KiB After Width: | Height: | Size: 276 KiB |
@@ -10,7 +10,7 @@ taxonomies:
|
||||
categories: [tech,community]
|
||||
extra:
|
||||
imgPath: evolution_of_the_internet1.png
|
||||
isFeatured: true
|
||||
isFeatured: false
|
||||
---
|
||||
|
||||
The internet has undergone a remarkable transformation since its inception in the 1960s. What started as a small, decentralized network designed for sharing knowledge and fostering collaboration has evolved into a vast, complex system that influences almost every aspect of modern life. However, this journey has been marked by significant shifts in the structure and nature of the internet, leading us to a critical juncture today.
|
||||
|
||||
|
Before Width: | Height: | Size: 1.5 MiB After Width: | Height: | Size: 381 KiB |
|
Before Width: | Height: | Size: 1021 KiB After Width: | Height: | Size: 294 KiB |
|
Before Width: | Height: | Size: 499 KiB After Width: | Height: | Size: 157 KiB |
|
Before Width: | Height: | Size: 1003 KiB After Width: | Height: | Size: 272 KiB |
@@ -40,7 +40,7 @@ It is challenging to use current Linux-based operating systems safely and effici
|
||||
|
||||
<br/>
|
||||
|
||||
[Zero OS](https://threefold.info/tech/tech/zos_innovation.html) is an innovative operating system, retaining the Linux kernel but fundamentally redesigned for heightened security, efficiency, and support for true peer-to-peer and decentralized workloads. This unique operating system doesn't require installation on hard disks or SSDs; it remains stateless, consistently up to date, and autonomously managed without human intervention. Its design enables scalability to millions of nodes and self-healing application delivery, opening new possibilities in system resilience and reliability.
|
||||
[Zero OS](https://manual.grid.tf/labs/knowledge_base/technology_toc/concepts_readme/zos) is an innovative operating system, retaining the Linux kernel but fundamentally redesigned for heightened security, efficiency, and support for true peer-to-peer and decentralized workloads. This unique operating system doesn't require installation on hard disks or SSDs; it remains stateless, consistently up to date, and autonomously managed without human intervention. Its design enables scalability to millions of nodes and self-healing application delivery, opening new possibilities in system resilience and reliability.
|
||||
|
||||
### **A quantum safe storage system**
|
||||
|
||||
@@ -52,7 +52,7 @@ Newer generation storage systems such as protocol-driven or blockchain-based sol
|
||||
|
||||
<br/>
|
||||
|
||||
[Quantum Safe Storage](https://threefold.info/tech/tech/zstor_innovation.html) is an ultra-scalable system capable of storing data indestructibly and efficiently. Previous versions of this system created by our team are widely used to store Zetabytes of information by large organizations.
|
||||
[Quantum Safe Storage](https://manual.grid.tf/labs/knowledge_base/technology_toc/qsss_home) is an ultra-scalable system capable of storing data indestructibly and efficiently. Previous versions of this system created by our team are widely used to store Zetabytes of information by large organizations.
|
||||
|
||||
### **A quantum safe network system**
|
||||
|
||||
@@ -60,7 +60,7 @@ The current centralized state of the internet poses significant security risks,
|
||||
|
||||
<br/>
|
||||
|
||||
[Mycelium](https://threefold.info/tech/tech/mycelium_inno.html) is an overlay network layer designed to enhance the existing internet infrastructure while remaining compatible with all current applications. It empowers true peer-to-peer communication. Mycelium can look for the shortest path, has a built-in naming and CDN (Content Delivery) system, and can survive disaster and network cuts much more efficiently as is possible today.
|
||||
[Mycelium](https://mycelium.threefold.io) is an overlay network layer designed to enhance the existing internet infrastructure while remaining compatible with all current applications. It empowers true peer-to-peer communication. Mycelium can look for the shortest path, has a built-in naming and CDN (Content Delivery) system, and can survive disaster and network cuts much more efficiently as is possible today.
|
||||
|
||||
### **The only way**
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 1.2 MiB After Width: | Height: | Size: 340 KiB |
|
Before Width: | Height: | Size: 633 KiB After Width: | Height: | Size: 292 KiB |
|
Before Width: | Height: | Size: 784 KiB After Width: | Height: | Size: 333 KiB |
|
Before Width: | Height: | Size: 666 KiB After Width: | Height: | Size: 186 KiB |
@@ -85,5 +85,4 @@ Dive in to learn more and how to get involved:
|
||||
<br/>
|
||||
|
||||
- [From the ground up: Three inventions that make ThreeFold possible](https://www.threefold.io/blog/ground-up-innovations/)
|
||||
- [The evolution of the Internet: From free to controlled, and back again](https://www.threefold.io/blog/eveloution-of-the-internet/)
|
||||
- [ThreeFold Docs: Litepaper, Tokenomics, Node Guide, & More](https://docs.threefold.io/)
|
||||
|
Before Width: | Height: | Size: 1.4 MiB After Width: | Height: | Size: 388 KiB |
62
content/blog/internet_origins/index.md
Normal file
@@ -0,0 +1,62 @@
|
||||
---
|
||||
id: internet_origins
|
||||
title: "An Internet That Remembers Its Origins"
|
||||
image_caption: An Internet That Remembers Its Origins
|
||||
description: The original vision is still alive. Now, we have the tools to realize it on a global scale.
|
||||
date: 2025-11-21
|
||||
taxonomies:
|
||||
people: [sam_taggart]
|
||||
tags: [grid,why,decentralization,cloud]
|
||||
categories: [grid,why,decentralization,cloud]
|
||||
extra:
|
||||
imgPath: internet_origins.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
Before today’s massive data centers and tightly controlled platforms, the early Internet felt more like a digital frontier than a ubiquitous part of the modern world. It was a living network built by curious engineers, tinkerers, hobbyists, universities – people plugging in a server, hosting a page, running an email service from bedrooms, garages, workspaces, and university basements. The network grew because individuals contributed capacity, creativity, and their intelligence. It was open and full of possibilities.
|
||||
|
||||
<br/>
|
||||
|
||||
Anyone could participate. Anyone could build. Anyone could host. People were free to own their digital lives instead of renting from cloud giants. That freedom was the Internet’s original superpower.
|
||||
|
||||
<br/>
|
||||
|
||||
Over time, as the web centralized into a handful of hyperscale clouds, we traded that grassroots openness for convenience. Infrastructure became something only giant companies could provide. The power shifted, the costs shifted, and the Internet’s early sense of shared ownership faded. And that early spirit of tinkering and autonomy was pushed to the margins.
|
||||
|
||||
<br/>
|
||||
|
||||
But it doesn’t have to stay in the past.
|
||||
|
||||
### **A Chance to Reclaim the Original Spirit of the Internet**
|
||||
|
||||
ThreeFold (and upcoming Project Mycelium, version 4 of the grid) taps into the idea that the Internet should be something we participate in, not just consume. Instead of relying on centralized cloud providers, the network is powered by individuals running small, efficient nodes that plug into a global, decentralized network. That means:
|
||||
|
||||
<br/>
|
||||
|
||||
1. **The power to run your own infrastructure (again)** <br/>
|
||||
No single company controls the grid. Just like the early days, anyone can plug in capacity and participate, returning ownership to the edges.
|
||||
|
||||
2. **The joy of tinkering – at modern scale** <br/>
|
||||
Set up a node, plug in capacity, experiment, build, break, fix, repeat. The hands-on creativity of the early Internet meets today’s possibilities.
|
||||
|
||||
3. **A community-powered digital commons** <br/>
|
||||
Each node strengthens the whole grid. Every contributor helps build a healthier, more neutral Internet, one owned by the people who run it.
|
||||
|
||||
4. **A privacy-first alternative to Big Cloud** <br/>
|
||||
Decentralized, energy-efficient, and secure. Your data stays yours, your infrastructure stays in your hands.
|
||||
|
||||
### **The Future Looks a Lot Like the Past (In a Good Way)**
|
||||
|
||||
ThreeFold isn’t about nostalgia. It’s about reviving what the early Internet got right: openness, decentralization, curiosity – and updating those values for a world now powered by AI, automation, and increasingly data-intensive workloads.
|
||||
|
||||
<br/>
|
||||
|
||||
It gives builders, tinkerers, privacy purists, and anyone uncomfortable with the way the Internet is going a path to reclaim agency in a world that desperately needs alternatives.
|
||||
|
||||
<br/>
|
||||
|
||||
The original vision is still alive. Now, we have the tools to realize it on a global scale.
|
||||
|
||||
<br/>
|
||||
|
||||
*With version 4 coming soon, we invite you to take a look at the opportunity [to participate](https://threefold.info/mycelium_economics/docs/hosting_economics/hosting_explanation) in the next phase of our project and ask questions either in our [main chat](https://t.me/threefold) or our [forum](https://forum.threefold.io).*
|
||||
BIN
content/blog/internet_origins/internet_origins.png
Normal file
|
After Width: | Height: | Size: 228 KiB |
|
Before Width: | Height: | Size: 1.4 MiB After Width: | Height: | Size: 400 KiB |
|
Before Width: | Height: | Size: 1.1 MiB After Width: | Height: | Size: 335 KiB |
142
content/blog/kubernetes_in_context/index.md
Normal file
@@ -0,0 +1,142 @@
|
||||
---
|
||||
id: kubernetes_in_context
|
||||
title: "Kubernetes in Context: Why the World Runs on K8s – and Why it Needs to Decentralized"
|
||||
image_caption: Kubernetes in Context
|
||||
description: Kubernetes has reshaped how the world builds and runs software but faces key challenges because of centralization. ThreeFold has a solution.
|
||||
date: 2025-09-10
|
||||
taxonomies:
|
||||
people: [raj_mitra]
|
||||
tags: [decentralization, grid, tech, cloud, why]
|
||||
categories: [decentralization, grid, tech, cloud, why]
|
||||
extra:
|
||||
imgPath: kubernetes_in_context.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
Kubernetes (aka K8S) has become the backbone of modern software. Teams use it to deploy, scale, and operate apps and platforms across clouds, data centers, and the edge, from banking to streaming to AI.
|
||||
|
||||
<br/>
|
||||
|
||||
However, despite its huge utility, most of Kubernetes still relies on centralized cloud providers, introducing issues like rising costs, vendor lock-in, and loss of control over data. The future demands a decentralized version.
|
||||
|
||||
<br/>
|
||||
|
||||
That’s exactly what our team is building with [KubeCloud](https://github.com/codescalers/kubecloud), a platform that brings Kubernetes to the decentralized ThreeFold Grid with simplicity, sovereignty, and scale.
|
||||
|
||||
### **So, What Exactly Does Kubernetes Do?**
|
||||
|
||||
At its core, Kubernetes helps teams run applications smoothly, no matter where they live, on laptops, in data centers, or in the cloud. It takes the heavy lifting out of day-to-day operations by automating what would otherwise be slow, error-prone, and manual:
|
||||
|
||||
<br/>
|
||||
|
||||
- **Tames complexity:** The main benefit is simplification. Kubernetes can simplify the chaos of microservices, making large, distributed systems manageable for multi-team organizations.
|
||||
- **Boosts reliability:** Built-in recovery, replication, and load balancing keep applications running with minimal downtime.
|
||||
- **Delivers consistency:** Standardizes deployment and operations across clouds, virtual machines, and bare metal. This makes sure that apps run the same everywhere.
|
||||
- **Automated deployment:** Roll out applications consistently across physical servers, virtual machines, and clouds without having to configure each by hand.
|
||||
- **Elastic scaling:** Add or remove capacity when demand spikes or shrinks, keeping performance steady while optimizing resources.
|
||||
- **Self-healing resilience:** Identifies system issues and resolves them automatically.
|
||||
- **Service discovery & load balancing:** Gives each connected app a fixed name and address so they can always find each other, while also spreading traffic out so nothing gets overloaded.
|
||||
- **Storage orchestration:** Works with many types of storage systems so apps can safely save their data and get it back whenever they need it.
|
||||
|
||||
<br/>
|
||||
|
||||
In short, Kubernetes takes the chaos out of running modern applications. That’s why it’s become the global standard.
|
||||
|
||||
### **Why the World Adopted K8s**
|
||||
|
||||
K8s didn’t become the de facto standard by accident. Kubernetes adoption was fueled by two converging technology shifts: the rise of containers and the rise of the cloud.
|
||||
|
||||
#### The Rise of Containers
|
||||
|
||||
Containers changed how software was built and shipped. These are lightweight “boxes” that package an app with everything it needs to run. They’re faster and more portable than traditional software setups. But once teams started running hundreds or thousands of containers, they needed a smart system to organize them. Kubernetes became that system.
|
||||
|
||||
#### The Rise of Cloud
|
||||
|
||||
Cloud computing redefined infrastructure. These platforms allow everyone to rent computing power instantly. However, every cloud worked a little differently. What was needed was a universal system that worked across providers. Kubernetes stepped up by becoming a unifying layer for hybrid and multi-cloud strategies.
|
||||
|
||||
<br/>
|
||||
|
||||
This combination made Kubernetes the go-to tool for modern infrastructure.
|
||||
|
||||
### **Limitations of the Centralized Kubernetes Model**
|
||||
|
||||
There is no doubt whatsoever about the practicality of traditional Kubernetes. As explained above, it has become the standard for running containerized applications. The issue, however, is that most clusters today live inside centralized cloud providers. This introduces several problems
|
||||
|
||||
<br/>
|
||||
|
||||
- **Vendor lock-in:** Dependence on a single provider limits flexibility and leverage.
|
||||
- **Rising costs:** Data-intensive workloads become expensive to run at scale.
|
||||
- **Reduced sovereignty:** Organizations have little control over where and how data is stored or processed.
|
||||
|
||||
<br/>
|
||||
|
||||
For developers, this means reduced flexibility. For enterprises, it means risk, especially when compliance, data privacy, or infrastructure resilience are on the line.
|
||||
|
||||
<br/>
|
||||
|
||||
A decentralized approach to Kubernetes can potentially address these gaps by distributing workloads across independent, globally available nodes, while still preserving the ease and power of cloud-native operations. In this decentralized environment, developers can enjoy the same features, without having to surrender control to hyperscale platforms.
|
||||
|
||||
<br/>
|
||||
|
||||
For AI and next-generation applications that demand both performance and sovereignty, decentralization is essential.
|
||||
|
||||
<br/>
|
||||
|
||||
This is where KubeCloud comes in.
|
||||
|
||||
### **KubeCloud: Decentralized Kubernetes on Steroids**
|
||||
|
||||
KubeCloud is designed to make decentralized Kubernetes both real and accessible. Instead of relying on centralized cloud providers, it provides clusters directly on the [ThreeFold Grid (TFGrid)](https://github.com/threefoldtech/tfgrid-sdk-go). The TFGrid is a decentralized, peer-to-peer cloud made up of independent capacity providers distributed worldwide. The Grid offers compute, storage, and networking resources contributed by individuals and organizations.
|
||||
|
||||
#### What Powers KubeCloud
|
||||
|
||||
Under the hood, KubeCloud integrates Mycelium. Mycelium forms an adaptive, encrypted mesh across TFGrid nodes, routing traffic securely and efficiently. Unlike traditional networking, which often depends on centralized ISPs and data centers, Mycelium self-heals and reroutes around failures, creating resilient connections between workloads no matter where they run.
|
||||
|
||||
<br/>
|
||||
|
||||
KubeCloud also supports multi-master clusters for high availability. Control plane nodes are distributed, and if one fails, the others automatically elect a new leader to keep the cluster running smoothly.
|
||||
|
||||
<br/>
|
||||
|
||||
Key capabilities include:
|
||||
|
||||
<br/>
|
||||
|
||||
- **Zero-downtime upgrades:** Apply updates without interrupting running workloads.
|
||||
- **Built-in failover:** Automatically recovers from node or service failures.
|
||||
- **Elastic scaling:** Expand or shrink services on demand to match workload needs.
|
||||
|
||||
<br/>
|
||||
|
||||
For observability, users can track cluster health through integrated Prometheus and Grafana dashboards. Exposing applications to the public internet is equally streamlined. A simplified web gateway replaces the usual complexity of ingress controllers with built-in domain and prefix-based routing.
|
||||
|
||||
### **What It Means for Users**
|
||||
|
||||
So, how does KubeCloud help users? Let’s take a look.
|
||||
|
||||
#### For Developers and DevOps
|
||||
|
||||
- Familiar workflows which includes declarative deployments, autoscaling, monitoring, logging, and collaboration workflows.
|
||||
- Runs in a decentralized environment, not a centralized vendor cloud
|
||||
- Users retain full control of compute, storage, and networking
|
||||
|
||||
#### For Enterprises
|
||||
|
||||
- Production-grade Kubernetes, without lock-in. Run clusters confidently, free from dependence on a single vendor.
|
||||
- Made for data-heavy teams. Tap into next-gen hardware on the ThreeFold Grid, built for AI and high-performance workloads.
|
||||
|
||||
### **In Closing**
|
||||
|
||||
Kubernetes has reshaped how the world builds and runs software. By automating deployment, scaling, and recovery. Yet, as powerful as Kubernetes is, most of its deployments still run on centralized clouds, bringing challenges of lock-in, cost, and sovereignty. That is why the next leap is decentralization.
|
||||
|
||||
<br/>
|
||||
|
||||
KubeCloud combines the familiarity of Kubernetes with the resilience and sovereignty of decentralized infra. It takes the power of the TFGrid and Mycelium and packages it into a platform that anyone can adopt with minimal onboarding friction.
|
||||
|
||||
<br/>
|
||||
|
||||
Kubernetes changed the world once. By leveraging decentralization and ThreeFold, KubeCloud may do so again.
|
||||
|
||||
<br/>
|
||||
|
||||
*Join [our Telegram](https://t.me/threefold) and stay up to date with the latest developments on ThreeFold.*
|
||||
BIN
content/blog/kubernetes_in_context/kubernetes_in_context.png
Normal file
|
After Width: | Height: | Size: 907 KiB |
|
Before Width: | Height: | Size: 704 KiB After Width: | Height: | Size: 289 KiB |
|
Before Width: | Height: | Size: 1.2 MiB After Width: | Height: | Size: 264 KiB |
|
Before Width: | Height: | Size: 934 KiB After Width: | Height: | Size: 256 KiB |
|
Before Width: | Height: | Size: 870 KiB After Width: | Height: | Size: 220 KiB |
BIN
content/blog/quantum_safe_storage/QSS_blog.png
Normal file
|
After Width: | Height: | Size: 351 KiB |
233
content/blog/quantum_safe_storage/index.md
Normal file
@@ -0,0 +1,233 @@
|
||||
---
|
||||
id: QSS
|
||||
title: "The Quantum Age Is Coming: Will Your Data Survive?"
|
||||
image_caption: QSS
|
||||
description: The quantum era is approaching fast, threatening encryption, blockchains, and security. ThreeFold’s Quantum Safe Storage delivers sovereign, resilient, and unbreakable protection for data in a post-quantum world.
|
||||
date: 2025-09-16
|
||||
taxonomies:
|
||||
people: [raj_mitra]
|
||||
tags: [tech,grid,community]
|
||||
categories: [tech,grid,community]
|
||||
extra:
|
||||
imgPath: QSS_blog.png
|
||||
---
|
||||
|
||||
The world is standing at the edge of a technological revolution. Quantum computing, once confined to theoretical discussions in labs, has begun breaking into reality. With advancements like [Google Willow](https://blog.google/technology/research/google-willow-quantum-chip/) and the race towards more powerful machines, quantum computers are an approaching storm, and most of us are not even close to being ready.
|
||||
|
||||
### The Quantum Threat to Security
|
||||
For decades, the bedrock of digital trust has been cryptography. Public-key encryption (RSA, ECC), digital signatures, and hashing algorithms are what secure our bank accounts, blockchain transactions, confidential files, and online identities.
|
||||
|
||||
<br/>
|
||||
|
||||
But here’s the problem: quantum computers are tailor-made to break these very defenses. [Shor’s algorithm](https://en.wikipedia.org/wiki/Shor%27s_algorithm) allows quantum systems to factor large numbers and break asymmetric encryption at a speed classical computers could never match. Once a quantum machine with sufficient qubits (the basic unit of information used to encode data in quantum computing) and error correction is operational, today’s standard cryptography becomes obsolete.
|
||||
|
||||
<br/>
|
||||
|
||||
This danger unfolds in multiple ways:
|
||||
|
||||
- **Harvest-now, decrypt-later:** Encrypted data stolen today can be stored and easily decrypted by quantum machines in the future.
|
||||
- **Compromised blockchains:** Bitcoin, Ethereum, and other cryptocurrencies are secured by vulnerable cryptography. A sufficiently advanced quantum computer could forge transactions or drain wallets.
|
||||
- **Broken trust in communications:** VPNs, HTTPS, and secure messaging would be exposed, jeopardizing global internet security.
|
||||
- **Critical infrastructure risk:** Power grids, defense systems, and financial networks could all be destabilized by quantum attacks.
|
||||
|
||||
<br/>
|
||||
|
||||
In short, quantum computing threatens the very assumption of “safety” on which the digital world has been built.
|
||||
|
||||
<br/>
|
||||
|
||||
For businesses, governments, and individuals alike, this presents both unparalleled opportunity and unprecedented danger.
|
||||
|
||||
#### Why Existing Systems Can’t Adapt Quickly
|
||||
Crypto networks, cloud providers, and enterprises face a brutal truth. It is absolutely critical for them to get quantum-safe.
|
||||
|
||||
<br/>
|
||||
|
||||
For blockchains, transitioning means changing the very essence of their algorithms, requiring contentious hard forks that could split communities and collapse valuations.
|
||||
|
||||
<br/>
|
||||
|
||||
For cloud storage providers, petabytes of vulnerable data are already locked in centralized infrastructures, making retrofitting costly and slow.
|
||||
|
||||
<br/>
|
||||
|
||||
For governments and enterprises, complacency is the biggest risk, assuming quantum is “decades away” when in reality, technological breakthroughs are accelerating faster than anyone expected.
|
||||
|
||||
<br/>
|
||||
|
||||
What’s needed isn’t retrofitting. It’s rethinking.
|
||||
|
||||
|
||||
### Enter ThreeFold’s Quantum Safe Storage (QSS)
|
||||
Zero-OS provides several core storage primitives like disks, volumes, and 0-DB. Quantum Safe Storage is constructed on top of these primitives, adding the encryption, encoding, and dispersion mechanisms that deliver a storage layer that is unbreakable, sovereign, and efficient.
|
||||
|
||||
<br/>
|
||||
|
||||
[QSS](https://manual.grid.tf/labs/knowledge_base/technology_toc/qsss_home/) is the productized form of Zero-OS storage, designed specifically for the quantum age. QSS packages its core advantages into a clear value proposition:
|
||||
|
||||
- **Quantum-Resistant Security:** Mathematically encoded fragments and post-quantum cryptography protect against future quantum attacks.
|
||||
- **Immutable & Append-Only:** Data can’t be altered or erased, ensuring integrity forever.
|
||||
- **Self-Healing:** Automatic detection and reconstruction of lost or corrupted fragments.
|
||||
- **Sovereign & Compliant:** Data placement can be controlled geographically for governance and compliance.
|
||||
- **Efficient:** Achieves redundancy with only ~20% overhead, compared to 400%+ for replication systems.
|
||||
|
||||
### The QSS Storage Stack
|
||||
The storage stack is made up of three core layers:
|
||||
|
||||
- **ZDBFS (Zero-DB FS):** A filesystem abstraction layer that makes the system accessible to applications, developers, and end-users.
|
||||
- **ZSTOR (Zero-Stor):** The encoding, encryption, and distribution engine that applies error-correcting codes and disperses fragments.
|
||||
- **ZDB (Zero-DB):** The append-only, immutable storage daemon that directly interfaces with physical drives.
|
||||
|
||||
#### #1 ZDBFS (Zero-DB FS)
|
||||
At the surface, Zero-OS offers the ZBDFS. In this layer, users and applications can interact with each other. To the user, ZBDFS feels like a familiar mounted filesystem. Beneath the surface, every action taken is translated into operations that the deeper architecture understands.
|
||||
|
||||
<br/>
|
||||
|
||||
When applications interact with ZDBFS, it passes those instructions down to ZSTOR, which performs the real work of encoding, encryption, and dispersal. On retrieval, ZBDFS orchestrates the reverse process, seamlessly reconstructing files from distributed fragments.
|
||||
|
||||
<br/>
|
||||
|
||||
The filesystem itself is robust at scale:
|
||||
|
||||
- It can hold petabytes of data
|
||||
- Manage up to two million files per instance
|
||||
- Transfer at speeds of 100 MB/s
|
||||
- It is optimized for larger objects.
|
||||
|
||||
<br/>
|
||||
|
||||
Metadata is redundantly maintained with configurable consistency, typically within a fifteen-minute window, ensuring durability without compromise.
|
||||
|
||||
#### #2 Zero-Stor (ZSTOR)
|
||||
In ZSTOR, raw input becomes mathematically encoded resilience. When data enters ZSTOR it goes through the following stages:
|
||||
|
||||
- The data is compressed to conserve space, then encrypted with user-defined keys
|
||||
- Forward error correction transforms it into fragments redundant yet efficient equations that can survive node failures without loss.
|
||||
- These fragments are distributed across multiple Zero-DB backends, with metadata carefully managed to map locations, redundancy, and integrity.
|
||||
|
||||
<br/>
|
||||
|
||||
ZSTOR also watches over data. A built-in monitoring layer continuously checks the health of every connected device, automatically rebuilding missing fragments if one goes dark. ZSTOR can even synchronize across clusters in real time, ensuring redundancy and failover across geographies.
|
||||
|
||||
#### #3 Zero-DB (ZDB)
|
||||
Unlike conventional storage engines, ZDB is designed for simplicity. It is append-only by default. New data is added sequentially, references update to the latest version, and old data remains as history. Mutation or deletion requires a compaction process, which is possible but not part of normal operation.
|
||||
|
||||
<br/>
|
||||
|
||||
ZDB is a general-purpose data store. It can hold entire unencrypted objects or the fragmented shards used by ZBDFS, and the engine itself remains indifferent to the content.
|
||||
|
||||
### Scalability in QSS
|
||||
QSS is built to scale outward, not upward. Each use case runs on its own dedicated instance of ZBDFS and ZSTOR, which connect to a constellation of ZDBs spread across the grid. A typical configuration uses around twenty or more, but the exact number is configurable by the user.
|
||||
|
||||
<br/>
|
||||
|
||||
These components can be distributed across geographies, giving the system reach without sacrificing integrity.
|
||||
|
||||
<br/>
|
||||
|
||||
There is no ceiling here. The architecture can support an unlimited number of ZBDFS and ZSTOR instances, each operating independently yet harmoniously. Since data is always processed and consumed at the place of its creation, latency is minimized and sovereignty preserved.
|
||||
|
||||
<br/>
|
||||
|
||||
The result is a storage fabric that grows horizontally, node by node, instead of demanding ever more powerful centralized machines.
|
||||
|
||||
### The Maths Behind QSS
|
||||
Replication is the crutch of conventional storage. QSS leaves it behind. A file, once ingested, is broken into sixteen fragments. From those fragments, twenty equations are born. Any sixteen of those equations can rebuild the whole. Four nodes may vanish from the network, and the data remains untouched, its integrity intact.
|
||||
|
||||
<br/>
|
||||
|
||||
Where traditional systems bloat themselves with 400% overhead just to promise redundancy, QSS achieves it with only 20%.
|
||||
|
||||
<br/>
|
||||
|
||||
**Example Implementation**
|
||||
|
||||
Imagine a piece of data split into three fragments with values:
|
||||
|
||||
- a = 1
|
||||
- b = 2
|
||||
- c = 3
|
||||
|
||||
Instead of storing these fragments directly, the system encodes them as equations:
|
||||
|
||||
- a + b + c = 6
|
||||
- c − b − a = 0
|
||||
- b − c + a = 0
|
||||
- 2b + a − c = 2
|
||||
- 5c − b − a = 12
|
||||
- …and more.
|
||||
|
||||
<br/>
|
||||
|
||||
At first glance this looks like overkill: why so many equations for just three unknowns?
|
||||
|
||||
<br/>
|
||||
|
||||
Here’s the math behind it:
|
||||
|
||||
<br/>
|
||||
|
||||
In a system with three variables (a, b, c), only three linearly independent equations are needed to uniquely recover them.
|
||||
|
||||
<br/>
|
||||
|
||||
Any set of more than three equations will be linearly dependent—they don’t add new information but can be expressed as combinations of the others.
|
||||
|
||||
<br/>
|
||||
|
||||
From a storage perspective, that means only three equations are strictly necessary.
|
||||
|
||||
<br/>
|
||||
|
||||
So why generate extra equations? For resilience. If some equations are lost or corrupted, the system can still pick any valid set of three independent ones and reconstruct the original fragments. This redundancy ensures the data remains recoverable even under failure.
|
||||
|
||||
<br/>
|
||||
|
||||
In production, the model scales. A typical configuration splits each object into sixteen fragments, then produces twenty equations, each stored on a separate device. To rebuild the data, only sixteen of the twenty are required. The system can lose four entire nodes and still recover the file without corruption.
|
||||
|
||||
<br/>
|
||||
|
||||
This mathematical method achieves redundancy with just 20% overhead, compared to the 400% overhead demanded by traditional replication systems.
|
||||
|
||||
### Deploy Quantum Safe Storage
|
||||
The [Quantum Daemon](https://github.com/threefoldtech/quantum-storage/blob/master/quantumd/README.md) is designed to manage all aspects of QSS that don’t fit neatly into the roles of the core components. Its goal is to simplify deployment, operation, and recovery of QSS into a single binary with a single config file.
|
||||
|
||||
#### Responsibilities
|
||||
The daemon takes care of:
|
||||
|
||||
- **Backend deployment:** Initial deployment of backend zdbs and replacement of failed backends during operation.
|
||||
- **Service management:** Installation of all required binaries and creation of system services (supports both systemd and zinit).
|
||||
- **Event handling:** Processing hook events from zdb (replacing legacy shell scripts).
|
||||
- **Data integrity:** Running checks and retries for failed uploads.
|
||||
- **Config management:** Providing a single central config file for end users (QSS component configs and CLI args are generated automatically).
|
||||
- **Recovery:** Automated restoration of QSS onto a new machine in case of frontend failure.
|
||||
- **Simplified operation:** One binary and one config file can bring up the whole system.
|
||||
|
||||
#### Usage
|
||||
A subset of functionality is already implemented, with heavy changes expected as the project evolves. Today, QSS can already be deployed with quantumd using either local or remote backends.
|
||||
|
||||
- Local backends are useful for testing, and can be spun up quickly with a single command.
|
||||
- Remote backends are used for real deployments, requiring a TFChain account and configuration details.
|
||||
- Daemon mode handles retries, hooks, and caching in the background once set up.
|
||||
|
||||
For step-by-step installation and deployment instructions, [see the official deployment guide](https://github.com/threefoldtech/quantum-storage/blob/master/docs/03_deployment.md).
|
||||
|
||||
### Comparing QSS With Traditional Storage Solutions
|
||||
|
||||
Here is a comparison between QSS and traditional storage to show how it outperforms conventional systems.
|
||||
|
||||
<br/>
|
||||
|
||||
| | **QSS** | **Traditional Storage Solutions** |
|
||||
| --- | --- | --- |
|
||||
| **Scalability** | Horizontally scalable architecture with no theoretical size limitations | Variable scalability |
|
||||
| **Compatibility** | High compatibility through the abstraction layer | Varies by implementation |
|
||||
| **Performance** | Optimized for reliability | Variable performance characteristics |
|
||||
| **Redundancy Efficiency** | With a 16–20 node setup, QSS achieves 4-node failure tolerance with only ~20% overhead. The overhead changes depending on the cluster size. This flexibility means QSS can be tuned to balance redundancy and efficiency for different deployment needs. | Typically 400-500% overhead (4-5 complete copies) for equivalent redundancy |
|
||||
| **Compute Integration** | Integrated with Infrastructure-as-Code tooling | Diverse integration approaches with varying complexity |
|
||||
| **Geographic Control** | User-controlled data placement with geographic autonomy | Limited geographic control due to centralized routing |
|
||||
| **Security Architecture** | Implements mathematical encoding and encryption | Conventional encryption models |
|
||||
| **Post-Quantum Readiness** | Implements post-quantum cryptographic algorithms | Not designed with quantum resistance |
|
||||
|
||||
### In Closing
|
||||
ZDBFS, ZSTOR, and ZDB form a storage stack that balances performance, sovereignty, and quantum resistance. Whether deployed for simple file storage, global applications, or blockchain-grade data integrity, QSS empowers organizations, developers, and individuals alike to move beyond the vulnerabilities of conventional storage and embrace a future where security, resilience, and sovereignty go hand in hand.
|
||||
@@ -10,6 +10,7 @@ taxonomies:
|
||||
categories: [decentralization, grid, tech]
|
||||
extra:
|
||||
imgPath: reclaiming_the_internet.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
In a world where access to the internet is increasingly mediated by tech giants, ThreeFold is delivering on what Web3 promised but has not delivered: a truly user-owned, peer-to-peer internet. Instead of building on someone else’s servers, ThreeFold started from the ground up with infrastructure, compute, storage, and network – to make the internet what it was supposed to be. Open. Resilient. Owned by the people.
|
||||
|
||||
|
Before Width: | Height: | Size: 982 KiB After Width: | Height: | Size: 220 KiB |
|
Before Width: | Height: | Size: 512 KiB After Width: | Height: | Size: 155 KiB |
|
Before Width: | Height: | Size: 934 KiB After Width: | Height: | Size: 248 KiB |
@@ -10,7 +10,7 @@ taxonomies:
|
||||
categories: [community, decentralization, farming, grid, cloud]
|
||||
extra:
|
||||
imgPath: roadmap_to_web4.png
|
||||
isFeatured: true
|
||||
isFeatured: false
|
||||
---
|
||||
|
||||
### **Part I: A Natural Evolution**
|
||||
@@ -80,11 +80,11 @@ Today, we are pleased to announce the next step in the roadmap to Web4: V4 3Node
|
||||
|
||||
<br>
|
||||
|
||||
**3Nodes** are a familiar concept in the ThreeFold ecosystem, now also entering their fourth generation. Nodes provide capacity to the network, and in exchange generate rewards. Today, in collaboration with ThreeFold community vendors HostServiceNL in Europe and DuckFarmData in North America, we are announcing three different models of the V4 3Node. You can find more info and how to place orders [here](https://docs.threefold.io/docs/become-a-farmer/get_started).
|
||||
**3Nodes** are a familiar concept in the ThreeFold ecosystem, now also entering their fourth generation. Nodes provide capacity to the network, and in exchange generate rewards. Today, in collaboration with ThreeFold community vendors YourData Network in Europe and DuckFarmData in North America, we are announcing three different models of the V4 3Node. You can find more info and how to place orders [here](https://docs.threefold.io/docs/become-a-farmer/get_started).
|
||||
|
||||
<br>
|
||||
|
||||
**[3Phones](https://docs.threefold.io/docs/components/3phone)** are a portal into the Web4 world. We are pleased to share that we will be offering several models of 3Phones into the market based on the [Volla Phone](https://volla.online/en/) platform. 3Phones will be equipped with your own decentralized AI agent called **[3Bot](https://docs.threefold.io/docs/components/3bot)**. You can pre-order a 3Phone [here](https://threefold.io/signup).
|
||||
**[3Phones](https://docs.threefold.io/docs/components/3phone)** are a portal into the Web4 world. We are pleased to share that we will be offering several models of 3Phones into the market based on the [Volla Phone](https://volla.online/en/) platform. 3Phones will be equipped with your own decentralized AI agent called **3Bot**. You can pre-order a 3Phone [here](https://threefold.io/signup).
|
||||
|
||||
<br>
|
||||
|
||||
@@ -92,7 +92,7 @@ And then there are **[3Routers](https://docs.threefold.io/docs/components/3route
|
||||
|
||||
<br>
|
||||
|
||||
<iframe width="896" height="504" src="https://www.youtube.com/embed/Z3TRrwxOIz0?si=fCnX1D1uHnU4k411" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
|
||||
<iframe width="866" height="487" src="https://www.youtube.com/embed/Z3TRrwxOIz0?si=fCnX1D1uHnU4k411" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 571 KiB After Width: | Height: | Size: 140 KiB |
|
Before Width: | Height: | Size: 981 KiB After Width: | Height: | Size: 229 KiB |
|
Before Width: | Height: | Size: 1.2 MiB After Width: | Height: | Size: 275 KiB |
82
content/blog/tf_decentralized_cloud_new/index.md
Normal file
@@ -0,0 +1,82 @@
|
||||
---
|
||||
id: tf_decentralized_cloud_new
|
||||
title: "How ThreeFold's Decentralized Cloud Empowers Builders – and End Users"
|
||||
image_caption: technology
|
||||
description: ThreeFold isn’t just a vision for the future. It’s a functioning, decentralized infrastructure already in production.
|
||||
date: 2025-10-08
|
||||
taxonomies:
|
||||
people: [raj_mitra]
|
||||
tags: [tech,cloud,community]
|
||||
categories: [tech,cloud,community]
|
||||
extra:
|
||||
imgPath: tf_decentralized_cloud_new.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
A network of decentralized nodes around the world contribute compute, storage, and network capacity to the ThreeFold Grid, powering live workloads for developers and independent projects. This isn’t a vision for the future. It’s a functioning, decentralized infrastructure already in production.
|
||||
|
||||
<br/>
|
||||
|
||||
While the ThreeFold team pushes forward on our own flagship commercial initiatives, builders are already commercializing the grid’s resources with consumer and enterprise products on top. Together, it’s forming an ecosystem where the infrastructure, builders, and users all reinforce one another.
|
||||
|
||||
#### The Grid: The Foundation
|
||||
At its core is the ThreeFold Grid, a global network of independently operated nodes. These nodes are run by “farmers,” aka individuals and organizations that contribute resources and are rewarded for making reliable resources available. Unlike hyperscalers, there is no central owner controlling pricing, access, or usage. Anyone can contribute hardware, anyone can consume capacity.
|
||||
|
||||
<br/>
|
||||
|
||||
From a [technical perspective](https://manual.grid.tf/labs/knowledge_base/technology_toc/grid3_howitworks), the grid offers the primitives developers need to run modern workloads: Linux VMs, private networking, IPv4/IPv6 routing, and the ability to deploy and manage infrastructure.
|
||||
|
||||
<br/>
|
||||
|
||||
A key challenge in decentralized hosting has always been network access, especially scarce and expensive IPv4 addresses. The grid solves this with smart gateway models, such as the Web gateway that turn ThreeFold nodes with public IPv4 addresses into reverse proxies, making any workload accessible from the internet, even if it runs on a node without a public IP.
|
||||
|
||||
<br/>
|
||||
|
||||
Farmers can offer gateway services using their own IPv4 addresses, so users can deploy anywhere on the grid without complex networking. This way, small operators can deploy apps without buying lots of expensive IPs.
|
||||
|
||||
<br/>
|
||||
|
||||
Gateways can also bridge Mycelium with the traditional web. Mycelium is a decentralized, end-to-end encrypted network built on the ThreeFold base layer. Developers building directly on Mycelium can often skip IPv4 gateways entirely.
|
||||
|
||||
#### The Builders: Turning Infrastructure into Products
|
||||
Above the raw grid sits a growing layer of builders and companies who package its primitives into usable, commercial-grade products.
|
||||
|
||||
<br/>
|
||||
|
||||
As concrete examples, we have [YourData Network](https://yourdata.network/), a seller of hardware and software, and [Shiloh Code](https://shilohcode.com/), experts in privacy and managed services, that both leverage the grid in their own ways. We also have interesting experiments like this [Ukrainian underground radio](https://github.com/threefoldtech/mycelium/discussions/670) which can safely run using the Mycelium network without worrying about centralized censorship.
|
||||
|
||||
<br/>
|
||||
|
||||
Independent developers are also using the grid to offer hosting and app gateways. A recent project showed that a single person could set up a reliable front door for many apps in just a few evenings – something that would normally require a lot more time and expensive infrastructure. [This gateway experiment](https://github.com/mik-tf/tfgrid-gateway) helps work around the current limits of decentralized hosting, such as IPv4 scarcity and the fact that many nodes run in residential settings without direct inbound access.
|
||||
|
||||
<br/>
|
||||
|
||||
Each of these efforts turns the raw ThreeFold Grid into accessible, commercial-grade services, without the specific need of a central rollout.
|
||||
|
||||
<br/>
|
||||
|
||||
This builder layer is critical and serves a clear purpose: by abstracting away the complexity of the grid, it makes it possible for end-users to access apps and services running on the grid through easy to use builders’ products.
|
||||
|
||||
#### The Users: Plugging Into Decentralization
|
||||
At the top of the stack are the end users, people and small teams who want to use products without running servers themselves. Thanks to the builder layer, there are already products and services offered on the internet that run on the grid, making it possible to benefit from a decentralized backbone without managing the infrastructure.
|
||||
|
||||
<br/>
|
||||
|
||||
They do not need to know how the network works. They simply use products like a hosted drive, a secure gateway or a custom web service that runs on a decentralized backbone. For them it feels as easy as a normal cloud, but without lock-in, tracking or sudden price changes.
|
||||
|
||||
#### Why This Matters Now
|
||||
This is no longer just a vision. It’s a functioning ecosystem where people are building and deploying. The technology is ready for production. Compute, storage and networking primitives are live, open source and easy to automate with modern tools.
|
||||
|
||||
<br/>
|
||||
|
||||
If you’re a developer or small company wanting to launch a product in a secure, decentralized environment, this is it. Here is what you should do:
|
||||
|
||||
<br/>
|
||||
|
||||
- Explore the [ThreeFold Grid](https://dashboard.grid.tf/#/)
|
||||
- Read through [our manual](https://manual.grid.tf/)
|
||||
- Join the [forum](https://forum.threefold.io/)
|
||||
|
||||
<br/>
|
||||
|
||||
The future of the internet isn’t coming – it’s already running. ThreeFold is ready for adoption.
|
||||
|
After Width: | Height: | Size: 337 KiB |
@@ -70,7 +70,7 @@ There are many ways to get involved:
|
||||
|
||||
- Join our [main chat](https://t.me/threefold), talk to humans
|
||||
- [Learn](https://manual.grid.tf/) about expanding the grid or deploying on top of it
|
||||
- [Buy and hold](https://manual.grid.tf/documentation/threefold_token/buy_sell_tft/buy_sell_tft.html) the token to provide fuel to the ecosystem
|
||||
- [Buy and hold](https://manual.grid.tf/users/buy-tft) the token to provide fuel to the ecosystem
|
||||
- [Stay tuned](https://t.me/threefoldnews) for news, updates, and community calls
|
||||
- Take part in the [feedback](https://forum.threefold.io/t/feedback-on-our-tfgrid-3-14/4276) about the next steps for ThreeFold
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 1.2 MiB After Width: | Height: | Size: 408 KiB |
|
Before Width: | Height: | Size: 1.0 MiB After Width: | Height: | Size: 268 KiB |
@@ -40,7 +40,7 @@ ThreeFold Farmers not only provide capacity but also take the opportunity of Thr
|
||||
|
||||
</br>
|
||||
|
||||
The ThreeFold farming community is an integral part of our [decentralized autonomous organization (DAO)](https://manual.grid.tf/documentation/dashboard/tfchain/tf_dao.html). A farmer's participation in the DAO discussions and proposals is pivotal as we chart the course for the grid's evolution, from our current version 3.14 release and beyond. Together, we're actively building the grid's future, thanks to our dedicated farmers' collaborative efforts. Join us, share your ideas, and let's shape the future of the ThreeFold Grid together.
|
||||
The ThreeFold farming community is an integral part of our decentralized autonomous organization (DAO). A farmer's participation in the DAO discussions and proposals is pivotal as we chart the course for the grid's evolution, from our current version 3.14 release and beyond. Together, we're actively building the grid's future, thanks to our dedicated farmers' collaborative efforts. Join us, share your ideas, and let's shape the future of the ThreeFold Grid together.
|
||||
|
||||
### **The Future of the Farming Community**
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 1.0 MiB After Width: | Height: | Size: 297 KiB |
|
Before Width: | Height: | Size: 556 KiB After Width: | Height: | Size: 223 KiB |
|
Before Width: | Height: | Size: 1.6 MiB After Width: | Height: | Size: 420 KiB |
|
Before Width: | Height: | Size: 501 KiB After Width: | Height: | Size: 127 KiB |
|
Before Width: | Height: | Size: 622 KiB After Width: | Height: | Size: 197 KiB |
@@ -10,7 +10,7 @@ taxonomies:
|
||||
categories: [decentralization, grid, cloud, tech]
|
||||
extra:
|
||||
imgPath: building_blocks_internet1.png
|
||||
isFeatured: true
|
||||
isFeatured: false
|
||||
---
|
||||
|
||||
*This article was originally published by Emilie Ouwerx, a former member of the ThreeFold team.*
|
||||
|
||||
@@ -10,7 +10,6 @@ taxonomies:
|
||||
categories: [community, decentralization]
|
||||
extra:
|
||||
imgPath: decentralized_governance.png
|
||||
isFeatured: true
|
||||
---
|
||||
|
||||
In the next phase of ThreeFold, we are focused on utilization and commercialization. With this comes a requirement for our project to establish reliable and trusted systems that allow anyone to enter the ecosystem with confidence.
|
||||
|
||||
|
Before Width: | Height: | Size: 525 KiB After Width: | Height: | Size: 140 KiB |