Layers

• Physical layer: This layer defines the physical infrastructure of the network, including the nodes, links, and protocols used for communication.

• Network layer: This layer manages the routing of data between nodes in the network, ensuring that packets are delivered to the correct destination.

• Transport layer: This layer ensures reliable delivery of data by providing error detection, flow control, and congestion control.

• Application layer: This layer provides the interface for applications to communicate with each other, using protocols such as HTTP, SMTP, and FTP.

Flow harmonizes communications with the sub-systems, leveraging the proposed runtime and novel isomorphic-state channels.

Flow accomplishes this in several ways including deriving our own custom variations to Hydra - lightning fast isomorphic state-channels created by researchers at IOHK. Furthermore, the platform heavily relies on the reduced overhead and increased throughput made possible the state-channels to ensure operating spaces remain light-weight. Flow operates the runtime fabric similar to that of a scheduler native to traditional operating systems. Flow leverages these channels to augment communications between detached surfaces by continuously adapting the runtime fabric to best suit the users needs.

Gas tanks enable us to tangibly describe the amount of cloud computing power users have access to. All devices registered to the user for a virtual private network allowing them to access the aggregated power and resources, streamed directly into their platform. Flow makes direct use of this, offloading various tasks onto more optimized surfaces the user isn't acting upon before searching for rentable computational spaces. We hope that this naturally increases network participation and further plan on offering a monthly subscription model payable through computational resources.

Resources

• Hydra 

A primary feature of Flow is centralizing any registered users' assets into a single, manageable portfolio. Flow is to implement payment channels similar to those found on currently developing layer-2 blockchain networks, remaining light-weight while further enabling peers to interact with one another.

Issues

Currently, financial services remain scattered across the internet making it nearly impossible for everyday users to reap any of the benefits of novel technologies. This issue is compounded when considering the vast number of projects currently being pursued.

Description

By nature, each Flow module is set to have unprecedented access to a user's personal information acting on behalf of the user when appropriate. This is includes a hefty amount of financial information, which is aptly applied leveraging out integrations with Stripe to bridge the gap between crypto and traditional finance. Furthermore, our users will be encouraged to open a bank account to make full use of the platform's capabilities. Leveraging the included debit card, each registrant will be able to spend any of their assets, anywhere without the hassle or fees that accompany similar projects like the Coinbase Debit Card.

Supporting Research

Brick: Asynchronous Payment Channels
Lightweight Virtual Payment Channels

A key feature of the project is the orchestration of various workloads across a range of devices. Each eligible device is broken down into a set of micro-environments.

Each triadic environment is transformable, therefore, it is critical that the distributor is capable of analyzing the surface w.r.t. both the current capabilities and number of transformations needed before it can execute the next task. For example, if a triadic object is a single transformation away from being capable than it might be better to execute the transformation rather than allocating the workload to a networked device. On the other hand, given a workload that would require several transformations to be applied than the opposite may be true.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.