Skip to content

Commit 76de577

Browse files
0xlukem0xlukem
committed
llms
1 parent d049547 commit 76de577

14 files changed

+258
-258
lines changed

‎.ai/categories/basics.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4704,7 +4704,7 @@ The Polkadot SDK allows developers to construct a runtime by combining various p
47044704
47054705
The following diagram illustrates the process of selecting and combining FRAME pallets to compose a runtime:
47064706
4707-
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp)
4707+
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp){ style="background:white; padding:1em;" }
47084708
47094709
This modular design allows developers to:
47104710
@@ -4891,7 +4891,7 @@ According to Polkadot's design, any blockchain that can compile to WebAssembly (
48914891
48924892
Here’s a high-level overview of the Polkadot protocol architecture:
48934893
4894-
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp)
4894+
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp){ style="background:white" }
48954895
48964896
Parachains propose blocks to Polkadot validators, who check for availability and validity before finalizing them. With the relay chain providing security, collators—full nodes of parachains—can focus on their tasks without needing strong incentives.
48974897
@@ -6064,7 +6064,7 @@ flowchart LR
60646064
E[Transaction] --> D
60656065
D --> F[(New State)]
60666066
D --> G[Execution Logs]
6067-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
6067+
style A stroke:#000000,stroke-width:1px
60686068
```
60696069
60706070
In addition, because smart contracts are programs that execute on top of existing chains, teams don't have to think about the underlying consensus they are built on.
@@ -6134,8 +6134,8 @@ flowchart TD
61346134
F --> J[(New Ethereum<br/>Emulated State)]
61356135
F --> K[Execution Logs]
61366136
6137-
style C fill:#ffffff,stroke:#000000,stroke-width:1px
6138-
style F fill:#ffffff,stroke:#000000,stroke-width:1px
6137+
style C stroke:#000000,stroke-width:1px
6138+
style F stroke:#000000,stroke-width:1px
61396139
```
61406140
61416141
Although it seems complex, users and developers are abstracted of that complexity, and tools can easily interact with the parachain as they would with any other Ethereum-compatible environment.
@@ -6170,7 +6170,7 @@ flowchart TD
61706170
A --> F[(New State)]
61716171
A --> G[Execution Logs]
61726172
6173-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
6173+
style A stroke:#000000,stroke-width:1px
61746174
```
61756175
61766176
@@ -6853,7 +6853,7 @@ Pallets, which compose the runtime's logic, define the specific transactions tha
68536853
68546854
In Polkadot SDK-based networks, some nodes are authorized to author blocks. These nodes validate and process transactions. When a transaction is sent to a node that can produce blocks, it undergoes a lifecycle that involves several stages, including validation and execution. Non-authoring nodes gossip the transaction across the network until an authoring node receives it. The following diagram illustrates the lifecycle of a transaction that's submitted to a network and processed by an authoring node.
68556855
6856-
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp)
6856+
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp){ style="background:white" }
68576857
68586858
### Validate and Queue
68596859

‎.ai/categories/dapps.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6890,7 +6890,7 @@ The Polkadot SDK allows developers to construct a runtime by combining various p
68906890

68916891
The following diagram illustrates the process of selecting and combining FRAME pallets to compose a runtime:
68926892

6893-
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp)
6893+
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp){ style="background:white; padding:1em;" }
68946894

68956895
This modular design allows developers to:
68966896

@@ -7077,7 +7077,7 @@ According to Polkadot's design, any blockchain that can compile to WebAssembly (
70777077

70787078
Here’s a high-level overview of the Polkadot protocol architecture:
70797079

7080-
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp)
7080+
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp){ style="background:white" }
70817081

70827082
Parachains propose blocks to Polkadot validators, who check for availability and validity before finalizing them. With the relay chain providing security, collators—full nodes of parachains—can focus on their tasks without needing strong incentives.
70837083

@@ -9249,7 +9249,7 @@ flowchart LR
92499249
E[Transaction] --> D
92509250
D --> F[(New State)]
92519251
D --> G[Execution Logs]
9252-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
9252+
style A stroke:#000000,stroke-width:1px
92539253
```
92549254

92559255
In addition, because smart contracts are programs that execute on top of existing chains, teams don't have to think about the underlying consensus they are built on.
@@ -9319,8 +9319,8 @@ flowchart TD
93199319
F --> J[(New Ethereum<br/>Emulated State)]
93209320
F --> K[Execution Logs]
93219321

