Develop

.github/issue_template.md

@@ -0,0 +1,17 @@
+### Steps to reproduce
+
+### Expected behavior
+<!-- Tell us what should happen -->
+
+### Actual behavior
+<!-- Tell us what happens instead -->
+
+### System configuration
+
+#### Incubed version
+
+#### Request
+
+#### Incubed Configuration
+
+#### Chain

.github/pull_request_template.md

@@ -0,0 +1,17 @@
+### Summary
+
+<!-- Provide a general description of the code changes in your pull
+request... were there any bugs you had fixed? If so, mention them. If
+these bugs have open GitHub issues, be sure to tag them here as well,
+to keep the conversation linked together. -->
+
+### Other Information
+
+<!-- If there's anything else that's important and relevant to your pull
+request, mention that information here. This could include
+benchmarks, or other information.
+
+Finally, if your pull request affects documentation or any non-code
+changes, please explain.
+
+Thanks for contributing to incubed! -->

.gitignore

@@ -20,4 +20,7 @@ cmake-build-debug/
 [._]s[a-rt-v][a-z]
 [._]ss[a-gi-z]
 [._]sw[a-p]
-
+.gradle/
+bin/
+.classpath
+.project

.gitlab-ci.yml

@@ -188,6 +188,19 @@ analyse:
     paths:
       - report
 
+cppcheck:
+  stage: test
+  image: docker.slock.it/build-images/cmake:gcc-x86-static-analysis
+  allow_failure: true
+  tags:
+    - short-jobs
+  script:
+    - mkdir _build
+    - cd _build
+    - cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_BUILD_TYPE=Release ..
+    - cd ..
+    - cppcheck  --project=_build/compile_commands.json -i/builds/in3/c/in3-core/test/unity -i/builds/in3/c/in3-core/src/third-party
+
 test_c:
   image: docker.slock.it/build-images/cmake:gcc8
   stage: test
@@ -430,6 +443,7 @@ readthedocs:
   stage: test
   tags:
     - short-jobs
+  allow_failure: true
   dependencies:
     - gcc8
   script:
@@ -638,6 +652,7 @@ release_win:
     paths:
       - in3-win
 
+
 release_maven:
   stage: deploy
   image: docker.slock.it/build-images/maven-deployment-image:latest
@@ -655,6 +670,31 @@ release_maven:
     - echo $MAVEN_SETTINGS > settings.xml
     - mvn -s settings.xml deploy:deploy-file -DgroupId=it.slock  -DartifactId=in3 -Dversion=$CI_COMMIT_TAG  -Dpackaging=jar -Dfile=java_build/lib/in3.jar  -DrepositoryId=github -Durl=https://maven.pkg.github.com/slockit/in3-c
 
+release_pip:
+  stage: deploy
+  image: docker.slock.it/build-images/python-dev-image:latest
+  tags:
+    - short-jobs
+  only:
+    - /^v[0-9]+.[0-9]+.[0-9]+(\-RC[0-9]+)?$/
+  except:
+    - branches
+  dependencies:
+    - mac_os
+  script:
+    - rm -rf src/bindings/python/in3/bind/slibs/
+    - mkdir src/bindings/python/in3/bind/slibs/
+    - cp mac_build/lib/libin3.dylib src/bindings/python/in3/bind/slibs/.
+    - export version=${CI_COMMIT_TAG}
+    - export download_url=https://github.com/slockit/in3-c/releases/download/${CI_COMMIT_TAG}/in3_${CI_COMMIT_TAG}_mac.tar.gz
+    - cd src/bindings/python
+    - cp $pypirc ~/.pypirc
+    - ./publish.sh
+  artifacts:
+    paths:
+      - in3-pip
+
+
 pages:
   stage: deploy
   only:
@@ -848,3 +888,5 @@ github_body_release:
     - cat in3-arm7/arm7_release_ipfs_hash.txt >> release_ipfs_hash.txt
     - cat in3-win/win_release_ipfs_hash.txt >> release_ipfs_hash.txt
     - ghr -u slockIt -r in3-c -b "$(cat release_ipfs_hash.txt)" $CI_COMMIT_TAG release_ipfs_hash.txt
+
+

.settings/org.eclipse.buildship.core.prefs

@@ -0,0 +1,2 @@
+connection.project.dir=
+eclipse.preferences.version=1

.settings/org.eclipse.jdt.core.prefs

