Skip to content

Commit 261009f

Browse files
TjemmmicTjemmmic
committed
chore: prettier
1 parent 6919f7f commit 261009f

File tree

11 files changed

+46
-43
lines changed

11 files changed

+46
-43
lines changed

‎pages/developers/blueprint-runner/background-services.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,4 +76,4 @@ Now that you understand background services, it might be helpful to take a look
7676

7777
## Conclusion
7878

79-
Background services are powerful components that enhance the capabilities of your Blueprint Runner by providing continuous support operations. By implementing well-designed background services, you can build more robust, efficient, and feature-rich Blueprints.
79+
Background services are powerful components that enhance the capabilities of your Blueprint Runner by providing continuous support operations. By implementing well-designed background services, you can build more robust, efficient, and feature-rich Blueprints.

‎pages/developers/blueprint-runner/building.mdx‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,7 @@ The [router](/developers/blueprint-runner/routers) directs job calls to the appr
7979
/>
8080

8181
This configuration:
82+
8283
1. Creates a new router
8384
2. Adds a route for the `square` job with ID `XSQUARE_JOB_ID`
8485
3. Applies the `TangleLayer` to add metadata to job results
@@ -175,4 +176,4 @@ After building your Blueprint Runner, you might want to explore:
175176

176177
## Conclusion
177178

178-
Building a Blueprint Runner involves setting up various components that work together to execute your Tangle Blueprint. By following this guide and adhering to best practices, you can create a robust and efficient Blueprint Runner for your Actively Validated Service on the Tangle Network.
179+
Building a Blueprint Runner involves setting up various components that work together to execute your Tangle Blueprint. By following this guide and adhering to best practices, you can create a robust and efficient Blueprint Runner for your Actively Validated Service on the Tangle Network.

‎pages/developers/blueprint-runner/consumers.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,4 +96,4 @@ Now that you understand consumers, learn about:
9696

9797
## Conclusion
9898

99-
Consumers are essential components that translate job results into meaningful actions in your Blueprint Runner. By implementing robust and efficient consumers, you can ensure that your Blueprint operates reliably and effectively.
99+
Consumers are essential components that translate job results into meaningful actions in your Blueprint Runner. By implementing robust and efficient consumers, you can ensure that your Blueprint operates reliably and effectively.

‎pages/developers/blueprint-runner/introduction.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,4 +90,4 @@ The Blueprint Runner follows a well-defined lifecycle to ensure reliable executi
9090

9191
## Next Steps
9292

93-
Ready to build your own Blueprint Runner? Check out our [step-by-step guide](/developers/blueprint-runner/building) to get started.
93+
Ready to build your own Blueprint Runner? Check out our [step-by-step guide](/developers/blueprint-runner/building) to get started.

‎pages/developers/blueprint-runner/jobs.mdx‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,7 @@ Here's an example of a simple job definition from the Incredible Squaring exampl
3939
/>
4040

4141
In this example:
42+
4243
- `XSQUARE_JOB_ID` is a constant that uniquely identifies the job
4344
- `square` is the function that implements the job's logic
4445
- The job takes a single input parameter `x` of type `i32`
@@ -100,4 +101,4 @@ Now that you understand jobs, it might be helpful to take a look at:
100101

101102
## Conclusion
102103

103-
Jobs are the core building blocks of your Blueprint, encapsulating the business logic that processes events and produces meaningful results. By implementing well-designed jobs, you can create powerful and flexible Blueprints that can handle a wide range of use cases.
104+
Jobs are the core building blocks of your Blueprint, encapsulating the business logic that processes events and produces meaningful results. By implementing well-designed jobs, you can create powerful and flexible Blueprints that can handle a wide range of use cases.

