smart-contract-best-practices VS web3.js

Then i delved into best practises (https://consensys.github.io/smart-contract-best-practices/) and patterns (https://fravoll.github.io/solidity-patterns/) to improve.

Search for solidity exploits on Google, useful one: https://consensys.github.io/smart-contract-best-practices/ there are a lot of possible exploits so deploying one by yourself without audits is a no-go imo

Consensys' Smart Contract Best Practices is a good start for security related stuff (super important because you'll be dealing with people's money in smart contracts) https://consensys.github.io/smart-contract-best-practices/

The first question which any auditing interview concerns is mostly regarding what is your preferred audit process? Answers could be subjective, but I like to follow the industry standard as in this ‘Solcurity Standard’ article by Rari-Capital along with the Consensys’ best practices set of guidelines which pave a path for a thorough audit process.

Security should always be a major priority when developing smart contracts. Millions of dollars are lost to hackers on what seems like a regular basis. As a Web3 developer, you need to continuously stay up to date on the latest security best practices.

Solidity basics and best practices

Smart Contracts Best Practices

Web3.js (16500 GitHub Stars) https://github.com/web3/web3.js/

- https://github.com/web3/web3.js - Web3 JavaScript

last I checked web3.js only supports EVM coins / tokens. Was there an announcement I missed?

I have attempted to increase the maxReceivedFrameSize in my truffle-config, which is a solution offered here like so:

Here is a way to do this using web3.js.

Since we will build a Web3 example, the web3 framework was installed using npm (other options can be found here):

yeah, I could see that.

web3.js is a super bloated library and will be added more frequently unless a team does a more optimal version from scratch

https://github.com/ChainSafe/web3.js/issues/1178