Senior Software Consultant
SeasiaInfotechAssistant Manager
Grant Thornton Bharat LLPSenior Technology Consultant
Ernst and Young LLPSoftware Developer
Frugal Software Pvt LtdBlockchain Developer
Logictrix TechnologiesAssociate delivery level3
Smart Data EnterprisesNode.js
REST API
Jira
Slack
Skype
Figma
Postman
Visual Studio Code
MS Office
MS Word
MS Excel
MS PowerPoint
Docker
Kubernetes
Kafka
Truffle
Remix
Cryptography
JWT
Golang
Grafana
Prometheus
Jenkins
Travis CI
CouchDB
Kafka
Microservices
CI/CD pipelines
IPFS
Hardhat
Azure
AWS
Terraform
Git
JSON Web Token (JWT)
Hyperledger Fabric
Golang
Prometheus
Elasticsearch
Kibana
Logstash
Microservices
Solidity
GitLab
SQL
PostgreSQL
NoSQL
Terraform
C
C++
Java
HTML
React
CSS
Prisma
Vercel
Nodejs
Remix
Rust
MySQL
AWS
GitHub
CI/CD
Terraform
Foundry
Jira Software
Kafka
Prometheus
Lambda
EC2
S3
RDS
Trello
OpenZeppelin
Metamask
Next.js
100ms
React.js
Redux
HTML
CSS
Express.js
AWS
CI/CD
Terraform
AWS
GCP
SNS
SQS
Digital Ocean
Step Functions
API Gateway
GitHub
Ansible
Octopus
Podman
Terraform
Linux
Celery
XPath
MariaDB
Nginx
Gunicorn
Scrapy
Selenium
BeautifulSoup
Elastic Search
Tesseract
PyTorch
OpenCV
scikit-learn
Redis
Memcached
CircleCI
EKS
ECS
Stripe
OpenTelemetry
Jaeger
Jest
Mocha
Cypress
Kafka
RabbitMQ
Google Cloud
Yeah. My name is Chetan Churassay, and I'm and I belong to. I completed my BTech from University. University. And after completing my BTech, I start my career as a software developer from Frugal Software Private Limited. And, uh, in different types of technologies, I also work on JavaScript, TypeScript, Golang, Node. Js. And apart from this, uh, Docker Kubernetes, Hyperledger Fabric, Hyperledger Besu, and different types of blockchain, including public blockchain chain and private blockchain, and different types of tools, Jira, Dockers. And apart from this, Elasticsearch, Kibana, Lockstack, different types of technology, I also work. And in database site, MongoDB, GraphQL, PostgreSQL. And apart from this is some, uh, the cloud service side to Azure and Microsoft Azure and different desktop cloud platform. DevOps side, I also worked. So there's, you know and apart from this, basically, in my last project, I was also working on the design government project and health department. So different types of functionality, I also work, uh, and apart from this, basically, uh, different types of, you know, their RFP part, bidding process, their POC part, and these type of functionality, I also worked in in my last organization.
If we're talking about, you know, method to automatic withdrawal of funds running from a smart contract, So, you know, sometimes we can say that, you know, uh, by the re you know, recursing call function. The recursing call function are this type of methodology. So we create a function, and after that, recursing call function, basically, when we are executing, so at the time, what will be happen that automatically withdraw a fund from a smart contact to multiple beneficiaries. It it has been, uh, you know, implemented. And if we're talking about the challenges, I do you know, some different types of, you know, attacks type of problem just like, you know, uh, reentrancy attack and double spending problem. So these type of problem, it can be happen. So through this web, basically, uh, you know, proper indication with the help of the, you know, for loop we are using and different types of vulnerability, it already had been happened. So we have to do proper smart contact functionality over there when we are using these things. And through this web, basically, we can use and we can say that we can use the automatic withdrawal of fund from a smart contact to multiple
Yeah. If we're talking about in web 3 and dotjs to update the UI in real time with transaction confirmation from a blockchain site, To hear, basically, what can be happen that we are using event and log. And to in event and log, what was happening when we are creating a particular, you know, transaction, a particular, you know, the method. So particular things when we are using executing in in our In every event, basically, different types of modifiers, basically, we are using here. And if anything's missing so each, basically, the message, it will be, you know, occur in the message. It will show on the message to the front end part. Through this web where, basically, what can be happen that when the event is, you know, occurring, the different types of log they are generating and their logs are generating the databases. Right? But after occurring the event, the the particular message, it will be shown. So it will be shown on the front end part and through the front end side, the UI, it it will be get the real time data with the transaction confirmation that the different types of scenario, we can use the this type of event and logs. So we can say So we can say that this this type of things, basically, we can implement.
Yeah. If we're talking about, you know, elaborated designing a liquidity pool, smart contract, and the associate calculation for implementing an automated market maker. So here, just like, you know, if I created a Nifty token just like, uh, you know, I created a token, what is the token name, token symbol, the total token supply balance of method, transfer method, transfer from method, approval method, allowance method. So when we are creating a token, after that, basically, when we are launching our token on the liquidity pool, uh, to determine what can what what is happening, we are putting particular token with respect to to Ether just like if we are talking Dogecoin and we are putting the, uh, you know, Ether. So we have to put in 1 ish to 1 ratio. Just like if there are 500 those points and in 1 ether, there are 500 those points. So there are 500 those points, 1 ether. If there are another user, they are coming. They are putting 1 more Ether. So right now, there are 2 Ether. So 2 Ether multiply unknown dot unknown dotcom quantity should be constant. So from this way, basically, we can find out that how many Dogecoin are in 1 ether. So, always, we are putting in 1 is to 1 ratio in our liquidity pool. And after that, the calculation, they are happening they are happening automatically with the method of the automated market
What is a secure way to implement a anki time lock and a function in a smart contract, ensuring anki the tokens are only accessible after a certain block time to stamp. Okay. If we're talking about any secure way to implement a time long function in a smart contact, So in this scenario, basically, what what is happening that, you know, we just like we are calling any function. So after that, basically, we set out a time lock function just like, you know, if I created a particular tokens and after that, I created, uh, our liquidity pool. So in this liquidity pool, basically, we can set out the time log that have in certain period, basically, the owner who have more than, you know, 90% of the liquidity, 80% of the liquidity, so they cannot sell out the their token scheduling. So through this time lock function, basically, we can use our smart contract. And through this way, basically, we are ensuring that tokens are only accessible after a certain block time stamp. So here, if we're talking about in the liquidity pool side, just like if any liquidity pool creator to their more than 80%, 90% of their token, it will be on the locking period side. So before that, they cannot withdraw their token. So through this way, basically
Yeah. If you are talking about, you know, the concept of the upgradable smart contract things, in upgradable smart contract things, basically, we are using the, you know, proxy smart contract functionality just like I, uh, I already have deployed our smart contract. But if we want to do some changes over there so data, basically, we are using the upgradeable smart contract. In upgradeable smart contract, basically, we are not changing the entire blockchain with some ecosystem. Basically, we are changing some function. So at the time, basically, just like their existing smart contract, there is a new smart contract. So we will do some changes in our existing smart contract and the functionality, it will be reflected in our new smart contract. So we are using the concept of the delegate call functionality. The through the concept of the delegate call functionality, we can implement these things, the upgradeable smart contract. And through this way, basically, we don't require to deploy all the smart contract. We are upgrading some only functions and parameters in our
Uh, if we're talking about in this JavaScript, right, 3 core that interact with a blockchain network, describe what functionality intend to do, and point out any errors. So here, basically, we are, you know, using the webtree live webtree.ether and transaction library. And the particular, you know, amount is it transferring from particular one address to another address and how much value basically we are able to clear. And we are using the transaction hash to console dot log and after that. The transaction has basically, it is generating the transaction But after that, basically, the transaction has it will be remain in hexadecimal format. But for for the reading perspective, we have we have to use the ABA encode packet. So after using the ABA encode packet, we can solve out this problem. So through this way, we can solve out.
Due to solidiate function below, explain what the modifiers only owner is likely doing here. Here, basically, in this function, basically, we are using the only owner. Only owner means, basically, if we are using, you know, any changes in our smart contract side. Yeah. Any anything we want to choose, the only owner are the the main person who can deploy this function. If another person, basically if they will try to, you know, use this function, then they cannot do. Only owner who deploy this smart contract only can use this function. So that's the main, you know, and the logic, um, for using the only owner in this in this, um, smart contact call.
Yeah. I was talking you were talking about the approach for implementing a governance token with a DeFi protocol and voting and protocol changes. So, uh, basically, if I'm talking about in the governance token so first of all, basically, we will create a token. What is their token name, token symbol, their total token supply, their balance of method, transfer method, transfer from method, approval method, allowance and method. And after that, basically, when we are connecting to our d DeFi protocols, we will also use their liquidity pool concept. And according to that, basically, we will use the defi. And after that there, how much is rate of interest I will get to their yearly rate of interest and different as opened. Apart from this, the stacking concept, we can also put out. And we are putting our token, yeah, ether in a locking period time. The the time we will get some rate of interest. It will it's remaining that, we can say, the is tracking format. So this type of things, basically, we can do implementing our token. On. And after that, we can, you know, use the DeFi protocol and mechanism to enable voting and, um, protocol changes. If we're talking about in voting rights here, so when the people they are, you know, using, uh, the people they have buy our token and 2 different types of, you know, just like in coin market, KPI, coin decoy. And after they they after purchasing the coin, the coin, basically, it will be reflected in their wallet just like MetaMask or something. So in this scenario, basically, they have the voting rights. Voting rights mean different types of, you know if anything, say, they want to change in the particular token, the normal user, they have hold the token. So they have the voting rights. And after that, they can, you know, uh, they can participate in the voting rights, and they can choose the different types of task the entire community they want to do changes.
Yeah. If we are talking about the, you know, gas price for pending transaction in the network to optimize the gas fee when deploying a smart contract. So at that time, what was happening when when we are, you know, compiling our smart contract and for the deploying part. So and all these transaction, they are going on the mempool side. So in the mempool, basically, what was happening that in the mempool, there were people who will who will give more you know, the transaction fee or more guest fee over there. So that transaction, it will be give on the priority basis. So here, basically, if you are paying more, so there is a more chance to become succeed succeed very fastly. So this is the main concept for the gas price for pending transaction and the gas optima.
Yeah. If we're talking about in the DevOps, uh, practice side for continuously integration and deployment of blockchain application, So just like, you know yeah. If we're talking about, you know, in the DApps side, so different types of DApps tools. So, basically, we are also using just like I'm giving example of the private blockchain Hyperledger Fabric. So here, basically, in Hyperledger Fabric, different types of node, basically, I'm using here. So in this scenario, basically, I will use the DevOps to, like, a Docker Kubernetes as you like. So in Docker, basically, we have different types of images and cluster I can create. And different types of, you know, cluster, I can also run at the same time. So this is a, you know, different advantage of the the Dao. So, basically, we can say, and I will also recommend it for the continuous integration deployment of blockchain application. And apart from this, basically, the Elasticsearch, Logstex, Kibana, basically, I will also recommend these d those 2 lego. They will give the logs, current logs, and