From 74cae318dca364d315ac49d732c226bbde71f026 Mon Sep 17 00:00:00 2001 From: cfranceschi-ledger Date: Mon, 29 Jan 2024 18:25:53 +0100 Subject: [PATCH 1/5] fix links device apps --- pages/docs/device-app/architecture.mdx | 18 +++++++++--------- .../deliver/deliverables/ui-flow-video.mdx | 2 +- pages/docs/device-app/deliver/maintenance.mdx | 2 +- pages/docs/device-app/develop.mdx | 2 +- pages/docs/device-app/develop/faq.mdx | 2 +- .../develop/sdk/ui/ledger-nano-display.mdx | 12 ++++-------- .../low-level-display-management.mdx | 2 +- pages/docs/device-app/develop/tutorials.mdx | 8 ++++---- .../device-app/develop/tutorials/plugin.mdx | 2 -- pages/docs/device-app/introduction.mdx | 6 +++--- pages/docs/device-app/introduction/clones.mdx | 10 +++++----- 11 files changed, 30 insertions(+), 36 deletions(-) diff --git a/pages/docs/device-app/architecture.mdx b/pages/docs/device-app/architecture.mdx index 69538662..d756f92e 100644 --- a/pages/docs/device-app/architecture.mdx +++ b/pages/docs/device-app/architecture.mdx @@ -5,25 +5,25 @@ import { Cards, Card } from 'nextra/components' This chapter talks about key concept of what a Personnal Security Device (PSD) is and why it is needed, the design of such a device, and more specific high-level consideration on the Ledger PSDs: UI, BOLOS and such. - + - + \ No newline at end of file diff --git a/pages/docs/device-app/deliver/deliverables/ui-flow-video.mdx b/pages/docs/device-app/deliver/deliverables/ui-flow-video.mdx index ac3cfe69..0978921e 100644 --- a/pages/docs/device-app/deliver/deliverables/ui-flow-video.mdx +++ b/pages/docs/device-app/deliver/deliverables/ui-flow-video.mdx @@ -61,4 +61,4 @@ If blind signing is implemented: - Sign a blind signed transaction while setting is disabled - Sign a blind signed transaction while setting is enabled -*Reminder : Blind signed operations must only be accessible behind a setting that must be disabled by default ([see blind signing section](../design#blind-signing))* +*Reminder : Blind signed operations must only be accessible behind a setting that must be disabled by default ([see blind signing section](../../develop/requirements/security#blind-signing))* diff --git a/pages/docs/device-app/deliver/maintenance.mdx b/pages/docs/device-app/deliver/maintenance.mdx index 37b0d2c8..4f0706d7 100644 --- a/pages/docs/device-app/deliver/maintenance.mdx +++ b/pages/docs/device-app/deliver/maintenance.mdx @@ -6,7 +6,7 @@ Since Ledger will not update your device app code, you are responsible for all s Application updates must be submitted alongside: - functional tests, and -- a [Security Audit](./requirements/security#security-audit) +- a [Security Audit](./deliverables/security-audit) Afterwards you will submit a new form where you can pick and choose the parts of the App that have been updated. diff --git a/pages/docs/device-app/develop.mdx b/pages/docs/device-app/develop.mdx index c518c178..0ffe22d4 100644 --- a/pages/docs/device-app/develop.mdx +++ b/pages/docs/device-app/develop.mdx @@ -32,7 +32,7 @@ explanations. /> diff --git a/pages/docs/device-app/develop/faq.mdx b/pages/docs/device-app/develop/faq.mdx index a72f4150..9147795a 100644 --- a/pages/docs/device-app/develop/faq.mdx +++ b/pages/docs/device-app/develop/faq.mdx @@ -10,7 +10,7 @@ title: Frequently Asked Questions | What is the maximum size of a message that can be sent in a single APDU? | The length of the data part is 255 bytes and the whole message sent in a single APDU is 260 bytes with the blocks cla, ins, p1, p2 and one extra byte that encodes the length of the data that follows. | | The Ledger team can not fork a repo which is already a fork on LedgerHQ *(e.g. ledger-panacea is a clone of ledger-cosmos but LedgerHQ has already a fork of ledger-cosmos)*. | This is a limitation of GitHub and the only solution for this is to break the link between the repository and the upstream one. This is done like in this [tutorial](https://ralphjsmit.com/unfork-github-repo). | | Can I freely choose the CLA in my embedded app as long as it is one byte or is there eanything I need to be aware of? | Apart from not using a few CLAs that are reserved for the SDK, OS, etc, developers are free to choose. For example, `0xB0` is for SDK. | -| How can I load an app without Ledger Live on my ledger nano S or S+? | Here are the links [to the documentation](./develop/quickstart#build--load-an-application). | +| How can I load an app without Ledger Live on my ledger nano S or S+? | Here are the links [to the documentation](./quickstart#build--load-an-application). | | When I build the application, I have this error message: `No targets specified and no makefile found`. | You need to go down one level in the repo to the app subfolder and then run the `make` command. You must have launched your ledger-app-builder before. | | I'm getting the error message `Ledger device: CLA_NOT_SUPPORTED`. | Many reasons could occur this error: the embedded app does not support the functionality you are implementing yet, you opened the wrong embedded app, or the CLA byte is not correctly set.| | How do I verify that my product is genuine (in CLI)? | You can check it by connecting your hardware wallet and executing the following commands in this [documentation](https://support.ledger.com/hc/en-us/articles/4404382029329-Check-hardware-integrity?support=true). | diff --git a/pages/docs/device-app/develop/sdk/ui/ledger-nano-display.mdx b/pages/docs/device-app/develop/sdk/ui/ledger-nano-display.mdx index c2feab06..cad66bdc 100644 --- a/pages/docs/device-app/develop/sdk/ui/ledger-nano-display.mdx +++ b/pages/docs/device-app/develop/sdk/ui/ledger-nano-display.mdx @@ -1,20 +1,16 @@ import { Cards, Card } from 'nextra/components' - + - \ No newline at end of file diff --git a/pages/docs/device-app/develop/sdk/ui/ledger-nano-display/low-level-display-management.mdx b/pages/docs/device-app/develop/sdk/ui/ledger-nano-display/low-level-display-management.mdx index 0671ce7a..76a270ee 100755 --- a/pages/docs/device-app/develop/sdk/ui/ledger-nano-display/low-level-display-management.mdx +++ b/pages/docs/device-app/develop/sdk/ui/ledger-nano-display/low-level-display-management.mdx @@ -49,7 +49,7 @@ See [the sample apps](https://github.com/LedgerHQ/ledger-sample-apps) for exampl ## BOLOS UX -The BOLOS UX is the implementation of the device-wide user interface; it is a component of the [dashboard application](../../bolos#dashboard). Applications delegate certain jobs to the BOLOS UX in order to retain consistency across all apps for certain UI components, as well as to allow the operating system to override the application's UI when necessary (for example, when locking the screen). The application interfaces with the BOLOS UX using `os_ux(...)`, which is a system call. However, applications don't need to call this function as it is automatically called by the display interaction helpers (the `UX_` macros). +The BOLOS UX is the implementation of the device-wide user interface; it is a component of the [dashboard application](../../../../architecture/bolos#dashboard). Applications delegate certain jobs to the BOLOS UX in order to retain consistency across all apps for certain UI components, as well as to allow the operating system to override the application's UI when necessary (for example, when locking the screen). The application interfaces with the BOLOS UX using `os_ux(...)`, which is a system call. However, applications don't need to call this function as it is automatically called by the display interaction helpers (the `UX_` macros). Applications should delegate **Events** like **Button Push Events** to the BOLOS UX (in this case, using `UX_BUTTON_PUSH_EVENT(...)`) instead of handling them directly, in case the BOLOS UX needs to override the application's UI. If the event is consumed by the BOLOS UX (for example, a pressed button while the user is unlocking the screen) then the event is not passed on to the application. diff --git a/pages/docs/device-app/develop/tutorials.mdx b/pages/docs/device-app/develop/tutorials.mdx index 41039f38..5030673f 100644 --- a/pages/docs/device-app/develop/tutorials.mdx +++ b/pages/docs/device-app/develop/tutorials.mdx @@ -7,18 +7,18 @@ need: diff --git a/pages/docs/device-app/develop/tutorials/plugin.mdx b/pages/docs/device-app/develop/tutorials/plugin.mdx index e88f16d3..81ddfe01 100644 --- a/pages/docs/device-app/develop/tutorials/plugin.mdx +++ b/pages/docs/device-app/develop/tutorials/plugin.mdx @@ -43,5 +43,3 @@ Ledger designed and implemented Paraswap, the first Ethereum plugin. We will walk through the plugin Boilerplate example, which is a DApp Plugin for Ethereum. This will help you code your plugin. Remember, the plugin gets called repeatedly by the Ethereum Application and answers with the appropriate message status. - -The complete interaction is detailed in the [reference flow](./plugin/flow/). diff --git a/pages/docs/device-app/introduction.mdx b/pages/docs/device-app/introduction.mdx index 03b40f21..086996a0 100644 --- a/pages/docs/device-app/introduction.mdx +++ b/pages/docs/device-app/introduction.mdx @@ -30,7 +30,7 @@ Joining Discord is not required to code your device application, but it will be ### Understand the process & meet the requirements -Ensure that you have a clear understanding of the [Process](./deliver/process) and are able to meet the [Requirements](./deliver/requirements) listed here. +Ensure that you have a clear understanding of the [Process](./deliver/process) and are able to meet the [Requirements](./develop/requirements) and produce the [deliverables](./deliver/deliverables). ### Begin Coding @@ -39,7 +39,7 @@ Device applications are primarily developed in C using the Blockchain Open Ledge To develop a device application, ensure that you: - Use Linux, Mac or Windows -- Know about the [Ledger Framework](./develop/tutorials/quickstart) and all the [environment tools](./develop/tools) +- Know about the [Ledger Framework](./develop/quickstart) and all the [environment tools](./develop/tools) - Know how to test your application, using either a physical device or the [Speculos emulator](./develop/tools#speculos) @@ -66,7 +66,7 @@ Ledger Personal Security Devices provide a secure and convenient way for users t | Component | Developing language | | ----------------------- | ------------------- | -| OS [Bolos](../bolos) | `C` | +| OS [Bolos](./architecture/bolos) | `C` | | Applications | `C` or `Rust` (WIP) | | Plugins | `C` | | Tools (including tests) | `Python` (mostely) | diff --git a/pages/docs/device-app/introduction/clones.mdx b/pages/docs/device-app/introduction/clones.mdx index c789d4ea..a18665b9 100644 --- a/pages/docs/device-app/introduction/clones.mdx +++ b/pages/docs/device-app/introduction/clones.mdx @@ -17,11 +17,11 @@ You don't need to follow all the coding guidelines. Only follow the steps below: | | Eth Clones | -----------------------------------------------------------------------|:----------:| -| [Blind Signing](../deliver/requirements/design#blind-signing) | Depends | -| [Icon](../deliver/requirements/deliverables/icons/) | **Yes** | -| [Documentation](../deliver/requirements/deliverables/documentation/) | Depends | -| [Functional Tests](../deliver/requirements/development) | **Yes** | -| [Warranty / Liability acceptance](../deliver/requirements/legal) | **Yes** | +| [Blind Signing](../develop/requirements/security#blind-signing) | Depends | +| [Icon](../deliver/deliverables/icons/) | **Yes** | +| [Documentation](../deliver/deliverables/documentation/) | Depends | +| [Functional Tests](../develop/requirements/development) | **Yes** | +| [Warranty / Liability acceptance](../deliver/deliverables/legal) | **Yes** | ### 2. Build & Load and use the Ledger framework From 354532ccb339b3640aca25fe96720ed8707e65fc Mon Sep 17 00:00:00 2001 From: cfranceschi-ledger Date: Tue, 30 Jan 2024 09:29:11 +0100 Subject: [PATCH 2/5] fix device app links --- .../architecture/psd/application-isolation.mdx | 2 +- pages/docs/device-app/develop/environment.mdx | 2 +- pages/docs/device-app/develop/sdk.mdx | 10 +++++----- pages/docs/device-app/develop/tutorials/clone.mdx | 10 +++++----- .../develop/tutorials/plugin/boilerplate-plugin.mdx | 7 ++++--- .../device-app/develop/tutorials/plugin/selectors.mdx | 2 +- 6 files changed, 17 insertions(+), 16 deletions(-) diff --git a/pages/docs/device-app/architecture/psd/application-isolation.mdx b/pages/docs/device-app/architecture/psd/application-isolation.mdx index 7fd8accf..017f13d1 100755 --- a/pages/docs/device-app/architecture/psd/application-isolation.mdx +++ b/pages/docs/device-app/architecture/psd/application-isolation.mdx @@ -18,7 +18,7 @@ When an application performs a syscall, the Secure Element switches to Superviso ## Accessing secrets The access that applications have to cryptographic secrets managed by the operating system can be configured when -loading an application onto the device (this is actually [a required metadata for an application to be deployed](../../deliver/requirements/security#derivation-path)). +loading an application onto the device (this is actually [a required metadata for an application to be deployed](../../develop/requirements/security#derivation-path)). Instead of accessing secrets like the device's master seed directly, applications instead have to use syscalls, i.e to request the operating system to derive a node from the master seed by providing the operating system with a path to the requested node. When the application is loaded, the BIP 32 paths that the application is permitted to derive nodes from diff --git a/pages/docs/device-app/develop/environment.mdx b/pages/docs/device-app/develop/environment.mdx index 571ef8cb..160c80ff 100644 --- a/pages/docs/device-app/develop/environment.mdx +++ b/pages/docs/device-app/develop/environment.mdx @@ -40,7 +40,7 @@ It includes the following capabilities: Ledger provides several workflows to ease the integration of applications into the GitHub CI. -[Some of them are mandatory for an application to be deployed](../deliver/requirements/development#workflows), but +[Some of them are mandatory for an application to be deployed](./requirements/development#workflows), but the others can still be useful. diff --git a/pages/docs/device-app/develop/sdk.mdx b/pages/docs/device-app/develop/sdk.mdx index 60323c40..2aa71d10 100644 --- a/pages/docs/device-app/develop/sdk.mdx +++ b/pages/docs/device-app/develop/sdk.mdx @@ -1,21 +1,21 @@ import { Cards, Card } from 'nextra/components' - + diff --git a/pages/docs/device-app/develop/tutorials/clone.mdx b/pages/docs/device-app/develop/tutorials/clone.mdx index 8c630b3e..fcc4e863 100644 --- a/pages/docs/device-app/develop/tutorials/clone.mdx +++ b/pages/docs/device-app/develop/tutorials/clone.mdx @@ -37,7 +37,7 @@ For any other clone type, use the [main Device App process](../quickstart/). #### Update an existing clone -If your Bitcoin clone was included in the Bitcoin Deice App and you need to update it, please start a [new Device App process](../introduction/). +If your Bitcoin clone was included in the Bitcoin Deice App and you need to update it, please start a [new Device App process](../../introduction/). ## A - Using the 44/60 path @@ -68,7 +68,7 @@ Add your chain ID, chain name and Ticker to [network.c](https://github.com/Ledge ### 2. Add an icon for Ledger Stax Add your 64x64px gif icon in the `glyphs` folder following this naming convention: `stax_yourchainid_64px.gif`. -Use the template provided [here](../deliverables/icons#stax-template). +Use the template provided [here](../../deliver/deliverables/icons#stax-template). ### 3. Add your Network to Chainlist.org and SLIP-0044 @@ -124,11 +124,11 @@ APPNAME = "WaltonChain" - Add your 16x16px Nanos , 14x14px Nano S Plus / Nano X and 32x32 Stax gif icons in the `icons` folder following these naming conventions: `nanos_app_chain_yourchainid.gif`, `nanox_app_chain_yourchainid.gif`, `stax_app_chain_yourchainid.gif` - Add your 64x64px gif icon in the `icons` folder following this naming convention: `stax_yourchainid_64px.gif`. -Use the template provided [here](../deliverables/icons#stax-template). +Use the template provided [here](../../deliver/deliverables/icons). ### 3. Build the application -To build the clone application, [follow these guidelines](../quickstart/build-load/). +To build the clone application, [follow these guidelines](../quickstart). 1. First run the `make` command for the Ethereum App and run `make load` 2. Run `make clean` 2. Load the Device App clone with the name of your chain. E.g: `make load CHAIN=tomochain` @@ -146,4 +146,4 @@ Please get in touch with our team on the [Ledger's Discord server](https://devel ### Publishing the application -If you want to publish a clone application, follow the process in [Publishing an application](../submission/requirements). +If you want to publish a clone application, follow the process in [Publishing an application](../../deliver). diff --git a/pages/docs/device-app/develop/tutorials/plugin/boilerplate-plugin.mdx b/pages/docs/device-app/develop/tutorials/plugin/boilerplate-plugin.mdx index 044b575c..b820949a 100644 --- a/pages/docs/device-app/develop/tutorials/plugin/boilerplate-plugin.mdx +++ b/pages/docs/device-app/develop/tutorials/plugin/boilerplate-plugin.mdx @@ -18,7 +18,7 @@ cd app-ethereum ## Build the Ethereum App -You can easily build the Ethereum app by following these [instructions](../../device-app/develop/quickstart). +You can easily build the Ethereum app by following these [instructions](../../quickstart). Once you've successfully compiled the Ethereum app you are ready to walk through the Boilerplate plugin example. @@ -37,10 +37,11 @@ git clone --recurse-submodules https://github.com/LedgerHQ/app-plugin-boilerplat There is no need to build it right now, only after adding tests. For now, in `app-plugin-boilerplate/` there are these folders: - `ethereum-plugin-sdk`: This repository contains information shared by the Ethereum app and your plugin, such as structure definitions, utility functions, etc. -- `icons` and `glyphs` : plugin icons as displayed on the device. We will get to it later, but you can read about it [here](../../device-app/deliverables/icons/#device-icon). +- `icons` and `glyphs` : plugin icons as displayed on the device. We will get to it later, but you can read about it [here](../../../deliver/deliverables/icons/#device-icon). - `src`: the actual source code (in C). - `tests`: the test folder (using the Ragger testing framework). -- `.github/workflows` : the CI workflows which are a requirement to submit your plugin. To have more details you can refer to this [section](../../device-app/quickstart/framework/#ci). +- `.github/workflows` : the CI workflows which are a requirement to submit your plugin. To have more details you can refer to this [section](../../environment#github-workflows). + ## Change the plugin info diff --git a/pages/docs/device-app/develop/tutorials/plugin/selectors.mdx b/pages/docs/device-app/develop/tutorials/plugin/selectors.mdx index f783c903..834e5568 100644 --- a/pages/docs/device-app/develop/tutorials/plugin/selectors.mdx +++ b/pages/docs/device-app/develop/tutorials/plugin/selectors.mdx @@ -59,5 +59,5 @@ typedef enum { ## handlers -Now we have to implement a handler for each case condition as described in the [reference flow](./flow). They must all have a corresponding `handle_*.c` located in `src/`. +Now we have to implement a handler for each case condition. They must all have a corresponding `handle_*.c` located in `src/`. From b4b970d6649eb2611f1422c4d97bf79c238dc98b Mon Sep 17 00:00:00 2001 From: cfranceschi-ledger Date: Tue, 30 Jan 2024 09:46:32 +0100 Subject: [PATCH 3/5] fix exchange links --- pages/docs/device-app/develop/quickstart.mdx | 2 +- pages/docs/exchange/integration.mdx | 2 +- pages/docs/exchange/integration/providers-liveapp.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/docs/device-app/develop/quickstart.mdx b/pages/docs/device-app/develop/quickstart.mdx index 1b4b0f98..83716ee0 100644 --- a/pages/docs/device-app/develop/quickstart.mdx +++ b/pages/docs/device-app/develop/quickstart.mdx @@ -11,7 +11,7 @@ To get your project started quickly, we provide a complete framework made to dev - Several boilerplate applications, to be used as a modifyable bases to create your own application: - [A `C` Boilerplate](https://github.com/LedgerHQ/app-boilerplate) - [A `Rust` Boilerplate](https://github.com/LedgerHQ/app-boilerplate-rust) and - - [A Plugin Boilerplate](https://github.com/LedgerHQ/app-pluginboilerplate) + - [A Plugin Boilerplate](https://github.com/LedgerHQ/app-plugin-boilerplate) More information on these components can be found in the [tutorials](./tutorials), [environment](./environment) and [tools](./tools) sections. diff --git a/pages/docs/exchange/integration.mdx b/pages/docs/exchange/integration.mdx index 03a07eb2..67403e89 100644 --- a/pages/docs/exchange/integration.mdx +++ b/pages/docs/exchange/integration.mdx @@ -32,7 +32,7 @@ Test end-to-end your integration as much as possible with some tools we provide, *: Not needed for BUY. In the following pages, you will find: -- [Backend](integration/providers-endpoints): details on the main endpoints needed for the chosen operation, the payload, the signature, and your public/private key. +- [Backend](integration/providers-backend): details on the main endpoints needed for the chosen operation, the payload, the signature, and your public/private key. - [LiveApp](integration/providers-liveapp): details on your LiveApp specifities, such as the deeplink's format, or the use of Exchange SDK instead of the Wallet API. - [Test & Submit](integration/providers-test-and-submit): details on how to use the Ledger Live Developer Mode and other tools (coming soon) to test your integration end-to-end, as well as how to submit it. - [[Reference] Advanced Flows](integration/flow): Details on advanced flows and architecture diagrams. diff --git a/pages/docs/exchange/integration/providers-liveapp.mdx b/pages/docs/exchange/integration/providers-liveapp.mdx index d7024e86..f8f54ccd 100644 --- a/pages/docs/exchange/integration/providers-liveapp.mdx +++ b/pages/docs/exchange/integration/providers-liveapp.mdx @@ -141,4 +141,4 @@ Your [LiveApp manifest](../../../../APIs/wallet-api/appendix/manifest) should co ## Flow/UX requirements -Please refer to the [Flow Breakdown](../flow/flow-breakdown) section for more information. \ No newline at end of file +Please refer to the [Flow Breakdown](../flow) section for more information. \ No newline at end of file From ed6eb778883147fba91a62541166b1ab5bac72ce Mon Sep 17 00:00:00 2001 From: cfranceschi-ledger Date: Tue, 30 Jan 2024 09:47:50 +0100 Subject: [PATCH 4/5] fix exchange link --- pages/docs/exchange/integration/providers-liveapp.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/docs/exchange/integration/providers-liveapp.mdx b/pages/docs/exchange/integration/providers-liveapp.mdx index f8f54ccd..79451862 100644 --- a/pages/docs/exchange/integration/providers-liveapp.mdx +++ b/pages/docs/exchange/integration/providers-liveapp.mdx @@ -15,7 +15,7 @@ Your LiveApp must: ## Ledger's exchange SDK -To learn how to create (or embed if already existing) your user interface for the swap/sell/buy/fund, please follow the [Discover documentation](../../../discover). +To learn how to create (or embed if already existing) your user interface for the swap/sell/buy/fund, please follow the [Discover documentation](../../discover). Your LiveApp will interact with Ledger Live, through the [ExchangeSDK](https://github.com/LedgerHQ/exchange-sdk), with the corresponding method. From 20221e72f76ae4d35762f9bd47f23a3c842263fc Mon Sep 17 00:00:00 2001 From: cfranceschi-ledger Date: Tue, 30 Jan 2024 10:08:48 +0100 Subject: [PATCH 5/5] fix links --- pages/docs/device-app/develop/tools.mdx | 2 +- pages/docs/exchange/integration/flow.mdx | 2 +- pages/docs/exchange/integration/providers-test-and-submit.mdx | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/docs/device-app/develop/tools.mdx b/pages/docs/device-app/develop/tools.mdx index bf3383cc..15d2c07d 100644 --- a/pages/docs/device-app/develop/tools.mdx +++ b/pages/docs/device-app/develop/tools.mdx @@ -33,7 +33,7 @@ high-level graphical interactions. It is widly used to write functional tests co Ledgered is a Python package which goal is to be a collection of small, autonomous utilitaries and libraries. For now, it only contains a tool (`ledger-manifest`) allowing to check `ledger_app.toml` manifest files (which are a -[requirement](../deliver/requirements/development#manifest) for an application to be deployed). +[requirement](./requirements/development#manifest) for an application to be deployed). Sources and documentation can be found [in the Ledgered repository](https://github.com/ledgerhq/ledgered). diff --git a/pages/docs/exchange/integration/flow.mdx b/pages/docs/exchange/integration/flow.mdx index 864cd995..f43d7641 100644 --- a/pages/docs/exchange/integration/flow.mdx +++ b/pages/docs/exchange/integration/flow.mdx @@ -4,7 +4,7 @@ import 'react-medium-image-zoom/dist/styles.css' # Detailled Technical Flows -For high-level flows, refer to the [flow-breakdown](../flow/flow-breakdown) section. +For high-level flows, refer to the [flow-breakdown](../flow) section. ## Swap diff --git a/pages/docs/exchange/integration/providers-test-and-submit.mdx b/pages/docs/exchange/integration/providers-test-and-submit.mdx index e741d086..d5761c4e 100644 --- a/pages/docs/exchange/integration/providers-test-and-submit.mdx +++ b/pages/docs/exchange/integration/providers-test-and-submit.mdx @@ -29,7 +29,7 @@ After testing your LiveApp and making sure it works with the Exchange App, you s ### Your API -Adapt your API to interact with our Backend, with some specifities. Details in [Backend](providers-endpoints) section. +Adapt your API to interact with our Backend, with some specifities. Details in [Backend](providers-backend) section. ### Your LiveApp's Manifest @@ -37,6 +37,6 @@ It's a bit more complex than the regular LiveApp's Manifest of the Discover sect ### Your Public key -Make sure your private key is secured, and send us your public key. Details in [Backend](providers-endpoints) section. +Make sure your private key is secured, and send us your public key. Details in [Backend](providers-backend) section.