1) Will there still be smart contracts behind the scenes?

Yes, FCT in a scripting language that runs on-chain and is operated by a smart contract

2) Will the SDK be open-sourced?

Yes, it will be in the near future. And not only that, but the community will be able to extend the SDK by creating more plugins for different protocols

3) Is the front-end open-sourced?

The plan is to make the front end open source in the future

4) Is the backend open-sourced?

The backend is not open-sourced for security reasons and the nature of FCTs is that the backend cannot change or influence the process of your transactions. It's simply a way to improve user experience & overall performance.

The backend is here to serve our visual builder & our own automatic activation services, which means that all FCT functionality is not relying on the backend. This basically means that people can create FCTs without using our server or front end and not only that but FCTs that were created using our app or other means - cannot be stopped from deploying on the blockchain whether our Kirobo server is running or not.

And in addition to that - we plan to release an open-source server for activators that will allow them to get and store locally all active FCTs.

5) What do Human readable signing transactions mean & how does it work

Using EIP-712, we are able to present a readable message that the user signs. Inside the FCT - this message will be translated into the data that is sent to the blockchain.

6) What will the developer SDK include?

It will include a core library in typescript/javascript that will allow you to easily build and manage the FCT workflow, variables, etc. As well as a plug-in library with pre-built interfaces to the most popular protocols.

7) What Web2 coding languages are necessary to know?

In order to use our SDK you will need to know how to use JavaScript or TypeScript

8) What exactly is on-chain scripting?

On-chain scripting is the ability to transcode the sent message on-chain, in real-time, to a runnable EVM code

9) How much will it cost to create an FCT?

It depends on the complexity of the FCT (amount of calls inside it and the used protocols)

10) Once I have created an FCT, where is it held?

For efficiency purposes, we keep a copy of the FCTs on our servers for immediate access. A copy of each FCT will also be held in a decentralized storage similar to IPFS. And in addition to that - we plan to release an open-source server for activators that will allow them to get and store locally all active FCTs.

11) Can I reuse the same FCT or do I have to continually recreate it?

It’s possible to reuse the same FCT you have already created

12) How does the payment process work? Gas fees etc?

The payment mechanism is based on our tokenomics which can be found on our website.

13) Can an FCT fail? If so, what happens then?

Each FCT is examined before each run in order to make sure all the conditions are met. On the off chance that the FCT does fail, then it will run again in the next block.

14) Can you cancel an FCT?

Yes, until an FCT has been executed it can be canceled.

15) Can you make multiple FCTs that will run at the same time?


16) How will an FCT be activated?

FCT is activated by an activator (miner for FCT’s) and activators will be a part of the FCT eco-system and will be rewarded for their activations.

17) Are FCTs focused only on DeFi users or are there other use cases?

There are endless possibilities for using FCT’s, not only for DeFi.

Last updated