いろは (Iroha) is a simple, distributed ledger.
Please include a developer certificate with pull requests: https://www.clahub.com/agreements/hyperledger/iroha
.
├── build (for cmake)
├── config
├── peer
├── core
│ ├── connection
│ ├── consensus
│ ├── crypto
│ ├── model
│ │ └── transactions
│ ├── infra
│ │ ├── connection
│ │ ├── crypto
│ │ ├── repository
│ │ ├── server
│ │ └── smart_contract
│ ├── repository
│ ├── server
│ ├── smart_contract
│ ├── util
│ ├── validation
│ └── vendor
├── doc
├── smart_contract
│ └── SampleCurrency_java
└── test
├── crypto
└── smart_contract
It contains config file. currently we use yaml, but JSON is good like as yaml.
It contains main.cpp
It contains smart_contract logic what user defines.
Currently use java virtual machine.
There's few tests for iroha. 🙇 We accept pull requests.
It contains main.
├── connection
├── consensus
├── crypto
├── domain
│ └── transactions
├── infra
│ ├── connection
│ ├── crypto
│ ├── repository
│ ├── server
│ └── smart_contract
│ └── jvm
├── repository
├── server
├── smart_contract
├── util
└── validation
We adopt a Domain-Driven Development structure as much as possible.
+--------------+
| web rest api |
+--------------+
|
+--------------+
| controller |--------+-----------------------------------------+
+--------------+ | |
| +-------------+ +----------------+ +----------------------+
| | repository | | domain model | | service |
| | (interface) |--| | |+---------++---------+|
| +-------------+ |+--------------+| || crypto ||validate ||
| | || transaction || || base64 |+---------+|
| | |+--------------+| || hash | |
| | || asset || |+---------+ |
| | |+--------------+| +----------------------+
| | |+--------------+|
| | ||smart contract||
+--------------+ | |+--------------+|
| consensus |--------+ +----------------+
| |
|+------------+|
|| messaging ||
|+------------+|
+--------------+
+----------------------------------------------------------------------------+
|infrastructure |
| |
|+------------++--------------++-------------++----------------++---------+ |
|| messaging || web rest api || repository || smart contract || crypto | |
||(use aeron )|| (use crow) ||(use leveldb)|| (use java vm) || ed25519 | |
|+------------++--------------++-------------++----------------++---------+ |
+----------------------------------------------------------------------------+
It contains the P2P messaging function interface.
void initialize_peer( std::unordered_map<std::string, std::string> config);
bool sendAll(std::string message);
bool send(std::string to,std::string message);
bool receive(std::function<void(std::string from,std::string message)> callback);
It contains the consensus algorithm(s).
It contains digital signature algorithms, base64, hash function interfaces, etc.
It contains asset model, transaction logic. independent of infra knowledge.
It contains some source depend on vendor (third party) libraries. If any source depends on vendor libraries, it should be in infra.
basically, filename is "function"_with_"lib name".cpp
connection
└── connection_with_aeron.cpp
repository
└── world_state_repository_with_level_db.cpp
It contains the server interface, currently.
void server();
It contains the Java virtual machine interface.
void initializeVM(std::string contractName);
void finishVM();
void invokeFunction(
std::string functionName,
std::unordered_map<std::string, std::string> params);
It contains logger, random, datetime, exception...
JAVA_HOME := java's home
IROHA_HOME := iroha's root
cmake(3.5.2)
gRPC
LevelDB
fabric3 (python library, not hyperledger/fabric)
$ git submodule init
$ git submodule update
$ mkdir build
$ cd build
$ cmake ..
$ make
(in server) or
$ fab deploy
(in local)
This step should only be necessary if protobuf definitions changes, or version of gRPC or protoc has been updated.
(invoked from $IROHA_HOME)
protoc --cpp_out=core/infra/connection core/infra/connection/connection.proto
protoc --grpc_out=core/infra/connection --plugin=protoc-gen-grpc=`which grpc_cpp_plugin` core/infra/connection/connection.proto
Copyright 2016 Soramitsu Co., Ltd.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.