eosDAC has contracted to host its own servers in M24seven’s privately owned data centres in Manchester and Bucharest. M24seven’s state-of-the-art Tier 3 facilities provide comprehensive security, resilience and bandwidth capacity and are ranked Europe’s greenest for electricity consumption.
We have 2 nodes in each location with 256GB RAM ( Rapid scaling to 2TB is supported) and over 5 TB of usable SSD space. Hardware based firewalls and DDOS prevention are as standard. The specifications will be reviewed on a regular basis and upgrades implemented as
Further servers are being deployed in Gibraltar where eosDAC is also exploring the unique licensing potential available to ‘Distributed Ledger Technology’ operators in that jurisdiction. In South Korea, eosDAC is working on a ‘bare metal through cloud solution’ within an IBM data
eosDAC agreement with Incommsec Ltd
eosDAC has agreed a partnership with Incommsec Ltd, UK.to allow for the rapid contracting and deployment of operational infrastructure and services in the UK and Europe. Incommsec Ltd is also providing interim payments and procedural functions to the DAC as an arm’s length service provider.
As of August 2018, eosDAC has total cash of around $850k held in a segregated holding account with Incommsec Ltd This is available to fund all operations that the eosDAC custodians or elected representative(s) instruct should be carried out on their behalf. All assets (e.g. servers, IP etc) procured by Incommsec Ltd and other DAC service companies on behalf of eosDAC, are held on behalf of eosDAC. Should eosDAC choose to end its service relationship with Incommsec Ltd, all assets will be transferred to the nominated person(s) or organisation chosen by the eosDAC custodians.
eosDAC is a collective of individuals working together for common purposes – to produce blocks on EOS, to support new Apps, to enable future decentralised autonomous communities (DACs) and any other priorities the community chooses. eosDAC is not a company and the members are not shareholders, instead eosDAC tokens confer membership and control of the DAC through voted Custodians and other mechanisms. The best place to read about how we are organised is in our Constitution.
Our Constitution is a ground-breaking effort to codify how a new organisation like a DAC can govern itself. It outlines the mechanisms for tokenholders to register their membership and vote for Custodians; empowers Custodians to make decisions and payments; and creates the framework by which members are severally liable for the operations of the DAC. It also empowers eosDAC to request identifying information of its tokenholders, in order for example to comply with national regulatory requirements. We really recommend you read it, to understand how we work!
Envisioned Dapps will include, but no be limited to:
DAC tools and DAPPS will be developed through worker proposals and will be shared with the EOS.IO communities. All tools will be built using an iterative process and will continue to be actively improved through improvement proposals from the eosDAC communities.
Teams within the DAC use Discord, Trello and GitHub to communicate about our workstreams and we invite you to join us on those open forums to start to collaborate. We intend to meet individuals where they are at and also expect them to meet us where we’re going. Our end goal isn’t to control the process, but to empower progress and improve efficiency.
We’re committed to continually evaluating our workflow processes and exploring new tools to improve efficiency. We’ll also do our best to provide training materials and guidance to those who are not familiar with the tools we suggest while at the same time being fully open to changing things up and looking at new approaches if they can provide more benefit to the community.