‎pages/developers/blueprint-runner/producers.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Producers are a key component of the [Blueprint Runner](/developers/blueprint-ru
1313
In a Blueprint Runner, producers are responsible for:
1414

1515
1. Listening for events from a given source (e.g., blockchain events, polling calls, etc.)
16-
2. Preparing events to be passed to a job for processing, with the router
16+
2. Preparing events to be passed to a job for processing, with the router
1717

1818
Producers act as the input handlers of your Blueprint Runner, ensuring that external events are properly captured and processed.
1919

@@ -91,4 +91,4 @@ Now that you understand producers, learn about:
9191

9292
## Conclusion
9393

94-
Producers are essential components that capture and prepare events for processing in your Blueprint Runner. By implementing robust and efficient producers, you can ensure that your Blueprint reliably processes desired events.
94+
Producers are essential components that capture and prepare events for processing in your Blueprint Runner. By implementing robust and efficient producers, you can ensure that your Blueprint reliably processes desired events.

‎pages/developers/blueprint-runner/routers.mdx‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,9 @@ Below is a real example from our Incredible Squaring Blueprint Example:
5454
Layers are used to filter job calls based on certain criteria. There are two places layers can be used:
5555

5656
1. A specific Route:
57-
- A job can be given a layer. This can be seen in the above code example, where the job is in the `TangleLayer`. This allows the consumer, which operates in that layer, to see the results from that job. This simplifies your Blueprint when you have many jobs, routes, and consumers.
57+
- A job can be given a layer. This can be seen in the above code example, where the job is in the `TangleLayer`. This allows the consumer, which operates in that layer, to see the results from that job. This simplifies your Blueprint when you have many jobs, routes, and consumers.
5858
2. A whole Router:
59-
- A layer can be used to filter job calls based on some criteria. This can also be seen in the above code example, where the router is given a filter for the service ID. This allows the router to only process jobs with a matching service ID.
59+
- A layer can be used to filter job calls based on some criteria. This can also be seen in the above code example, where the router is given a filter for the service ID. This allows the router to only process jobs with a matching service ID.
6060

6161
## Integration with Other Components
6262

@@ -75,4 +75,4 @@ Now that you understand routers, check out:
7575

7676
## Conclusion
7777

78-
Routers are a fundamental component of Blueprint Runners, enabling efficient job execution and management. By properly configuring and utilizing routers, you can build robust and performant Blueprints and AVSs.
78+
Routers are a fundamental component of Blueprint Runners, enabling efficient job execution and management. By properly configuring and utilizing routers, you can build robust and performant Blueprints and AVSs.

‎pages/developers/eigenlayer-avs/bls-example.mdx‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -41,17 +41,17 @@ You will be prompted for each contract's constructor arguments (if it has any).
4141

4242
### Default Addresses for demo deployment
4343

44-
| Address | Value |
45-
| -------------------- | -------------------------------------------- |
46-
| Registry Coordinator | Obtained from Deployment output |
47-
| Pauser Registry | Obtained from Deployment output |
48-
| Initial Owner | 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 |
49-
| Aggregator | 0xa0Ee7A142d267C1f36714E4a8F75612F20a79720 |
50-
| Generator | 0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65 |
51-
| AVS Directory | 0x5fc8d32690cc91d4c39d9d3abcbd16989f875707 |
52-
| Rewards Coordinator | 0xb7f8bc63bbcad18155201308c8f3540b07f84f5e |
53-
| Stake Registry | 0x4c5859f0f772848b2d91f1d83e2fe57935348029 |
54-
| Tangle Task Manager | Obtained from Deployment output |
44+
| Address | Value |
45+
| -------------------- | ------------------------------------------ |
46+
| Registry Coordinator | Obtained from Deployment output |
47+
| Pauser Registry | Obtained from Deployment output |
48+
| Initial Owner | 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 |
49+
| Aggregator | 0xa0Ee7A142d267C1f36714E4a8F75612F20a79720 |
50+
| Generator | 0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65 |
51+
| AVS Directory | 0x5fc8d32690cc91d4c39d9d3abcbd16989f875707 |
52+
| Rewards Coordinator | 0xb7f8bc63bbcad18155201308c8f3540b07f84f5e |
53+
| Stake Registry | 0x4c5859f0f772848b2d91f1d83e2fe57935348029 |
54+
| Tangle Task Manager | Obtained from Deployment output |
5555

5656
Once all contracts have been deployed, you will notice that it continues running to keep the testnet alive.
5757

‎pages/developers/eigenlayer-avs/bls-template.mdx‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -68,17 +68,17 @@ cargo tangle blueprint deploy eigenlayer \
6868

6969
If you're using the template as is, you can find the addresses of the contracts you need in your project's settings.env file. Others are below.
7070

71-
| Address | Value |
72-
| -------------------- | -------------------------------------------- |
73-
| Registry Coordinator | Obtained from Deployment output |
74-
| Pauser Registry | Obtained from Deployment output |
75-
| Initial Owner | 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 |
76-
| Aggregator | 0xa0Ee7A142d267C1f36714E4a8F75612F20a79720 |
77-
| Generator | 0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65 |
78-
| AVS Directory | 0x5fc8d32690cc91d4c39d9d3abcbd16989f875707 |
79-
| Rewards Coordinator | 0xb7f8bc63bbcad18155201308c8f3540b07f84f5e |
80-
| Stake Registry | 0x4c5859f0f772848b2d91f1d83e2fe57935348029 |
81-
| Tangle Task Manager | Obtained from Deployment output |
71+
| Address | Value |
72+
| -------------------- | ------------------------------------------ |
73+
| Registry Coordinator | Obtained from Deployment output |
74+
| Pauser Registry | Obtained from Deployment output |
75+
| Initial Owner | 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 |
76+
| Aggregator | 0xa0Ee7A142d267C1f36714E4a8F75612F20a79720 |
77+
| Generator | 0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65 |
78+
| AVS Directory | 0x5fc8d32690cc91d4c39d9d3abcbd16989f875707 |
79+
| Rewards Coordinator | 0xb7f8bc63bbcad18155201308c8f3540b07f84f5e |
80+
| Stake Registry | 0x4c5859f0f772848b2d91f1d83e2fe57935348029 |
81+
| Tangle Task Manager | Obtained from Deployment output |
8282

8383
Once all contracts have been deployed, you will notice that it continues running to keep the testnet alive.
8484

‎pages/developers/eigenlayer-avs/ecdsa-template.mdx‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -66,17 +66,17 @@ cargo tangle blueprint deploy eigenlayer \
6666

6767
If you're using the template as is, you can find the addresses of the contracts you need in your project's settings.env file. Others are below.
6868

69-
| Address | Value |
70-
| -------------------- | -------------------------------------------- |
71-
| Registry Coordinator | Obtained from Deployment output |
72-
| Pauser Registry | Obtained from Deployment output |
73-
| Initial Owner | 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 |
74-
| Aggregator | 0xa0Ee7A142d267C1f36714E4a8F75612F20a79720 |
75-
| Generator | 0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65 |
76-
| AVS Directory | 0x5fc8d32690cc91d4c39d9d3abcbd16989f875707 |
77-
| Rewards Coordinator | 0xb7f8bc63bbcad18155201308c8f3540b07f84f5e |
78-
| Stake Registry | Obtained from Deployment output |
79-
| Tangle Task Manager | Obtained from Deployment output |
69+
| Address | Value |
70+
| -------------------- | ------------------------------------------ |
71+
| Registry Coordinator | Obtained from Deployment output |
72+
| Pauser Registry | Obtained from Deployment output |
73+
| Initial Owner | 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 |
74+
| Aggregator | 0xa0Ee7A142d267C1f36714E4a8F75612F20a79720 |
75+
| Generator | 0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65 |
76+
| AVS Directory | 0x5fc8d32690cc91d4c39d9d3abcbd16989f875707 |
77+
| Rewards Coordinator | 0xb7f8bc63bbcad18155201308c8f3540b07f84f5e |
78+
| Stake Registry | Obtained from Deployment output |
79+
| Tangle Task Manager | Obtained from Deployment output |
8080

8181
Once all contracts have been deployed, you will notice that it continues running to keep the testnet alive.
8282

0 commit comments

Comments
 (0)