Package: additive
Data structure for representing additive secret shares of integers, designed for use within secure multi-party computation (MPC) protocol implementations.PurposeThis library provides a data structure and methods that make it possible work withn-out-of-nadditive secret sharesof integers within secure multi-party computation (MPC) protocol implementations. Secret shares of signed and unsigned integers can be represented using elements from finite fields, with support currently limited to fields having a power-of-two order.Installation and UsageThis library is available as apackage on PyPI:python-mpipinstalladditiveThe library can be imported in the usual ways:importadditivefromadditiveimport*ExamplesThis library makes it possible to concisely construct multiple secret shares from an integer:>>>fromadditiveimportshares>>>(a,b)=shares(123)>>>(c,d)=shares(456)>>>((a+c)+(b+d)).to_int()579It is possible to specify the exponent in the order of the finite field used to represent secret shares, as well as whether the encoding of the integer should support signed integers:>>>(s,t)=shares(-123,exponent=8,signed=True)>>>(s+t).to_int()-123The number of shares can be specified explicitly (the default is two shares):>>>(r,s,t)=shares(123,quantity=3)Thesharedata structure supports Python’s built-in addition operators, enabling both operations on shares and concise reconstruction of values from a collection of shares:>>>(r+s+t).to_int()123>>>sum([r,s,t]).to_int()123In addition, conversion methods for Base64 strings and bytes-like objects are included to support encoding and decoding ofshareobjects:>>>fromadditiveimportshare>>>share.from_base64('HgEA').to_bytes().hex()'1e0100'>>>[s.to_base64()forsinshares(123)]['PvmKMG8=','PoJ1z5A=']DevelopmentAll installation and development dependencies are fully specified inpyproject.toml. Theproject.optional-dependenciesobject is used tospecify optional requirementsfor various development tasks. This makes it possible to specify additional options (such asdocs,lint, and so on) when performing installation usingpip:python-mpipinstall.[docs,lint]DocumentationThe documentation can be generated automatically from the source files usingSphinx:python-mpipinstall.[docs]cddocssphinx-apidoc-f-E--templatedir=_templates-o_source..&&makehtmlTesting and ConventionsAll unit tests are executed and their coverage is measured when usingpytest(see thepyproject.tomlfile for configuration details):python-mpipinstall.[test]python-mpytestAlternatively, all unit tests are included in the module itself and can be executed usingdoctest:pythonsrc/additive/additive.py-vStyle conventions are enforced usingPylint:python-mpipinstall.[lint]python-mpylintsrc/additiveContributionsIn order to contribute to the source code, open an issue or submit a pull request on theGitHub pagefor this library.VersioningThe version number format for this library and the changes to the library associated with version number increments conform withSemantic Versioning 2.0.0.PublishingThis library can be published as apackage on PyPIby a package maintainer. First, install the dependencies required for packaging and publishing:python-mpipinstall.[publish]Ensure that the correct version number appears inpyproject.toml, and that any links in this README document to the Read the Docs documentation of this package (or its dependencies) have appropriate version numbers. Also ensure that the Read the Docs project for this library has anautomation rulethat activates and sets as the default all tagged versions. Create and push a tag for this version (replacing?.?.?with the version number):gittag?.?.?gitpushorigin?.?.?Remove any old build/distribution files. Then, package the source into a distribution archive:rm-rfbuilddistsrc/*.egg-infopython-mbuild--sdist--wheel.Finally, upload the package distribution archive toPyPI:python-mtwineuploaddist/*