smart-contract-best-practices VS openzeppelin-contracts-upgradeable

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

v4.8.2 of OpenZeppelin contracts and contracts-upgradeable bug fix for ERC721Consecutive that could cause a balance overflow when _mintConsecutive was used for batches of size 1 breaking changes to ERC721: the internal function _beforeTokenTransfer will no longer update balances when batchSize is greater than 1

Yeah. That restriction is coming from a utility. There are options to modify the owner through transfer ownership on the `OwnableUpgradable` contract. You can also use the `reinitializer' modifier to create your own re-init logic.

Most smart contracts developers have used Openzeppelin/contracts. Those developers dabbling in Upgradeable smart contracts use its sister project Openzeppelin/contracts-upgradeable. The two are the same albeit the constructor in the contract is replaced by the initializer.

Here’s a few references: - https://openzeppelin.com/contracts/ - https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable (highly recommended)

https://github.com/OpenZeppelin/openzeppelin-contracts-upgra...

For KYC you'll need to implement your own ERC20 compatible token with some checks in the transfer functions. The CMTA is the Swiss contract reference and proposes one: