Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


Statistics on serpent

Number of watchers on Github 262
Number of open issues 61
Average time to close an issue 25 days
Main language C++
Average time to merge a PR 6 days
Open pull requests 23+
Closed pull requests 9+
Last commit about 2 years ago
Repo Created over 5 years ago
Repo Last Updated over 1 year ago
Size 3.4 MB
Organization / Authorethereum
Contributors13
Page Updated
Do you use serpent? Leave a review!
View open issues (61)
View serpent activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating serpent for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

Introduction

Serpent is an assembly language that compiles to EVM code that is extended with various high-level features. It can be useful for writing code that requires low-level opcode manipulation as well as access to high-level primitives like the ABI.

Being a low-level language, Serpent is NOT RECOMMENDED for building applications unless you really really know what you're doing. The creator recommends Solidity as a default choice, LLL if you want close-to-the-metal optimizations, or Viper if you like its features though it is still experimental.

Installation:

make && sudo make install

Testing

Testing is done using pytest and tox.

$ pip install tox -r requirements-dev.txt

To run the test suite in your current python version:

$ py.test

To run the full test suite across all supported python versions:

$ tox
serpent open issues Ask a question     (View All Issues)
  • about 3 years Serpent: Redundant btyecode
  • over 3 years Add latest develop code to PyPi
  • over 3 years Unable to Install
  • over 3 years Too many array index lookups. I cannot run anything
  • over 3 years The `def code` function doesn't compile correctly.
  • over 3 years 2^256 == 0, 2^255 == -578...
  • over 3 years Python 3 support
  • almost 4 years function to return uint256 requires all code paths to return uint256
  • almost 4 years master (1.6.7) is broken? merge develop (2.0.2)?
  • almost 4 years version tagging in git?
  • about 4 years serpent not generating correct ABI for a method with a return
  • over 4 years preprocessing stage and macro evaluation stage
  • over 4 years macro substitution in init()
  • over 4 years init() doesn't call functions defined in an inset()
  • over 4 years Does ``return`` only return a single 256 bit word?
  • over 4 years Potential optimizations
  • over 4 years Private functions? The danger of exposing functions?!
  • over 4 years space saver
  • over 4 years inset() is changing behavior of function that writes to storage
  • over 4 years Using log(data=a) with an array prints each byte, not each item
  • almost 5 years collatz example is broken
  • almost 5 years Add NatSpec support
  • almost 5 years behavior when refactoring inset to extern
  • almost 5 years how to return array containing an array
  • almost 5 years broken compilation
  • almost 5 years Loops of Length 311 are Too Big for init Functions
  • almost 5 years help installing serpent please
  • about 5 years Segmentation fault when rewriting
  • about 5 years Compiler doesnt spot nonexistant variables.
  • about 5 years examples/quicksort_pairs.py gives wrong results
serpent open pull requests (View All Pulls)
  • fix ETH/USD conversion in SchellingDollar example
  • Build on Windows (develop)
  • Build on Windows
  • Add a Gitter chat badge to README.md
  • Add Omni Currency Example
  • Python3 support
  • add tutorial
  • addr is never defined using variable k instead...
  • Left sided string, fixing inconsistency with Alethzero(#5)
  • fix: #9
  • fixed py3 incompatibility
  • fixed py3 incompatibility
  • Piper/add travis ci testing
  • fixed py3 incompatibility
  • Fix pretty_compile command
  • Fixed ecc tests (except --ringsig) by adding uint256 type annotations
  • Fix setup on pypy which doesn't export OPT env
  • what is?
  • Fix for Makefile
  • Added install_requires: `future` package
  • Add the packaging metadata to build the serpent snap
  • Support DESTDIR in the Makefile
  • Vyper, not Viper
serpent questions on Stackoverflow (View All Questions)
  • Encryption and decryption with Serpent using Crypto++ and Bouncy Castle?
  • Serpent GCM bouncy castle implementation is very slow on Android
  • Using Serpent or TwoFish C# example?
  • AES, Serpent or Twofish in C example?
  • Serpent/CBC/NoPadding (BouncyCastle) not working correctly
  • Serpent Cipher ONLY in BitSlice performs wrong calculations
  • Serpent and Twofish library C
  • Serpent Implementation in Crypto++
  • Serpent Sbox transformation
  • truecrypt bug in serpent implementation
  • serpent encryption - better than rijndael?
  • Using the serpent serializer for safe object pickling
  • freehand drawing class for serpent line
  • How do you generate a PBEKey for Serpent in Java?
  • How to use/wrap Serpent/blowfish/whirlpool Encryption Engine Code?
serpent list of languages used
Other projects in C++