Flow.Sol

Token per Project

Empowering Projects with Natural Flow

Live Data

Tokens will be available in:
Current Status:
Contract Network (important!):
Contract Address (important!):
Version:
Solidity Code: The contract is fully verified and available on Polygonscan. The main token logic begins at line 3231. 👉 View contract on Polygonscan
Tokens:

How to purchase FLW tokens:

    Option 1: Purchase via a decentralized exchange (DEX) based on supply and demand.
    You can use any supported currency (such as USDC, ETH, BTC, etc.), also from other networks - a bridge operation may be required. Follow the to the instructions follwing the link below.
    ⚠️ The price may change in real time for liquidity and trading:
    Buy FLW on QuickSwap

    Option 2: Directly from the contract:
    •⁠ ⁠Download MetaMask wallet as a Chrome extension
    •⁠ ⁠⁠Buy POL coins in the desired amount such as from Binance
    •⁠ ⁠⁠Transfer to your Metamask wallet address
    •⁠ ⁠⁠Click the "Support/Invest" button below if tokens are available for sale:

Milestones:
Project's Commitment:
Owner Activity:

About Flow.Sol

Flow.Sol is a smart contract for managing projects on a blockchain network. The tool offers a decentralized, transparent and flexible framework for managing the life cycle of a project – from funding, through meeting goals to distributing incentives. Flow.Sol is a standalone software file, independent of a managed platform, empowering direct and transparent project management while fostering trust through decentralization.

How It Works

Step 1: Create the Contract and Issue Tokens
The entrepreneur defines the size of the project and divides it into milestones.
Example:
- Producing a musical album with 10 songs.
- Total Tokens: 10,000 tokens at $1 per token.
- First Milestone: Create the first song (1,000 tokens).

Step 2: Sell Tokens to Supporters
- Supporters purchase tokens at a fixed price for each milestone.
- The tokens are transferred directly to supporters' wallets via the smart contract.

Step 3: Achieve Milestones and Earn Tokens
- The entrepreneur completes the milestone and reports it via the contract.
- Once the milestone is completed and verified, the entrepreneur must manually finalize it in Remix (or another blockchain explorer) by calling approveFinishMilestone(). This transfers any remaining unsold tokens to the entrepreneur’s wallet.

Step 4: Continue the Project
- The entrepreneur can publish a new milestone with defined goals and pricing. Milestones can be added dynamically, allowing flexible project adaptation.
- A new funding cycle begins, building on the trust and progress demonstrated in previous milestones.

System Principles and Unique Features

Full Transparency: All stages, transactions, and updates are public on the blockchain.
Milestone-Based Management: The project is divided into pre-defined stages with clear goals.
Economic Incentives: Unsold tokens are transferred to the entrepreneur only after successfully completing a milestone.
Complete Entrepreneur Control: The entrepreneur defines the structure, scope, and pace of the project. Currently, Flow.Sol does not support multi-owner roles or shared control.
Decentralized Independence: The system operates without intermediaries or hidden fees.
Open Source: The policy requires transparency until project completion.
Versatility: Suitable for projects of any size or type – music, art, software, education, and even national projects.
Direct Connection: Supporters and entrepreneurs are directly linked via the smart contract, creating a foundation of trust and transparency.

Who Is It For?

Entrepreneurs: Looking to manage projects independently and transparently.
Investors: Wanting to invest in defined stages and follow the project's progress.
Communities: Interested in managing projects without dependence on central entities.

Conclusion

Flow.Sol is a simple and effective tool for the smooth and natural management of projects of any type or size using blockchain-based project-specific currencies. The system emphasizes transparency, clear incentives, and full control for the entrepreneur.

How to Start

The Flow.sol file is a contract template built on the Solidity framework and utilizes the OpenZeppelin library, a well-established and secure library for creating ERC20 smart contracts. This design offers greater control and reliability in the development process while providing robust tools for managing and auditing the project’s digital resources.

The contract is written in a clear and concise language, enabling users to easily understand its operational mechanisms and embedded control features.

