APECS offers a permissionless operations center for crypto Builders to get their work done! https://apecs.dev

Shomari ce46f7afa3 Add Docker cleanup. 1 viikko sitten
api 39f08c4e01 Remove all references to devops. 1 vuosi sitten
docs 1fce5546c7 Update docs. 1 vuosi sitten
ide a50901337f Rebrand from Cash DevOps to APECS. 1 vuosi sitten
logger 49bdea03b4 Update logger. 1 vuosi sitten
tests 871bdc27b0 Refactor Vue.js. 3 vuotta sitten
web ce46f7afa3 Add Docker cleanup. 1 viikko sitten
www-portals c4dccc90de Add Dash portal. 1 vuosi sitten
.gitignore 92b104ad36 Add legacy web components. 1 vuosi sitten
LICENSE 4e6c03229f Update license. 1 vuosi sitten
README.md 39f08c4e01 Remove all references to devops. 1 vuosi sitten

README.md

APECS — A Peer-to-Peer Electronic Cash System

APECS Poster

Build Status Greenkeeper badge

APECS provides the Crypto community with its own platform to support developers, by supporting the effortless BUIDLing of services on top of BCH.

It's time we ALL come together to BU!DL BCH! and #MakeBitcoinCashAgain

APECS will always be 100% FREE for use by the Crypto community;
as well as any others that wishes to BUIDL on top of BCH.

Publishing your project(s) on APECS

Anyone can manage their personal and/or team projects on APECS. However, in order to PUBLISH, it is required that project use open source software licenses compatible with other projects in the Crypto ecosystem for ALL client-side (user-facing) source code.

What is client-side?

  1. Website (html, js, css, etc) source code
  2. Mobile app source code
  3. IOT (hardware) embedded code
  4. Smart contract code

You MUST have your code available on a publicly-accessible source code repository (eg. Github, Bitbucket, Gitlab, etc).

NOTE: Repos can be self-hosted.

It is NOT required to have an open-source back office to qualify for publishing.

What is back office?

This will typically be Application Programming Interface (API) servers, that interface with the client. These servers/systems can often require:

  1. Security keys
  2. Proprietary integrations

As a result, there is NO requirement for these code-bases to be open source.