The Dragonchain platform attempts to simplify integration of real business applications onto a blockchain. Providing features such as easy integration, protection of business data, fixed 5 second blocks, currency agnosticism, and interop features, Dragonchain shines a new and interesting light on blockchain technology.
- Ease of integration of existing systems
- Ease of development for traditional engineers and coders unfamiliar with blockchain, distributed systems, and cryptography
- Client server style and simple RESTful integration points for business integration
- Simple architecture (flexible and usable for unforeseen applications)
- Provide protection of business data by default
- Allow business focused control of processes
- Fixed length period blocks
- Short/fast blocks
- Currency agnostic blockchain (multicurrency support)
- No base currency
- Interoperability with other blockchains public and private
- Adoption of standards as they become available (see W3C Blockchain Community Group blockchain standardization)
- Dragonchain Organization
- Dragonchain Architecture Document - PDF
- Use Cases
- Disney Blockchain Standardization Notes - W3C
- Slack Team: Dragonchain Slack Team sign up:
- Slack Support Channel: #support
- Email: [email protected]
Joe Roets (j03) [email protected]
Requires Docker version 1.13.0 and docker-compose version 1.10.0
Stack declaration is made via the docker-compose.yaml in the docker directory. Docker-compose.yml uses the dockerfile declarations that packages the project services into containers.
To bring up the stack:
cd docker
docker-compose up -d
Postgres is exposed at port 5432
Query service is exposed at port 80
Transaction service is exposed at port 81
Processor service is exposed at port 8080
Requires Postgres 9.4+
cd <Dragonchain Home>/sql
createuser blocky
createdb -O blocky blockchain
psql -U blocky -d blockchain -a -f depl.sql
Dragonchain utilized Python 2.7
To install Python library dependencies, run the following:
pip install -r requirements.txt
Message classes and RMI services are generated by thrift templates. If you have Apache Thrift installed you can regenerate these classes by using the gen_thrift setup command:
python setup.py gen_thrift
mkdir pki
- Signing Key Generation
openssl ecparam -name secp224r1 -genkey -out <Dragonchain Home>/pki/sk.pem - Verifying Key Generation
openssl ec -in pki/sk.pem -pubout -out <Dragonchain Home>/pki/pk.pem - The signing key must be kept private. The pki directory is listed in .gitignore to prevent accidentally pushing keys to a public repository.
Pre-create a directory for log files before execution.
mkdir logs
export PYTHONPATH=/path/to/dragonchain
python <Dragonchain Home>/blockchain/transaction_svc.py --private-key <Dragonchain Home>/pki/sk.pem --public-key <Dragonchain Home>/pki/pk.pem
python <Dragonchain Home>/blockchain/query_svc.py [-p port] //defaults to 8080
localhost:8080/transaction/?create_ts=1475155787 //timestamp in Unix Epoch timecode
- create_ts can be replaced with any of the header fields in a transaction
python <Dragonchain Home>/blockchain/processing.py --private-key <Dragonchain Home>/pki/sk.pem --public-key <Dragonchain Home>/pki/pk.pem
--private-key (required - signing key for transaction service and processing module)
--public-key (required)
--host (defaults to localhost)
--port, -p (defaults to 8080)
--phase (required)
For phase 5 node only:
--bitcoin-network (mainnet/testnet/regtest)
The current implementation of the phase 5 node can connect to a local bitcoin node with wallet in order to run or can remotely connect to another bitcoin wallet running Bitcoin-Qt. Make sure that your bitcoin.conf file is in the proper location:
$HOME/Library/Application Support/Bitcoin/
$HOME/.bitcoin/
%APPDATA%\Bitcoin\
rpcuser="some username"
rpcpassword="password for the node"
Optional for running on a remote node:
rpcconnect="bitcoin_node_ip_address"
rpcport="bitcoin_node_port" (defaults to 8333)
Configuration within yaml files within configs directory.
BLOCKCHAIN_DB_HOSTNAME = Hostname of the database instance (default localhost)
BLOCKCHAIN_DB_PORT = Port of the database server (default 5432)
BLOCKCHAIN_DB_USERNAME = Database username (default blocky)
BLOCKCHAIN_DB_PASSWORD = Database password (default None)
BLOCKCHAIN_DB_NAME = Blockchain database (default blockchain, also selects .yaml config and log file with same name)
Dragonchain uses a standard Feature Branch Workflow.
All feature development should take place in Git branch dedicated to that feature. A feature branch should be named starting with the ticket ID followed by a dash and a short description.
Issues are tracked within Github: Dragonchain Issues
Code should follow the PEP 8 Style Guide for Python code where possible.
- Joe Roets - Principal Architect / Vision
- Eileen Quenin - Product Manager / Evangelist
- Brandon Kite - Lead Developer
- Dylan Yelton - Developer
- Alex Benedetto - Developer
- Michael Bachtel - DevOps / Developer
- Lucas Ontivero - Developer
- Adam Bronfin - Developer / Reviewer
- Benjamin Israelson - Developer / Reviewer
- Forrest Fisher - Program Manager
- Robbin Schill - Program Manager
- Krassi Krustev - Developer
- Rob Eickmann - iOS Developer
- Sean Ochoa - DevOps / Sysadmin
- Paul Sonier - Developer / Reviewer
- Kevin Schumacher - Artist / Web Design
- Brian J Wilson - Architect
- Mike De'Shazer - Developer / Reviewer
- Tai Kersten - Developer / Reviewer
- Steve Owens - Reviewer
- Mark LaPerriere - Reviewer
- Kevin Duane - Reviewer
- Chris Moore - Reviewer
The comments, views, and opinions expressed in this forum are those of the authors and do not necessarily reflect the official policy or position of the Walt Disney Company, Disney Connected and Advanced Technologies, or any affiliated companies.
All code contained herein is provided “AS IS” without warranties of any kind. Any implied warranties of non-infringement, merchantability, and fitness for a particular purpose are expressly disclaimed by the author(s).
Copyright 2016 Disney Connected and Advanced Technologies
Licensed under the Apache License, Version 2.0 (the "Apache License")
with the following modification; you may not use this file except in
compliance with the Apache License and the following modification to it:
Section 6. Trademarks. is deleted and replaced with:
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor
and its affiliates, except as required to comply with Section 4(c) of
the License and to reproduce the content of the NOTICE file.
You may obtain a copy of the Apache License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the Apache License with the above modification is
distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the Apache License for the specific
language governing permissions and limitations under the Apache License.