Artax2.1

artaxcommittee · Mar 20, 2019 · d73d7ce · d73d7ce
commit d73d7ce
Show file tree

Hide file tree

Showing 1,315 changed files with 295,703 additions and 0 deletions.
diff --git a/.travis.yml b/.travis.yml
@@ -0,0 +1,82 @@
+sudo: required
+dist: trusty
+
+#workaround for https://github.com/travis-ci/travis-ci/issues/5227
+addons:
+  hostname: artax-tester
+
+os: linux
+language: generic
+cache:
+  directories:
+  - depends/built
+  - depends/sdk-sources
+  - $HOME/.ccache
+env:
+  global:
+    - MAKEJOBS=-j3
+    - RUN_TESTS=false
+    - CHECK_DOC=0
+    - CHECK_LOGPRINT=0
+    - BOOST_TEST_RANDOM=1$TRAVIS_BUILD_ID
+    - CCACHE_SIZE=100M
+    - CCACHE_TEMPDIR=/tmp/.ccache-temp
+    - CCACHE_COMPRESS=1
+    - BASE_OUTDIR=$TRAVIS_BUILD_DIR/out
+    - SDK_URL=https://bitcoincore.org/depends-sources/sdks
+    - PYTHON_DEBUG=1
+    - WINEDEBUG=fixme-all
+  matrix:
+# ARM
+#    - HOST=arm-linux-gnueabihf PACKAGES="g++-arm-linux-gnueabihf" GOAL="install" BITCOIN_CONFIG="--enable-glibc-back-compat --enable-reduce-exports"
+# Win32
+    - HOST=i686-w64-mingw32 DPKG_ADD_ARCH="i386" DEP_OPTS="NO_QT=1" PACKAGES="python3 nsis g++-mingw-w64-i686 wine1.6 bc" RUN_TESTS=true GOAL="install" BITCOIN_CONFIG="--enable-reduce-exports"
+# 32-bit + dash
+    - HOST=i686-pc-linux-gnu PACKAGES="g++-multilib bc python3-zmq" DEP_OPTS="NO_QT=1" RUN_TESTS=true GOAL="install" BITCOIN_CONFIG="--enable-zmq --enable-glibc-back-compat --enable-reduce-exports LDFLAGS=-static-libstdc++" USE_SHELL="/bin/dash" PYZMQ=true
+# Win64
+    - HOST=x86_64-w64-mingw32 DPKG_ADD_ARCH="i386" DEP_OPTS="NO_QT=1" PACKAGES="python3 nsis g++-mingw-w64-x86-64 wine1.6 bc" RUN_TESTS=true GOAL="install" BITCOIN_CONFIG="--enable-reduce-exports"
+# artaxd
+    - HOST=x86_64-unknown-linux-gnu PACKAGES="bc python3-zmq" DEP_OPTS="NO_QT=1 NO_UPNP=1 DEBUG=1" RUN_TESTS=true GOAL="install" BITCOIN_CONFIG="--enable-zmq --enable-glibc-back-compat --enable-reduce-exports CPPFLAGS=-DDEBUG_LOCKORDER" PYZMQ=true
+
+# No wallet
+#    - HOST=x86_64-unknown-linux-gnu PACKAGES="python3" DEP_OPTS="NO_WALLET=1" RUN_TESTS=true GOAL="install" BITCOIN_CONFIG="--enable-glibc-back-compat --enable-reduce-exports"
+# Cross-Mac
+    - HOST=x86_64-apple-darwin11 PACKAGES="cmake imagemagick libcap-dev librxax2-bin libz-dev libbz2-dev libtiff-tools python-dev" BITCOIN_CONFIG="--enable-reduce-exports" OSX_SDK=10.11 GOAL="deploy"
+
+before_install:
+    - export PATH=$(echo $PATH | tr ':' "\n" | sed '/\/opt\/python/d' | tr "\n" ":" | sed "s|::|:|g")
+install:
+    - if [ "$PYZMQ" = "true" ]; then pip install pyzmq --user ; fi
+    - if [ -n "$PPA" ]; then travis_retry sudo add-apt-repository "$PPA" -y; fi
+    - if [ -n "$DPKG_ADD_ARCH" ]; then sudo dpkg --add-architecture "$DPKG_ADD_ARCH" ; fi
+    - if [ -n "$PACKAGES" ]; then travis_retry sudo apt-get update; fi
+    - if [ -n "$PACKAGES" ]; then travis_retry sudo apt-get install --no-install-recommends --no-upgrade -qq $PACKAGES; fi
+before_script:
+    - unset CC; unset CXX
+    - if [ "$CHECK_DOC" = 1 ]; then contrib/devtools/check-doc.py; fi
+    - if [ "$CHECK_LOGPRINT" = 1 ]; then contrib/devtools/logprint-scanner.py; fi
+    - mkdir -p depends/SDKs depends/sdk-sources
+    - if [ -n "$OSX_SDK" -a ! -f depends/sdk-sources/MacOSX${OSX_SDK}.sdk.tar.gz ]; then curl --location --fail $SDK_URL/MacOSX${OSX_SDK}.sdk.tar.gz -o depends/sdk-sources/MacOSX${OSX_SDK}.sdk.tar.gz; fi
+    - if [ -n "$OSX_SDK" -a -f depends/sdk-sources/MacOSX${OSX_SDK}.sdk.tar.gz ]; then tar -C depends/SDKs -xf depends/sdk-sources/MacOSX${OSX_SDK}.sdk.tar.gz; fi
+    - make $MAKEJOBS -C depends HOST=$HOST $DEP_OPTS
+script:
+    - export TRAVIS_COMMIT_LOG=`git log --format=fuller -1`
+    - if [ -n "$USE_SHELL" ]; then export CONFIG_SHELL="$USE_SHELL"; fi
+    - OUTDIR=$BASE_OUTDIR/$TRAVIS_PULL_REQUEST/$TRAVIS_JOB_NUMBER-$HOST
+    - BITCOIN_CONFIG_ALL="--disable-dependency-tracking --prefix=$TRAVIS_BUILD_DIR/depends/$HOST --bindir=$OUTDIR/bin --libdir=$OUTDIR/lib"
+    - depends/$HOST/native/bin/ccache --max-size=$CCACHE_SIZE
+    - test -n "$USE_SHELL" && eval '"$USE_SHELL" -c "./autogen.sh"' || ./autogen.sh
+    - ./configure --cache-file=config.cache $BITCOIN_CONFIG_ALL $BITCOIN_CONFIG || ( cat config.log && false)
+    - make distdir PACKAGE=bitcoin VERSION=$HOST
+    - cd bitcoin-$HOST
+    - ./configure --cache-file=../config.cache $BITCOIN_CONFIG_ALL $BITCOIN_CONFIG || ( cat config.log && false)
+    - make $MAKEJOBS $GOAL || ( echo "Build failure. Verbose build follows." && make $GOAL V=1 ; false )
+    - export LD_LIBRARY_PATH=$TRAVIS_BUILD_DIR/depends/$HOST/lib
+    - if [ "$RUN_TESTS" = "true" ]; then make $MAKEJOBS check VERBOSE=1; fi
+    #- if [ "$RUN_TESTS" = "true" ]; then qa/pull-tester/rpc-tests.py --coverage; fi
+after_script:
+    - echo $TRAVIS_COMMIT_RANGE
+    - echo $TRAVIS_COMMIT_LOG
+notifications:
+  slack:
+    secure: w22XjHoG/3xplxWzddS9Ma7i99Q/hq4FA3Q56xS+RtO2vlFgDT+eDzCppstdx96mn2/4e+/V1aiQ4E6GVEvJMeldqSUhPv9OBnKR0KJVAOwu4haNXt+0ZeQFt8lIndKB5cMVyOJkoq6peGoHNXslClM0lGuBn7g7VC2QPQYNWrJNrrGL7IiVb6fNOIKHWcC4URkzSvXAhO/WIqSSlmKxAAx0B2oEsM8LhdAbcjbp7Sm7zH87TIVGBZ7iTVuMc6B9+SfClbE8bBuRtvjTX57Q4UUZzn0zDtKdPdCte0oXdaQF4RdVim9mDodBGIpDo+avW4WL7EE+AK33fs94pwH5bu0LEandR/aeEvVpbSpQ2XsEKSe+6woizgl5i4GXFVZduJF62y/o1f+S/zC3qW9lIEEpiZc4PpX7pDy30X3p6S5nMrW7T/zNh+SjLhS1VP6XKdQtpD3WRCY4GKZYammZhk5RbOy3jTXAahIXuttWdhl/Q3Rb5VqfFJWlrG/qQXt73qOk2/DgJnABxXE6gnWO4MpHAq+kdomNR+nod4HeXI3DOk1wRuQRVoW1rSjiqQd6Db+TP56RKYgt4M4csOD0DG9G+W0AOtZkuKHTeoEtmQfkKFPZLYAQumv41cDN2UE9gKIECmvJSevj4sMCDTWtozKWqay/W4n2+cmhbzmGflY=
diff --git a/ARTAX_COMMITTEE.md b/ARTAX_COMMITTEE.md
@@ -0,0 +1,80 @@
+ARTAX COMMITTEE   - Artax [NO ICO] Community driven coin.
+
+Establishment of steering committee for proposal implementation and planning
+
+v1.2
+
+Preamble 
+
+This proposal aims to establish a committee of node holders, developers and skilled community members to spearhead, develop, research and action proposals put forward for the future of the respective coins.
+
+As a coin requires technical modification or direction or structural changes, a proposal for this would be tabled to the committee and approved or rejected by a voting process wherein each committee member holds a voting right. Once approval is reached, the committee will transparently manage and report on the status of the proposal through action to completion.
+For proposals that are deemed large enough in scope to require a community voting process, the proposal must first pass committee vote prior to a community vote taking place. This ensures only proposals that are deemed meritorious are presented to master-node holders or the community at large.
+
+Committee formation, management and requirements.
+
+All committee member seats are voluntary positions and they will not be paid for any committee related activities. 
+The initial committee selection will be advertised by announcements in the various coin channels inviting interested parties to submit an application to the developers via a public channel. Applications should include brief outlines of experience, skillsets, knowledge base and may be asked for a brief interview in discord or other method to verify their credentials and experience. This is to ensure that the committee contains a range of different experience, knowledge and perspectives. 
+
+Initially, the developers will collectively choose suitable candidates based on those applications whom they wish to allocate the initial committee seats to. This will form the initial committee.
+
+- 	Committee members may step down from their seats at any time without obligation.
+- 	Committee members can also vote to remove a sitting committee member. The member will be voted out if a majority of 75% eligible vote is reached.
+- 	New committee members may be sourced by application or recommendation and must be approved by a vote amongst existing members prior to acceptance as a committee member.
+
+Each committee member has an equal vote which is based on 100% (total voting rights) divided by the total number of active committee members. 
+
+All committee members are required to vote on tabled proposals within a deadline which is stated with the tabled proposal (see below), after which if they have not voted, a null vote is recorded. 51% of any remaining eligible vote must be passed to pass the tabled proposal.
+
+Example: 
+-	3 community members with 5% voting rights each abstain from or miss voting
+-	total remaining eligible vote is 85%
+-	51% of 85% or 43% is required to pass
+
+Proposal process, handling, approvals and rejection.
+
+Proposals can be sourced directly if a specific need exists or arises or if ideas or opportunities to improve are bought to the attention of a committee members that warrants a proposal being put forth.
+Proposals are a call to a vote and also a call to research, validate and confirm the reasoning contained within the proposal as being an appropriate step to take with the coin.
+
+Any active committee member can put forward a proposal to be tabled.
+For a proposal to be tabled, it must include:
+a)	A summary of the proposal
+b)	Any supporting evidence or data
+c)	Any recommendations
+d)	Timelines required to vote which can be no less than 48 hours.
+
+A proposal must be supported by 20% of active committee members to be tabled.
+
+All tabled proposals:
+a)	Will be discussed and researched. 
+b)	Any modifications that are required to the proposals to finalize them will be discussed, planned and all modifications agreed via committee vote.
+c)	Finalized proposals are closed to modifications and must be voted by committee vote to accept or reject the proposal. 
+Once a proposal is accepted, the committee will report this finished proposal to the community and if any further modification is deemed necessary, it can be re-tabled and discussed.
+The committee will maintain communications for projects that are in action and will report as needed either internally. Key milestones will be reported publicly to the community.
+
+Amendments
+
+Changed voting rights from
+-	a community voting pool with 50% of the vote broken up into 5% stakes per member
+-	a dev pool holding 50% of the voting rights collectively
+-	ability of either pool to universally veto if all members are in agreement.
+To current, split equal allocation no forced veto rights. Easier
+
+Added 75% member removal vote threshold.
+Added 20% of committee members must agree that a proposal is suitable to be tabled.
+
+Artax is driven by a dedicated community of contributers yet controlled
+by not one single individual. Every new direction is put to vote and decided by the Dev-Committee. 
+This attractive Model will help ensure sovereignty, stability, growth, and compelling developments.
+This also enables contributors to come and go on the project without commitment or constraint. 
+All Artax contributors are treated as anonymous, unbound volunteers much like Bitcoin.
+
+Authored by @gote (dev-committee lead)
+
+
+
+
+
+
+
+
diff --git a/ARTAX_COMMITTEE.txt b/ARTAX_COMMITTEE.txt
@@ -0,0 +1,80 @@
+ARTAX COMMITTEE   - Artax [NO ICO] Community driven coin.
+
+Establishment of steering committee for proposal implementation and planning
+
+v1.2
+
+Preamble 
+
+This proposal aims to establish a committee of node holders, developers and skilled community members to spearhead, develop, research and action proposals put forward for the future of the respective coins.
+
+As a coin requires technical modification or direction or structural changes, a proposal for this would be tabled to the committee and approved or rejected by a voting process wherein each committee member holds a voting right. Once approval is reached, the committee will transparently manage and report on the status of the proposal through action to completion.
+For proposals that are deemed large enough in scope to require a community voting process, the proposal must first pass committee vote prior to a community vote taking place. This ensures only proposals that are deemed meritorious are presented to master-node holders or the community at large.
+
+Committee formation, management and requirements.
+
+All committee member seats are voluntary positions and they will not be paid for any committee related activities. 
+The initial committee selection will be advertised by announcements in the various coin channels inviting interested parties to submit an application to the developers via a public channel. Applications should include brief outlines of experience, skillsets, knowledge base and may be asked for a brief interview in discord or other method to verify their credentials and experience. This is to ensure that the committee contains a range of different experience, knowledge and perspectives. 
+
+Initially, the developers will collectively choose suitable candidates based on those applications whom they wish to allocate the initial committee seats to. This will form the initial committee.
+
+- 	Committee members may step down from their seats at any time without obligation.
+- 	Committee members can also vote to remove a sitting committee member. The member will be voted out if a majority of 75% eligible vote is reached.
+- 	New committee members may be sourced by application or recommendation and must be approved by a vote amongst existing members prior to acceptance as a committee member.
+
+Each committee member has an equal vote which is based on 100% (total voting rights) divided by the total number of active committee members. 
+
+All committee members are required to vote on tabled proposals within a deadline which is stated with the tabled proposal (see below), after which if they have not voted, a null vote is recorded. 51% of any remaining eligible vote must be passed to pass the tabled proposal.
+
+Example: 
+-	3 community members with 5% voting rights each abstain from or miss voting
+-	total remaining eligible vote is 85%
+-	51% of 85% or 43% is required to pass
+
+Proposal process, handling, approvals and rejection.
+
+Proposals can be sourced directly if a specific need exists or arises or if ideas or opportunities to improve are bought to the attention of a committee members that warrants a proposal being put forth.
+Proposals are a call to a vote and also a call to research, validate and confirm the reasoning contained within the proposal as being an appropriate step to take with the coin.
+
+Any active committee member can put forward a proposal to be tabled.
+For a proposal to be tabled, it must include:
+a)	A summary of the proposal
+b)	Any supporting evidence or data
+c)	Any recommendations
+d)	Timelines required to vote which can be no less than 48 hours.
+
+A proposal must be supported by 20% of active committee members to be tabled.
+
+All tabled proposals:
+a)	Will be discussed and researched. 
+b)	Any modifications that are required to the proposals to finalize them will be discussed, planned and all modifications agreed via committee vote.
+c)	Finalized proposals are closed to modifications and must be voted by committee vote to accept or reject the proposal. 
+Once a proposal is accepted, the committee will report this finished proposal to the community and if any further modification is deemed necessary, it can be re-tabled and discussed.
+The committee will maintain communications for projects that are in action and will report as needed either internally. Key milestones will be reported publicly to the community.
+
+Amendments
+
+Changed voting rights from
+-	a community voting pool with 50% of the vote broken up into 5% stakes per member
+-	a dev pool holding 50% of the voting rights collectively
+-	ability of either pool to universally veto if all members are in agreement.
+To current, split equal allocation no forced veto rights. Easier
+
+Added 75% member removal vote threshold.
+Added 20% of committee members must agree that a proposal is suitable to be tabled.
+
+Artax is driven by a dedicated community of contributers yet controlled
+by not one single individual. Every new direction is put to vote and decided by the Dev-Committee. 
+This attractive Model will help ensure sovereignty, stability, growth, and compelling developments.
+This also enables contributors to come and go on the project without commitment or constraint. 
+All Artax contributors are treated as anonymous, unbound volunteers much like Bitcoin.
+
+Authored by @gote (dev-committee lead)
+
+
+
+
+
+
+
+