diff --git a/components/AskCookbook/AskCookbook.tsx b/components/AskCookbook/AskCookbook.tsx index 0ed11834..fca801a3 100644 --- a/components/AskCookbook/AskCookbook.tsx +++ b/components/AskCookbook/AskCookbook.tsx @@ -1,10 +1,14 @@ import React from "react"; import dynamic from "next/dynamic"; -const BaseAskCookbook = dynamic(() => import("@cookbookdev/docsbot/react"), { ssr: false }); -/** It's going to be exposed in HTTP requests anyway so it's fine to just hardcode it here */ +interface BaseAskCookbookProps { + apiKey: string; +} + +const BaseAskCookbook = dynamic(() => import("@cookbookdev/docsbot/react"), { ssr: false }); + const COOKBOOK_PUBLIC_API_KEY = "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiI2NjdlZmMxYjcyYzRmNTI5YzMxODUyZmUiLCJpYXQiOjE3MTk1OTgxMDcsImV4cCI6MjAzNTE3NDEwN30.etICfDHEcewxP9QTajrS4ggral2IgaxY_rWAlK4kNiQ"; export const AskCookbook = () => { - return ; + return ; }; diff --git a/pages/_app.mdx b/pages/_app.mdx index 0d9c9fa3..01cbdecb 100644 --- a/pages/_app.mdx +++ b/pages/_app.mdx @@ -6,15 +6,6 @@ import { ThemeProvider } from 'next-themes'; import { MantineWrapper, AskCookbook } from '../components'; export default function Nextra({ Component, pageProps }) { -<<<<<<< HEAD - return ( - - - - - - ); -======= return ( @@ -23,5 +14,4 @@ export default function Nextra({ Component, pageProps }) { ); ->>>>>>> main } diff --git a/pages/dev-advanced-concepts/_meta.json b/pages/dev-advanced-concepts/_meta.json deleted file mode 100644 index d7c94052..00000000 --- a/pages/dev-advanced-concepts/_meta.json +++ /dev/null @@ -1,12 +0,0 @@ -{ - "fee-grants": "Fee Grants", - "account-structure": "Account Structure", - "wallet-association": "Wallet Association", - "hardware-wallets": "Hardware Wallets", - "oracles": "Oracles", - "execute-multiple": "Execute Multiple Transactions", - "hd-path-coin-types": "HD Path & Coin Types", - "proposals": "Proposals", - "ibc-relayer": "IBC Relayer", - "differences-with-ethereum": "Differences from Ethereum" -} diff --git a/pages/dev-ecosystem-providers/oracles/_meta.json b/pages/dev-ecosystem-providers/oracles/_meta.json deleted file mode 100644 index 7bd7cf82..00000000 --- a/pages/dev-ecosystem-providers/oracles/_meta.json +++ /dev/null @@ -1,4 +0,0 @@ -{ - "oracles": "Overview", - "api3": "Api3" -} diff --git a/pages/dev-ecosystem-providers/oracles/api3.mdx b/pages/dev-ecosystem-providers/oracles/api3.mdx deleted file mode 100644 index 7941c6ed..00000000 --- a/pages/dev-ecosystem-providers/oracles/api3.mdx +++ /dev/null @@ -1,58 +0,0 @@ -![Logo](../../../public/assets/ecosystem/api3.png) - -API3 is a collaborative project delivers traditional API services to smart contract platforms in a decentralized and trust-minimized way. -Unlike traditional data feeds, accessing [API3 price feeds](https://market.api3.org/dapis) allows dApps to auction off the right to update the feeds to searcher bots, improving the efficiency of liquidation processes for users and LPs in DeFi money markets. The recaptured OEV is returned to the dApp. - -## Quick Start - -Head over to the [quickstart section](https://docs.api3.org/dapps/quickstart/) for an introduction how to get a price feed to your smart contract. Here is a [video option](https://www.youtube.com/watch?v=t4mcgxUpbwg) that you can go through in less than 10 minutes to get integrated. - -In just a few lines of code, you can get our price feeds integrated to your contract - -```javascript -// SPDX-License-Identifier: MIT -pragma solidity ^0.8.0; - -import "@openzeppelin/contracts/access/Ownable.sol"; -import "@api3/contracts/interfaces/IApi3ReaderProxy.sol"; - -contract DataFeedReaderExample is Ownable { - - address public proxy; - - constructor(address _proxy) { - setProxy(_proxy); - } - - function setProxy(address _proxy) public onlyOwner { - proxy = _proxy; - } - - function readDataFeed() external view returns (int224 value, uint256 timestamp) - { - (value, timestamp) = IApi3ReaderProxy(proxy).read(); - require(value > 0, "Value not positive"); - require( - timestamp + 1 days > block.timestamp, - "Timestamp older than one day" - ); - // After validation, you can implement your contract logic here. - - // Refer to https://docs.api3.org/dapps/integration/contract-integration.html - // for more information about how to integrate your contract securely. - } -} -``` - -### Migrating over but using a different oracle? - -API3 has an [adaptor contract](https://docs.api3.org/dapps/integration/aggregatorv2v3interface.html) that will allow you to use your existing repo with API3 price feeds data structure. - - -## Oracle Extractable Value -### Oracles that pay you - -Oracles play an important role in the health of a platform. When an oracle updates the data onchain, opportunities can present themselves to searchers. API3 allows anyone to bid in an auction for the right to update the oracle to the most exact current value. A majority of the bidding amount is returned to the platform to help recapture the loss in TVL. This feature is built into the oracle, there are no additional costs or code refactoring needed to use this feature. - - -To find out more details about OEV, please check [here](https://docs.api3.org/oev-searchers/) diff --git a/pages/dev-ecosystem-providers/oracles/oracles.mdx b/pages/dev-ecosystem-providers/oracles/oracles.mdx deleted file mode 100644 index 6229aa48..00000000 --- a/pages/dev-ecosystem-providers/oracles/oracles.mdx +++ /dev/null @@ -1,8 +0,0 @@ -import { AppCardsGridCategory } from "../../../components"; -import { Tag } from "../../../data/appData"; - -# Oracles - -Oracles provide external data to smart contracts, enabling more dynamic and responsive applications. Notable oracles for Sei include: - - diff --git a/pages/dev-token-standards.mdx b/pages/dev-token-standards.mdx deleted file mode 100644 index 19cde341..00000000 --- a/pages/dev-token-standards.mdx +++ /dev/null @@ -1,80 +0,0 @@ -import {Tabs, Blockquote, Title} from '@mantine/core'; - -# Token Standards - -In this section, we delve into the various token standards supported on Sei. Understanding these standards is crucial for developers as they form the foundation of many decentralized applications. - -Sei offers support for four main token types: -- [Sei Token](#sei-token) -- [Token Factory Tokens](#tokenfactory) -- [Smart Contract Tokens](#smart-contract-tokens) -- [IBC Tokens](#ibc-tokens) - -## **Sei Token** - -The Sei token is the native token of the Sei blockchain, serving multiple roles within the ecosystem. - -- **Fee Token**: Used to pay transaction fees on the Sei network. -- **Governance Token**: Used to participate in governance decisions affecting the network. - - -**EVM** - -`1sei = 10**18 wei = 1000000000000000000wei` - -`1sei = 10**9 wei = 1000000000gwei` (giga-wei) - -**Native** - -`1sei = 10**18 asei = 1000000000000000000asei` (atto-sei) - -`1sei = 10**9 nsei = 1000000000nsei` (nano-sei) - -`1sei = 10**6 usei = 1000000usei` (micro-sei) - -`1gwei = 1nsei` - -## **Fungible Tokens** - -Fungible tokens are digital assets that are interchangeable with one another and are not unique. Sei supports both ERC20 and CW20 fungible token standards, so developers have the option to create tokens using the native TokenFactory or via smart contract standards. - -### TokenFactory - -TokenFactory allows for the creation of tokens that are natively integrated into the base chain modules. This integration means bank balances are available through native bank queries, unlike CW20 or ERC20 tokens which require querying the smart contract directly. - -- **Native Integration**: Tokens created via TokenFactory are integrated into the chain allowing the core modules to efficiently interact with these tokens and RPC clients to return their balances in native bank and account queries. -- **Efficient Queries**: Tokens are available through native queries, making it more efficient than querying smart contracts directly. -- **Recommended Use**: Ideal for scenarios where performance and ease of access are priorities or for native applications. - -Learn more about creating tokens using TokenFactory in the [TokenFactory Tutorial](/dev-tutorials/tokenfactory-tutorial). - -### Smart Contract Tokens - -- **ERC20**: The ERC20 standard defines a common set of rules for fungible tokens on EVM-based blockchains. These tokens can be transferred, approved, and queried using standard functions. -- **CW20**: The CW20 standard is the wasm equivalent of ERC20, providing similar functionalities with much easier tracking and no need for external indexers. -- **Standard Compatibility**: Supporting both CW20 and ERC20 ensure compatibility with existing dApps and ecosystems while enabling onboarding of EVM-centric projects. -- **Interoperability**: Both standards support pointer contracts, enabling seamless interaction between native and EVM environments. -- **Interoperability and Pointer Contracts**: [Pointer contracts](/dev-tutorials/pointer-contracts) enable interoperability between ERC20 and CW20 tokens, allowing for seamless interaction between the two standards. A registry is kept to track pointer contracts and facilitate interoperability. -- **Recommended Use**: Suitable for applications needing standard token interactions for use with existing dApps and maximum compatibility. - - -
- Interoperability - Regardless of the choice, both TokenFactory and CW20/ERC20 tokens can have pointer contracts deployed, facilitating seamless cross-vm interoperability. - - For more detailed guidance, refer to the [Pointer Contracts Documentation](/dev-tutorials/pointer-contracts). -
- -## **NFTs** - -Non-fungible tokens (NFTs) represent unique digital assets. Sei supports both ERC721 and CW721 standards as well as their counterparts with royalties (2981). - -- **ERC721**: The ERC721 standard defines the structure for non-fungible tokens on EVM-based blockchains. Each token is unique and cannot be exchanged on a one-to-one basis like fungible tokens. -- **CW721**: The CW721 standard is the wasm equivalent of ERC721, providing similar functionalities with the added benefit of not requiring complicated indexing techniques and platforms to track them. -- **CW2981 & ERC2981**: These standards define royalty mechanisms for NFTs, ensuring creators receive a percentage of sales. -- **Interoperability**: Similar to fungible tokens, NFTs can interact across different standards using pointer contracts. -- **Pointer Contract Registry**: A registry for tracking pointer contracts specific to NFTs. - -## **IBC Tokens** - -Inter-Blockchain Communication (IBC) is a trustless permissionless interchain messaging protocol that enables communication between many different chains. IBC tokens are tokens bridged from one chain to another using the IBC protocol. Channels are set up to establish communication between the chains. Each channel has a unique identifier and specific configurations. View the [IBC Channel](https://github.com/sei-protocol/chain-registry/blob/main/ibc_info.json) section of the Sei chain registry for channel information. diff --git a/pages/reference/providers/indexers/goldrush.mdx b/pages/reference/providers/indexers/goldrush.mdx index 58c115fa..a8e664fd 100644 --- a/pages/reference/providers/indexers/goldrush.mdx +++ b/pages/reference/providers/indexers/goldrush.mdx @@ -1,6 +1,6 @@ -import {ImageWithCaption} from '../../../components'; +import {ImageWithCaption} from '../../../../components'; -import imgWalletUiComponent from "../../../public/assets/ecosystem/resources/goldrush/wallet_ui_component.png"; +import imgWalletUiComponent from "../../../../public/assets/ecosystem/resources/goldrush/wallet_ui_component.png"; # GoldRush - powered by Covalent diff --git a/pages/reference/providers/wallets.mdx b/pages/reference/providers/wallets.mdx index 02d92e60..15ecbd29 100644 --- a/pages/reference/providers/wallets.mdx +++ b/pages/reference/providers/wallets.mdx @@ -1,10 +1,5 @@ -<<<<<<< HEAD:pages/reference/providers/wallets.mdx -import { EcosystemDynamicSection } from "../../../components"; -import { AppCardsGridCategory } from "../../../components"; -======= -import { EcosystemDynamicSection } from '../../components'; -import { AppCardsGridCategory } from '../../components'; ->>>>>>> main:pages/dev-ecosystem-providers/wallets.mdx +import { EcosystemDynamicSection } from '../../../components'; +import { AppCardsGridCategory } from '../../../components'; Wallets are essential for managing assets and interacting with the Sei blockchain. There are various types of wallets available, each offering different features and levels of security.