diff --git a/docs/pages/index.mdx b/docs/pages/index.mdx index ea096a2..5846d31 100644 --- 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 -* [Keyspace on GitHub](https://github.com/base-org/keyspace) +* [Keyspace on GitHub](https://github.com/base/keyspace) * [Coinbase Smart Wallet](https://www.smartwallet.dev/) Keyspace integration - * [JavaScript Client](https://github.com/base-org/keyspace-client) + * [JavaScript Client](https://github.com/base/keyspace-client) * [Smart Contracts](https://github.com/niran/smart-wallet/tree/keyspace) diff --git a/docs/pages/keystore-basics.mdx b/docs/pages/keystore-basics.mdx index 8d84406..471c403 100644 --- 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/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. +The `MultiOwnableWallet` example in the [Keyspace GitHub repository](https://github.com/base/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 `setConfig` from eventual consistency allows the wallet to replay configuration changes to get to the latest version of the configuration without relying on a sync. Cross-chain syncing can break with each L1 and L2 hard fork, so it's important that your wallet can handle this case. diff --git a/docs/pages/releases.mdx b/docs/pages/releases.mdx index 7390998..5c46438 100644 --- a/docs/pages/releases.mdx +++ b/docs/pages/releases.mdx @@ -14,7 +14,7 @@ Keyspace v0.1.0 is the first smart contract-based implementation of Keyspace. Th *June 18, 2024* -The Dedicated Rollup Beta (v0.0.2) release of Keyspace introduces [`keyspace-client`](https://github.com/base-org/keyspace-client/tree/v0.0.2), an example TypeScript client for Keyspace with an integrated smart wallet, and [`keyspace-recovery-service`](https://github.com/base-org/keyspace-recovery-service/tree/v0.0.2), an RPC service for generating SNARK proofs of the signatures users sign to change their keys. The supported chains have been expanded from Base Sepolia and Optimism Sepolia to include Arbitrum Sepolia, Gnosis Chiado, Polygon Amoy, BSC Testnet, and Avalanche Fuji. +The Dedicated Rollup Beta (v0.0.2) release of Keyspace introduces [`keyspace-client`](https://github.com/base/keyspace-client/tree/v0.0.2), an example TypeScript client for Keyspace with an integrated smart wallet, and [`keyspace-recovery-service`](https://github.com/base/keyspace-recovery-service/tree/v0.0.2), an RPC service for generating SNARK proofs of the signatures users sign to change their keys. The supported chains have been expanded from Base Sepolia and Optimism Sepolia to include Arbitrum Sepolia, Gnosis Chiado, Polygon Amoy, BSC Testnet, and Avalanche Fuji. ## Dedicated Rollup Alpha (v0.0.1) diff --git a/vocs.config.ts b/vocs.config.ts index 54d9bba..8ada06c 100644 --- a/vocs.config.ts +++ b/vocs.config.ts @@ -6,7 +6,7 @@ export default defineConfig({ topNav: [ { text: 'Github', - link: 'https://github.com/base-org/keyspace-client', + link: 'https://github.com/base/keyspace-client', }, ], sidebar: [