Change keyspace repository location to base-org/keyspace

base · Dec 3, 2024 · d32a0ce · d32a0ce
1 parent 349aad0
commit d32a0ce
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/pages/index.mdx b/docs/pages/index.mdx
@@ -13,7 +13,7 @@ Keyspace is built by the Base team as open, neutral infrastructure for all chain
 
 <iframe width="560" height="315" src="https://www.youtube.com/embed/DibVD2gCyp8?si=OCBQbDiFRBuZaxs2" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
-* [Keyspace on GitHub](https://github.com/xenoliss/keyspace-v3)
+* [Keyspace on GitHub](https://github.com/base-org/keyspace)
 * [Coinbase Smart Wallet](https://www.smartwallet.dev/) Keyspace integration
   * [JavaScript Client](https://github.com/base-org/keyspace-client)
   * [Smart Contracts](https://github.com/coinbase/smart-wallet/tree/baptiste/keyspace/src)
diff --git a/docs/pages/keystore-basics.mdx b/docs/pages/keystore-basics.mdx
@@ -78,7 +78,7 @@ When an implementation upgrade has occurred, `hookIsNewConfigValid` is called vi
 
 Inheriting from the `Keystore` contract will require your wallet to implement `_eventualConsistencyWindow()`, which should return the maximum duration that can elapse on a replica chain before the wallet's configuration expires. This value is used by `_enforceEventualConsistency()`, which reverts on replica chains if the configuration has expired. Each of your wallet's methods that are designed to be called by the `EntryPoint` should call `_enforceEventualConsistency()` to ensure that the configuration has not expired.
 
-The `MultiOwnableWallet` example in the [Keyspace GitHub repository](https://github.com/xenoliss/keyspace-v3) shows how this can be done. It makes exceptions for `confirmConfig()` and `setConfig()` to be called even if the wallet hasn't been synced recently.
+The `MultiOwnableWallet` example in the [Keyspace GitHub repository](https://github.com/base-org/keyspace) shows how this can be done. It makes exceptions for `confirmConfig()` and `setConfig()` to be called even if the wallet hasn't been synced recently.
 
 Exempting `confirmConfig` from eventual consistency allows the wallet to sync itself instead of relying on an external account to call `confirmConfig()`.