├── .prettierignore ├── public └── assets │ ├── trfs │ └── trf-4 │ │ ├── test │ │ └── test.png │ ├── irs │ ├── IR-8-2.png │ ├── IR-8-3.png │ └── IR-8-4.png │ ├── xips │ ├── xip-17 │ │ └── image.png │ ├── xip-47 │ │ └── image.png │ ├── xip-52 │ │ └── pxeth.jpg │ ├── xip-8 │ │ └── XIP Proxy.png │ ├── xip-3-perps │ │ ├── xip-3-1.png │ │ ├── xip-3-2.png │ │ └── xip-3-4.png │ ├── xip-75 │ │ └── smartcontract.png │ ├── xip-9 │ │ └── architecture.jpg │ ├── xip-2-security-core │ │ ├── xip-2-1.png │ │ ├── xip-2-2.png │ │ ├── xip-2-3.png │ │ ├── xip-2-4.png │ │ ├── xip-2-5.png │ │ ├── xip-2-6.png │ │ └── xip-2-7.png │ ├── Stytch_and_Lit_Auxiliary_file.pdf │ ├── xip-6 │ │ ├── circle-bridge-deposit-flow.png │ │ └── circle-bridge-withdrawal-flow.png │ ├── Browser_Key_Storage_Auxiliary_File.pdf │ ├── Offchain_Security_Model_Auxiliary.pdf │ └── xip-33 │ │ └── hero-distribution-proposal@2x.png │ └── icons │ ├── mobile-menu.svg │ └── close.svg ├── .github └── CODEOWNERS ├── .eslintrc.json ├── src ├── app │ ├── globals.css │ ├── favicon.ico │ ├── keystatic │ │ ├── [[...params]] │ │ │ └── page.tsx │ │ ├── layout.tsx │ │ └── keystatic.tsx │ ├── api │ │ └── keystatic │ │ │ └── [...params] │ │ │ └── route.ts │ ├── layout.tsx │ ├── irs │ │ ├── [slug] │ │ │ └── page.tsx │ │ └── page.tsx │ ├── tas │ │ ├── [slug] │ │ │ └── page.tsx │ │ └── page.tsx │ ├── rcs │ │ ├── [slug] │ │ │ └── page.tsx │ │ └── page.tsx │ ├── wgcs │ │ ├── [slug] │ │ │ └── page.tsx │ │ └── page.tsx │ ├── xips │ │ └── [slug] │ │ │ └── page.tsx │ └── page.tsx ├── lib │ ├── config.ts │ ├── reader.ts │ └── util.ts └── components │ ├── Logo.tsx │ ├── UI.tsx │ └── Entries.tsx ├── .vscode ├── extensions.json └── settings.json ├── .prettierrc ├── postcss.config.js ├── next.config.js ├── styles └── typography │ ├── index.ts │ └── addTypographyClassesPlugin.ts ├── content ├── rcs │ ├── rc-29.mdoc │ ├── rc-44.mdoc │ ├── rc-18.mdoc │ ├── rc-23.mdoc │ ├── rc-37.mdoc │ ├── rc-20.mdoc │ ├── rc-42.mdoc │ ├── rc-31.mdoc │ ├── rc-16.mdoc │ ├── rc-32.mdoc │ ├── rc-27.mdoc │ ├── rc-30.mdoc │ ├── rc-39.mdoc │ ├── rc-28.mdoc │ ├── rc-13.mdoc │ ├── rc-34.mdoc │ ├── rc-25.mdoc │ ├── rc-26.mdoc │ ├── rc-19.mdoc │ ├── rc-22.mdoc │ ├── rc-36.mdoc │ ├── rc-24.mdoc │ ├── rc-41.mdoc │ ├── rc-43.mdoc │ ├── rc-21.mdoc │ ├── rc-15.mdoc │ ├── rc-14.mdoc │ ├── rc-33.mdoc │ ├── rc-35.mdoc │ ├── rc-12.mdoc │ ├── rc-40.mdoc │ ├── rc-11.mdoc │ ├── rc-7.mdoc │ ├── rc-10.mdoc │ ├── rc-3.mdoc │ ├── rc-38.mdoc │ ├── rc-17.mdoc │ ├── rc-6.mdoc │ ├── rc-9.mdoc │ ├── rc-8.mdoc │ ├── rc-5.mdoc │ └── rc-2.mdoc ├── tas │ ├── ta-7.mdoc │ ├── ta-5.mdoc │ ├── ta-6.mdoc │ ├── ta-4.mdoc │ ├── ta-2.mdoc │ └── ta-3.mdoc ├── xips │ ├── xip-72.mdoc │ ├── xip-81.mdoc │ ├── xip-80.mdoc │ ├── xip-32.mdoc │ ├── xip-100.mdoc │ ├── xip-102.mdoc │ ├── xip-56.mdoc │ ├── xip-87.mdoc │ ├── xip-59.mdoc │ ├── xip-30.mdoc │ ├── xip-96.mdoc │ ├── xip-82.mdoc │ ├── xip-101.mdoc │ ├── xip-65.mdoc │ ├── xip-38.mdoc │ ├── xip-78.mdoc │ ├── xip-97.mdoc │ ├── xip-90.mdoc │ ├── xip-68.mdoc │ ├── xip-58.mdoc │ ├── xip-66.mdoc │ ├── xip-79.mdoc │ ├── xip-57.mdoc │ ├── xip-29.mdoc │ ├── xip-11.mdoc │ ├── xip-89.mdoc │ ├── xip-70.mdoc │ ├── xip-92.mdoc │ ├── xip-63.mdoc │ ├── xip-52.mdoc │ ├── xip-24.mdoc │ ├── xip-86.mdoc │ ├── xip-95.mdoc │ ├── xip-48.mdoc │ ├── xip-49.mdoc │ ├── xip-64.mdoc │ ├── xip-50.mdoc │ ├── xip-77.mdoc │ ├── xip-19.mdoc │ ├── xip-31.mdoc │ ├── xip-36.mdoc │ ├── xip-17.mdoc │ ├── xip-35.mdoc │ ├── xip-69.mdoc │ ├── xip-55.mdoc │ ├── xip-27.mdoc │ ├── xip-61.mdoc │ ├── xip-45.mdoc │ ├── xip-71.mdoc │ ├── xip-54.mdoc │ ├── xip-42.mdoc │ └── xip-12.mdoc ├── wgcs │ ├── wgc-5.mdoc │ └── wgc-6.mdoc └── irs │ └── ir-7.mdoc ├── .gitignore ├── tsconfig.json ├── package.json ├── LICENSE ├── templates ├── ir-template.mdoc └── xip-template.mdoc └── tailwind.config.ts /.prettierignore: -------------------------------------------------------------------------------- 1 | *.mdoc 2 | -------------------------------------------------------------------------------- /public/assets/trfs/trf-4/test: -------------------------------------------------------------------------------- 1 | s 2 | -------------------------------------------------------------------------------- /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | content/ @infinex-io/xip-editors -------------------------------------------------------------------------------- /.eslintrc.json: -------------------------------------------------------------------------------- 1 | { 2 | "extends": "next/core-web-vitals" 3 | } 4 | -------------------------------------------------------------------------------- /src/app/globals.css: -------------------------------------------------------------------------------- 1 | @tailwind base; 2 | @tailwind components; 3 | @tailwind utilities; 4 | -------------------------------------------------------------------------------- /src/app/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/src/app/favicon.ico -------------------------------------------------------------------------------- /src/app/keystatic/[[...params]]/page.tsx: -------------------------------------------------------------------------------- 1 | export default function Page() { 2 | return null; 3 | } 4 | -------------------------------------------------------------------------------- /.vscode/extensions.json: -------------------------------------------------------------------------------- 1 | { 2 | "recommendations": ["dbaeumer.vscode-eslint", "esbenp.prettier-vscode"] 3 | } 4 | -------------------------------------------------------------------------------- /public/assets/irs/IR-8-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/irs/IR-8-2.png -------------------------------------------------------------------------------- /public/assets/irs/IR-8-3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/irs/IR-8-3.png -------------------------------------------------------------------------------- /public/assets/irs/IR-8-4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/irs/IR-8-4.png -------------------------------------------------------------------------------- /.prettierrc: -------------------------------------------------------------------------------- 1 | { 2 | "semi": true, 3 | "singleQuote": true, 4 | "plugins": ["prettier-plugin-tailwindcss"] 5 | } 6 | -------------------------------------------------------------------------------- /postcss.config.js: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | plugins: { 3 | tailwindcss: {}, 4 | autoprefixer: {}, 5 | }, 6 | } 7 | -------------------------------------------------------------------------------- /public/assets/trfs/trf-4/test.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/trfs/trf-4/test.png -------------------------------------------------------------------------------- /next.config.js: -------------------------------------------------------------------------------- 1 | /** @type {import('next').NextConfig} */ 2 | const nextConfig = {}; 3 | 4 | module.exports = nextConfig; 5 | -------------------------------------------------------------------------------- /public/assets/xips/xip-17/image.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-17/image.png -------------------------------------------------------------------------------- /public/assets/xips/xip-47/image.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-47/image.png -------------------------------------------------------------------------------- /public/assets/xips/xip-52/pxeth.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-52/pxeth.jpg -------------------------------------------------------------------------------- /public/assets/xips/xip-8/XIP Proxy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-8/XIP Proxy.png -------------------------------------------------------------------------------- /public/assets/xips/xip-3-perps/xip-3-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-3-perps/xip-3-1.png -------------------------------------------------------------------------------- /public/assets/xips/xip-3-perps/xip-3-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-3-perps/xip-3-2.png -------------------------------------------------------------------------------- /public/assets/xips/xip-3-perps/xip-3-4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-3-perps/xip-3-4.png -------------------------------------------------------------------------------- /public/assets/xips/xip-75/smartcontract.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-75/smartcontract.png -------------------------------------------------------------------------------- /public/assets/xips/xip-9/architecture.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-9/architecture.jpg -------------------------------------------------------------------------------- /public/assets/xips/xip-2-security-core/xip-2-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-2-security-core/xip-2-1.png -------------------------------------------------------------------------------- /public/assets/xips/xip-2-security-core/xip-2-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-2-security-core/xip-2-2.png -------------------------------------------------------------------------------- /public/assets/xips/xip-2-security-core/xip-2-3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-2-security-core/xip-2-3.png -------------------------------------------------------------------------------- /public/assets/xips/xip-2-security-core/xip-2-4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-2-security-core/xip-2-4.png -------------------------------------------------------------------------------- /public/assets/xips/xip-2-security-core/xip-2-5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-2-security-core/xip-2-5.png -------------------------------------------------------------------------------- /public/assets/xips/xip-2-security-core/xip-2-6.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-2-security-core/xip-2-6.png -------------------------------------------------------------------------------- /public/assets/xips/xip-2-security-core/xip-2-7.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-2-security-core/xip-2-7.png -------------------------------------------------------------------------------- /src/app/keystatic/layout.tsx: -------------------------------------------------------------------------------- 1 | import KeystaticApp from './keystatic'; 2 | 3 | export default function RootLayout() { 4 | return ; 5 | } 6 | -------------------------------------------------------------------------------- /public/assets/xips/Stytch_and_Lit_Auxiliary_file.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/Stytch_and_Lit_Auxiliary_file.pdf -------------------------------------------------------------------------------- /public/assets/xips/xip-6/circle-bridge-deposit-flow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-6/circle-bridge-deposit-flow.png -------------------------------------------------------------------------------- /public/assets/xips/Browser_Key_Storage_Auxiliary_File.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/Browser_Key_Storage_Auxiliary_File.pdf -------------------------------------------------------------------------------- /public/assets/xips/Offchain_Security_Model_Auxiliary.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/Offchain_Security_Model_Auxiliary.pdf -------------------------------------------------------------------------------- /public/assets/xips/xip-6/circle-bridge-withdrawal-flow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-6/circle-bridge-withdrawal-flow.png -------------------------------------------------------------------------------- /styles/typography/index.ts: -------------------------------------------------------------------------------- 1 | export { addTypographyClassesPlugin } from './addTypographyClassesPlugin'; 2 | export { typography, extendedFontSizes } from './typography'; 3 | -------------------------------------------------------------------------------- /public/assets/xips/xip-33/hero-distribution-proposal@2x.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/infinex-xyz/proposals/HEAD/public/assets/xips/xip-33/hero-distribution-proposal@2x.png -------------------------------------------------------------------------------- /src/lib/config.ts: -------------------------------------------------------------------------------- 1 | export const project = 'infinex/proposals'; 2 | export const isProduction = process.env.NODE_ENV === 'production'; 3 | export const shouldUseCloudStorage = isProduction; 4 | -------------------------------------------------------------------------------- /src/app/keystatic/keystatic.tsx: -------------------------------------------------------------------------------- 1 | 'use client'; 2 | 3 | import { makePage } from '@keystatic/next/ui/app'; 4 | import config from '../../../keystatic.config'; 5 | 6 | export default makePage(config); 7 | -------------------------------------------------------------------------------- /src/lib/reader.ts: -------------------------------------------------------------------------------- 1 | import { createReader } from '@keystatic/core/reader'; 2 | import keystaticConfig from '../../keystatic.config'; 3 | 4 | export const reader = createReader(process.cwd(), keystaticConfig); 5 | -------------------------------------------------------------------------------- /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "editor.codeActionsOnSave": { 3 | "source.fixAll": "explicit" 4 | }, 5 | "editor.defaultFormatter": "esbenp.prettier-vscode", 6 | "editor.formatOnSave": true, 7 | "typescript.tsdk": "node_modules/typescript/lib" 8 | } 9 | -------------------------------------------------------------------------------- /src/app/api/keystatic/[...params]/route.ts: -------------------------------------------------------------------------------- 1 | import { makeRouteHandler } from '@keystatic/next/route-handler'; 2 | import keystaticConfig from '@/../keystatic.config'; 3 | 4 | export const { POST, GET } = makeRouteHandler({ 5 | config: keystaticConfig, 6 | }); 7 | -------------------------------------------------------------------------------- /public/assets/icons/mobile-menu.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | -------------------------------------------------------------------------------- /public/assets/icons/close.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | -------------------------------------------------------------------------------- /content/rcs/rc-29.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Add Eigen Token 3 | id: 29 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-10-08' 8 | updated: '2024-10-16' 9 | implemented: '2024-10-09' 10 | --- 11 | # **Outcome** 12 | 13 | Adds the Eigen token 14 | 15 | # **Overview** 16 | 17 | This release adds the Eigen token, based off [XIP-81](https://proposals.infinex.xyz/xips/xip-81). 18 | 19 | # **Copyright** 20 | 21 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 22 | -------------------------------------------------------------------------------- /content/rcs/rc-44.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Deploy on BSC 3 | id: 44 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Draft 7 | created: '2025-03-03' 8 | --- 9 | # **Outcome** 10 | 11 | Deploy onto Binance Smart Chain. 12 | 13 | # **Overview** 14 | 15 | Infinex will implement [XIP-100](https://proposals.infinex.xyz/xips/xip-100), which means deploying onto BSC with Swidging to and from the chain, wallets and vaults. 16 | 17 | # **Copyright** 18 | 19 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 20 | -------------------------------------------------------------------------------- /content/rcs/rc-18.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Implement XIP-66 3 | id: 18 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-08-07' 8 | updated: '2024-08-14' 9 | implemented: '2024-08-14' 10 | --- 11 | # **Outcome** 12 | 13 | Implement [XIP-66](https://proposals.infinex.xyz/xips/xip-66). 14 | # **Overview** 15 | 16 | This release enables the support for depositing and withdrawing JUPSOL and INF. 17 | 18 | # **Copyright** 19 | 20 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 21 | -------------------------------------------------------------------------------- /content/rcs/rc-23.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: End Ethena Sats Campaign 3 | id: 23 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-09-03' 8 | updated: '2024-09-09' 9 | implemented: '2024-09-06' 10 | --- 11 | # **Outcome** 12 | 13 | Close the Ethena Sats campaign. 14 | 15 | # **Overview** 16 | 17 | This releases includes the end of the Ethena Sats campaign, and fixes reporting bridge errors for Solana-EVM bridges. 18 | 19 | # **Copyright** 20 | 21 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 22 | -------------------------------------------------------------------------------- /content/rcs/rc-37.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Scheduled Off-time 3 | id: 37 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-12-09' 8 | implemented: '2024-12-10' 9 | updated: '2025-01-09' 10 | --- 11 | # **Outcome** 12 | 13 | Schedule down-time to implement platform updates. 14 | 15 | # **Overview** 16 | 17 | Infinex will undergo up to 2 hours of down-time tomorrow to implement Send v2 and the new V4 accounts 18 | 19 | # **Copyright** 20 | 21 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 22 | -------------------------------------------------------------------------------- /content/rcs/rc-20.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Implement XIP-68 & 69 3 | id: 20 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-08-21' 8 | updated: '2024-08-22' 9 | implemented: '2024-08-27' 10 | --- 11 | # **Outcome** 12 | 13 | Implement [XIP-68](https://proposals.infinex.xyz/xips/xip-68) & [69](https://proposals.infinex.xyz/xips/xip-69). 14 | 15 | # **Overview** 16 | 17 | This release implements both XIP-68 & 69. 18 | 19 | # **Copyright** 20 | 21 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 22 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # See https://help.github.com/articles/ignoring-files/ for more about ignoring files. 2 | 3 | # dependencies 4 | /node_modules 5 | /.pnp 6 | .pnp.js 7 | .yarn/install-state.gz 8 | 9 | # testing 10 | /coverage 11 | 12 | # next.js 13 | /.next/ 14 | /out/ 15 | 16 | # production 17 | /build 18 | 19 | # misc 20 | .DS_Store 21 | *.pem 22 | 23 | # debug 24 | npm-debug.log* 25 | yarn-debug.log* 26 | yarn-error.log* 27 | 28 | # local env files 29 | .env*.local 30 | 31 | # vercel 32 | .vercel 33 | 34 | # typescript 35 | *.tsbuildinfo 36 | next-env.d.ts 37 | 38 | # local .env 39 | .env 40 | -------------------------------------------------------------------------------- /content/rcs/rc-42.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Deploy on Berachain 3 | id: 42 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2025-01-13' 8 | updated: '2025-02-13' 9 | implemented: '2025-02-08' 10 | --- 11 | # **Outcome** 12 | 13 | Deploy onto Berachain. 14 | 15 | # **Overview** 16 | 17 | Infinex will implement [XIP-97](https://proposals.infinex.xyz/xips/xip-97), which means deploying onto Berachain with Swidging to and from the chain, wallets and vaults. 18 | 19 | # **Copyright** 20 | 21 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 22 | -------------------------------------------------------------------------------- /src/app/layout.tsx: -------------------------------------------------------------------------------- 1 | import type { Metadata } from 'next'; 2 | import { Inter } from 'next/font/google'; 3 | import './globals.css'; 4 | 5 | const inter = Inter({ subsets: ['latin'] }); 6 | 7 | export const metadata: Metadata = { 8 | title: 'Infinex Proposals', 9 | description: 'Infinex Governance Proposals (XIPs, IRs, WGCs, RCs)', 10 | }; 11 | 12 | export default function RootLayout({ 13 | children, 14 | }: { 15 | children: React.ReactNode; 16 | }) { 17 | return ( 18 | 19 | 20 | {children} 21 | 22 | 23 | ); 24 | } 25 | -------------------------------------------------------------------------------- /content/rcs/rc-31.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Patron NFT Distribution 3 | id: 31 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-10-14' 8 | updated: '2024-10-28' 9 | implemented: '2024-10-28' 10 | --- 11 | # **Outcome** 12 | 13 | Mints Patron NFTs on-chain to your Infinex Account. 14 | 15 | # **Overview** 16 | 17 | Changes include: 18 | 19 | - Patron NFTs are minted to users accounts on-chain 20 | - GP Redemption is turned off 21 | - Add claim functionality UI for vested Patrons to the App 22 | 23 | # **Copyright** 24 | 25 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 26 | -------------------------------------------------------------------------------- /content/rcs/rc-16.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: End Craterun 3 | id: 16 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-07-29' 8 | implemented: '2024-07-30' 9 | --- 10 | # **Outcome** 11 | 12 | End the Craterun Campaign 13 | 14 | # **Overview** 15 | 16 | This release aims to end the Craterun Campaign. Changes include: 17 | 18 | - Update public and in-app pages to reflect the end of the Craterun campaign 19 | - Display user-specific Craterun stats in-app 20 | - Implement a "bad luck" badge for users 21 | 22 | # **Copyright** 23 | 24 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 25 | -------------------------------------------------------------------------------- /content/rcs/rc-32.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Add SPX6900 & $BITCOIN 3 | id: 32 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-10-29' 8 | updated: '2024-11-10' 9 | implemented: '2024-11-18' 10 | --- 11 | # **Outcome** 12 | 13 | Add SPX6900 & HarryPotterObamaSonic10Inu. 14 | 15 | # **Overview** 16 | 17 | This release implements the assets associated with [XIP-82](https://proposals.infinex.xyz/xips/xip-82) & [87](https://proposals.infinex.xyz/xips/xip-87). Furthermore, it also adds support for ENA on other chains. 18 | 19 | # **Copyright** 20 | 21 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 22 | -------------------------------------------------------------------------------- /content/rcs/rc-27.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Launch GP Migration Tool 3 | id: 27 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-09-18' 8 | updated: '2024-10-16' 9 | implemented: '2024-10-14' 10 | --- 11 | # **Outcome** 12 | 13 | Start the GP migration process. 14 | 15 | # **Overview** 16 | 17 | Changes include: 18 | 19 | - Upgrading GP to an ERC-20 asset. 20 | - Enabling GP to be withdraw-able, deposit-able and transferrable. 21 | - Migrating all sources of GP into the Infinex Platform, via the launch of the GP Migration Tool 22 | 23 | # **Copyright** 24 | 25 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 26 | -------------------------------------------------------------------------------- /content/rcs/rc-30.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: GP & Patron Sale Updates 3 | id: 30 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-10-16' 8 | updated: '2024-10-29' 9 | implemented: '2024-10-24' 10 | --- 11 | # **Outcome** 12 | 13 | Update GP and Patron NFTs. 14 | 15 | # **Overview** 16 | 17 | Changes include: 18 | 19 | - Allowing earned/farmed GP to be associated with an Infinex Account. 20 | - Allowing the redemption of GP into Patron NFTs. 21 | - Enabling the transfer, deposit and withdraw of GP. 22 | - Additional UI updates for Bullrun 23 | 24 | # **Copyright** 25 | 26 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 27 | -------------------------------------------------------------------------------- /content/rcs/rc-39.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Release Swaps for MegaPatrons 3 | id: 39 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2025-01-09' 8 | updated: '2024-01-17' 9 | implemented: '2025-01-10' 10 | --- 11 | # **Outcome** 12 | 13 | Release [Swaps](https://proposals.infinex.xyz/xips/xip-93) to Mega Patrons 14 | 15 | # **Overview** 16 | 17 | This RC proposes [XIP-93: Infinex v2.0](https://proposals.infinex.xyz/xips/xip-93) to be released to Mega Patrons (Users who hold >= 20 Patrons in their Infinex account). There are ~200 Mega Patrons currently. 18 | 19 | # **Copyright** 20 | 21 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 22 | -------------------------------------------------------------------------------- /tsconfig.json: -------------------------------------------------------------------------------- 1 | { 2 | "compilerOptions": { 3 | "target": "es2015", 4 | "lib": ["dom", "dom.iterable", "esnext"], 5 | "allowJs": true, 6 | "skipLibCheck": true, 7 | "strict": true, 8 | "noEmit": true, 9 | "esModuleInterop": true, 10 | "module": "esnext", 11 | "moduleResolution": "bundler", 12 | "resolveJsonModule": true, 13 | "isolatedModules": true, 14 | "jsx": "preserve", 15 | "incremental": true, 16 | "plugins": [ 17 | { 18 | "name": "next" 19 | } 20 | ], 21 | "paths": { 22 | "@/*": ["./src/*"] 23 | } 24 | }, 25 | "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"], 26 | "exclude": ["node_modules"] 27 | } 28 | -------------------------------------------------------------------------------- /content/rcs/rc-28.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Patron Sale Updates 3 | id: 28 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-09-20' 8 | updated: '2024-09-24' 9 | implemented: '2024-09-21' 10 | --- 11 | # **Outcome** 12 | 13 | Opens Wave 3 and 4 for the Patron Sale 14 | 15 | # **Overview** 16 | 17 | This release includes various updates to the Patron Sale. Changes include: 18 | 19 | - Wave 3 will begin on Sunday 00:00 UTC, and end Mon 23:59 UTC. 20 | - Wave 4 will begin on Tuesday 00:00 UTC, and end Tuesday 23:59 UTC. 21 | - The ability to gift Patron Passes will be implemented. 22 | 23 | # **Copyright** 24 | 25 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 26 | -------------------------------------------------------------------------------- /content/rcs/rc-13.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Add Support For More Assets 3 | id: 13 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-07-06' 8 | implemented: '2024-07-07' 9 | --- 10 | # Overview 11 | 12 | This release adds support for Pirex Staked ETH, Pirex apxETH, BlazeStake Staked SOL and the Pyth Network tokens. 13 | 14 | # Outcome 15 | 16 | Upgrade the platform to enable the deposit and withdraw of PXETH, APXETH, BSOL & PYTH, as per [XIP-52](https://proposals.infinex.xyz/xips/xip-52), [55](https://proposals.infinex.xyz/xips/xip-55), and [57](https://proposals.infinex.xyz/xips/xip-57). 17 | 18 | # Copyright 19 | 20 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 21 | -------------------------------------------------------------------------------- /content/rcs/rc-34.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: GP Redemption & Burn 3 | id: 34 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-11-06' 8 | updated: '2024-11-18' 9 | implemented: '2024-11-07' 10 | --- 11 | # **Outcome** 12 | 13 | Re-enable the redemption of GP, and burn used or erroneous GP. 14 | 15 | # **Overview** 16 | 17 | RC-31 paused GP redemption for Patron NFTs as Patron NFTs were initially distributed to users. This change is to: 18 | 19 | - Re-enable redemption of GP for Patron NFTs. 20 | - Burn any GP associated with a Patron NFT redemption. 21 | - Burn any GP associated with erroneous GP claims or Infinex Account associations. 22 | 23 | # **Copyright** 24 | 25 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 26 | -------------------------------------------------------------------------------- /content/rcs/rc-25.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Launch Bullrun & Patron Sale 3 | id: 25 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-09-13' 8 | updated: '2024-09-18' 9 | implemented: '2024-09-16' 10 | --- 11 | # **Outcome** 12 | 13 | Launch Bullrun into Alpha, and enable early access for the Patron Sale. 14 | 15 | # **Overview** 16 | 17 | This release includes various changes to the Infinex platform. Changes include: 18 | 19 | - A closed alpha version of Bullrun will soon be released. Users were privately invited from the CWG. 20 | - The in-app Patron Sale will be enabled for everyone. Only users that are in Wave 1 or 2 will be able to buy a Patron. 21 | 22 | # **Copyright** 23 | 24 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 25 | -------------------------------------------------------------------------------- /content/rcs/rc-26.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Patron Sale and Bullrun Updates 3 | id: 26 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-09-16' 8 | updated: '2024-09-18' 9 | implemented: '2024-09-16' 10 | --- 11 | # **Outcome** 12 | 13 | Add additional functionality to the Patron Sale, and Launch Bullrun 14 | 15 | # **Overview** 16 | 17 | This release includes various changes to the Infinex platform. Changes include: 18 | 19 | - Adding functionality for users to transfer Patron Passes 20 | - Adds functionality that allows an Infinex user to connect their X account and, if eligible, accept their invite to Patron Sale Early Access 21 | - Open the closed alpha version of Bullrun to all users. 22 | 23 | # **Copyright** 24 | 25 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 26 | -------------------------------------------------------------------------------- /content/rcs/rc-19.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: USDC bridging rollout 3 | id: 19 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-08-20' 8 | updated: '2024-08-22' 9 | implemented: '2024-08-27' 10 | --- 11 | # **Outcome** 12 | 13 | Turn on USDC bridging for all users, upgrade the activity log and prepare for V3 upgrades. 14 | 15 | # **Overview** 16 | 17 | This release includes various changes to the Infinex platform. Changes include: 18 | 19 | - Turn on USDC bridging for all users 20 | - A unified activity log (withdrawals, swaps, bridging) 21 | - Preparation for V3 upgrades (frontend & backend work) 22 | - Removal of craterun code paths 23 | - Frontend refactor (for bridges) to use API-oriented RQ model 24 | 25 | # **Copyright** 26 | 27 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 28 | -------------------------------------------------------------------------------- /content/rcs/rc-22.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Implement XIP-74, XIP-75, XIP-76 3 | id: 22 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-08-30' 8 | updated: '2024-09-04' 9 | implemented: '2024-12-02' 10 | --- 11 | # **Outcome** 12 | 13 | Enable [Bullrun (XIP-74)](https://proposals.infinex.xyz/xips/xip-74), [Infinex Account v3 (XIP-76)](https://proposals.infinex.xyz/xips/xip-76) and the [Patron Sale Early Access (XIP-75)](https://proposals.infinex.xyz/xips/xip-75). 14 | 15 | # **Overview** 16 | 17 | This release enables: 18 | 19 | - The initial alpha of Bullrun per XIP-74. 20 | - The initial rollout of the Patron Sale to Early Access users per XIP-75. 21 | - The upgrade of the Infinex Account to v3 per XIP-76. 22 | 23 | # **Copyright** 24 | 25 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 26 | -------------------------------------------------------------------------------- /content/rcs/rc-36.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Implement Infinex V4 Account 3 | id: 36 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-12-02' 8 | updated: '2025-01-09' 9 | implemented: '2025-12-08' 10 | --- 11 | # **Outcome** 12 | 13 | Prepare for Infinex v2.0 update and implement Infinex Account v4. 14 | 15 | # **Overview** 16 | 17 | Infinex will implement the following changes 18 | 19 | - Implement the new [XIP-91: Infinex Account V4](https://proposals.infinex.xyz/xips/xip-91) 20 | - Temporarily turn off bridge and swap functionality in preparation for the Infinex V2 update. 21 | - Temporarily schedule up to up to 2 hours of downtime, where the Infinex App (app.infinex.xyz) will redirect users to a maintenance page. 22 | 23 | # **Copyright** 24 | 25 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 26 | -------------------------------------------------------------------------------- /content/rcs/rc-24.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Deploy Bullrun Contracts 3 | id: 24 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-09-11' 8 | updated: '2024-09-18' 9 | implemented: '2024-09-12' 10 | --- 11 | # **Outcome** 12 | 13 | Deploy Bullrun contracts onto Blast. 14 | 15 | # **Overview** 16 | 17 | The CWG aims to deploy the Bullrun contracts to Blast. In order to perform the deployment, the CWG needs to deploy the full set of Infinex contracts, which includes account creation. 18 | 19 | Account creation will not be turned on until [XIP-78](https://proposals.infinex.xyz/xips/xip-78) has been approved - the only functionality that will be live will be the specification described in [XIP-74: Bullrun](https://proposals.infinex.xyz/xips/xip-74). 20 | 21 | # **Copyright** 22 | 23 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 24 | -------------------------------------------------------------------------------- /content/rcs/rc-41.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Update Swidge Fees 3 | id: 41 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2025-01-20' 8 | updated: '2025-02-13' 9 | implemented: '2025-01-24' 10 | --- 11 | # **Outcome** 12 | 13 | Update the Swidge Fees 14 | 15 | # **Overview** 16 | 17 | Infinex will implement the following changes: 18 | 19 | - Swidge fees will move from % based on amount to being based on gas estimation. 20 | 21 | - This means users that are swidging will only pay for the gas that Infinex uses to execute the transaction 22 | 23 | - Patrons will have base network fees sponsored by us for L2s and Solana. 24 | 25 | - Patrons will still need to pay for Ethereum network fees 26 | - Patrons can also choose to pay extra gas in order to accelerate their transaction. 27 | 28 | # **Copyright** 29 | 30 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 31 | -------------------------------------------------------------------------------- /content/rcs/rc-43.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Upgrade Swidge 3 | id: 43 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Approved 7 | created: '2025-02-27' 8 | updated: '2025-03-03' 9 | --- 10 | # **Outcome** 11 | 12 | Release improvements to Swidge 13 | 14 | # **Overview** 15 | 16 | This RC includes the following changes to swidge: 17 | 18 | - Support for Cowswap and Stargate LFT as new swidge providers. 19 | - Release of the Infinex Faucet - specified in [XIP-99](https://proposals.infinex.xyz/xips/xip-99). 20 | - Smarter swidging with additional routes from existing providers and a refreshed UI. 21 | 22 | Furthermore, the following general updates are proposed: 23 | 24 | - A fix to the Pengu airdrop, ensuring all valid users receive their tokens 25 | - Removing the auto deployment of Solana vaults on signup. 26 | 27 | # **Copyright** 28 | 29 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 30 | -------------------------------------------------------------------------------- /content/rcs/rc-21.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Add more Tokens & NFTs 3 | id: 21 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-08-27' 8 | updated: '2024-08-30' 9 | --- 10 | # **Outcome** 11 | 12 | Implement [XIP-70](https://proposals.infinex.xyz/xips/xip-70), [71](https://proposals.infinex.xyz/xips/xip-71), [72](https://proposals.infinex.xyz/xips/xip-72) and partially implement [XIP-73](https://proposals.infinex.xyz/xips/xip-73). 13 | 14 | # **Overview** 15 | 16 | This release implements the assets associated with XIP-70, 71 and 72. This release also implements five NFTs that are approved in [XIP-73](https://proposals.infinex.xyz/xips/xip-73). 17 | 18 | These five NFTs are 19 | 20 | 1. CryptoPunks 21 | 1. Pudgy Penguins 22 | 1. Bored Ape Yacht Club 23 | 1. Mutant Ape Yacht Club 24 | 1. Milady Maker 25 | 26 | # **Copyright** 27 | 28 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 29 | -------------------------------------------------------------------------------- /content/rcs/rc-15.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Update Craterun Campaign 2 3 | id: 15 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-07-19' 8 | implemented: '2024-07-20' 9 | --- 10 | # Outcome 11 | 12 | Update Craterun to display Renzo and Eigenlayer points, implement XIP-60 and release the funds recovery app. 13 | 14 | # Overview 15 | 16 | This release includes a variety of updates to the Craterun Campaign. Changes include: 17 | 18 | - Updating the UI to reflect a user’s Renzo and Eigenlayer points (earned from depositing ezETH). 19 | - Enabling support for DeFi assets, and implementing DeFi Summer boosts, as approved in [XIP-60](https://proposals.infinex.xyz/xips/xip-60). 20 | - Releasing the funds recovery app, as per [XIP-23](https://proposals.infinex.xyz/xips/xip-23), which allows users with lost passkeys to recover their funds. 21 | 22 | # **Copyright** 23 | 24 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 25 | -------------------------------------------------------------------------------- /content/rcs/rc-14.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Prepare for Pyth Airdrop 3 | id: 14 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-07-08' 8 | implemented: '2024-07-10' 9 | --- 10 | # Overview 11 | 12 | This release prepares Infinex for the upcoming pyth airdrop, and updates the implementation of referral boosts. 13 | 14 | Changes include: 15 | 16 | - Adding bridged variants of PYTH to all Infinex supported networks, based on official PYTH [docs](https://docs.pyth.network/home/pyth-token/pyth-token-addresses). 17 | - Added implementation of referral boosts as per [XIP-53](https://proposals.infinex.xyz/xips/xip-53). 18 | - Added badges for the Pyth airdrop in preparation for [TRF-4](https://proposals.infinex.xyz/trfs/trf-4) 19 | - Added public /public/ctp/prizes endpoint 20 | 21 | # Outcome 22 | 23 | Prepare Infinex for PYTH Airdrop, and update referrals. 24 | 25 | # Copyright 26 | 27 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 28 | -------------------------------------------------------------------------------- /content/rcs/rc-33.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Slash Bullrun Bot Prizes 3 | id: 33 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-10-30' 8 | updated: '2024-11-18' 9 | implemented: '2024-11-01' 10 | --- 11 | # **Outcome** 12 | 13 | Slash Bullrun Bot Prizes. 14 | 15 | # **Overview** 16 | 17 | Bullrun players that won a Patron NFT but were detected as having used automated bots to play across >10 accounts will have their prizes disallowed. This totals 87 Patron NFTs in prizes. The exact methodology for detection will not be revealed, however players that believe they have been incorrectly slashed can reach out to Infinex Support. Slashed Patrons will be returned to the treasury. 18 | 19 | Furthermore, Infinex will introduce anti-botting strategies to bullrun. 20 | 21 | - New game mechanics (locking), to reduce the chance of bot strategies winning 22 | - More anti-bot measures 23 | 24 | # **Copyright** 25 | 26 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 27 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "infinex-proposals", 3 | "version": "1.0.0", 4 | "private": true, 5 | "scripts": { 6 | "dev": "next dev", 7 | "build": "next build", 8 | "start": "next start", 9 | "lint": "next lint", 10 | "preinstall": "npx -y only-allow pnpm" 11 | }, 12 | "dependencies": { 13 | "@keystatic/core": "^0.5.29", 14 | "@keystatic/next": "^5.0.1", 15 | "@markdoc/markdoc": "^0.4.0", 16 | "dotenv": "^16.3.1", 17 | "next": "14.2.5", 18 | "react": "^18.2.0", 19 | "react-dom": "^18.2.0", 20 | "zod": "^3.22.4" 21 | }, 22 | "devDependencies": { 23 | "@tailwindcss/typography": "^0.5.10", 24 | "@types/node": "^20", 25 | "@types/react": "^18.2.0", 26 | "@types/react-dom": "^18.2.0", 27 | "autoprefixer": "^10.0.1", 28 | "eslint": "^8", 29 | "eslint-config-next": "14.0.3", 30 | "postcss": "^8", 31 | "prettier": "^3.1.0", 32 | "prettier-plugin-tailwindcss": "^0.5.7", 33 | "tailwindcss": "^3.3.0", 34 | "typescript": "^5" 35 | } 36 | } 37 | -------------------------------------------------------------------------------- /content/rcs/rc-35.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Implement ENA Airdrops 3 | id: 35 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-11-19' 8 | updated: '2024-12-02' 9 | implemented: '2024-11-20' 10 | --- 11 | # **Outcome** 12 | 13 | Implement ENA Airdrops. 14 | 15 | # **Overview** 16 | 17 | Infinex will implement 3 separate Ethena airdrops. 18 | 19 | - [Badge Airdrop](https://proposals.infinex.xyz/trfs/trf-5): Users with a "OG Real Yield Maxi" will receive 482.27 ENA. Users will have 30 days to claim this. 20 | - [Season 2 Airdrop](https://proposals.infinex.xyz/xips/xip-64): Users will be able to claim their ENA from the Ethena Season 2 Sats Campaign. Users will have an indefinite time to claim 21 | - [Bonus Season 2 Airdrop](https://proposals.infinex.xyz/trfs/trf-7): Users will be able to claim their bonus ENA from the Ethena Season 2 Sats Campaign. Users will have an indefinite time to claim. 22 | 23 | # **Copyright** 24 | 25 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 26 | -------------------------------------------------------------------------------- /content/rcs/rc-12.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Add Memecoins 3 | id: 12 4 | wg: CWG 5 | author: jaynex (@0xjaynex) 6 | status: Implemented 7 | created: '2024-07-04' 8 | implemented: '2024-07-05' 9 | --- 10 | # Overview 11 | 12 | This release adds support for memecoins and launches the memecoin battles for Craterun boosts. It also includes a variety of fixes relating to crate opening. 13 | 14 | Changes include: 15 | 16 | - Enabling deposits from memecoins as per [XIP-51](https://proposals.infinex.xyz/xips/xip-51) 17 | - Enabling tracking and display of memecoin balances as battles as per [XIP-51](https://proposals.infinex.xyz/xips/xip-51) 18 | - Enabling memecoin battle boosts in Craterun as per [XIP-51](https://proposals.infinex.xyz/xips/xip-51) 19 | - A variety of visual and audio fixes to crate opening 20 | 21 | It also includes a variety of UI fixes and tweaks. 22 | 23 | # Outcome 24 | 25 | Upgrade the platform to enable memecoin deposits and memecoin battles. 26 | 27 | # Copyright 28 | 29 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 30 | -------------------------------------------------------------------------------- /content/rcs/rc-40.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Release Swidging to All 3 | id: 40 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2025-01-13' 8 | updated: '2025-02-13' 9 | implemented: '2025-01-17' 10 | --- 11 | # **Outcome** 12 | 13 | Release Swidging to all Infinex users. 14 | 15 | # **Overview** 16 | 17 | Infinex will implement the following changes 18 | 19 | - [Swidging](https://proposals.infinex.xyz/xips/xip-93) (Swapping and bridging) will be slowly rolled out to all Infinex users. Currently only users that have over 20 Patrons are able to access "Swidge". The CWG will slowly lower the amount of patrons required to access "Swidge", before granting all users access. 20 | - The process to transfer between a user's wallet and vault has been streamlined, no longer requiring a Time-based One-Time Passwords (TOTP) code. 21 | - The Bulls distribution for Bullrun has also been altered, instead of giving bulls to the top 1,000 users, Bulls are now granted to the top 2,500 users. 22 | 23 | # **Copyright** 24 | 25 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 26 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2023 Infinex 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /content/rcs/rc-11.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Update Craterun Campaign 3 | id: 11 4 | wg: CWG 5 | author: jaynex (@0xjaynex) 6 | status: Implemented 7 | created: '2024-07-02' 8 | implemented: '2024-07-02' 9 | --- 10 | # Overview 11 | 12 | This release launches the ability to open crates and receive prizes. It also adds referrals. 13 | 14 | Changes include: 15 | 16 | - Deploying and funding the crate opening contract 17 | - Integrating the crate opening contract into the app 18 | - Updating the Craterun UI to allow opening crates and viewing prizes 19 | - Updating Craterun boosts to count boosts from opened crates 20 | - Adding referral codes for all users 21 | - Adding new referred user bonus as per [XIP-53](https://proposals.infinex.xyz/xips/xip-53) 22 | - Add new referral bonuses as per [XIP-53](https://proposals.infinex.xyz/xips/xip-53) 23 | - Remove old STW frontend components 24 | 25 | It also includes a variety of UI fixes and tweaks. 26 | 27 | # Outcome 28 | 29 | Upgrade the platform to allow crate opening and support referrals. 30 | 31 | # Copyright 32 | 33 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 34 | -------------------------------------------------------------------------------- /content/rcs/rc-7.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Finalise STW Campaign 3 | id: 7 4 | wg: CWG 5 | author: jaynex (@0xjaynex) 6 | status: Implemented 7 | created: "2024-06-12" 8 | implemented: "2024-06-12" 9 | --- 10 | ### Overview 11 | 12 | The Speedrun The Waitlist Campaign ends 13/06/2024. The CWG has updated the Infinex Website, Dashboard, and Home Page to reflect this and enable users to participate in the next campaign. 13 | 14 | ### Outcome 15 | 16 | Upgrade the platform to finalise Speedrun The Waitlist and prepare for what's coming next. 17 | 18 | ### Proposed Changes 19 | 20 | ##### **Platform** 21 | 22 | Added functionality to close out the Speedrun The Waitlist campaign and support subsequent campaign features, including updates to the homepage and dashboard. 23 | 24 | Notable changes include summarising the campaign outcomes, displaying final waitlist rankings, as well as the removal of staking and claiming functionality after the campaign timer has ended. 25 | 26 | Additional optimisations have been made for loading speed and mobile devices. 27 | 28 | # Copyright 29 | 30 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 31 | -------------------------------------------------------------------------------- /content/rcs/rc-10.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Release Craterun Campaign 3 | id: 10 4 | wg: CWG 5 | author: jaynex (@0xjaynex) 6 | status: Implemented 7 | created: '2024-06-24' 8 | implemented: '2024-06-25' 9 | --- 10 | # Overview 11 | 12 | This release launches the Infinex Craterun Campaign, including: 13 | 14 | - New Craterun UI, including campaign-specific terms and conditions 15 | - Allow Users to stake their Account Balance plus any earned Boosts and (after reward streaming is started) earn Crate Points 16 | - Enable additional assets as per [XIP-43](https://proposals.infinex.xyz/xips/xip-43), [XIP-46](https://proposals.infinex.xyz/xips/xip-46), [XIP-48](https://proposals.infinex.xyz/xips/xip-48), [XIP-49](https://proposals.infinex.xyz/xips/xip-49), [XIP-50](https://proposals.infinex.xyz/xips/xip-50) 17 | - Enable the amnesty feature for withdrawals and redeposits as per [XIP-40](https://proposals.infinex.xyz/xips/xip-40) 18 | 19 | It also includes a variety of UI fixes and tweaks. 20 | 21 | # Outcome 22 | 23 | Upgrade the platform to launch Craterun and support new assets. 24 | 25 | # Copyright 26 | 27 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 28 | -------------------------------------------------------------------------------- /content/rcs/rc-3.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Host Pre-Alpha Infinex App Infrastructure 3 | id: 3 4 | wg: Infrastructure WG 5 | author: RocketFish (@Rocketfish0007), Bilby (@bilb-y) 6 | status: Reverted 7 | created: '2023-12-20' 8 | updated: '2023-04-15' 9 | implemented: '2023-12-21' 10 | --- 11 | ## Pre-alpha Release 12 | 13 | ### Overview 14 | 15 | The Infrastructure Working Group (WG) will deploy the Infinex App to a production environment so that it can undergo quality assurance and be accessible to users invited to the pre-alpha release. 16 | 17 | --- 18 | 19 | ### Outcome 20 | 21 | Deploy a pre-alpha build of Infinex to a production environment, as specified in [RC-2](/content/rcs/rc-2.mdoc) and [XIP-9](/content/xips/xip-9.mdoc). 22 | 23 | --- 24 | 25 | ### Proposed Changes 26 | 27 | **Infinex App & Platform** 28 | 29 | The backend and frontend tagged engineering output from [RC-2](/content/rcs/rc-2.mdoc) is proposed be deployed by the Infrastructure WG using some or all (as required) of the following platforms: 30 | 31 | - AWS 32 | - PlanetScale 33 | - CloudFlare 34 | - Vercel 35 | 36 | --- 37 | 38 | # Copyright 39 | 40 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 41 | -------------------------------------------------------------------------------- /content/rcs/rc-38.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Fee Update for Swaps 3 | id: 38 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-12-30' 8 | updated: '2025-01-17' 9 | implemented: '2025-01-09' 10 | --- 11 | # **Outcome** 12 | 13 | Update the fees taken on swaps. 14 | 15 | # **Overview** 16 | 17 | This RC proposes a new fee structure to be implemented for Swaps. 18 | 19 | - "Swap" here means from and to are on the same chain. 20 | - "Stable" here means the same underlying asset is the price driver (ie a nominal 1:1 and non volatile swap ratio), eg USDC and USDT are both `usd`, ETH, WETH and STETH are all `eth` etc. 21 | - "Swidge" refers to the swapping and bridging of an asset, i.e ETH → SOL. 22 | - Fees are all in bps 23 | 24 | {% table %} 25 | --- 26 | - 27 | - 0 Patrons 28 | - 1 Patron 29 | - 5 Patrons 30 | - 10 Patrons 31 | --- 32 | - Stable Swap 33 | - 10 34 | - 6 35 | - 4 36 | - 2 37 | --- 38 | - Stable Swidge 39 | - 12 40 | - 8 41 | - 6 42 | - 4 43 | --- 44 | - Swap 45 | - 80 46 | - 48 47 | - 32 48 | - 16 49 | --- 50 | - Swidge (no change in fees) 51 | - 100 52 | - 60 53 | - 40 54 | - 20 55 | {% /table %} 56 | 57 | # **Copyright** 58 | 59 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 60 | -------------------------------------------------------------------------------- /content/tas/ta-7.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Airdrop Additional ENA to Users 3 | id: 7 4 | author: Egor (@egorsidelska), kmao (@kmaox) 5 | status: Implemented 6 | created: '2024-11-19' 7 | --- 8 | # **Summary** 9 | 10 | Treasury has approved to airdrop an additional 85,579.5 ENA to users that are eligible for ENA via the Season 2 Ethena Sats Campaign on the Infinex Platform. 11 | 12 | # **Overview** 13 | 14 | Users who were eligible to receive ENA through the [Ethena Season 2 Campaign](https://proposals.infinex.xyz/xips/xip-64) will receive an additional 15% bonus on top of their pro-rata’d rewards. As an example, a user who would receive 10,000 ENA will now receive 11,500 ENA. 15 | 16 | # **Rationale** 17 | 18 | We would like to express our gratitude to users for their understanding and patience regarding the delay in the distribution of Season 2 rewards. 19 | 20 | # **Specification** 21 | 22 | Airdropped ENA will be liquid, however, requires a user to claim via the Infinex Platform. 23 | 24 | The process of claiming involves the user initiating a claim through their Infinex Account. Once claimed, ENA will show up in their account assets under Wallet. 25 | 26 | Accounts which do not have a EVM recovery address will need to create one and follow the account security steps before they can withdraw. 27 | -------------------------------------------------------------------------------- /content/rcs/rc-17.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Release Ethena Sats Campaign 3 | id: 17 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-08-05' 8 | updated: '2024-08-14' 9 | implemented: '2024-08-06' 10 | --- 11 | # **Outcome** 12 | 13 | Release the functionality required for the Ethena Sats Campaign, as well as update various other UI components. 14 | 15 | # **Overview** 16 | 17 | This release includes various changes related to the upcoming Ethena Campaign. Changes include 18 | 19 | - Add functionality for swaps between USDC and USDe in the Wallet page, as per [XIP-30](https://proposals.infinex.xyz/xips/xip-30). 20 | - Enable calculation and tracking of earned Sats including bonuses per [XIP-64](https://proposals.infinex.xyz/xips/xip-64). 21 | - Enable bridging of USDC between all supported chains. 22 | - Enable withdrawal amounts to be chosen by users per [XIP-39](https://proposals.infinex.xyz/xips/xip-39) (does not fully implement Send V1 yet). 23 | - Implement a new app sidebar and nav structure 24 | - Implement an updated homepage after Craterun 25 | - Add a new "Earn" page (listing of all the earning integrations; replaces the current 'integrations' page). 26 | 27 | # **Copyright** 28 | 29 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 30 | -------------------------------------------------------------------------------- /content/xips/xip-72.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Renzo Token 3 | id: 72 4 | author: kmao (@kmaox) 5 | type: core-upgrade 6 | network: Ethereum 7 | status: Implemented 8 | created: '2024-08-26' 9 | updated: '2024-08-30' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-72 enables support for the Renzo token, REZ. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Infinex will need to update the UI to effectively reflect REZ deposits and withdrawals, as well as the current market price of the asset. The value of these assets will be denominated in USD and determined by a 3rd-party market price feed. 20 | 21 | ## Rationale 22 | 23 | Renzo has recently concluded it's Season 2 campaign, which has resulted in the conversion of ezPoints to REZ tokens. In order to enable users to claim their tokens, Infinex must support the REZ token. 24 | 25 | ## Technical Specification 26 | 27 | Infinex will add for the REZ token on the Mainnet network. The token address is `0x3b50805453023a91a8bf641e279401a0b23fa6f9` 28 | 29 | The Infinex account currently does not block deposits from any tokens, which means to support these assets, Infinex will simply just need to upgrade the backend infrastructure to track them. 30 | 31 | # Copyright 32 | 33 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 34 | -------------------------------------------------------------------------------- /content/xips/xip-81.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Eigen Token 3 | id: 81 4 | author: kmao (@kmaox) 5 | type: core-upgrade 6 | network: Ethereum 7 | status: Implemented 8 | created: '2024-09-24' 9 | updated: '2024-10-29' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-81 enables support for the EIGEN token. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Infinex will need to update the UI to effectively reflect EIGEN deposits and withdrawals, as well as the current market price of the asset. The value of these assets will be denominated in USD and determined by a 3rd-party market price feed. 20 | 21 | ## Rationale 22 | 23 | Eigen has recently concluded it's Season 2 campaign, which has resulted in the conversion of Eigenlayer points to EIGEN. In order to enable users to claim their tokens, Infinex must support the EIGEN token. 24 | 25 | ## Technical Specification 26 | 27 | Infinex will add for the EIGEN token on the Mainnet network. The token address is `0xec53bF9167f50cDEB3Ae105f56099aaaB9061F83` 28 | 29 | The Infinex account currently does not block deposits from any tokens, which means to support these assets, Infinex will simply just need to upgrade the backend infrastructure to track them. 30 | 31 | # Copyright 32 | 33 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 34 | -------------------------------------------------------------------------------- /content/xips/xip-80.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Gift Patron Passes 3 | id: 80 4 | author: kmao (@kmaox) 5 | type: core-upgrade 6 | status: Implemented 7 | created: '2024-09-19' 8 | updated: '2024-09-24' 9 | --- 10 | # **Proposal Summary** 11 | 12 | This XIP proposes the ability to gift Patron Passes. 13 | 14 | # **Specification** 15 | 16 | ## **Overview** 17 | 18 | Infinex will update the UI to allow users to gift other users Patron Passes. These Passes will grant users access to Wave 3 of the Patron Sale. 19 | 20 | ## **Rationale** 21 | 22 | A large amount of Patron Passes are held in accounts that have already been granted access to the Patron Sale via Wave 1 or 2, making them redundant. On the flipside, there are various users that have no Patron Passes, that would like to participate in the Wave 3 sale. 23 | 24 | Allowing users to gift their Patron Passes to others will reduce the unused Patron Passes held by accounts that have already purchased their desired allocation. 25 | 26 | ## **Technical Specification** 27 | 28 | Since Patron Passes are not on-chain, the CWG just needs to update the UI to allow users to transfer their Patron Passes, and update the amount of Patron Passes a user has in the database. 29 | 30 | # **Copyright** 31 | 32 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 33 | -------------------------------------------------------------------------------- /content/xips/xip-32.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Improve GP Distribution Vote 3 | id: 32 4 | author: fommes (@fommes) 5 | type: 'community' 6 | network: 'Base' 7 | status: Rejected 8 | created: '2024-06-05' 9 | --- 10 | # Proposal Summary 11 | This XIP proposes an improved GP distribution vote from the Retirement Fund to commited community members. 12 | 13 | # Specification 14 | 15 | ## Overview 16 | 17 | [This tweet](https://x.com/infinex_app/status/1796693183642149094) from the Infinex Twitter account has asked various crypto communities to vote for which ones will recieve a share of 30M GP from the Retirement Fund. 18 | 19 | Instead, this proposal aims to create a better vote in which only commited community members can participate. I propose the vote be conducted instead in the Infinex discord, where NFTs holders of mentioned communities and Infinex community members are allowed to participate. 20 | ## Rationale 21 | 22 | Votes on Twitter can easily be botted or just soliciting non community members to vote favourable and should not be indicative. 23 | 24 | ## Technical Specification 25 | 26 | To identify holders, Discord bots have to be added: 27 | 28 | - Guild or Collabland for EVM 29 | - Matrica Verification for Solana 30 | 31 | # Copyright 32 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 33 | -------------------------------------------------------------------------------- /src/components/Logo.tsx: -------------------------------------------------------------------------------- 1 | type LogoProps = React.SVGProps; 2 | export const InfinexLogo = (props: LogoProps) => { 3 | return ( 4 | 12 | 18 | 24 | 25 | ); 26 | }; 27 | -------------------------------------------------------------------------------- /content/rcs/rc-6.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support USDe Deposits 3 | id: 6 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-05-28' 8 | implemented: '2024-05-28' 9 | --- 10 | ### Overview 11 | 12 | Infinex currently supports USDC deposits for staking and claiming. The CWG will add support for USDe deposits and GP staking. 13 | 14 | ### Outcome 15 | 16 | Upgrade the platform to support USDe deposits, as approved in [XIP-29](https://proposals.infinex.xyz/xips/xip-29). 17 | 18 | ### Proposed Changes 19 | 20 | ##### **Platform** 21 | 22 | Releasing support for USDe deposits requires a refreshed wallet interface that displays all supported (native and bridged USDC, and USDe). Furthermore, this RC also aims to update the "integrations" page in-app to show information about USDe support. This integration was approved in [XIP-29](https://proposals.infinex.xyz/xips/xip-29), and this RC implements the technical specification outlined there. 23 | 24 | Other user experience improvements included in this proposed release include: 25 | 26 | - Improved deposit UI and workflow. 27 | - Improved funds recovery setup experience. 28 | 29 | **Once upgraded, users who deposit USDe will be able to stake their full deposited balance (USDe + USDC) and earn GP.** 30 | 31 | # Copyright 32 | 33 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 34 | -------------------------------------------------------------------------------- /src/app/irs/[slug]/page.tsx: -------------------------------------------------------------------------------- 1 | import { notFound } from 'next/navigation'; 2 | import { ID, Properties, Renderer } from '@/components/Document'; 3 | import { Header } from '@/components/Header'; 4 | import { Back, PageContainer, PageTitle } from '@/components/UI'; 5 | import { reader } from '@/lib/reader'; 6 | import { number } from '@/lib/util'; 7 | import keystatic from '@/../keystatic.config'; 8 | 9 | type Params = { 10 | slug: string; 11 | }; 12 | 13 | const schema = keystatic.collections.irs.schema; 14 | const fields = Object.keys(schema); 15 | 16 | export async function generateStaticParams(): Promise { 17 | const topics = await reader.collections.irs.all(); 18 | return topics.map((ir) => ({ 19 | slug: ir.slug, 20 | })); 21 | } 22 | 23 | export default async function Page({ params }: { params: Params }) { 24 | const ir = await reader.collections.irs.read(params.slug, { 25 | resolveLinkedFiles: true, 26 | }); 27 | 28 | if (!ir) return notFound(); 29 | 30 | return ( 31 | 32 |
33 |
34 | Back to all IRs 35 |
36 | IR-{number(ir.id!)} 37 | {ir.title} 38 | 39 | 40 | 41 | ); 42 | } 43 | -------------------------------------------------------------------------------- /src/app/tas/[slug]/page.tsx: -------------------------------------------------------------------------------- 1 | import { notFound } from 'next/navigation'; 2 | import { ID, Properties, Renderer } from '@/components/Document'; 3 | import { Header } from '@/components/Header'; 4 | import { Back, PageContainer, PageTitle } from '@/components/UI'; 5 | import { reader } from '@/lib/reader'; 6 | import { number } from '@/lib/util'; 7 | import keystatic from '@/../keystatic.config'; 8 | 9 | type Params = { 10 | slug: string; 11 | }; 12 | 13 | const schema = keystatic.collections.tas.schema; 14 | const fields = Object.keys(schema); 15 | 16 | export async function generateStaticParams(): Promise { 17 | const topics = await reader.collections.tas.all(); 18 | return topics.map((ta) => ({ 19 | slug: ta.slug, 20 | })); 21 | } 22 | 23 | export default async function Page({ params }: { params: Params }) { 24 | const ta = await reader.collections.tas.read(params.slug, { 25 | resolveLinkedFiles: true, 26 | }); 27 | 28 | if (!ta) return notFound(); 29 | 30 | return ( 31 | 32 |
33 |
34 | Back to all TAs 35 |
36 | ta-{number(ta.id!)} 37 | {ta.title} 38 | 39 | 40 | 41 | ); 42 | } 43 | -------------------------------------------------------------------------------- /src/lib/util.ts: -------------------------------------------------------------------------------- 1 | const authorRegExp = /(.+)\(@([\w\-]+)\)/; 2 | 3 | export function splitAuthors(authors: string) { 4 | return authors.split(',').map((author) => { 5 | const parts = authorRegExp.exec(author); 6 | return parts 7 | ? { name: parts[1].trim(), handle: parts[2].trim() } 8 | : { name: author.trim() }; 9 | }); 10 | } 11 | 12 | export function number(num: number) { 13 | return [0, 9999].includes(num) ? 'X' : num; 14 | } 15 | 16 | type StatusColors = { 17 | [key: string]: { 18 | border: string; 19 | text: string; 20 | }; 21 | }; 22 | 23 | export const statusColors: StatusColors = { 24 | DEFAULT: { 25 | border: 'border-DEFAULT', 26 | text: 'text-slate11', 27 | }, 28 | Approved: { 29 | border: 'border-positive', 30 | text: 'text-positive', 31 | }, 32 | Rejected: { 33 | border: 'border-ruby3', 34 | text: 'text-critical', 35 | }, 36 | Reverted: { 37 | border: 'border-ruby3', 38 | text: 'text-critical', 39 | }, 40 | Dissolved: { 41 | border: 'border-ruby3', 42 | text: 'text-critical', 43 | }, 44 | Superseded: { 45 | border: 'border-caution', 46 | text: 'text-caution', 47 | }, 48 | Implemented: { 49 | border: 'border-blue6', 50 | text: 'text-blue11', 51 | }, 52 | }; 53 | 54 | export function getStatusColors(status: string) { 55 | return statusColors[status] || statusColors.DEFAULT; 56 | } 57 | -------------------------------------------------------------------------------- /content/xips/xip-100.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: BSC Expansion 3 | id: 100 4 | author: kmao (@kmaox) 5 | type: integration-upgrade 6 | network: BSC 7 | status: Approved 8 | created: '2025-02-24' 9 | updated: '2025-03-03' 10 | --- 11 | # **Proposal Summary** 12 | 13 | This XIP proposes integrating BSC Vaults, Wallets and Swidging. 14 | 15 | # **Specification** 16 | 17 | ## **Overview** 18 | 19 | Infinex will expand the existing Vault and Wallet infrastructure onto Binance Smart Chain, to allow users to deposit, withdraw, and send funds on BSC. 20 | 21 | Infinex will also support all assets on BSC, based on [**XIP-96**](https://proposals.infinex.xyz/xips/xip-96). Some assets may not be initially supported, however, the CWG will have the ability to add them based on community request. 22 | 23 | ## **Rationale** 24 | 25 | ## **Technical Specification** 26 | 27 | To allow for the deployment of the Infinex vault, wallet, and swidging on BSC, Infinex would be required to deploy the same smart contracts and infrastructure that exists on other supported chains, specified in the O2 Cannon deployment. 28 | 29 | Infinex's existing list of Swidge providers already provides coverage for BSC swidging, however additional providers may be added in the future, to help further improve speed and pricing. 30 | 31 | # **Copyright** 32 | 33 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 34 | -------------------------------------------------------------------------------- /src/app/rcs/[slug]/page.tsx: -------------------------------------------------------------------------------- 1 | import { notFound } from 'next/navigation'; 2 | import { ID, Properties, Renderer } from '@/components/Document'; 3 | import { Header } from '@/components/Header'; 4 | import { Back, PageContainer, PageTitle } from '@/components/UI'; 5 | import { reader } from '@/lib/reader'; 6 | import { number } from '@/lib/util'; 7 | import keystatic from '@/../keystatic.config'; 8 | 9 | type Params = { 10 | slug: string; 11 | }; 12 | 13 | const schema = keystatic.collections.rcs.schema; 14 | const fields = Object.keys(schema); 15 | 16 | export async function generateStaticParams(): Promise { 17 | const topics = await reader.collections.rcs.all(); 18 | return topics.map((rc) => ({ 19 | slug: rc.slug, 20 | })); 21 | } 22 | 23 | export default async function Page({ params }: { params: Params }) { 24 | const entry = await reader.collections.rcs.read(params.slug, { 25 | resolveLinkedFiles: true, 26 | }); 27 | 28 | if (!entry) return notFound(); 29 | 30 | return ( 31 | 32 |
33 |
34 | Back to all RCs 35 |
36 | RC-{number(entry.id!)} 37 | {entry.title} 38 | 39 | 40 | 41 | ); 42 | } 43 | -------------------------------------------------------------------------------- /src/app/wgcs/[slug]/page.tsx: -------------------------------------------------------------------------------- 1 | import { notFound } from 'next/navigation'; 2 | import { ID, Properties, Renderer } from '@/components/Document'; 3 | import { Header } from '@/components/Header'; 4 | import { Back, PageContainer, PageTitle } from '@/components/UI'; 5 | import { reader } from '@/lib/reader'; 6 | import { number } from '@/lib/util'; 7 | import keystatic from '@/../keystatic.config'; 8 | 9 | type Params = { 10 | slug: string; 11 | }; 12 | 13 | const schema = keystatic.collections.wgcs.schema; 14 | const fields = Object.keys(schema); 15 | 16 | export async function generateStaticParams(): Promise { 17 | const topics = await reader.collections.wgcs.all(); 18 | return topics.map((wgc) => ({ 19 | slug: wgc.slug, 20 | })); 21 | } 22 | 23 | export default async function Page({ params }: { params: Params }) { 24 | const entry = await reader.collections.wgcs.read(params.slug, { 25 | resolveLinkedFiles: true, 26 | }); 27 | 28 | if (!entry) return notFound(); 29 | 30 | return ( 31 | 32 |
33 |
34 | Back to all WGCs 35 |
36 | WGC-{number(entry.id!)} 37 | {entry.title} 38 | 39 | 40 | 41 | ); 42 | } 43 | -------------------------------------------------------------------------------- /src/app/xips/[slug]/page.tsx: -------------------------------------------------------------------------------- 1 | import { notFound } from 'next/navigation'; 2 | import { ID, Properties, Renderer } from '@/components/Document'; 3 | import { Header } from '@/components/Header'; 4 | import { Back, PageContainer, PageTitle } from '@/components/UI'; 5 | import { reader } from '@/lib/reader'; 6 | import { getStatusColors, number } from '@/lib/util'; 7 | import keystatic from '@/../keystatic.config'; 8 | 9 | type Params = { 10 | slug: string; 11 | }; 12 | 13 | const schema = keystatic.collections.xips.schema; 14 | const fields = Object.keys(schema); 15 | 16 | export async function generateStaticParams(): Promise { 17 | const topics = await reader.collections.xips.all(); 18 | return topics.map((xip) => ({ 19 | slug: xip.slug, 20 | })); 21 | } 22 | 23 | export default async function Page({ params }: { params: Params }) { 24 | const xip = await reader.collections.xips.read(params.slug, { 25 | resolveLinkedFiles: true, 26 | }); 27 | 28 | if (!xip) return notFound(); 29 | const colors = getStatusColors(xip.status); 30 | 31 | return ( 32 | 33 |
34 |
35 | Back to all XIPs 36 |
37 | XIP-{number(xip.id!)} 38 | {xip.title} 39 | 40 | 41 | 42 | ); 43 | } 44 | -------------------------------------------------------------------------------- /content/xips/xip-102.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sonic Expansion 3 | id: 102 4 | author: Jed (@jedinfinex) 5 | type: integration-upgrade 6 | network: Sonic 7 | status: Draft 8 | created: '2025-03-17' 9 | --- 10 | # **Proposal Summary** 11 | 12 | This XIP proposes integrating Sonic Vaults, Wallets and Swidging. 13 | 14 | # **Specification** 15 | 16 | ## **Overview** 17 | 18 | Infinex will expand the existing Vault and Wallet infrastructure onto Sonic, to allow users to deposit, withdraw, and send funds on Sonic. 19 | 20 | Infinex will also support all assets on Sonic, based on [**XIP-96**](https://proposals.infinex.xyz/xips/xip-96). Some assets may not be initially supported, however, the CWG will have the ability to add them based on community request. 21 | 22 | ## **Rationale** 23 | 24 | Sonic is a popular new chain that has seen rapid adoption, with a lot of TVL and activity. Infinex wants to ensure that its users can interact with it. 25 | 26 | ## **Technical Specification** 27 | 28 | To allow for the deployment of the Infinex vault, wallet, and swidging on Sonic, Infinex would be required to deploy the same smart contracts and infrastructure that exists on other supported chains. 29 | 30 | Infinex's existing list of Swidge providers already provides coverage for Sonic swidging, however additional providers may be added in the future, to help further improve speed and pricing. 31 | 32 | # **Copyright** 33 | 34 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 35 | -------------------------------------------------------------------------------- /content/xips/xip-56.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Increase Memecoin Madness Boosts 3 | id: 56 4 | author: kmao (@kmaox) 5 | type: integration-upgrade 6 | network: Solana, Ethereum, Base, Arbitrum 7 | status: Implemented 8 | created: '2024-07-04' 9 | updated: '2024-07-18' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-56 provides an update to "[Memecoin Madness](https://proposals.infinex.xyz/xips/xip-51)". 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | As crate opening has been enabled on Infinex, it is now apparent that users are recieving a high amount of boosts, which make the 25% boost incentive for depositing memecoins not as strong as before. 20 | 21 | In order to better encourage memecoin deposits, Infinex aims to increase the 25% boost incentive to 100%. This means, each day for a week, two memecoins will battle for the highest TVL. Users will have 24 hours to deposit into their Infinex Account, the memecoin that wins will qualify for a 100% deposit bonus for the rest of Craterun. 22 | 23 | ## Rationale 24 | 25 | Infinex has distributed a large amount of boosts already, which means the incentives for Memecoin Madness will no longer be as effective. As such, this XIP aims to rectify this. 26 | 27 | ## Technical Specification 28 | 29 | Infinex will need to update the backend code to grant users a 100% boost on the winning memewar, memecoin deposit bonus, instead of the prior 25%. 30 | 31 | # Copyright 32 | 33 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 34 | -------------------------------------------------------------------------------- /content/xips/xip-87.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support $BITCOIN 3 | id: 87 4 | author: Graeme (@sonicdigitallabs) 5 | type: integration-upgrade 6 | network: 'Ethereum, Base' 7 | status: Approved 8 | created: '2024-10-19' 9 | updated: '2024-10-29' 10 | --- 11 | # Proposal Summary 12 | 13 | This XIP proposes support of the $BITCOIN token within the Infinex ecosystem 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | $BITCOIN is a parody memecoin that helped start the memecoin revolution 20 | 21 | Currently, $BITCOIN is not displayed on Infinex. 22 | 23 | ## Rationale 24 | 25 | Memecoins are one of the hottest narratives in crypto right now, and a variety of Infinex community members have requested support for them. Memecoins also have no utility, which means most users are simply holding them in a wallet. This means users will be more likely to deposit these assets into their Infinex Account due to lower opportunity costs. 26 | 27 | ## Technical Specification 28 | 29 | A list of the supported token, network, and token address can be found below. Infinex will add support for deposit and withdrawals for all of the listed tokens. 30 | 31 | {% table %} 32 | --- 33 | - Token 34 | - Network 35 | - Token Address 36 | --- 37 | - BITCOIN 38 | - Mainnet 39 | - 0x72e4f9F808C49A2a61dE9C5896298920Dc4EEEa9 40 | --- 41 | - BITCOIN 42 | - Base 43 | - 0x2a06A17CBC6d0032Cac2c6696DA90f29D39a1a29 44 | {% /table %} 45 | 46 | # Copyright 47 | 48 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 49 | -------------------------------------------------------------------------------- /content/xips/xip-59.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support ZK token + ZKsync Era 3 | id: 59 4 | author: Kvasir (@0xKvasir) 5 | type: core-upgrade 6 | network: Zksync Era 7 | status: Rejected 8 | created: '2024-07-12' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-59 proposes enabling support for ZKsync and its token ZKsync (ZK). 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | ZKsync Era is a Layer 2 ZK rollup, a trustless protocol that uses cryptographic validity proofs to provide scalable and low-cost transactions on Ethereum. In ZKsync Era, computation is performed off-chain and most data is stored off-chain as well. Transactions are bundled into batches before generating a validity proof. As all validity proofs are proven on Ethereum, users enjoy the same security warranties as in the L1. 19 | 20 | ## Rationale 21 | There are quite a few projects building on ZK technology and its usage is increasing, therefor it would be a great addition for the broader Infinex ecosystem. 22 | 23 | ## Technical Specification 24 | 25 | Infinex already has support for (L2) EVM tokens, so it just needs to update the backend to support the new token and chain structure. 26 | 27 | ### Token contracts 28 | 29 | - Zksync [0x5a7d6b2f92c77fad6ccabd7ee0624e64907eaf3e] 30 | 31 | ### Token Format 32 | 33 | Native ERC20 34 | Token symbol: ZK 35 | Max supply: 21,000,000,000 36 | 37 | [Additional information](https://blog.zknation.io/zk-token/) 38 | 39 | ## Test Cases 40 | 41 | # Copyright 42 | 43 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 44 | -------------------------------------------------------------------------------- /content/xips/xip-30.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Enable USDe Swaps 3 | id: 30 4 | author: winston (@blockchainwinston), axe (@axefinaxe) 5 | type: 'integration-upgrade' 6 | network: Ethereum, Arbitrum 7 | status: Implemented 8 | created: '2024-05-31' 9 | updated: '2024-08-27' 10 | --- 11 | # Proposal Summary 12 | XIP-30 proposes enabling swapping of USDC to USDe on Ethereum and Arbitrum. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Allow users to swap USDC to USDe to earn from Ethena in their Infinex accounts. 19 | 20 | ## Rationale 21 | 22 | Holding USDC in Infinex accounts does not earn any interest. As USDCe is now a supported asset, it would benefit users to be able to swap USDC to USDCe to earn from Ethena. This will decrease the need for users to withdraw USDC to their wallets and then deposit USDCe to earn from Ethena and participate in Infinex. 23 | 24 | ## Technical Specification 25 | 26 | Ethena currently supports swapping into USDe using a variety of pools. The primary pools are Curve StableSwapNG pools on Ethereum and Arbitrum. We will also add integrations for additional chains as they come along. 27 | 28 | We propose integrating Curve swaps for these pools on both chains to allow users to swap USDC to USDe within their Infinex accounts. 29 | 30 | Ethena does support minting via their API, however this is only for approved users and requires an application with KYC to be approved. Utilising the Curve pools instead is permissionless. 31 | 32 | # Copyright 33 | 34 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 35 | -------------------------------------------------------------------------------- /content/xips/xip-96.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support All Tokens 3 | id: 96 4 | author: kmao (@kmaox) 5 | type: core-upgrade 6 | network: Base, Optimism, Ethereum, Solana, Arbitrum, Polygon 7 | status: Approved 8 | created: '2025-01-14' 9 | updated: '2025-01-14' 10 | --- 11 | # **Proposal Summary** 12 | 13 | This XIP proposes support for all tokens on Solana and EVM chains. 14 | 15 | # **Specification** 16 | 17 | ## **Overview** 18 | 19 | The Infinex platform should be upgraded to support ALL assets on the chains where Infinex is supported on. Supporting an asset involves the following things: 20 | 21 | - Reflecting the asset in the user's balance and wallet. 22 | - Reflecting the price of the asset to the user. 23 | - Accepting withdrawals and deposits of the asset. 24 | - Allowing the asset to be Swidged (Swapped and/or bridged). 25 | 26 | ## **Rationale** 27 | 28 | Infinex has currently expanded to support the top 2000 tokens by market cap, assuming the token is on a supported network. However, users often want to trade trending coins, which may not have been added to Infinex yet, which is what this proposal helps support. 29 | 30 | ## **Technical Specification** 31 | 32 | For a token to be supported on Infinex, the token needs to have the following: 33 | 34 | - The token needs to be on a supported chain. 35 | - The token needs at least $10,000 of liquidity. 36 | 37 | Further details on what liquidity avenues are supported will be published in a future RC. 38 | 39 | # **Copyright** 40 | 41 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 42 | -------------------------------------------------------------------------------- /styles/typography/addTypographyClassesPlugin.ts: -------------------------------------------------------------------------------- 1 | import plugin from 'tailwindcss/plugin'; 2 | import { Typography, typography } from './typography'; 3 | 4 | /** 5 | * Helper function to generate class names and styles 6 | * for a given typography type. 7 | */ 8 | const generateTypographyClasses = ( 9 | type: 'title' | 'body', 10 | typography: Typography 11 | ) => { 12 | return Object.fromEntries( 13 | Object.entries(typography[type]).map(([key, value]) => [ 14 | `.${type}-${key}`, 15 | { 16 | fontFamily: [ 17 | typography.fontFamily[type], 18 | typography.fontFamily.fallback, 19 | ].join(', '), 20 | fontSize: value.fontSize, 21 | fontWeight: value.fontWeight, 22 | lineHeight: value.lineHeight, 23 | letterSpacing: value.letterSpacing, 24 | ...(type === 'title' && { textTransform: 'uppercase' }), 25 | }, 26 | ]) 27 | ); 28 | }; 29 | 30 | /** 31 | * Tailwind plugin that creates typography utility classes. 32 | * These utility classes bundle styles for font-family, font-size, font-weight, 33 | * line-height, and letter-spacing. 34 | * 35 | * @example 36 | * ```tsx 37 | *