9322-
style C fill:#ffffff,stroke:#000000,stroke-width:1px
9323-
style F fill:#ffffff,stroke:#000000,stroke-width:1px
9322+
style C stroke:#000000,stroke-width:1px
9323+
style F stroke:#000000,stroke-width:1px
93249324
```
93259325

93269326
Although it seems complex, users and developers are abstracted of that complexity, and tools can easily interact with the parachain as they would with any other Ethereum-compatible environment.
@@ -9355,7 +9355,7 @@ flowchart TD
93559355
A --> F[(New State)]
93569356
A --> G[Execution Logs]
93579357

9358-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
9358+
style A stroke:#000000,stroke-width:1px
93599359
```
93609360

93619361

@@ -10251,7 +10251,7 @@ Pallets, which compose the runtime's logic, define the specific transactions tha
1025110251

1025210252
In Polkadot SDK-based networks, some nodes are authorized to author blocks. These nodes validate and process transactions. When a transaction is sent to a node that can produce blocks, it undergoes a lifecycle that involves several stages, including validation and execution. Non-authoring nodes gossip the transaction across the network until an authoring node receives it. The following diagram illustrates the lifecycle of a transaction that's submitted to a network and processed by an authoring node.
1025310253

10254-
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp)
10254+
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp){ style="background:white" }
1025510255

1025610256
### Validate and Queue
1025710257

‎.ai/categories/infrastructure.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6843,7 +6843,7 @@ The Polkadot SDK allows developers to construct a runtime by combining various p
68436843

68446844
The following diagram illustrates the process of selecting and combining FRAME pallets to compose a runtime:
68456845

6846-
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp)
6846+
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp){ style="background:white; padding:1em;" }
68476847

68486848
This modular design allows developers to:
68496849

@@ -7030,7 +7030,7 @@ According to Polkadot's design, any blockchain that can compile to WebAssembly (
70307030

70317031
Here’s a high-level overview of the Polkadot protocol architecture:
70327032

7033-
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp)
7033+
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp){ style="background:white" }
70347034

70357035
Parachains propose blocks to Polkadot validators, who check for availability and validity before finalizing them. With the relay chain providing security, collators—full nodes of parachains—can focus on their tasks without needing strong incentives.
70367036

@@ -9279,7 +9279,7 @@ flowchart LR
92799279
E[Transaction] --> D
92809280
D --> F[(New State)]
92819281
D --> G[Execution Logs]
9282-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
9282+
style A stroke:#000000,stroke-width:1px
92839283
```
92849284

92859285
In addition, because smart contracts are programs that execute on top of existing chains, teams don't have to think about the underlying consensus they are built on.
@@ -9349,8 +9349,8 @@ flowchart TD
93499349
F --> J[(New Ethereum<br/>Emulated State)]
93509350
F --> K[Execution Logs]
93519351

9352-
style C fill:#ffffff,stroke:#000000,stroke-width:1px
9353-
style F fill:#ffffff,stroke:#000000,stroke-width:1px
9352+
style C stroke:#000000,stroke-width:1px
9353+
style F stroke:#000000,stroke-width:1px
93549354
```
93559355

93569356
Although it seems complex, users and developers are abstracted of that complexity, and tools can easily interact with the parachain as they would with any other Ethereum-compatible environment.
@@ -9385,7 +9385,7 @@ flowchart TD
93859385
A --> F[(New State)]
93869386
A --> G[Execution Logs]
93879387

9388-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
9388+
style A stroke:#000000,stroke-width:1px
93899389
```
93909390

93919391

@@ -10374,7 +10374,7 @@ Pallets, which compose the runtime's logic, define the specific transactions tha
1037410374

1037510375
In Polkadot SDK-based networks, some nodes are authorized to author blocks. These nodes validate and process transactions. When a transaction is sent to a node that can produce blocks, it undergoes a lifecycle that involves several stages, including validation and execution. Non-authoring nodes gossip the transaction across the network until an authoring node receives it. The following diagram illustrates the lifecycle of a transaction that's submitted to a network and processed by an authoring node.
1037610376

10377-
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp)
10377+
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp){ style="background:white" }
1037810378

1037910379
### Validate and Queue
1038010380

‎.ai/categories/networks.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5944,7 +5944,7 @@ The Polkadot SDK allows developers to construct a runtime by combining various p
59445944

59455945
The following diagram illustrates the process of selecting and combining FRAME pallets to compose a runtime:
59465946

5947-
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp)
5947+
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp){ style="background:white; padding:1em;" }
59485948

59495949
This modular design allows developers to:
59505950

@@ -6131,7 +6131,7 @@ According to Polkadot's design, any blockchain that can compile to WebAssembly (
61316131

61326132
Here’s a high-level overview of the Polkadot protocol architecture:
61336133

6134-
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp)
6134+
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp){ style="background:white" }
61356135

61366136
Parachains propose blocks to Polkadot validators, who check for availability and validity before finalizing them. With the relay chain providing security, collators—full nodes of parachains—can focus on their tasks without needing strong incentives.
61376137

@@ -7304,7 +7304,7 @@ flowchart LR
73047304
E[Transaction] --> D
73057305
D --> F[(New State)]
73067306
D --> G[Execution Logs]
7307-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
7307+
style A stroke:#000000,stroke-width:1px
73087308
```
73097309

73107310
In addition, because smart contracts are programs that execute on top of existing chains, teams don't have to think about the underlying consensus they are built on.
@@ -7374,8 +7374,8 @@ flowchart TD
73747374
F --> J[(New Ethereum<br/>Emulated State)]
73757375
F --> K[Execution Logs]
73767376

7377-
style C fill:#ffffff,stroke:#000000,stroke-width:1px
7378-
style F fill:#ffffff,stroke:#000000,stroke-width:1px
7377+
style C stroke:#000000,stroke-width:1px
7378+
style F stroke:#000000,stroke-width:1px
73797379
```
73807380

73817381
Although it seems complex, users and developers are abstracted of that complexity, and tools can easily interact with the parachain as they would with any other Ethereum-compatible environment.
@@ -7410,7 +7410,7 @@ flowchart TD
74107410
A --> F[(New State)]
74117411
A --> G[Execution Logs]
74127412

7413-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
7413+
style A stroke:#000000,stroke-width:1px
74147414
```
74157415

74167416

@@ -8093,7 +8093,7 @@ Pallets, which compose the runtime's logic, define the specific transactions tha
80938093

80948094
In Polkadot SDK-based networks, some nodes are authorized to author blocks. These nodes validate and process transactions. When a transaction is sent to a node that can produce blocks, it undergoes a lifecycle that involves several stages, including validation and execution. Non-authoring nodes gossip the transaction across the network until an authoring node receives it. The following diagram illustrates the lifecycle of a transaction that's submitted to a network and processed by an authoring node.
80958095

8096-
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp)
8096+
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp){ style="background:white" }
80978097

80988098
### Validate and Queue
80998099

‎.ai/categories/parachains.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10631,7 +10631,7 @@ The Polkadot SDK allows developers to construct a runtime by combining various p
1063110631

1063210632
The following diagram illustrates the process of selecting and combining FRAME pallets to compose a runtime:
1063310633

10634-
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp)
10634+
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp){ style="background:white; padding:1em;" }
1063510635

1063610636
This modular design allows developers to:
1063710637

@@ -10818,7 +10818,7 @@ According to Polkadot's design, any blockchain that can compile to WebAssembly (
1081810818

1081910819
Here’s a high-level overview of the Polkadot protocol architecture:
1082010820

10821-
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp)
10821+
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp){ style="background:white" }
1082210822

1082310823
Parachains propose blocks to Polkadot validators, who check for availability and validity before finalizing them. With the relay chain providing security, collators—full nodes of parachains—can focus on their tasks without needing strong incentives.
1082410824

@@ -13699,7 +13699,7 @@ flowchart LR
1369913699
E[Transaction] --> D
1370013700
D --> F[(New State)]
1370113701
D --> G[Execution Logs]
13702-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
13702+
style A stroke:#000000,stroke-width:1px
1370313703
```
1370413704

1370513705
In addition, because smart contracts are programs that execute on top of existing chains, teams don't have to think about the underlying consensus they are built on.
@@ -13769,8 +13769,8 @@ flowchart TD
1376913769
F --> J[(New Ethereum<br/>Emulated State)]
1377013770
F --> K[Execution Logs]
1377113771

13772-
style C fill:#ffffff,stroke:#000000,stroke-width:1px
13773-
style F fill:#ffffff,stroke:#000000,stroke-width:1px
13772+
style C stroke:#000000,stroke-width:1px
13773+
style F stroke:#000000,stroke-width:1px
1377413774
```
1377513775

