s
This commit is contained in:
@@ -4,50 +4,44 @@
|
||||
<h1>All Trust</h1>
|
||||
|
||||
- [A Paradigm of Trust](#a-paradigm-of-trust)
|
||||
- [Guardian Circles: Humans Ensuring Oversight](#guardian-circles-humans-ensuring-oversight)
|
||||
- [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)
|
||||
- [ThreeFold Farmers: Investors in Shared Internet/Cloud Infrastructure](#threefold-farmers-investors-in-shared-internetcloud-infrastructure)
|
||||
- [Shared Internet, Network \& AI Services](#shared-internet-network--ai-services)
|
||||
- [Guardian Circles: Humans Ensuring Oversight](#guardian-circles-humans-ensuring-oversight)
|
||||
|
||||
***
|
||||
|
||||
## A Paradigm of Trust
|
||||
|
||||
What if instead of distrusting others, we embrace a paradigm of trust?
|
||||
|
||||
Our system is built on this principle of trust between all participants.
|
||||
|
||||
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, ...
|
||||
|
||||
A Human chain rather than a Blockchain has the capability to build/maintain a good governance system.
|
||||
|
||||
## Guardian Circles: Humans Ensuring Oversight
|
||||
|
||||
- We believe a Guardian Circle has the potential to be as good as blockchain and more because Guardian Circles still provide human oversight over key decisions when needed, the bulk of transactions run automated.
|
||||
- Circles enact decisions when their 9-99 member nodes reach consensus. They manage treasuries, set policies, enable collaboration between regional grids, and more.
|
||||
- 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.
|
||||
|
||||
- What if instead of distrusting others, we embrace a paradigm of trust?
|
||||
- Our system is built on this principle of trust between all participants.
|
||||
- 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, ...
|
||||
- An Automated Human Chain has the capability to build/maintain a good governance system with greater flexibility compared to Block Chain.
|
||||
|
||||
## 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.
|
||||
- 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.
|
||||
- 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 ledger to identify any bad actors abusing the system.
|
||||
- **Fundamentally, the system relies on trust between participants.**
|
||||
|
||||
## Farmers: Investors in Shared Internet/Cloud Infrastructure
|
||||
## ThreeFold 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
|
||||
- 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.
|
||||
- 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
|
||||
|
||||
@@ -60,3 +54,10 @@ A Human chain rather than a Blockchain has the capability to build/maintain a go
|
||||
- Oracles for pricing, weather, ...
|
||||
- ...
|
||||
|
||||
|
||||
## Guardian Circles: Humans Ensuring Oversight
|
||||
|
||||
- We believe a Guardian Circle has the potential to be as good as blockchain and more because Guardian Circles still provide human oversight over key decisions when needed, the bulk of transactions run automated.
|
||||
- Circles enact decisions when their 9-99 member nodes reach consensus. They manage treasuries, set policies, enable collaboration between regional grids, and more.
|
||||
- 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.
|
||||
|
@@ -1,68 +0,0 @@
|
||||
# All Trust
|
||||
|
||||
What if in stead of not trusting anyone, we change the paradigm and we are going to trust everyone.
|
||||
|
||||
The TFGrid 4.0 system is built up out of actors, each actor is implemented inside a 3bot.
|
||||
|
||||
Some example actors
|
||||
|
||||
- farming: represents selected Grid Servives which run on top of 3nodes
|
||||
- farming cooperative: a cooperative of farmers, working on behalf of many farmers, who don't want to manage their own operation
|
||||
- 3node: manages one 3node and its operating system called ZOS
|
||||
- OurVerse node: manages a OurVerse node, OurVerse can be installed on deskopts, phones, ...
|
||||
- grid service: a grid service can be storage, compute, telecom, network services and can run on ZeroOS or OurVerse Node
|
||||
- grid consumer: an actor who works on behalf of a consumer of services of tfgrid, and helps the user to deploy and manage solutions deployed on the grid, payments are done on behalf of user
|
||||
|
||||
All of these actors work together to make a super scalable network of services which can support millions (if not billions) of consumers & service providers.
|
||||
|
||||
## Farmers
|
||||
|
||||
- Invest in TFNodes or other OurVerse based Services e.g. web gateway, telco service (5G,sms), ...
|
||||
- A Farmer invested in the required hardware to run these services.
|
||||
- A Farmer or Farming Cooperative will operationally run the services (set billing parameters, monitor environment, manage the networks, optionally give support, ...). Farming Cooperatives define how they distribute the margin they make to their members.
|
||||
- A Farmer can actively manage his own infrastructure or become part of a Farming Cooperative.
|
||||
- Farmers make profit thanks to people using their infrastructure and optionally monthly fixed farming rewards.
|
||||
|
||||
## Grid Services
|
||||
|
||||
In TFGrid 4.0 hundreds if eventually not thousands of services can be deployed inside the ecosystem of a new internet
|
||||
|
||||
How does it work?
|
||||
|
||||
- Grid Services track used capacity (e.g. bandwidth, storage, rpc requests), report this capacity to the relevant farming actor (or farming cooperative).
|
||||
- The Grid Consumer can talk to any of the Grid Services directly over OurVerse Reliable Message bus. The Consumer can ask for status reports, monitoring, or can ask for deployment of a serice or ask for a service request e.g. send SMS, send email, ask AI cloud ...
|
||||
- The Farming Actor will use their flexible pricing policies to define the price for the request or deployed capacity.
|
||||
- The Farming Actor will use OurVerse Pay to request payment (my means of request for IOU)
|
||||
|
||||
## IOU = I Owe You (Mutual Credit system)
|
||||
|
||||
- proofs of consumption & payment
|
||||
- farmers & consumers agree on the IOU (think about like a checque in the old banking days)
|
||||
- farmers & consumers sign both the IOU (done automatically by the actors using OurVerse for security)
|
||||
- the farmer will request the OurVerse Pay Bridge to do the payment at regular intervals e.g. once a day.
|
||||
- The OurVerse Pay Bridge is implemented inside a TFGrid Guardian Circle.
|
||||
- The OurVerse Pay Bridge will safely aggregate the IUO's and ask the relevant Consumer Actor to do the payment (in future their might be the notion of escrow accounts, so Consumers need to park money before asking services with a chosen Bridge).
|
||||
- Reputation of the Consumers is kept in the relevant TFGrid Guardian Circle, to make sure bad actors cannot cause harm.
|
||||
|
||||
## TFGrid Guardian Circle (our replace for blockchain)
|
||||
|
||||
- We believe in human chains, which acts and behaves as a blockchain but is directly linked to Humans rather than just a piece of code.
|
||||
- A Guardian Circle is a group of minimum 9 people (max 99).
|
||||
- Each person runs a 3bot who works on their behalf, so they don't have to do many tasks manually.
|
||||
- The Guradian owned 3bots communicate over OurVerse which takes care of security, encryption, consensus and reliable message delivery.
|
||||
- The OurVerse Concensus mechanism uses a derivate of Tendermint (see Kosmos blockchain ecosystem) to make sure that the consensus between the members is solid and done in time & space order.
|
||||
- A Guardian Circle can own one or more Treasury Wallets which are wallets of money blockchains (Ethereum, Stellar), these wallets use multisignature between all signers of a Guardian Circle.
|
||||
- The 3bots use VLang based DSL (Domain Specic coding Language) to describe the functionality.
|
||||
- All required actions are executing using 3Script (our own scripting language, super high level and easy), these 3scripts get executed by all members of the Guardian Circle, only if each Guardian TFNode comes to the exact same conclusion the action will be executed.
|
||||
- Typical actions as can be executed by a Guardian Circle
|
||||
- voting
|
||||
- roll up of IOU
|
||||
- validation of TFGrid status and auditing of capacity as provided by TFGrid
|
||||
- payments from Treasury as result of vote of roll up of IOU
|
||||
- pricing mechanism
|
||||
- billing for TfGrid Services
|
||||
- If needed manual actions (checks) can be done by the humans behind a Gurdian Circle e.g. validate a price chain.
|
||||
- Such a TFGrid Guardian Circle is ultra flexible, there can be millions of them and they can all work together, they can be made fully compatible with any chosen money blockchain or other financial institute.
|
||||
- Its very easy for developers to extend capabilities of a Guardian Circle (alternative to smart contracts on blockchain)
|
||||
|
||||
|
@@ -2,17 +2,14 @@
|
||||
|
||||
!!wiki.include page:'slice_intro.md'
|
||||
|
||||
An AI box is a unit of AI capacity (GPU or future TPU driven).
|
||||
|
||||
- An AI box is a unit of AI capacity (GPU or in the future TPU).
|
||||
- The mininal GPU supported for now is a Nvidia 4090 or comparable
|
||||
|
||||
An AI box can be launched in our Zero-OS and can enable any possible AI workload.
|
||||
- An AI box can be launched in our Zero-OS and can enable any possible AI workload.
|
||||
|
||||
## AI Hour (AH)
|
||||
|
||||
AI hour (AH) is like a kwatth unit for electricty: it represents a AI Slice being used for 1h and billed as such.
|
||||
|
||||
INCA Hosts (our cloud providers) can price the AI Hour themselves in a chosen currency.
|
||||
- AI hour (AH) is like a kwatth unit for electricty: it represents a AI Slice being used for 1h and billed as such.
|
||||
- ThreeFold Farmers can price the AI Hour in a chosen currency.
|
||||
|
||||
## AI Slice Properties
|
||||
|
||||
@@ -20,7 +17,7 @@ The service provider (hoster) defines the following properties per AI Slice:
|
||||
|
||||
- Type of GPU
|
||||
- Price per hour
|
||||
- Discounts if used for longer periods & if renter has large amount of TFT in wallet
|
||||
- Maximum Discount (based on participation in Liquidity Pool and/or longer renting periods)
|
||||
- Max bandwidth
|
||||
- Min bandwidth (min 1 mbit/sec)
|
||||
- Cost per GB bandwidth if any
|
||||
@@ -29,5 +26,4 @@ The service provider (hoster) defines the following properties per AI Slice:
|
||||
- If linked to Hosting Pool (company giving support on the machines)
|
||||
- Location & type of location
|
||||
|
||||
Each AI Slice has unique ID and can be looked at through a portal (or found).
|
||||
|
||||
|
@@ -4,12 +4,9 @@
|
||||
|
||||
## Cloud Slice
|
||||
|
||||
A Cloud Slice is a unit of compute, fast storage and memory.
|
||||
There are unlimited different configurations of Cloud Slice.
|
||||
|
||||
A configuration of a machine defines the Cloud Slice which can be made.
|
||||
|
||||
A Cloud Slice can be aggregated to make a bigger Cloud Slice.
|
||||
- A Cloud Slice is a unit of compute, fast storage and memory.
|
||||
- A configuration of a machine defines the Cloud Slice which can be made.
|
||||
- A Cloud Slice can be aggregated to make a bigger Cloud Slice.
|
||||
|
||||
The default Cloud Slice has
|
||||
|
||||
@@ -26,12 +23,12 @@ Terms
|
||||
|
||||
**Example a node with 64 GB or mem and 2 TB of SSD and 24 virtual cores.**
|
||||
|
||||
- 15 StorageSlices each:
|
||||
- 15 Cloud Slices 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 StorageSlices 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
|
||||
- when a user choses the full machine, then he/she will have reserved all Compute Slices capacity which means the machine is now dedicated reserved for the user, the hoster specifies the discount for this typically 50%.
|
||||
- Min 2GB always needs to be left as buffer for memory and 10% of SSD capacity on the host machine
|
||||
|
||||
How does it work:
|
||||
|
||||
@@ -39,19 +36,18 @@ How does it work:
|
||||
|
||||
## Cloud Hour (CH)
|
||||
|
||||
A cloudhour is like a kwatth unit for electricty: it represents a Cloud Slice being used for 1h and billed as such.
|
||||
|
||||
INCA Hosts (our cloud providers) can price the CloudHour themselves in a chosen currency.
|
||||
- A Cloud Hour is like a kwatth unit for electricty: it represents a Cloud Slice being used for 1h and billed as such.
|
||||
- ThreeFold Farmers (Providers) can define the proce of the Cloud Hour in a chosen currency.
|
||||
|
||||
## Cloud Slice Properties
|
||||
|
||||
The service provider (hoster) defines the following properties per cloud box
|
||||
The ThreeFold Farmer defines the following properties per Cloud Slice
|
||||
|
||||
- Cost of 1 CloudHour (use the box for 1h)
|
||||
- Discounts if used for longer periods & if renter has large amount of TFT in wallet
|
||||
- Cost of 1 Cloud Hour (use the slice for 1h)
|
||||
- Maximum Discount (based on participation in Liquidity Pool and/or longer renting periods)
|
||||
- Min available storage in GB (min 50)
|
||||
- Max available storage in GB
|
||||
- Min passmark, max passmark
|
||||
- Min passmark, Max passmark
|
||||
- Max bandwidth
|
||||
- Min bandwidth (min 1 mbit/sec)
|
||||
- Cost per GB bandwidth
|
||||
@@ -59,10 +55,9 @@ The service provider (hoster) defines the following properties per cloud box
|
||||
- Max additional storage
|
||||
- Max aggregation size (how many of the Cloud Slice 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)
|
||||
- Pub ip address possible or not (is option)
|
||||
- If linked to Farming Pool (company giving support on the machines)
|
||||
- Pub IP address possible or not (is option)
|
||||
- Link to monitoring page (if any)
|
||||
- Location & type of location
|
||||
|
||||
Each Cloud Slice has unique ID and can be looked at through a portal (or found).
|
||||
|
||||
|
@@ -1,7 +1,7 @@
|
||||
|
||||
A Cloud, Storage or AI Slice is a part of a server/computer (3Node) which delivers a service which has well defined properties in relation to capacity, pricing, serviceabity, capabilities.
|
||||
|
||||
These Cloud, Storage or AI Slices can be bought by the ThreeFold Community through the TF Marketplace.
|
||||
These Cloud, Storage or AI Slices can be bought by the ThreeFold Community through the Marketplace.
|
||||
|
||||
|
||||
|
||||
|
@@ -4,7 +4,7 @@
|
||||
|
||||
## Storage Slice
|
||||
|
||||
A Storage Slice is a unit of ZDB storage as can be used as backend for Zero-Stor (our quantum safe storage system).
|
||||
A Storage Slice is a unit of ZDB storage (our key value stor) as can be used as backend for Zero-Stor (our quantum safe storage system).
|
||||
|
||||
The default Cloud Slice has:
|
||||
|
||||
@@ -12,16 +12,15 @@ The default Cloud Slice has:
|
||||
|
||||
## Storage Hour (SH)
|
||||
|
||||
A storagehour is like a kwatth unit for electricty, it represents a Storage Slice being used for 1h and billed as such.
|
||||
|
||||
INCA Hosts (our cloud providers) can price the StorageHour themselves in a chosen currency.
|
||||
- A Storage Hour is like a kwatth unit for electricty, it represents a Storage Slice being used for 1h and billed as such.
|
||||
- ThreeFold Farmers can price the StorageHour themselves in a chosen currency.
|
||||
|
||||
## Storage Slice Properties
|
||||
|
||||
The service provider (hoster) defines the following properties per Storage Slice:
|
||||
|
||||
- Min size in GB (100GB+), max size
|
||||
- Discounts if used for longer periods & if renter has large amount of TFT in wallet
|
||||
- Maximum Discount (based on participation in Liquidity Pool and/or longer renting periods)
|
||||
- Max bandwidth
|
||||
- Min bandwidth (min 1 mbit/sec)
|
||||
- Cost per GB bandwidth
|
||||
@@ -30,5 +29,4 @@ The service provider (hoster) defines the following properties per Storage Slice
|
||||
- If linked to Hosting Pool (company giving support on the machines)
|
||||
- Location & type of location
|
||||
|
||||
Each Storage Slice has unique ID and can be looked at through a portal (or found).
|
||||
|
||||
|
Reference in New Issue
Block a user