From da03be35f572731f15f70b63a3b3c02a0114d264 Mon Sep 17 00:00:00 2001 From: Ulan Degenbaev Date: Tue, 30 Jan 2024 22:58:11 +0100 Subject: [PATCH] Another attempt to center images --- docs/concepts/what-is-ic.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/concepts/what-is-ic.md b/docs/concepts/what-is-ic.md index c0786c648d..4347e6b208 100644 --- a/docs/concepts/what-is-ic.md +++ b/docs/concepts/what-is-ic.md @@ -5,7 +5,7 @@ Smart contracts on ICP are expressive and scalable like traditional apps, but be ICP is designed for a practical balance in the tradeoff between scalability and decentralization. -
+
ICP in the tradeoff space
@@ -32,7 +32,7 @@ The following diagram shows the flow of the message on ICP: Note that steps 3-5 are asynchronous and decoupled from each other, which may be unusual for developers who are used to Ethereum-style atomic transactions that are executed when they are added to a block. The motivation for this design is scalability. -
+
Flow of a message on ICP
@@ -55,7 +55,7 @@ This feature has profound implications and use cases: - Smart contracts [can have their own secret keys](https://medium.com/dfinity/how-icps-bitcoin-integration-secures-private-keys-c2af14597846) and can sign transactions for other blockchains such as Bitcoin and Ethereum. This enables trustless interaction with those blockchains. -
+
Threshold signature
@@ -94,7 +94,7 @@ In the context of ICP, smart contracts are referred to as **canisters**. ICP derives the address of a user account from the user’s public key by hashing it. -
+
Accounts, keys, principals