Create smart_contracts.py

[shriyadindi]

Added the code that can prevent and detect vulnerabilities using Python and Solidity programming for Smart Contracts in Blockchain Technology.

Pull Request for PyVerse 💡

Requesting to submit a pull request to the PyVerse repository.

---

Issue Title

Please enter the title of the issue related to your pull request.
Adding Smart Contracts vulnerabilities prevention techniques

• I have provided the issue title.

---

Name

Please mention your name.
Shriya Dindi

• I have provided my name.

---

GitHub ID

Please mention your GitHub ID.
shriyadindi

• I have provided my GitHub ID.

---

Email ID

Please mention your email ID for further communication.
dindishriya@gmail.com

• I have provided my email ID.

---

Identify Yourself

Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, SWOC).
GSSOC

• I have mentioned my participant role.

---

Closes

Enter the issue number that will be closed through this PR.
*Closes: #814

• I have provided the issue number.

---

Describe the Add-ons or Changes You've Made

Give a clear description of what you have added or modified.
Added Formalistic Occurrences of Vulnerabilities in the Transactions of Smart Contracts In Blockchain project. Vulnerabilities like Timestamp validation, Reentrancy exploits and overflow conditions will be detected and prevented in this project. I want to add this to the blockchain development section.

• I have described my changes.

---

Type of Change

Select the type of change:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

---

How Has This Been Tested?

Describe how your changes have been tested.
Describe your testing process here.

• I have described my testing process.

---

Checklist

Please confirm the following:

• My code follows the guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly wherever it was hard to understand.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added things that prove my fix is effective or that my feature works.
• Any dependent changes have been merged and published in downstream modules.

[github-actions]

👋 Thank you for opening this pull request! We're excited to review your contribution. Please give us a moment, and we'll get back to you shortly!

Feel free to join our community on Discord to discuss more!

[shriyadindi]

@UTSAVS26 kindly add a level 2 badge for this, as it is IOCL approved project.

[UTSAVS26]

@UTSAVS26 kindly add a level 2 badge for this, as it is IOCL approved project.

You are adding project that's why it comes under level1 category.

[ruhi47]

Hey @shriyadindi ,
Please a README file that has details about dependencies, program working and others if needed.
Uploading a project to an open-source repository with a README file is generally considered a good practice.
Thanks!

[shriyadindi]

@ruhi47 I've added it here
#1131