🌊 Welcome to Fluid Finance!

A set of protocols that redefine how current deFi operates

👤 Sample User Flow on Fluid Finance ( try this to simulate txns ) :-

L&B User Flow

• setup admin params
  flow transactions send "cadence\transactions\L&B\setupAdminParams.cdc" --signer "L&B"

• create new bucket
  flow transactions send "cadence\transactions\L&B\createNewBucket.cdc" --signer default

• mint some tokens for yourself
  flow transactions send "cadence\transactions\standards\mintSomeExampleTokens.cdc" --signer default 1000000.0

• get your bucketIds for next txn
  flow scripts execute "cadence\scripts\L&B\fetchAllBuckets.cdc" {default-signers-address}

• supply tokens to pool
  flow transactions send "cadence\transactions\L&B\supplyTokensToPool.cdc" --signer default 100.0 {your-bucketId}

• borrow from the poool
  flow transactions send "cadence\transactions\L&B\borrowTokensFromPool.cdc" --signer default 70.0 {your-bucketId}

• repay to pool
  flow transactions send "cadence\transactions\L&B\repayTokensToPool.cdc" --signer default 70.0 {your-bucketId}

• unsupply tokens to pool
  flow transactions send "cadence\transactions\L&B\unsupplyTokensToPool.cdc" --signer default 70.0 {your-bucketId}

OLM User Flow

• setup admin params
  flow transactions send "cadence\transactions\OLM\setupAdminParams.cdc" --signer OLM

• mint some buyWith tokens for yourself
  flow transactions send "cadence\transactions\standards\mintSomeBuyWithTokens.cdc" --signer default 1000000.0

• mint some staking tokens for yourself
  flow transactions send "cadence\transactions\standards\mintSomeStakeTokens.cdc" --signer default 1000000.0

• stake in the contract
  flow transactions send "cadence\transactions\OLM\stakeTokens.cdc" --signer default 100.0

• claim oTokens as reward
  flow transactions send "cadence\transactions\OLM\claimOTokens.cdc" --signer default

• redeem oTokens for payout Tokens
  flow transactions send "cadence\transactions\OLM\redeemOTokens.cdc" --signer default

• unstake your tokens
  flow transactions send "cadence\transactions\OLM\unstakeTokens.cdc" --signer default

🔨 Getting started

Getting started can feel overwhelming, but we are here for you. Depending on how accustomed you are to Flow here's a list of resources you might find useful:

• Cadence documentation: here you will find language reference for Cadence, which will be the language in which you develop your smart contracts,
• Visual Studio Code and Cadence extension: we suggest using Visual Studio Code IDE for writing Cadence with the Cadence extension installed, that will give you nice syntax highlitning and additional smart features,
• SDKs: here you will find a list of SDKs you can use to ease the interaction with Flow network (sending transactions, fetching accounts etc),
• Tools: development tools you can use to make your development easier, Flowser can be super handy to see what's going on the blockchain while you develop

📦 Project Structure

Your project comes with some standard folders which have a special purpose:

• /cadence inside here is where your Cadence smart contracts code lives
• flow.json configuration file for your project, you can think of it as package.json, but you don't need to worry, flow dev command will configure it for you

Inside cadence folder you will find:

• /contracts location for Cadence contracts go in this folder
• /scripts location for Cadence scripts goes here
• /transactions location for Cadence transactions goes in this folder
• /tests all the integration tests for your dapp and Cadence tests go into this folder

👨‍💻 Start Developing

After creating this project using the flow setup command you should then start the emulator by running:

> flow emulator --contracts

we use --contracts flag to include more already deployed contract we can then easily import in our project.

and then start the development command by running:

> flow dev

After the command is started it will automatically watch any changes you make to Cadence files and make sure to continiously sync those changes on the emulator network. If you make any mistakes it will report the errors as well. Read more about the command here

Importing Contracts

When you want to import the contracts you've just created you can simply do so by writing the import statement:

import "Foo"

We will automatically find your project contract named Foo and handle the importing for you.

Deploying to specific accounts

By default all contracts are deployed to a default account. If you want to seperate contracts to different accounts you can easily do so by creating a folder inside the contracts folder and we will create the account for you which will have the same name as the folder you just created. All the contracts inside that folder will be deployed automatically to the newly created account.

Example deploying to charlie account:

folder structure

/contracts
    Bar.cdc
    /charlie
        Foo.cdc

You can then import the Foo contract in Bar contract the same way as any other contract:

import "Foo"

Included Imports

You can already import certain common contracts we included for you, just make sure you started your emulator with the --contracts flag so those contracts are really deployed. The list of contracts you can import out of the box is:

• NonFungibleToken import "NonFungibleToken"
• FlowToken import "FlowToken"
• FungibleToken import "FungibleToken"
• FUSD import "FUSD"
• MetadataViews import "MetadataViews"
• ExampleNFT import "ExampleNFT"
• NFTStorefrontV2 import "NFTStorefrontV2"
• NFTStorefront import "NFTStorefront"

Further Reading

• Cadence Language Reference https://developers.flow.com/cadence/language
• Flow Smart Contract Project Development Standards https://developers.flow.com/cadence/style-guide/project-development-tips
• Cadence anti-patterns https://developers.flow.com/cadence/anti-patterns