You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build/apps/example-application-tutorial/anchor-integration/sep6.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Since many of the SEP-6 (and SEP-24) endpoints require authentication, we wait u
51
51
52
52
The user can then initiate one of the transfer methods (in BasicPay, only deposits and withdraws are supported) by clicking the “Deposit” or “Withdraw” button underneath a supported asset.
Copy file name to clipboardExpand all lines: docs/build/apps/wallet/sep30.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
8
8
9
9
<Header />
10
10
11
-
The [Sep-30](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md) standard defines the standard way for an individual (e.g., a user or wallet) to regain access to their Stellar account after losing its private key without providing any third party control of the account. During this flow the wallet communicates with one or more recovery signer servers to register the wallet for a later recovery if it's needed.
11
+
The [SEP-30](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md) standard defines the standard way for an individual (e.g., a user or wallet) to regain access to their Stellar account after losing its private key without providing any third party control of the account. During this flow the wallet communicates with one or more recovery signer servers to register the wallet for a later recovery if it's needed.
Copy file name to clipboardExpand all lines: docs/build/apps/wallet/sep38.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,11 @@ import Header from "./component/header.mdx";
12
12
13
13
The [SEP-38](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md) standard defines a way for anchors to provide quotes for the exchange of an off-chain asset and a different on-chain asset, and vice versa. Quotes may be [indicative](https://www.investopedia.com/terms/i/indicativequote.asp) or [firm](https://www.investopedia.com/terms/f/firmquote.asp) ones. When either is used is explained in the sections below.
14
14
15
-
## Creating Sep-38 Object
15
+
## Creating SEP-38 Object
16
16
17
17
Let's start with creating a sep38 object, which we'll use for all SEP-38 interactions. Authentication is optional for these requests, and depends on the anchor implementation. For our example we will include it.
18
18
19
-
Authentication is done using [Sep-10](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md), and we add the authentication token to the sep38 object.
19
+
Authentication is done using [SEP-10](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md), and we add the authentication token to the sep38 object.
Copy file name to clipboardExpand all lines: docs/build/apps/wallet/sep7.mdx
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
8
8
9
9
<Header />
10
10
11
-
The [Sep-7](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md) standard defines a way for a non-wallet application to construct a URI scheme that represents a specific transaction for an account to sign. The scheme used is `web+stellar`, followed by a colon. Example: `web+stellar:<operation>?<param1>=<value1>&<param2>=<value2>`
11
+
The [SEP-7](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md) standard defines a way for a non-wallet application to construct a URI scheme that represents a specific transaction for an account to sign. The scheme used is `web+stellar`, followed by a colon. Example: `web+stellar:<operation>?<param1>=<value1>&<param2>=<value2>`
// uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
30
+
// uri can be parsed and transaction can be signed/submitted by an application that implements SEP-7
31
31
```
32
32
33
33
```dart
@@ -39,7 +39,7 @@ final xdr = Uri.encodeComponent(tx.toEnvelopeXdrBase64());
39
39
final callback = Uri.encodeComponent('https://example.com/callback');
40
40
final txUri = 'web+stellar:tx?xdr=$xdr&callback=$callback';
41
41
final uri = wallet.parseSep7Uri(txUri);
42
-
// uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
42
+
// uri can be parsed and transaction can be signed/submitted by an application that implements SEP-7
43
43
```
44
44
45
45
```swift
@@ -51,12 +51,12 @@ let xdr = try tx.encodedEnvelope().addingPercentEncoding(withAllowedCharacters:
51
51
let callback ="https://example.com/callback".addingPercentEncoding(withAllowedCharacters: .urlHostAllowed) // url encoded
52
52
let txUri ="web+stellar:tx?xdr=\(xdr!)&callback=\(callback!)"
53
53
let uri =try wallet.parseSep7Uri(uri: txUri)
54
-
// uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
54
+
// uri can be parsed and transaction can be signed/submitted by an application that implements SEP-7
55
55
```
56
56
57
57
</WalletCodeExample>
58
58
59
-
You can set replacements to be made in the xdr for specific fields by the application, these will be added in the [Sep-11 transaction representation format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md) to the URI.
59
+
You can set replacements to be made in the xdr for specific fields by the application, these will be added in the [SEP-11 transaction representation format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md) to the URI.
60
60
61
61
<WalletCodeExample>
62
62
@@ -153,7 +153,7 @@ const message = encodeURIComponent("pay me with lumens");
// uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
156
+
// uri can be parsed and transaction can be built/signed/submitted by an application that implements SEP-7
157
157
```
158
158
159
159
```dart
@@ -166,7 +166,7 @@ final message = Uri.encodeComponent('pay me with lumens');
166
166
const originDomain = 'example.com';
167
167
final payUri = 'web+stellar:pay?destination=$destination&amount=$amount&memo=$memo&msg=$message&origin_domain=$originDomain&asset_issuer=$assetIssuer&asset_code=$assetCode';
168
168
final uri = Sep7.parseSep7Uri(payUri);
169
-
// uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
169
+
// uri can be parsed and transaction can be built/signed/submitted by an application that implements SEP-7
170
170
```
171
171
172
172
```swift
@@ -179,7 +179,7 @@ let message = "pay me with lumens".addingPercentEncoding(withAllowedCharacters:
179
179
let originDomain ="example.com"
180
180
let payUri ="web+stellar:pay?destination=\(destination)&amount=\(amount)&memo=\(memo)&msg=\(message!)&origin_domain=\(originDomain)&asset_issuer=\(assetIssuer)&asset_code=\(assetCode)"
181
181
uri =try Sep7.parseSep7Uri(uri: payUri)
182
-
// uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
182
+
// uri can be parsed and transaction can be built/signed/submitted by an application that implements SEP-7
Copy file name to clipboardExpand all lines: docs/data/oracles/oracle-providers.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Oracles exist on the Stellar network to bring off-chain data onto the blockchain
11
11
12
12
The Reflector oracle protocol is a combination of specialized smart contracts and peer-to-peer consensus of data provider nodes maintained by trusted Stellar ecosystem organizations. Feeds include on-chain and off-chain asset prices, CEX & DEX exchange rates, foreign exchange rates, etc. Reflector nodes process, normalize, aggregate, and store trades information from Stellar Classic DEX, Soroban protocols, as well as external sources.
13
13
14
-
Publicly availble free price oracles are compatible with [SEP40](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0040.md) ecosystem standard interface. Learn how to integrate Reflector feeds [in their documentation](https://reflector.network/docs).
14
+
Publicly availble free price oracles are compatible with [SEP-40](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0040.md) ecosystem standard interface. Learn how to integrate Reflector feeds [in their documentation](https://reflector.network/docs).
15
15
16
16
[Reflector Subscriptions](https://reflector.network/subscription) provide a service for user-defined customized triggers invoked automatically once the price change for a specified symbol reaches a certain threshold. When the condition is met, cluster nodes simultaneously push a notification to the WebHook URL provided in the subscription and publish an on-chain proof of the triggered event.
Copy file name to clipboardExpand all lines: docs/platforms/stellar-disbursement-platform/admin-guide/security.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ SDP enforces rate limiting at the HTTP layer to curb scripted abuse. Each unique
41
41
42
42
### Authentication and Authorization Models
43
43
44
-
All authenticated API routes require clients to present either an SDP-issued API key or a JWT derived from the SEP10/SEP24 flows. These two mechanisms run in parallel: JWTs are for interactive users, while API keys enable programmatic integrations with their own scoping model.
44
+
All authenticated API routes require clients to present either an SDP-issued API key or a JWT derived from the SEP-10/SEP-24 flows. These two mechanisms run in parallel: JWTs are for interactive users, while API keys enable programmatic integrations with their own scoping model.
0 commit comments