Forge4Flow

Explore the docs »
Report Bug · Request Feature

Forge4Flow provides ecosystem and developer tools for the Flow Blockchain, including Identity and Access Management, Blockchain Event Monitoring, and SDKs to better integrate dApps with the ecosystem.

The problem it solves

Developers face challenges in creating dApps due to issues like user authentication, access control, system monitoring, and third-party integration. Forge4Flow aims to address these problems with a developer infrastructure and tooling platform. We're excited to introduce three tool sets to advance the ecosystem:

Auth4Flow:

Blockchain-based authentication lacks comprehensive user verification, requiring custom solutions for advanced functionalities and role-based access control. Transitioning to a Web3 environment increases the complexity of achieving secure user access control, both within DApps and when interacting with Web2 technologies. Auth4Flow offers a simple, open-source Identity and Access Management platform that simplifies Web3 authentication. It supports various authorization schemes, including RBAC, FGAC, ReBAC, and NFT/FT gated access.

Alerts4Flow:

One of the biggest advanges of the Flow Blockchain is it's ability to emmit events from within contracts, thus allowing developers to react to changes as they occur. Unfortuantley tooling in this area has not been widely developed. With Alerts4Flow developers can easily setup Event Monitors to receive alerts in realtime using Websockets or Webhooks.

Ecosystem SDKs:

Lack of mobile resources is a huge factor for their being verry little Web3 Mobile apps. By releases ecosystem SDKs for multiple platofrms we can lower the barrier to entry for new developers. We have scoped several SDKs to target for Swift (iOS).

By providing these tool sets, we aim to empower developers to focus on delivering exceptional user experiences without worrying about complex authentication, access control, and other Web3 challenges.

Getting Started

To get started using Forge4Flow, follow the deployment guide to self host your own instance of Forge4Flow-Manager. Once you have an instance started, follow one of our SDK quick start guides or check out or documentation for more information.

Roadmap

Auth4Flow

• Blockchain Native Login w/ Client & Server Sessions
• Walletless Onboarding w/ Client & Server Sessions
  • Transaction Signing APIs
  • Parent/Child Account Linking
  • Forced Hybrid Authentication (Creating Flow Child Accounts for Blockchain Native Accounts)
• NFT Gated Access Controll
• .find Name and Profile Integration
• [] GO Server SDK
• JS SDK
• Node SDK
• React SDK
• NextJS
• Swift SDK
• Kotlin SDK
• Admin Dashboard
• Multi-Tenant Support

Alerts4Flow

• Custom Event Monitors
• Admin Dashboard

Ecosystem SDKs

• Flow Ecosystem
  • FLOAT
    • Swift (iOS)
    • JS, Node
    • Go
  • .find
    • Swift (iOS)
    • JS, Node
    • Go
  • Flow NFT Catalog
    • Swift (iOS)
    • Go
• Mobile Platforms
  • Swift (iOS)
    • NFT.storage
    • SwiftIPFS-Image
• General Purpose
  • GCP KMS authorizer (signer)

See the open issues for a full list of proposed features (and known issues).

(back to top)

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated Please see CONTRIBUTING.md for more information.

License

Forge4Flow is distributed under the ELv2 License. See LICENSE for more information. Our SDKs are distributed under MIT licenses, see each SDKs GitHub repo for more information.

Acknowledgments

• warrant.dev Forge4Flow was built on top an amazing open source authorization project called Warrant. All credit for the Web2 authorization functionality within Forge4Flow goes to the amazing warrant.dev team.

(back to top)