diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 60a66d10a2..3723a525f9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -43,7 +43,7 @@ These guidelines exist because they're the difference between a PR that merges i ## Development Quickstart -We use [pnpm](https://pnpm.io/). See the [README](README.md#quick-start) for full setup. +We use [pnpm](https://pnpm.io). See the [README](README.md#quick-start) for full setup. ```bash pnpm install # install dependencies diff --git a/docs/build/apps/privacy.mdx b/docs/build/apps/privacy.mdx index 478bc6e0e9..b85a5c5d0f 100644 --- a/docs/build/apps/privacy.mdx +++ b/docs/build/apps/privacy.mdx @@ -37,7 +37,7 @@ Research prototype, not audited. Do not use in production with real assets. Proofs are generated client-side in the browser via WebAssembly — user secrets never leave the device. - **Repo**: [NethermindEth/stellar-private-payments](https://github.com/NethermindEth/stellar-private-payments) -- **Demo**: [nethermindeth.github.io/stellar-private-payments](https://nethermindeth.github.io/stellar-private-payments/) +- **Demo**: [nethermindeth.github.io/stellar-private-payments](https://nethermindeth.github.io/stellar-private-payments) ## Confidential Tokens @@ -56,7 +56,7 @@ Confidential tokens on Stellar are a developer preview. The contracts and demo l Learn more about our work with OpenZeppelin in the post [Developer Preview: Confidential Tokens on Stellar](https://stellar.org/blog/developers/developer-preview-confidential-tokens-on-stellar), published on June 29, 2026 during the Testnet preview, and watch the [Developer Preview stream with OpenZeppelin](https://youtu.be/nfbr3KuYqPE?si=n5jX6g3-azW4Lp1B) that explains more about the architecture and design choices. - **OpenZeppelin Confidential Token Repo**: [GitHub](https://github.com/OpenZeppelin/stellar-contracts/tree/feat/confidential-verifier-ultrahonk/packages/tokens/src/confidential) -- **OpenZeppelin Confidential Token Demo**: [Demo](https://stellar-confidential-token-demo.billowing-moon-0c6f.workers.dev/), [GitHub](https://github.com/brozorec/stellar-confidential-token-demo), [Video walkthrough](https://x.com/BuildOnStellar/status/2072357829353308214) +- **OpenZeppelin Confidential Token Demo**: [Demo](https://stellar-confidential-token-demo.billowing-moon-0c6f.workers.dev), [GitHub](https://github.com/brozorec/stellar-confidential-token-demo), [Video walkthrough](https://x.com/BuildOnStellar/status/2072357829353308214) - **Confidential Token Association**: [confidentialtoken.org](https://www.confidentialtoken.org) - **Confidential Token overview/demo by Jay Geng (SDF) at Meridian 2025**: [YouTube](https://www.youtube.com/watch?v=6NnDqVQYOHM) diff --git a/docs/build/building-with-ai.mdx b/docs/build/building-with-ai.mdx index f2bf2f9c69..837e903078 100644 --- a/docs/build/building-with-ai.mdx +++ b/docs/build/building-with-ai.mdx @@ -107,7 +107,7 @@ For clients without native remote/OAuth support, bridge with [`mcp-remote`](http ## Stellar Skills -[**skills.stellar.org**](https://skills.stellar.org/) is the home for Stellar Skills—a collection of AI agent skills that give your coding assistant the right Stellar context before it writes code. They work with any AI agent, and you can browse every skill on the website with no installation required. +[**skills.stellar.org**](https://skills.stellar.org) is the home for Stellar Skills—a collection of AI agent skills that give your coding assistant the right Stellar context before it writes code. They work with any AI agent, and you can browse every skill on the website with no installation required. Skills are open source and maintained in the [stellar/stellar-dev-skill](https://github.com/stellar/stellar-dev-skill) repository. @@ -127,7 +127,7 @@ The official skills cover the core areas of Stellar development: ### Community skills -The ecosystem also contributes skills for popular protocols and tools. Browse the full, up-to-date list at [skills.stellar.org](https://skills.stellar.org/). Community skills are maintained by their respective authors, so review each one to confirm it meets your security and maintenance requirements before using it. +The ecosystem also contributes skills for popular protocols and tools. Browse the full, up-to-date list at [skills.stellar.org](https://skills.stellar.org). Community skills are maintained by their respective authors, so review each one to confirm it meets your security and maintenance requirements before using it. ### stellar-build diff --git a/docs/data/analytics/analytics-providers/analytics-providers.mdx b/docs/data/analytics/analytics-providers/analytics-providers.mdx index 72c8772d62..ca5ad42b3c 100644 --- a/docs/data/analytics/analytics-providers/analytics-providers.mdx +++ b/docs/data/analytics/analytics-providers/analytics-providers.mdx @@ -22,7 +22,7 @@ The following is a list of data analytics platforms that make a complete histori {/* Allium login not working as of the writing of this doc */} -{/* | Allium | Raw dataset access to the Stellar network. | [Allium](https://www.allium.so) | Free data access and queries | For data access, checkout [Allium Docs](https://docs.allium.so/) | N/A | */} +{/* | Allium | Raw dataset access to the Stellar network. | [Allium](https://www.allium.so) | Free data access and queries | For data access, checkout [Allium Docs](https://docs.allium.so) | N/A | */} ## Run Your Own Hubble diff --git a/docs/data/apis/rpc/providers.mdx b/docs/data/apis/rpc/providers.mdx index 41cfb315ca..d9ae547a5d 100644 --- a/docs/data/apis/rpc/providers.mdx +++ b/docs/data/apis/rpc/providers.mdx @@ -23,7 +23,7 @@ These providers allow access to the Futurenet, Testnet and Mainnet network. | [Uniblock](https://www.uniblock.dev) | ❌ | ✅ | ✅ | ❌ | ❌ | | [Exaion](https://crypto.exaion.com) | ❌ | ❌ | ✅ | ✅ | ✅ | | [Alchemy](https://dashboard.alchemy.com/?utm_source=chain_partner&utm_medium=referral&utm_campaign=stellar) | ❌ | ✅ | ✅ | ✅ | ❌ | -| [GetBlock](https://getblock.io/nodes/xlm/) | ❌ | ❌ | ✅ | ✅ | ✅ | +| [GetBlock](https://getblock.io/nodes/xlm) | ❌ | ❌ | ✅ | ✅ | ✅ | \*_RPC Archive is a new option for those looking to retrieve full ledger history. Currently only the [getLedgers](./api-reference/methods/getLedgers.mdx) RPC method supports this feature. You can choose one of the providers above, or create your own getLedgers archive by following [these steps](./admin-guide/data-lake-integration.mdx)._ diff --git a/docs/tools/developer-tools/wallets.mdx b/docs/tools/developer-tools/wallets.mdx index 8db712fd93..b48cebcf19 100644 --- a/docs/tools/developer-tools/wallets.mdx +++ b/docs/tools/developer-tools/wallets.mdx @@ -47,7 +47,7 @@ Estimates the XLM requirements for wallets looking to use sponsored reserves and - [Simplified spreadsheet](https://docs.google.com/spreadsheets/d/1Vhk__s-ZrJLEgEs3N2oGEsI35RKPixD5w-qQ6uGYnO0/edit?gid=270060868#gid=270060868) - [Tutorial article and video](https://cheesecakelabs.com/blog/stellar-lumens-xlm-cost-estimator) -### [Blux](https://blux.cc/) +### [Blux](https://blux.cc) Blux is wallet infrastructure built specifically for Stellar dApps, designed to make user onboarding seamless, even for those who have never used a Stellar wallet before. Newcomers can sign in instantly with credentials they already use, while existing Stellar users can connect their preferred wallet, all through a single integration, so no one has to set up a wallet before getting started. @@ -77,9 +77,9 @@ Blux supports a broad range of Stellar ecosystem wallets: For developers, Blux ships with a comprehensive set of pre-built hooks and modals covering transaction signing, balance checking, swaps, transaction history, and on/off-ramp flows. Its SDKs offer type-safe, TypeScript-first APIs for both React and vanilla JavaScript, and the fully configurable modal system can be tailored to match each dApp's branding. You can also track and review user analytics directly from the Blux dashboard. -Learn more in the [Blux documentation](https://docs.blux.cc/). +Learn more in the [Blux documentation](https://docs.blux.cc). -### [Dfns](https://www.dfns.co/) +### [Dfns](https://www.dfns.co) A wallet-as-a-service platform that streamlines digital asset operations, offering full wallet feature support, including automatic detection of asset and NFT balances (when applicable), on-chain transfer history, asset transfers, transaction broadcasting, and signature generation. diff --git a/docs/validators/admin-guide/configuring.mdx b/docs/validators/admin-guide/configuring.mdx index 631c4ad60e..110d4fa437 100644 --- a/docs/validators/admin-guide/configuring.mdx +++ b/docs/validators/admin-guide/configuring.mdx @@ -140,7 +140,7 @@ When you add a validating node to your quorum set, it's generally because you tr In order to create a self-verified link between a node and the organization that runs it, a validator declares a home domain on-chain using a [`set_options` operation](../../learn/fundamentals/transactions/list-of-operations.mdx#set-options), and publishes organizational information in a `stellar.toml` file hosted on that domain. To find out how that works, take a look at [SEP-20]. -As a result of that link, you can look up a node by its Stellar public key and check the `stellar.toml` file to find out who runs it. It's possible to do that manually, but you can also just consult the list of nodes on [Obsrvr Radar](https://radar.withobsrvr.com/). If you decide to trust an organization, you can use that list to collect the information necessary to add their nodes to your configuration. +As a result of that link, you can look up a node by its Stellar public key and check the `stellar.toml` file to find out who runs it. It's possible to do that manually, but you can also just consult the list of nodes on [Obsrvr Radar](https://radar.withobsrvr.com). If you decide to trust an organization, you can use that list to collect the information necessary to add their nodes to your configuration. When you look at that list, you will discover that the most reliable organizations actually run more than one validator, and adding all of an organization's nodes to your quorum set creates the redundancy necessary to sustain arbitrary node failure. When an organization with a trio of nodes takes one down for maintenance, for instance, the remaining two nodes vote on the organization's behalf, and the organization's network presence persists. diff --git a/docs/validators/admin-guide/monitoring.mdx b/docs/validators/admin-guide/monitoring.mdx index 086b68155a..b6ca5ce47c 100644 --- a/docs/validators/admin-guide/monitoring.mdx +++ b/docs/validators/admin-guide/monitoring.mdx @@ -9,7 +9,7 @@ You can access this information using commands and inspecting Stellar Core's out :::info -[**Obsrvr Radar**](https://radar.withobsrvr.com/), a community-run monitoring dashboard, can also be useful for viewing network health as a whole. You should keep a very close eye on your own node(s) using some of the tools suggested on this page, but monitoring performance of all the network's nodes can also be useful to understand how they all interact with each other. +[**Obsrvr Radar**](https://radar.withobsrvr.com), a community-run monitoring dashboard, can also be useful for viewing network health as a whole. You should keep a very close eye on your own node(s) using some of the tools suggested on this page, but monitoring performance of all the network's nodes can also be useful to understand how they all interact with each other. ::: diff --git a/docs/validators/admin-guide/prerequisites.mdx b/docs/validators/admin-guide/prerequisites.mdx index 7826ffd6b0..24d05741a5 100644 --- a/docs/validators/admin-guide/prerequisites.mdx +++ b/docs/validators/admin-guide/prerequisites.mdx @@ -81,7 +81,7 @@ Local clock is off by ms versus NTP server If you see this warning, fix your clock synchronization. Even if you have never seen it, we strongly recommend running an NTP service on every node. -We recommend [chrony](https://chrony-project.org/). Install it with your distribution's package manager: +We recommend [chrony](https://chrony-project.org). Install it with your distribution's package manager: ```bash # Ubuntu / Debian diff --git a/docs/validators/tier-1-orgs.mdx b/docs/validators/tier-1-orgs.mdx index 00c136c032..463b42416f 100644 --- a/docs/validators/tier-1-orgs.mdx +++ b/docs/validators/tier-1-orgs.mdx @@ -11,7 +11,7 @@ To become a Tier 1 organization, a team running validators must convince enough :::info[In short] -Run three geographically dispersed Full Validators, achieve sustained 99.9%+ uptime visible on [Obsrvr Radar](https://radar.withobsrvr.com/), complete [SEP-20](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) and [SEP-1](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) self-verification, and coordinate actively with the existing Tier 1 community. Joining is not a unilateral SDF decision — every existing Tier 1 organization independently decides whether to add you to their quorum set. Expect a process measured in months, not weeks. +Run three geographically dispersed Full Validators, achieve sustained 99.9%+ uptime visible on [Obsrvr Radar](https://radar.withobsrvr.com), complete [SEP-20](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) and [SEP-1](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) self-verification, and coordinate actively with the existing Tier 1 community. Joining is not a unilateral SDF decision — every existing Tier 1 organization independently decides whether to add you to their quorum set. Expect a process measured in months, not weeks. ::: @@ -127,7 +127,7 @@ Make your organization discoverable and verifiable: - [ ] Create funded Stellar accounts for each validator node - [ ] Set home domain on-chain for each ([SEP-20](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md)) - [ ] Publish a complete stellar.toml ([SEP-1](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md)) with organization info and all three `[[VALIDATORS]]` entries -- [ ] Verify your nodes appear correctly on [Obsrvr Radar](https://radar.withobsrvr.com/) +- [ ] Verify your nodes appear correctly on [Obsrvr Radar](https://radar.withobsrvr.com) ### Phase 4: Build Trust (Ongoing) @@ -168,7 +168,7 @@ The `#validator` channel on the [Stellar Dev Discord](https://discord.gg/stellar | --- | --- | | Stellar Dev Discord (`#validator`) — primary coordination channel for validator operators. Release announcements, upgrade coordination, incident response. | [discord.gg/stellardev](https://discord.gg/stellardev) | | stellar-core GitHub releases — official release notes | [github.com/stellar/stellar-core/releases](https://github.com/stellar/stellar-core/releases) | -| Obsrvr Radar — public validator uptime and quorum monitoring | [radar.withobsrvr.com](https://radar.withobsrvr.com/) | +| Obsrvr Radar — public validator uptime and quorum monitoring | [radar.withobsrvr.com](https://radar.withobsrvr.com) | | Admin Guide | [Admin Guide](./admin-guide/README.mdx) | | Example Mainnet Full Validator config | [stellar/packages on GitHub](https://github.com/stellar/packages/blob/master/docs/examples/pubnet-validator-full/stellar-core.cfg) | | SEP-20 (Self-Verification) | [stellar-protocol on GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) |