This commit is contained in:
2024-05-02 08:28:43 +02:00
parent 46912722d1
commit 28f366cb14
43 changed files with 381 additions and 108 deletions

View File

@@ -1,48 +1,26 @@
<h1>All Trust</h1>
![](img/alltrust.png)
<h2>Table of Contents</h2>
<h1>All Trust</h1>
- [A Paradigm of Trust](#a-paradigm-of-trust)
- [Farmers: Investors in Shared Infrastructure](#farmers-investors-in-shared-infrastructure)
- [Grid Services: Facilitating System Usage](#grid-services-facilitating-system-usage)
- [Flexible Pricing Policies](#flexible-pricing-policies)
- [IOUs Enable Trusted Transactions](#ious-enable-trusted-transactions)
- [Guardian Circles: Humans Ensuring Oversight](#guardian-circles-humans-ensuring-oversight)
- [Summary](#summary)
- [Everyone can be a Service Provider / Merchant](#everyone-can-be-a-service-provider--merchant)
- [IOUs Enable Trusted Transactions = mutual credit](#ious-enable-trusted-transactions--mutual-credit)
- [Farmers: Investors in Shared Internet/Cloud Infrastructure](#farmers-investors-in-shared-internetcloud-infrastructure)
- [Shared Internet, Network \& AI Services](#shared-internet-network--ai-services)
***
## A Paradigm of Trust
What if instead of distrusting others, we embrace a paradigm of trust? The *TFGRID 4.0 system is built on this principle of trust between all participants.
What if instead of distrusting others, we embrace a paradigm of trust?
The TFGrid 4.0 comprises different actors, each represented by a 3bot digital assistant. 3bots enable automated interactions between farmers, service providers, and consumers.
Our system is built on this principle of trust between all participants.
## Farmers: Investors in Shared Infrastructure
Each actor is represented by a digital assistant (based on our Hero) who helps us to organize our collaboration, e-commerce flows, system administration tasks, ...
- Farmers invest in hardware capacity like TFNodes or OurVerse-based services (web gateways, 5G, etc). Their investments fund the grid infrastructure.
- Farmers can choose to actively manage their infrastructure using their 3bot. Or they can join a Farming Cooperative to simplify operations.
- Either way, farmers earn profits when people purchase and utilize the infrastructure capacity they invested in. Their 3bots handle billing, monitoring, support issues, etc.
## Grid Services: Facilitating System Usage
- Hundreds of different grid services can exist, from storage and compute to telecom and networking.
- These services track usage metrics like bandwidth, storage consumption, RPC requests, etc. Usage data is reported transparently to the relevant farming 3bot.
- Consumers can interact directly with any service via the OurVerse message bus. Services deploy workloads, fulfill requests, provide monitoring, etc as needed.
## Flexible Pricing Policies
- Farming 3bots define customized pricing policies for their services based on usage. Costs may vary based on compute time, storage quantities, bandwidth, etc.
- Pricing flexibility creates an open market. Farmers can price based on costs and desired profit margins. Consumers can shop for services based on performance, reliability, location, and price.
## IOUs Enable Trusted Transactions
- IOUs (I Owe You) represent agreements between farmers and consumers for grid usage.
- Both parties digitally sign each IOU, ensuring consensus on the transaction details.
- At regular intervals, farmers submit IOUs to the OurVerse Pay Bridge operated by a Guardian Circle. This aggregates IOUs and requests payment from the consumer 3bots.
- Reputations are maintained on the blockchain to identify any bad actors abusing the system. But fundamentally, the system relies on trust between participants.
A Human chain rather than a Blockchain has the capability to build/maintain a good governance system.
## Guardian Circles: Humans Ensuring Oversight
@@ -51,6 +29,34 @@ The TFGrid 4.0 comprises different actors, each represented by a 3bot digital as
- Their flexibility allows customization by each grid community based on local needs.
- Circles leverage tools like multisig wallets, OurVerse consensus, and VLang DSLs to codify logic while retaining human checks and balances.
## Summary
In summary, *TFGRID 4.0 demonstrates that with the right incentives and oversight, we can build shared digital ecosystems founded on trust and collaboration.
## Everyone can be a Service Provider / Merchant
- Farmers define their own pricing policies for their services based on usage. Costs may vary based on compute time, storage quantities, bandwidth, etc.
- Pricing flexibility creates an open market. Farmers can price based on costs and desired profit margins. Consumers can shop for services based on performance, reliability, location, and price.
## IOUs Enable Trusted Transactions = mutual credit
- IOUs (I Owe You) represent agreements between farmers and consumers or for any other Internet / Hero Service
- Both parties digitally sign each IOU, ensuring consensus on the transaction details.
- At regular intervals, farmers submit IOUs to the Payment Bridges which are typically operated in a Digital Freezone. This aggregates IOUs and requests payment from the Hero's who represent the buyers.
- Reputations are maintained on a decentralized ledfer to identify any bad actors abusing the system.
- **Fundamentally, the system relies on trust between participants.**
## Farmers: Investors in Shared Internet/Cloud Infrastructure
- Farmers invest in hardware capacity for the Internet and Cloud (web gateways, 5G, etc). This capacity can be used for cloud workloads, AI, web2, web3 or hosting Hero's of project mycelium
- Smaller farmers join a Farming Cooperative which helps with the commercial and operational duties if needed.
- Farmers earn rewards when people purchase and utilize the infrastructure capacity they invested in. Their autonomous agents (hero) handle billing, monitoring, support issues, etc.
## Shared Internet, Network & AI Services
- People can collaborate (through their Hero's) to deploy shared services
- Each of those services is co-owned by groups of people and managed through a circular governance system
- Some examples
- AI Neural networks / Language Models
- Internet Connectivity Services
- Index & Search of Internet Content
- Oracles for pricing, weather, ...
- ...

View File

@@ -1,7 +1,7 @@
A Cloud, Storage or AI Box is a part of a server/computer (3Node) which delivers a service which has well defined properties in relation to capacity, pricing, serviceabity, capabilities.
A Cloud, Storage or AI Box is a part of a server/computer (TF or INCA Node) which delivers a service which has well defined properties in relation to capacity, pricing, serviceabity, capabilities.
These Cloud, Storage or AI Boxes can be bought by the INCA/TF Community through the INCA marketplace.
The boxes are hosted on 3Nodes.

View File

@@ -1,5 +1,13 @@
# CloudBox Concepts
<h2>Table of Contents</h2>
- [CloudBox Concepts](#cloudbox-concepts)
- [CloudBox (CB)](#cloudbox-cb)
- [Cloud Hour (CH)](#cloud-hour-ch)
- [CloudBox Properties](#cloudbox-properties)
!!wiki.include page:'box_intro.md'
## CloudBox (CB)
@@ -24,9 +32,22 @@ Terms
- Min passmark per cloudbox is 500 passmark (CPU benchmark)
- At least 50 GB storage available, more is better
## CloudHour (CH)
**Example a node with 64 GB or mem and 2 TB of SSD and 24 virtual cores.**
A cloudhour is like a kwatth unit for electricty: it represents a cloudbox being used for 1h and billed as such.
- 15 Storage Blocks each:
- 4 GB of memory (60 GB total)
- 120 GB of SSD capacity
- 6.4 logical CPU core (oversubscription of 4, which means user can max use 4x CPU capacity if system allows)
- when a user choses the full machine, then he/she will have reserved all Storage Blocks capacity which means the machine is now dedicated reserved for the user, the hoster specifies the discount for this typically 50%. On a dedicated machine the user has full access to the GPU.
- min 2GB always needs to be left as buffer for memory and 10% of SSD capacity
How does it work:
- When a developer wants to deploy a virtual machine, he/she needs to define the required capacity and will be able to make a choice based on these CloudBlocks, each CloudBlock has different base specs (mem, ssd, gpu, cpu) and reputation, the developer can now make a selection of how many of these Storage Blocks need to be given to the virtual machine. This defines the monthly price which will have to be paid as well as capacity available to the VM.
## Cloud Hour (CH)
A cloudhour is like a kwatth unit for electricty: it represents a CloudBlock being used for 1h and billed as such.
INCA Hosts (our cloud providers) can price the CloudHour themselves in a chosen currency.

View File

@@ -25,7 +25,7 @@ The service provider (hoster) defines the following properties per StorageBox:
- Max bandwidth
- Min bandwidth (min 1 mbit/sec)
- Cost per GB bandwidth
- Max aggregation size (how many of the storage boxes can be combined)
- Max aggregation size (how many of the Storage Blockes can be combined)
- Link to support site if any (find info about hoster and service capabilities)
- If linked to Hosting Pool (company giving support on the machines)
- Location & type of location