1377613776
Although it seems complex, users and developers are abstracted of that complexity, and tools can easily interact with the parachain as they would with any other Ethereum-compatible environment.
@@ -13805,7 +13805,7 @@ flowchart TD
1380513805
A --> F[(New State)]
1380613806
A --> G[Execution Logs]
1380713807

13808-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
13808+
style A stroke:#000000,stroke-width:1px
1380913809
```
1381013810

1381113811

@@ -14842,7 +14842,7 @@ Pallets, which compose the runtime's logic, define the specific transactions tha
1484214842

1484314843
In Polkadot SDK-based networks, some nodes are authorized to author blocks. These nodes validate and process transactions. When a transaction is sent to a node that can produce blocks, it undergoes a lifecycle that involves several stages, including validation and execution. Non-authoring nodes gossip the transaction across the network until an authoring node receives it. The following diagram illustrates the lifecycle of a transaction that's submitted to a network and processed by an authoring node.
1484414844

14845-
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp)
14845+
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp){ style="background:white" }
1484614846

1484714847
### Validate and Queue
1484814848

‎.ai/categories/polkadot-protocol.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6550,7 +6550,7 @@ The Polkadot SDK allows developers to construct a runtime by combining various p
65506550

65516551
The following diagram illustrates the process of selecting and combining FRAME pallets to compose a runtime:
65526552

6553-
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp)
6553+
![](/images/develop/parachains/customize-parachain/overview/frame-overview-2.webp){ style="background:white; padding:1em;" }
65546554

65556555
This modular design allows developers to:
65566556

@@ -6737,7 +6737,7 @@ According to Polkadot's design, any blockchain that can compile to WebAssembly (
67376737

67386738
Here’s a high-level overview of the Polkadot protocol architecture:
67396739

6740-
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp)
6740+
![](/images/polkadot-protocol/architecture/polkadot-chain/overview/overview-1.webp){ style="background:white" }
67416741

67426742
Parachains propose blocks to Polkadot validators, who check for availability and validity before finalizing them. With the relay chain providing security, collators—full nodes of parachains—can focus on their tasks without needing strong incentives.
67436743

@@ -8271,7 +8271,7 @@ flowchart LR
82718271
E[Transaction] --> D
82728272
D --> F[(New State)]
82738273
D --> G[Execution Logs]
8274-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
8274+
style A stroke:#000000,stroke-width:1px
82758275
```
82768276

82778277
In addition, because smart contracts are programs that execute on top of existing chains, teams don't have to think about the underlying consensus they are built on.
@@ -8341,8 +8341,8 @@ flowchart TD
83418341
F --> J[(New Ethereum<br/>Emulated State)]
83428342
F --> K[Execution Logs]
83438343

8344-
style C fill:#ffffff,stroke:#000000,stroke-width:1px
8345-
style F fill:#ffffff,stroke:#000000,stroke-width:1px
8344+
style C stroke:#000000,stroke-width:1px
8345+
style F stroke:#000000,stroke-width:1px
83468346
```
83478347

83488348
Although it seems complex, users and developers are abstracted of that complexity, and tools can easily interact with the parachain as they would with any other Ethereum-compatible environment.
@@ -8377,7 +8377,7 @@ flowchart TD
83778377
A --> F[(New State)]
83788378
A --> G[Execution Logs]
83798379

8380-
style A fill:#ffffff,stroke:#000000,stroke-width:1px
8380+
style A stroke:#000000,stroke-width:1px
83818381
```
83828382

83838383

@@ -9060,7 +9060,7 @@ Pallets, which compose the runtime's logic, define the specific transactions tha
90609060

90619061
In Polkadot SDK-based networks, some nodes are authorized to author blocks. These nodes validate and process transactions. When a transaction is sent to a node that can produce blocks, it undergoes a lifecycle that involves several stages, including validation and execution. Non-authoring nodes gossip the transaction across the network until an authoring node receives it. The following diagram illustrates the lifecycle of a transaction that's submitted to a network and processed by an authoring node.
90629062

9063-
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp)
9063+
![Transaction lifecycle diagram](/images/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/transaction-lifecycle-1.webp){ style="background:white" }
90649064

90659065
### Validate and Queue
90669066

0 commit comments

Comments
 (0)