@@ -0,0 +1,13 @@
+#
+#Mon Jan 13 14:01:51 CET 2020
+org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
+org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
+org.eclipse.jdt.core.compiler.codegen.targetPlatform=13
+org.eclipse.jdt.core.compiler.source=13
+org.eclipse.jdt.core.compiler.debug.localVariable=generate
+org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve
+eclipse.preferences.version=1
+org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
+org.eclipse.jdt.core.compiler.debug.lineNumber=generate
+org.eclipse.jdt.core.compiler.compliance=13
+org.eclipse.jdt.core.compiler.debug.sourceFile=generate

.vscode/launch.json

@@ -47,6 +47,20 @@
             ],
             "cwd": "${workspaceFolder}/build"
         },
+        {
+            "type": "lldb",
+            "request": "launch",
+            "name": "run binary test",
+            "program": "${workspaceFolder}/build/test/test_binary_encoding",
+            "cwd": "${workspaceFolder}/build"
+        },
+        {
+            "type": "lldb",
+            "request": "launch",
+            "name": "run ethapi test",
+            "program": "${workspaceFolder}/build/test/test_ethapi",
+            "cwd": "${workspaceFolder}/build"
+        },
         {
             "type": "lldb",
             "request": "launch",

.vscode/settings.json

@@ -81,7 +81,10 @@
         "deque": "cpp",
         "memory": "cpp",
         "streambuf": "cpp",
-        "__node_handle": "c"
+        "__node_handle": "c",
+        "cstdlib": "c",
+        "locale": "c",
+        "eth_call_response_binary.h": "c"
     },
     "C_Cpp.errorSquiggles": "Disabled"
 }

CMakeLists.txt

@@ -126,7 +126,7 @@ IF (SEGGER_RTT)
     ADD_DEFINITIONS(-DSEGGER_RTT)
 ENDIF (SEGGER_RTT)
 
