# Smart contracts and GitHub Repo

## Smart Contracts

The Smart Contract is one of the fundamental components within a financial blockchain. The FomoETH contract serves as the digital agreement between engaging parties that is subsequently stored in the blockchain, solidifying prior transactions made on the chain. These contracts may be determined between two parties, through peer-to-peer (P2P), person-to-organisation (P2O) and person-to-machine (P2M) business.

&#x20;The FomoETH smart contracts work similarly to those on popular networks, whereby once a given criteria is fulfilled, the financial contract is automatically performed and the holder’s assets, where that be fiat money, digital currency, and other personal data, are then exchanged between the contracting parties. To prove the transaction occurred, the data is then replicated and validated on the Blockchain.

&#x20;Smart contracts allow individuals and organisations to exchange fiat and assets in an unprecedented format, opening up the possibility of disintermediating the entire legal system and establishing a new branch of virtual agreements.

&#x20;The Smart Contracts that contain all FomoETH on-chain transactions are key for user security assurance, keeping the tokens and NFTs minted on the FomoETH ecosystem safe from fraudulent persons and loss of data.



Smart Contracts:

{% embed url="https://bscscan.com/address/0x8A65B987D9813f0a97446eDa0dE918b2573Ae406#code" %}

{% embed url="https://etherscan.io/address/0x8a65b987d9813f0a97446eda0de918b2573ae406#code" %}

## GitHub Repo

The foundation of the FomoETH technology stems from the functionality of GitHub, which has the capability to fork (copy) a repository from one system to another. GitHub has allowed FomoETH to fork the ERC20 and repurpose the technology to create a project without re-writing any of the source code.

&#x20;Prior to the advent of GitHub, if developers wanted to contribute to an open-source project, they were required to manually download the project’s source code, make changes locally, create a list of changes called a “patch” and then email the patch to the project’s maintainer. The maintainer would then have to evaluate this patch, possibly sent by a total stranger, and decide whether to merge the changes.

&#x20;Even for maintainers who disregard the GitHub interface, it can still ease management. Lowering the barrier to entry democratizes open-source development, and helps young projects grow with a secure and supportive base.



GitHub Repo URL:

{% embed url="https://github.com/fomo-eth/Contract_ERC20" %}

{% embed url="https://github.com/fomo-eth/Contract_BEP20" %}