This template is designed to facilitate an iterative and natural process of project development by supporting continuous adaptation and improvement based on real-world feedback and evolving needs. Additionally, the codebase remains open until the project’s completion, ensuring full transparency and shared accountability.

Step 1: Define Your Project

This step outlines a recommended approach for successfully launching and managing your project's milestones. While these are guidelines, you are free to adapt them to your specific needs.

Step 2: Set Up a Digital Wallet

A digital wallet is essential for interacting with the Flow.sol smart contract. Follow these steps to set up your wallet.

Step 3: Edit the Code of the `.sol` File

The contract file is written in accordance with the accepted standards in the software world and is designed for flexible and simple use. Users without an advanced technical background can simply update a few essential constants at the top of the code to adapt it to the needs of their project. Experienced users can modify and adapt the entire code according to their understanding.

Loading the Contract in Remix
1. - You must copy the contract address from the Live Data area (there is no copy button for security reasons) on the project website (at the top of this page for the MVP version).
  - With each milestone completion, the code will be deployed to a test network, and the new contract address will be published in the Roadmap section of this site.
2. - Go to Remix and open the IDE.
  - Select File Explorers → Load Contract from Address.
  - Paste the copied contract address and click “Load”.
- Note: You can also work with other tools such as Hardhat and Truffle.
Updating Essential Parameters
The contract includes a set of constants at the top of the file, which should be updated according to your project needs. Each constant includes inline documentation explaining its purpose. Unless specific modifications are needed, no changes are required beyond these constants:
- INITIAL_SUPPLY: The initial and final token supply. No additional tokens can be minted after deployment.
- MIN_TOKEN_PRICE_ETH: The minimum price of a token in ETH.
- FIRST_MILESTONE: Description of the first milestone.
- PROJECT_COMMITMENT: Declaration of project commitment. The process is bound to the project even if the owner changes.
- TOKEN_URI: URL of the token’s icon.
Tip: It is recommended to maintain a structured versioning approach for your project:
- Initial version for a milestone deliverable: 0.1.0.
- Final version upon project completion: 1.0.0.
- Minor changes within a milestone: 0.0.1 updates.
Compiling the Contract
- In Remix, go to the Solidity Compiler tab and click “Compile”.
- The contract should compile without errors.
Errors are not expected if only constants were modified. If an error occurs, review the changes made or consult a professional.

Step 4: Deploy to a Test Network

Before deploying the contract to the main network, it is highly recommended to test it on a test network. This ensures that the contract functions correctly without spending real funds. In this guide, we will demonstrate the deployment process on Fuji Testnet (Avalanche C-Chain Testnet), but the process is similar for other test networks like Goerli, Sepolia, and Mumbai.

Selecting a Test Network
- Recommended network: Fuji Testnet (Avalanche C-Chain), but Goerli, Sepolia, and Mumbai can also be used.
- Adding the network to MetaMask:
  - Go to Chainlist and search for your desired network.
  - Connect your wallet and approve the addition.
  - Alternatively, manually add the network via MetaMask → Settings → Networks → Add Network and enter the required parameters.

Funding Your Wallet with Test Tokens (Faucet)
- Ensure you have sufficient test tokens to cover transaction fees.
- Use the appropriate faucet to obtain tokens:
  - Fuji Testnet: Avalanche Faucet
  - Goerli Testnet: Alchemy Faucet
  - Sepolia Testnet: Infura Faucet

Deploying the Contract via Remix
- Open Remix and Load the Contract: (This was done in Step 3.)
- Select the Correct Environment:
  - In Remix, go to the Deploy & Run Transactions tab.
  - Under Environment, select Injected Provider - MetaMask.
  - Ensure that your wallet address is displayed and that the selected network is your test network.
- Deploy the Contract:
  - Under Contract, ensure that FlowToken.sol is selected.
  - Enter the initialOwner address (your main wallet).
  - Click Deploy and confirm the transaction in MetaMask.

Verifying the Contract on the Test Network
- Once deployed, Remix will display the contract address.
- Check the contract on the relevant blockchain explorer:
  - Fuji Testnet: Snowtrace (Avalanche Explorer)
  - Goerli Testnet: Etherscan (Goerli)
  - Sepolia Testnet: Etherscan (Sepolia)
- Paste your contract address into the search field to verify the deployment.

Summary:

This step ensures the contract is working correctly before deploying to the main network.
It is recommended to verify all functions are behaving as expected and fix any issues before moving to live deployment.
Deploying the contract is only the beginning – in the next step, we will simulate real project cycles to ensure everything works correctly under real conditions.
Once the contract is successfully tested, proceed to the next step – Simulating Project Cycles.

Step 5: Simulate Project Cycles

After deploying the contract on a test network, it is essential to simulate a complete project cycle. This ensures that milestones progress correctly, funding mechanics work as expected, and ownership mechanisms behave properly. The goal is to test the project as if it were already live.

Step 1: Load the Contract and Deploy on a Test Network
- The recommended environment for project management is Remix IDE or any other equivalent tool (e.g., Hardhat, Truffle).
- Open Remix and import the contract from the published contract address.
- Ensure the contract is loaded with a constructor that includes the first milestone already defined.
- Deploy the contract to a test network (e.g., Fuji, Sepolia, Goerli).

Step 2: Buy Tokens and Close the First Milestone
- (Anyone) Use buyCurrentOpenMilestoneTokens in Remix to simulate purchasing project tokens.
- Verify that the tokens appear in the buyer’s wallet.
- (Owner Only) Close the milestone using approveFinishMilestone.
- Ensure that the remaining balance is automatically transferred to the project owner.

Step 3: Create and Activate a New Milestone
- (Owner Only) Add a new milestone using addMilestone.
- (Owner Only) Activate the next milestone using activateMilestone.
- Repeat the token purchase and milestone completion steps.

Step 4: Iterating Through the Project Until Completion
- It is recommended to complete at least three milestones before reaching version 1.0.0.
- Each cycle follows this structure:
- Repeat the process until the project reaches completion.
- (Owner Only) Ensure that setProjectStatus properly marks the project as Completed when all milestones are finished.

Important:
Most actions can be performed through the Remix UI buttons. However, only the contract owner (the project manager) has access to certain management functions such as defining, activating, and closing milestones. Investors and users can only interact with public functions like token purchases.

Step 6: Deploy to the Main Network

Now that you've tested your contract on a test network and ensured that it works as expected, it's time to deploy it to the main network. This is a critical step, as once the contract is deployed, it cannot be changed!

Final Preparations Before Deployment
Before deploying the contract, make sure you have checked the following:
- Tested on a test network: Verified that all functions work correctly and there are no issues. ✅
- Your wallet is ready for project management: The contract will assign you as the owner, so ensure that your main wallet is connected. ✅
- Sufficient funds for gas fees: Ensure you have enough ETH or the equivalent cryptocurrency to cover transaction costs. ✅
- External addresses are correctly set: If your contract references external addresses (e.g., investors or additional managers), verify them carefully. ✅

Selecting a Deployment Network
Flow.Sol supports any EVM-compatible blockchain. Different networks vary in fees, scalability, and performance. It is recommended to research and select the most suitable network for your project.

Deploying via Remix

Connecting Your Wallet:
- Open Remix → Navigate to Deploy & Run Transactions.
- Under Environment, select Injected Provider - MetaMask.
- Ensure your wallet is connected to the target network. ✅
Deploying the Contract:
- Load the FlowToken.sol contract.
- Select the contract from the list.
- Verify that the initial parameters are correct. ✅
- Click Deploy, approve the transaction in MetaMask, and wait for confirmation.

Verifying the Deployment
Once deployment is complete, Remix will display the contract address.
- Check the contract: Search for the contract address on a block explorer: ✅
- Ensure that all contract functions are visible and that there were no errors in the deployment transactions. ✅

Verifying the Contract Code
On most networks, you can verify the contract code to allow users to inspect it.
- Go to the block explorer – Search for your contract address and click Verify & Publish.
- Select the compiler version – Use the same version that was used to compile the contract.
- Upload the contract code – Copy and paste the Solidity file from Remix and confirm. ✅
Flow.Sol project supports open-source transparency, providing a contract template + recommended process. However, each entrepreneur can manage their project independently.

Publishing the Contract Address
After deployment, it is recommended to publish the contract address to allow investors direct access:
- On the project website – Display the contract address and provide a link to the block explorer.
- In project documentation – Explain how to interact with tokens and make purchases.
- Or any other method – Flow.Sol provides a contract template and a recommended workflow, but each entrepreneur can manage it as they see fit.

The Contract is Now Live! 🎉

Step 7: Tokens Sale

Once your contract is live on the main network, you need to ensure that supporters and investors can easily purchase tokens. This section explains the available options for managing token sales and receiving payments.

Purchasing Tokens via Smart Contract
Before purchasing tokens, make sure:
- You have sufficient ETH / AVAX to cover the transaction and gas fees.
- There are available tokens for sale in an active milestone.
- The correct contract address is used for the transaction.
The Flow.Sol contract allows supporters to purchase tokens directly using the built-in function:
- Function: buyCurrentOpenMilestoneTokens()
- How it works: Supporters send ETH (or the relevant blockchain currency) to the contract.
- Token Allocation: The contract automatically calculates the number of tokens and assigns them to the buyer.
- Funds Handling: The funds remain locked in the contract until the milestone is completed.

Accepting Payments and External Integrations
While the smart contract automates token sales, you may want to integrate other payment methods:
- Direct Wallet Transfers: You can manually distribute tokens by receiving payments to your wallet and calling transfer().
- DEX Listings: Entrepreneurs can list their token on decentralized exchanges (DEX) such as Uniswap, PancakeSwap, or Trader Joe. This requires manually adding liquidity and ensuring a price discovery mechanism, as Flow.Sol does not provide built-in DEX integration. Currently, Flow.Sol does not provide automatic DEX integration, and listing is the responsibility of the token issuer.
- Bridging to Other Chains: If needed, use token bridges to expand availability across multiple blockchains.

Monitoring Token Transactions
Investors and project owners can track all token sales using blockchain explorers:
- Etherscan (Ethereum): View transactions
- BscScan (BSC): View transactions
- Polygonscan (Polygon): View transactions

Releasing Funds After Milestone Completion
Once a milestone is successfully completed, the contract allows the project owner to claim the remaining tokens:
- Function: approveFinishMilestone()
- Effect: The contract distributes any unsold tokens to the project owner.
- Conditions: Only the project owner can call this function via Remix, Snowtrace, Etherscan, or any other compatible blockchain explorer, ensuring controlled token distribution.

Transparency and Investor Communication
To maintain trust and transparency, consider:
- Publishing the token contract address on your project website.
- Providing real-time updates on sales, funding, and milestones.
- Allowing investors to verify transactions on the blockchain.

The next step: Managing and progressing through project milestones efficiently.

Step 8: Manage Your Project

Maintain transparency and keep your supporters informed as you progress.

Update the smart contract after completing each milestone.
Release unsold tokens as incentives for yourself.
Publish new milestones and start new funding cycles. Only one milestone can be active at a time. Once a milestone is completed, the entrepreneur must manually activate the next milestone by calling activateMilestone() in Remix or an EVM-compatible interface.
For public tracking, supporters can use tools like Etherscan to view blockchain activity.

Step 9: Continuous Improvement

Leverage the natural feedback cycle of Flow.Sol:

Successful milestone completion builds trust and raises token value.
Publish updates, manage new milestones, and attract additional supporters.
If a project fails to meet expectations, its token value will be determined by market dynamics, investor demand, and overall project progress.

Use Cases

Share your project with me if you wish and inspire others

Roadmap

Flow.Sol is currently in its Beta development stage. The current token version is 0.1.X and will remain unchanged throughout the project. Future developments will focus on providing more advanced smart contract files (with higher version numbers), but each contract will operate independently without upgrading the token version for ongoing projects. Below, you can find details about the current stage and potential future directions.

Phase 1: MVP (0.1.X)

The first phase focuses on creating a functional and independent Minimum Viable Product (MVP). This phase includes:

Development of a fully operational and autonomous smart contract system.
Bug fixes and security testing (Beta version - please proceed with caution).
Comprehensive guides or clear references for:
- Creating tokens and deploying contracts.
- Testing and debugging processes.
- Designing and managing project lifecycles.
- Reading and interpreting project data.

Estimated cost: Equivalent to four months of developer work.
Scope: This phase constitutes 33% of the total project effort, which is planned for one year of active work.

Future Directions

While the next steps are not finalized, several potential directions are being considered:

Involving investors in business decision-making processes.
Expanding the system to support additional features, if necessary.
Improving guides and tutorials to help users set up and manage their projects correctly.

The token version for the current project, 0.1.X, will remain static for the entirety of this project. Future releases (e.g., version 1.0.0) will be introduced as separate systems and will not impact the current version unless critical fixes are required.

Pause and Continuity

After completing the first phase (MVP), I may pause the Flow.Sol project temporarily to focus on the development of YARRIVA_bot, a critical project aimed at improving societal conditions in my country. However, this does not mean the project will be abandoned:

If I decide to halt the project permanently, I will announce it and work to find a resolution for investors.
If no updates are provided within a defined period, a pre-determined process will occur automatically.

FAQ

The FAQ section addresses common concerns and provides insights into how Flow.Sol works. Whether you're an entrepreneur looking to start a project or a supporter exploring investment opportunities, you'll find useful information here. If your question isn’t covered, feel free to reach out via my Contact section.

Q: What happens if a milestone is not completed?

A: In Flow.Sol’s natural ecosystem, successful projects thrive, raising token value and rewarding early investors. Unsuccessful projects fade naturally as risk increases and token value adjusts, reflecting true progress. This dynamic fosters accountability, trust, and organic growth, reflecting the natural evolution of projects and their lifecycle.

Q: Can I modify milestones after the contract is deployed?

A: No, milestones cannot be modified once the contract is deployed to maintain the integrity and trust of the system. You can, however, create additional milestones for future goals.

Q: Which blockchain networks are supported?

A: Flow.Sol is compatible with any Ethereum Virtual Machine (EVM)-based blockchain. This includes Ethereum, Binance Smart Chain, Polygon, and others. Ensure you choose a network that aligns with your project's needs and cost efficiency.

Q: How are supporters protected from scams?

A: Flow.Sol operates transparently on the blockchain, meaning all transactions, milestones, and updates are public. Supporters can verify the contract and track the project's progress before contributing.

Q: Can I use Flow.Sol for a non-profit project?

A: Absolutely! Flow.Sol is designed for flexibility and can be used for any type of project, including non-profits. Simply define milestones that reflect your goals, and use the system to gather transparent contributions.

Q: Is there a minimum amount of funding required to start?

A: No minimum funding amount is required. You can define your project's scope and milestones based on your specific needs and adjust token pricing accordingly.

Q: How do I withdraw funds from the contract?

A: You are not dependent on the project manager to withdraw or use funds. The tokens you purchase are digital assets, like any other cryptocurrency, and can be traded freely on the market (specific details are in the technical section).
Tokens are freely tradable digital assets, independent of project management. However, project tokens do not automatically appear on exchanges and may require manual liquidity provisioning. Successful projects increase token value, benefiting supporters and enabling meaningful contributions. A well-managed project naturally increases token value, rewarding supporters while enabling them to contribute to meaningful initiatives.

Q: Can multiple entrepreneurs collaborate on a single project?

A: Currently, the contract supports only a single project manager. There are no additional roles or multi-entrepreneur collaboration capabilities defined in the current version of the contract.

Live Data

About Flow.Sol Show More

How It Works

System Principles and Unique Features

Who Is It For?

Conclusion

How to Start Show More

Step 1: Define Your Project Show More

Step 2: Set Up a Digital Wallet Show More

Step 3: Edit the Code of the `.sol` File Show More

Step 4: Deploy to a Test Network Show More

Step 5: Simulate Project Cycles Show More

Step 6: Deploy to the Main Network Show More

Step 7: Tokens Sale Show More