00:01.3 - 00:30.2 - Hello everyone, my name is Angel and I'm the CTO and co-founder of Finboot. Now I'm going to show you and give you a quick tour on our MARCO console in order to manage their MARCO resources for building your own bloating application or manager bloating environment. Once you have set up your own organization and projects in MARCO, you can select the project you want to work with here, we'll have selected the project you can start creating resources inside this project.
00:31.9 - 00:59.8 - The main resource you are going to create is an application, once you create an application we only need to set up a name and that will create an application for you. Once you have an application you are going to need to use the application token that you can see on the application Details page. This is the application token and it is intended to be used from MARCO API calls in order to identify your applications and who has access to your application.
01:00.9 - 01:06.9 - The application token is a secret value that is only allowed to be seen by a specific user.
01:09.2 - 01:37.1 - Another important resource are the plugins. The plugins will allow you to extend MARCO functionality. So for example, if you are going to connect to your own network or you want to start using a blockchain technology that is not still supported by Marco you can develop your own plug-in following our plugging interfaces more like to connect and use that new blockchain technology or even you can do use our custom plugin
01:37.2 - 02:05.2 - to redirect calls and API calls from MARCO to your plugin in order to extend functionality or work in a specific way that you want for example with a wallet or to connect to proxies, firewall Etc. You just need to set up a plugin URL and then MARCO will take care of redirecting those to your plugin via configurations. You can also add text to the plugin in order to retrieve information from MARCO once you are connected to the plugin.
02:07.1 - 02:35.5 - You also have the service account functionality and service account are identities that can be authenticated in MARCO in order to execute API calls with any kind of human interaction. Service account is intended to be used from Bobbi Brown services from servers or even from different IOT devices that don't need a human in order to execute that API call. If we register our service account, let's say my
02:35.6 - 03:05.5 - service account, we will be redirected to the service Account Details page where we will be able to set up the service account credentials. There are different types of credentials that you can use for a service account. For example, service account keys or service account API keys. Keys are private keys, that are downloaded to your device and are intended to be kept private and only read by the MARCO decay in order to authenticate this service account
03:05.8 - 03:35.5 - or you can create service account API Keys. Once you create an API Keys you can use that as the authorization header for API codes. You can also disable the API key if it is compromised or you want to rotate the key token for more improved security. You have the option to grant access to this specific service account to different applications in order for this service account to execute calls
03:35.6 - 04:05.4 - in this specific application. Another functionality is the Smart Contracts Templates where you can register a template or upload a smart contract code like solidity and it will be compiled and managed by MARCO. What you have as my contract template uploaded you can define different specifications but you can consider them to be different versions of your smart contract code. Once you have a specification uploaded it will be compiled by the Marco and after that you can
04:05.7 - 04:35.4 - use via API calls or via obvious from MARCO consult front end. The smart contract specification will allow you to deploy the contract on the network you want as long as it is compatible with the technology that the contract was built for. The deployment contract option allows you even to define and set up the parameters you need for this specific smart contract code and you can choose on what you judge you want to deploy it, again as long as it is compatible with the
04:35.6 - 05:05.4 - blockchain technology which my contract was introduced into. Once a smart contract is deployed it becomes a smart contract instance. A smart contract instance is the code, is the Smart contract that already exists on the blockchain with its own address transaction HASH and data. And you can come to the MARCO console to see the details of that is my contract, you can see of its was deployed, with its address on its Ledger on this transaction from this front
05:05.6 - 05:31.5 - you can also query the contract or see all of the transactions that has been executed on this as my contract also via API for example you can execute contract methods by using this smart contract instance ID or you can query this as my contract via APIs or SDK again using this instance idea and MARCO will know how to connect to the nodes where this instance can be rich.
05:33.2 - 06:01.2 - Also you have the Wallets. The Wallet, remember that MARCO does kind of private keys or wallet files that are managed and handled by plugins but they need to be registered on MARCO or MARCO can access them and really get close to the plugins. Other important features are the Explorer Nodes and Ledger. With Explorer Nodes and Ledger you can always register new networks that you want to work with.
06:02.8 - 06:22.4 - For example if you want to work with your own private Network or you have a production Network ready to be used you can register the nodes and ledger. In order to do that you will need to contact support or your account manager and if you have any questions about the MARCO console or how to build your blockchain application please don't hesitate to contact us, bye!