Hello World

38 | *

Hello World

39 | * ``` 40 | */ 41 | export const addTypographyClassesPlugin = () => { 42 | return plugin(({ addComponents }) => { 43 | const titleClasses = generateTypographyClasses('title', typography); 44 | const bodyClasses = generateTypographyClasses('body', typography); 45 | 46 | addComponents({ ...titleClasses, ...bodyClasses }); 47 | }); 48 | }; 49 | -------------------------------------------------------------------------------- /content/xips/xip-82.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Support SPX6900' 3 | id: 82 4 | author: baproll (@user_baproll), jumbo (@Jumbo-Infinex) 5 | type: core-upgrade 6 | network: Solana, Ethereum, Base 7 | status: Implemented 8 | created: '2024-10-10' 9 | updated: '2024-10-29' 10 | --- 11 | # Proposal Summary 12 | 13 | This XIP proposes support of the $SPX6900 token within the Infinex ecosystem. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | $SPX6900 is a parody memecoin aiming to flip the entire stock market. 20 | 21 | Currently, $SPX6900 is not displayed on Infinex. 22 | 23 | ## Rationale 24 | 25 | Memecoins are one of the hottest narratives in crypto right now, and a variety of Infinex community members have requested support for them. Memecoins also have no utility, which means most users are simply holding them in a wallet. This means users will be more likely to deposit these assets into their Infinex Account due to lower opportunity costs. 26 | 27 | ## Technical Specification 28 | 29 | A list of the supported token, network, and token address can be found below. Infinex will add support for deposit and withdrawals for all of the listed tokens. 30 | 31 | {% table %} 32 | - **Token** 33 | - **Network** 34 | - **Token Address** 35 | --- 36 | - SPX6900 37 | - Mainnet 38 | - 0xe0f63a424a4439cbe457d80e4f4b51ad25b2c56c 39 | --- 40 | - SPX6900 41 | - Base 42 | - 0x50dA645f148798F68EF2d7dB7C1CB22A6819bb2C 43 | --- 44 | - SPX6900 45 | - Solana 46 | - J3NKxxXZcnNiMjKw9hYb2K4LUxgwB6t1FtPtQVsv3KFr 47 | --- 48 | {% /table %} 49 | 50 | # Copyright 51 | 52 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 53 | -------------------------------------------------------------------------------- /content/xips/xip-101.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Unichain Expansion 3 | id: 101 4 | author: kmao (@kmaox) 5 | type: integration-upgrade 6 | network: Unichain 7 | status: Implemented 8 | created: '2025-02-25' 9 | updated: '2025-03-03' 10 | --- 11 | # **Proposal Summary** 12 | 13 | This XIP proposes integrating Unichain Vaults, Wallets and Swidging. 14 | 15 | # **Specification** 16 | 17 | ## **Overview** 18 | 19 | Infinex will expand the existing Vault and Wallet infrastructure onto Unichain, to allow users to deposit, withdraw, and send funds on it. 20 | 21 | Infinex will also support all assets on Unichain, based on [**XIP-96**](https://proposals.infinex.xyz/xips/xip-96). Some assets may not be initially supported, however, the CWG will have the ability to add them based on community request. 22 | 23 | ## **Rationale** 24 | 25 | Infinex wants to continue the 2025 meta of quick chain intergrations following a rapid Berachain intergration. Unichain could potentially be one of the biggest chains this cycle and it is imperative Infinex users are able to interact with the chain. 26 | 27 | ## **Technical Specification** 28 | 29 | To allow for the deployment of the Infinex vault, wallet, and swidging on Unichain, Infinex would be required to deploy the same smart contracts and infrastructure that exists on other supported chains, specified in the O2 Cannon deployment. 30 | 31 | Infinex's existing list of Swidge providers already provides coverage for Unichain swidging, however additional providers may be added in the future, to help further improve speed and pricing. 32 | 33 | # **Copyright** 34 | 35 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 36 | -------------------------------------------------------------------------------- /content/xips/xip-65.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Bonsai Token 3 | id: 65 4 | author: gregcardo (@richardgreg) 5 | type: core-upgrade 6 | network: Polygon 7 | status: Draft 8 | created: '2024-07-22' 9 | updated: '2024-07-23' 10 | --- 11 | 12 | # Proposal Summary 13 | 14 | XIP-65 proposes support of the $BONSAI token within the Infinex ecosystem. 15 | 16 | # Specification 17 | 18 | ## Overview 19 | 20 | This proposal aims to integrate the $BONSAI token into the Infinex ecosystem, allowing users to utilize $BONSAI for craterun and future campaigns. 21 | Bonsai is a DN-404 token on Polygon, airdropped to active profiles across the Lens ecosystem. 22 | An experimental, mixed ERC-20 / ERC-721 implementation with native liquidity, fractionalization and unique art. 23 | 1 BONSAI NFT is linked to 100,000 $BONSAI Token! The $BONSAI token, being an essential part of the Lens Protocol ecosystem, provides unique opportunities for Infinex and Bonsai to synergize. 24 | 25 | ## Rationale 26 | Integrating $BONSAI will enrich the Infinex ecosystem by leveraging the token's existing community. This integration will encourage broader adoption and enhance user engagement. 27 | 28 | The founders of Bonsai have a strong presence in decentralized technologies and have secured substantial funding which includes investment from the Polygon Foundation, to ensure the token's development and sustainability. 29 | 30 | ## Technical Specification 31 | Bonsai is a DN-404 token on Polygon. Polygon deposits are already enabled so it's only a matter of adding the token to the list in the backend. 32 | 33 | Contract Address: `0x3d2bD0e15829AA5C362a4144FdF4A1112fa29B5c` 34 | 35 | ## Copyright Waiver 36 | This work is licensed under the Creative Commons Zero (CC0) license. 37 | -------------------------------------------------------------------------------- /content/xips/xip-38.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Clarify GP Distribution to NFT Holders 3 | id: 38 4 | author: kmao (@kmaox) 5 | type: community 6 | status: Implemented 7 | created: '2024-06-14' 8 | --- 9 | # Proposal Summary 10 | 11 | XIP-38 clarifies the method in which holders of Milady Maker, Pudgy Penguins, Mad Lads claim their GP airdrop. 12 | 13 | # Specification 14 | 15 | ## Overview 16 | 17 | [XIP-21](https://arc.net/l/quote/nguhowpd) states that there will be a snapshot of NFT holders taken after STW ends as the method for tracking a user's airdrop associated with the NFTs. Instead, this proposal proposes the method of "linking" the GP to the various NFT ids, and then marking them as claimed, once a user claims them. 18 | 19 | This means a user's GP airdrop will no longer be associated to a user's address, and instead their NFT id, which means if you transfer your NFT to a new wallet, you can claim your airdrop from the new wallet. This means, when purchasing new NFTs, you may also purchase NFTs which have a GP airdrop associated with them. 20 | 21 | ## Rationale 22 | 23 | The prior snapshot method of distributing GP would not ensure that the allocated GP per NFT collection would be claimed, as users may not have deposited their funds during STW. This new proposed method ensures that all GP may be claimed by STW depositors. 24 | 25 | ## Technical Specification 26 | 27 | Infinex will need to track if a NFT id has been claimed, instead of tracking the snapshotted addresses. The user interface to claim your GP will be the same, which will require a user to connect their wallet to the Infinex Account, and sign a message. 28 | 29 | # Copyright 30 | 31 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 32 | -------------------------------------------------------------------------------- /content/xips/xip-78.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Blast Expansion 3 | id: 78 4 | author: kmao (@kmaox), Yamen (@yaminfinex) 5 | type: integration-upgrade 6 | network: Blast 7 | status: Implemented 8 | created: '2024-09-09' 9 | updated: '2024-10-29' 10 | --- 11 | # **Proposal Summary** 12 | 13 | This XIP proposes integrating the Blast chain. 14 | 15 | # **Specification** 16 | 17 | ## **Overview** 18 | 19 | Infinex will deploy the AccountFactory contract onto the Blast network, thus enabling allowing users on Blast to deposit and withdraw supported tokens on Infinex. The only supported Blast token initially will be USDB. 20 | 21 | ## **Rationale** 22 | 23 | Six major chains were supported at the launch of Infinex: Ethereum, Arbitrum, Optimism, Base, Polygon POS, and Solana. Integrating a new chain has several technical constraints. Blast was chosen because it satisfies almost all of these constraints. In addition, its focus on the gamified crypto experience aligns well with Infinex’s latest campaign, Bullrun. Bullrun’s contract architecture will be deployed to Blast, which makes expanding Infinex Accounts to Blast a logical second step. 24 | 25 | ## **Technical Specification** 26 | 27 | To allow for deployment of infinex accounts on the Blast network, this would require the same deployment of smart contracts as the other supported chains, as specified in the O2 Cannon deployment.  28 | 29 | As there is no official USDC on Blast, certain platform features will be unavailable on Blast: 30 | 31 | - No bridging using CCTP 32 | 33 | All the supported assets on Blast are: 34 | 35 | USDB: 0x4300000000000000000000000000000000000003 36 | 37 | # **Copyright** 38 | 39 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 40 | -------------------------------------------------------------------------------- /templates/ir-template.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: IR Template 3 | ir: 9999 4 | author: kmao (@kmaox) 5 | status: Draft 6 | --- 7 | # Referendum Summary 8 | 9 | `This section provides a short, less than 500-word summary of the referendum. The Referendum Summary should briefly cover what will happen if the proposal passes, why it should pass, and how it will be implemented. The overview should be non-technical and accessible to a casual community member.` 10 | 11 | # Specification 12 | 13 | `The specification should describe the syntax and semantics of any new feature. There are three suggested sections:` 14 | 15 | 1. `Overview` 16 | 1. `Rationale` 17 | 1. `Technical Specification` 18 | 19 | ## Overview 20 | 21 | `This is a high-level overview of how the IR will solve the problem. The overview should clearly describe how the new feature will be implemented.` 22 | 23 | ## Rationale 24 | 25 | `This is where you explain the reasoning behind how and why you propose to solve the problem. Why did you propose to implement the change in this way, what were the considerations and trade-offs? The rationale fleshes out what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work. The rationale may also provide evidence of consensus within the community and should discuss important objections or concerns raised during discussion.` 26 | 27 | ## Technical Specification 28 | 29 | `The technical specification should outline the public API of the changes proposed. That is, changes to any of the interfaces Infinex currently exposes or the creations of new ones.` 30 | 31 | # Copyright 32 | 33 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 34 | -------------------------------------------------------------------------------- /content/xips/xip-97.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Berachain Expansion 3 | id: 97 4 | author: kmao 5 | type: integration-upgrade 6 | network: Berachain 7 | status: Implemented 8 | created: '2025-01-28' 9 | updated: '2025-02-13' 10 | --- 11 | # Proposal Summary 12 | 13 | This XIP proposes integrating Berachain Vaults, Wallets and Swidging. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Infinex will expand the existing Vault and Wallet infrastructure onto Berachain, to allow users to deposit, withdraw, and send funds on Berachain. 20 | 21 | Infinex will also support all assets on Berachain, based on [XIP-96](https://proposals.infinex.xyz/xips/xip-96). Some assets may not be initially supported, however, the CWG will have the ability to add them based on community request. 22 | 23 | ## Rationale 24 | 25 | Berachain is one of the chains launching in 2025 with the most hype associated with it. Infinex has already had conversations and prior partnerships with Berachain, and thus believes a deployment on Berachain will help further the working relationship, as well as expand Infinex's existing userbase and TVL to Berachain native users. 26 | 27 | ## Technical Specification 28 | 29 | To allow for the deployment of the Infinex vault, wallet, and swidging on Berachain, Infinex would be required to deploy the same smart contracts and infrastructure that exists on other supported chains, specified in the O2 Cannon deployment. 30 | 31 | In order to support swidging from/to Berachain, Infinex will also need to support new Swidge providers. Further details on which specific Swidge providers will be integrated will be detailed in a future RC. 32 | 33 | # Copyright 34 | 35 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 36 | -------------------------------------------------------------------------------- /content/xips/xip-90.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Stonks Token 3 | id: 90 4 | author: Pedro Bergamini (@pedrobergamini) 5 | type: core-upgrade 6 | network: Solana 7 | status: Superseded 8 | supersededby: XIP-89 9 | created: '2024-11-24' 10 | updated: '2024-12-02' 11 | --- 12 | 13 | # Proposal Summary 14 | 15 | XIP-90 proposes support of the $STNK token within the Infinex ecosystem. 16 | 17 | # Specification 18 | 19 | ## Overview 20 | 21 | This proposal aims to integrate the $STNK token into the Infinex ecosystem, allowing users to utilize $STNK for future campaigns. 22 | Stonks is considered to be the first memecoin on Solana, a blockchain popular for its strong meme community due to its monolithic architecture leveraging a single global state, while supporting a high transaction throughput. 23 | The $STNK token has started to see increased traction recently and it is expected to potentially continue growing in popularity, making it a valuable opportunity for Infinex to be a first-mover by integrating the token. 24 | 25 | 26 | ## Rationale 27 | Integrating $STNK will enrich the Infinex ecosystem by leveraging the token's existing community. This integration will encourage broader adoption and enhance user engagement. 28 | 29 | As one of the first memecoins on Solana and the most recognizable finance meme in history, onboarding $STNK is an opportunity to attract a very active audience to the Infinex ecosystem. 30 | 31 | ## Technical Specification 32 | Stonks is an SPL20 token on Solana. Solana deposits are already enabled so it's only a matter of adding the token to the list in the backend. 33 | 34 | Contract Address: `43VWkd99HjqkhFTZbWBpMpRhjG469nWa7x7uEsgSH7We` 35 | 36 | ## Copyright Waiver 37 | This work is licensed under the Creative Commons Zero (CC0) license. 38 | -------------------------------------------------------------------------------- /content/xips/xip-68.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Dinero & Blaze Tokens 3 | id: 68 4 | author: kmao (@kmaox) 5 | type: core-upgrade 6 | network: Ethereum, Solana 7 | status: Implemented 8 | created: '2024-08-14' 9 | updated: '2024-08-27' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-68 enables support for the Dinero and Blaze Tokens. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Infinex will need to update the UI to effectively reflect Dinero and Blaze deposits and withdrawals, as well as the current market price of the asset. The value of these assets will be denominated in USD and determined by a 3rd-party market price feed. 20 | 21 | ## Rationale 22 | 23 | Craterun's prize pool included both BTRFLY and Blaze rewards. After Craterun ended, BTRFLY underwent a migration to DINERO, at the ratio of 1:2000, which meant the 35 BTRFLY prize was changed to 70,000 DINERO. 24 | 25 | These assets are required to be supported by Infinex to ensure the Craterun winners are able to interact with their prizes. 26 | 27 | ## Technical Specification 28 | 29 | Infinex will add support for deposits and withdrawals for tokens on following networks below. 30 | 31 | {% table %} 32 | - **Coin** 33 | - **Network** 34 | - **Token Address** 35 | --- 36 | - DINERO 37 | - Ethereum Mainnet 38 | - 0x6df0e641fc9847c0c6fde39be6253045440c14d3 39 | --- 40 | - BLZE 41 | - Solana 42 | - BLZEEuZUBVqFhj8adcCFPJvPVCiCyVmh3hkJMrU8KuJA 43 | {% /table %} 44 | 45 | The Infinex account currently does not block deposits from any Ethereum or Solana Token, which means to support these assets, Infinex will simply just need to upgrade the backend infrastructure to track them. 46 | 47 | # Copyright 48 | 49 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 50 | -------------------------------------------------------------------------------- /content/xips/xip-58.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Wormhole Token 3 | id: 58 4 | author: Kvasir (@0xKvasir) 5 | type: core-upgrade 6 | network: Solana, Ethereum, Base, Arbitrum One 7 | status: Implemented 8 | created: '2024-07-10' 9 | updated: '2024-07-24' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-58 proposes enabling support for Wormhole (W) token. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Infinex launched with an integration for Wormhole enabling seamless multi-chain support. It would be great to add support for the Wormhole (W) token on the following chains: 20 | 21 | - Solana 22 | - Ethereum 23 | - Base 24 | - Arbitrum One 25 | 26 | ## Rationale 27 | 28 | The Wormhole token is supported by major exchanges and available on both EVM chains and Solana. For future usage it might be good to have staking support in the interface, but for the short term just support for additional tokens. 29 | 30 | ## Technical Specification 31 | 32 | Infinex already has support for EVM & Solana tokens, so it just needs to update the backend to support the new token. 33 | 34 | ### Token contracts 35 | 36 | - Solana [85VBFQZC9TZkfaptBWjvUw7YbZjy52A6mjtPGjstQAmQ] 37 | - Ethereum [0xb0ffa8000886e57f86dd5264b9582b2ad87b2b91] 38 | - Base [0xb0ffa8000886e57f86dd5264b9582b2ad87b2b91] 39 | - Arbitrum One [0xb0ffa8000886e57f86dd5264b9582b2ad87b2b91] 40 | 41 | ### Token Format 42 | 43 | Native ERC20 and SPL (using Wormhole’s Native Token Transfer framework) 44 | Token symbol: W 45 | Max supply: 10,000,000,000 46 | Initial circulating supply: 1,800,000,000 47 | 48 | [Additional information](https://wormhole.com/ecosystem/w-token) 49 | 50 | ## Test Cases 51 | 52 | # Copyright 53 | 54 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 55 | -------------------------------------------------------------------------------- /content/rcs/rc-9.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Close STW and Prepare Craterun 3 | id: 9 4 | wg: CWG 5 | author: jaynex (@0xjaynex) 6 | status: Implemented 7 | created: '2024-06-19' 8 | updated: '2024-06-19' 9 | implemented: '2024-06-20' 10 | --- 11 | ### Overview 12 | 13 | This release supports a variety of platform features: 14 | 15 | - Claim any unclaimed GP for a user (now that STW has finished) 16 | - Enable non-USD assets as per [XIP-36](https://proposals.infinex.xyz/xips/xip-36), [XIP-42](https://proposals.infinex.xyz/xips/xip-42) and any other upcoming assetse 17 | - Add language to login pages that support changes to terms of use for existing users 18 | - Add transaction monitoring as per [XIP-41](https://proposals.infinex.xyz/xips/xip-41) 19 | 20 | It also includes a variety of UI fixes and tweaks in support of closing out Speedrun the Waitlist and preparing to launch Craterun. 21 | 22 | ### Outcome 23 | 24 | Upgrade the platform to close out STW, prepare for Craterun and support new assets. 25 | 26 | ### Proposed Changes 27 | 28 | ##### **Platform** 29 | 30 | The following changes will be made to the platform: 31 | 32 | - Users with unclaimed GP points will have points automatically claimed for them in their account 33 | - Asset prices in USD will be sourced and saved in the system to support non-USD assets 34 | - A central supported assets list will be maintained 35 | - Users last login time will be captured, in order to infer the last set of terms of use they accepted 36 | - Users balances will be shown in USD-equivalent values using the external price feed 37 | - Add address screening of deposit addresses, withdrawal addresses and recovery keys as per XIP-41 38 | 39 | # Copyright 40 | 41 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 42 | -------------------------------------------------------------------------------- /src/components/UI.tsx: -------------------------------------------------------------------------------- 1 | import Link from 'next/link'; 2 | 3 | import { ArrowLeftIcon, GitHubOutlineIcon } from './Icons'; 4 | 5 | export function PageContainer({ children }: { children: React.ReactNode }) { 6 | return ( 7 |
8 |
{children}
9 | 19 |
20 | ); 21 | } 22 | 23 | export function PageTitle({ children }: { children: React.ReactNode }) { 24 | return

{children}

; 25 | } 26 | 27 | export function PageIntro({ children }: { children: React.ReactNode }) { 28 | return ( 29 |

{children}

30 | ); 31 | } 32 | 33 | export function Separator() { 34 | return
; 35 | } 36 | 37 | export function Back({ 38 | children, 39 | href, 40 | }: { 41 | children?: React.ReactNode; 42 | href: string; 43 | }) { 44 | return ( 45 | 49 | 50 | 51 | {children} 52 | 53 | 54 | ); 55 | } 56 | -------------------------------------------------------------------------------- /content/xips/xip-66.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support JUPSOL & INF 3 | id: 66 4 | author: ablaiser, kmao (@kmaox) 5 | type: integration-upgrade 6 | network: Solana 7 | status: Implemented 8 | created: '2024-07-31' 9 | updated: '2024-08-14' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-66 proposes enabling support for Jupiter Staked SOL and Sanctum Infinity. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | This proposal aims to integrate the JUPSOL and Infinity LSTs into the infinex ecosystem, allowing users to utilize staking APY while holding their funds in Infinex for future campaigns. 20 | 21 | JUPSOL is a Liquid Staking Token (LST) on Solana and has over 2 million SOL staked, second only to JITOSOL. Infinity is a pool of LSTs on Solana created by Sanctum and has over 1.5 million SOL staked. 22 | 23 | ## Rationale 24 | 25 | Integrating JUPSOL and INF will enrich the Infinex ecosystem by leveraging the liquidity of sol staked with these LSTs. Users will feel more encouraged to move their Solana assets to infinex without promise of future campaigns because they are still earning APY. This integration will encourage broader adoption and enhance solana engagement. 26 | 27 | ## Technical Specification 28 | 29 | {% table %} 30 | - Coin 31 | - Network 32 | - Token Address 33 | --- 34 | - JUPSOL 35 | - Solana 36 | - jupSoLaHXQiZZTSfEWMTRRgpnyFm8f6sZdosWBjx93v 37 | --- 38 | - INF 39 | - Solana 40 | - 5oVNBeEEQvYi1cX3ir8Dx5n1P7pdxydbGF2X4TxVusJm 41 | {% /table %} 42 | 43 | The Infinex account currently does not block deposits from any Solana tokens, which means to support JUPSOL & INF deposits and withdrawals, Infinex will simply just need to upgrade the backend infrastructure to track them. 44 | 45 | # Copyright 46 | 47 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 48 | -------------------------------------------------------------------------------- /content/xips/xip-79.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Re-allocate Infinex Early Supporters GP 3 | id: 79 4 | author: kmao (@kmaox) 5 | type: integration-upgrade 6 | network: Base 7 | status: Implemented 8 | created: '2024-09-10' 9 | updated: '2024-09-18' 10 | --- 11 | # **Proposal Summary** 12 | 13 | This XIP proposes reallocating the GP assigned to the "Infinex Early Supporters Airdrop" to the reserve fund. 14 | 15 | # **Specification** 16 | 17 | ## **Overview** 18 | 19 | In 2023, the Infinex Core Working Group distributed product research surveys via the Infinex waitlist, and approximately five thousands survey responses were returned. 10,000,000 GP was allocated to these participants. 20 | 21 | This proposal aims to re-distribute this GP to the Infinex Retirement Fund. Infinex will first allow users who believe they have submitted relevant responses to reach out and secure their prior GP allocation. After a month, Infinex will close this program and return the remaining GP to the Retirement Fund. Each user who has a valid response will recieve 10,000 GP. 22 | 23 | ## **Rationale** 24 | 25 | After further analysis of the survey responses that were given, over 99% of the responses were all single sentence/word responses that did not make sense. I do not believe that the obvious attempt and sybilling an airdrop should be rewarded, and the 10,000,000 GP allocated can be used for better purposes. 26 | 27 | ## **Technical Specification** 28 | 29 | When GP is converted to an ERC-20 token, Infinex will mint all the GP to a platform address to distribute to users via the GP Migration Tool. The GP that was allocated to the Infinex Early Supporters Airdrop will be transferred to the Infinex Reserve Fund instead. 30 | 31 | # **Copyright** 32 | 33 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 34 | -------------------------------------------------------------------------------- /content/rcs/rc-8.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Ship Interim Withdrawals 3 | id: 8 4 | wg: CWG 5 | author: jaynex (@0xjaynex) 6 | status: Implemented 7 | created: "2024-06-14" 8 | implemented: "2024-06-14" 9 | --- 10 | ### Overview 11 | 12 | As decided in [XIP-35](https://proposals.infinex.xyz/xips/xip-35), the CWG is going to update the Infinex App to enable interim withdrawals so that Users who want to withdraw their funds at the end of Speedrun The Waitlist are able to. 13 | 14 | Additional UI to show information about the upcoming Craterun campaign (per [XIP-34](https://proposals.infinex.xyz/xips/xip-34)) has also been prepared, along with warnings for users who withdraw that they will lose their Speedrun Bonus for the Craterun Campaign. 15 | 16 | ### Outcome 17 | 18 | Upgrade the platform to enable Interim Withdrawals and announce initial details for the Craterun Campaign. 19 | 20 | ### Proposed Changes 21 | 22 | ##### **Platform** 23 | 24 | Added frontend and backend functionality to enable withdrawals, which use the onchain recovery methods in combination with the User's passkey to send the entire balance of a single asset to the funds recovery address (as already set by the User before depositing) on the same chain. 25 | 26 | > For example, a User can "withdraw" the entire USDC balance on Base in their Infinex Account to their EVM Funds Recovery Address on Base. 27 | 28 | Added Craterun UI to the Infinex App: 29 | 30 | - Announcement on the Dashboard 31 | - New Craterun Section with information about the campaign 32 | - Display the User's Speedrun Bonus for Craterun in various parts of the UI 33 | - Warn Users who are about to withdraw funds that doing so will forfeit their Speedrun Bonus for Craterun 34 | 35 | # Copyright 36 | 37 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 38 | -------------------------------------------------------------------------------- /content/xips/xip-57.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Pyth Token 3 | id: 57 4 | author: kmao (@kmaox), Egor (@egorsidelska) 5 | type: core-upgrade 6 | network: Solana 7 | status: Implemented 8 | created: '2024-07-04' 9 | updated: '2024-07-18' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-57 proposes enabling support for the Pyth Network token. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | The Infinex Treasury is aiming to distribute the users who opened crates in the first 24 hours of Craterun Pyth tokens. In order for users to withdraw their distributed PYTH, I propose that Infinex enables support of PYTH tokens. 20 | 21 | Infinex will need to update the UI to effectively reflect Pyth deposits and withdrawals, as well as the current market price of the asset. The value of Pyth will be denominated in USD and determined by a 3rd-party market price feed and will also be counted as TVL for the upcoming [**Craterun**](https://proposals.infinex.xyz/xips/xip-34) campaign. 22 | 23 | ## Rationale 24 | 25 | Infinex's grand vision is to become the UX layer for all of Defi, which makes it important for the platform to support a variety of tokens. Infinex has already intergrated Pyth as a partner, and has used [Pyth Entropy](https://docs.pyth.network/entropy) for the recent [Craterun Campaign](https://proposals.infinex.xyz/xips/xip-34). 26 | 27 | ## Technical Specification 28 | 29 | Infinex will add PYTH on the Solana network. The token address is HZ1JovNiVvGrGNiiYvEozEVgZ58xaU3RKwX8eACQBCt3 30 | 31 | The Infinex account currently does not block deposits from all Solana coins, which means to support SOL deposits, Infinex will simply just need to upgrade the backend infrastructure to track PYTH deposits. 32 | 33 | # Copyright 34 | 35 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 36 | -------------------------------------------------------------------------------- /content/xips/xip-29.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Enable USDe Deposits and GP Staking 3 | id: 29 4 | author: kmao (@kmaox), Kain (@kaiynne) 5 | type: core-upgrade 6 | network: Ethereum, Arbitrum 7 | status: Implemented 8 | created: '2024-05-27' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-29 proposes enabling [USDe](https://www.coingecko.com/en/coins/ethena-usde) deposits and adding USDe to the list of assets that earn GP during Speedrun the Waitlist. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Add USDe as the second asset enabled for deposits. USDe deposited will earn USDe rewards claimable by each Infinex Account that deposits and holds USDe, on a rolling weekly basis. 19 | 20 | Users that deposit USDe are also eligible to earn GP during the STW campaign. 21 | 22 | ## Rationale 23 | 24 | Expanding support for more stablecoins beyond USDC will allow Infinex TVL to continue to grow past the $100m USD already deposited across over 10,000 accounts. USDe was chosen because it is the fastest growing stablecoin with almost $3b in circulation and because staked USDe currently provides over 35% APY for holders. The ability to earn from Ethena while also earning Infinex GP will drive significant TVL growth in the Speedrun the Waitlist campaign. 25 | 26 | ## Technical Specification 27 | 28 | The Infinex account currently accepts deposits from all ERC20 assets. This means the technical implementation required to enable USDe is: 29 | 30 | 1. Upgrade the Infinex backend infrastructure to track USDe deposits, and stream GP to deposited USDe. 31 | 1. Claimable in USDe from a distribution contract each week to Infinex accounts that hold USDe. 32 | 33 | Only USDe deposited on Ethereum or Arbitrum networks will be recognised. 34 | 35 | # Copyright 36 | 37 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 38 | -------------------------------------------------------------------------------- /src/app/irs/page.tsx: -------------------------------------------------------------------------------- 1 | import { Status, Entry } from '@/components/Entries'; 2 | import { Header } from '@/components/Header'; 3 | import { PageContainer, PageIntro, PageTitle } from '@/components/UI'; 4 | import { reader } from '@/lib/reader'; 5 | import keystatic from '@/../keystatic.config'; 6 | import { number } from '@/lib/util'; 7 | 8 | const statuses = keystatic.collections.irs.schema.status.options; 9 | 10 | export default async function IRs() { 11 | const entries = await reader.collections.irs.all(); 12 | entries.sort((a, b) => (a.entry.id || 0) - (b.entry.id || 0)); 13 | const byStatus = statuses.map((status) => { 14 | const matches = entries.filter((i) => i?.entry.status === status.value); 15 | return matches.length ? { status, entries: matches } : null; 16 | }); 17 | 18 | return ( 19 | 20 |
21 | Infinex Referendums 22 | 23 | IRs are the mechanism for how meta-governance changes are made to the 24 | Infinex Protocol. 25 | 26 | 27 | {byStatus.map((i) => { 28 | if (!i) return null; 29 | const { status, entries } = i; 30 | return ( 31 |
32 | 33 |
34 | {entries.map((e) => ( 35 | 41 | ))} 42 |
43 |
44 | ); 45 | })} 46 | 47 | ); 48 | } 49 | -------------------------------------------------------------------------------- /src/components/Entries.tsx: -------------------------------------------------------------------------------- 1 | import { getStatusColors, splitAuthors } from '@/lib/util'; 2 | 3 | export function Status({ 4 | status, 5 | count, 6 | }: { 7 | status: { label: string; value: string }; 8 | count: number; 9 | }) { 10 | const colors = getStatusColors(status.value); 11 | return ( 12 |

13 |
{status.label}
14 |
({count})
15 |

16 | ); 17 | } 18 | 19 | function Authors({ authors }: { authors: string }) { 20 | const list = splitAuthors(authors); 21 | return list.map((author, i) => { 22 | return ( 23 | 24 | {author.name} 25 | {i < list.length - 1 ? ', ' : ''} 26 | 27 | ); 28 | }); 29 | } 30 | 31 | export function Entry({ 32 | data, 33 | id, 34 | path, 35 | }: { 36 | data: { 37 | slug: string; 38 | entry: { title: string; author: string; status: string }; 39 | }; 40 | id: string; 41 | path: string; 42 | }) { 43 | const colors = getStatusColors(data.entry.status); 44 | return ( 45 | 46 |
47 | 50 | {id} 51 | 52 | {data.entry.title}{' '} 53 | {data.entry.author ? ( 54 | 55 | by 56 | 57 | ) : null} 58 |
59 | 60 | ); 61 | } 62 | -------------------------------------------------------------------------------- /src/app/rcs/page.tsx: -------------------------------------------------------------------------------- 1 | import { Status, Entry } from '@/components/Entries'; 2 | import { Header } from '@/components/Header'; 3 | import { PageContainer, PageIntro, PageTitle } from '@/components/UI'; 4 | import { reader } from '@/lib/reader'; 5 | import keystatic from '@/../keystatic.config'; 6 | import { number } from '@/lib/util'; 7 | 8 | const statuses = keystatic.collections.rcs.schema.status.options; 9 | 10 | export default async function Page() { 11 | const entries = await reader.collections.rcs.all(); 12 | entries.sort((a, b) => (a.entry.id || 0) - (b.entry.id || 0)); 13 | const byStatus = statuses.map((status) => { 14 | const matches = entries.filter((i) => i?.entry.status === status.value); 15 | return matches.length ? { status, entries: matches } : null; 16 | }); 17 | 18 | return ( 19 | 20 |
21 | Release Candidates 22 | 23 | RCs are an alternative method in which only approved working groups are 24 | able to bundle proposed changes for approval by the council. 25 | 26 | 27 | {byStatus.map((i) => { 28 | if (!i) return null; 29 | const { status, entries } = i; 30 | return ( 31 |
32 | 33 |
34 | {entries.map((e) => ( 35 | 41 | ))} 42 |
43 |
44 | ); 45 | })} 46 | 47 | ); 48 | } 49 | -------------------------------------------------------------------------------- /templates/xip-template.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Xip Template 3 | id: 9999 4 | type: '' 5 | network: '' 6 | status: Draft 7 | --- 8 | # Proposal Summary 9 | 10 | `This section provides a short, less than 500-word summary of the proposal. The Proposal Summary should briefly cover what will happen if the proposal passes, why it should pass, and how it will be implemented. The overview should be non-technical and accessible to a casual community member.` 11 | 12 | # Specification 13 | 14 | `The specification should describe the syntax and semantics of any new feature. There are four sections:` 15 | 16 | 1. `Overview` 17 | 1. `Rationale` 18 | 1. `Technical Specification` 19 | 1. `Test Cases` 20 | 21 | ## Overview 22 | 23 | `This is a high-level overview of how the XIP will solve the problem. The overview should clearly describe how the new feature will be implemented.` 24 | 25 | ## Rationale 26 | 27 | `This is where you explain the reasoning behind how and why you propose to solve the problem. Why did you propose to implement the change in this way, what were the considerations and trade-offs? The rationale fleshes out what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work. The rationale may also provide evidence of consensus within the community and should discuss important objections or concerns raised during discussion.` 28 | 29 | ## Technical Specification 30 | 31 | `The technical specification should outline the public API of the changes proposed. That is, changes to any of the interfaces Infinex currently exposes or the creations of new ones.` 32 | 33 | ## Test Cases 34 | 35 | `Test cases for an implementation are mandatory for XIPs but can be included with the implementation.` 36 | 37 | # Copyright 38 | 39 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 40 | -------------------------------------------------------------------------------- /content/xips/xip-11.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Update to Alpha Selection 3 | id: 11 4 | author: kmao (@kmaox) 5 | type: integration-upgrade 6 | network: Ethereum & Base 7 | status: Superseded 8 | supersededby: XIP-22 9 | created: '2023-12-21' 10 | updated: '2024-07-18' 11 | --- 12 | # Proposal Summary 13 | 14 | This XIP proposes a change to the selection criteria for the Infinex Alpha Launch, specifically for the testnet users. 15 | 16 | # Specification 17 | 18 | ## Overview 19 | 20 | The initial Testnet deployment was burdened by significant bugs due to Synthetix testnet contract changes. This meant that the Infinex frontend was broken which affected user participation in the trading competition. Funding rates were also affected due to the small user base, which meant that if the majority of users take the same side in a pair, it was always more profitable to take the opposite side, regardless of market action, in order to farm funding. 21 | 22 | Based on the above factors, as well as community feedback, the criteria for selection in the Alpha from the Testnet userbase has been re-evaluated. 23 | 24 | ## Rationale 25 | 26 | [XIP-5](https://proposals.infinex.xyz/xips/xip-5-skinny-alpha-launch) stated that the top 5 traders from Infinex would receive access to the Alpha Launch. However, this no longer correctly incentivises users effectively due to the technical constraints of trading on testnet. 27 | 28 | ## Technical Specification 29 | 30 | This XIP proposes that the selection criteria of the 5 testnet users granted access to the Infinex Alpha be changed to: 31 | 32 | - 2 performance-based, ranked by highest PNL 33 | - 3 feedback-based, decided at the discretion of the CC seat. 34 | 35 | Furthermore, profits or losses from the funding rate will not be counted towards a trader's PNL. 36 | 37 | # Copyright 38 | 39 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 40 | -------------------------------------------------------------------------------- /content/xips/xip-89.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Broad Asset Support 3 | id: 89 4 | author: kmao (@kmaox) 5 | type: core-upgrade 6 | network: Base, Optimism, Ethereum, Solana, Arbitrum, Polygon, Blast 7 | status: Approved 8 | created: '2024-11-07' 9 | updated: '2024-11-25' 10 | --- 11 | # **Proposal Summary** 12 | 13 | This XIP enables broad support for tokens. 14 | 15 | # **Specification** 16 | 17 | ## **Overview** 18 | 19 | The Infinex Platform should be upgraded to support a broader range of assets. Supporting an asset involves the following things: 20 | 21 | - Reflecting the asset in the user's balance and wallet. 22 | - Reflecting the price of the asset to the user. 23 | - Accepting withdrawals and deposits of the asset. 24 | 25 | While the CWG implements this, they may add additional assets that are listed on Coingecko. These assets should not require approval via XIP or release candidate. For any new assets the CWG wants to add, they may just add it - assuming the asset is listed on Coingecko. 26 | ## **Rationale** 27 | 28 | Prior to this proposal, Infinex has operated on the basis that each new supported token requires specific approval. In the current state, Infinex believes that they are ready to update their framework to a more broad one, that allows more assets to be added automatically. 29 | 30 | ## **Technical Specification** 31 | 32 | Enabling broad support for more assets will involve the use of the [Coingecko API]([Coins List (ID Map)](https://docs.coingecko.com/reference/coins-list) ). Infinex will enable support for the top 2000 tokens by Market Cap, assuming the token is on a supported network. The list of supported tokens will expand daily, and new tokens that enter the top 2000 will also be supported, whilst assets that drop below top 2000 ranking will also remain supported. 33 | 34 | # **Copyright** 35 | 36 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 37 | -------------------------------------------------------------------------------- /content/tas/ta-5.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Airdrop ENA to Early Ethena Supporters 3 | id: 5 4 | author: Egor (@egorsidelska), kmao (@kmaox) 5 | status: Implemented 6 | created: '2024-10-29' 7 | --- 8 | # **Summary** 9 | 10 | Treasury has approved to airdrop 233,419 ENA to 484 Infinex Accounts that have a "OG Real Yield Maxi" badge. 11 | 12 | # **Overview** 13 | 14 | Infinex wants to reward early community members who are engaged, active and paying attention. By airdropping ENA to users who have held USDe in Infinex prior to the Ethena Sats Swap Campaign, Infinex aims to continue rewarding Patrons that respond quickly to future campaigns and product features. 15 | 16 | # **Rationale** 17 | 18 | ENA was one of Infinex's first partners and has continued to be a staple asset in the Infinex ecosystem. Our two teams are very closely aligned and Ethena has given Infinex unique incentives for Infinex users to swap and hold USDe in platform. 19 | 20 | By aligning Infinex Patrons with ENA holders and the broader Ethena community, we build a stronger bridge between our platforms, teams and community. Infinex aims to continue supporting the Ethena ecosystem and encouraging early adopters of new product features with additional rewards. 21 | 22 | # **Outcome** 23 | 24 | The ENA will be distributed across all eligible accounts equally. ENA will show as an asset under the Wallet tab in your Infinex account and be represented onchain. 25 | 26 | # **Specification** 27 | 28 | Airdropped ENA will be liquid, however, requires a user to claim via the Infinex Platform. Claims will be open for 30 days from implementation and any unclaimed ENA will be returned to the Treasury. 29 | 30 | The action of claiming will be the user calling claim via their Infinex Account. Once claimed, ENA will show up in their account assets. 31 | 32 | Accounts which do not have a EVM recovery address will need to create one and follow the account security steps before they can withdraw. 33 | -------------------------------------------------------------------------------- /src/app/wgcs/page.tsx: -------------------------------------------------------------------------------- 1 | import { Status, Entry } from '@/components/Entries'; 2 | import { Header } from '@/components/Header'; 3 | import { PageContainer, PageIntro, PageTitle } from '@/components/UI'; 4 | import { reader } from '@/lib/reader'; 5 | import keystatic from '@/../keystatic.config'; 6 | import { number } from '@/lib/util'; 7 | 8 | const statuses = keystatic.collections.wgcs.schema.status.options; 9 | 10 | export default async function Page() { 11 | const entries = await reader.collections.wgcs.all(); 12 | entries.sort((a, b) => (a.entry.id || 0) - (b.entry.id || 0)); 13 | const byStatus = statuses.map((status) => { 14 | const matches = entries.filter((i) => i?.entry.status === status.value); 15 | return matches.length ? { status, entries: matches } : null; 16 | }); 17 | 18 | return ( 19 | 20 |
21 | Working Group Charters 22 | 23 | WGCs are a documentation type that outlines the establishment of a 24 | working group, defines its outcomes, and aligns expectations between the 25 | working group and the council. 26 | 27 | 28 | {byStatus.map((i) => { 29 | if (!i) return null; 30 | const { status, entries } = i; 31 | return ( 32 |
33 | 34 |
35 | {entries.map((e) => ( 36 | 42 | ))} 43 |
44 |
45 | ); 46 | })} 47 | 48 | ); 49 | } 50 | -------------------------------------------------------------------------------- /src/app/tas/page.tsx: -------------------------------------------------------------------------------- 1 | import { Status, Entry } from '@/components/Entries'; 2 | import { Header } from '@/components/Header'; 3 | import { PageContainer, PageIntro, PageTitle } from '@/components/UI'; 4 | import { reader } from '@/lib/reader'; 5 | import keystatic from '@/../keystatic.config'; 6 | import { number } from '@/lib/util'; 7 | 8 | const statuses = keystatic.collections.tas.schema.status.options; 9 | 10 | export default async function TASs() { 11 | const entries = await reader.collections.tas.all(); 12 | entries.sort((a, b) => (a.entry.id || 0) - (b.entry.id || 0)); 13 | const byStatus = statuses.map((status) => { 14 | const matches = entries.filter((i) => i?.entry.status === status.value); 15 | return matches.length ? { status, entries: matches } : null; 16 | }); 17 | 18 | return ( 19 | 20 |
21 | Treasury Annoucements 22 | 23 | A Treasury Annoucement (TA) is a document written by the Treasury Seat, 24 | which outlines a proposed initiative from the Infinex Treasury. TAs do 25 | not require to be voted on by the council. 26 | 27 | 28 | {byStatus.map((i) => { 29 | if (!i) return null; 30 | const { status, entries } = i; 31 | return ( 32 |
33 | 34 |
35 | {entries.map((e) => ( 36 | 42 | ))} 43 |
44 |
45 | ); 46 | })} 47 | 48 | ); 49 | } 50 | -------------------------------------------------------------------------------- /content/xips/xip-70.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Helius Staked Solana 3 | id: 70 4 | author: mert (@mertimus), Emma 5 | type: core-upgrade 6 | network: Solana 7 | status: Implemented 8 | created: '2024-08-22' 9 | updated: '2024-08-30' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-70 proposes enabling support for Helius Staked SOL, hSOL. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Infinex supports a variety of Solana LSTs. hSOL is another popular LST that has been requested by various community members and will help grow Infinex's TVL further. 20 | 21 | Infinex will need to update the UI to effectively reflect hSOL deposits and withdrawals, as well as the current market price of the asset. 22 | 23 | ## Rationale 24 | 25 | hSOL is broadly considered one of the leading protocols in the Solana ecosystem. hSOL currently has an APY of 9.02% and is initially pegged at a 1:1 ratio with SOL. The value of this token increases over time as staking rewards accumulate. By holding hSOL, users automatically earn staking rewards, enhancing their investment without any active management.  26 | 27 | hSOL is powered by the SPL stake pool program, one of the safest of its kind globally. This program has undergone nine rigorous audits and is trusted by the largest stake pools on Solana. 28 | 29 | Over the past two years, it has securely managed more than $1 billion of staked SOL without an incident. 30 | 31 | Also the CEO is bald and super angry on twitter. 32 | 33 | ## Technical Specification 34 | 35 | Infinex will add HSOL on the Solana network. The token address is he1iusmfkpAdwvxLNGV8Y1iSbj4rUy6yMhEA3fotn9A 36 | 37 | The Infinex account currently does not block deposits from all Solana coins, which means to support HSOL deposits and withdrawals, Infinex will simply just need to upgrade the backend infrastructure to track them. 38 | 39 | # Copyright 40 | 41 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 42 | -------------------------------------------------------------------------------- /src/app/page.tsx: -------------------------------------------------------------------------------- 1 | import { Status, Entry } from '@/components/Entries'; 2 | import { Header } from '@/components/Header'; 3 | import { PageContainer, PageIntro, PageTitle } from '@/components/UI'; 4 | import { reader } from '@/lib/reader'; 5 | import { number } from '@/lib/util'; 6 | import keystatic from '@/../keystatic.config'; 7 | 8 | const statuses = keystatic.collections.xips.schema.status.options; 9 | 10 | export default async function Home() { 11 | const entries = await reader.collections.xips.all(); 12 | entries.sort((a, b) => (b.entry.id || 0) - (a.entry.id || 0)); 13 | const byStatus = statuses.map((status) => { 14 | const matches = entries.filter((i) => i?.entry.status === status.value); 15 | return matches.length ? { status, entries: matches } : null; 16 | }); 17 | 18 | return ( 19 | 20 |
21 | Infinex Improvement Proposals 22 | 23 | XIPs are the primary mechanism for suggesting new features, collecting 24 | community input on an issue, documenting design decisions for changes to 25 | Infinex, and making adjustments to system parameters. 26 | 27 | 28 | {byStatus.map((i) => { 29 | if (!i) return null; 30 | const { status, entries } = i; 31 | return ( 32 |
33 | 34 |
35 | {entries.map((e) => ( 36 | 42 | ))} 43 |
44 |
45 | ); 46 | })} 47 | 48 | ); 49 | } 50 | -------------------------------------------------------------------------------- /content/xips/xip-92.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Patron Vesting Updates 3 | id: 92 4 | author: kmao (@kmaox), axe (@axefinaxe) 5 | type: core-upgrade 6 | network: Ethereum 7 | status: Implemented 8 | created: '2024-12-02' 9 | updated: '2025-01-17' 10 | --- 11 | # **Proposal Summary** 12 | 13 | This XIP proposes various updates to the Patron NFT Vesting Contract. 14 | 15 | # **Specification** 16 | 17 | ## **Overview** 18 | 19 | Infinex proposes the following additions to the Patron NFT Vesting contract: 20 | 21 | - The ability to allow the Treasury Seat to call a function that will claim on behalf of their strategic accounts, to their nominated address. This will only be for strategic purchasers. 22 | - Enable CWG tier owners to allocate patrons to relevant CWG members, from the existing CWG supply, under the existing CWG lockup terms. 23 | 24 | ## **Rationale** 25 | 26 | Some of Infinex's strategic partners have vesting patrons assigned to a CEX account, and are thus unable to claim their Patrons once vested. The additional functionality of allowing the Treasury Seat to claim on behalf of these users will allow these partners will receive their Patrons whilst not impacting the security of other users. Furthermore, Infinex needs to distribute additional CWG Patrons to members, which have been previously assigned to a null address. This function change will allow this to be done, whilst not affecting the previously approved unlock terms and allocation amount. 27 | 28 | ## **Technical Specification** 29 | 30 | This XIP will include the following updates to the Patron Vesting Contract: 31 | 32 | - `allocateCWGTokens`: Enable tier owners to reallocate unclaimed CWG tokens from dead addresses to new recipients while maintaining vesting schedules. 33 | - `claimForStrategicTierType`: Allow tier owners to execute token claims on behalf of recipients in strategic tiers. 34 | 35 | # **Copyright** 36 | 37 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 38 | -------------------------------------------------------------------------------- /content/xips/xip-63.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Dorge Token 3 | id: 63 4 | author: Pstar 5 | type: core-upgrade 6 | network: Base 7 | status: Approved 8 | created: '2024-07-22' 9 | updated: '2024-07-30' 10 | --- 11 | 12 | # Proposal Summary 13 | 14 | XIP-63 proposes enabling support for the $DORGE token on Infinex. 15 | 16 | # Specification 17 | 18 | ## Overview 19 | 20 | $DORGE is a memecoin currently being developed by Grant Warwick. $DORGE was initially intended as an addition to Infinex’s Memecoin support as per XIP-51, to be included in the Infinex Craterun campaign. However, $DORGE was not strictly included in crates themselves and has instead been airdropped to certain crate holders randomly. This process will continue until all crates are distributed. 21 | 22 | Currently, $DORGE is not displayed on Infinex, rendering only technical users capable of seeing if they have been airdropped $DORGE. Accessibility to $DORGE should be more inclusive to its holders. However, as $DORGE currently does not have a price feed, it should be temporarily listed as “Other Assets” on Infinex. 23 | 24 | ## Rationale 25 | 26 | Infinex wishes to support memecoins; $DORGE is and will continue to be a valuable addition to the Infinex memecoin ecosystem, and should be made as accessible as possible. Supporting $DORGE would allow users to withdraw and deposit the token, even though it currently does not have a price feed. 27 | 28 | ## Technical Specification 29 | 30 | Infinex will add $DORGE on the Base network. The token address is *0xa51f512a2c4d6354691a2174cf5fe886b38c8160*. 31 | 32 | Infinex will need to upgrade the backend infrastructure to track $DORGE deposits and withdrawals. 33 | 34 | The UI will need to be updated to reflect $DORGE deposits and withdrawals. As $DORGE does not have a price feed, it will be listed under “Other Assets” until a reliable price feed is established after the $DORGE presale planned for Q3 2024. 35 | 36 | # Copyright 37 | 38 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 39 | -------------------------------------------------------------------------------- /content/xips/xip-52.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Pirex ETH 3 | id: 52 4 | author: kmao (@kmaox), 0xfunky (@0xfunky) 5 | type: core-upgrade 6 | network: Ethereum 7 | status: Implemented 8 | created: '2024-07-01' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-52 proposes enabling support for Pirex Staked ETH & Pirex apxETH. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Infinex already supports another Ethereum LST (Lido Staked Ether), and aims to add additional one, being PXETH & APXETH. 19 | 20 | Infinex will need to update the UI to effectively reflect PXETH & AXPETH deposits and withdrawals, as well as the current market price of the asset. The value of PXETH & AXPETH will be denominated in USD and determined by a 3rd-party market price feed and will also be counted as TVL for the upcoming [**Craterun**](https://proposals.infinex.xyz/xips/xip-34) campaign. 21 | 22 | Furthermore, Redacted has offered 140 BTRFLY in Ecosystem Prizes for the Craterun Campaign. This will be split between 4 different prizes of 35 BTRFLY each, and will take up 4 slots of the approved 69 ecosystem prizes, as per [XIP-34](https://proposals.infinex.xyz/xips/xip-34). 23 | 24 | ## Rationale 25 | Pirex Eth gives users access to the highest yielding LST, which currently has almost 3x the base staking yield. 26 | 27 | ![](/assets/xips/xip-52/pxeth.jpg) 28 | 29 | ## Technical Specification 30 | 31 | The token addresses of PXETH & AXPETH can be found below: 32 | 33 | {% table %} 34 | - Coin 35 | - **Network** 36 | - **Token Address** 37 | --- 38 | - PXETH 39 | - Mainnet 40 | - 0x04c154b66cb340f3ae24111cc767e0184ed00cc6 41 | --- 42 | - APXETH 43 | - Mainnet 44 | - 0x9ba021b0a9b958b5e75ce9f6dff97c7ee52cb3e6 45 | {% /table %} 46 | 47 | The Infinex account currently does not block deposits from all ERC-20 tokens, which means to support PXETH & APXETH deposits, Infinex will simply just need to upgrade the backend infrastructure to track them. 48 | 49 | # Copyright 50 | 51 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 52 | -------------------------------------------------------------------------------- /content/xips/xip-24.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Replace Madladz with Saga owners 3 | id: 24 4 | author: Yung Peso (@yungpeso) 5 | type: community 6 | network: 'Solana, Base' 7 | status: Rejected 8 | created: '2024-05-11' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-24 proposes a minor revision to [XIP-21](https://proposals.infinex.xyz/xips/xip-21) by changing the airdrop to Solana users from Mad Lads holders to Saga owners. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Following recent discussions on XIP-21, a reconsideration of which crypto communities should recieve an airdrop is warranted. The changes proposed are:  19 | 20 | 1. Remove the [Mad Lads](https://magiceden.io/marketplace/mad_lads) airdrop allocation from XIP-21.  21 | 1. Grant the GP allocation to [Saga](https://solscan.io/collection/4a2d96b22ab0c8f01cb5ce5bc960b627c2a8271529ae5132d5352b7c86b3b54d) Owners. 22 | 23 | ## Rationale 24 | 25 | Targeted airdrops attempt to make existing communities join other project’s community in return for a reward. Airdropping to Madlads holders is a suboptimal choice because of the collection size in comparison to Saga owners (9,967 vs 17,300). This allows us to reach a broader group of people. 26 | 27 | Furthermore, sybils and whales getting outsized GP allocations from this proposed airdrop is less of a concern due to the physical restraint of owning the Saga device in order to acquire the NFTs. 28 | 29 | ## Technical Specification 30 | 31 | A snapshot of Saga owners has been taken [here](https://drive.google.com/file/d/1B_Tq3ckSpLnOoCRvighnxjsRVD2YkIOj/view?usp=sharing). 32 | 33 | 19,895,000 GP will be distributed to these addresses. This is approximately 3.3% of the total GP supply and around 0.1% of the total supply. Wrapped GP will be distributed to a user's Solana address, and users can unwrap it by bridging it to Base.  34 | 35 | This results in an allocation of 1,150 GP per NFT (17,300 Genesis NFTs were minted). 36 | 37 | # Copyright 38 | 39 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 40 | -------------------------------------------------------------------------------- /content/wgcs/wgc-5.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | id: 5 3 | title: Establish a Data Analytics WG 4 | wgName: Data Analytics 5 | wgLead: Gateway (@gateway-fm) 6 | author: temocio (@temocio), Bilby (@bilb-y) 7 | status: Implemented 8 | budget: 10,000 USDC 9 | budgetCadence: Monthly 10 | timeline: Indefinetly 11 | created: '2024-01-15' 12 | --- 13 | ### **Working Group Name** 14 | 15 | Data Analytics Working Group 16 | 17 | ### **Working Group Lead** 18 | 19 | Discord – andskur 20 | 21 | Github – [Gateway FM](https://github.com/gateway-fm) 22 | 23 | ### **Outcomes** 24 | 25 | Members of the proposed Data Analytics Working Group (DA WG) have been operating as part of Core Working Group and developed the Synthetix PerpsV3 API for consumption by the Infinex app Synthetix PerpsV3 integration, as detailed in [XIP-9](https://proposals.infinex.xyz/xips/xip-9). 26 | 27 | This charter will separate these core working group members into their own working group, the DA WG, in an effort to further the decentralise the protocol. 28 | 29 | The DA WG will be responsible for: 30 | 31 | - Maintaining the Synthetix PerpsV3 API 32 | 33 | # **Budget** 34 | 35 | ### **Budget Rationale** 36 | 37 | Whilst the DA WG were integrated within the Core WG, they were paid the following amounts for their contribution: 38 | 39 | - Milestone I: $14,842 USDC 40 | - Milestone II: $22,012.77 USDC 41 | - Milestone III: $19,906.37 USDC 42 | - Milestone IV: $16,452.09 USDC 43 | - Maintenance: $8,613.65 USDC 44 | - Delivery bonus: 2000 SNX 45 | 46 | Based on these prior estimates, and the uncertainty around how much maintenance is currently required, the DA WG will bill the council at a monthly cadence, with an upper limit of 10,000 USDC per month. 47 | 48 | The working group will be paid to the following address: 49 | 50 | eth:0x78CEE97C23560279909c0215e084dB293F036774 51 | 52 | # **Timeline** 53 | 54 | ### **Timeline Rationale** 55 | 56 | The DA WG will operate indefinitely until further changes are required to be made. 57 | 58 | ### **Release Candidate Frequency** 59 | 60 | The release candidate frequency of the DA WG will be ad-hoc. 61 | -------------------------------------------------------------------------------- /content/tas/ta-6.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Distribution to Liquid Patron Purchasers 3 | id: 6 4 | author: Egor (@egorsidelska) 5 | status: Implemented 6 | created: '2024-11-07' 7 | --- 8 | # **Summary** 9 | 10 | Treasury has approved an distribution of additional Patrons for Liquid Patrons buyers during the Patron sale. Anyone who bought Liquid Patrons during the Patron sale at the $5000 tier will receive one Locked Patron into their Infinex Account. 11 | 12 | # **Overview** 13 | 14 | 713 Liquid Patrons were sold in total during the Patron sale. These buyers paid a premium for liquidity. 332 Liquid Patrons were purchased via treasury during the strategic wave (wave 1) and a further 381 Patrons bought in the community sale in waves 2, 3 and 4. 15 | 16 | Of the 205 users that bought Liquid Patrons, less than 5% sold their Patrons post distribution. 17 | 18 | Treasury will distribute the Liquid Patron buyers one Locked Patron NFT for each of their Liquid Patrons. 19 | 20 | Locked Patrons carry a 1-year lock and then vest linearly over 24-months as per the sale. 21 | 22 | # **Rationale** 23 | 24 | Infinex wrapped up the Patron Sale on the 24th of October 2024. The sale consisted of three tiers which included Liquid, Linear and Locked tiers priced at $5000, $3000 and $1250 respectively. 25 | 26 | The tiered pricing structure allowed for Patron buyers to balance liquidity and price. However, the price tiers were fixed to reduce the pricing uncertainty. Post distribution, Liquid Patrons have had a floor price of approximately $3000. By distributing Liquid Patron buyers a Locked Patron (priced at $1,250 during the sale) the treasury ensures that Liquid Patron buyers during the sale did not pay more than the current floor price. 27 | 28 | # **Outcome** 29 | 30 | Treasury has committed up to 713 Locked Patrons for this distribution which will be credited directly from Treasury reserves. 31 | 32 | The Locked Patrons will appear in Infinex User Accounts carrying the same vesting schedule as all other Locked Patrons. 33 | 34 | # **Specification** 35 | 36 | A list of Infinex Account holders has already been prepared and no user action is necessary. 37 | -------------------------------------------------------------------------------- /content/xips/xip-86.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: ENS Integration 3 | id: 86 4 | author: ben (@hooperben) 5 | type: integration-upgrade 6 | status: Approved 7 | created: '2024-10-21' 8 | updated: '2024-11-25' 9 | --- 10 | # Proposal Summary 11 | 12 | This XIP proposes an integration within the Infinex web app that would allow for management of ENS domain records. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | I think that being able to manage and assign ENS usernames with the schmick UI that Infinex offers could onboard a lot more volume if done correctly. 19 | 20 | If I can tell someone to send ETH/USDC/whatever to benhooper.eth and that's my infinex account, that's easy for everyone involved. If I can also manage my ENS records through my Infinex account, that'd be even better. 21 | 22 | ## Rationale 23 | 24 | Currently, Infinex user names are a nice touch, but ENS still reigns supreme (see most Infinex employees twitter handles). 25 | 26 | ## Technical Specification 27 | 28 | To make it incredibly easy for the user, I'd split this integration into 2 parts: 29 | 30 | - ens.infinex.xyz 31 | - ENS page within infinex app 32 | 33 | ### ens.infinex.xyz 34 | 35 | ens.infinex.xyz would be a site where users can connect their existing wallets that own ENS records, and can easily transfer to their Infinex username. 36 | 37 | ### ENS page within Infinex app 38 | 39 | To start with, this is where a user could see ENS domains owned by their Infinex wallet, and then eventually could do all the same functionality as app.ens.domains for their existing records (set address owner, create subname, see expiry/extend, etc). 40 | 41 | 🚨 **Cool Bonus Idea** 🚨 - if a user opt's in (mainly to save on gas) set up their .infinex.eth record too, i.e. mine would be ben.infinex.eth, which would map to my Infinex smart account address. This also assumes that Infinex owns infinex.eth which I'm unsure of. 42 | 43 | **Security** 44 | 45 | I don't believe this model adds any new security risks to Infinex. 46 | 47 | # Copyright 48 | 49 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 50 | -------------------------------------------------------------------------------- /content/xips/xip-95.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Bulls Rewards for Swidgers 3 | id: 95 4 | author: kmao (@kmaox) 5 | type: core-upgrade 6 | network: Base, Optimism, Ethereum, Solana, Arbitrum, Polygon 7 | status: Approved 8 | created: '2025-01-14' 9 | updated: '2025-01-17' 10 | --- 11 | # Proposal Summary 12 | 13 | # Specification 14 | 15 | This proposal introduces a Bulls incentive campaign aimed at increasing user engagement and platform activity by rewarding users who utilize Swidge (Swap or Bridge). 16 | 17 | ## Overview 18 | 19 | Swidge has become a critical feature of the platform, serving as the first big intergration Infinex has implemented. Swidging allows users to efficiently move assets across chains and/or swap them within their ecosystems. To encourage further user adoption of Swidge, Infinex plans to distribute bulls at the rate of 1 Bull for every 5 dollars of swap or swidge volume, and 1 Bull for every 500 dollars for stable swaps/bridges. 20 | 21 | ## Rationale 22 | 23 | Swidging has been the most important functionality that Infinex has launched as of recent. Whilst the DRV trading competition provides users some incentive to Swidge on Infinex, implementing broader incentives for any Swidge will help promote user activity and acquisition. 24 | 25 | ## Technical Specification 26 | 27 | Currently, Infinex distributes 1,000,000 Bulls a day via Bullrun rewards, which are distributed to the top 2,500 users. 28 | 29 | For the Swidge campaign, Infinex proposes a starting rate of 1 Bull for every 5 dollars of swap or swidge volume, and 1 Bull for every 500 dollars for stable swaps/bridges. This campaign will last indefinitely, with a start date and future start date decided in a later RC. 30 | 31 | Patron holders will also receive a 25% boost on Bulls earned throughout the campaign. 32 | 33 | Currently there are no anti-sybil measures, however the CWG reserves the right to update anti-sybil rules and potentially remove a user's sybilled bulls in future RCs. The CWG also reserves the right to change the reward rate of Bulls in future RCs. 34 | 35 | # Copyright 36 | 37 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 38 | -------------------------------------------------------------------------------- /content/xips/xip-48.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support USDT 3 | id: 48 4 | author: kmao (@kmaox) 5 | type: integration-upgrade 6 | network: Ethereum, Base, Arbitrum 7 | status: Implemented 8 | created: '2024-06-24' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-48 proposes enabling support for USDT. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Infinex currently supports only supports USDC and USDE stablecoins. Adding USDT as another supported asset will further grow TVL. 19 | 20 | Infinex will need to update the UI to effectively reflect USDT deposits and withdrawals, as well as the current market price of the asset. The value of these assets will be denominated in USD and determined by a 3rd-party market price feed and will also be counted as TVL for the upcoming [**Craterun**](https://proposals.infinex.xyz/xips/xip-34) campaign. 21 | 22 | ## Rationale 23 | 24 | USDT is the biggest stablecoin by marketcap, and various Infinex users have already accidentally deposited USDT. By enabling support for USDT, these users will be able to stake their funds, and also withdraw them. 25 | 26 | ## Technical Specification 27 | 28 | Infinex will add support for deposits and withdrawals of USDT on all supported chains except Base and Optimism. Some networks will have the native USDT token supported, and other networks will have a bridged variant supported. The token addresses can be found below. 29 | 30 | {% table %} 31 | - Network 32 | - Token Address 33 | --- 34 | - Mainnet 35 | - 0xdac17f958d2ee523a2206206994597c13d831ec7 36 | --- 37 | - Arbitrum 38 | - 0xfd086bc7cd5c481dcc9c85ebe478a1c0b69fcbb9 39 | --- 40 | - Polygon 41 | - 0xc2132d05d31c914a87c6611c10748aeb04b58e8f 42 | --- 43 | - Optimism 44 | - 0x94b008aA00579c1307B0EF2c499aD98a8ce58e58 45 | --- 46 | - Solana 47 | - Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB 48 | {% /table %} 49 | 50 | The Infinex account currently does not block deposits from all ERC-20 tokens, which means to support USDT deposits, Infinex will simply just need to upgrade the backend infrastructure to track those deposits. 51 | 52 | # Copyright 53 | 54 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 55 | -------------------------------------------------------------------------------- /content/rcs/rc-5.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Add L2 bridged USDC variants 3 | id: 5 4 | wg: CWG 5 | author: kmao (@kmaox) 6 | status: Implemented 7 | created: '2024-05-13' 8 | updated: '2023-05-13' 9 | implemented: '2023-12-13' 10 | --- 11 | ### Overview 12 | 13 | The current STW platform only recognises native USDC deposits for staking and claiming. The Core WG will upgrade the STW platform to allow L2 bridged USDC deposits to be recognised and earn GP during STW. 14 | 15 | ### Outcome 16 | 17 | Upgrade the STW platform to recognise L2 bridged USDC deposits. 18 | 19 | ### Proposed Changes 20 | 21 | ##### **Platform** 22 | 23 | Infinex aims to upgrade the platform to support L2 bridged variants of USDC as part of the users total USDC balance, and the total available to be staked. 24 | 25 | The existing USDC variants that are supported are: 26 | 27 | {% table %} 28 | - Chain 29 | - Ticker 30 | - Address 31 | --- 32 | - Arbitrum 33 | - USDC 34 | - `0xaf88d065e77c8cC2239327C5EDb3A432268e5831` 35 | --- 36 | - Base 37 | - USDC 38 | - `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` 39 | --- 40 | - Optimism 41 | - USDC 42 | - `0x0b2c639c533813f4aa9d7837caf62653d097ff85` 43 | --- 44 | - Polygon POS 45 | - USDC 46 | - `0x3c499c542cef5e3811e1192ce70d8cc03d5c3359` 47 | --- 48 | - Ethereum 49 | - USDC 50 | - `0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48` 51 | --- 52 | - Solana 53 | - USDC 54 | - `EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v` 55 | {% /table %} 56 | 57 | The new USDC variants that the Core WG is aiming to add: 58 | 59 | {% table %} 60 | - Chain 61 | - Ticker 62 | - Address 63 | --- 64 | - Arbitrum 65 | - USDC.e 66 | - `0xff970a61a04b1ca14834a43f5de4533ebddb5cc8` 67 | --- 68 | - Base 69 | - USDCbc 70 | - `0xd9aaec86b65d86f6a7b5b1b0c42ffa531710b6ca` 71 | --- 72 | - Optimism 73 | - USDC.e 74 | - `0x7f5c764cbc14f9669b88837ca1490cca17c31607` 75 | --- 76 | - Polygon POS 77 | - USDC.e 78 | - `0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174` 79 | {% /table %} 80 | 81 | Once upgraded, existing users who have deposited those USDC variants will be able to stake their full deposited USDC balance. 82 | 83 | # Copyright 84 | 85 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 86 | -------------------------------------------------------------------------------- /content/tas/ta-4.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Airdrop PYTH to Craterun Users 3 | id: 4 4 | author: Egor (@egorsidelska) 5 | status: Implemented 6 | created: '2024-07-05' 7 | --- 8 | # **Summary** 9 | 10 | Treasury has approved to airdrop 1,000,000 PYTH to Infinex accounts which opened crates within the first 24 hours of Craterun launch. 11 | 12 | # **Overview** 13 | 14 | Infinex wants to reward early community members who are engaged, active and paying attention. By airdropping PYTH, Infinex hopes to continue rewarding Patrons while building integrations and product features in the coming months. 15 | 16 | # **Rationale** 17 | 18 | Pyth is an Infinex partner and Pyth's entropy product has been specifically used to make the Craterun campaign possible. Infinex received an early and substantial grant from Pyth Foundation to align the communities. 19 | 20 | Pyth is one of the leading onchain data providers in crypto with over 450+ price feeds and 50+ supported chains. Infinex is a primary user of Pyths VRF ([https://pyth.network/blog/secure-random-numbers-for-blockchains](https://pyth.network/blog/secure-random-numbers-for-blockchains)) on BASE resulting in substantial onchain volume recorded during the first day of crate opening. 21 | 22 | ![](/assets/trfs/trf-4/test.png) 23 | 24 | By aligning Infinex Patrons with Pyth holders, stakers and the community we build a stronger bridge between our platforms. Infinex plans to expand integration partners rapidly to provide additional functionality to Patrons of the Infinex platform. Integration partners like Curve, Wormhole, Solana, Lido, Jupiter, Renzo, Arbitrum, Optimism, BASE and many more have already been added to the roadmap. 25 | 26 | # **Outcome** 27 | 28 | The PYTH will be distributed across all eligible accounts equally. PYTH will show as an asset under the Wallet tab in your Infinex account and be represented onchain. 29 | 30 | # **Specification** 31 | 32 | Airdropped PYTH will be liquid and require no claiming function. Patrons will be able to stake their additional balance into the Craterun campaign on receipt. 33 | 34 | Accounts which do not have a Solana recovery address will need to create one and follow the account security steps before they can withdraw. 35 | -------------------------------------------------------------------------------- /content/xips/xip-49.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support OP & ARB 3 | id: 49 4 | author: kmao (@kmaox) 5 | type: integration-upgrade 6 | network: Ethereum, Optimism, Arbitrum 7 | status: Implemented 8 | created: '2024-06-24' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-49 proposes enabling support for the Optimism and Arbitrum Tokens. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | OP and ARB are tokens that mostly sit idle in a user's wallet, making it a low opportunity cost for a user to deposit it into their Infinex Account. Enabling deposits of these coins will help grow Infinex's TVL as well as provide users a safer place to hold their tokens. 19 | 20 | Infinex will need to update the UI to effectively reflect ARB and OP deposits and withdrawals, as well as the current market price of the asset. The value of these assets will be denominated in USD and determined by a 3rd-party market price feed and will also be counted as TVL for the upcoming [**Craterun**](https://proposals.infinex.xyz/xips/xip-34) campaign. 21 | 22 | ## Rationale 23 | 24 | Arbitrum and Optimism tokens serve little utility outside of governance rights. With the majority of crypto users not participating in governance, it makes sense for a user to instead deposit their tokens into Infinex and engage in the upcoming Craterun campaign. 25 | 26 | ## Technical Specification 27 | 28 | A list of the supported token, network, and token address can be found below. Infinex will add support for deposit and withdrawals for all of the listed tokens. 29 | 30 | {% table %} 31 | - Token 32 | - Network 33 | - Token Address 34 | --- 35 | - OP 36 | - Optimism 37 | - 0x4200000000000000000000000000000000000042 38 | --- 39 | - Arbitrum 40 | - Arbitrum One 41 | - 0x912CE59144191C1204E64559FE8253a0e49E6548 42 | --- 43 | - Arbitrum 44 | - Ethereum 45 | - 0xb50721bcf8d664c30412cfbc6cf7a15145234ad1 46 | {% /table %} 47 | 48 | The Infinex account currently does not block deposits from all ERC-20 tokens, which means to support ARB & OP deposits, Infinex will simply just need to upgrade the backend infrastructure to track those deposits. 49 | 50 | # Copyright 51 | 52 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 53 | -------------------------------------------------------------------------------- /content/irs/ir-7.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Establish Patron NFT Governance 3 | id: 7 4 | author: kmao (@kmaox) 5 | status: Approved 6 | created: '2024-06-25' 7 | --- 8 | # Referendum Summary 9 | 10 | IR-7 proposes that the Patron NFT be established as the voting mechanism for the ecosystem seats of Infinex Governance. 11 | 12 | # Specification 13 | 14 | ## Overview 15 | 16 | The following upgrades are proposed in IR-7. 17 | 18 | 1. The Patron NFT be used as the voting mechanism for the ecosystem seats of Infinex Governance. 19 | 1. Epoch 2 elections are delayed until the end of the Patron NFT sale. 20 | 21 | As GP has not been implemented yet as a voting mechanism, this IR will be voted on via SDS. 22 | 23 | ## Rationale 24 | 25 | Infinex currently uses GP to vote in the council members, and with this points program having already been sunset in favor of the Patron NFT, it's clear that the Patron NFT should become the official voting tool of Infinex. 26 | 27 | In order to allow this, Infinex will then need to delay the council elections until after the Patron NFT sale. 28 | 29 | ## Technical Specification 30 | 31 | #### Patron NFT Voting Rights 32 | 33 | This IR proposes that Patron NFTs be used to vote for all of ecosystem seats. Voting power should be calculated linearly, with one liquid Patron NFT serving for one vote. Any illiquid Patron NFTs should also have 0.2 voting power, the Patron community sale allows parties to purchase locked NFTs. 34 | 35 | This mean's the Infinex Council will be voted in via these means: 36 | 37 | {% table %} 38 | --- 39 | - Council 40 | - Count 41 | - Voting Method 42 | --- 43 | - Ecosystem Seat 44 | - 4 45 | - Patron NFTs 46 | --- 47 | - Treasury Seat 48 | - 1 49 | - Patron NFTs 50 | --- 51 | - Security Seat 52 | - 1 53 | - Appointed Seat 54 | --- 55 | - Operations Seat 56 | - 1 57 | - Appointed Seat 58 | {% /table %} 59 | 60 | #### Delayed Epoch 2 61 | 62 | As the Patron NFT has not been released yet, this IR also proposes that Epoch 2 elections begin after the Patron NFT sale has concluded. This is estimated to be around mid August. 63 | 64 | In the meantime, council members will still receive their prior stipend, with only Epoch 2 candidates receiving the new Patron NFT stipend. 65 | 66 | # Copyright 67 | 68 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 69 | -------------------------------------------------------------------------------- /content/xips/xip-64.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Implement Ethena Sats 3 | id: 64 4 | author: kmao (@kmaox), Guy (@EthenaLabs) 5 | type: integration-upgrade 6 | network: 'Ethereum, Arbitrum ' 7 | status: Implemented 8 | created: '2024-07-26' 9 | updated: '2024-08-14' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-64 proposes enabling Ethena SATs for Infinex users and SATs bonuses for swapping from USDC into USDe in the Infinex platform. It also proposes the introduction of several new badges related to Ethena USDe holders. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | USDe deposited in Infinex currently earns weekly USDe rewards. This XIP proposes integrating Ethena SATs at a rate of 20x daily. 20 | 21 | Infinex is also planning an RC to implement [XIP-31](https://proposals.infinex.xyz/xips/xip-30), which will allow users to swap USDC to USDe on Ethereum Mainnet and Arbitrum. 22 | 23 | Users who swap to USDe will eligible for a one-time bonus of 200 SATs per USDe. Users who hold USDe at the start of the campaign will also receive this bonus. 24 | 25 | This campaign will run until the end of the Ethena Season two campaign. 26 | 27 | Users who withdraw USDe before the campaign ends will lose all SATs. Users who also swap back from USDe to USDc will also lose all SATs. 28 | 29 | Users who swap from USDC to USDe will receive a "Real Yield Maxi" badge, and users who held USDe at 2024-07-25 08:00:00 UTC will receive an "OG Real Yield Maxi" badge. Users will recieve these badges even if they withdraw after the snapshot, or after they perform the swap. 30 | 31 | An example: 32 | 33 | **A user swaps 100,000 USDC for 100,000 USDe, and holds until the end of the campaign.** 34 | 35 | This user will receive 20,000,000 SATs swap bonus plus 2,000,000 SATs per day, as well as weekly distribution of USDe rewards. 36 | 37 | ## Rationale 38 | 39 | USDe is one of the largest assets by deposit volume on Infinex, the current USDe incentives have been well received but the addition of SATs should increase the demand for holding USDe on Infinex. 40 | 41 | ## Technical Specification 42 | 43 | The Infinex interface will be updated to implement swaps from USDC to USDe. An integration into the SATs API will also be made to allow users to see their SATs balance in their account. 44 | 45 | # Copyright 46 | 47 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 48 | -------------------------------------------------------------------------------- /content/xips/xip-50.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support DAI & SDAI 3 | id: 50 4 | author: kmao (@kmaox) 5 | type: integration-upgrade 6 | network: 'Ethereum, Optimism, Arbitrum, Base, Polygon ' 7 | status: Implemented 8 | created: '2024-06-24' 9 | --- 10 | ## **Proposal Summary** 11 | 12 | XIP-50 proposes enabling support for DAI and Savings DAI. 13 | 14 | # **Specification** 15 | 16 | ## **Overview** 17 | 18 | Infinex currently supports only supports USDC and USDE stablecoins. Adding DAI as another supported stablecoin, and a yield accruing asset like SDAI will further grow TVL. 19 | 20 | Infinex will need to update the UI to effectively reflect DAI & SDAI deposits and withdrawals, as well as the current market price of the asset. The value of these assets will be denominated in USD and determined by a 3rd-party market price feed and will also be counted as TVL for the upcoming [**Craterun**](https://proposals.infinex.xyz/xips/xip-34) campaign. 21 | 22 | ## **Rationale** 23 | 24 | DAI is the next biggest stablecoin that has not yet been approved by Infinex governance, making it obvious why Infinex supporting it will be important. Furthermore, SDAI is another yield accruing asset which can also added to Infinex to encourage further deposits. 25 | 26 | ## **Technical Specification** 27 | 28 | A list of the supported token, network, and token address can be found below. Infinex will add support for deposit and withdrawals for all of the listed tokens. 29 | 30 | {% table %} 31 | - Token 32 | - Network 33 | - Token Address 34 | --- 35 | - DAI 36 | - Mainnet 37 | - 0x6b175474e89094c44da98b954eedeac495271d0f 38 | --- 39 | - DAI 40 | - Arbitrum One 41 | - 0xda10009cbd5d07dd0cecc66161fc93d7c9000da1 42 | --- 43 | - DAI 44 | - Optimism 45 | - 0xda10009cbd5d07dd0cecc66161fc93d7c9000da1 46 | --- 47 | - DAI 48 | - Base 49 | - 0x50c5725949a6f0c72e6c4a641f24049a917db0cb 50 | --- 51 | - DAI 52 | - Polygon POS 53 | - 0x8f3cf7ad23cd3cadbd9735aff958023239c6a063 54 | --- 55 | - Savings Dai (SDAI) 56 | - Mainnet 57 | - 0x83f20f44975d03b1b09e64809b757c47f942beea 58 | {% /table %} 59 | 60 | The Infinex account currently does not block deposits from all ERC-20 tokens, which means to support DAI & SDAI deposits, Infinex will simply just need to upgrade the backend infrastructure to track those deposits. 61 | 62 | # Copyright 63 | 64 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 65 | -------------------------------------------------------------------------------- /content/xips/xip-77.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Jupiter Swaps 3 | id: 77 4 | author: Yamen (@yaminfinex) 5 | type: integration-upgrade 6 | network: Solana 7 | status: Approved 8 | created: '2024-08-29' 9 | updated: '2024-09-09' 10 | --- 11 | # Proposal Summary 12 | 13 | This XIP proposes the capability to perform swaps using Jupiter on Solana as part of the Infinex Account on Solana. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Infinex currently supports very limited swap capability, with no swap capability at all on Solana. Now that the platform supports many additional tokens, it makes sense to enable swapping between these tokens without requiring users to withdraw and deposit back onto platform. 20 | 21 | Jupiter is the largest and most well known swapping destination on Solana, supporting 41 underlying DEX protocols through a single interface. 22 | 23 | The Infinex Account on Solana should be upgraded to allow atomic swaps using the Jupiter Swap v6 Program. 24 | 25 | The Infinex Platform will later use the Jupiter API to find appropriate route paths to submit to this functionality, including limiting which tokens or DEXes are allowed. 26 | 27 | ## Rationale 28 | 29 | Enabling the ability to swap between assets is a core function of Infinex. Jupiter is proposed instead of other aggregators or individual DEXes because: 30 | 31 | - Integrating once with Jupiter Swap v6 is much simpler than integrating with all 41 DEXes on Solana. 32 | - Jupiter provides an API to find the best routes and therefore prices for Infinex users, which is never worse than direct DEX integration and often quite a bit better. 33 | - Jupiter is the main aggregator on Solana. 34 | - Jupiter Swap v6 does not take any fees (only does a passthrough of fees from underlying DEXes). 35 | 36 | ## Technical Specification 37 | 38 | The proposed changes to the Infinex Account on Solana is to: 39 | 40 | - Change the Authorizer program to allow calling the Jupiter v6 Program (JUP6LkbZbjS1jKKwapdHNy74zcZ3tLUZoi5QNyVTaV4). 41 | - Implement appropriate risk controls (using sub-accounts or temporary wallets) to limit the potential surface area of funds exposed to the program. 42 | 43 | Infinex users will need to trigger an account upgrade to receive this new functionality in their Solana account. 44 | 45 | The Infinex App will also require changes in order to deliver a seamless swap experience. 46 | 47 | # Copyright 48 | 49 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 50 | -------------------------------------------------------------------------------- /tailwind.config.ts: -------------------------------------------------------------------------------- 1 | import type { Config } from 'tailwindcss'; 2 | import tokens from './styles/tokens'; 3 | import defaultTheme from 'tailwindcss/defaultTheme'; 4 | import { 5 | addTypographyClassesPlugin, 6 | extendedFontSizes, 7 | typography, 8 | } from './styles/typography'; 9 | 10 | const config: Config = { 11 | content: [ 12 | './src/pages/**/*.{js,ts,jsx,tsx,mdx}', 13 | './src/components/**/*.{js,ts,jsx,tsx,mdx}', 14 | './src/app/**/*.{js,ts,jsx,tsx,mdx}', 15 | './src/lib/**/*.{js,ts,jsx,tsx,mdx}', 16 | ], 17 | theme: { 18 | // Colors 19 | borderColor: tokens.borderColor, 20 | outlineColor: tokens.outlineColor, 21 | textColor: tokens.textColor, 22 | divideColor: tokens.dividerColor, 23 | backgroundColor: tokens.backgroundColor, 24 | ringColor: tokens.ringColor, 25 | ringOpacity: { 26 | DEFAULT: '1', 27 | }, 28 | ringOffsetColor: tokens.ringOffsetColor, 29 | fill: tokens.fill, 30 | caretColor: tokens.borderColor, 31 | textDecorationColor: tokens.textColor, 32 | gradientColorStops: tokens.backgroundColor, 33 | 34 | fontFamily: { 35 | // Infinex brand fonts 36 | DEFAULT: [typography.fontFamily.body, ...defaultTheme.fontFamily.sans], 37 | sans: [typography.fontFamily.body, ...defaultTheme.fontFamily.sans], 38 | mono: [typography.fontFamily.mono, ...defaultTheme.fontFamily.mono], 39 | condensed: [typography.fontFamily.title, ...defaultTheme.fontFamily.sans], 40 | // Campaign specific fonts 41 | barlow: ['var(--font-barlow, "Barlow")', ...defaultTheme.fontFamily.sans], 42 | 'bai-jamjuree': [ 43 | 'var(--font-bai-jamjuree, "Bai Jamjuree")', 44 | ...defaultTheme.fontFamily.sans, 45 | ], 46 | kanit: ['var(--font-kanit, "Kanit")', ...defaultTheme.fontFamily.sans], 47 | }, 48 | 49 | extend: { 50 | fontSize: { 51 | // Generates `text-2xs` class (11px): 52 | '2xs': [ 53 | extendedFontSizes['2xs'].fontSize, 54 | extendedFontSizes['2xs'].lineHeight, 55 | ], 56 | }, 57 | backgroundImage: { 58 | 'gradient-radial': 'radial-gradient(var(--tw-gradient-stops))', 59 | 'gradient-conic': 60 | 'conic-gradient(from 180deg at 50% 50%, var(--tw-gradient-stops))', 61 | }, 62 | }, 63 | }, 64 | plugins: [ 65 | require('@tailwindcss/typography'), // Generates custom `body-` and `title-` typography classes: 66 | addTypographyClassesPlugin(), 67 | ], 68 | }; 69 | 70 | export default config; 71 | -------------------------------------------------------------------------------- /content/xips/xip-19.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: GP Rewards Program for Synthetix Stakers 3 | id: 19 4 | author: hakari (@HakariBet) 5 | type: governance 6 | network: Ethereum & Optimism 7 | status: Rejected 8 | created: '2024-02-14' 9 | --- 10 | # Proposal Summary 11 | 12 | This proposal advocates for the introduction of a Governance Points (GP) rewards program to acknowledge and incentivize Synthetix stakers contributions. 13 | 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Synthetix has been a cornerstone in the development and growth of protocols like Infinex. To further strengthen this collaboration and acknowledge the contributions of Synthetix stakers, this proposal suggests the introduction of a GP rewards program. 20 | By staking SNX tokens, users actively contribute to the stability and growth of the ecosystem, particularly in this case supporting the integration and success of Infinex. 21 | The program aims to gather and incentivize stakers which are active participants in Synthetix Governance and Infinex Governance. 22 | For this rewards program 10 million GP is planned to be minted and distributed. This proposal, once approved, aims to contribute to the continued success and growth of Infinex and its governance. 23 | 24 | ## Rationale 25 | Synthetix stakers play a crucial role in the workings of Infinex. Recognizing their commitment and dedication to the ecosystem, this proposal aims to implement a GP rewards program as a token of appreciation and commitment. 26 | This initiative strengthens the bond between Synthetix and Infinex but also encourages members of the Synthetix community to participate in Infinex governance. 27 | 28 | ## Technical Specification 29 | 30 | ### GP Distribution 31 | 32 | A total of 10,000,000 GP rewards will be distributed, increasing the total supply to 147,184,576 GP. There will be a single criterion for qualifying, with a 40% bonus if the staker participated in the Synthetix governance by voting in previous elections. A specified smart contract will be deployed to facilitate the distribution process. GP will be assigned to the user's onchain addresses. 33 | 34 | ### Qualification Criterion 35 | 36 | To be eligible for GP rewards, Synthetix stakers must meet this criterion: 37 | 1. Active participation in the Infinex governance by voting in previous IR proposals. 38 | 39 | ### Duration 40 | 41 | The GP rewards program for Synthetix stakers should be retroactive in nature. 42 | 43 | # Copyright 44 | 45 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 46 | -------------------------------------------------------------------------------- /content/xips/xip-31.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Integrate the WalletConnect API 3 | id: 31 4 | author: winston (@blockchainwinston) 5 | type: core-upgrade 6 | network: Ethereum, Base, Optimism, Arbitrum, Polygon POS, Solana 7 | status: In Review 8 | created: '2024-06-05' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-31 proposes the integration of the WalletConnect API with the Infinex platform. This integration aims to enable connections between Infinex Wallet and decentralized applications (dApps) that support WalletConnect. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Connect to dApps (that supports WalletConnect) with Infinex wallet, using WalletConnect protocol. 19 | 20 | ## Rationale 21 | 22 | 1. Interim Solution for Feature Gaps: Implementing core features such as swapping, staking, lending, and yield farming can be time-consuming. In the interim, integrating WalletConnect provides users with immediate access to these functionalities through external dApps, ensuring they can fully utilize their assets and the DeFi ecosystem without waiting for these features to be developed natively. 23 | 2. Asset Utilization: Currently, stablecoins and other assets sitting idle in users' wallets offer limited utility. With WalletConnect, users can seamlessly use these assets across various DeFi platforms without transferring them out, thereby increasing engagement and retention within the Infinex ecosystem. An example includes staking of USDe. 24 | 25 | ## Technical Specification 26 | 27 | I propose to integrate WalletConnect API with Infinex Wallets. This can be achieved by: 28 | 1. Integrate WalletConnect library into Infinex. 29 | 2. Establish API endpoints to handle connection requests from dApps. 30 | 3. Upgrade Infinex UI to allow users to initiate and manage WalletConnect sessions. 31 | 4. Configure WalletConnect to support connections on Ethereum, Base, Optimism, Arbitrum, Polygon POS, and Solana. 32 | 33 | ## Product considerations 34 | 35 | The original vision for Infinex was to develop and integrate native features such as swapping, staking, lending, and yield farming directly within the platform. While the integration of WalletConnect does not fully align with this long-term vision, it serves as a practical interim solution. This approach enables users to access these critical DeFi functionalities through external dApps, ensuring they can fully utilize their assets in the meantime. 36 | 37 | # Copyright 38 | 39 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 40 | -------------------------------------------------------------------------------- /content/tas/ta-2.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Large USDC Deposits 3 | id: 2 4 | author: Egor (@egorsidelska) 5 | status: Implemented 6 | created: '2024-05-11' 7 | --- 8 | ## Summary 9 | 10 | The Speedrun the Waitlist campaign begins on the 13th of May, 2024. Infinex has received significant interest from large USDC depositors wishing to participate in the campaign, as such the treasury has decided to create a separate incentive for large deposits to not significantly dilute the Governance Point pool. 11 | 12 | ## Overview 13 | 14 | The Speedrun the Waitlist campaign for the launch of the Infinex account is generating significant interest from large USDC holders. The aim of the Speedrun the Waitlist campaign is to incentivise individuals to create Infinex accounts, deposit USDC and earn Governance Points (GP). 15 | 16 | Given the interest we have received so far there is some concern large depositors will dilute the GP earned by smaller individuals creating a poor incentive for users to create accounts and deposit USDC who join later in the campaign. There have been numerous recent incentive campaigns which created poor alignment through dynamics like this and the Infinex Treasury is highly motivated to avoid this. 17 | 18 | To address this the Infinex Treasury has offered USDC depositors with an intent to deposit more than 1m USDC to segregate their deposits from the Speedrun GP pool. They will be ineligible for GP farming but receive a direct incentive from the Infinex Treasury. 19 | 20 | ## Outcome 21 | 22 | Treasury is segregating a portion of committed USDC depositors outside of the GP farming program. 23 | 24 | Segregating large depositors creates a fairer market for smaller contributors. The aim is have smaller depositors benefit from a larger GP distribution.  25 | 26 | ## **Specification** 27 | 28 | While treasury retains discretion to modify incentives, in the interest of disclosure, the Treasury is offering a maximum of 1% (1000 Patron NFTs) for this incentive. 29 | 30 | The minimum requirement to participate is $1m USDC. 31 | 32 | ## **Rationale** 33 | 34 | Excluding large USDC depositors creates a fairer market for the majority of individuals to participate and will result in more meaningful GP earned for these smaller deposits. 35 | 36 | While Infinex aims to incentivise the maximum amount of deposits into the platform, the focus of this campaign is on ensuring the initial depositors have the best chance to earn GP, therefore, this program will be on a first come first serve basis. 37 | 38 | # **Copyright** 39 | 40 | Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/). 41 | -------------------------------------------------------------------------------- /content/tas/ta-3.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Immunifi Bug Bounty 3 | id: 3 4 | author: Egor (@egorsidelska) 5 | status: Implemented 6 | created: '2024-05-30' 7 | --- 8 | 9 | # Summary 10 | 11 | Infinex has approved an Immunifi bug bounty program with a maximum bounty of $1,000,000 USD. 12 | 13 | # Overview 14 | 15 | Immunefi bug bounties are one of the most effective mechanisms for securing production code. By approving a $1,000,000 bounty Infinex is incentivising white-hats to prioritise the review of Infinex's production system. 16 | 17 | # Rationale 18 | 19 | Securing production infrastructure requires a holistic approach, including testing and audits prior to deployment, as well as incentivised bounties post deployment. Immunefi is the industry leading bug bounty platform which aims to attract the best white-hat hackers to properly disclose bugs for a fee. 20 | 21 | # Outcome 22 | 23 | The Immunefi bounty program is live and can be found here: [https://immunefi.com/bug-bounty/infinex/](https://immunefi.com/bug-bounty/infinex/) 24 | 25 | The program includes a variety of critical, high, medium and low level risks Infinex will reward, a high level summary is outlined below: 26 | 27 | Rewards are based on the Immunefi Vulnerability Severity Classification System V2.3. 28 | 29 | **Critical Level Reports** 30 | 31 | - **Reward Amount:** 10% of the directly affected funds, up to USD 1,000,000. 32 | - **Minimum Reward:** USD 50,000 to incentivise reporting. 33 | - **Calculation Basis:** Based on the time and date of the bug report submission. 34 | 35 | **Repeatable Attack Limitations** 36 | 37 | - **Upgradeable/Pausable Contracts:** Only the initial attack is considered for a reward. 38 | - **Non-Upgradeable/Pausable Contracts:** Cumulative impact of repeatable attacks is considered, capped at the maximum critical reward. 39 | 40 | **High Level Reports** 41 | 42 | - **Theft/Permanent Freezing:** Rewards range from USD 5,000 to USD 10,000, depending on the funds at risk. 43 | - **Temporary Freezing:** Reward doubles from the full frozen value for every additional 24 hours of freezing, up to the high reward cap. 44 | 45 | **Reward Payment Terms** 46 | 47 | - **Payouts:** Handled directly by the Infinex team, denominated in USD, but paid in USDC at the team's discretion. 48 | 49 | Treasury has approved a maximum bounty of $1,000,000 USD to Immunefi and will periodically review this bounty and increase it as needed or the TVL of the platform grows. 50 | 51 | # Specification 52 | 53 | The most recent and up to date specification can be found on the immunefi platform under Infinex Bounty. 54 | 55 | [https://immunefi.com/bug-bounty/infinex/](https://immunefi.com/bug-bounty/infinex/) 56 | -------------------------------------------------------------------------------- /content/xips/xip-36.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support ETH & SOL 3 | id: 36 4 | author: kmao (@kmaox), Jaynex (@0xjaynex) 5 | type: core-upgrade 6 | network: Ethereum, Solana 7 | status: Implemented 8 | created: '2024-06-13' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-36 proposes enabling ETH & SOL deposits. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Infinex currently supports USDC and USDE. This XIP proposes expanding support to include ETH and SOL. 19 | 20 | In order to do so, the Infinex Platform will need to be upgraded to support these assets. This will involve enabling support in the EVM Smart Contracts for ETH deposits, tracking deposits of these assets in the Infinex backend, and displaying them in the UI. 21 | 22 | It will also mean adding support for volatile assets in the UI, taking the current market price of the assets in USD into account when displaying total wallet value, as well as the total balance available for staking in campaigns. 23 | 24 | The value of ETH and SOL deposited by users, demoninated in USD and determined by a 3rd-party market price feed, will be counted as TVL for the upcoming [Craterun](https://proposals.infinex.xyz/xips/xip-34) campaign. These assets will be the first volatile assets to be added to Infinex, and be eligible for Craterun rewards, however these will not necessarily be all of the additional supported assets for Craterun. 25 | 26 | ## Rationale 27 | 28 | Expanding support for more assets besides stablecoins will allow Infinex's TVL to continue to grow after the end of STW, and the community has expressed interest in depositing more volatile assets. ETH and SOL are the clearest first two assets to add, given their market cap value and the fact that they are the native assets of chains Infinex currently supports. 29 | 30 | ## Technical Specification 31 | 32 | The supported assets will be 33 | 34 | - Ethereum and Wrapped Ethereum on Ethereum Mainnet, Arbitrum, Optimism, Base, Polygon 35 | - Solana and Wrapped Solana on Solana. 36 | 37 | Specific contract addresses of these assets will be posted in a future RC. 38 | 39 | The Infinex account currently does not block deposits from all Solana coins, which means to support SOL deposits, Infinex will simply just need to upgrade the backend infrastructure to track Solana deposits. 40 | 41 | However, accepting deposits for Ethereum require a contract upgrade, as Ethereum is a native coin, not a token. 42 | 43 | It is expected that a Terms Of Use upgrade and Contract Version Upgrade will need to be accepted by Users to enable ETH and SOL support in the UI. 44 | 45 | # Copyright 46 | 47 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 48 | -------------------------------------------------------------------------------- /content/xips/xip-17.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Wormhole for Deposits 3 | id: 17 4 | author: Axe (@infinAxe), Kain (@kaiynne) 5 | type: integration-upgrade 6 | network: Ethereum & Base & Optimism 7 | status: Implemented 8 | created: '2024-02-05' 9 | updated: '2024-02-05' 10 | --- 11 | # Proposal Summary 12 | 13 | This XIP proposes the use of Wormhole CCTP for processing deposits. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | We propose using Wormhole CCTP to process Infinex deposits. This implementation still relies on the Circle CCTP bridge but adds the security of the Wormhole decentralized guardians to validate transactions. 20 | 21 | ## Rationale 22 | While it would have been possible to rely only on CCTP for USDC bridging, many more assets are expected to be added to Infinex over the coming months. Using the Wormhole CCTP wrapper ensures these assets will conform to the same bridging process, reducing the complexity of future asset integrations. 23 | 24 | ## Technical Specification 25 | 26 | Building on from [XIP-6](https://proposals.infinex.xyz/xips/xip-6), the flow is expanded with the following: 27 | 28 | Instead of calling the Circle CCTP contracts, the deposit account now calls the Wormhole Circle integration. This takes an additional payload in which we specify the recipient of the token. The Wormhole contract transfers the tokens to itself, verifies the payload and parameters emits a message, and calls the Circle CCTP contract, which in turn burns the tokens, and emits a message. 29 | 30 | In addition to calling Circle to get the attestation of the CCTP message, we also call Wormhole which uses its decentralized guardians to verify the Wormhole message and provide attestation. 31 | 32 | Instead of calling the Circle CCTP contract on the target chain, we now call the Infinex account which is the intended recipient. This is required as wormhole only allows transfers from and to the same address, this also provides additional security and surety that the funds are going to the intended account. Wormhole verifies the attestation, and calls Circle CCTP, which in turn validates its attestation, before minting the tokens to the intended account. 33 | 34 | This diagram details the updated cross-chain flow for a deposit: 35 | 36 | ![](/assets/xips/xip-17/image.png) 37 | 38 | Unfortunately, due to the account to account check, the withdrawal flow will still have to be processed via Circle CCTP, as we do not have the ability to ensure that the recipient will call the Wormhole contract with the necessary attestation. 39 | 40 | ## Test Cases 41 | 42 | The flow has been tested on Sepolia and Base Sepolia. 43 | 44 | # Copyright 45 | 46 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 47 | -------------------------------------------------------------------------------- /content/xips/xip-35.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Interim Withdrawals 3 | id: 35 4 | author: Jaynex (@0xjaynex) 5 | type: core-upgrade 6 | status: Implemented 7 | created: '2024-06-13' 8 | --- 9 | # Proposal Summary 10 | 11 | This XIP proposes an interim version of withdrawals that uses the Funds Recovery specified in [XIP-23](https://proposals.infinex.xyz/xips/xip-23) and already implemented for Speedrun The Waitilist, to allow users to withdraw funds from their accounts as close as possible to the end of the Speedrun campaign. 12 | 13 | # Specification 14 | 15 | ## Overview 16 | 17 | A fully functional and secure spec for how users will withdraw funds from Infinex, or send funds to other addresses, is yet to be finalised and built. Additionally, as specified in [XIP-23](https://proposals.infinex.xyz/xips/xip-23), more sophisticated withdrawals / send functionality will require users to opt into an account upgrade. 18 | 19 | With the end of Infinex's Speedrun The Waitlist campaign in mind, the Core Working Group has identified a way to safely unlock funds in the protocol for users who wish to withdraw. 20 | 21 | We propose to add UI to the Infinex App which uses the Funds Recovery functionality in the contracts to allow withdrawals, and signs the transaction with the user's Sudo Key. 22 | 23 | ## Rationale 24 | 25 | Transferring the entire asset balance per chain is a limitation of using the existing Funds Recovery functionality, but it seems preferable to unlock funds than continue to block withdrawals until work on the full withdraw/send functionality has been completed. 26 | 27 | ## Technical Specification 28 | 29 | Funds recovery allows users to send the entire balance of a single asset (e.g USDC) on a single chain (e.g Ethereum) to the Funds Recovery Address that was set up before the User deposited the asset into their Infinex Account. 30 | 31 | A new screen will be added to the Infinex App listing each asset in the account, on each chain, and present the user with a button to transfer the entire balance to the funds recovery address. The user will sign the transaction by unlocking their Passkey. 32 | 33 | Constraints will be: 34 | 35 | - Only the entire balance of a specific asset on a specific chain will be transferred 36 | - The assets can only be transferred to the pre-set Recovery Address 37 | 38 | If a user only wants to transfer some of their assets from their account to another address, they will have to withdraw the entire balance and re-deposit the amount they want to leave in their Infinex account. 39 | 40 | Functionality to send a specific amount of an asset to any address will be specified and implemented separately. 41 | 42 | # Copyright 43 | 44 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 45 | -------------------------------------------------------------------------------- /content/xips/xip-69.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Initial Support for NFTs 3 | id: 69 4 | author: kmao (@kmaox), Jaynex (@0xjaynex) 5 | type: core-upgrade 6 | network: Ethereum 7 | status: Implemented 8 | created: '2024-08-19' 9 | updated: '2024-08-27' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-69 proposes initial support for NFTs. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | This proposal aims to upgrade the Infinex Platform to provide initial support for NFTs. The Infinex Account can currently receive NFTs, however, lacks an interface for users to be able to smoothly deposit and withdraw their NFTs. The Infinex Platform will be updated to: 20 | 21 | - Reflect supported NFTs in a user's wallet. 22 | - Allow users to deposit and withdraw supported NFTs. 23 | 24 | Depending on CWG R&D, the Infinex platform should also be updated to reflect the rough price of NFT based on the last sale and collection floor price. Due to technical complexity, as well as low liquidity / rarity / and other concerns regarding showing NFT prices, this may be implemented subsequently to basic NFT custody. 25 | 26 | Due to the wide range of risks associated with accepting all NFTs, Infinex will only support a limited range of NFTs initially. These collections are part of the prizes associated with Craterun, and are: 27 | 28 | - [Sappy Seals](https://blur.io/eth/collection/sappy-seals) 29 | - [Lil Pudgies](https://blur.io/eth/collection/lilpudgys) 30 | 31 | ## Rationale 32 | 33 | Infinex aims to become the UX layer for all of crypto, which includes supporting NFTs. Broader NFT support is planned in the future, however initially supporting a small collection makes it easier for Infinex to iterate on NFT support. 34 | 35 | Sappy Seals and Lil Pudgies were selected as the first collections to be supported as they are included in the Craterun Prizes, and are required to be supported in order for the winners to interact with their prizes. 36 | 37 | ## **Technical Specification** 38 | 39 | Infinex will add functionality for users to view their Sappy Seals and Lil Pudgies in-app. Functionality to deposit and withdraw these assets will also be added. The token addresses for these collections are: 40 | 41 | {% table %} 42 | --- 43 | - Collection 44 | - Network 45 | - Address 46 | --- 47 | - Sappy Seals 48 | - Ethereum Mainnet 49 | - 0x364C828eE171616a39897688A831c2499aD972ec 50 | --- 51 | - Lil Pudgies 52 | - Ethereum Mainnet 53 | - 0x524cAB2ec69124574082676e6F654a18df49A048 54 | {% /table %} 55 | 56 | In order to implement these upgrades, Infinex will simply need to upgrade the backend infrastructure to track these assets, and also reflect it in the UI. 57 | 58 | # Copyright 59 | 60 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 61 | -------------------------------------------------------------------------------- /content/xips/xip-55.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support BlazeStake Staked Solana 3 | id: 55 4 | author: kmao (@kmaox), SolBlaze (@SolBlazeDev) 5 | type: core-upgrade 6 | network: Solana 7 | status: Implemented 8 | created: '2024-07-04' 9 | updated: '2024-07-18' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-55 proposes enabling support for BlazeStake Staked SOL. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Infinex already supports another Solana LST (JITOSOL), and aims to add additional one, being BSOL. 20 | 21 | Infinex will need to update the UI to effectively reflect BSOL deposits and withdrawals, as well as the current market price of the asset. The value of BSOL will be denominated in USD and determined by a 3rd-party market price feed and will also be counted as TVL for the upcoming [**Craterun**](https://proposals.infinex.xyz/xips/xip-34) campaign. 22 | 23 | Furthermore, BlazeStake has offered 70 MIL BLZ in Ecosystem Prizes for the Craterun Campaign. This will be split between 5 different prizes of 14 MIL BLZE each, and will take up 5 slots of the approved 69 ecosystem prizes, as per [XIP-34](https://proposals.infinex.xyz/xips/xip-34). 24 | 25 | ## Rationale 26 | 27 | bSOL is one of the main LSTs on Solana with $300m+ in TVL. In addition, bSOL is used heavily throughout Solana DeFi, with over half of all bSOL tokens deployed in various lending and liquidity protocols across the Solana ecosystem including Kamino, Solend, Drift, marginfi, Hawksight, Meteora, Orca, and Raydium. Furthermore, bSOL features the widest validator set of any Solana stake pool, showcasing its commitment to decentralization. 28 | 29 | Creative incentive programs are at the core of bSOL's culture. bSOL pioneered many of the concepts behind liquid staking airdrops on Solana that have inspired other protocols across the ecosystem. Incentive mechanisms have also been used to harness the capabilities of bSOL to help bootstrap liquidity for more than a dozen new token launches on Solana, including the popular JUP token from Jupiter (the bSOL-JUP pair is the largest liquidity pool for JUP across all of Solana). 30 | 31 | Given its wide-ranging usage throughout the Solana DeFi ecosystem paired with an innovative incentives-driven culture, bSOL would be a perfect fit for an integration into Infinex, especially with the upcoming Craterun campaign. 32 | 33 | ## Technical Specification 34 | 35 | Infinex will add BSOL on the Solana network. The token address is bSo13r4TkiE4KumL71LsHTPpL2euBYLFx6h9HP3piy1 36 | 37 | The Infinex account currently does not block deposits from all Solana coins, which means to support SOL deposits, Infinex will simply just need to upgrade the backend infrastructure to track BSOL deposits. 38 | 39 | # Copyright 40 | 41 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 42 | -------------------------------------------------------------------------------- /content/xips/xip-27.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Airdrop GP to Memecoins Instead of NFTs 3 | id: 27 4 | author: piotrmisiurek (@piotrmisiurek) 5 | type: integration-upgrade 6 | network: Base, Ethereum, Solana 7 | status: Rejected 8 | created: '2024-05-15' 9 | --- 10 | 11 | # Proposal Summary 12 | 13 | Airdrop GPs to top-tier memecoin communities instead of NFTs. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Remove GP allocations for NFT holders and assign them to top-tier memecoin holders (PEPE, WIF, DEGEN). 20 | 21 | The idea is to remove GP allocation from NFT collections: Pudgy Penguin, Milady Maker, Berachain, or Mad Lads. Instead, allocate those points to top-tier meme holders on the most active chains: Ethereum (PEPE), Base (DEGEN), and Solana (WIF). 22 | 23 | As memecoins have many more holders than NFTs and we want to airdrop meaningful allocations, two mechanisms will be implemented: 24 | - Minimum holdings threshold 25 | - Limited number of allocations: first come, first served 26 | 27 | ## Rationale 28 | 29 | We use GP airdrops as a marketing tool to attract more users to Infinex. Memecoins are a better choice than NFTs for several reasons. 30 | 31 | The communities of the largest memecoins are significantly larger than those of NFTs. In this cycle, they are also much more active. Since the entry barrier is considerably lower, this group also features greater diversity. A larger percentage of these communities are potential users of Infinex. 32 | 33 | ## Technical Specification 34 | 35 | We remove allocations for NFT collections: 36 | * Pudgy Penguin (19,553,600 GPs) 37 | * Milady (20,000,000 GPs) 38 | * Berachain (10,027,600 GPs) 39 | * MadLads (19,939,000 GPs) 40 | 41 | As a result, we have 69,520,200 GPs to allocate. 42 | 43 | We use them to reward top-tier memecoin holders: 44 | - PEPE (Ethereum) 45 | - WIF (Solana) 46 | - DEGEN (Base) 47 | 48 | For NFTs, we allocated from 2,000 to 4,000 GPs per NFT holder. As we want to target a broader audience, we change the allocation to 1,000 GP per user. This allows us to serve more people while still making the allocation significant. As a result, we can distribute to 69,520 top-tier memecoin holders. 49 | 50 | As there are many more top-tier memecoin holders than that, we implement two additional mechanisms: 51 | - First come, first served. You need to actively claim your GPs by depositing 50 USDC into your Infinex account. 52 | - Minimum holding value of 50 USDC. This allows small holders to claim but cleans up the dust. Why 50 USD? We use the same number as the deposit condition. 53 | 54 | The holder snapshot will be taken after STW concludes (June 13th). 55 | 56 | #### Keng Lernitas Airdrop 57 | 58 | This XIP doesn't modify rules for the Keng Lernitas airdrop. 59 | 60 | # Copyright 61 | 62 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 63 | -------------------------------------------------------------------------------- /content/xips/xip-61.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Rocket Pool ETH 3 | id: 61 4 | author: fleb (@fleb__) 5 | type: integration-upgrade 6 | network: Ethereum 7 | status: Implemented 8 | created: '2024-07-17' 9 | updated: '2024-07-24' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-61 proposes enabling support for Rocket Pool ETH 14 | 15 | # Specification 16 | 17 | ## Overview 18 | Rocket Pool's $RETH is a decentralized liquid staking token for Ethereum (ETH). Rocket Pool lowers the entry barrier for Ethereum staking to as little as 0.01 ETH, making it accessible to more users. It utilizes decentralized node operators who need only 16 ETH to run a validator node, with the remaining 16 ETH pooled from other users' contributions. 19 | Users who contribute to the staking pool receive $RETH tokens, which represent their staked ETH and accrue value over time based on the staking rewards earned by node operators. This makes $RETH an appreciating asset relative to ETH. 20 | The protocol emphasizes security and decentralization, with measures including audits from ConsenSys Diligence and an insurance mechanism using its native RPL token. Rocket Pool also features a fully on-chain DAO for governance, enhancing its decentralized nature and flexibility in staking setups. 21 | Rocket Pool's approach not only increases participation in Ethereum's Proof-of-Stake system but also contributes to the network's security and decentralization. 22 | 23 | Infinex will need to update the UI to effectively reflect RETH deposits and withdrawals, as well as the current market price of the asset. The value of these assets will be denominated in USD and determined by a 3rd-party market price feed and will also be counted as TVL for the Craterun campaign. 24 | 25 | ## Rationale 26 | Infinex currently supports Solana LST Protocol Jito and their$JTOSOL (SOL), this gives an opportunity to support an Ethereum LST protocol Rocket Pool and their $RETH (ETH) token. 27 | 28 | ## Technical Specification 29 | 30 | Infinex already has support for EVM tokens, so it just needs to update the backend to support the new token on Ethereum. The proposed token addresses are listed below. 31 | 32 | {% table %} 33 | - Coin 34 | - **Network** 35 | - **Token Address** 36 | --- 37 | - RETH 38 | - Ethereum Mainnet 39 | - 0xae78736cd615f374d3085123a210448e74fc6393 40 | --- 41 | - RETH 42 | - Optimism 43 | - 0x9bcef72be871e61ed4fbbc7630889bee758eb81d 44 | --- 45 | - RETH 46 | - Base 47 | - 0xb6fe221fe9eef5aba221c348ba20a1bf5e73624c 48 | --- 49 | - RETH 50 | - Arbitrum One 51 | - 0xec70dcb4a1efa46b8f2d97c310c9c4790ba5ffa8 52 | --- 53 | - RETH 54 | - Polygon POS 55 | - 0x0266f4f08d82372cf0fcbccc0ff74309089c74d1 56 | {% /table %} 57 | 58 | 59 | # Copyright 60 | 61 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 62 | -------------------------------------------------------------------------------- /content/xips/xip-45.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: GP Distribution to Sappy Seals 3 | id: 45 4 | author: mooney (@mooneynft) 5 | type: community 6 | network: Base 7 | status: Implemented 8 | created: '2024-06-21' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-45 proposes to distribute a portion (8,050,000 GP) of the GP Reserve Fund to [Staked Sappy Seals](https://x.com/SappySealsNFT). 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Infinex, as of this proposal has allocated GP to NFT projects such as Mad Lads, Pudgy Penguins and Milady Maker. This proposal proposes to include Sappy Seals in the GP Reserve Fund distribution, specifically Seals that are staked. By doing so, Infinex onboards undeniably one of the strongest communities present in Web3. 19 | 20 | ## Rationale 21 | 22 | As outlined in [XIP-26](https://proposals.infinex.xyz/xips/xip-26), Infinex established a GP Reserve Fund to collaborate with more communities. Infinex then opened a [form via X](https://x.com/infinex_app/status/1793325976149184838) for communities to request a portion of the fund and why they are deserving of the airdrop. Below describes the rationale behind adding Sappy Seals into the GP distribution to communities. 23 | 24 | Airdrops are a powerful marketing tool to onboard high-quality participants into your ecosystem. The Sappy Seals have fostered a strong community since 2021 who are committed to decentralization, making them a great fit for the Infinex community. With over 4500 unique holders and 70% of the collection staked, the Seals community demonstrate their strong conviction in the long-term vision of the Seals. Distributing GP to Seals boosts Infinex's marketing and attracts quality individuals to their ecosystem. 25 | 26 | Onboarding the Seals has proven to be effective, as seen in Nifty Islands airdrop campaign, where the Seals are the largest and most active community, resulting in them receiving the highest allocation for $ISLAND ([Exhibit A](https://x.com/wabdoteth/status/1754195562625220691), [Exhibit B](https://www.niftyisland.com/communities)). Furthermore, the proposal suggests that GP is only distributed to Staked Sappy Seals, ensuring GP is given to long-term community members. 27 | 28 | ## Technical Specification 29 | Recipients of the airdrop are required to sign up for an Infinex account and deposit at least 50 USDC into their account. Users will be able to connect and verify their wallets, then claim their GP directly into their Infinex account. 30 | 31 | 8,050,000 GP from the GP Reserve Fund will be distributed to the Sappy Seals accordingly: 32 | 33 | Staked Sappy Seals - 8,050,000 GP 34 | 35 | - Distribute 8,050,000 GP to [Staked Sappy Seals](https://opensea.io/collection/stakedseals). This is approximately 1.28% of the total GP supply (given supply is 630m). 36 | - This equates to 1150 per Staked Sappy Seal (7000 Staked Seals). 37 | 38 | # Copyright 39 | 40 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 41 | -------------------------------------------------------------------------------- /content/xips/xip-71.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Gaming Tokens 3 | id: 71 4 | author: kmao (@kmaox) 5 | type: core-upgrade 6 | network: Ethereum, Polygon, Solana, Base 7 | status: Implemented 8 | created: '2024-08-25' 9 | updated: '2024-08-30' 10 | --- 11 | # Proposal Summary 12 | 13 | XIP-71 proposes support for more assets; IMX, BEAM, GALA, AXS, SAND, APE, GMT, ILV, GODS, GHST, GOG, PRIME. 14 | 15 | # Specification 16 | 17 | ## Overview 18 | 19 | Infinex will need to update the UI to effectively reflect the deposits and withdrawals of these assets, as well as the current market price of them. The value of these assets will be denominated in USD and determined by a 3rd-party market price feed. 20 | 21 | ## Rationale 22 | 23 | Gaming tokens make up a large portion of the crypto market cap, and are a necessary asset for Infinex to support. Adding these additional assets can help boost Infinex's existing TVL. 24 | 25 | ## Technical Specification 26 | 27 | A list of the supported token, network, and token address can be found below. Infinex will add support for deposit and withdrawals for all of the listed tokens. 28 | 29 | {% table %} 30 | - **Token** 31 | - **Network** 32 | - **Token Address** 33 | --- 34 | - IMX 35 | - Mainnet 36 | - 0xf57e7e7c23978c3caec3c3548e3d615c346e79ff 37 | --- 38 | - BEAM 39 | - Mainnet 40 | - 0x62d0a8458ed7719fdaf978fe5929c6d342b0bfce 41 | --- 42 | - GALA 43 | - Mainnet 44 | - 0xd1d2eb1b1e90b638588728b4130137d262c87cae 45 | --- 46 | - AXS 47 | - Mainnet 48 | - 0xbb0e17ef65f82ab018d8edd776e8dd940327b28b 49 | --- 50 | - SAND 51 | - Mainnet 52 | - 0x3845badade8e6dff049820680d1f14bd3903a5d0 53 | --- 54 | - SAND 55 | - Polygon 56 | - 0xbbba073c31bf03b8acf7c28ef0738decf3695683 57 | --- 58 | - APE 59 | - Mainnet 60 | - 0x4d224452801aced8b2f0aebe155379bb5d594381 61 | --- 62 | - APE 63 | - Polygon 64 | - 0xb7b31a6bc18e48888545ce79e83e06003be70930 65 | --- 66 | - GMT 67 | - Solana 68 | - 7i5KKsX2weiTkry7jA4ZwSuXGhs5eJBEjY8vVxR4pfRx 69 | --- 70 | - GMT 71 | - Polygon 72 | - 0x714db550b574b3e927af3d93e26127d15721d4c2 73 | --- 74 | - GMT 75 | - Mainnet 76 | - 0xe3c408bd53c31c085a1746af401a4042954ff740 77 | --- 78 | - ILV 79 | - Mainnet 80 | - 0x767fe9edc9e0df98e07454847909b5e959d7ca0e 81 | --- 82 | - GODS 83 | - Mainnet 84 | - 0xccc8cb5229b0ac8069c51fd58367fd1e622afd97 85 | --- 86 | - GHST 87 | - Mainnet 88 | - 0x3f382dbd960e3a9bbceae22651e88158d2791550 89 | --- 90 | - GHST 91 | - Polygon 92 | - 0x385eeac5cb85a38a9a07a70c73e0a3271cfb54a7 93 | --- 94 | - GHST 95 | - Base 96 | - 0xcd2f22236dd9dfe2356d7c543161d4d260fd9bcb 97 | --- 98 | - GOG 99 | - Mainnet 100 | - 0x9ab7bb7fdc60f4357ecfef43986818a2a3569c62 101 | --- 102 | - PRIME 103 | - Mainnet 104 | - 0xb23d80f5fefcddaa212212f028021b41ded428cf 105 | --- 106 | - PRIME 107 | - Base 108 | - 0xfa980ced6895ac314e7de34ef1bfae90a5add21b 109 | {% /table %} 110 | 111 | # Copyright 112 | 113 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 114 | -------------------------------------------------------------------------------- /content/xips/xip-54.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Support Super Symbiotic LRT' 3 | id: 54 4 | author: blockchainwinston (@blockchainwinston) 5 | type: integration-upgrade 6 | network: Ethereum 7 | status: In Review 8 | created: '2024-06-25' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-54 proposes enabling support for Super Symbiotic LRT (weETHs). 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Super Symbiotic Liquid Restaking Token (LRT) is an automated vault that earns you Symbiotic, Veda and ether.fi points on your liquid staking assets. Currently, there is an increasing hype towards those points, as it can be seen my the increasing TVL locked in the vault ($129 million now). 19 | 20 | ## Rationale 21 | 22 | Symbiotic is a decentralized finance (DeFi) protocol designed to provide a flexible and permissionless framework for restaking. It allows networks to customize their staking implementations, leveraging the security of existing ecosystems. The protocol supports multiple ERC-20 tokens and aims to enhance security and incentivize adherence to protocol rules through a modular design. Symbiotic is backed by prominent investors such as Paradigm and Lido co-founders. 23 | 24 | Veda is a native yield layer that tokenizes complex DeFi interactions, allowing protocols to embed yield directly into their user experience. It integrates with various DeFi platforms to optimize asset yields across blockchains. Veda's technology is utilized by Ether.Fi, significantly boosting its total value locked (TVL) to $700 million. This protocol simplifies DeFi participation by providing a user-friendly interface and enforcing verifiable on-chain restrictions for secure capital allocation. 25 | 26 | EtherFi is a liquid staking platform that collaborates with Veda to enhance its liquid staking products. It allows users to stake assets while maintaining liquidity, benefiting from increased yields and simplified access to DeFi strategies. 27 | 28 | All three protocols are huge and becoming increasing popular. Symbiotic staking caps has been fully filled. Veda has many strong institution backings. I am certain that with the inclusion of weETHs, our TVL will grow a lot. 29 | 30 | ## Technical Specification 31 | 32 | Infinex will add support for deposits and withdrawals of Super Symbiotic LRT (weETHs) on Ethereum mainnet. The accepted chain, and token address are listed below: 33 | 34 | {% table %} 35 | - Network 36 | - Token Address 37 | --- 38 | - Mainnet 39 | - 0x917ceE801a67f933F2e6b33fC0cD1ED2d5909D88 40 | {% /table %} 41 | 42 | The Infinex account currently does not block deposits from all ERC-20 tokens, which means to support weETHs deposits, Infinex will simply just need to upgrade the backend infrastructure to track those deposits. 43 | 44 | In order to track Symbiotic, Veda and ether.fi points accrued by the user, Infinex will push a later update, via an RC, which will let the user see how much points they've accrued from holding weETHs. 45 | 46 | # Copyright 47 | 48 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 49 | -------------------------------------------------------------------------------- /content/wgcs/wgc-6.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | id: 6 3 | title: Establish a Cross-Chain WG 4 | wgName: Cross-Chain Working Group 5 | wgLead: Tonyjin (@tonyjin) 6 | author: Tonyjin (@tonyjin), Bilby (@bilb-y) 7 | status: Implemented 8 | budget: N/A 9 | budgetCadence: N/A 10 | timeline: Indefinitely 11 | created: '2024-01-30' 12 | --- 13 | ### Working Group Name 14 | 15 | Cross-Chain Working Group (XCWG) 16 | 17 | ### Working Group Lead 18 | 19 | Discord: `tonyjin_wl` 20 | 21 | Github: `tonyjin` 22 | 23 | ### Outcomes 24 | 25 | To compete with centralized exchanges, Infinex will need to serve as a gateway to decentralized applications across multiple ecosystems, while seamlessly abstracting away token bridging and blockchains from the perspective of the user. Achieving this will require cross-chain messaging that is scalable, secure, and doesn't compromise on security or trustlessness. 26 | 27 | W7, Aka "Wormhole Labs" have been researching decentralized cross-chain messaging since 2021, and have developed multiple products that enable secure abstraction of blockchains. Namely relevant for this proposal: 28 | 29 | - Wormhole Connect: Embeddable frontend component that enables low-cost cross-chain asset transfers with destination gas dropoff 30 | - Wormhole CCTP: Native USDC transfers composed with Wormhole messages 31 | - Token Bridge: Enables cross-chain asset transfer by locking native tokens and minting synthetic representations 32 | - Standard Relayer: Enables Wormhole core messaging integrations without the need to run off-chain relayer infrastructure. Powered by a network of decentralized relayers 33 | - Wormhole Queries: Decentralized reads of on-chain data attested by Wormhole's validator (Guardian) set 34 | - Cross-chain Governance: The casting of votes across multiple chains as well as the execution of governance decisions 35 | - Wormhole Native Token Transfers (NTT): Burn and mint token bridging solution with custom rate limiting for enhanced security. 36 | 37 | The XCWG will be led by Tony Jin, Co-Founder & CTO of Wormhole Labs, to investigate and propose cross-chain infrastructure to scale Infinex across multiple ecosystems: 38 | 39 | - Token Bridging 40 | - Cross-chain Messaging 41 | - Cross-chain Token Swaps 42 | - Cross-chain Governance 43 | - New Chain Expansion Advisement 44 | 45 | The XCWG will also collaborate with the Core Working Group to investigate and propose integrations that leverage cross-chain infrastructure, with an emphasis on non-EVM ecosystems like Solana ecosystem. They will also assist the Core Working Group in acquiring rust engineering resources. 46 | 47 | # Budget 48 | 49 | ### Budget Rationale 50 | 51 | The XCWG will collaborate with the Core Working Group as an in-kind contribution to the protocol. They won't require a cash budget from the Infinex treasury for the foreseeable future. 52 | 53 | # Timeline 54 | 55 | ### Timeline Rationale 56 | 57 | The working group will be established indefinitely. 58 | 59 | ### Release Candidate Frequency 60 | 61 | The nature of the work proposed by the XCWG will require a proposal via XIPs. Any release candidates will be released on an ad hoc basis. 62 | -------------------------------------------------------------------------------- /content/xips/xip-42.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support Jito Staked Solana 3 | id: 42 4 | author: kmao (@kmaox), AndrewT (@agsthurman) 5 | type: integration-upgrade 6 | network: Solana 7 | status: Implemented 8 | created: '2024-06-18' 9 | --- 10 | # Proposal Summary 11 | 12 | XIP-42 proposes enabling support for Jito Staked Solana. 13 | 14 | # Specification 15 | 16 | ## Overview 17 | 18 | Infinex currently supports USDC and USDE, with ETH and SOL support also approved. Adding a yield accruing LST like JITOSOL to Infinex will further grow TVL, and incentive users who are simply holding JITOSOL, to deposit into Infinex, as there will be minimal opportunity cost. 19 | 20 | Infinex will need to update the UI to effectively reflect JITOSOL deposits and withdrawals, as well as the current market price of the asset. The value of JITOSOL will be denominated in USD and determined by a 3rd-party market price feed and will also be counted as TVL for the upcoming [**Craterun**](https://proposals.infinex.xyz/xips/xip-34) campaign. 21 | 22 | Furthermore, Jito has offered 20k JTO in Ecosystem Prizes for the Craterun Campaign. This will be split between 10 different prizes of 2,000 JTO each, and will take up 10 slots of the approved 69 ecosystem prizes, as per [XIP-34](https://proposals.infinex.xyz/xips/xip-34). 23 | 24 | ## Rationale 25 | 26 | JitoSOL is the largest LST on Solana, currently accounting for $1.5 billion in TVL. Apart from its size, it’s proven to be an especially popular form of collateral in Solana DeFi. JitoSOL accounts for nearly 50% of the TVL in the Drift perps DEX, and additionally accounts for over 20% of the TVL for Solana-leading lending and liquidity platforms Kamino and MarginFi.  27 | 28 | During points and incentive programs on Solana in the past six months, JitoSOL has likewise been highly overrepresented. At times JitoSOL accounted for over 30% of Sanctum’s pool during the points campaign, and ran as high as 30% of Kamino’s TVL while the platform’s initial points program was ongoing.  29 | 30 | Finally, research from analytics firm Gauntlet indicates that the core userbase for JitoSOL is DeFi-active whales.  31 | 32 | In aggregate, this data shows that JitoSOL is an ideal asset to onboard to Infinex during the forthcoming Craterun Campaign: a capital efficient form of collateral favored by power users who like to farm incentives.  33 | 34 | Additionally, this integration and the TVL it ideally drives will set the stage for larger and more complex integrations, possibly leveraging JitoSOL as a cross-chain asset, in the future.  35 | 36 | ## Technical Specification 37 | 38 | Infinex will add functionality to deposit and withdraw JITOSOL on the Solana network. 39 | 40 | The token address is ``J1toso1uCk3RLmjorhTtrVwY9HJ7X8V9yYac6Y7kGCPn`` 41 | 42 | The Infinex account currently does not block deposits from Solana tokens, which means to support JITOSOL deposits & withdrawals, Infinex will simply just need to upgrade the backend infrastructure to track them. 43 | 44 | # Copyright 45 | 46 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 47 | -------------------------------------------------------------------------------- /content/rcs/rc-2.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Release Pre-Alpha Infinex to Mainnet 3 | id: 2 4 | wg: Core WG 5 | author: Jed (@jedwatson), kmao (@kmaox) 6 | status: Implemented 7 | created: '2023-12-20' 8 | updated: '2023-12-20' 9 | implemented: '2023-12-21' 10 | --- 11 | ## Pre-alpha Release 12 | 13 | ### Overview 14 | 15 | The Core WG has prepared the Infinex App and Service to be deployed to production so that Invited Users can sign up for Infinex Accounts and trade on Mainnet. 16 | 17 | --- 18 | 19 | ### Outcome 20 | 21 | Release a pre-alpha build of Infinex to Mainnet, so invited users can create an Infinex Account, and execute perps trades on Synthetix V3. 22 | 23 | Features include: 24 | 25 | - Users can create accounts if their email is on the Infinex Pre-Alpha Guest List 26 | - The Infinex account is associated with a user in the production Stytch project 27 | - The Browser Key is created locally and secured 28 | - The MFA and Recovery Keys are created and stored by the Lit Protocol 29 | - Users can log in from additional devices, with additional Browser Keys created and added to the Smart Contracts 30 | - Users' wallets are funded with USDC by Infinex when accounts are created 31 | - When logged in, Users can see the Trading UI and execute trades 32 | 33 | --- 34 | 35 | ### Proposed Changes 36 | 37 | **Infinex App & Platform** 38 | 39 | This is, generally, the same functionality that has been deployed to Testnet, with the following differences: 40 | 41 | - The system is integrated with Lit for 2FA and Recovery Key handling 42 | - Users can log in from multiple devices with the same Infinex Account 43 | - The system is ready to run on Mainnet 44 | 45 | The following limitations are in effect: 46 | 47 | - All funds are provided by Infinex 48 | - Users are not able to deposit or withdraw funds 49 | - Less than the full functional scope and polish of Infinex Alpha is implemented 50 | 51 | The release should be deployed on a mix of Vercel, Cloudflare, PlanetScale, and AWS (as appropriate) managed by the Infrastructure WG. 52 | 53 | --- 54 | 55 | **Infinex Marketing** 56 | 57 | - Updates to the Infinex public website ([infinex.xyz](http://infinex.xyz/)), including various copy and asset changes 58 | - Commencement of the “Infinex 13” marketing campaign (as per the foundations set by [XIP-5](https://proposals.infinex.xyz/xips/xip-5-skinny-alpha-launch)), which will continue until all thirteen members of the Infinex Alpha are finalized, and includes: 59 | - Marketing posts on the Infinex (@infinex_app) Twitter including launch announcements, trader profiles, #infinex13, and feature showcases of the Infinex app. 60 | - Publication of a Mirror article outlining the core thinking and innovations of the Infinex Account. 61 | - Commencement of a $SNX and $ETH guessing competition in the Infinex Discord, ending December 25th (1PM UTC), that is determined by the closest guess by percentage difference. This figure will be averaged across both SNX and ETH. 62 | - Participation in podcasts and other media (if and as opportunities arise) 63 | 64 | --- 65 | 66 | # Copyright 67 | 68 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 69 | -------------------------------------------------------------------------------- /content/xips/xip-12.mdoc: -------------------------------------------------------------------------------- 1 | --- 2 | title: Patron NFT 3 | id: 12 4 | author: Egor (@egorsidelska), kmao (@kmaox) 5 | type: core-upgrade 6 | network: Ethereum 7 | status: Superseded 8 | supersededby: XIP-33 9 | created: '2024-01-23' 10 | updated: '2024-07-18' 11 | --- 12 | # Proposal Summary 13 | 14 | The Patron NFT enables contributions to the Infinex Treasury. 15 | 16 | # Specification 17 | 18 | ## Overview 19 | 20 | Following the election of the Treasury Seat, Infinex requires a mechanism for funding the protocol. This XIP details a "Patron NFT" design, which will enable contributions to the Infinex Treasury. 21 | 22 | ## Rationale 23 | 24 | In [Infinex's Governance 1.0](https://vote.infinex.io/#/proposal/0x98619961d046180aedf60cdf7ab237eb0ef1e22ccaf728c05d346d9847c581b0:~:text=The%20Treasury%20seat%20will%20be%20responsible%20for%20managing%20the%20treasury%20and%20will%20use%20funds%20to%20bootstrap%20the%20project%20and%20ensure%20its%20long%2Dterm%20sustainability.), the responsibility of managing the treasury and using said funds to bootstrap the project was granted to the Treasury Seat. In Infinex's Governance 1.1 upgrade, Infinex aimed to elect a Treasury Seat to ensure Infinex has sufficient capital to fund Working Groups and other protocol expenses. The Treasury Seat is primarily responsible for funding Working Groups by maintaining adequate operating capital. Furthermore, additional expenses are covered from Treasury, such as: 25 | 26 | - Operational overhead 27 | - Growth and marketing incentives 28 | - Contributor alignment 29 | 30 | In creating an NFT to represent these contributions, the Council recognises these individuals are Patrons, referencing the name, Patron NFTs. 31 | 32 | Given the competitive nature of the DeFi space and the high capital requirements of Infinex development, this XIP will enable the Treasury Seat to enter into agreements before the actual deployment of the Patron NFT to ensure continuity of funding for all Infinex Working Groups. Patron NFTs may also be used as incentives for non-financial contributions to the Infinex Protocol. 33 | 34 | The Treasury Seat is expected to collaborate with the Infinex Council to implement the Patron NFT, particularly the Core Contributor Seat, responsible for the deployment of the Patron NFT. 35 | 36 | ## Technical Specification 37 | 38 | **The Patron NFT** 39 | 40 | Each Patron NFT will be mintable via a mint pass, the cost to mint each pass will be set at the time of issuance by the Treasury Seat. Patron NFT has no implicit rights. A maximum of 100,000 Patron NFTs can be minted. 41 | 42 | Patron NFTs mint passes can be issued over multiple 'rounds', which have the following properties: 43 | 44 | - Round supply 45 | - Mint cost/s 46 | - Mint token/s 47 | 48 | In order to mint a Patron NFT, the holder of a mint pass must pay the minting cost to the Patron NFT contract. Mint passes act as an allowlist for Infinex Patrons and will be distributed by the Treasury Seat. There is no limit to how many mint passes can be created for a single round. Mint fees will be distributed to the Infinex Treasury. 49 | 50 | # Copyright 51 | 52 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 53 | --------------------------------------------------------------------------------