Enlist the major difference between a contract and a library in Solidity?

In Solidity, a contract is a unit of code that can contain data and functions that can be invoked and interacted with. A contract can be used to represent a real-world entity, such as a token, an agreement, or a voting system.

while library is a collection of functions that can be called by other contracts or functions. Unlike contracts, libraries do not have their own state and cannot receive or send transactions. They are used to provide utility functions that can be shared across multiple contracts.

Here are some key differences between contracts and libraries in Solidity

• State: Contracts have their own state, which means they can store data and maintain a record of their interactions. Libraries do not have their own state and cannot store data.
• Transactions: Contracts can receive and send transactions, while libraries cannot.
• Instances: A contract can have multiple instances, each with its own unique state. Libraries cannot be instantiated and do not have their own state.
• Inheritance: Contracts can inherit from other contracts, while libraries cannot be inherited from.
• Functions: Both contracts and libraries can have functions, but the functions in a contract can change the state of the contract, while the functions in a library cannot.