Solidity, the Smart Contract Programming Language
Go to file
rainbeam 76473808b4 wrap lllc add_executable
Allows static linking.
2016-05-01 00:43:03 +01:00
docs Typo fix 2016-04-11 22:53:26 -05:00
libevmasm Windows fix. 2016-04-21 16:13:39 +02:00
liblll Remove log.h from solidity. 2016-04-12 01:03:46 +02:00
libsolidity Windows fix. 2016-04-21 16:13:39 +02:00
lllc wrap lllc add_executable 2016-05-01 00:43:03 +01:00
solc Source location for inline assembly. 2016-04-19 18:35:21 +02:00
test Merge pull request #507 from chriseth/sealEngine 2016-04-15 15:06:32 -04:00
.gitignore Added docs/utils/__pycache__ to .gitignore when building docs with Python 3 2016-02-18 10:27:14 +01:00
CMakeLists.txt Version change. 2016-04-18 17:33:11 +02:00
LICENSE Initial commit 2015-08-17 14:27:26 +02:00
README.md Update README.md 2015-12-07 23:40:12 +01:00

The Solidity Contract-Oriented Programming Language

Join the chat at https://gitter.im/ethereum/solidity

To get started you can find a basic introduction to the language in the Solidity Documentation.

You can start using Solidity in your browser with no need to download or compile anything. This application only supports compilation - if you want to inject it into the blockchain, you have to use a client like Geth or AlethZero.

Also check out more documentations for Solidity ABI and a crowdfunding example contract written in Solidity.

Changelog

The Solidity Features page contains a list of already completed Solidity feature stories with explanations and demonstrations, it is being updated continuously. More technical information you can find in the Pivotal Tracker.

Solidity is still under development. So please do not hesitate and open an issue in github if you encounter anything strange.

Building

See the Wiki for build instructions, compatibility information and build tips.

How to Contribute

External Contributors

I hereby place all my contributions in this codebase under an MIT licence, as specified here.

  • Name Surname (email@domain)

Contribution guideline

Please add yourself in the @author doxygen section of the file your are adding/editing with the same wording as the one you listed yourself in the external contributors section above, only replacing the word contribution by file

Please read CodingStandards.txt thoroughly before making alterations to the code base. Please do NOT use an editor that automatically reformats whitespace away from astylerc or the formatting guidelines as described in CodingStandards.txt.