Skip to content

Commit 1458f23

Browse files
Junha Yangsgkim126
authored andcommitted
Update the introductory section in README.md
Revised by DoHyung
1 parent 18d7f1d commit 1458f23

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

README.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,15 @@ Foundry
55
==============
66

77
CodeChain Foundry is a blockchain engine based on a composable module system, called _Mold_.
8-
Users can define their own modules, and can construct an arbitrary blockchain application with them.
9-
The reason we provide such a composable, and user-customizable module system is
10-
because we want to make only application logic as user's responsibility,
11-
while the _host_ manages common things such as consensus, networking, mempool or DB, for all kinds of applications.
12-
13-
The actual execution of the transaction, which is essentially a transition of state from the previous one, will be requested to the _coordinator_ from the host.
14-
The coordinator manages multiple modules for the application, and handles such requests from the host asking the modules.
15-
Transactions will be delivered to the responsible module, and that module will handle the transaction in the way it is implemented in,
8+
Users can write their own modules and additionally bring those written by others in to construct an arbitrary blockchain application.
9+
The reason why we provide such a composable and user-configurable module system is
10+
because we want to make as much of an application configurable as possible and foster an ecosystem of reusable modules,
11+
while reusing the underlying consensus engine across all the different kinds of applications.
12+
13+
On an execution of a transaction, that is essentially a state transition, the coordinator will be told to do so from the underlying consensus engine.
14+
Then the coordinator literally coordinates multiple modules constituting an application
15+
by invoking services exported by the modules to the coordinator in an appropriate order passing appropriate arguments.
16+
Transactions will be delivered to the responsible modules, and that the modules will handle the executions of the transactions,
1617
which might also involve communications with other modules.
1718

1819
## Build

0 commit comments

Comments
 (0)