Fig.1 - How the Brian Architecture works
OpenAI GPT models vs Brian models
| Action | Description | Capabilities | Eg. prompts |
|---|---|---|---|
| Swap | Swap any token through the LI. FI and ENSO solvers |
|
|
| Bridge | Bridge any token through the LI. FI and ENSO solvers. *All the available chains on Brian are possible destination chains. |
|
|
| Crosschain swap | Cross-chain swap any token through the LI. FI and ENSO solvers. *All the available chains on Brian are possible destination chains. |
|
|
| Transfer | Transfer any token to an addres or ENS. *Always check the address associated to the ENS. |
|
|
| Wrap | Wrap any native token. |
|
|
| Unwrap | Unwrap any native token. |
|
|
| Register ENS | Register an ENS and set it as primary address. |
|
|
| Renew ENS | Renew an ENS. |
|
|
| Check ENS availability, expiration, registrations and renewal cost. | (Read actions) Perform a series of operations with ENS |
|
|
| Resolve ENS <--> Address | (Read actions) ENS resolution is the process of mapping an address to an ENS and vice versa |
|
|
| Deposit | Deposit ETH and other tokens into DeFi protocols |
|
|
| Withdraw | Withdraw ETH and other tokens from DeFi protocols |
|
|
| Borrow | borrow tokens ETH from AAVE v3 |
|
|
| Repay | repay debt on AAVE v3 |
|
|
| Check AAVE position parameters | (Read actions) check loan-to-value, health rate, liquidation threshold, borrowed amount, borrowable amount) |
|
|
{
"error": "internal server error."
}
curl -XPOST "https://api.brianknows.org/api/v0/agent/transaction" -d '{"prompt": "transfer 10 usdc to 0x05288402db9a6260a5edfeeb6e5922fd103280e579d103106788a2a33b42fc73 on starknet", "address": "0x0309e6b209031362268d62d646a067365e6f6d6eb7f571b5212cbdfd5f26fe54"}' -H "Content-Type: application/json" -H "x-brian-api-key: API_KEY"
curl -XPOST "https://api.brianknows.org/api/v0/agent/transaction" -d '{"prompt": "swap 10 usdc to eth on starknet", "address": "0x0309e6b209031362268d62d646a067365e6f6d6eb7f571b5212cbdfd5f26fe54"}' -H "Content-Type: application/json" -H "x-brian-api-key: API_KEY"
curl -XPOST "https://api.brianknows.org/api/v0/agent/transaction" -d '{"prompt": "transfer 2 sol to CnXMWB8W7bcnADsZsJAJYkcuu8jr392ZFvxDBiumW3ww on solana", "address": "53unSgGWqEWANcPYRF35B2Bgf8BkszUtcccKiXwGGLyr"}' -H "Content-Type: application/json" -H "x-brian-api-key: API_KEY"
curl -XPOST "https://api.brianknows.org/api/v0/agent/transaction" -d '{"prompt": "swap 2 sol to usdc on solana", "address": "53unSgGWqEWANcPYRF35B2Bgf8BkszUtcccKiXwGGLyr"}' -H "Content-Type: application/json" -H "x-brian-api-key: API_KEY"
| Name | Type | Description |
|---|---|---|
| prompt* | String | User input prompt. |
| compile | Boolean | If true, it compiles the contract and returns the ABI and bytecode |
| messages | array object[] | messages exchanged between the user and Brian (conversation history). |
Brian app settings page
Brian app create api key modal
const brian = new BrianSDK(options);
const request = await brian.ask({
prompt: "explain uniswap v4 compared to v3",
kb: "public-knowledge-box"
});
console.log("Knowledge result:", request);
/*
Knowledge result: {
input: "explain uniswap v4 compared to v3",
chat_history: [],
context: [
{
pageContent: "Two years ago, we released Uniswap v3, a watershed moment for onchain liquidity and DeFi. Today, the Uniswap Protocol is the largest decentralized exchange protocol, processing over $1.5 trillion in trading volume. As public infrastructure, it's a vital part of the crypto ecosystem.\nAs technology and markets evolve, so must the Uniswap Protocol. That's why we're thrilled to introduce our vision for Uniswap v4, which we believe will open up a world of possibilities for how liquidity is created and how tokens are traded onchain.\nWe are releasing the draft code now so that v4 can be built in public, with open feedback and meaningful community contribution. We expect this will be a months-long process. You can read the open-sourced, early version of the Uniswap v4 core and periphery repositories, read the draft technical whitepaper here, and learn more about how to contribute here.\nUniswap v3 took a powerful, opinionated approach to liquidity provision, balancing an incredibly complex tradeoff space. New features come at the expense of higher fees and code complexity. For example, v3 enshrined oracles, allowing builders to integrate real-time, onchain pricing data, but at the expense of some increased costs for swappers.\nOur vision with Uniswap v4 is to allow anyone to make these tradeoff decisions through the introduction of \"hooks.\" Hooks are contracts that run at various points of a pool action's lifecycle. Pools can make the same tradeoffs as v3, or they can add totally new functionality. For example, v4 will allow pools that natively support dynamic fees, add onchain limit orders, or act as a time-weighted average market maker (TWAMM) to spread out large orders over time.",
metadata: {
description: "All about our vision for Uniswap v4 and why we're building in public.",
language: "en",
source: "https://blog.uniswap.org/uniswap-v4",
title: "Our Vision for Uniswap v4 ",
},
}, {
pageContent: "License and Governance\nAs always, we strongly believe that core financial infrastructure should be open and transparent. We also believe that the Uniswap community — the people and teams that support, use, and build on the Protocol — should govern v4 of the Protocol, just as they govern prior versions.\nThe code will be released under a Business Source License 1.1, which limits the use of the v4 source code in a commercial or production setting for up to four years, at which point it will convert to a GPL license into perpetuity. Like v3, Uniswap Governance and Uniswap Labs can grant exceptions to the license.\nThe Protocol fee mechanism will also be modeled after v3. Governance will be able to vote to add a Protocol fee to any pool, up to a capped amount. More details on the fee mechanism can be found in the whitepaper.What is Uniswap v4Hooks & custom poolsImproved architecture and gas savingsLicense and GovernanceRelated posts March 23, 2021Introducing Uniswap v3 October 19, 2023Community Contributions to Uniswap v4 May 05, 2021Uniswap v3 Mainnet launch",
metadata: {
description: "All about our vision for Uniswap v4 and why we're building in public.",
language: "en",
source: "https://blog.uniswap.org/uniswap-v4",
title: "Our Vision for Uniswap v4 ",
},
}, {
pageContent: "Along with this customization, Uniswap v4's architecture reduces costs and ensures efficiency. It introduces a new \"singleton\" contract, where all pools live within a single smart contract. We believe the combination of hooks and singleton architecture creates an incredibly powerful platform ⸺ fast, safe pool customization and efficient routing across many pools. Uniswap v4 brings fast, expressive AMM innovation within one powerful ecosystem.\nWhat is Uniswap v4\nHooks & custom pools\nEach Uniswap liquidity pool has a lifecycle. During a pool’s lifecycle, several things happen. A pool is created with a default fee tier. Liquidity is added, removed, or readjusted. And, of course, users swap tokens. In Uniswap v3, these lifecycle events are tightly coupled and executed in a very strict sequence.\nTo create room for customizable liquidity in Uniswap v4, we want to create a way for pool deployers to introduce code that performs a designated action at key points throughout the pool’s lifecycle – like before or after a swap, or before or after an LP position is changed.\nEnter hooks, which are plugins to customize how pools, swaps, fees, and LP positions interact. Developers can innovate on top of the Uniswap Protocol’s liquidity and security to create customized AMM pools through hooks that integrate with v4’s smart contracts.\nSome experiments we’re excited about include:",
metadata: {
description: "All about our vision for Uniswap v4 and why we're building in public.",
language: "en",
source: "https://blog.uniswap.org/uniswap-v4",
title: "Our Vision for Uniswap v4 ",
},
}, {
pageContent: "Improved architecture and gas savings\nIn Uniswap v3, we deploy a new contract for every pool, making creating pools and performing multi-pool swaps more expensive. In v4, we hold all the pools in one singleton contract, which will provide important gas savings because swaps will no longer need to transfer tokens between pools held in different contracts. Early estimates show that v4 reduces pool creation gas costs by 99%. Hooks introduce a world with endless options and singleton allows you to efficiently route across all of them.\nThis singleton architecture is complemented by a new \"flash accounting\" system. Instead of transferring assets in and out of pools at the end of every swap in v3, this system transfers only on net balances -- meaning a far more efficient system that provides additional gas savings in Uniswap v4.\nWe believe the best design for flash accounting uses \"transient storage,\" which would be enabled by EIP-1153. This EIP is being considered as part of the Ethereum Cancun hardfork and will bring even bigger gas improvements and cleaner contract designs across a wide variety of applications.\nWith the efficiency of singleton and flash accounting, fee tiers no longer need to be limited. Pool creators can set them at the level that makes them most competitive or customize them with a dynamic fee hook. v4 also brings back support for native ETH, which offers additional gas savings.",
metadata: {
description: "All about our vision for Uniswap v4 and why we're building in public.",
language: "en",
source: "https://blog.uniswap.org/uniswap-v4",
title: "Our Vision for Uniswap v4 ",
},
}
],
answer: "Uniswap v4 represents a significant evolution from v3, allowing developers greater customization and efficiency while maintaining the core liquidity provision functionality. Here’s a structured comparison of Uniswap v4 and v3:\n\n\"\n\n### 1. **Core Architecture**\n\n- **Uniswap v3**: Each liquidity pool operates as a separate smart contract, which leads to higher costs for deploying new pools and conducting multi-pool swaps due to multiple contract interactions.\n \n- **Uniswap v4**: Introduces a **singleton architecture**, where all pools are managed under a single smart contract. This design dramatically reduces the gas fees associated with creating new pools and executing swaps, estimated to reduce pool creation gas costs by 99%.\n\n\"\n\n### 2. **Customizability Through Hooks**\n\n- **Uniswap v3**: Liquidities are managed in a tightly coupled manner with limited customization. The lifecycle of pools and swaps follows a strict sequence, constraining developers in terms of pool functionalities.\n\n- **Uniswap v4**: Implements **hooks**, which are plugins that allow developers to execute custom logic at various points in the pool's lifecycle, such as before and after swaps or liquidity changes. This opens a plethora of innovative possibilities, allowing for customized AMM functionality and improved interaction between swaps and LP positions.\n\n\"\n\n### 3. **Dynamic Fee Structures**\n\n- **Uniswap v3**: Introduces fee tiers, but these are set initially and not easily adjustable post-deployment. While LPs could theoretically offer different fees, making them competitive would require deploying multiple pools.\n\n- **Uniswap v4**: Enhances fee customization by allowing pools to support **dynamic fees** with hooks, enabling the fee structure to adapt more responsively to market conditions or specific trading strategies.\n\n\"\n\n### 4. **Flash Accounting Efficiency**\n\n- **Uniswap v3**: Transfers assets at the end of every swap, resulting in significant transaction overhead and gas costs.\n\n- **Uniswap v4**: Employs a new **flash accounting** system that transfers only net balances after transactions, significantly improving efficiency. This is complemented by the anticipated benefits of **EIP-1153**, which may further streamline contract interactions and reduce operational overhead.\n\n\"\n\n### 5. **Gas Savings and Native Token Support**\n\n- **Uniswap v3**: Lacks substantial gas optimization features and does not support native ETH for liquidity provision, limiting options for LPs looking to minimize transaction costs.\n\n- **Uniswap v4**: Reintroduces support for **native ETH**, offering additional gas savings and providing LPs with an opportunity to optimize their capital efficiency.\n\n\"\n\n### 6. **License and Governance**\n\n- **Uniswap v3**: Governed by Uniswap governance procedures; the protocol fee mechanism allows for some fee adjustments based on community votes.\n\n- **Uniswap v4**: Continues the principle of decentralized governance under a **Business Source License 1.1**, which permits the community to effectively govern the protocol while restricting commercial use for a transitional period before converting to a GPL license.\n\n\"\n\n### Conclusion\n\nIn summary, Uniswap v4 is designed to empower developers and liquidity providers by enhancing customized features while optimizing overall gas efficiency and operational costs. The introduction of hooks and a singleton architecture not only paves the way for novel AMM functionalities but also supports a more sustainable economic ecosystem within decentralized finance.\n\nFor further information, you can access the open-source version of the [Uniswap v4 core and periphery repositories](https://github.com/Uniswap) or read the accompanying [draft technical whitepaper](https://uniswap.org/docs/v4).",
}
*/