-OPTION(FILTER_NODES "if true the nodelist is filtered against config node properties" false)
+OPTION(FILTER_NODES "if true the nodelist is filtered against config node properties" OFF)
 IF (FILTER_NODES)
     MESSAGE(STATUS "Enable nodelist filter based on properties")
     ADD_DEFINITIONS(-DFILTER_NODES)

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,96 @@
+# How to contribute
+
+I'm really glad you're reading this, because we need volunteer developers to help this project come to fruition.
+
+If you haven't already, come find us in Gitter [![Gitter](https://img.shields.io/badge/Gitter-chat-blue)](https://gitter.im/slockit-in3/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge). We want you working on things you're excited about.
+
+Here are some important resources:
+
+ * [ReadTheDocs](https://in3.readthedocs.io/en/latest/)
+ * [C API reference](https://in3.readthedocs.io/en/latest/api-c.html)
+ * [C examples](https://in3.readthedocs.io/en/latest/api-c.html#examples)
+ * [in3-node](https://github.com/slockit/in3-server)
+ * [in3 typescript client](https://github.com/slockit/in3)
+ * [Website](https://slock.it/incubed/) 
+ * [Blog](https://blog.slock.it/)
+ * [Incubed concept video by Christoph Jentzsch](https://www.youtube.com/watch?v=_vodQubed2A)
+ * [Ethereum verification explained by Simon Jentzsch](https://www.youtube.com/watch?v=wlUlypmt6Oo)
+
+ [![Twitter](https://img.shields.io/badge/Twitter-Page-blue)](https://twitter.com/slockitproject?s=17)
+ [![Blog](https://img.shields.io/badge/Blog-Medium-blue)](https://blog.slock.it/)
+ [![Youtube](https://img.shields.io/badge/Youtube-channel-blue)](https://www.youtube.com/channel/UCPOrzp3CZmdb5HJWxSjv4Ig)
+ [![LinkedIn](https://img.shields.io/badge/Linkedin-page-blue)](https://www.linkedin.com/company/10327305)
+ [![Gitter](https://img.shields.io/badge/Gitter-chat-blue)](https://gitter.im/slockit-in3/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) 
+
+
+## Testing
+
+We also welcome any feedback of how you use it and what kind of challenges you may face. So when testing incubed let us know. 
+Also if you want to increase our testbase, feeld free to create more test data in our testrequests.
+
+## Submitting changes
+
+Please send a [GitHub Pull Request to incubed](https://github.com/slockit/in3-c/pull/new/develop) with a clear list of what you've done. Please follow our coding conventions (below) and make sure all of your commits are atomic (one feature per commit).
+
+Always write a clear log message for your commits. One-line messages are fine for small changes, but bigger changes should look like this:
+
+    $ git commit -m "A brief summary of the commit
+    > 
+    > A paragraph describing what changed and its impact."
+
+## Coding conventions
+
+Start reading our code and you'll get the hang of it. We optimize for readability:
+
+  * for code-formating use the [clang-format](https://github.com/slockit/in3-c/blob/master/.clang-format) provided in the repository
+  * This is open source software. Consider the people who will read your code, and make it look nice for them. It's sort of like driving a car: Perhaps you love doing donuts when you're alone, but with passengers the goal is to make the ride as smooth as possible.
+
+## Company Contribution License Agreement
+
+For us to accept your Pull Request, we need to ask you to agree to the following Contribution License Agreement:
+
+In order to clarify the intellectual property license granted with Contributions from any person or entity, Blockchains, LLC (**“Company”**) must have a Contributor License Agreement (**“CLA”**) on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for Your protection as a Contributor as well as the protection of Company and its users; it does not change Your rights to use Your own Contributions for any other purpose.
+
+This CLA allows either an individual or an entity (the “Corporation”) to submit Contributions to Company, to authorize Contributions submitted by its employees or agents to Company (in the case of a Corporation), and to grant copyright and patent licenses thereto.
+
+If You have not already done so, please complete and sign, then scan and email a PDF file of this CLA to [email protected].  Please read this document carefully before signing and keep a copy for your records.
+
+Name of Individual or Corporation:__________________________________________
+
+Mailing address:________________________________________________________
+
+Country:_______________________________________________________________
+
+Telephone:_____________________________________________________________
+
+E-Mail:________________________________________________________________
+
+You accept and agree to the following terms and conditions for Your present and future Contributions submitted to Company. Except for the license granted herein to Company and recipients of software distributed by Company, You reserve all right, title, and interest in and to Your Contributions.
+
+1.	Definitions.
+**“You”** (or **“Your”**) shall mean you as an individual (if you are signing this CLA on your own behalf) or the Corporation (if the person signing this CLA is acting on behalf of the Corporation) that is making this CLA with Company. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor and this CLA shall apply to Contributions by all such entities. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+“Contribution” shall mean the code, documentation or other original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to Company for inclusion in, or documentation of, any of the products owned or managed by Company (the “Work”). For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to Company or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, Company for the purpose of discussing and improving the Work, but excluding any communication that is conspicuously marked or otherwise designated in writing by You as “Not a Contribution.”
+
+2.	Grant of Copyright License. Subject to the terms and conditions of this CLA, You hereby grant to Company and to recipients of software distributed by or on behalf of Company a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.
+
+3.	Grant of Patent License. Subject to the terms and conditions of this CLA, You hereby grant to Company and to recipients of software distributed by or on behalf of Company a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any person or entity institutes patent litigation against You or any other person or entity (including a cross-claim or counterclaim in a lawsuit) alleging that Your Contribution, or the Work to which You have contributed, constitutes direct or indirect patent infringement, then any patent licenses granted to that person or entity under this CLA for that Contribution or Work shall terminate as of the date such litigation is filed.
+
+4.	You represent that You have sufficient rights and are legally entitled to grant the above licenses with respect to each Contribution. If this CLA is being made on behalf of the Corporation, the individual signing this CLA represents that he or she is authorized to do so on behalf of the Corporation to enter into this CLA, and the Corporation represents further that each employee or agent of the Corporation designated by it is authorized to submit Contributions on behalf of the Corporation. If You are making the Contribution as an individual, and if Your present or past employer(s) or other entities for whom you have performed work has rights to intellectual property that You create that includes Your Contributions, You represent that You have received permission to make Contributions on behalf of that employer or such other entity, that Your employer or such other entity has waived such rights for Your Contributions to Company, or that Your employer or such other entity has executed a separate CLA with Company.
+
+5.	You represent that each of Your Contributions is Your original creation (see section 8 for submissions that are not Your original creation).
+
+6.	Based on the grant of the rights in sections 2 and 3, You acknowledge and agree that we may license Your Contributions under any license, including copyleft, permissive, commercial, or proprietary license.   
+
+7.	You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
+
+8.	Should You wish to submit work that is not Your original creation, You may submit it to Company separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which You are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".
+
+9.	You agree to notify Company of any facts or circumstances of which You become aware that would make these representations inaccurate in any respect.
+
+10.	This CLA and any action related thereto will be governed by the laws of England without regard to its conflict of laws provisions. Exclusive jurisdiction and venue for actions related to this CLA will be a court of competent jurisdiction in London, England, and both parties consent to the jurisdiction of such courts with respect to any such actions. If this CLA is modified or updated by Company, Company will notify You of such updates on Company GitHub portal or will notify You via Your registered email address or via Your GitHub account (if applicable). If You do not reject the update and send Your rejection to Company within five (5) business days after Company notifies You of the change to the CLA then You will be deemed to have accepted the changed terms to the CLA. 
+
+
+
+Thanks,
+
+Your Incubed Team